Correspondences
This function is used to define a match between a status code and the reason codes that are associated to it.
The detail level of the relationships between status and reason must make it possible to deal with responsabilities and if necessary to implement a commercial processing of the information.
Prerequisite
Refer to documentation Implementation
Screen management
The screen is composed of a single tab.
Entry screen
Presentation
- For each status code, association of one or several reason codes.
The match between a status code and the reason codes is defined upon interchange agreement with the carriers. - Upon integration or manual creation of an EDI message, the system checks that the message pairs (status code, reason code) is defined in Warehousing.
- The "End message" indicator is used to specify on the basis of the pairs (status code, reason code) whether the message is the last one or not to be received fot the processed entity.
- "Yes": last message to be received for the entity
- "No": the system accepts to receive other messages for the entity - The internal code is used to define the managament of a workflow and the recipients for the pairs (status code, reason code).
The workflow recipient types are defined in local menu 76.
Example:
Equivalence table parameterization so as to send a workflow to the customer, the carrier and the depositor if the goods are not delivered because of a theft.
Status Reason Internal code
56: NOT DELIVERED66: STOLEN CCD (C for Customer, C for Carrier and D for
Depositor)
Close
Fields
The following fields are present on this tab :
Block number 1
| It describes the situation of the entity (removed, delivery under progress, etc.) Statuses are defined for all the carriers and their codification is defined upon each interchange agreement with the carrier. |
Grid Correspondences
| The reason code provides a justification or an explanation for a status (eg. missing, damaged, etc.) It is defined upon interchange agreement with the carrier. |
| Used to specify whether or not the EDI message is the last one to be received from the pairs (status code, reason code) for the processed entity. The possible values are: Yes: last message to be received for the entity No: the system accepts to receive other message for the entity |
| The internal code is used to define the managament of a workflow and the recipients for the pairs (status code, reason code). The workflow recipient types are defined in local menu 76. For instance: Setup designed to send a workflow to the customer, the carrier and the depositor. = > internal code = CCD (C for Customer, C for Carrier and D for Depositor) |
Close
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
"Status code" field error, Mandatory field
Upon creating a new equivalence, the entered status code must not be blank.
"Status code" field error, Record does not exist.
The entered status code does not exist in the status code table for the current site.
"Reason code" field error, mandatory field
The entered reason code must not be blank.
"Reason code" field error, Record does not exist.
The entered reason code does not exist in the reason code table for the current site.
"Reason code" field error, Code already exists in line X.
The entered reason code has already been associated with the processed status code.