Skip Headers
JD Edwards EnterpriseOne Applications Interoperability Fundamentals Implementation Guide
Release 9.1

E15081-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

10 Processing Interoperability for Shop Floor Management

This chapter contains the following topics:

10.1 Processing Outbound Interoperability for Shop Floor Management

This section provides an overview of outbound interoperability for Shop Floor Management, lists a prerequisite, and discusses how to:

  • Set selected processing options for originating programs.

  • Set selected additional processing options for Hours and Quantities Update (R31422).

  • Set selected additional processing options for Work Order Completions (P31114).

10.1.1 Understanding Outbound Interoperability for Shop Floor Management

You might need to send to another system transactions that you create or change in Shop Floor Management. For example, if the organization uses handheld scanning devices, you can use interoperability transactions to update the database used by the scanning devices.

This table lists the JD Edwards EnterpriseOne Shop Floor Management programs from which you can send transactions to an external system:

Originating Program Transaction Type EDI Outbound Interface Table Extraction Program
Enter/Change Order (P48013) JDEWO Outbound Work Order Header (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Enter/Change Rate Schedule (P3109) JDEWO Outbound Work Order Header (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Order Processing (R31410) JDEWO: Work Order Transaction Type

JDEPL: Parts List Transaction Type

JDERTG: Routing Instructions Transaction Type

Outbound Work Order Header (F4801Z1)

Warranty Claim/Supplier Recovery processing (F3111Z2)

Outbound Work Order Extraction (R4801Z1X)

Outbound Supplier Recovery Processing (R174801Z2O)

Inventory Issues (P31113) JDEII: Inventory Issue Transaction Type

JDEWO: Work Order Transaction Type

Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Hours and Quantities Update (R31422) JDEWO Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Work Order Completions (P31114) JDEWO Outbound Work Order Header interface (F4801Z1) Outbound Work Order Extraction (R4801Z1X)
Work Order Parts Detail (P17730) JDEII (Inventory Issues) Outbound Work Order Parts List (F3111Z1) N/A
Work Order Parts Detail (P17730) JDEPL (WO Parts List Transactions) Outbound Work Order Header (F4801Z1)

Outbound Work Order Parts List (F3111Z1)

N/A

To create outbound transactions, specify the appropriate transaction type in the processing options for these programs. The system places a copy of the transaction in the interface table for that type of transaction. The system uses the Flat File Cross-Reference Table (F47001) to identify the interface tables to populate based on the transaction type you specify in the processing options.

The system creates the outbound transaction in EDI format. External systems can process the transactions using standard EDI processing, including extraction.

You run outbound extraction programs to retrieve data from the outbound transaction tables and create a flat file if one does not exist, or to append to an existing flat file. Every field is written from the EDI interface tables to the flat file.

10.1.1.1 Work Order Parts Detail

To process outbound interoperability for work order parts detail transactions:

  1. Specify a transaction type in the processing options of the Work Order Parts Detail program (P17730).

  2. Enter or change a record in this originating program.

    The system calls a master business function that writes records to the Outbound Work Order Header table (F4801Z1) and the Outbound Work Order Parts List table (F3111Z1). The same master business function calls a special subsystem API that sends a message to the subsystem kernel running on the server. The subsystem kernel adds a record to the Subsystem Job Master table (F986113).

  3. Create a custom UBE or function to process the data from the F4801Z1 and F3111Z1 tables in such a way that it can be used by the external system.

  4. Use the Data Export Controls program (P0047) to specify the custom UBE or function for the transaction type you specified in the processing options of the originating program.

    The system stores this information in the Data Export Control table (F0047).

  5. Run the Interoperability Generic Outbound Subsystem UBE program (R00460).

    The Interoperability Generic Outbound Subsystem UBE program fetches the F986113 record and retrieves the name and version of the custom UBE from the F0047 table. The Interoperability Generic Outbound Subsystem UBE program passes information about the order to the custom UBE. The custom UBE then retrieves the records from the F4801Z1 and F3111Z1A tables and processes that information.

10.1.2 Prerequisite

Define the data export controls for the type of outbound transaction. The system uses data export controls to determine the batch programs or business processes that third parties supply for use in processing transactions.

See Setting Up Data Export Controls.

10.1.3 Setting Selected Processing Options for Originating Programs

This section lists only the processing options that are specific to outbound interoperability. These processing options are used for the following programs:

  • Enter/Change Order (P48013)

  • Enter/Change Rate Schedule (P3109)

  • Order Processing (R31410)

  • Inventory Issues (P31113)

  • Hours and Quantities Update (R31422)

  • Work Order Completions (P31114)

  • Work Order Parts Detail (P17730)

Transaction Type

Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed.

Before Image

Specify whether the system creates a record of the image before it was changed, in addition to a record of the transaction after the change. The system creates these records in the unedited transaction table when outbound interoperability processing is enabled. Values are:

Blank: Write the record only after it has been changed; do not write a before image record.

1: Write two records: one before the image is changed and one after the image is changed.

10.1.4 Setting Selected Additional Processing Options for Hours and Quantities Update (R31422)

The Hours and Quantities Update program has a unique processing option in addition to the interoperability processing options that are common to all of the originating programs.

10.1.4.1 Interop

2. Outbound Subsystem UBE

Enter 1 to call the subsystem after the Hours and Quantities Update program (P31422) successfully processes the outbound transactions.

10.1.5 Setting Selected Additional Processing Options for Work Order Completions (P31114)

The Work Order Completions program has a unique processing option in addition to the interoperability processing options that are common to all of the originating programs.

10.1.5.1 Interop

2. Call Outbound Subsystem

Enter 1 to call the subsystem after the Work Order Completions program (P31114) has successfully processed an outbound transaction.

10.2 Processing Inbound Interoperability for Shop Floor Management

This section provides an overview of inbound interoperability for Shop Floor Management, lists prerequisites, and discusses how to:

  • Set processing options for Inbound Hours and Quantity Processor (R31122Z1I).

  • Set processing options for Inbound Inventory Issues Processor (R31113Z1I).

  • Set processing options for Inbound Completion Processor (R31114Z1I).

  • Set processing options for Inbound Super Backflush Processor (R31123Z1I).

  • Setting processing options for Inbound Kanban Transaction (R30161Z1I).

  • Run the inbound processing programs.

10.2.1 Understanding Inbound Interoperability for Shop Floor Management

In an inbound transaction, you accept data from another system into this system.

10.2.1.1 Interoperability Programs

JD Edwards EnterpriseOne Shop Floor Management provides these versions of the Inbound Flat File Conversion program (R47002C):

  • Inbound Backflush Flat File Conversion.

  • Inbound Completion Flat File Conversion.

  • Inbound Issues Flat File Conversion.

  • Inbound Work Order Flat File Conversion.

See Processing Inbound Interoperability Transactions.

10.2.1.2 Hours and Quantities Inbound Transactions

The interoperability interface table for hours and quantities inbound transactions is the Work Order Time Transactions Unedited Transaction table (F31122Z1).

You run the Inbound Hours and Quantity Processor program (R31122Z1I) to copy the information from the F31122Z1 table to the related application tables.

10.2.1.3 Inventory Issues Inbound Transactions

The interoperability interface table for inventory issues inbound transactions is the Outbound Work Order Parts List table (F3111Z1).

You run the Inbound Inventory Issues Processor program (R31113Z1I) to copy the information from the F3111Z1 table to the related application tables.

10.2.1.4 Completion Inbound Transactions

The interoperability interface table for completion inbound transactions is the Outbound Work Order Header table (F4801Z1).

You run the Inbound Completion Processor program (R31114Z1I) to copy the information from the F4801Z1 table to the related application tables.

10.2.1.5 Super Backflush Inbound Transactions

The interoperability interface table for completion inbound transactions is the Outbound Work Order Routings table (F3112Z1).

You run the Inbound Super Backflush Processor program (R31123Z1I) to copy the information from the F3112Z1 table to the related application tables.

10.2.1.6 Kanban Inbound Transactions

The interoperability interface table for kanban transactions is the Inbound Kanban Card Detail table (F30161Z1).

You run the Inbound Kanban Transaction program (R30161Z1I) to copy the information from the F30161Z1 table to the related application tables.

10.2.2 Prerequisites

Before you complete the tasks in this section:

10.2.3 Setting Processing Options for Inbound Hours and Quantity Processor (R31122Z1I)

Processing options enable you to specify the default processing for programs and reports.

10.2.3.1 Versions

1. Enter the version for P311221 Hours and Quantities to be called.

Enter a version of hours and quantities. If you leave this processing option blank, the system uses ZJDE0001.

10.2.3.2 Printing

1. Enter '1' to print unsuccessfully processed records only.

Specify the type of processing for an event. If you leave this processing option blank, the system prints all records.

10.2.4 Setting Processing Options for Inbound Inventory Issues Processor (R31113Z1I)

Processing options enable you to specify the default processing for programs and reports.

10.2.4.1 Versions

1. Enter the Version of Work Order Inventory Issues (P31113) to be called.

Enter a version of work order inventory issues. If you leave this processing option blank, the system uses ZJDE0001.

10.2.5 Setting Processing Options for Inbound Completion Processor (R31114Z1I)

Processing options enable you to specify the default processing for programs and reports.

10.2.5.1 Versions

Enter the version of Inventory Completions (P31114).

Enter a version of inventory completions.

The system has versions that begin with XJDE or ZJDE. If you leave this processing option blank, the system uses ZJDE0001.

10.2.5.2 Process

1. Enter '1' to print only the records with errors.

Specify the type of processing for an event.

10.2.6 Setting Processing Options for Inbound Super Backflush Processor (R31123Z1I)

Processing options enable you to specify the default processing for programs and reports.

10.2.6.1 Data Edits

Enter the Version of Work Order Super Backflush (P31123).

Enter a version of work order super backflush. If you leave this processing option blank, the system uses ZJDE0001.

10.2.6.2 Printing

1. Enter '1' to print unsuccessfully processed records only.

Specify the type of processing for an event. If you leave this processing option blank, the system prints all records.

10.2.7 Setting Processing Options for Inbound Kanban Transaction (R30161Z1I)

Processing options enable you to specify the default processing for programs and reports.

10.2.7.1 Versions

1. Enter the version of Kanban Processing (P3157).

Enter a version of the Kanban Processing program. If you leave this processing option blank, the system uses ZJDE0001.

10.2.7.2 Printing

1. Enter '1' to print unsuccessfully processed records only.

Enter 1 to print only records that are not processed successfully. If you leave this processing option blank, all records are printed.

10.2.8 Running the Inbound Processing Programs

To receive hours and quantity inbound transactions, select Shop Floor Management Interoperability (G31311), Inbound Hours and Quantity Processor.

To receive inventory issues inbound transactions, select Shop Floor Management Interoperability (G31311), Inbound Inventory Issues Processor.

To receive completion inbound transactions, select Shop Floor Management Interoperability (G31311), Inbound Completion Processor.

To receive super backflush inbound transactions, select Shop Floor Management Interoperability (G31311), Inbound Super Backflush Processor.

To receive kanban inbound transactions, select Shop Floor Management Interoperability (G31311), Inbound Kanban Transaction.

10.3 Reviewing and Revising Interoperability Transactions for Shop Floor Management

This section provides an overview of reviewing and revising interoperability transactions for Shop Floor Management, lists the forms used to review and revise interoperability transactions for Shop Floor Management, and discusses how to:

  • Set processing options for Inbound Work Order Inquiry (P4801Z1).

  • Set processing options for Inbound Hours and Quantity Inquiry (P31122Z1).

  • Set processing options for Inbound Inventory Issues Inquiry (P3111Z1).

  • Set processing options for Inbound Super Backflush Inquiry (P3112Z1).

  • Set processing options for Kanban Transactions Revisions (P30161Z1).

10.3.1 Understanding Reviewing and Revising Interoperability Transactions for Shop Floor Management

Running one of the transaction processes, such as the Inbound Work Order Inquiry (P4801Z1), often identifies one or more inbound transactions that contain invalid transactions. For example, a work order might have an invalid item number. In that case, the program cannot add that work order to the Work Order Master table (F4801). Instead, the program sends an error message to the Employee Work Center program (P012501), which indicates the transaction number for the transaction in error.

Use the inbound inquiry programs to review and revise inbound transactions, as well as to add, change, or delete transactions that contain errors. Then run the transaction process again. Continue to make corrections and rerun the transaction process until the program runs without errors.

See "Running Inquiries and Revising EDI Documents" in the JD Edwards EnterpriseOne Applications Data Interface for Electronic Data Interchange Implementation Guide.

10.3.2 Forms Used to Review and Revise Interoperability Transactions for Shop Floor Management

Form Name FormID Navigation Usage
Work With Outbound Work Order Header W4801Z1A Shop Floor Management Interoperability (G31311), Inbound Work Order Inquiry

Shop Floor Management Interoperability (G31311), Outbound Work Order Inquiry

hop Floor Management Interoperability (G31311), Inbound Completion Inquiry

Locate interoperability transaction records.
Outbound Work Order Header Revisions W4801Z1B Select a transaction record on the Work With Outbound Work Order Header form and click Select. Locate and review an inbound or outbound transaction record.

After you correct the errors identified by the inquiry program, run the transaction process again.

Transaction Record Revisions for F31122Z1 W31122Z1B Shop Floor Management Interoperability (G31311), Inbound Hours and Quantity Inquiry

Locate a transaction record and click Select.

Locate and review an inbound transaction record.

After you correct the errors identified by the Inbound Hours and Quantity Inquiry program, run the transaction process again.

Work Order Inventory Issues Transactions Revision W3111Z1B Shop Floor Management Interoperability (G31311), Inbound Inventory Issues Inquiry

Locate a transaction record and click Select.

Locate and review an inbound transaction record.

After you correct the errors identified by the Inbound Inventory Issues Inquiry program, run the transaction process again.

Work Order Super Backflush Transactions Revisions W3112Z1B Shop Floor Management Interoperability (G31311), Inbound Super Backflush Inquiry

Locate a transaction record and click Select.

Locate and review an inbound transaction record.

After you correct the errors identified by the Inbound Super Backflush Inquiry program, run the transaction process again.

Kanban Transactions Revisions W30161Z1B hop Floor Management Interoperability (G31311), Kanban Transactions Revisions

Locate a transaction record and click Select.

Locate and review an inbound transaction record.

After you correct the errors identified by the Kanban Transactions Revisions program, run the transaction process again.


10.3.3 Setting Processing Options for the Inbound Work Order Inquiry Program (P4801Z1)

Processing options enable you to specify the default processing for programs and reports.

10.3.3.1 Display

1. Default View Mode.

Specify the type of processing for an event. Values are:

1: View unprocessed records

2: View records processed successfully

3: View records processed unsuccessfully

If you leave this processing option blank, the system uses View unprocessed records as the default.

2. Enter the Direction Indicator value.

Specify whether the transaction is inbound or outbound. Values are:

1: Inbound

2: Outbound

If you leave this processing option blank, the system uses Outbound as the default.

3. Enter the value for the screen to be displayed.

Enter 1 or leave this processing option blank to display the Work Order Revisions form. Enter 2 to display the Completion Revisions form.

10.3.3.2 Defaults

1. Enter the Transaction Type for new Work Order Header Transactions.

Specify the type of transaction for the work order. If you leave this processing option blank, the system uses JDEHO.

2. Enter the Transaction Type for new Work Order Parts List Transactions.

Specify the type of transaction for the work order parts list. If you leave this processing option blank, the system uses JDEPL.

3. Enter the Transaction Type for new Work Order Routings Transactions.

Specify the type of transaction for the work order routings. If you leave this processing option blank, the system uses JDERTG.

10.3.3.3 Process 1

1. Name of Inbound Subsystem UBE to call to process Inbound transactions.

Specify the program to process the transactions. If you leave this processing option blank, the system uses R31122Z1I.

2. Version of Inbound UBE.

Enter a version of Inbound UBE. If you leave this processing option blank, the system uses XJDE0002.

10.3.4 Setting Processing Options for the Inbound Hours and Quantity Inquiry Program (P31122Z1)

Processing options enable you to specify the default processing for programs and reports.

10.3.4.1 Display

1. Default View Mode.

Specify the type of processing for an event. Values are:

1: View unprocessed records

2: View records processed successfully

3: View records processed unsuccessfully

If you leave this processing option blank, the system uses View unprocessed records as the default.

2. Enter the Direction Indicator value.

Specify whether the transaction is inbound or outbound. If you leave this processing option blank, the system uses Inbound as the default. Values are:

1: Inbound

2: Outbound

10.3.4.2 Defaults

1. Enter the Transaction Type for new Work Order Header Transactions.

Specify the transaction for the work order. If you leave this processing option blank, the system uses JDEHO.

10.3.4.3 Process

1. Name of Inbound Subsystem UBE to call to process Inbound transactions.

Specify the object member to be sent out on a PTF request. If you leave this processing option blank, the system uses R31122Z1I as the default.

2. Version of Inbound UBE to call.

Enter a version of Inbound UBE. If you leave this processing option blank, the system uses XJDE0002.

10.3.5 Setting Processing Options for Inbound Inventory Issues Inquiry (P3111Z1)

Processing options enable you to specify the default processing for programs and reports.

10.3.5.1 Display

1. Default View Mode.

Specify the type of processing for an event. If you leave this processing option blank, the system uses View unprocessed records as the default. Values are:

1: View unprocessed records

2: View records processed successfully

3: View records processed unsuccessfully

2. Enter the Direction Indicator value.

Specify whether the transaction is inbound or outbound. Values are:

If you leave this processing option blank, the system uses Inbound as the default. Values are:

1: Inbound

2: Outbound

10.3.5.2 Defaults

1. Enter the Transaction Type for new Work Order Header Transactions.

Specify a specific type of transaction for the work order. If you leave this processing option blank, the system uses JDEII.

10.3.5.3 Process

1. Name of Inbound Subsystem UBE to call to process Inbound transactions.

Specify the object member to be sent out on a PTF request. If you leave this processing option blank, the system uses R31113Z1I.

2. Version of Inbound UBE to call.

Enter a version of Inbound UBE. If you leave this processing option blank, the system uses XJDE0002.

10.3.6 Setting Processing Options for Inbound Super Backflush Inquiry (P3112Z1)

Processing options enable you to specify the default processing for programs and reports.

10.3.6.1 Display

1. Default View Mode.

Specify the type of processing for an event. If you leave this processing option blank, the system uses View unprocessed records as the default. Values are:

1: View unprocessed records

2: View records processed successfully

3: View records processed unsuccessfully

Enter the Direction Indicator value.

Specify whether the transaction is inbound or outbound.

If you leave this processing option blank, the system uses inbound as the default. Values are:

1: Inbound

2: Outbound

10.3.6.2 Defaults

1. Enter the Transaction Type for new Work Order Header Transactions.

Specify the transaction for the work order. If you leave this processing option blank, the system uses JDESBF.

10.3.6.3 Process

1. Name of Inbound Subsystem UBE to call to process Inbound transactions.

Specify the object member to be sent out on a PTF request. If you leave this processing option blank, the system uses R31123Z1I.

2. Version of Inbound UBE to call.

If you leave this processing option blank, the system uses ZJDE0001 (inbound records) as the default.

10.3.7 Setting Processing Options for Kanban Transactions Revisions (P30161Z1)

Processing options enable you to specify the default processing for programs and reports.

10.3.7.1 Display

1. Default View mode.

Specify a value to indicate how the system displays the records. Values are:

1: The system displays the unprocessed records.

2: The system displays all successfully processed records.

3: The system displays all unsuccessfully processed records.

2. Enter the Direction Indicator value.

Specify a code that indicates whether the transaction is inbound or outbound. Values are:

1: Inbound Records

2: Outbound Records

10.3.7.2 Defaults

Transaction Type

Enter the transaction type for new Kanban transactions. If you leave this processing option blank, the system uses JDEKNB.

10.3.7.3 Process

Inbound Subsystem UBE

Enter the name of the inbound subsystem UBE to call to process inbound transactions. If you leave this processing option blank, the system uses R30161Z1I.

Version of Inbound UBE

Specify a version of the inbound subsystem UBE. If you leave this processing option blank, the system uses XJDE0001.

10.4 Purging Interoperability Transactions for Shop Floor Management

This section provides an overview of purging interoperability transactions and discusses how to purge interoperability transactions.

10.4.1 Understanding Purging Interoperability Transactions

When data becomes obsolete or you need more disk space, you can use purge programs to remove data from interface tables.

The interoperability menu contains options for purging transactions. Use one of these purge programs to remove data from the corresponding interface tables:

  • Interoperability Work Order Purge (R4801Z1P)

  • Inbound Hours and Quantity Purge (R31122Z1)

  • Inbound Inventory Issues Purge (R3111Z1P)

  • Inbound Completion Purge (R4801Z1)

  • Inbound Super Backflush Purge (R3112Z1P)

  • Inbound Kanban Purge (R30161Z1P)

For records in the Processing Log table (F0046) that are marked as processed, the program purges the associated transactions in the corresponding interoperability tables, as well as the records in the F0046 table. If the records in the F0046 table are not marked as processed, the program does not purge any records.

When you purge cycle count transactions, you can set the processing option to print only the records that are in error. Otherwise, the program prints all records that are deleted.

10.4.2 Purging Interoperability Transactions

To purge inbound or outbound work order transactions, select Shop Floor Management Interoperability (G31311), Interoperability Work Order Purge.

To purge inbound hours and quantity transactions, select Shop Floor Management Interoperability (G31311), Inbound Hours and Quantity Purge.

To purge inbound inventory issues transactions, select Shop Floor Management Interoperability (G31311), Inbound Inventory Issues Purge.

To purge inbound completion transactions, select Shop Floor Management Interoperability (G31311), Inbound Completion Purge.

To purge inbound super backflush transactions, select Shop Floor Management Interoperability (G31311), Inbound Super Backflush Purge.

To purge inbound kanban transactions, select Shop Floor Management Interoperability (G31311), Inbound Kanban Purge.