Infor ION - Sample BOD XMLs for Sync message
Summary
Infor ION - Sample BOD XMLs for Sync message
A collection of XML files that provide a sample of BOD content for testing and learning.
Features
Standard XML BOD Representation
Naming convention of a standard BOD is VERB+NOUN
Verb communication the event of “Action” eg. SYNC, PROCESS, GET, ACKNOWLEDGE, SHOW, CONFIRM etc. whereas a noun defines the name of document.
Sample BOD names: SyncAccountingChart.xml, SyncAssetMaster.xml, SyncBillOfMaterials.xml, etc.
A standard BOD contains an Application Area and a Data Area.
- Application Area contains the sender details and BOD creation details whereas - Data Area contains the VERB and other relevant details.
Verb communication the event of “Action” eg. SYNC, PROCESS, GET, ACKNOWLEDGE, SHOW, CONFIRM etc. whereas a noun defines the name of document.
Sample BOD names: SyncAccountingChart.xml, SyncAssetMaster.xml, SyncBillOfMaterials.xml, etc.
A standard BOD contains an Application Area and a Data Area.
- Application Area contains the sender details and BOD creation details whereas - Data Area contains the VERB and other relevant details.
System of record
An important concept related to the BODs is the system of record. This is the application instance that owns a business object. A system of record can own all instances of a noun or it can own part of the instances. Being a system of record or not determines the verb to be used.
Publishing a Sync BOD
If you are the owner of a piece of business object data that can be represented in a BOD document. You can send Sync BODs to inform other parties about the status. It is important to find the right balance when publishing Sync BODs. You do not want to publish too many BODs and not all changes to a document are relevant for the outside world. However, publishing less BODs can limit a customer when creating an integration or when using event management or workflow.
