| # To configure ERP LN for BOD publishing An integration can be established between ERP LN and other applications through business object documents (BODs) that are sent to Infor On-ramp. To exchange data between applications, specific configuration settings are required in ERP LN and the other application. This topic only handles the ERP LN configuration part. For an example of data configuration in another application, refer to the MyDay Integration Guide. Caution! To prevent ERP LN from publishing BODs before the setup in ERP LN is completed, in the BOD Parameters (tcbod0100m000) session, select the Prevent BOD Publishing check box. To validate the data setup Use the Validate Publishing Data Setup (tcbod0300m000) session to check whether the data setup is complete to publish BODs. You can run this session at the beginning and at the end of the ERP LN configuration for BOD publishing. Run this session at the beginning to view the data that must be filled. To map master data to ISO codes The BODs use ISO codes for currencies, countries, and languages. Maintain the mapping between the ERP LN specific codes and the ISO codes in the following sessions: Currencies (tcmcs0102m000) Countries (tcmcs0510m000) Languages (tcmcs0146m000) Note For countries, the 2-alpha ISO codes are used in the BODs, not the 3-alpha codes. For more information, refer to ISO language and country codes. To define blocking reasons Define the following blocking reasons in the Inventory Handling Parameters (whinh0100m000) session, which are used as hold codes in multiple BODs: Inbound Inspection Blocking Reason Outbound Inspection Blocking Reason Rejection Blocking Reason To define tenants, accounting entities, and locations In the BODs, information on tenant, accounting entity, and location must be present.
Tenant | Accounting entity | Location
--- | --- | ---
The top level container. | The lowest level where financial reports are produced. | The physical location associated with the data or transaction. This can be a warehouse, a manufacturing location, or an office.
No data is shared between tenants. | Required on transactional BOD. | Optional on each BOD.
Required on each BOD. | Optional on master data BOD. | For evolve applications, required on transactional and balance BOD.
In the Tenant, Accounting Entity and Location (tcemm3100m000) session, create a mapping for these concepts based on department, warehouse, project, enterprise unit, and master data. You can use the Generate Tenant, Accounting Entity and Location (tcemm3200m000) session to generate records for the Tenant, Accounting Entity and Location (tcemm3100m000) session. To define financial master data To use financial BODs, you must first define financial master data in the following sessions: BIA Parameters (tfbia0500m000) Flexible Dimension Definitions (tfbia8501m000) Fixed Dimension Definitions (tfbia8502m000) Map LN Dimensions to Reporting Dimensions (tfbia8503m000) To load initial publication data To publish ERP LN data to On-ramp, an initial load of data is required from multiple ERP LN packages. Data is initially loaded from the following sessions: Publish Logistic Master Data (tcbod0200m000) Publish Financial Master Data (tfbia0200m000) Publish Order Management Transactional Data (tdbod0200m000) Publish Financial Transactional Data (tfbia0210m000) Publish Warehouse Management Transactional Data (whbod0200m000) Publish Manufacturing Transactional Data (tibod0200m000) Publish General Ledger Movement (tfbia8205m000) In general, you publish data from these sessions once. However, if errors occur during the publication process or if the other software application needs a new set of data, you can rerun the sessions. Note Before you run the publish transactional data sessions, you must run the publish master data sessions. Before you run the Publish Warehouse Management Transactional Data (whbod0200m000) and Publish Manufacturing Transactional Data (tibod0200m000) sessions, you must run the Publish Order Management Transactional Data (tdbod0200m000) session. Caution! After you have published the information for the BODs on On-ramp, the publication cannot be undone. For more information on the publication process, refer to the log files. To publish financial documents For ERP LN, the BODs are published when the business event happens. However, for performance reasons, several financial documents are published in separate sessions. Use the Publish Financial Documents (tfbia8210m000) session to publish the following documents: Invoice PayableTransaction ReceivableTransaction SourceSystemJournalEntry Use the Publish General Ledger Balances (tfbia8211m000) session to publish SourceSystemGLMovement messages. These sessions can be manually run or in a job mode. To publish inventory figures Usually, balance information is sent at quiet moments. Use the Publish InventoryCount Messages (whinr1448m000) session to publish InventoryCount BOD messages for warehouse-item combinations. This session can be manually run or in a job mode. Note A cycle counting order in ERP LN does not result in an InventoryCount BOD. The results of the cycle counting order are published via the InventoryAdjustment BOD. Related topics ISO language and country codes |