## Processing Interoperability for Procurement

This chapter discusses how to:

- Process outbound interoperability for Procurement.

- Process inbound interoperability for Procurement.

- Review and revise inbound interoperability transactions for Procurement.

- Purge interoperability transactions for Procurement.

### Processing Outbound Interoperability for Procurement

This section provides an overview of outbound interoperability for Procurement, lists a prerequisite, and discusses how to set selected processing options for the Enter Purchase Orders program (P4310).

#### Understanding Outbound Interoperability for Procurement

To process outbound interoperability in Procurement:

1. Specify a transaction type in the processing options of the Enter Purchase Orders program (P4310).

   The system provides transaction type JDEPOOUT for purchase orders.

2. Enter or change a purchase order using the Enter Purchase Orders program.

   The JD Edwards EnterpriseOne Procurement system calls a business function that writes records to the Purchase Order Header Unedited Transaction Table (F4301Z1) and the Purchase Order Detail Unedited Transaction Table (F4311Z1). 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).

3. Create a custom UBE to process the data from the F4301Z1 and F4311Z1 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 for the transaction type you specified in the processing options of the Enter Purchase Orders 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 F4301Z1 and F4311Z1 tables and processes that information.

#### 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.

#### Setting Selected Processing Options for Enter Purchase Orders (P4310)

This section lists only the processing options for the Enter Purchase Orders program (P4310) that are specific to outbound interoperability.

12-Interop

You use these processing options to set up outbound interoperability.

1. Purchase Order Before/After Image Processing | Specify whether the system creates a record of the purchase order before it was changed, in addition to a record of the purchase order after the change. The system creates these records in the Purchase Order Header Unedited Transaction Table (F4301Z1) and the Purchase Order Detail Unedited Transaction Table (F4311Z1) when outbound interoperability processing is enabled. Values are: Blank: Write the purchase order record only after it has been changed; do not write a before image record. 1: Write two purchase order records: one before the purchase order is changed and one after the purchase order is changed.
2. Purchase Order Transaction Type | Specify the transaction type for the interoperability transaction. If you leave this processing option blank, the outbound interoperability is not performed. Note. The system provides transaction type JDEPOOUT for outbound purchase orders.
3. Work Order Before/After Image Processing | Specify whether the system creates a record of the work order before it was changed, in addition to a record of the work order after the change. The system creates these records in the Purchase Order Header Unedited Transaction Table (F4301Z1) and the Purchase Order Detail Unedited Transaction Table (F4311Z1) when outbound interoperability processing is enabled. Values are: Blank: Write the work order record only after it has been changed; do not write a before image record. 1: Write two work order records: one before the work order is changed and one after the work order is changed.
4. Work Order Transaction Type | Specify the transaction type for work orders. If you leave this processing option blank, the outbound interoperability for work orders is not performed. Note. The system provides transaction type JDEWO for work orders.

### Processing Inbound Interoperability for Procurement

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

- Set processing options for Inbound Purchase Order (R4311Z1I).

- Set processing options for Receiving Advice Edit/Create (R47071).

- Set processing options for Receipt Routing Inbound Processor (R43092Z1I).

- Run the Inbound Purchase Order program.

- Run the Receiving Advice Edit/Create program.

- Run the Receipt Routing Inbound Processor program.

#### Understanding Inbound Interoperability for Procurement

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

Inbound Purchase Orders

You might receive inbound purchase orders, for example, if you are using a third-party manufacturing system and need to create a purchase order in Procurement software. In this example, the manufacturing system maps the data to a flat file.

The Inbound Flat File Conversion program (R47002C) copies the data from a flat file to the Purchase Order Header Unedited Transaction Table (F4301Z1) and the Purchase Order Detail Unedited Transaction Table (F4311Z1) if you have set up a flat file cross-reference to these tables.

Note. The system provides transaction type JDEPOIN for inbound purchase order transactions.

You run the Inbound Purchase Order program (R4311Z1I) to copy the information from these unedited transaction tables to the Purchase Order Header table (F4301) and the Purchase Order Detail File table (F4311).

Review of Receiving Advice Edit/Create

The Receiving Advice document is a confirmation from the customer or off-site consigned warehouse to the supplier that the goods or services were received. This document includes the condition of the received items and customer's acceptance or rejection of the received items.

When a supplier sends you receiving advice documents, the translator software maps the data into a flat file, and the Inbound Flat File Conversion program copies it to the EDI Receiving Advice Header - Inbound table (F47071) and the EDI Receiving Advice Detail - Inbound table (F47072) if you have set up a flat file cross-reference to these tables.

Note. The system provides transaction type 861 for receiving advice documents.

You run the Receiving Advice Edit/Create program (R47071) to copy the information from these EDI tables to the Procurement application tables.

See Understanding Inbound Advices into Purchasing (861/RECADV).

Receipt Routing Inbound Processor

The Inbound Flat File Conversion program (R47002C) copies data from a flat file to the Receipt Routing Unedited Transaction Table (F43092Z1) if you have set up a flat file cross-reference to this table.

Note. The system provides transaction type JDERR for receipt routing information.

You run the Receipt Routing Unedited Transactions Inbound Processor batch program (R43092Z1I) to copy information from the unedited transaction table to the Purchase Order Receipt Routing table (F43092).

#### Prerequisites

Before you complete the tasks in this section:

- Set up flat file cross-references.

  See Setting Up the Flat File Cross-Reference.

- Run the Inbound Flat File Conversion program (R47002C).

  See Running the Inbound Flat File Conversion Program (R47002C).

#### Setting Processing Options for Inbound Purchase Order (R4311Z1I)

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

Version

This processing option enables you to specify a version of a program that is called by the Inbound Purchase Order program (R4311Z1I).

1. P.O. Entry (P4310) | Specify the version of the P.O. Entry program (P4310) that you want to use to create purchase order information in the F4301 and F4311 tables.

#### Setting Processing Options for Receiving Advice Edit/Create (R47071)

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

Updates

These processing options specify default information that is used by the program.

1. Enter '1' to run this program in final mode. | Enter a code to specify whether the system runs this program in proof or final mode. When the system runs this program in proof mode, the system does not update any tables. When the system runs this program in final mode, the system updates the records that are being processed. Values are: Blank: Proof mode. 1: Final mode.
2. Enter the G/L Date to be used, if left blank the system date will be used. | Specify the general ledger date that the system uses. If you leave this processing option blank, the system uses the system date as the general ledger date.
3. Enter the default route type to be used to search for a receipt route. | Enter a code that qualifies the routing for an Item/Supplier combination. Examples include specific routing types for ASNs (EDI 856 Ship Notice/Manifest transactions) and for transfers.

Version

These processing options enable you to specify versions of programs that are called by the Receiving Advice Edit/Create program (R47071).

1. Receipts By PO (P4312) | Specify which version of the PO Receipts program (P4312) the system uses. If you leave this processing option blank, the system uses version ZJDE0001.
2. Transportation Shipment Confirmation (P49645) | Specify which version of the Transportation Shipment Confirmation program (P49645) that the system uses. If you leave this processing option blank, the system uses version ZJDE0001.
3. Transportation Load Confirmation (P49640) | Specify the version of Transportation Load Confirmation program (P49640) that the system uses. If you leave this processing option blank, the system uses version ZJDE0001.

#### Setting Processing Options for Receipt Routing Inbound Processor (R43092Z1I)

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

Versions

This processing option enables you to specify a version of a program that is called by the Receipt Routing Inbound Processor program (R43092Z1I).

1. Receipts by Purchase Order (P4312) | Specify the version that the system uses when you access the Receipts by Purchase Order program. You use the Receipts by Purchase Order program when you are moving items to an operation that is set up to move quantities into inventory. Review the version's processing options to ensure that the version meets your needs.

#### Running the Inbound Purchase Order Program

Select Purchasing Interoperability (G43A313), Inbound Purchase Order.

#### Running the Receiving Advice Edit/Create Program

Select Purchasing Interoperability (G43A313), Receiving Advice Edit/Create.

#### Running the Receipt Routing Inbound Processor Program

Select Purchasing Interoperability (G43A313), Receipt Routing Inbound Processor.

### Reviewing and Revising Interoperability Transactions for Procurement

This section provides an overview of reviewing and revising interoperability transactions for Procurement and lists the forms used to review and revise inbound interoperability transactions for Procurement.

#### Understanding Reviewing and Revising Interoperability Transactions for Procurement

Running a transaction process, such as Receipt Routing Inbound Processor (R43092Z1I), often identifies one or more inbound transactions that contain invalid transactions. For example, if you are in receipt routing and you try to move inventory to a step that was not defined in the receipt route, the Receipt Routing Inbound Processor program identifies the invalid transaction and sends an error message to the Work Center (P012501). The error message indicates the transaction number for the transaction in error.

You can use on these programs to review and revise inbound transactions:

- Inbound Purchase Order Inquiry (P4311Z1)

- Inbound Receiving Advice Inquiry (P47070)

- Inbound Receipt Routing Inquiry (P43092Z1)

Use the inquiry menu selections to add, change, or delete transactions containing errors. Then run the appropriate 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.

You can review and revise receiving advice transactions, receipt routing transactions, or purchase order transactions.

#### Forms Used to Review and Revise Inbound Interoperability Transactions for Procurement

Form Name | FormID | Navigation | Usage
Inbound EDI Receiving Advice Revisions | W47070B | Purchasing Interoperability (G43A313), Inbound Receiving Advice Inquiry Locate a transaction and click Select on Work with Inbound EDI Receiving Advice. | Locate and revise receiving advice transactions. If applicable, select Detail Revisions from the Row menu to review or change additional detail information. After you correct the errors identified by the Inbound Receiving Advice Inquiry process, run the transaction process again.
Unedited Transaction Revisions | W43092Z1B | Purchasing Interoperability (G43A313), Inbound Receipt Routing Inquiry Locate a transaction and click Select on Work With Unedited Transactions. | Locate and revise receipt routing transactions. If applicable, select Revisions from the Row menu to review or change additional detail information. After you correct the errors identified by the Inbound Receipt Routing Inquiry process, run the transaction process again.
Unedited Transaction Header Revision | W4311Z1C | Purchasing Interoperability (G43A313), Inbound Purchase Order Inquiry Locate a transaction and click Select on Work With PO Unedited Transactions. | Locate and revise purchase order transactions. If applicable, select Detail Revisions from the Row menu to review or change additional detail information. After you correct the errors identified by the Inbound Purchase Order Inquiry process, run the transaction process again.

### Purging Interoperability Transactions for Procurement

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

#### Understanding Purging 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.

Procurement contains a purge option for both inbound and outbound transactions. Use these purges to remove data from the corresponding interoperability tables:

- EDI Purchase Order Inbound Purge (R47018)

- EDI Receiving Advice Inbound Purge (R47078)

- Purge Receipt Routing Records (R43092Z1P)

- EDI Purchase Order Outbound Purge (R47019)

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.

See JD Edwards EnterpriseOne Tools 8.98 Interoperability Guide.

#### Purging Interoperability Transactions

To purge inbound interoperability transactions for purchase orders, select Custom Order (G47212), Purge/Archive. Select the first instance of Purge/Archive on this menu.

To purge inbound interoperability transactions for receipts, select Purchasing Interoperability (G43A313), Receiving Advice Inbound Purge.

To purge receipt routing records, select Distribution Purges (G00234), Purge Receipt Routing Records.

To purge outbound interoperability transactions for purchase orders, select Purchasing Interoperability (G43A313), Order Outbound Purge.