Understanding EDI Cross References
When EDI data enters the system, the system uses the codes to identify the type and the frequency of the requirement. Requirement codes are standard within the EDI system, but their uses can vary, depending on each customer's business practices, as described in the table:
Customer |
EDI |
Requirement Type |
Requirement Frequency |
Actual Use |
---|---|---|---|---|
Customer 1 |
X.12 |
C |
D |
Firm Daily |
Customer 1 |
X.12 |
D |
D |
Plan Daily |
Customer 1 |
X.12 |
D |
W |
Plan Weekly |
Customer 2 |
X.12 |
C |
C |
Firm Daily |
Customer 2 |
X.12 |
D |
C |
Plan Daily |
Customer 2 |
X.12 |
D |
W |
Plan Weekly |
Customer 3 |
EDIFACT |
1 |
D |
Firm Daily |
Customer 3 |
EDIFACT |
4 |
D |
Plan Daily |
Customer 3 |
EDIFACT |
4 |
W |
Plan Weekly |
To handle these differences, you must set up a cross-reference record for each requirement type and requirement frequency combination. This record specifies the demand type (firm or plan) and the frequency of demand (such as daily). The system processes the Demand Type and the Demand Period fields to determine the requirement.
You can set up cross references for all Branch/Plant and Sold To records, all Sold To records for a Branch/Plant, or for a specific Sold To record.