customization guide for external integration transactionsbaansupport.com/docs/erpln/u9002b...

Infor10 ERP Enterprise (LN)

Customization Guide for External IntegrationTransactions

© Copyright 2011 Infor

All rights reserved. The word and design marks set forth herein are trademarks and/or registered trademarks of Inforand/or its affiliates and subsidiaries. All rights reserved. All other trademarks listed herein are the property of their respectiveowners.

Important Notices

The material contained in this publication (including any supplementary information) constitutes and contains confidentialand proprietary information of Infor.By gaining access to the attached, you acknowledge and agree that the material (including any modification, translationor adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the soleproperty of Infor and that you shall not gain right, title or interest in the material (including any modification, translation oradaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solelyin connection with and the furtherance of your license and use of software made available to your company from Inforpursuant to a separate agreement (“Purpose”).In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain suchmaterial in strict confidence and that your use of such material is limited to the Purpose described above.Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Inforcannot warrant that the information contained in this publication is complete, does not contain typographical or othererrors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability,consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors oromissions in this publication (including any supplementary information), whether such errors or omissions result fromnegligence, accident or any other cause.

Trademark Acknowledgements

All other company, product, trade or service names referenced may be registered trademarks or trademarks of theirrespective owners.

Publication Information

U9002B USDocument code

FP7Release

September 2011Publication date

About this document

.................7Chapter 1 Introduction........................................................................................................

.................7Introduction..................................................................................................................

.................7Purpose..............................................................................................................

.................7Definitions, acronyms and abbreviations...........................................................

.................9Chapter 2 Procedure...........................................................................................................

.................9Procedure....................................................................................................................

.................9Introduction........................................................................................................

.................9Master data........................................................................................................

.................9Mapping scheme................................................................................................

...............10Integration transactions......................................................................................

...............11Chapter 3 Master Data Setup..............................................................................................

...............11Master Data Setup.......................................................................................................

...............11Initialization script...............................................................................................

...............11Business objects (tfgld454)................................................................................

...............12Elements (tfgld456)............................................................................................

...............13Integration document types (tfgld457)...............................................................

...............15Elements by integration document type (tfgld458).............................................

...............15Additional procedure steps................................................................................

...............17Chapter 4 Mapping Scheme Setup....................................................................................

...............17Mapping Scheme Setup..............................................................................................

...............17Procedure...........................................................................................................

...............19Chapter 5 External Integration Transactions....................................................................

...............19External Integration Transactions................................................................................

...............19Introduction........................................................................................................

...............20Integration transactions (tfgld482).....................................................................

...............28Logged elements (tfgld481)...............................................................................

Table of Contents

...............29Unmapped/unposted integration transactions (tfgld487)...................................

...............30GL code by integration transaction (tfgld486)....................................................

How to read this document

Comments?We continually review and improve our documentation. Any remarks/requests for information concerningthis document or topic are appreciated. Please e-mail your comments to [email protected] .

In your e-mail, refer to the document number and title. More specific information will enable us to processfeedback efficiently.

Customer SupportIf you have questions regarding the Infor products described, go to Infor’s Customer Support portal atwww.infor365.com .

▪ To access Infor365, go to www.infor365.com and log in. If you do not have an Infor365 account,click Register now, complete the registration form, and a login will be sent to you within 24hours.

▪ To access Infor knowledgebases, documentation, downloads, communities, and incidents,click the appropriate link in the top menu of the home page.

▪ To find your local support phone number, click Contact Infor in the top right corner of thehome page, enter a product name, and click Search.

Infor10 ERP Enterprise (LN) | Customization Guide for External Integration Transactions | 5

About this document

mailto:[email protected]

http://www.infor365.com/

http://www.infor365.com/

6 | Infor10 ERP Enterprise (LN) | Customization Guide for External Integration Transactions

About this document

Introduction

Purpose

In ERP LN 6.1, Financials is open for financial integration transactions originating from externalapplications, such as a salary application.

The current document describes the procedure that should be followed to achieve the eventual importand subsequent processing of external integration transactions in Financials.

Note

Note: The logging of reconciliation transactions, which is new in ERP LN 6.1, is not enabled for externalintegrations.

Definitions, acronyms and abbreviations

Definitions, acronyms and abbreviations used in the document are listed below in alphabetical order.

DefinitionTerm

Data access layerDAL

Dynamic link libraryDLL

Code that defines a specific combination of ledgeraccount and dimensions

GL code

Globally unique identifierGUID


1Chapter 1Introduction


Introduction

Procedure

Introduction

Before you can actually import integration transactions into Financials from an external source, you mustfirst initialize a series of master data, and extend the mapping scheme with the mapping setup for theintegration document types that are used in the external integration.

Master data

The integration mapping in ERP LN 6.1 Financials differs from the integration mapping in previous ERPLN versions in many aspects. A main difference is that in ERP LN 6.1, integration mapping makes useof a meta-modeled data model. Among other things, this means that database fields neither directlyrefer to concrete objects, such as purchase order, service order, and so on, nor to concrete elements,such as business partner, cost component, item, and so on. Instead, a meta model defines whichbusiness object and which element are referred to for a specific integration transaction (table tfgld482)or logged element (table tfgld481).

These meta-modeled master data have to be initialized for use in the mapping scheme by an initializationscript. For more information, refer to Chapter 3, "Master Data Setup."

Mapping scheme

After initialization of the external master data, create a new mapping scheme version (by copying anexisting mapping scheme). This new mapping scheme version must be extended with the mappingsetup for the external master data, namely, the new external integration document types. For theprocedure, refer to Chapter 4. "Mapping Scheme Setup."


2Chapter 2Procedure

Integration transactions

After the newmapping scheme versions has been activated, the system is fit to receive the new externalintegration transactions.

One of the most obvious methods to import external transactions into the Financials integrationtransactions tables, is to make use of an Exchange scheme, as has been done for previous ERP LNversions.

Compared to previous ERP LN versions, in some respects different data has to be provided (amongothers, the business object and elements already mentioned earlier), and it is mandatory to log moredata. For details, refer to Chapter 5, "External Integration Transactions."


Procedure

Master Data Setup

Initialization script

An initialization script has to be written which uses the DAL (DAL.NEW) of the involved tables to createrows 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, visiblein the Integration Transactions (tfgld4582m000) session).

RemarksMandatory*DomainFormatDescriptionField

must start withthe "#"-charac-

yestcbonastr(17)business objectbona

ter; other charac-ters are free tochoose; thisname will,among others,be displayed insession Integra-tion Transac-


3Chapter 3Master Data Setup

tions(tfgld4582m000)

value:tcyesno.yes

yestcyesnoenumtransaction log-ging allowed

lita

value:tcyesno.no

yestcyesnoenummapping al-lowed

maal

* 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 beprimarily used for ledger account and dimension mapping (among others, visible during the setting upof the mapping scheme).


must start withthe string "EXT";

yestfgld.elcdstr(12)element codeelcd

other charactersmust be numeric

(softly) refers totfgld454.bona

yestcbonastr(17)business objectbonm


yestcboatstr(17)business objectattribute

boat

ter; other charac-ters are free tochoose; thisname will be vis-ible while main-taining the map-ping scheme

description ofthe element that

yestcdscastr(30)element descrip-tion

elds

will be visible tothe user


Master Data Setup

value: 1yestfgld.srnobyteelement levellevl

should be leftempty (not usedexternally)

notfgld.elcdstr(12)parent elementpecd

should be leftempty (not usedexternally)

notcrelcstr(12)reconciliationelement

rcel

value:tcyesno.no (notused externally)

yestcyesnoenumbusiness partnerbpyn

value:tcyesno.no

yestcyesnoenumexpired y/nexpi


Integration document types (tfgld457)

This table contains the integration document types that will be part of integration transactions (amongothers, visible in the Integration Transactions (tfgld4582m000) session).


must start withthe string "EXT";

yestcidtystr(8)integration docu-ment type

idtc

other charactersmust be numeric


yestcdscastr(30)integration docu-ment type de-scription

idtd

ter; other charac-ters are free tochoose; thisname will,among others,be displayed insession Integra-tion Transac-


Master Data Setup

tions(tfgld4582m000)

(softly) refers totfgld454.bona

yestcbonastr(17)business objectbonm

(softly) refers totfgld456.elcd;

notfgld.elcdstr(12)sort elementsecd

must only befilled if the sortelement function-ality is used

value:tcyesno.no

yestcyesnoenummodifiable docu-ment type

modt


yestcyesnoenumpublish postingdetails

ppdt

value:tcyesno.no

yestcyesnoenumexpired y/nexpi

value:tcyesno.yes

yestcyesnoenumledger mappingmandatory

lemm

value:tcyesno.yes

yestcyesnoenumlog all elementsdebit

dlae

value:tcyesno.yes

yestcyesnoenumlog all elementscredit

clae

value:tcyesno.yes

yestcyesnoenummapping al-lowed

maal

value:tcyesno.yes

yestcyesnoenumlinked to integra-tion account

ltia



Master Data Setup

Elements by integration document type (tfgld458)

This table contains the elements that will be logged for a particular integration document type, and thatcan be used within the mapping scheme for ledger account and dimension mapping.


refers totfgld457.idtc


idtc

refers totfgld456.elcd

yestfgld.elcdstr(12)element codeelcd

value:tcyesno.yes

yestcyesnoenumdebit ledgermapping applic-able

dele

value:tcyesno.yes

yestcyesnoenumcredit ledgermapping applic-able

crle

value:tcyesno.no

yestcyesnoenumnever fillednefi


yestcyesnoenumbusiness part-ner for generalledger

bpgl


Additional procedure steps

After running the initialization script, in the Integration Parameters (tfgld4150s000) session, on theSpecific menu, select Initialize Descriptions to renew the business object and integration documenttype language dependent descriptions.

Subsequently, in the Period Handling by Integration Document Type (tfgld4579m000) session, for eachexternal integration document type – debit/credit combination, set the Closed Period Handling value toeither Post to next open period, or Post to current period, because exception handling is only applicablefor internal business objects. Because table tfgld479 must be shared for all financial companies (pleasecheck!), you do not need to repeat the latter action for each individual financial company.


Master Data Setup


Master Data Setup

Mapping Scheme Setup

Procedure

Next, set up the ledger account and dimensionmapping for the newly added external integration documenttypes, using the standard mapping scheme functionality.

This should be done according to the company’s usual procedure for adding new mappings to themapping scheme. The most obvious way to do this is to copy the existing mapping scheme to a newmapping scheme version. Subsequently, you can add the mapping for the external document types.Finally, the mapping scheme consistency must be checked, and, after all errors have been corrected,you can activate the mapping scheme.


4Chapter 4Mapping Scheme Setup


Mapping Scheme Setup

External Integration Transactions

Introduction

Now, the system is ready to receive financial integration transactions from an external source.

One of the most obvious methods to import external transactions into the Financials integrationtransactions tables, is to make use of an Exchange scheme, as has been done for previous ERP LNversions.

In the following sections, the requirements for the logged transactions are listed. The database tablesthat are involved are Integration transactions (tfgld482), Logged elements (tfgld481), Unmapped/unpostedintegration transactions (tfgld487), and, in case GL codes are involved, GL code by integration transaction(tfgld486).

Integration transactions must be logged in pairs (in tfgld482): a credit transaction and an accompanyingdebit transaction. Both transactions will be stored in the same financial company, which is the financialcompany of the credit transaction (this is important for inter-company postings). Both transactions mustbe assigned the same GUID (see below). The transactions will refer to the same unmapped/unposteddata in (tfgld487).

Each integration transaction can have a set of related logged elements (tfgld481). If the integrationtransaction has a GL code attached, an additional row must be stored in (tfgld486).

If a GL code is used, themapping schemewill be bypassed in determining ledger account and dimensions,and the transactions will be posted to the ledger account and dimensions defined for the GL code.


5Chapter 5External Integration Transactions

Integration transactions (tfgld482)

This table contains the individual integration transactions. Note that, as stated above, a debit transactionand a credit transactions that belong to each other must have the same GUID assigned.


must be thesame for credit

yestcguidstr(22)globally uniqueidentifier

guid

and debit trans-actions that be-long to eachother; to be as-signed usingfunctionuuid.generate$()

yestfgld.dbcrenumdebit/credit indic-ator

dbcr

logistic companyin which the

yestcncmpint(3)source logisticcompany

ocmp

business objectresides; must bethe same forcredit and debittransactions thatbelong to eachother



idtc

and debit trans-actions that be-long to eachother; refers totfgld457.idtc

date on which,among others,

yestcdateutc datetransaction datetrdt

the documentdate will bebased; must bethe same for



credit and debittransactions thatbelong to eachother

same as sourcelogistic company(tfgld482.ocmp)

yestcncmpint(3)logistic companytcmp

(softly) refers totfgld456.elcd;

notfgld.elcdstr(12)sort elementsecd

must only befilled if the sortelement function-ality is used

belongs totfgld482.secd

notcelvastr(50)sort elementvalue

seva


yestcbonastr(17)business objectrbon

and debit trans-actions that be-long to eachother; refers totfgld454.bona


yestcboidstr(11)business objectID

rbid

and debit trans-actions that be-long to eachother; the ID ofthe business ob-ject, for ex-ample, the pur-chase ordernumber in caseof a purchaseorder


notcsopolong(8)sort positionrpon

and debit trans-actions that be-



long to eachother; used inindices for de-tailed sorting bybusiness object(see indicestfgld482),among others,used in Integra-tion Transac-tions(tfgld4582m000)


notcborfstr(40)business objectreference

obre

and debit trans-actions that be-long to eachother; extensionof the businessobject ID, tospecify moreprecisely whatorigin the trans-action relates to;first part shouldbe the same astfgld482.rpon

leave empty: notused externally

notcguidstr(22)business objectreference GUID

buid

(softly) refers totccom100; busi-

notccom.bpidstr(9)business partnerbpid

ness partnerthat should belogged with thetransaction inthe generalledger

leave empty; de-termined duringposting

notfgld.ttypstr(3)transaction typettyp




notfgld.docnlong(8)document num-ber

docn


notfgld.btnolong(6)batch numberbtno


notfgld.linolong(8)line numberlino

must be set totfgld.ints.mapped

yestfgld.intsenumtransactionstatus

sint

if a GL code isinvolved, other-wise must bedefaulted totfgld.ints.logged


yestcdateutc datecreation datecrdt

and debit trans-actions that be-long to eachother; the dateof the actualcreation of theintegrationtransaction

user ID (log-name$) of the

yestfgld.userstr(16)user (creation)crus

user that logsthe transaction;must be thesame for creditand debit trans-actions that be-long to eachother

refers totfgld435; to be

notfgld.usgrstr(6)financial usergroup

usgr

retrieved from



tfgld436 fortfgld482.crus;does not have tobe present,though


notfgld.userstr(16)user (posting)pous


notcdateutc dateposting datepodt

value:tcyesno.no

yestcyesnoenumprintedprin

value must beset to

yestcyesnoenumGL code usedglcu

tcyesno.yes if aGL code isused, otherwisetcyesno.no

financial com-pany to which

yestcncmpint(3)financial com-pany

fcom

general ledgerthe specifictransactionmustbe posted; candiffer betweenthe credit trans-action and thedebit transactionit belongs to; forthe credit trans-action, it mustalways be thefinancial com-pany in whichthe integrationtransactions arelogged (thephysical finan-cial company)



must be empty ifno GL code is

notfgld.leacstr(12)ledger accountleac

used; however,if GL code isused, then itmust be filled byretrieval fromtfgld475

seetfgld482.leac

notfgld.dimxstr(6)dimension 1dim1

seetfgld482.leac


seetfgld482.leac


seetfgld482.leac


seetfgld482.leac



yestfgld.amntdoubletransactionamount

amnt

and debit trans-actions that be-long to eachother; must beproperly roun-ded; zero can bea valid value


yestcccurstr(3)transaction cur-rency code

ccur

and debit trans-actions that be-long to eachother; refers totcmcs002

date for whichthe currency

yestcdateutc datecurrency ratedate

ratd



rates towardsthe homecurren-cies have beenretrieved; prob-ably equal totfgld482.trdt

rate type used inthe home

yestcrtypstr(3)currency ratetype

rtyp

amounts calcula-tion; will prob-ably be equal tothe (financial)company’s in-ternal rate type(tcemm170.ex-eu)

rates towardsthe transaction’s

yestcratcdouble (array)currency ratesrate

financial com-pany’s homecurrencies; canbe retrieved us-ing the standardtcemm.dll5000/5010 functions

rate factors to-wards the trans-

yestcratflong(6) (array)currency ratefactors

ratf

action’s financialcompany’shome curren-cies; can be re-trieved using thestandardtcemm.dll5000/5010 functions

"Express inBase Currency"

yestcyesnoenum (array)express in basecurrency indicat-ors

eibc

indicators to-wards the trans-action’s financialcompany’s



home curren-cies; can be re-trieved using thestandardtcemm.dll5000/5010 functions

amounts in thetransaction’s fin-

yestfgld.amntdouble (array)amounts inhome currency

amth

ancial com-pany’s homecurrencies; canbe calculatedusing the stand-ardtcemm.dll5000/5010 functions;must be properlyrounded aftercalculation

refers totcmcs001; must

notccunistr(3)the quantity’sunit

cuni

be filled if aquantity islogged

belongs totfgld482.cuni

notfgld.quandoublequantitynuni

see tfgld482.fprdyestfgld.yearint(4)financial yearfyer

must be filled,and must exist

yestfgld.prodint(2)financial periodfprd

in tfgld005; canbe determinedbased ontfgld482.trdt(transaction dateand financialperiod shouldpreferably be inline)



mandatory if re-porting periods

notfgld.yearint(4)reporting yearryer

are used; seetfgld482.fyer

mandatory if re-porting periods

notfgld.prodint(2)reporting periodrprd

are used; seetfgld482.fprd

see tfgld482.fyeryestfgld.yearint(4)tax yeartyer

see tfgld482.fprdyestfgld.prodint(2)tax periodtprd

leave empty; de-termined duringmapping

notfgld.mscdstr(6)used mappingscheme code

mscd

leave empty; de-termined duringmapping

notfgld.msvslong(5)used mappingscheme version

msvs


Logged elements (tfgld481)

This table contains the logged elements by integration transaction, which elements will be used formapping of the integration transaction.


(softly) refers totfgld482.guid

yestcguidstr(22)globally uniqueidentifier

guid

(softly) refers totfgld482.dbcr

yestfgld.dbcrenumdebit/credit indic-ator

dbcr

sequence num-ber to extend

yestcponoint(4)sequence num-ber

seqn

the primary key;first 30 elementsmust be stored



in the row withsequence num-ber 1, next 30 inthat with number2, and so on.

each element(softly) refers to

yestfgld.elcdstr(12) (array)element codeselcd

tfgld456.elcd;elements thathave an emptyvalue do nothave to belogged

belongs totfgld481.elcd

yestcelvastr(50)element valueselva


Unmapped/unposted integration transactions (tfgld487)

This table contains the integration transactions pairs, and will be used during mapping and posting. Itis actually a parent table of tfgld482.




= tfgld482.guidyestcguidstr(22)globally uniqueidentifier

guid

value:tfgld.ints.logged

yestfgld.intsenumtransactionstatus

sint

= tfgld482.ocmpyestcncmpint(3)source logisticcompany

ocmp

the credit trans-action’s finan-cial company

yestcncmpint(3)credit financialcompany

fcom

= tfgld482.rbonyestcbonastr(17)business objectrbon

= tfgld482.idtcyestcidtystr(8)integration docu-ment type

idtc

= tfgld482.trdtyestcdateutc datetransaction datetrdt

= tfgld482.usgrnotfgld.usgrstr(6)financial usergroup

usgr

= tfgld482.crdtyestcdateutc datecreation datecrdt


GL code by integration transaction (tfgld486)

This table contains the information which GL code has been used in a certain integration transaction.




= tfgld482.guidyestcguidstr(22)globally uniqueidentifier

guid

= tfgld482.dbcryestfgld.dbcrenumdebit/credit indic-ator

dbcr

= tfgld482.fcom;(softly) refers totfgld475.fcmp

yestcncmpint(3)financial com-pany

fcom

(softly) refers totfgld475.glcd

yestcglcostr(50)GL codeglco




customization guide for external integration transactionsbaansupport.com/docs/erpln/u9002b...

Documents