| Tenant, Accounting Entity and Location (tcemm3100m000) |  |
| Use this session to configure how ERP LN selects the relevant tenant, accounting entity, and location when creating Business Object Documents (BODs). The codes for tenant, accounting entity, and location defined in this session must be the same as the codes used in the other applications that integrate with ERP LN. Search strategy Each record in this session specifies a tenant, and optionally an accounting entity and location. If a Business Object Document (BOD) is created, ERP LN searches for an applicable record. If ERP LN attempts to create a BOD for which this session contains no matching record, ERP LN fails to create the BOD. A distinction is made between BODs for transactional data and BODs for master data. Transactional data For BODs for transactional data, ERP LN first attempts to select the applicable record based on the following information: The company number. Additional input data, which is one of the following: A department. A warehouse. A project. An enterprise unit. If no matching record is found in the previous step, and the input data is of type Department, Warehouse, or Project, ERP LN retrieves the enterprise unit of this department, warehouse or project and searches for a record for that enterprise unit. Note For BODs for contracts, requests-for-quotation (RFQ), and purchase requisitions, the department can be unspecified. In that case, ERP LN can select a record with the Type field Department and an empty Code field. Master data For BODs for master data, the input data is of type Master Data. For BODs for master data, ERP LN attempts to select the applicable record based on the following information: The company number. The code of a master data element. If no matching record is found in the previous step, ERP LN selects the record where the Type field is Master Data and the Code field is empty. Important! Specify a record for each relevant company with the Type field Master Data and the Code field empty. These records serve as default. Related topics To configure ERP LN for BOD publishing
Fields | Description
Company | A working environment in which you can carry out logistic or financial transactions. All the transaction data is stored in the company's database. Depending on the type of data that the company controls, the company is: A logistic company. A financial company. A logistic and a financial company. In a multisite structure, some of the database tables can be unique for the company and the company can share other database tables with other companies.
Type | The Type and Code fields are part of the key based on which ERP LN selects the applicable record. The Type field can have the following values: Department The Code field contains the code of a department. Warehouse The Code field contains the code of a warehouse. Project The Code field contains the code of a project. Enterprise Unit The Code field contains the code of a enterprise unit. Master Data The Code field contains the code of the noun of the BOD.
Tenant | In a Software as a Service (SaaS) software deployment environment, a tenant is the client organization that uses the software that is offered as a service. No data is shared between tenants. The tenant is the top level container for all data. In ERP LN, the tenant is always a constant value for an ERP LN installation. Tenant is a mandatory field in Business Object Documents (BODs). To keep the data in test companies separated from the live data, you can specify a separate tenant code for the test companies. Note Some applications have a hard coded tenant code. If ERP LN integrates with these applications, you must enter the same codes here. For integration with MyDay, this field must be infor.
Accounting Entity | The lowest level on which financial reports are produced. In ERP LN, accounting entities have a one-to-one relationship with financial companies. Accounting entity is a mandatory field in Business Object Documents (BODs) for transactional data. Department and warehouses belonging to the same financial company must have the same value for this field.
Location | The physical location associated with the data or transaction, such as a warehouse, production site, city, or country. Location is a mandatory field in Business Object Documents (BODs) for transactional data. Allowed values The following values are permitted: Warehouse codes Department codes Location codes defined manually in the PublicMDM (Master Data Management component).