Best Practice for Transaction turn-around data using F55 series tables: For inbound and outbound EDI, JDE might not have a field we need for our business requirements. A JDE best practice to meet business partner requirements would be to utilize the F55-F59 series tables to turn around data for EDI and non-EDI transactions. These tables are custom tables designed using the JD Edwards Table Design Aid. Once created these custom tables can be viewed via JDE’s Data Browser Web Client.
Examples of Transaction turn-around using F55 tables: An example of where data would need to be turned around is an inbound purchase order where we need to capture the customer item number.
As of today the sales order detail file, F4211, does not have a customer item number field. Meaning when we translate data into F47012 and we populate the SZCITM, this value is not transposed into F4211 when an edit/update is performed. This can be an issue if we do not store the customer item number in F4104.
Take Home Depot.com for example, many of their items have the same customer item number. If we do not store the value in F4104 we will not be able to return the same value in the outbound 810, outbound 856. In this scenario, capturing the customer item number is essential to having the invoice paid.
Why the best practice for transaction turn-around with the F55 series tables: By utilizing a JDE Best Practices for the item cross reference, JDE users can execute a policy of where logic and transformation is kept separate from the data warehousing.
Reason 1: By not using this best practice, JDE users will find themselves unable to meet internal business requirements and possibly trading partner requirements.
Using our best practice of implementing a custom F55-F59 series table, we would be able to meet the trading partner requirements with minimal effort.
How we use Transaction turn-around data using F55 series tables: The JDE best practice to transaction turn around in F55 tables is to use JDE’s Table Design Aid to design a generic header file and detail file, at minimum. These two files would be ‘children’ of common F47 tables such as the Purchase Order Header and Detail tables - F47011 and F47012.
We can incorporate these two tables as part of the overall inbound transformation schema so the key fields are shared among the other F47 tables. Keys such as company number (EKCO), EDOC, Document Type (EDCT).
Since these tables are designed internally to JDE, the F55 tables are updated just as the F47 tables are update during the edit update process. Meaning an order number will be assigned to each respective record and the DOCO field will be updated. With this information, a B2B solution can look at these files on the turnaround process to retrieve the data JDE was unable to store for us.
By: Sean Hoppe on