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 current 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.

Take this into account:

1. When is my business object complete?

   In case of order entry, when the order header is saved but the lines are not added yet. It is not useful to publish a sync BOD for the order document. On the other hand, don’t be too late. For example, you can say “I will not publish this document until it has status ‘Approved’, because it is still being updated”. But this means that an event monitor cannot generate an alert until the document is Approved, which can be too late for corrective action.

2. Which status changes are relevant?

   It is hard to give general guidelines. What is important for one business document may not be important for another document. Changing a description or adding a note may not be relevant outside the context of your application. Changing the status or changing important data such as amounts or dates will usually be relevant.

3. When is my business object at the end of its lifecycle?

   Usually data is not deleted but archived when a business object is no longer current. This is important to sync out. It will inform other applications to not use the business object anymore.