<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/bc/ttf/bcttf0105m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Ledger Mapping (bcttf0105m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to view the additional fields from Baan IVc (= elements in ERP LN 6.1 ) that are used to define the <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.leac" role="formfield">Ledger Account</GUIRef>. This session can also be used to change the <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.leac" role="formfield">Ledger Account</GUIRef> that will be used in the financial mapping scheme. The <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.leac" role="formfield">Ledger Account</GUIRef> can be changed on each view. Through view “Reconciliation Group, Companies, Priority, Sequence, To be Used” it is possible to change the indicator <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef>.</Paragraph>
			<Paragraph>At the first form the data about the originating bcttf020.tror and <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.fitr" role="formfield">Financial Transaction</GUIRef> is visible. At the next forms the elements (i.e. Item and Warehouse) are visible that are used to determine the <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.leac" role="formfield">Ledger Account</GUIRef>.</Paragraph>
			<Paragraph>This maintain session prepares the input for session <GUIRef href="/baanerp/bc/ttf/bcttf0201m000" role="session">Migrate Mapping Scheme (bcttf0201m000)</GUIRef>. Dependent on the filled additional fields of Baan IVc, the element groups and the elements by element groups of ledger account mapping are generated.</Paragraph>
		</AimSection>
		<GeneralSection><SectionTitle>Preparation</SectionTitle>
			<Paragraph>Not applicable.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Execution</SectionTitle>
			<Paragraph>It is strongly advised to start this session to judge the ledger accounts and the indication ‘To be Used’ before running session <GUIRef href="/baanerp/bc/ttf/bcttf0201m000" role="session">Migrate Mapping Scheme (bcttf0201m000)</GUIRef>.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Process logic</SectionTitle>
			<Paragraph>If this session is started for the first time then the data from interim tables Ledger Mapping Base (bcttf001) and Ledger Mapping (Project and Service) (bcttf002) is copied to table Ledger Mapping (bcttf005). First data of table Ledger Mapping (Project and Service) (bcttf002) is copied to table Ledger Mapping Base (bcttf001). Based on the table Ledger Mapping Base (bcttf001) the fields <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.prio" role="formfield">Priority</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.sern" role="formfield">Sequence</GUIRef> are filled without gaps. Lines with the same <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.prio" role="formfield">Priority</GUIRef> having other elements will get a new <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.sern" role="formfield">Sequence</GUIRef>. This is done according to the similar functionality used in the integration mapping scheme.</Paragraph>
			<Paragraph>Per reconciliation group, companies, <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.prio" role="formfield">Priority</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.sern" role="formfield">Sequence</GUIRef> one line will be flagged with <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef> = Yes. The other lines (flagged with <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef> = No) of the same group have overlapping values in the elements. It is mandatory that only one line in the group be flagged with Yes. If the indicator <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef> of another line is manually changed into Yes, the old indicator ‘Yes’ is switched into ‘No’.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Note that no overlapping values are allowed in the elements of one reconciliation group, companies, <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.prio" role="formfield">Priority</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.sern" role="formfield">Sequence</GUIRef> because the debit postings and credit postings must result in the same ledger account. For example purchase order / receipt books debit on ledger account ‘Interim Transit’ and warehouse receipt / receipt books credit on the same account. Only one ‘set of elements’ and one ledger account must be used to generate the mapping. Therefore (through <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef> ) a choice is made between the different financial transactions that are related to each other. Session <GUIRef href="/baanerp/bc/ttf/bcttf0201m000" role="session">Migrate Mapping Scheme (bcttf0201m000)</GUIRef> generates the same elements for the reconciliation groups that must be ‘cleared’. The generated debit and credit mapping will contain the same elements (=elements of Baan IVc, for example “Item” and “Item Group”).</Paragraph>
				<Paragraph>Dependent on the reconciliation group the elements that can be used in ERP LN 6.1, are marked as ‘Yes’. Some elements can be filled with data from Baan IVc but can be marked with ‘No’ if this element is not longer available in ERP LN 6.1.</Paragraph>
				<Paragraph>In session <GUIRef href="/baanerp/bc/ttf/bcttf0201m000" role="session">Migrate Mapping Scheme (bcttf0201m000)</GUIRef> the lines with indicator <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef> = ‘Yes’ are selected to fill the integration mapping scheme. The other lines with <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.used" role="formfield">To be Used</GUIRef> = ‘No’ are ignored.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection><SectionTitle>Duration</SectionTitle>
			<Paragraph>Warning: Execution of this session takes some time if it is started for the first time. The next time it will be faster.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Restart</SectionTitle>
			<Paragraph>Not applicable.</Paragraph>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfgld0004" role="manual">To migrate the Integration Mapping Scheme (Overview) (tfgld0004)</Link>
			</RelTopic>
			<RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfgld0001" role="manual">To migrate ledger accounts to integration mapping scheme (tfgld0001)</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldGroup><Title>Ledger Mapping</Title>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Reconciliation Group</Title>
				</Header>
				<FuncDesc>The reconciliation group is determined based on the <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.tror" role="formfield">Transaction Origin</GUIRef> and <GUIRef href="/baanerp/bc/ttf/bcttf0105m000#bcttf005.fitr" role="formfield">Financial Transaction</GUIRef> where the mapping data is defined.</FuncDesc>
				<RelatedTopics><SectionTitle>Related topics</SectionTitle>
					<RelTopic>General Migration Topics: <Link href="/baanerp/baaniv/tech/general/GTtfgld0001" role="manual">To migrate ledger accounts to integration mapping scheme (tfgld0001)</Link>
					</RelTopic>
				</RelatedTopics>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Logistic Company</Title>
				</Header>
				<FuncDesc>The logistic company for which the mapping will be used. If this field is filled with zero, then the mapping is applicable for all logistic companies.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Financial Company</Title>
				</Header>
				<FuncDesc>The financial company for which the mapping will be used. If this field is filled with zero, then the mapping is applicable for all financial companies.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Priority</Title>
				</Header>
				<FuncDesc>The priority of the mapping. A low number is found first in the mapping process.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Sequence</Title>
				</Header>
				<FuncDesc>The sequence of the mapping is used to define different mappings (not overlapping within one priority).</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Transaction Origin</Title>
				</Header>
				<FuncDesc>The origin of the transaction for which the mapping will be used. Note that the values of this field are taken over from Baan IVc. In ERP LN 6.1 other values are applicable for this field.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Financial Transaction</Title>
				</Header>
				<FuncDesc>The financial transaction for which the mapping will be used. Note that the values of this field are taken over from Baan IVc. In ERP LN 6.1 other values are applicable for this field.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Additional Type</Title>
				</Header>
				<FuncDesc>This field contains an additional value to separate a mapping within one combination of transaction origin and financial transaction. The first 8 values of this field are taken over 1:1 from Baan IVc (“Invoice Totals”, “Late Payment Surcharge”, “Order Discount”, “Material Costs”, “Operation Costs”, “Revenues”, “Rebate”, “Commission”). The other values are new defined ones for example to separate between transactions that are split in ERP LN 6.1.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Debit/Credit</Title>
				</Header>
				<FuncDesc>The indicator whether the mapping is used for the debit or for the credit side of the financial transaction.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To be used</Title>
				</Header>
				<FuncDesc>This flag indicates whether the line originating from Baan IVc will be used during generation of the mapping scheme.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Ledger Account</Title>
				</Header>
				<FuncDesc>This ledger account is used to map the financial transactions that originate from the several packages.</FuncDesc>
			</FieldHelp>
		</FieldGroup>
		<FieldGroup><Title>General</Title>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Financial B.P. Group (A/P)</Title>
				</Header>
				<FuncDesc>This element is filled with the supplier group of Baan IVc. The ‘Yes/No’ flag indicates whether this element is available in ERP LN 6.1. Also a From and a To value is show. Note that for elements that are not used for mapping, the minimum and the maximum value are filled.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Financial B.P. Group (A/R)</Title>
				</Header>
				<FuncDesc>The financial business partner group (accounts receivable) is show here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Warehouse</Title>
				</Header>
				<FuncDesc>The warehouse element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item</Title>
				</Header>
				<FuncDesc>The item element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item Group</Title>
				</Header>
				<FuncDesc>The Item Group element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Project Package Linked</Title>
				</Header>
				<FuncDesc>The Project Package Linked element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Project</Title>
				</Header>
				<FuncDesc>The Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Main Project Package Linked</Title>
				</Header>
				<FuncDesc>The Main Project Package Linked element is shown here. Note that this field indicates whether a mapping is applicable for PCS or for SSA ERP Project or for all types of projects.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Main Project</Title>
				</Header>
				<FuncDesc>The Main Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item Cost Component</Title>
				</Header>
				<FuncDesc>The Item Cost Component element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost Component Type</Title>
				</Header>
				<FuncDesc>The Cost Component Type element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Country</Title>
				</Header>
				<FuncDesc>The Country element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Reason Code</Title>
				</Header>
				<FuncDesc>The Reason Code element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Transaction Type</Title>
				</Header>
				<FuncDesc>The Transaction Type element is shown here.</FuncDesc>
			</FieldHelp>
		</FieldGroup>
		<FieldGroup><Title>TP Project</Title>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost Component (TP)</Title>
				</Header>
				<FuncDesc>The cost component for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost Type (TP)</Title>
				</Header>
				<FuncDesc>The cost type for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Task</Title>
				</Header>
				<FuncDesc>The task for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Equipment</Title>
				</Header>
				<FuncDesc>The equipment for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Subcontracting</Title>
				</Header>
				<FuncDesc>The subcontracting for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Sundry Cost</Title>
				</Header>
				<FuncDesc>The sundry cost for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Result Type</Title>
				</Header>
				<FuncDesc>The result type for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Contract Execution</Title>
				</Header>
				<FuncDesc>The contract execution for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Category</Title>
				</Header>
				<FuncDesc>The category for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Agreement Type</Title>
				</Header>
				<FuncDesc>The agreement type for SSA ERP Project element is shown here.</FuncDesc>
			</FieldHelp>
		</FieldGroup>
		<FieldGroup><Title>Service</Title>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Service Contract Type</Title>
				</Header>
				<FuncDesc>The service contract type for SSA ERP Service element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost Type (TS)</Title>
				</Header>
				<FuncDesc>The cost type for SSA ERP Service element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost Type Group</Title>
				</Header>
				<FuncDesc>The cost type group for SSA ERP Service element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Cost Analysis Type</Title>
				</Header>
				<FuncDesc>The cost analysis type for SSA ERP Service element is shown here.</FuncDesc>
			</FieldHelp>
		</FieldGroup>
		<FieldGroup><Title>Commissions and Rebates</Title>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Customer</Title>
				</Header>
				<FuncDesc>The cost analysis type for SSA ERP Commission and Rebated element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Relation</Title>
				</Header>
				<FuncDesc>The relation for SSA ERP Commission and Rebated element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Relation Type</Title>
				</Header>
				<FuncDesc>The relation type for SSA ERP Commission and Rebated element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Agreement Group</Title>
				</Header>
				<FuncDesc>The agreement group for SSA ERP Commission and Rebated element is shown here.</FuncDesc>
			</FieldHelp>
			<FieldHelp><Header>
					<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Commission/Rebate Group</Title>
				</Header>
				<FuncDesc>The commission or rebate group for SSA ERP Commission and Rebated element is shown here.</FuncDesc>
			</FieldHelp>
		</FieldGroup>
	</Fields>
</Session>
