Master Data Setup
Initialization script
- An initialization script must be written which uses the DAL
(DAL.NEW) of the involved tables to create rows in the database tables
mentioned in the sections below.
- Naming conventions mentioned in this document should be
strictly adhered to. Otherwise, mixing up with (future) standard data cannot be
ruled out.
Business objects (tfgld454)
This table shows the business objects that will be part of
integration transactions displayed in, for example, the Integration Transactions (tfgld4582m000) session.
| Field | Description | Format | Domain | Mandatory * | Comments |
|---|
| bona | business object | str(17) | tcbona | Yes | must start with the "#"-character; other characters are free to
choose; this name will be displayed in, for example, the Integration Transactions (tfgld4582m000) session |
| lita | transaction logging allowed | enum | tcyesno | Yes | value: tcyesno.yes |
| maal | mapping allowed | enum | tcyesno | Yes | value: tcyesno.no |
* For external data, this setting may be different from the
table field’s property.
Elements (tfgld456)
This table shows the elements that will be logged related to
integration transactions, and will be primarily used for ledger account and
dimension mapping. The elements are displayed when, for example, you set up the
mapping scheme.
| Field | Description | Format | Domain | Mandatory * | Comments |
|---|
| elcd | element code | str(12) | tfgld.elcd | Yes | must start with the string "EXT"; other characters must be
numeric |
| bonm | business object | str(17) | tcbona | Yes | soft reference to tfgld454.bona |
| boat | business object attribute | str(17) | tcboat | Yes | must start with the "#" character; other characters are free to
choose; this name will be displayed when you maintain the mapping scheme |
| elds | element description | str(30) | tcdsca | Yes | description of the element that will be visible to the user |
| levl | element level | byte | tfgld.srno | Yes | value: 1 |
| pecd | parent element | str(12) | tfgld.elcd | No | should be left empty (not used externally) |
| rcel | reconciliation element | str(12) | tcrelc | No | should be left empty (not used externally) |
| bpyn | business partner | enum | tcyesno | Yes | value: tcyesno.no (not used externally) |
| expi | expired y/n | enum | tcyesno | Yes | value: tcyesno.no |
* For external data, this setting may be different from the
table field’s property.
Integration document types (tfgld457)
This table shows the integration document types that will be
part of integration transactions displayed in, for example, the Integration Transactions (tfgld4582m000) session.
| Field | Description | Format | Domain | Mandatory * | Comments |
|---|
| idtc | integration document type | str(8) | tcidty | Yes | must start with the string "EXT"; other characters must be
numeric |
| idtd | integration document type description | str(30) | tcdsca | Yes | must start with the "#" character; other characters are free to
choose; this name will be displayed in, for example, the Integration Transactions (tfgld4582m000) session |
| bonm | business object | str(17) | tcbona | Yes | soft reference to tfgld454.bona |
| secd | sort element | str(12) | tfgld.elcd | no | soft reference to tfgld456.elcd; must only be filled if the sort
element functionality is used |
| modt | modifiable document type | enum | tcyesno | Yes | value: tcyesno.no |
| ppdt | publish posting details | enum | tcyesno | Yes | value: tcyesno.no (not used externally) |
| expi | expired y/n | enum | tcyesno | Yes | value: tcyesno.no |
| lemm | ledger mapping mandatory | enum | tcyesno | Yes | value: tcyesno.yes |
| dlae | log all elements debit | enum | tcyesno | Yes | value: tcyesno.yes |
| clae | log all elements credit | enum | tcyesno | Yes | value: tcyesno.yes |
| maal | mapping allowed | enum | tcyesno | Yes | value: tcyesno.yes |
| ltia | linked to integration account | enum | tcyesno | Yes | value: tcyesno.yes |
* For external data, this setting may be different from the
table field’s property.
Elements by integration document type
(tfgld458)
This table shows the elements that will be logged for a
particular integration document type, and that can be used within the mapping
scheme for ledger account and dimension mapping.
| Field | Description | Format | Domain | Mandatory * | Comments |
|---|
| idtc | integration document type | str(8) | tcidty | Yes | refers to tfgld457.idtc |
| elcd | element code | str(12) | tfgld.elcd | Yes | refers to tfgld456.elcd |
| dele | debit ledger mapping applicable | enum | tcyesno | Yes | value: tcyesno.yes |
| crle | credit ledger mapping applicable | enum | tcyesno | Yes | value: tcyesno.yes |
| nefi | never filled | enum | tcyesno | Yes | value: tcyesno.no |
| bpgl | business partner for general ledger | enum | tcyesno | Yes | value: tcyesno.no (not used externally) |
* For external data, this setting may be different from the
table field’s property.
Additional procedure steps
After running the initialization script, complete these
steps:
- To update the business object and integration document type
language dependent descriptions, in the Integration Parameters (tfgld4150s000) session, from the appropriate menu,
select Initialize Descriptions.
In the Period Handling by Integration Document Type (tfgld4579m000) session, for each external
integration document type – debit/credit combination, set Closed Period Handling to either Post to next open period or Post to current period. (Exception handling is only applicable for internal
business objects.)
Because table tfgld479 must be shared for all financial
companies (please check!), you do not need to repeat this step for each
individual financial company.