| # Migrate Integration Transactions (bcttf0220m000) Use this session to migrate the integration transactions that are already posted in Baan IVc. The data of Baan IVc is copied to ERP LN 6.1 through 3 interim tables. Table Integration Transactions (References) (bcttf020) contains the data of Baan IVc table Integration References (tfgld418). Table Integration Transactions (bcttf021) contains the data of Baan IVc table Integration Transactions (tfgld410). Table Integration Transactions (Posted Credit Lines) (bcttf022) contains the data of Baan IVc table Posted Integration Transactions - Credit Lines (tfgld417). Preparation Before you can use this session, the migration of the 3 interim tables Integration Transactions (References) (bcttf020), Integration Transactions (bcttf021) and Integration Transactions (Posted Credit Lines) (bcttf022) must be done. Execution This session must be executed to make the old integration transactions available in the new table Integration Transactions (tfgld482). Process logic For performance reasons a range of financial transactions can be selected. Even if the session runs, the Cancel button of the progress indicator will stop the session. With help of the indicator Processed (bcttf020.proc) the session is restartable. The already processed lines are skipped. Next new fields in ERP LN 6.1 are filled with a fixed value: GUID (tfgld482.guid) is filled with a new determined unique GUID for the whole financial transaction (Debit and Credit line that belongs to each other). Field Currency Rate Type (tfgld482.rtyp) is filled with the internal rate type (see session Companies (tcemm1170m000)). Field Integration Document Type Code (tfgld482.idtc) is filled with a new value generated based on Transaction Origin (bcttf020.tror), Financial Transaction (bcttf020.fitr) and Additional Type (bcttf001.adtp). Note that the new field will start with ‘11’ to separate them from the integrattion transaction posted in ERP LN 6.1. Field Originating Logistic Company is filled with a new value that is determined based on Transaction Origin (bcttf020.tror) and Financial Transaction (bcttf020.fitr). Field Business Object is filled with the Project (bcttf020.cprj) for project-related transactions, otherwise it is filled with the Order Number (bcttf020.orno). Note that for inventory transactions, this field is filled with the field Inventory Transaction ID generated during the conversion of table Inventory Transactions by Item and Warehouse (whinr110). Note that General Cost transactions originating from session Maintain Hours Accounting Transactions (tphrs1100m000) are linked to a fixed employee code “ZZZZZZZ” because no project and no order is filled in such transactions. Field Express in Base Currency is filled with the value belonging to the field Transaction Amount determined for the current date. Note that the Business Object Reference (tfgld482.obre) can not be filled because the originating line can not be found from the integration transaction. The empty field Business Object Reference (tfgld482.obre) causes that zooming from the migrated transactions to the transaction origin will not work. Also some fixed integration transaction additions (see session Logged Elements (tfgld4583m000)) are logged if the related fiels is filled at the migrated integration transactions. Next elements are used: Sales Order / Sold - to BP (code "110300000000") Sales Order / Country (code "110800000000") Purchase Order / Buy from BP (code = "210300000000") Warehouse Order / Item (code "320100000000") Warehouse Order / Warehouse (code "320200000000") Warehouse Order / Project (code "320300000000") Warehouse Order / Item Cost Component (code"322100000000") Financial transactions (containing A Debit posting and one or more credit postings) than contain one or more errors are printed at an error report and are skipped. The whole financial transaction is processed if it contains no error. Duration Warning: Execution of this session takes a long time, because of the high volume of the source tables. Restart When you will restart the session, the not yet processed transactions are handled. Note The lead time used by this session can be shortened by starting this session more times. Per bshell for example a separate Transaction Origin can be processed. Company The selection of the originating company can be filled here. Transaction Origin The selection of the origin of the financial transaction can be filled here. Note that the Baan IVc origin is used here. Financial Transaction The selection of the financial transaction can be filled here. Note that the Baan IVc origin is used here. Simulate The simulate indicator can be used to do a trial run first. If simulate = ‘No’ then the definite run is executed. |