| Fixed Dimension Definitions (tfbia8502m000) |  |
| Use this session to view fixed dimension definitions, which represent the additional attributes in the financial transactions of ERP LN that can be published as dimensions. These fixed dimensions can be published: Business Partner This dimension is used in the SourceSystemGLMovementBOD if ledger balances for ledger accounts are stored by business partner. It is used in the SourceSystemJournalEntryBOD for transactions that are related to a business partner, such as invoices and payments. If the Business Partner Balance check box is selected in the Chart of Accounts (tfgld0508m000) session, publishing the business partner dimension sequence is mandatory. Ledger Unit 1 and Ledger Unit 2 These dimensions are used in the SourceSystemGLMovementBOD and the SourceSystemJournalEntryBOD if ledger balance quantities and transaction quantities are stored in ERP LN. Through these dimension fields, the quantities and their related unit codes are published in the BODs. Although the quantities and their related unit codes can be published in the BODs, they are not stored in the reporting database. Therefore, do not publish these dimension sequences, unless you really need them in the BODs. Other dimensions Other dimensions, such as tax code, tax country, tax ledger account, reconciliation group, cash flow reason, and journal book are only used in the SourceSystemJournalEntryBOD. The reason for this is that the ledger balances are not stored by these codes in ERP LN. The codes are only available on ledger transactions. Because these dimensions are not available in the ledger/dimension balances, do not publish these dimension sequences, unless you really need them in the BODs. You can specify: Which dimension sequence must be included in the BODs. For a dimension sequence, the name that is used in the reporting database for PM Dashboards. This name can deviate from the name used in ERP LN Financials. This can be useful if data from multiple ERPs is stored in the reporting database and the setup differs between the ERPs. To approve a single dimension definition or enter a name, double-click the appropriate line. This will start the Fixed Dimension Definitions (Details) (tfbia8102s000) session. To approve a range of dimension definitions, use the Approve Range command on the appropriate menu. After approval of the dimension definition, the dimension name is published in the CodeDefinitionBOD, which results in a code list using this dimension name in the Public MDM of Evolve applications. Therefore, you can then no longer modify the data in this session. Note Use the Map LN Dimensions to Reporting Dimensions (tfbia8503m000) session to map the dimension sequences used in ERP LN to the external dimension sequences in the reporting database. Related topics To configure ERP LN for BOD publishing To use dimensions
Fields | Description
Dimension Sequence | The dimension sequence number.
Default Dimension Description | The default dimension description. Note To create default descriptions for a selected range of dimension definitions, on the appropriate menu, click Create Default Dimension Descriptions. ERP LN then uses the (hard-coded) dimension names provided by the ERP LN application.
Publish | If this check box is selected, the dimension definition was approved and published.
Dimension Name | The dimension name that is used in the reporting database. You can enter or change the name of an (unapproved) dimension definition in the Fixed Dimension Definitions (Details) (tfbia8102s000) session. Note The dimension name must not contain multibyte characters or an underscore ("_" ).
Approved | If this check box is selected, the dimension definition was approved.