Publishing BODs

The sequence of the BODs that are published from your ERP differ across functional area but the general order is important, especially where General Ledger balances are involved.

When adding an additional function in LSP, the BODs that have already been published and operational must be accounted for when using our recommendations. In this case, only new BODs should be taken into consideration.

Note:  Ensure that you only set up BODs that your ERP supports in LSP. Setting up more than the required increases BOD traffic in your tenant, leading to a significant decrease in the performance of ION and LSP. See the ERP Integration Guide. for the supported BODs

Base data details (Financial Calendar and Accounting Chart) must be created first in Accounting Entity Maintenance.

You can then publish any other Master data if they are required for the service you are implementing. Subsequently, you should ensure that all the Master data is published in an initial data load. This can be done in any order.

If your function requires historical transactional data such as invoices, then these must be published in an initial data load also or you may encounter validation errors, which prompts you to publish them. You can also use show BODs to perform bulk updates, but these kind of documents are not considered in push reporting or automatic message generation.

After all the initial loads have been completed, then you can assign the service to the Accounting Entity and start to trigger the transactional data on an as needed basis.

Note: 
  • The initial data load may take some time, depending on data volumes
  • The Accounting Entity BOD is no longer supported in LSP and must be removed from your ION doc flow to prevent unwanted BOD traffic

See BOD usage in LSP for the consolidated BOD list.

Show BODs

You should use Show BODs to do bulk updates on the database. For example, when setting up a new service where historical data is required. It would not result in a push action, and only the sync verb is used in push reporting.