Processing EDI Inventory Documents

This chapter includes an overview of EDI inventory document processing and discusses how to:

Receive product activity data.
Send product activity data.

Understanding EDI Inventory Document Processing

When setting up and using the Data Interface for Electronic Data Interchange (EDI) system, you need to specify how the system will process inventory documents.

Receiving Product Activity Data

This section provides an overview of inbound product activity data transactions and discusses how to receive product activity data.

Understanding Inbound Product Activity Data Transactions

Run the EDI Product Activity Data Edit/Create program (R47121) from the Product Activity Data menu to report inventory activity and to generate replacement orders for distribution centers, warehouses, or retail outlets.

Note. You must have the JD Edwards EnterpriseOne Inventory Management, Sales Order Management, and Procurement systems to receive product activity data.

The receiver of the transaction typically maintains inventory levels on their computer for the sender of the transaction and plans when orders should be issued to replenish the sender's stock.

You can set up versions to run the EDI Product Activity Data Edit/Create program in either proof or final mode. In proof mode, the program edits and prints the transaction. In final mode, the program edits and prints the transaction, and then updates the JD Edwards EnterpriseOne system tables. It also marks the EDI transaction as processed if no errors are detected. You should always run the program in proof mode first and then make corrections using the Revisions form. The program bypasses any records with errors, which eliminate the records from the netting process and reorder point check on the last record. Once you are satisfied with the results from the proof version, you can run the final version.

When you run EDI Product Activity Data Edit/Create for product activity data, the program can create:

Audit reports

List all the transactions that this program has processed, including inquiry type product activity data transactions.
Error messages

Sends a message to the employee message center if errors occur while running the EDI Product Activity Data Edit/Create program.

Working With the Product Activity Code

Use the product activity code from user-defined code (UDC) table 47/PA in each detail record to specify the type of transaction and how it affects inventory.

This table describes the defined action for each product activity code:

Code	Action
− (Decrease inventory)	If the product activity code description is −, the transaction functions similarly to the Inventory Issues program (P4112). The quantity of the transaction decreases the quantity on hand for records in the F41021 table and updates the F4115 table if the processing options are set accordingly. The transaction also generates the necessary general ledger transactions to account for the decrease if the item's general ledger code and the document type interface with inventory.
+ (Increase inventory)	If the product activity code description is +, the transaction functions similarly to the Inventory Adjustments program (P4114). The quantity of the transaction increases in the Item Location record's quantity on hand. The system writes the new quantity on hand to the F4111 table and generates the necessary general ledger transaction to account for the receipt of the inventory.
I (Information only)	If the product activity code description is I, the transactions are informational only and do not update any JD Edwards EnterpriseOne tables. The transaction is edited for validity and prints on the Product Activity Audit Report.
R (Replace inventory on-hand balance)	If the product activity code description is R, the transaction functions similarly to the Cycle Count Update program (R41413). The quantity of the transaction replaces the quantity on hand for the records in the F41021 table. The system writes the new quantity on hand to the F4111 table, updates the F4115 table, and generates the necessary general ledger transactions to account for the adjustment to the inventory.
T (Transfer inventory from one location to another)	If the product activity code description is T, the transaction functions similarly to the Inventory Transfers program (P4113). The quantity of the first transfer transaction (the From side) decreases the quantity on hand for the Item Location record. The second transfer transaction (the To side) increases the quantity on hand for the record in the F41021 table (requires two records to be sent in). The transactions also generate the necessary general ledger transactions to account for the changes to the inventory if the item's general ledger code and the document type affect inventory.

The Sort Selection Sequence field in the inbound detail record controls the order in which transactions are processed. For example, process the beginning balances first, then plus (+) transactions, then minus (−) transactions, and ending balances.

Using the EDI Inbound Interface Tables

When you run EDI Product Activity Data Edit/Create (R47121) for product activity data, the program uses these EDI inbound interface tables:

F47121
F47122

Using Mapping Guidelines

Mapping is the process of converting information from one table structure to another.

In the F47121 table, the following fields must contain data before you can effectively use the EDI Product Activity Data Edit/Create (R47121) program for product activity data:

EDI Document Number (EDOC).
EDI Document Type (EDCT).
EDI Document Key Company (EKCO).
EDI Transaction Set (EDST).
Send/Receive Flag = R (EDER).
Transaction Handling Code (THCD).
Address Number (AN8).

In the F47122 table, the following fields must contain data before you can effectively use the EDI Product Activity Data Edit/Create (R47122) program for product activity data:

EDI Document Number (EDOC).
EDI Document Type (EDCT).
EDI Document Key Company (EKCO).
EDI Transaction Set (EDST).
EDI Line Number (EDLN).
Send/Receive Flag = R (EDER).
Product Activity Code (PACD).
Sort Selection Sequence (KSEQ).
Short Item Number (ITM), Second Item Number (LITM), Third Item Number (AITM), or Customer Item Number (CITM).
Transaction Quantity (TRQT).
Transaction Date (EDDT).
Transaction Explanation (TREX).
Business Unit (MCU).

Updating Application Tables

When you run EDI Product Activity Data Edit/Create (R47121) for product activity data, the program copies the data from the EDI interface tables and updates these application tables:

F41021
F4115
F4111
F0911

Receiving Product Activity Data

Select Product Activity Data (G47241), Inbound Edit/Update.

To prevent duplicates, the EDI Product Activity Data Edit/Create program (R47121) updates EDI documents that are successfully processed in the EDI inbound interface tables. The program updates EDI documents by entering Y in the Processed column (EDSP) in all of the EDI inbound interface tables.

After you run EDI Product Activity Data Edit/Create for product activity data, review and post the general ledger transactions that the system created.

Sending Product Activity Data

This section provides an overview of outbound product activity data transactions and discusses how to send product activity data.

Understanding Outbound Product Activity Data Transactions

Run the EDI Product Activity Data Extraction program (R47122) from the Product Activity Data menu to generate product activity data transactions (852/INVRPT) to send to a central distribution center, warehouse, or the parent company.

The receiver of the transaction typically maintains inventory levels for the sender of the transaction and plans when orders should be issued to replenish the sender's stock.

You can run the EDI Product Activity Data Extraction program in either proof or final mode. In proof mode, the program edits and prints the transaction. In final mode, the program edits and prints the transaction and also updates the JD Edwards EnterpriseOne system tables.

You specify which transactions to extract using the processing options for EDI Product Activity Data Extraction. Valid codes are found in UDC table 47/PA. You can generate these transactions:

QS: Quantity sold
QR: Quantity received
QO: Quantity out of stock
QT: Adjustments to inventory
QW: Quantity withdrawn from warehouse
QC: Quantity committed
QD: Additional demand quantity
QH: Quantity damaged or on hold
QI: Quantity in transit (receipt routing bucket 1)
QP: Quantity on order, not received
QA: Current quantity available to ship
QE: Current quantity on hand
QL: Minimum reorder quantity
QM: Maximum reorder quantity
QN: Planned reorder quantity
QX: Quantity requested

Using Processing Guidelines

Be aware of these processing guidelines before you run the EDI Product Activity Data Extraction program (R47122):

Specify the item ledger document types that represent item ledger transactions.

You can specify up to 10 document types per line. Enter the document type codes consecutively with no intervening spaces (for example, SOSTSESZ).
Do not specify a document type more than once.
The Sort Sequence code computes automatically for outbound transactions.

If the first character in the second description field for 47/PA is R, then the sequence = 90. Otherwise, the sequence = 100.
The JD Edwards EnterpriseOne system provides four versions to control how item ledger records are summarized to create the outbound product activity data. These versions are:
Date within location within item.
Date within item.
Location within item.
By item.

Use one of these versions. Do not change the sort sequence or control breaks.

Data selection is based upon selection of any field in the F4111 table.

Note. To receive the transaction, you must have the JD Edwards EnterpriseOne Inventory Management, Sales Order Management, and Procurement systems. To send the transaction, you only need the JD Edwards EnterpriseOne Inventory Management system.

Updating Application Tables

When you run EDI Product Activity Data Extraction (R47122) for product activity data, the program extracts the data from these application tables:

F4104
F41021
F4108
F0911
F4111
F4101
F4102
F4105

Using the EDI Outbound Interface Tables

When you run EDI Product Activity Data Extraction (R47122) for product activity data, the program creates records in these EDI outbound interface tables:

F47126
F47127

After these records are created, you need to perform the flat file conversion process.

Sending Product Activity Data

Select Product Activity Data (G47241), Outbound Extraction.

The EDI Product Activity Data Extraction program (R47122) extracts records from the Inventory application tables and creates product activity data documents within the EDI outbound interface tables so they can be sent to the trading partner.