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

4 Processing Interoperability for Sales Order Management

This chapter contains the following topics:

4.1 Processing Outbound Interoperability for Sales Order Management

This section provides overviews of the outbound interoperability for Sales Order Management and subsystem processing in sales order entry, lists a prerequisite, and discusses how to:

  • Set selected processing options for Sales Order Entry (P4210).

  • Set selected processing options for Sales Order Entry (P42101).

  • Set selected processing options for Shipment Confirmation (P4205).

4.1.1 Understanding Outbound Interoperability for Sales Order Management

You might send transactions you create or change in Sales Order Management to an external system. For example, if the organization sends order acknowledgements to customers, you can use Interoperability transactions to convey order and price information.

To process outbound interoperability in Sales Order Management:

  1. Specify a transaction type in the processing options of these programs:

    • Sales Order Entry (P4210)

    • Shipment Confirmation (P4205)

  2. Enter or change a sales order or shipment confirmation using the Sales Order Entry program (P42101).

    The JD Edwards EnterpriseOne Sales Order system calls a business function that writes records to the Sales Order Header Unedited Transaction File table (F4201Z1) and the Sales Order Detail Unedited Transaction File table (F4211Z1). The same business function calls a special subsystem API (application program interface) 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 F4201Z1 and F4211Z1 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 F4201Z1 and F4211Z1 tables and processes that information.

4.1.2 Understanding Subsystem Processing in Sales Order Entry

If you need a pick slip or invoice when you finish the order entry process, you can set up and activate the subsystem. You might want this instant print capability if you:

  • Operate in an environment that has a high volume of same-day-delivery orders, and you want to create the pick slip as soon as you enter the order.

  • Have many counter sales, where the customer expects to leave the premises with both the merchandise and the invoice for that merchandise.

The processing options in the Sales Order Entry program (P4210) activate subsystem processing. For example, in the version of Sales Order Entry that you use for printing pick slips immediately after order entry, you would set the value in the processing options to print pick slips and then identify the version of the Print Pick Slips program. You must set a processing option to activate the subsystem processing and then identify the corresponding subsystem version of the programs to run these programs:

  • Print Pick Slips (R42520)

  • Print Invoices (R42565)

  • Inventory Commitment (R42997)

  • Batch Edit and Creation (R4210Z)

You should create a version of Sales Order Entry (P4210) specifically for subsystem processing.

Important:

You must stop the subsystem processing before performing end-of-day processing. You can also stop one or more jobs in the subsystem at any time. You use the Subsystem Jobs program (P986113) to end subsystem processing.

See JD Edwards EnterpriseOne Tools System Administration Guide

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

4.1.4 Setting Selected Processing Options for Sales Order Entry (P4210)

This section lists only the processing options for the Sales Order Entry program (P4210) that are specific to outbound interoperability.

4.1.4.1 7-Process

This section lists only the processing options on the Process tab that relate to subsystem processing.

2. Subsystem Processing

Specify a value to activate the subsystem to print the pick slip or invoice immediately after the order entry process. Values are:

1: The system uses this version of Sales Order Entry (P4210) for subsystem processing to print pick slips and activate the subsystem processing. Identify the corresponding version of the program in the Sales Order Entry (P4210), Versions, Pick Slip Print processing options.

2: The system uses this version of Sales Order Entry (P4210) for subsystem processing to print invoices and activate the subsystem processing. Identify the corresponding version of the program in the Sales Order Entry (P4210), Versions, Invoice Print processing options.

3: The system uses this version of Sales Order Entry for subsystem commitment processing and does not commit inventory until you complete the order. After you accept the order, the system processes the order through the subsystem batch program while you enter another order.

4: The system uses this version of Sales Order Entry for online commitment processing and the system does not process order detail lines asynchronously. After you enter the order, the system processes commitments for the complete order before you can enter another order. This enables you to review commitments online as the system processes availability for each order detail line in the order.

Note:

Option 5 is no longer used because the store and forward process is no longer supported.

5: The system uses this version of Sales Order Entry for entering and processing orders in a store-and-forward mode. Identify the appropriate version of the program, Sales Order Batch Transaction Editor (R4210Z), in the Sales Order Entry (P4210), Versions tab, Sales Order Batch Transaction Editor (R4210Z) processing option.

Note:

If you specify either 3 or 4, you must specify a version of the Inventory Commitment program (R42997) on the Versions tab.

4.1.4.2 9-Versions

You use these processing options to specify versions of other programs that are called by the Sales Order Entry program (P4210).

13. Online/Subsystem Commitment (R42997)

Specify the version of the Inventory Commitment program (R42997) the system uses for either online or subsystem commitments. You must specify the Subsystem Processing option on the Process tab for either online or subsystem commitments and specify the version of the corresponding Commitments program. If you leave this processing option blank, the system uses version ZJDE0001.

4.1.4.3 18-Interop

You use these processing options to set up outbound interoperability.

1. Transaction Type

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 JDESOOUT for sales orders.
2. Before/After Image Processing

Specify whether the system creates a record of the sales order before it was changed, in addition to a record of the sales order after the change. The system creates these records in the Sales Order Header Unedited Transaction File table (F4201Z1) and the Sales Order Detail Unedited Transaction File table (F4211Z1) when outbound interoperability processing is enabled. Values are:

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

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

4.1.5 Setting Selected Processing Options for Sales Order Entry (P42101)

This section lists only the processing options for the Sales Order Entry program (P42101) that are specific to outbound interoperability.

4.1.5.1 Versions

You use these processing options to specify the version of the Sales Order Entry program (P4210) to use.

1. Sales Order Model Version

Specify a version of the Sales Order Entry program (P4210). When you process a sales order using the P42101 program, the system retrieves the processing options related to interoperability from the processing options of the version of the P4210 program that you specify.

4.1.6 Setting Selected Processing Options for Shipment Confirmation (P4205)

This section lists only the processing options for the Shipment Confirmation program (P4205) that are specific to outbound interoperability.

4.1.6.1 18-Interop

You use these processing options to set up outbound interoperability.

1. Interoperability Transaction Type

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 JDESC for shipment confirmations.
2. Run the Outbound Subsystem UBE

Indicate whether the system processes outbound interoperability transactions through the subsystem. Values are:

Blank: Bypass outbound subsystem processing.

1: Perform subsystem processing.

4.2 Reviewing and Revising Interoperability Transactions for Sales Order Management

This section provides an overview of reviewing and revising interoperability transactions for Sales Order Management and lists the form used to review and revise interoperability transactions for Sales Order Management.

4.2.1 Understanding Reviewing and Revising Interoperability Transactions for Sales Order Management

Running an inbound transaction process often identifies one or more invalid inbound transactions in the interface table. For example, an inventory item on an order might have an invalid address book number, Ship To address, or Sold To address. The program cannot add that transaction to the Sales Order Detail File table (F4211). When an error occurs, the program sends an error message to the Work Center (P012501), indicating the transaction number for the transaction in error. You can inquire on these transactions to review and revise unedited sales transactions.

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.

After you correct the errors identified by the Inbound Transaction Process, run the transaction process again. If other errors are identified, correct them and run the transaction process again.

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

See JD Edwards EnterpriseOne Tools Interoperability Guide

4.2.2 Form Used to Review and Revise Interoperability Transactions for Sales Order Management

Form Name FormID Navigation Usage
Unedited Detail Transactions Revisions W4211Z1C Sales Interoperability (G42A313), Outbound Sales Transaction Revisions

Select a transaction on the Work With Sales Orders Unedited Transactions form and click Select.

Review and revise interoperability transactions.

If applicable, select Detail Revisions from the Row menu to review or change additional detail information.


4.3 Purging Interoperability Transactions for Sales Order Management

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

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

For records in the Processing Log table (F0046) that are marked as processed, the program purges the associated transactions in the F4201Z1 interoperability table, 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 Interoperability Guide

4.3.2 Purging Interoperability Transactions

To purge inbound interoperability transactions for sales orders, select Sales Interoperability (G42A313), Purge Sales Transaction Records.