<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tf/integrations/400018" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Period handling for integration transactions</Title>
		<Keyword><Level1>Integration transactions</Level1>
			<Level2>financial period</Level2>
		</Keyword>
		<Keyword><Level1>Mapping scheme</Level1>
			<Level2>financial period</Level2>
		</Keyword>
		<Keyword><Level1>Financial period</Level1>
			<Level2>of integration transactions</Level2>
		</Keyword>
	</Header>
	<GeneralSection><SectionTitle>Dates</SectionTitle>
		<List><ListIntro>If <Link href="/baanerp/tf/glossary/glossary#000451" role="glossary">Operations Management</Link> transactions are posted to <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, the following types of dates are involved:</ListIntro>
			<ListItemHead>Transaction date</ListItemHead>
			<ListItem>The date you enter when you create the transaction such as a sales order or a warehouse receipt. Usually the transaction date is the current date. Only for backdated and antedated transactions, the transaction date differs from the current date. Internally, the transaction date is registered in <Link href="/baanerp/tc/glossary/glossary#100000" role="glossary">UTC time</Link>.</ListItem>
			<ListItemHead>Transaction entry date</ListItemHead>
			<ListItem>The date you enter when you create the batch. Usually the transaction entry date is the current date. Only for backdated and antedated transactions, the transaction entry date differs from the current date. Internally, the transaction entry date is registered in local time.</ListItem>
			<ListItemHead>Document date</ListItemHead>
			<ListItem>The transaction date in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. The document date is always registered in local time. For invoices, the document date is the invoice date. Usually the document date is the same date as the transaction date, except if you manually enter a different transaction date in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> or if the UTC time and the local time differ by a day. The document date is not used for integration transactions.</ListItem>
			<ListItemHead>Creation date</ListItemHead>
			<ListItem>The date and time when the transaction is created. For backdated and antedated transactions, the creation date differs from the transaction date. The creation date is only used for integration transactions.</ListItem>
			<ListItemHead>Posting date</ListItemHead>
			<ListItem>The date and time (local time) when the transaction is posted.</ListItem>
		</List>
	</GeneralSection>
	<GeneralSection><List><ListTitle>Periods</ListTitle>
			<ListIntro>For every integration transaction, the following financial periods are recorded:</ListIntro>
			<ListItem>Fiscal year and Fiscal period.</ListItem>
			<ListItem>Reporting year and Reporting period.</ListItem>
			<ListItem>Tax year and Tax period.</ListItem>
		</List>
		<Paragraph>For details about the period types, refer to <Link href="/baanerp/tf/onlinemanual/000014" role="manual">To use periods</Link>.</Paragraph>
		<Paragraph>Usually, the financial transactions are posted in the financial periods that correspond with the transaction date. The posting date and the document date are in the same period.</Paragraph>
		<Paragraph>To log the integration transactions, the financial period status must be <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef>. Usually, if the transaction date is the current date, the financial periods are <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef>. However, if a transaction is antedated or if the transaction date is near the end of a financial period, the period can be already <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> when the related financial transaction is posted.</Paragraph>
		<Paragraph>If you create an integration transaction, the transaction is logged. Usually this is the moment when you approve an order or invoice. Because the financial periods of the postings are included in the logged information, SSA ERP checks the period status before the transaction is logged. If the period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>, the transaction cannot be logged. The user cannot save the approved order or invoice.</Paragraph>
		<Paragraph>You can select the period type of which SSA ERP checks the status to detect whether the period is <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> and the integration transaction can be logged.</Paragraph>
		<List><ListIntro>You can select the following period types:</ListIntro>
			<ListItem><GUIRef href="/baanerp/tf/domains/gld.pech#int" role="enum">INT</GUIRef> for integration transactions.</ListItem>
			<ListItem><GUIRef href="/baanerp/tf/domains/gld.pech#acp" role="enum">ACP</GUIRef> for accounts payable transactions.</ListItem>
			<ListItem><GUIRef href="/baanerp/tf/domains/gld.pech#acr" role="enum">ACR</GUIRef> for accounts receivable transactions.</ListItem>
			<ListItem><GUIRef href="/baanerp/tf/domains/gld.pech#gld" role="enum">GLD</GUIRef> for general ledger transactions.</ListItem>
		</List>
		<Paragraph>For example, if you select <GUIRef href="/baanerp/tf/domains/gld.pech#acp" role="enum">ACP</GUIRef>, you cannot post an integration transaction if the <GUIRef href="/baanerp/tf/domains/gld.pech#acp" role="enum">ACP</GUIRef> period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>, even if the <GUIRef href="/baanerp/tf/domains/gld.pech#int" role="enum">INT</GUIRef> period is still <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef>.</Paragraph>
		<Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4150s000" role="session">Integration Parameters (tfgld4150s000)</GUIRef> session, you can select the default period type. In the <GUIRef href="/baanerp/tf/gld/tfgld4579m000" role="session">Period Handling by Integration Document Type (tfgld4579m000)</GUIRef> session, you can select the period type for individual integration document types.</Paragraph>
		<Paragraph>It is usually correct to check the <GUIRef href="/baanerp/tf/domains/gld.pech#int" role="enum">INT</GUIRef> period. In exceptional situations, you can select the other period types.</Paragraph>
		<GeneralSection><SectionTitle>If the period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef></SectionTitle>
			<Paragraph>If the period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>, SSA ERP tries to post the transaction according to the <GUIRef href="/baanerp/tf/domains/gld.clha" role="domain">Closed Period Handling</GUIRef> option that applies to the integration transaction. In the <GUIRef href="/baanerp/tf/gld/tfgld4150s000" role="session">Integration Parameters (tfgld4150s000)</GUIRef> session, you can select the default <GUIRef href="/baanerp/tf/gld/tfgld4150s000#tfgld450.clha" role="formfield">Closed Period Handling</GUIRef> option. In the <GUIRef href="/baanerp/tf/gld/tfgld4579m000" role="session">Period Handling by Integration Document Type (tfgld4579m000)</GUIRef> session, you can select the closed period handling option for specific integration document types.</Paragraph>
			<List><ListIntro>You can select the following <GUIRef href="/baanerp/tf/domains/gld.clha" role="domain">Closed Period Handling</GUIRef> options:</ListIntro>
				<ListItemHead><GUIRef href="/baanerp/tf/domains/gld.clha#post.curr.per" role="enum">Post to current period</GUIRef>
				</ListItemHead>
				<ListItem><Paragraph>SSA ERP posts the transaction to the current financial period.</Paragraph>
				</ListItem>
				<ListItemHead><GUIRef href="/baanerp/tf/domains/gld.clha#post.next.per" role="enum">Post to next open period</GUIRef>
				</ListItemHead>
				<ListItem><Paragraph>SSA ERP posts the transaction to the next open period.</Paragraph>
				</ListItem>
				<ListItemHead><GUIRef href="/baanerp/tf/domains/gld.clha#except.handling" role="enum">Exception handling</GUIRef>
				</ListItemHead>
				<ListItem><Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4585m000" role="session">Requested Exceptions for Integration Transactions (tfgld4585m000)</GUIRef> session, enter a request to post integration transactions to specific financial periods of which the status is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>.</Paragraph>
					<Paragraph>After an authorized user approves the request, the transaction can be logged and posted. You do not need to set a <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> period to <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef>. However, the corresponding <GUIRef href="/baanerp/tf/domains/gld.pech#gld" role="enum">GLD</GUIRef> period must be <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> at the time when you post the integration transaction. If required, you can manually set the <GUIRef href="/baanerp/tf/domains/gld.pech#gld" role="enum">GLD</GUIRef> period to <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> in the <GUIRef href="/baanerp/tf/gld/tfgld0107m000" role="session">Period Status (tfgld0107m000)</GUIRef> session.</Paragraph>
				</ListItem>
				<ListItemHead><GUIRef href="/baanerp/tf/domains/gld.clha#param.default" role="enum">Parameters' default</GUIRef>
				</ListItemHead>
				<ListItem>SSA ERP uses the default <GUIRef href="/baanerp/tf/gld/tfgld4150s000#tfgld450.clha" role="formfield">Closed Period Handling</GUIRef> option that you selected in the <GUIRef href="/baanerp/tf/gld/tfgld4150s000" role="session">Integration Parameters (tfgld4150s000)</GUIRef>
				</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>Requests for exceptions</SectionTitle>
			<Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4585m000" role="session">Requested Exceptions for Integration Transactions (tfgld4585m000)</GUIRef> session, enter a request to log and post integration transactions to specific financial periods.</Paragraph>
			<Paragraph>You can enter the fiscal year and period, the reporting year and period, and/or the tax year and period to which the integration transaction must be posted. Only the fields that correspond to a <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> period are enabled.</Paragraph>
			<Paragraph>By default, SSA ERP displays the year and period that corresponds with the transaction date of the integration transaction.</Paragraph>
			<List><ListIntro>You can perform one of the following actions:</ListIntro>
				<ListItem>To create a request for posting the integration transaction to the <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> period, use the default value.</ListItem>
				<ListItem>To create a request for posting the integration transaction to a different period, enter the period number. The new period can be <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> or <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>.</ListItem>
			</List>
			<Paragraph>If the transaction still cannot be logged, SSA ERP displays an error message on the user’s screen when the transaction is created. For example, if the <GUIRef href="/baanerp/tf/domains/gld.clha" role="domain">Closed Period Handling</GUIRef> option is <GUIRef href="/baanerp/tf/domains/gld.clha#post.curr.per" role="enum">Post to current period</GUIRef> and the current period is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>, SSA ERP cannot log the transaction. To solve the problem, you can change the transaction date to a date in the next <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef> fiscal period.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>The employees who have permission to run the <GUIRef href="/baanerp/tf/gld/tfgld4585m100" role="session">Approve Requested Exceptions for Integration Transactions (tfgld4585m100)</GUIRef> session are authorized to approve the requests.</Paragraph>
				<Paragraph>You cannot post transactions to a financial period that has the <GUIRef href="/baanerp/tf/domains/gld.sper#finally.closed" role="enum">Finally Closed</GUIRef> status. Periods should only be set to <GUIRef href="/baanerp/tf/domains/gld.sper#finally.closed" role="enum">Finally Closed</GUIRef> when the financial year is closed.</Paragraph>
			</Note>
			<ExampleSection><SectionTitle>Example</SectionTitle>
				<Paragraph>For example, the integration transaction was created in period two of the fiscal year 2005.</Paragraph>
				<List><ListIntro>For the period type selected for the integration document type, the periods have the following status:</ListIntro>
					<ListItem>Fiscal period 2005/2 is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>
					</ListItem>
					<ListItem>Tax period 2005/2 is <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef>
					</ListItem>
					<ListItem>Reporting period 2005/2 is still <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="enum">Open</GUIRef>
					</ListItem>
				</List>
				<Paragraph>SSA ERP posts the integration transaction to Reporting period 2005/2. You cannot change this setting. For the Fiscal period and the Tax period, you can enter a period number.</Paragraph>
				<Paragraph>If you accept the default value 2005/2, SSA ERP creates a request to post the transaction to a <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="enum">Closed</GUIRef> period.</Paragraph>
				<Paragraph>If you enter a different number, for example, 2005/3, SSA ERP creates a request to post the transaction to a period that does not correspond with the transaction date.</Paragraph>
			</ExampleSection>
		</GeneralSection>
		<GeneralSection><SectionTitle>Period handling exceptions in reconciliation</SectionTitle>
			<Paragraph>If you post the transaction to the next <GUIRef href="" role="manual">Open</GUIRef> fiscal period, the transaction date is outside the fiscal period to which the transaction is posted. This makes matching of logistic reports and financial reports more complex. You can print a report of the requests for exceptions in the <GUIRef href="/baanerp/tf/gld/tfgld4485m000" role="session">Print Next-open-period Transactions (tfgld4485m000)</GUIRef> session, and use this during reconciliation.</Paragraph>
			<Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4495m000" role="session">Print Reconciliation Data (tfgld4495m000)</GUIRef> session, you can select the <GUIRef href="/baanerp/tf/gld/tfgld4495m000#anted.trans" role="formfield">Print Backdated Transactions</GUIRef> check box to print the reconciliation report for such transactions.</Paragraph>
			<Paragraph>For the <GUIRef href="" role="manual">Invoice Accrual 3</GUIRef> reconciliation group that represents the Goods Received not Invoiced (GRNI), if you print reconciliation reports with the <GUIRef href="/baanerp/tf/gld/tfgld4495m200" role="session">Checklist Reconciliation Goods Received Not Invoiced (tfgld4495m200)</GUIRef> session, the financial transaction is reported in the fiscal period of the document date instead of the posting date.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>In general, backdated transactions make the reconciliation process more complex. To avoid the generation of errors when the currency differences and rounding differences are calculated, logging antedated transactions with a transaction date earlier than the most recent archiving date of the reconciliation data is not permitted for the following reconciliation areas:</ListIntro>
				<ListItem>Inventory.</ListItem>
				<ListItem>Consignment Inventory.</ListItem>
				<ListItem>Assembly Line WIP.</ListItem>
			</List>
		</Note>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>If you received goods late onJanuary 31 and you register the receipt on February 1 but with a transaction date of January 31, the following situation occurs. The posting date and the document date differ.</Paragraph>
			<TABLE border="1"><TBODY><TR><TD></TD>
						<TD width="221">Fiscal period 101/01 – 01/31</TD>
						<TD width="217">Fiscal period 202/01 – 02/28</TD>
					</TR>
					<TR><TD>Operations Management transaction</TD>
						<TD width="221">Receipt: Transaction date = 01/30 Document date = 01/30</TD>
						<TD width="217"></TD>
					</TR>
					<TR><TD>Financial transaction</TD>
						<TD width="221"></TD>
						<TD width="217">Receipt: Posting date = 02/01 Backdated: Document date = 01/30</TD>
					</TR>
				</TBODY>
			</TABLE>
		</ExampleSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/tf/integrations/400012" role="manual">To process integration transactions</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tf/integrations/400034" role="manual">The reconciliation process</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
