| |
|
|
|
|
| |
The code identifying the reason for the order response rejection or modification |
|
|
|
|
| |
The Code is used by the Responder to indicate the Error Code of the error or warning being communicated. The Initiator may use the Code field to enable automated machine processing of errors. |
|
|
| |
|
|
|
|
| |
APPLICATION_ROUTING_ERROR |
|
|
| |
|
|
| |
| |
APPLICATION_ROUTING_ERROR |
|
|
| |
Application Routing Error |
|
|
|
| |
Indicates the type of scope, the identifiers for the scope, other supporting information and the scope content itself |
|
| |
CODE_NOT_MAPPED_TO_APPLICATION |
|
|
| |
Code Not Mapped to Application |
|
| |
CUSTOMER_IDENTIFICATION_NUMBER_AND_ENTITY_NAME_DO_NOT_MATCH |
|
|
| |
Customer Identification Number and Entity Name Do not match |
|
| |
CUSTOMER_IDENTIFICATION_NUMBER_DOES_NOT_EXIST |
|
|
| |
Customer Identification Number Does not Exist |
|
| |
CUSTOMER_IDENTIFICATION_NUMBER_IS_INVALID |
|
|
| |
Customer Identification Number is Invalid |
|
| |
CUSTOMER_IDENTIFICATION_NUMBER_IS_MISSING |
|
|
| |
Customer Identification Number Is Missing |
|
|
|
| |
Latest time to place order exceeded therefore slot not available |
|
| |
DELIVERY_SLOT_NOT_VALID_FOR_LOCATION |
|
|
| |
Requested delivery time slot not valid for that ship to location |
|
|
|
| |
To cease making or manufacturing |
|
| |
DOCUMENT_ENCLOSED_IN_THE_FIRST_TRANSMISSION |
|
|
| |
Documents enclosed in the first transmission |
|
| |
DOCUMENT_ENCLOSED_IN_THE_SECOND_TRANSMISSION |
|
|
| |
Documents enclosed in the second transmission |
|
|
|
|
|
|
|
| |
DOCUMENT_NOT_REQUIRED_WAIVER_ISSUED |
|
|
| |
Document not required, waiver issued |
|
|
|
|
|
|
| |
Expected adjacent, non-overlapping weekly samples but got non-adjacent weekly samples |
|
|
|
|
|
|
|
|
|
| |
Descriptor which contains reference information which uniquely identifies this instance of the SBD between the sender and the receiver |
|
| |
INVALID_BUSINESS_PROCESS_CURRENT_STATUS_CODE |
|
|
| |
Invalid Business Process Current Status Code |
|
| |
INVALID_BUYER_EVENT_IDENTIFICATION |
|
|
| |
As a result of an acknowledgement, change, or change in status; the ‘buyer’ Event ID does not exist |
|
| |
INVALID_BUYER_IDENTIFICATION |
|
|
| |
Buyer (Trading Partner Identification) is invalid |
|
| |
INVALID_BUYER_LOCATION_GROUP_IDENTIFICATION |
|
|
| |
Invalid buyer group location Identification |
|
| |
INVALID_BUYER_LOCATION_IDENTIFICATION |
|
|
| |
Invalid buyer location identification number |
|
|
|
|
| |
INVALID_PRODUCT_BUYER_GROUP_IDENTIFICATION |
|
|
| |
Product / Item Buyer Group Identification Number does not exist |
|
| |
INVALID_PRODUCT_OR_ITEM_IDENTIFICATION |
|
|
| |
Product / Item Number does not exist |
|
| |
INVALID_PRODUCT_SELLER_GROUP_IDENTIFICATION |
|
|
| |
Product / Item Seller Group Identification Number does not exist |
|
| |
INVALID_SELLER_EVENT_IDENTIFICATION |
|
|
| |
As a result of an acknowledgement, change, or change in status; the ‘seller’ Event ID does not exist |
|
| |
INVALID_SELLER_IDENTIFICATION |
|
|
| |
Seller (Trading Partner Identification) is invalid |
|
| |
INVALID_SELLER_LOCATION_GROUP_IDENTIFICATION |
|
|
| |
Invalid seller group location Identification |
|
| |
INVALID_SELLER_LOCATION_IDENTIFICATION |
|
|
| |
Invalid seller location identification number |
|
| |
INVALID_STATUS_TRANSITION |
|
|
| |
The Status of this Event has changed and does not follow the acceptable status change life cycle |
|
|
|
| |
Example: Expected weekly forecast and received monthly |
|
|
|
|
|
|
|
| |
ITEM_TEMPORARILY_NOT_AVAILABLE |
|
|
| |
Item temporarily not available |
|
|
|
| |
A flag to indicate that there is more than one type of Document in the instance |
|
| |
MESSAGE_UNDER_DEVELOPMENT |
|
|
| |
Message under development |
|
| |
MISSING_CODE_FOR_APPLICATION |
|
|
| |
Missing Code for Application |
|
|
|
|
| |
MISSING_EFFECTIVE_MESSAGE_DATE |
|
|
| |
Missing Effective Message Date |
|
| |
MISSING_IDENTIFICATION_CODE |
|
|
| |
Missing Identification Code |
|
| |
MISSING_MESSAGE_REFERENCE_NUMBER |
|
|
| |
Missing Message Reference Number |
|
| |
MISSING_OR_INVALID_DUNS_NUMBER |
|
|
| |
Missing or Invalid DUNS Number |
|
| |
MISSING_OR_INVALID_LOCATION |
|
|
| |
Missing or Invalid Location |
|
| |
MISSING_OR_INVALID_MESSAGE_CODE |
|
|
| |
Missing or Invalid Message Code |
|
|
|
|
| |
MISSING_OR_INVALID_UPC_CODE |
|
|
| |
Missing or Invalid U.P.C. Code |
|
|
|
|
|
|
| |
Expected adjacent, non-overlapping weekly samples, but got overlapping weekly samples |
|
|
|
| |
Number of Participating Locations does not equal the number of Locations communicated in the detail |
|
|
|
| |
Percent of all participating locations |
|
| |
PRODUCT_NOT_VALID_FOR_LOCATION |
|
|
| |
Requested product not valid for that ship to location |
|
|
|
|
| |
RECEIVED_AFTER_CUTOFF_DATE_OR_TIME |
|
|
| |
Received After Cutoff Date or Time |
|
| |
SENDER_NOT_AUTHORIZED_FOR_THIS_MESSAGE |
|
|
| |
Sender Not Authorized for this message |
|
| |
STANDARD_BUSINESS_DOCUMENT_STANDARD_TYPE |
|
|
| |
Originator of the type of the Business Data standard, e.g. SWIFT, OAG, used |
|
| |
STANDARD_STANDARD_BUSINESS_DOCUMENT_STANDARD_TYPE |
|
|
| |
**DEPRECATE For MAJOR VERSION**Originator of the type of the Business Data standard, e.g. SWIFT, OAG, used |
|
| |
TO_ARRIVE_BY_SEPARATE_XML_MESSAGE |
|
|
| |
To arrive by separate XML message |
|
|
|
| |
A logical indicator representing the type of Business Data being sent or the named type of business data |
|
|
|
| |
(Standard Business Document. Standard Type Version.Identifier): Descriptor which contains versioning information or number of the standard that defines the document which is specified in the ’Type’ data element, e.g. D.96A |
|
| |
UNAUTHORIZED_BUSINESS_PROCESS_STATE |
|
|
| |
Unauthorized Business Process State code |
|
| |
UNAUTHORIZED_BUSINESS_SERVICE_ACTION_CODE |
|
|
| |
Unauthorized Business Service Action Code |
|