Database considerations
These are some important parts of the BOD to consider upon publishing for it to populate to LSP databases.
VariationIDs
The sequence of BODs published from your ERP is not necessarily the same sequence that is processed in LSP because ION does not operate on a first-in, first-out basis. In order to manage this better, variation IDs are used to determine if BODs are being processed out of sequence.
For Sync BODs, its value should always be higher than its previous record based on the way it was processed in LSP database.
This table shows these variationIDs:
| BOD | First content | Second content | Status |
|---|---|---|---|
| Invoice | ID: 123 variationID: 5 |
ID: 123 variationID: 6 |
Successful |
| Invoice | ID: 123 variationID: 6 |
ID: 123 variationID: 5 |
Outdated |
LSP only consumes transactional BODs with an active service. All master data BODs are consumed regardless of the status of the service.
This table shows these accountingEntity values:
| BOD | Accounting entity is active | Accounting entity is inactive |
|---|---|---|
| CustomerPartyMaster | Success | Success |
| Invoice | Success | Failed |