| # Master Data Setup Initialization script An initialization script has to be written which uses the DAL (DAL.NEW) of the involved tables to create rows in the database tables mentioned in the sections below. It is important that the naming conventions mentioned in this document should be strictly adhered to. Otherwise, mixing up with (future) standard data cannot be excluded. Business objects (tfgld454) This table lists the business objects that will be part of integration transactions (among others, visible in the Integration Transactions (tfgld4582m000) session).
Field | Description | Format | Domain | Mandatory* | Remarks
--- | --- | --- | --- | --- | ---
bona | business object | str(17) | tcbona | yes | must start with the "#"-character; other characters are free to choose; this name will, among others, be displayed in session Integration Transactions (tfgld4582m000)
lita | transaction logging allowed | enum | tcyesno | yes | value: tcyesno.yes
maal | mapping allowed | enum | tcyesno | yes | value: tcyesno.no
* The Mandatory option for external data can deviate from the table field’s property. Elements (tfgld456) This table contains the elements that will be logged related to integration transactions, and will be primarily used for ledger account and dimension mapping (among others, visible during the setting up of the mapping scheme).
Field | Description | Format | Domain | Mandatory* | Remarks
--- | --- | --- | --- | --- | ---
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 | (softly) refers 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 visible while maintaining 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
* The Mandatory option for external data can deviate from the table field’s property. Integration document types (tfgld457) This table contains the integration document types that will be part of integration transactions (among others, visible in the Integration Transactions (tfgld4582m000) session).
Field | Description | Format | Domain | Mandatory* | Remarks
--- | --- | --- | --- | --- | ---
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, among others, be displayed in session Integration Transactions (tfgld4582m000)
bonm | business object | str(17) | tcbona | yes | (softly) refers to tfgld454.bona
secd | sort element | str(12) | tfgld.elcd | no | (softly) refers 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
* The Mandatory option for external data can deviate from the table field’s property. Elements by integration document type (tfgld458) This table contains 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* | Remarks
--- | --- | --- | --- | --- | ---
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)
* The Mandatory option for external data can deviate from the table field’s property. Additional procedure steps After running the initialization script, in the Integration Parameters (tfgld4150s000) session, on the Specific menu, select Initialize Descriptions to renew the business object and integration document type language dependent descriptions. Subsequently, in the Period Handling by Integration Document Type (tfgld4579m000) session, for each external integration document type – debit/credit combination, set the Closed Period Handling value to either Post to next open period, or Post to current period, because 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 the latter action for each individual financial company. |