Mapping Requirements for Processing Inbound EDI Transmissions
These tables are used to receive EDI transmissions:
EDI Product Activity Data Header - Inbound (F47121)
EDI Product Activity Data Detail - Inbound(F47122)
EDI Product Activity Data (SDQ) - Inbound(F47123)
You can receive multiple transactions in a single EDI transmission. The system uses key fields in EDI tables F47121, F47122, and F47123 to differentiate transactions and their related components. You should assign the same value to the key fields in all of the EDI tables.
To successfully process EDI transactions, complete the required fields in the EDI Product Activity Data Header - Inbound (F47121) table:
Field Name |
Alias |
Type |
Length |
Definition |
---|---|---|---|---|
EDI - Document Number |
EDOC |
Numeric |
9 |
The document number that is assigned by the transmitter in an EDI transaction. |
EDI - Document Type |
EDCT |
String |
2 |
The document type that is assigned by the transmitter in an EDI transaction. |
Company - Key (EDI - Document Key Co) |
EKCO |
String |
5 |
The company that is assigned by the transmitter in an EDI transaction. |
EDI - Transaction Set Number |
EDST |
String |
6 |
A code used to identify a specific type of EDI transaction. |
EDI - Send/Receive Indicator |
EDER |
Character |
1 |
Indicator used to identify if a specific transaction set can be sent, received or both. Valid values are: S Send R Receive B Both |
Transaction Handling Code |
THCD |
Character |
1 |
EDI Code designating the action to be taken by all parties. See User Defined Code Table 47/TH for valid codes. Refer to ANSI X.12 Data Item 305. |
Address Number |
AN8 |
Numeric |
8 |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location. For Outbound Inventory transactions, this field represents the Sold To value. |
To successfully process EDI transactions, complete the required fields in the EDI Product Activity Data Detail - Inbound (F47122) table:
Field Name |
Alias |
Type |
Length |
Definition |
---|---|---|---|---|
EDI - Document Number |
EDOC |
Numeric |
9 |
The document number that is assigned by the transmitter in an EDI transaction. |
EDI - Document Type |
EDCT |
String |
2 |
The document type that is assigned by the transmitter in an EDI transaction. |
Company - Key (EDI - Document Key Co) |
EKCO |
String |
5 |
The company that is assigned by the transmitter in an EDI transaction. |
EDI - Transaction Set Number |
EDST |
String |
6 |
A code used to identify a specific type of EDI transaction. |
EDI - Send/Receive Indicator |
EDER |
Character |
1 |
Indicator used to identify if a specific transaction set can be sent, received or both. Valid values are: S Send R Receive B Both |
Address Number |
AN8 |
Numeric |
8 |
A number that identifies an entry in the Address Book system, such as employee, applicant, participant, customer, supplier, tenant, or location. For Outbound Inventory transactions, this value represents the Ship To value. |
EDI - Line Number |
EDLN |
Numeric |
7 |
This is the line number you assign when originating an EDI transaction. This number can represent an order line number (applicable for any order type), an invoice pay item, a journal entry line number, and so on. |
Product Activity Code |
PACD |
String |
2 |
A code identifying activity details for the product being reported on an EDI Product Activity Data transaction. See User Define Code 47/PA. Refer to ANSI X.12 Data Item 859. For receiving Outbound Inventory consumption data, you must specify a product activity code of type C from UDC 47/PA. |
Sort Selection Sequence |
KSEQ |
Numeric |
3 |
The sort sequence allows you to specify whether data is to be included in the sequence. For example, you could sequence a version of the report by Alpha Name, Reporting Code 1 and Address Number and a second version of the report by State, Alpha Name and Postal Code. |
Supplier Name |
VR01 |
String |
25 |
An alphanumeric value used as a cross-reference or secondary reference number. Typically, this is the customer number, supplier number, or job number. For Outbound Inventory transactions, this field represents the Customer Purchase Order number. |
Item Number - Short |
ITM |
Numeric |
8 |
An eight-digit, computer-assigned item number |
2nd Item Number |
LITM |
String |
25 |
A 25-digit, user defined, alphanumeric item number. |
3rd Item Number |
AITM |
String |
25 |
A 25-digit, free-form, user defined alphanumeric item number. |
Item Number - Customer/Supplier |
CITM |
String |
25 |
The cross-reference item number that the system assigns to an item number. A cross-reference number allows you to use a supplier's item number if it is different from your own item number when you are processing an order or printing. |
Transaction Quantity |
TRQT |
Numeric |
15 |
A value that represents the available quantity, which might consist of the on-hand balance minus commitments, reservations, and backorders. You enter this value in the Branch/Plant Constants program (P41001). For Outbound Inventory transactions, the quantity in this field represents the consumed quantity or the remaining quantity at customer's location. The value in the FT (FROTO) field identifies the value in the Transaction Quantity field. FT field can contain values:
|
Unit of Measure - Transaction |
TRUM |
String |
2 |
The unit of measure you used when you entered this transaction into the system. |
Units - Secondary Quantity Ordered |
SQOR |
Numeric |
15 |
If the secondary unit of measure option in Inventory Constants is selected, this field will display on data entry screens. For dual pick items, you must update the secondary quantity. If you do not specify the secondary quantity, the system considers the secondary quantity as zero. |
Unit of Measure - Secondary |
UOM2 |
String |
2 |
A user defined code (00/UM) that indicates an alternate unit of measure for the item. |
Agreement Number |
DMCT |
String |
12 |
This field represents the Outbound Inventory agreement number. You can leave this field blank. If you leave this field blank, the system automatically identifies the agreement based on Sold To, Ship To, Item Number and Location values and consumes quantity from the agreement. If the system finds more than one agreement for the entered agreement search criteria, it consumes inventory from the first agreement. |
Supplement Number |
DMCS |
Numeric |
3 |
The supplement number records any changes or addendum to outbound inventory agreements that occur over time or by item |
EDI - Transmission Date |
EDDT |
Date |
6 |
The specific date that an EDI transaction was either transmitted or received. For Outbound Inventory transactions, this field represents the consumption date. |
Explanation - Transaction |
TREX |
String |
30 |
Text that identifies the reason that a transaction occurred. |
Business Unit |
MCU |
String |
12 |
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority. For Outbound Inventory transactions, this field represents the Outbound Branch/Plant. |
Location |
LOCN |
String |
20 |
The storage location from which goods will be moved. For Outbound Inventory transactions, this field represents Outbound Location. You can map customer's location to a location in the JD Edwards system, using the Location Cross Reference application (P4109). |