This chapter contains the following topics:
Section 9.1, "Processing Outbound Interoperability for Product Data Management"
Section 9.2, "Processing Inbound Interoperability for Product Data Management"
Section 9.3, "Reviewing and Revising Interoperability Transactions for Product Data Management"
Section 9.4, "Purging Interoperability Transactions for Product Data Management"
This section provides an overview of outbound interoperability for Product Data Management, lists a prerequisite, and discusses how to:
Set selected processing options for Work Center Revision (P3006).
Set processing options for Workday Calendar (P00071).
Set selected processing options for Enter/Change Bill (P3002).
Set selected processing options for Work With Routing Master (P3003).
You might send transactions that you create or change in Product Data Management to another system. For example, if the organization uses hand-held scanning devices, you can use interoperability transactions to update the database that is used by the scanning devices.
To process outbound interoperability in JD Edwards EnterpriseOne Product Data Management:
Specify a transaction type in the processing options of the originating programs listed in the table that follows these steps.
Enter or change a transaction using any of the originating programs.
The JD Edwards EnterpriseOne Product Data Management system calls a business function that writes records to the corresponding transaction table listed in the table that follows these steps. For example, when you run the Work Center Revision program (P3006) with the interoperability processing option turned on, the system places a copy of updated work center data in the Work Center Transaction File table (F30006Z1).
The same 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).
Create a custom UBE or function to process the data from the transaction tables in such a way that it can be used by the external system.
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).
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 transaction tables and processes that information.
You can send transactions to an external system from these programs in Product Data Management:
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.
This section lists only the processing options for the Work Center Revision program (P3006) that are specific to outbound interoperability.
You use these processing options to set up outbound interoperability.
Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed.
|
Note: We provide transaction type JDEWC for work center transactions. |
Specify whether the system creates a record of the work center transaction before it was changed, in addition to a record of the work center transaction after the change. The system creates these records in the Work Center Transaction File table (F30006Z1) when outbound interoperability processing is enabled. Values are:
Blank: Write the work center record only after it has been changed; do not write a before image record.
1: Write two work center records: one before the work center transaction is changed and one after the work center transaction is changed.
This section lists all the processing options for the Workday Calendar program (P00071).
You use these processing options to set up outbound interoperability.
Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed.
|
Note: We provide transaction type JDEWDC for workday calendar transactions. |
Specify whether the system creates a record of the workday calendar transaction before it was changed, in addition to a record of the workday calendar transaction after the change. The system creates these records in the Work Day Calendar Transaction File table (F0007Z1) when outbound interoperability processing is enabled. Values are:
Blank: Write the workday calendar record only after it has been changed; do not write a before image record.
1: Write two workday calendar records: one before the workday calendar transaction is changed and one after the workday calendar transaction is changed.
This section lists only the processing options for the Enter/Change Bill program (P3002) that are specific to outbound interoperability.
You use these processing options to set up outbound interoperability.
Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed.
|
Note: We provide transaction type JDEBOM for bill of material transactions. |
Specify whether the system creates a record of the bill of material transaction before it was changed, in addition to a record of the bill of material transaction after the change. The system creates these records in the Bill of Material Transaction File table (F3002Z1) when outbound interoperability processing is enabled. Values are:
Blank: Write the bill of material record only after it has been changed; do not write a before image record.
1: Write two bill of material records: one before the bill of material transaction is changed and one after the bill of material transaction is changed.
Specify the version of the Interoperability Outbound Subsystem program (R00460) that the system uses for export processing. If you leave this processing option blank, the system uses the ZJDE0001 version.
Versions control how the Interoperability Outbound Subsystem program displays information. Therefore, you might need to set the processing option to a specific version to meet your needs.
This section lists only the processing options for the Work With Routing Master program (P3003) that are specific to outbound interoperability.
You use these processing options to set up outbound interoperability.
Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed.
|
Note: We provide transaction type JDEROU for routing transactions. |
Specify the version that the system uses when you access the Outbound Processing program (R00460) from the Enter/Change Routing form. If you leave this processing option blank, the system uses version ZJDE0001
Specify whether the system creates a record of the routing transaction before it was changed, in addition to a record of the routing transaction after the change. The system creates these records in the Routing Transactions File table (F3003Z1) when outbound interoperability processing is enabled. Values are:
Blank: Write the routing record only after it has been changed; do not write a before image record.
1: Write two routing records: one before the routing transaction is changed and one after the routing transaction is changed.
This section provides an overview of inbound interoperability for Product Data Management, lists prerequisites, and discusses how to:
Set processing options for Process Inbound Routing (R3003Z1I)
Run the inbound processing programs.
In an inbound transaction, you accept data from another system into this system.
The Inbound Flat File Conversion program (R47002C) copies the data from a flat file to the Work Center Transaction File table (F30006Z1) if you have set up a flat file cross-reference to this table.
|
Note: We provide transaction type JDEWC for work center transactions. |
You run the Process Inbound Work Center program (R30006Z1I) to copy the information from the F30006Z1 table to the Work Center Master File table (F30006).
The Inbound Flat File Conversion program (R47002C) copies the data from a flat file to the Work Day Calendar Transaction File table (F0007Z1) if you have set up a flat file cross-reference to this table.
|
Note: We provide transaction type JDEWDC for work day calendar transactions. |
You run the Process Inbound Work Day Calendar DC program (R0007Z1I) to copy the information from the F0007Z1 table to the Workday Calendar table (F0007).
The Inbound Flat File Conversion program (R47002C) copies the data from a flat file to the Bill of Material Transaction File table (F3002Z1) if you have set up a flat file cross-reference to this table.
|
Note: We provide transaction type JDEBOM for bill of material transactions. |
You run the Process Inbound Bill of Material program (R3002Z1I) to copy the information from the F3002Z1 table to the Bill of Material Master File table (F3002).
The Inbound Flat File Conversion program (R47002C) copies the data from a flat file to the Routing Transactions File table (F3003Z1) if you have set up a flat file cross-reference to this table.
|
Note: We provide transaction type JDEROU for routing transactions. |
You run the Process Inbound Routing program (R3003Z1I) to copy the information from the F3003Z1 table to the Routing Master File table (F3003).
Before you complete the tasks in this section:
Set up flat file cross-references.
Run the Inbound Flat File Conversion program (R47002C).
See Running the Inbound Flat File Conversion Program (R47002C).
Processing options enable you to specify the default processing for programs and reports.
Specify a version of the Work With Routing Master program (P3003). If you leave this processing option blank, the system uses version ZJDE0001
To process inbound work center data, select Product Data Interoperability (G30311), Process Inbound Work Center Transactions.
To process inbound work day calendar data, select Product Data Interoperability (G30311), Process Inbound WDC Transactions.
To process inbound bill of material data, select Product Data Interoperability (G30311), Process Inbound BOM.
To process inbound routing data, select Product Data Interoperability (G30311), Process Inbound Routing.
This section provides an overview of reviewing and revising inbound interoperability transactions for Product Data Management, lists the forms used to review and revise interoperability transactions for Product Data Management, and discusses how to:
Set common processing options for revision programs.
Set additional processing options for Bill Of Material Transaction Revisions (P3002Z1).
Running one of the transaction processes, such as the Work Center Transaction Revisions, often identifies one or more inbound transactions that contain invalid transactions. For example, a work center might have an invalid location branch. In that case, the program cannot add that work center to the Work Center Master File table (F30006). Instead, the program sends an error message to the Employee Work Center indicating the transaction number for the transaction in error.
Use the inquiry menu selections to add, change, or delete transactions containing errors. Then run the transaction process again. Continue to make corrections and rerun the transaction process until the program runs without errors.
You can also use the inquiry menu selects to review and revise outbound transactions.
|
See Also:
|
The revision programs use many of the same processing options. The processing options discussed in this section apply to:
Specify the type of processing for an event. Values are:
Blank: Inquire at the transaction level.
1: Inquire at the batch level.
Specify the type of processing for an event. Values are:
Blank: Both Possessed and Unprocessed
1: Processed
2: Unprocessed
Specify a flag that indicates that data is case sensitive. Values are:
Blank: Both Inbound and Outbound
1: Inbound
2: Outbound
The Bill of Material Transaction Revisions program has a unique processing option in addition to the processing options that are common to all of the revision programs.
Enter the version for Processed Inbound Bill of Material to submit. If you leave this processing option blank, the system uses ZJDE0001.
This section provides an overview of purging interoperability transactions and discusses how to purge interoperability transactions.
When data becomes obsolete or when you need more disk space, you can use the Purge Interoperability Table programs to remove data from the interoperability tables.
Product Data Management contains purge options for both inbound and outbound transactions. Use these purges to remove data from the corresponding interoperability tables:
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.
To purge interoperability transactions for work center transactions, select Product Data Interoperability (G30311), Purge Work Center Transactions.
To purge interoperability transactions for workday calendar transactions, select Product Data Interoperability (G30311), Purge WDC Transactions.
To purge interoperability transactions for bill of material transactions, select Product Data Interoperability (G30311), Purge BOM Transactions.
To purge interoperability transactions for routing transactions, select Product Data Interoperability (G30311), Purge Routing Transactions.