Common
This section explains the common aspects of the messages edinn sends to the systems with which it is integrated. To receive these messages proceed with the appropriate configuration in the interface tab of the server console.
Common aspects about ISA-95 compliant messages (for more information please read the B2MML document).
Attending to the ISA-95 classification, edinn has four types of messages (SyncProductionSchedule, SyncProductionPerformance, CancelProductionPerformance and GetMaterialInformation) and expects two types of responses (ConfirmBOD and ShowMaterialInformation).
Production Schedule Synchronizationa and Production Performance Synchronization are Synchronization messages.
Each message has two sections:
- ApplicationArea: contains the metadata.
- Sender: identifies the message sender.
- LogicalID: unique identifier of the message that is usefull to prevent to duplicate information.
- ComponentID: identifier of the sender, usually the software that generates the message.
- ConfitmationCode: indicates when the sender expects a response. The possible values are: Always, OnError and Never.
- CreationDateTime: date and time when the message was created.
- DataArea: contains the action to perform ans the data itself.
- Sync/ActionCriteria/ActionsExpression: action to perform. The possible values are: Add, Change and Delete.
- ProductionSchedule or ProductionPerformance: Contains the data to be porocessed. Detailed information in the corresponding section of help document.
{ "SyncProductionSchedule": { "ApplicationArea": { "Sender": { "LogicalID": "20200526172352AABCENTRAL", "ComponentID": "EDINNM2", "ConfirmationCode": "Always" }, "CreationDateTime": "2020-05-22T12:15:45" }, "DataArea": { "Sync": { "ActionCriteria": { "ActionExpression": { "@actionCode": "Change" } } }, "ProductionSchedule": { ... } OR "ProductionPerformance": { ... } } } } |
Production Schedule Synchronization messages:
- ID: Identifies the group of orders.
- ProdutionSchedule: Contains the information about each order.
- ID: Identifies the order.
- SegmentRequirement: Contains the information about each operation.
- ID: Identifies the operation.
... "ProductionSchedule": { "ID": "20200401", "ProductionRequest": { "ID": "2020040128-10", ... "SegmentRequirement": { "ID": "10", ... } } } ... |
Production Performance Synchronization messages:
- ProdutionResponse: Contains the information about each order.
- ProductionRequestID: Identifies the order.
- SegmentResponse: Contains the information about each operation.
- ID: Identifies the operation.
... "ProductionPerformance": { "ProductionResponse": { "ProductionRequestID": "20200202", "SegmentResponse": { "ID": "10", ... |
Production Performance Cancellation messages begin with the key CancelProductionPerformance and the structure is similar to the synchronization messages.
BOD Confirmation is the expected response to Synchronization and Cancelation messages.
Each message has two sections: ApplicationArea and DataArea. DataArea contains the response itself.
- Confirm: Contains the key value in ResponseCriteria/ResponseExpression/actionCode. The possible values are: Accpeted or Rejected.
- BOD: Contains detailed information about the response.
- Description: A descriptive message about the cause of the error (in case of rejected message).
- Note: A code to identify the notification in the subscriber, needed for audit purposes.
Expected response for accepted messages.
{ "ConfirmBOD": { "ApplicationArea": { "Sender": { "LogicalID": "20200526172352AABCENTRAL", "ComponentID": "ERP", "ConfirmationCode": "Always" }, "CreationDateTime": "2020-05-26T13:25:23" }, "DataArea": { "Confirm": { "ResponseCriteria": { "ResponseExpression": { "@actionCode": "Accepted" } } }, "BOD": { "Description": "Accepted", "Note": "1590492323.1673" } } } } |
Expected response for rejected messages.
{ "ConfirmBOD": { "ApplicationArea": { "Sender": { "LogicalID": "20200526172352AABCENTRAL", "ComponentID": "ERP", "ConfirmationCode": "Always" }, "CreationDateTime": "2020-05-14T15:56:15" }, "DataArea": { "Confirm": { "ResponseCriteria": { "ResponseExpression": { "@actionCode": "Rejected" } } }, "BOD": { "Description": "Error descripion", "Note": "Error aditional information" } } } } |