<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tf/integrations/400012" xml:lang="en">
   <Header>
      <Title>To process integration transactions</Title>
      <Keyword type="header" order="d1e1923301">
         <Level1>Integration mapping scheme</Level1>
         <Level2>process integration transactions</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1923306">
         <Level1>Mapping scheme</Level1>
         <Level2>process integration transactions</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1923311">
         <Level1>Integration transactions</Level1>
         <Level2>to process</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <ProcedureList>
         <ListTitle>To process integration transactions - overview</ListTitle>
         <ListIntro>To process the integration transactions and to create the
		  corresponding entries in the General Ledger consists of the following
		  steps:</ListIntro>
         <ListItemHead>Logging the transaction data.</ListItemHead>
         <ListItem>Of every event in Operations Management, ERP Enterprise automatically logs the
		  logistic data in the Integration Transactions (tfgld482) table and in the
		  Reconciliation Data (tfgld495).</ListItem>
         <ListItemHead>Optionally view the integration transactions.</ListItemHead>
         <ListItem>In the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session, you can view the integration
		  transaction details.</ListItem>
         <ListItemHead>Optionally map individual transactions.</ListItemHead>
         <ListItem>In the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session, you can map individual
		  transactions according to the current mapping scheme or a previous mapping
		  scheme version.</ListItem>
         <ListItemHead>Map the integration transactions.</ListItemHead>
         <ListItem>Use the <GUIRef href="/baanerp/tf/gld/tfgld4281m000" role="session">Map Integration Transactions (tfgld4281m000)</GUIRef> session to start the mapping. Ledger
		  accounts and dimensions are assigned to the transactions.</ListItem>
         <ListItemHead>Solve the mapping errors.</ListItemHead>
         <ListItem>Start the <GUIRef href="/baanerp/tf/gld/tfgld4484m000" role="session">Print Integration Transactions Error Log (tfgld4484m000)</GUIRef> session to print an error
		  report. If mapping errors occurred, create a new version of the mapping scheme
		  in which you solve the errors.</ListItem>
         <ListItemHead>Post the integration transactions</ListItemHead>
         <ListItem>Use the <GUIRef href="/baanerp/tf/gld/tfgld4282m000" role="session">Post Integration Transactions (tfgld4282m000)</GUIRef> session to start the posting.
		  Non-finalized journal entries are created for the integration transactions in
		  the General Ledger. <Emphasis>Note</Emphasis>: Users can only post integration
		  transactions if they belong to an <Link href="/baanerp/tf/glossary/glossary#000461" role="glossary">integration user group</Link>. For details, refer to <Link href="/baanerp/tf/integrations/400021" role="manual">Integration user groups</Link>.</ListItem>
         <ListItemHead>Solve the posting errors.</ListItemHead>
         <ListItem>Start the <GUIRef href="/baanerp/tf/gld/tfgld4484m000" role="session">Print Integration Transactions Error Log (tfgld4484m000)</GUIRef> session to print an error
		  report. Solve the errors and post the integration transactions again.</ListItem>
         <ListItemHead>Finalize the transactions</ListItemHead>
         <ListItem>In the <GUIRef href="/baanerp/tf/gld/tfgld1210m000" role="session">Global Selection of Batches for Finalization (tfgld1210m000)</GUIRef> session or the <GUIRef href="/baanerp/tf/gld/tfgld1111s000" role="session">Attach Batches to Finalization Run (tfgld1111s000)</GUIRef> session, finalize the batch. Final
		  checks are carried out on the non-finalized integration transactions, finalized
		  transactions are created in the General Ledger.</ListItem>
         <ListItemHead>Archive and/or delete the integration
		  transactions.</ListItemHead>
         <ListItem>After the transactions are posted, run the <GUIRef href="/baanerp/tf/gld/tfgld4283m000" role="session">Archive / Delete Integration Elements and Integration Transactions (tfgld4283m000)</GUIRef> session to clear up the database.</ListItem>
      </ProcedureList>
      <Paragraph>These steps are described in detail below.</Paragraph>
      <Paragraph>You can remap <GUIRef href="/baanerp/tf/domains/gld.sint#posted" role="option">Posted</GUIRef> transactions that were mapped incorrectly. ERP Enterprise reverses the posted
		integration transactions and generates a new integration transaction. If the
		mapping elements are still available, you can remap the integration
		transaction, for example, using a new version of the mapping scheme, or you can
		remap the transaction through a <Link href="/baanerp/tf/glossary/glossary#000446" role="glossary">GL code</Link>. For more information, refer to <Link href="/baanerp/tf/integrations/400026" role="manual">To remap integration transactions</Link>.</Paragraph>
      <GeneralSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>For fixed assets transactions, procurement card
			 transactions, and dimension accounting, ERP Enterprise only uses the mapping
			 scheme functionality to map the transactions to ledger accounts and dimensions.
			 These processes do not result in integration transactions and the related
			 transactions are not included when you map and post integration transactions.</Paragraph>
         </Note>
      </GeneralSection>
   </GeneralSection>
   <ProcedureSection>
      <SectionTitle>To process integration transactions</SectionTitle>
      <Steps>
         <Step>
            <StepTitle>Logging the transaction data</StepTitle>
            <Paragraph>When logistic events occur that result in financial
			 postings, ERP Enterprise automatically logs the logistic data such as the order amount, the order
			 number, the quantity, and the business partner, in the Integration Transactions
			 (tfgld482) table. Simultaneously, this data is stored in the Reconciliation
			 Data (tfgld495) table, for inquiries, reporting, and reconciliation purposes.</Paragraph>
            <Paragraph>Based on the transaction date, ERP Enterprise determines the
			 financial period in which the transaction must be posted. This is especially
			 important for the reconciliation process. If the financial period is closed, ERP Enterprise displays an error
			 message. However, in the <GUIRef href="/baanerp/tf/gld/tfgld4150s000" role="session">Integration Parameters (tfgld4150s000)</GUIRef> session, you can select a default <GUIRef href="/baanerp/tf/gld/tfgld4150s000#tfgld450.clha" role="manual">Closed Period Handling</GUIRef> option. For more information, refer to <Link href="/baanerp/tf/integrations/400018" role="manual">Period handling for integration transactions</Link>.</Paragraph>
            <Paragraph>The mapping elements of transactions for which you enter a <Link href="/baanerp/tf/glossary/glossary#000446" role="glossary">GL code</Link> are not logged, as these are not needed to determine the ledger account
			 and dimensions for the transaction.</Paragraph>
         </Step>
         <Step>
            <StepTitle>View the integration transactions</StepTitle>
            <Paragraph>You can use the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session to view the integration
			 transactions. On the various tabs you can view all the details of the
			 integration transactions.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Optionally map and post individual transactions</StepTitle>
            <Paragraph>You can optionally map and post individual transactions, for
			 example, to post a specific transaction or to map an antedated transaction with
			 the mapping scheme version that was active on the transaction date.</Paragraph>
            <List>
               <ListIntro>In the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session, select the transaction and on
				the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu,
				click:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/tf/gld/tfgld4582m000#map.specific.transaction" role="command">Map Specific Transaction</GUIRef>, to map the selected
				transaction according to the currently active mapping scheme.</ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tf/gld/tfgld4582m000#map.with.specific" role="command">Map with Specific Mapping Scheme</GUIRef>, to map a selected transaction according
				to a specific mapping scheme version. You can select any mapping scheme version
				from the <GUIRef href="/baanerp/tf/gld/tfgld4573m100" role="session">Mapping Schemes (tfgld4573m100)</GUIRef> session. If the selected version has not been
				Active, you can only simulate the mapping. If the selected version has been <GUIRef href="" role="manual">Active</GUIRef> at any time, you can simulate the mapping and you can
				actually map the transaction.</ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/tf/gld/tfgld4582m000#post.specific.transaction" role="command">Post Specific Transactions</GUIRef>, to post a selected
				transaction manually.</ListItem>
            </List>
         </Step>
         <Step>
            <StepTitle>Map the integration transactions</StepTitle>
            <Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4281m000" role="session">Map Integration Transactions (tfgld4281m000)</GUIRef> session, select a range of transactions
			 to be mapped.</Paragraph>
            <Paragraph>If you click the <GUIRef href="/baanerp/tf/gld/tfgld4281m000#exec.cont.process" role="command">Map</GUIRef> button, ERP Enterprise assigns ledger
			 accounts and dimensions to the transactions based on the integration mapping
			 scheme and the values of the mapping elements.</Paragraph>
            <Paragraph>ERP Enterprise uses the currently <GUIRef href="" role="manual">Active</GUIRef> mapping scheme version, independent
			 of the transaction dates.</Paragraph>
            <List>
               <ListIntro>You can select transactions with specific statuses for the
				mapping. By default, ERP Enterprise maps transactions that have the following statuses:</ListIntro>
               <ListItemHead>Logged</ListItemHead>
               <ListItem>The transaction data has been logged. Usually this check
				box is selected.</ListItem>
               <ListItemHead>Mapping error</ListItemHead>
               <ListItem>Previous mapping of the transaction has resulted in an
				error message.</ListItem>
               <ListItemHead>Posting error</ListItemHead>
               <ListItem>Previous posting of the transaction has resulted in an
				error message.</ListItem>
            </List>
            <Paragraph>The transactions for which you enter a <Link href="/baanerp/tf/glossary/glossary#000446" role="glossary">GL code</Link> are not mapped, as these can be immediately posted to the ledger
			 account and dimensions of the GL code.</Paragraph>
            <Paragraph>To remap transactions that were previously mapped, select <GUIRef href="/baanerp/tf/domains/gld.ints#mapped" role="option">Mapped</GUIRef> in the <GUIRef href="/baanerp/tf/gld/tfgld4281m000#specific.status" role="manual" Update="No">Status</GUIRef> field. The previous mapping is replaced with the
			 new mapping. For example, if you wish to overrule the individual mapping of
			 transactions performed in the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session, you can use this option.</Paragraph>
            <Paragraph>After the mapping, you can still map individual transactions
			 according to previously active mapping scheme versions. Use the commands on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu of the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session.</Paragraph>
         </Step>
         <Step ID="map.errors">
            <StepTitle>Solve the mapping errors</StepTitle>
            <Paragraph>After mapping the integration transactions, to see whether
			 any errors occurred, you can start the <GUIRef href="/baanerp/tf/gld/tfgld4484m000" role="session">Print Integration Transactions Error Log (tfgld4484m000)</GUIRef> session to display or print an
			 error report.</Paragraph>
            <Paragraph>If mapping errors occurred, create a new version of the
			 mapping scheme in which you solve the errors. Alternatively, in the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session you can manually map individual
			 transactions according to a previously active mapping scheme.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Post the integration transactions</StepTitle>
            <Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4282m000" role="session">Post Integration Transactions (tfgld4282m000)</GUIRef> session, select a range of transactions
			 to be posted.</Paragraph>
            <Paragraph>You can only post integration transactions if you belong to
			 an <Link href="/baanerp/tf/glossary/glossary#000461" role="glossary">integration user group</Link>. For
			 details, refer to <Link href="/baanerp/tf/integrations/400021" role="manual">Integration user groups</Link>.</Paragraph>
            <Paragraph>If you click the <GUIRef href="/baanerp/tf/gld/tfgld4282m000#exec.cont.process" role="command"
                       Update="No">Post</GUIRef> command button, ERP Enterprise creates non-finalized
			 journal entries in the General Ledger. Debit and credit transactions are
			 compressed if this is indicated in the mapping scheme. The batch numbers are
			 assigned according to the setting of the <GUIRef href="/baanerp/tf/gld/tfgld4150s000#tfgld450.htyp" role="manual">Handling of Batch Numbers</GUIRef> parameter in the <GUIRef href="/baanerp/tf/gld/tfgld4150s000" role="session">Integration Parameters (tfgld4150s000)</GUIRef> session.</Paragraph>
            <Paragraph>If you select the <GUIRef href="/baanerp/tf/gld/tfgld4282m000#use.freq" role="manual">Continuous Process Frequency</GUIRef> check box, as long as
			 the session is open ERP Enterprise posts newly mapped transactions in the selected range at regular intervals. You
			 can enter the time in minutes between two runs of the posting process. If you
			 enter zero, the process is not repeated.</Paragraph>
         </Step>
         <Step ID="post.errors">
            <StepTitle>Solve the posting errors</StepTitle>
            <Paragraph>After posting the integration transactions, to see whether
			 any errors occurred, you can start the <GUIRef href="/baanerp/tf/gld/tfgld4484m000" role="session">Print Integration Transactions Error Log (tfgld4484m000)</GUIRef> session to display or print an
			 error report.</Paragraph>
            <List>
               <ListIntro>The following main types of posting errors can
				occur:</ListIntro>
               <ListItem>In a multifinancial company structure, the intercompany
				relations or the intergroup relations are not set up correctly in the <GUIRef href="/baanerp/tf/gld/tfgld0515m000" role="session">Inter-Company Relations (tfgld0515m000)</GUIRef> session and the <GUIRef href="/baanerp/tf/gld/tfgld2501m000" role="session">Intergroup Relations (tfgld2501m000)</GUIRef> session. For example, check that the ledger
				accounts exist.</ListItem>
               <ListItem>The fiscal period corresponding to the transaction date is
				already <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="option">Closed</GUIRef>. To post the transaction, you must set the period
				to <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="option">Open</GUIRef> for General Ledger (GLD) transactions in the <GUIRef href="/baanerp/tf/gld/tfgld0107m000" role="session">Period Status (tfgld0107m000)</GUIRef> session.</ListItem>
               <ListItem>General transaction processing errors, for example, the
				highest free number of a document number series has been reached.</ListItem>
            </List>
            <Paragraph>Solve the errors and post the integration transactions
			 again.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Finalize the transactions</StepTitle>
            <Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld1210m000" role="session">Global Selection of Batches for Finalization (tfgld1210m000)</GUIRef> session or the <GUIRef href="/baanerp/tf/gld/tfgld1111s000" role="session">Attach Batches to Finalization Run (tfgld1111s000)</GUIRef> session, finalize the batch. ERP Enterprise checks whether the
			 transactions of the batch are balanced.</Paragraph>
            <Paragraph>If the debit and the credit side of a transaction must be
			 posted in different financial companies, intercompany transactions are
			 generated. In addition, currency exchange gain and loss amounts are calculated
			 and posted.</Paragraph>
            <Paragraph>The finalized transactions are stored in the General Ledger
			 and the corresponding non-finalized transactions are removed.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Remap posted transactions</StepTitle>
            <Paragraph>Before you archive and delete the integration transactions,
			 you can remap <GUIRef href="/baanerp/tf/domains/gld.sint#posted" role="option">Posted</GUIRef> transactions that were mapped incorrectly. For
			 details, refer to <Link href="/baanerp/tf/integrations/400026" role="manual">To remap integration transactions</Link>.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Archive and/or delete the integration
			 transactions</StepTitle>
            <Paragraph>After the transactions are posted, the integration
			 transactions details are no longer needed. The logistic data required for
			 inquiries, reporting, and reconciliation is stored separately in the
			 Reconciliation Data (tfgld495) table.</Paragraph>
            <Paragraph>A large amount of logged data that is no longer needed can
			 have a negative impact on the performance of the processes that handle
			 integration transactions and reconciliation transactions. To save space and
			 avoid a possible low performance, at regular intervals you can run the <GUIRef href="/baanerp/tf/gld/tfgld4283m000" role="session">Archive / Delete Integration Elements and Integration Transactions (tfgld4283m000)</GUIRef> session which is part of the <GUIRef href="" role="manual">Utilities</GUIRef> of the <GUIRef href="/baanerp/tf/gld" role="module">General Ledger</GUIRef> module.
			 All integration transactions and their <Link href="/baanerp/tf/glossary/glossary#000016" role="glossary">mapping elements</Link> within the selection that have the <GUIRef href="/baanerp/tf/domains/gld.ints#posted" role="option">Posted</GUIRef> status are archived and/or deleted depending on the selected options.</Paragraph>
            <Paragraph>The <Link href="/baanerp/tf/glossary/glossary#000016" role="glossary">mapping elements</Link> reflect logistic data. If the logistic
			 data changes, for example, if item codes or projects expire or you redefine the
			 order types, you cannot at a later stage create a correction integration
			 transaction or remap the integration transactions. In such a situation, you can
			 also archive the mapping elements.</Paragraph>
         </Step>
      </Steps>
   </ProcedureSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400018" role="manual">Period handling for integration transactions</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400000" role="manual">Financial integrations - overview</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>