Integration transactions (tfgld482)

Integration transactions must be logged in pairs (in tfgld482): a credit transaction and an accompanying debit transaction. Both transactions will be stored in the same financial company, which is the financial company of the credit transaction (this is important for intercompany postings). Both transactions must be assigned the same GUID (see below). The transactions will refer to the same unmapped/unposted data in (tfgld487).

This table contains the individual integration transactions.

Note: Related debit and credit transactions must have the same GUID assigned.
Field Description Format Domain Mandatory * Comments
guid globally unique identifier str(22) tcguid Yes must be the same for related debit and credit transactions; to be assigned using function uuid.generate$()
dbcr debit/credit indicator enum tfgld.dbcr Yes  
ocmp source logistic company int(3) tcncmp Yes logistic company in which the business object resides; must be the same for related debit and credit transactions
idtc integration document type str(8) tcidty Yes must be the same for related debit and credit transactions; refers to tfgld457.idtc
trdt transaction date utc date tcdate Yes date on which, among others, the document date will be based; must be the same for related debit and credit transactions
tcmp logistic company int(3) tcncmp Yes same as source logistic company (tfgld482.ocmp)
secd sort element str(12) tfgld.elcd No soft reference to tfgld456.elcd; must only be filled if the sort element functionality is used
seva sort element value str(50) tcelva No belongs to tfgld482.secd
rbon business object str(17) tcbona Yes must be the same for related debit and credit transactions; refers to tfgld454.bona
rbid business object ID str(11) tcboid Yes must be the same for related debit and credit transactions; the ID of the business object, for example, the purchase order number in case of a purchase order
rpon sort position long(8) tcsopo No must be the same for related debit and credit transactions; used in indices for detailed sorting by business object (see indices tfgld482), among others, used in Integration Transactions (tfgld4582m000)
obre business object reference str(40) tcborf No must be the same for related debit and credit transactions; extension of the business object ID, to specify more precisely what origin the transaction relates to; first part should be the same as tfgld482.rpon
buid business object reference GUID str(22) tcguid No leave empty: not used externally
bpid business partner str(9) tccom.bpid No soft reference to tccom100; business partner that should be logged with the transaction in the General Ledger
ttyp transaction type str(3) tfgld.ttyp No leave empty; determined during posting
docn document number long(8) tfgld.docn No leave empty; determined during posting
btno batch number long(6) tfgld.btno No leave empty; determined during posting
lino line number long(8) tfgld.lino No leave empty; determined during posting
sint transaction status enum tfgld.ints Yes must be set to tfgld.ints.mapped if a GL code is involved, otherwise must be defaulted to tfgld.ints.logged
crdt creation date utc date tcdate Yes must be the same for related debit and credit transactions; the date of the actual creation of the integration transaction
crus user (creation) str(16) tfgld.user Yes user ID (logname$) of the user who logs the transaction; must be the same for related debit and credit transactions
usgr financial user group str(6) tfgld.usgr No refers to tfgld435; to be retrieved from tfgld436 for tfgld482.crus; however, does not need to exist
pous user (posting) str(16) tfgld.user No leave empty; determined during posting
podt posting date utc date tcdate No leave empty; determined during posting
prin printed enum tcyesno Yes value: tcyesno.no
glcu GL code used enum tcyesno Yes value must be set to tcyesno.yes if a GL code is used, otherwise tcyesno.no
fcom financial company int(3) tcncmp Yes financial company to whose General Ledger the transaction must be posted; can differ between the credit transaction and the debit transaction it belongs to; for the credit transaction, it must always be the financial company in which the integration transactions are logged (the physical financial company)
leac ledger account str(12) tfgld.leac No must be empty if no GL code is used; otherwise, it must be filled by retrieval from tfgld475
dim1 dimension 1 str(6) tfgld.dimx No see tfgld482.leac
dim2 dimension 2 str(6) tfgld.dimx No see tfgld482.leac
dim3 dimension 3 str(6) tfgld.dimx No see tfgld482.leac
dim4 dimension 4 str(6) tfgld.dimx No see tfgld482.leac
dim5 dimension 5 str(6) tfgld.dimx No see tfgld482.leac
amnt transaction amount double tfgld.amnt Yes must be the same for related debit and credit transactions; must be properly rounded; zero can be a valid value
ccur transaction currency code str(3) tcccur Yes must be the same for related debit and credit transactions; refers to tcmcs002
ratd currency rate date utc date tcdate Yes date for which the currency rates towards the home currencies have been retrieved; probably equal to tfgld482.trdt
rtyp currency rate type str(3) tcrtyp Yes rate type used in the home amounts calculation; will probably be equal to the (financial) company’s internal rate type (tcemm170.exeu)
rate currency rates double (array) tcratc Yes rates towards the transaction’s financial company’s home currencies; can be retrieved using the standard tcemm.dll5000/5010 functions
ratf currency rate factors long(6) (array) tcratf Yes rate factors towards the transaction’s financial company’s home currencies; can be retrieved using the standard tcemm.dll5000/5010 functions
eibc express in base currency indicators enum (array) tcyesno Yes Express in Base Currency indicators towards the transaction’s financial company’s home currencies; can be retrieved using the standard tcemm.dll5000/5010 functions
amth amounts in home currency double (array) tfgld.amnt Yes amounts in the transaction’s financial company’s home currencies; can be calculated using the standard tcemm.dll5000/5010 functions; must be properly rounded after calculation
cuni the quantity’s unit str(3) tccuni No refers to tcmcs001; must be filled if a quantity is logged
nuni quantity double tfgld.quan No belongs to tfgld482.cuni
fyer financial year int(4) tfgld.year Yes see tfgld482.fprd
fprd financial period int(2) tfgld.prod Yes must be filled, and must exist in tfgld005; can be determined based on tfgld482.trdt (transaction date and financial period should preferably be in line)
ryer reporting year int(4) tfgld.year No mandatory if reporting periods are used; see tfgld482.fyer
rprd reporting period int(2) tfgld.prod No mandatory if reporting periods are used; see tfgld482.fprd
tyer tax year int(4) tfgld.year Yes see tfgld482.fyer
tprd tax period int(2) tfgld.prod Yes see tfgld482.fprd
mscd used mapping scheme code str(6) tfgld.mscd No leave empty; determined during mapping
msvs used mapping scheme version long(5) tfgld.msvs No leave empty; determined during mapping

* For external data, this setting may be different from the table field’s property.