| # Master Data Introduction By using the related initial-load publish sessions, you can enforce the publication of existing master data from Infor LN. However, since dependencies and references exist between certain BODs, you must publish the master data in the order given in the Initial load section. Apart from initial data loading, whenever master data is created or maintained in Infor LN the BOD publishing is triggered. Unlike the initial-load BOD publishing of master data, staging is also possible for the creation and maintenance of the triggered master data BOD publishing. When you enable staging for a certain BOD, it is recommended that you enable a similar staging for referenced BODs. Relevant relationships between BODs are indicated in the subsections of this chapter. Initial Load You must perform the initial load in the correct order (For example, you must first publish projects, and then items) because references exist between objects. The master data that is used by the integration must be published in this order: In the Publish Logistic Code Definitions A-L (tcbod0200m100) and Publish Logistic Code Definitions M-Z (tcbod0200m200) sessions, on the various tabs; select: Business Sector Cost Component Financing Method Area Line of Business or Line of Business Invoice Delivery Method Item Standard Equipment Project Equipment Standard Subcontracting Project Subcontracting Standard Labor Project Labor Overhead Phase Acquiring Method Categories Label is set in script Label is set in script Standard Revenues Project Revenues Sales Type Standard Sundry Costs Project Sundry Costs Label is set in script In the Publish Financial Master Data (tfbia0200m000) session, on the various tabs; select: Label is set in script In the Publish Logistic Master Data (tcbod0200m000) session, select: Label is set in script PartyMaster > Sold-to Business Partner In the Publish Project Data (tpbod0200m000) session, select: Label is set in script Label is set in script- (depends on earlier publication of Label is set in script) Label is set in script Label is set in script- (depends on earlier publication of Label is set in script) Label is set in script Label is set in script- (depends on earlier publication of Label is set in script) In the Publish Logistic Master Data (tcbod0200m000) session, select: Label is set in script CodeDefinition For project-specific master data, the published code is prefixed with the project ID. Apart from project-specific items, this applies to project-specific labor, sundry costs, and other control codes. FinancialCalender The Period Table code in Infor LN translates to a common FinancialCalendar ID. Before publication, in order to prevent any redundancies with the financial FinancialCalendar, the ID is prefixed as “C_”. The entire common FinancialCalendar is always published, that is, all years and all periods that relate to a certain Period Table code. Person No specific dependencies exist. Customer Party Master No specific dependencies exist. LnUserDefinedStructure All user defined hierarchical structures of type OBS, and that are used in projects, are published. ProjectMaster As ProjectMaster publishing is triggered from different locations, it is recommended that staging is enabled. The SyncProjectMaster BOD is triggered when the user creates a project. Subsequent triggering is only executed when the project is activated and for active projects, when changes are made to the project itself, or to the activities and elements structures. The entire project header and the project structure are published. LaborCostMaster LaborCostMaster is published as soon as this is created in Infor LN. For project-specific labor, the published code is prefixed with the project ID. SundryCostMaster SundryCostMaster is published as soon as it is created in Infor LN. For project-specific sundry costs, the published code is prefixed with the project ID. ItemMaster Infor LN publishes all items. For project cost and earned value reporting, items that have an item control code published as one of the classifications in the ItemMaster are relevant. These items are used as cost objects in projects, that is, cost objects of cost type material, equipment, or subcontracting item. Additionally, from Infor LN 10.2.0 onwards, material-type items that have no specific item project data defined and therefore have no control code in Infor LN, can still be used within projects for cost transactions. In such cases, before storing the item, Infor BI uses the item’s control code as the item code. This is done because certain reports can only be generated by control code. |