| # Tenant, Accounting Entity and Location (tcemm3100m000) Use this session to configure how 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 LN. Before LN can use a record to create a BOD, you must approve the record. To approve a record, or undo the approval, select the record and click the corresponding command in the appropriate menu. To generate records for this session, use the Generate Tenant, Accounting Entity and Location (tcemm3200m000) session. 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, LN searches for an applicable record. If LN attempts to create a BOD for which this session contains no matching record, 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, 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, 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), purchase requisitions. and some types of warehousing orders, the department can be unspecified. In that case, 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, 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, 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 Configuring LN for BOD publishing 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 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 LN, the tenant is always a constant value for an 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 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 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 that is 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). Approved If this check box is selected, this record is available for creating BODs To select or clear this check box, use the commands in the appropriate menu. Approval Date The data of the last time this record was set to approved. Approve Selects the Approved check box. Undo Approve Clears the Approved check box. Generate Tenant, Accounting Entity and Location Starts the Generate Tenant, Accounting Entity and Location (tcemm3200m000) session. |