<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tg/onlinemanual/000053" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Import, export and conversion of components</Title>
		<Keyword><Level1>import components</Level1>
		</Keyword>
		<Keyword><Level1>export components</Level1>
		</Keyword>
		<Keyword><Level1>conversion of component applications</Level1>
		</Keyword>
	</Header>
	<GeneralSection><List><ListIntro>You can move component data, for example, between companies or systems via the following:</ListIntro>
			<ListItem><Link href="#A" role="internal">To export component</Link>
			</ListItem>
			<ListItem><Link href="#B" role="internal">To import component</Link>
			</ListItem>
		</List>
		<List><ListIntro>You can import application information, other than ERP sessions (ERP sessions can be imported from the ERP session tables), via the following:</ListIntro>
			<ListItem><Link href="#C" role="internal">To import applications other than SSA ERP</Link>
			</ListItem>
		</List>
		<List><ListIntro>The activities of type application and support applications within DEM models use applications of a component release. When you want to migrate from one component release to another, and application codes differ between the two component releases, it is a lot of work to manually find and apply the changes in the DEM models. This is why an application conversion table between component releases must be administered.</ListIntro>
			<ListItem><Link href="#D" role="internal">To convert applications from one component to another</Link>
			</ListItem>
		</List>
		<List><ListIntro>Reference in activities, <Link href="/baanerp/tg/glossary/glossary#000308" role="glossary">sub-applications</Link> and <Link href="/baanerp/tg/glossary/glossary#000280" role="glossary">support applications</Link> to a <Link href="/baanerp/tg/glossary/glossary#000213" role="glossary">component</Link> and <Link href="/baanerp/tg/glossary/glossary#000216" role="glossary">component release</Link> can be converted to another component and component release. This may be necessary when a business model is exported from one company to another where the name of the component and component release is not the same.</ListIntro>
			<ListItem><Link href="#E" role="internal">To merge component and release codes</Link>
			</ListItem>
		</List>
		<GeneralSection ID="A"><SectionTitle>To export component</SectionTitle>
			<Paragraph>Via the <Link href="/baanerp/tg/brg/tgbrg5257m000" role="session">Export Component Model Data (tgbrg5257m000)</Link> session you can export component information from your current company.</Paragraph>
		</GeneralSection>
		<GeneralSection ID="B"><SectionTitle>To import component</SectionTitle>
			<Paragraph>Via the <Link href="/baanerp/tg/brg/tgbrg5256m000" role="session">Import Component Model Data (tgbrg5256m000)</Link> session you can import component information into your current company.</Paragraph>
		</GeneralSection>
		<GeneralSection ID="C"><SectionTitle>To import applications other than SSA ERP</SectionTitle>
			<Paragraph>Via the <Link href="/baanerp/tg/brg/tgbrg5254m000" role="session">XML Import Component Model Data (tgbrg5254m000)</Link> session you can import application information into a component you have defined.</Paragraph>
			<Paragraph>To be able to import the application information into the component the application information must be structured in a XML format.</Paragraph>
			<GeneralSection><SectionTitle>The XML import scheme:</SectionTitle>
				<Formula><Paragraph UserLevel="Novice" UserType="Taskuser">
Example ERP:

&lt;applications&gt;
        &lt;application&gt;
                &lt;atr name="id"&gt;tdsls1500m000&lt;/atr&gt;
                &lt;atr name="main"&gt;true&lt;/atr&gt;
                &lt;atr name="text"&gt;This application is used for viewing
Quotations&lt;/atr&gt;
                &lt;atr name="1"&gt;Prijsopgaven&lt;/atr&gt;
                &lt;atr name="2"&gt;Quotations&lt;/atr&gt;
                &lt;subapplications&gt;
                        &lt;subapplication&gt;
                                &lt;atr name="id"&gt;tdsls1100m000&lt;/atr&gt;
                        &lt;/subapplication&gt;
                        &lt;subapplication&gt;
                                &lt;atr name="id"&gt;tdsls1501m000&lt;/atr&gt;
                        &lt;/subapplication&gt;
                        &lt;subapplication&gt;
                                &lt;atr name="id"&gt;tdsls1550m000&lt;/atr&gt;
                        &lt;/subapplication&gt;
                        &lt;subapplication&gt;
                                &lt;atr name="id"&gt;tdsls1205s000&lt;/atr&gt;
                        &lt;/subapplication&gt;
                        &lt;subapplication&gt;
                                &lt;atr name="id"&gt;tdsls1210m000&lt;/atr&gt;
                        &lt;/subapplication&gt;
                &lt;/subapplications&gt;
        &lt;/application&gt;
        &lt;application&gt;
                &lt;atr name="id"&gt;tdsls1100m000&lt;/atr&gt;
                &lt;atr name="main"&gt;false&lt;/atr&gt;
                &lt;atr name="text"&gt;This application is used for updating
Quotations&lt;/atr&gt;
                &lt;atr name="1"&gt;Prijsopgaven&lt;/atr&gt;
                &lt;atr name="2"&gt;Quotations&lt;/atr&gt;
        &lt;/application&gt;
        ...
&lt;/applications&gt;

Example Ms Outlook:

&lt;applications&gt;
        &lt;application&gt;
                &lt;atr name="id"&gt;New Message&lt;/atr&gt;
                &lt;atr name="main"&gt;true&lt;/atr&gt;
                &lt;atr name="text"&gt;This application is used for sending
e-mail around the world&lt;/atr&gt;
                &lt;atr name="2"&gt;New Message&lt;/atr&gt;
                &lt;atr name="argument"&gt;/c IPM.note&lt;/atr&gt;
        &lt;/application&gt;
&lt;/applications&gt;
</Paragraph>
				</Formula>
				<Paragraph>The subapplications can be nested as shown in the example. For an application to have subapplications, it must be a main application.</Paragraph>
				<Paragraph>The application description can be given in multiple languages. The language codes must be consistent with ERP standards. These language codes are:</Paragraph>
			</GeneralSection>
			<GeneralSection><SectionTitle>A-languages</SectionTitle>
				<TABLE border="1"><TBODY><TR><TD>2</TD>
							<TD>US English</TD>
						</TR>
						<TR><TD>1</TD>
							<TD>Dutch</TD>
						</TR>
						<TR><TD>3</TD>
							<TD>German</TD>
						</TR>
						<TR><TD>j</TD>
							<TD>Japanese</TD>
						</TR>
					</TBODY>
				</TABLE>
			</GeneralSection>
			<GeneralSection><SectionTitle>B-languages</SectionTitle>
				<TABLE border="1"><TBODY><TR><TD>4</TD>
							<TD>French</TD>
						</TR>
						<TR><TD>5</TD>
							<TD>Spanish</TD>
						</TR>
						<TR><TD>6</TD>
							<TD>Italian</TD>
						</TR>
						<TR><TD>7</TD>
							<TD>Danish</TD>
						</TR>
						<TR><TD>8</TD>
							<TD>Norwegian</TD>
						</TR>
						<TR><TD>9</TD>
							<TD>Swedish</TD>
						</TR>
						<TR><TD>P</TD>
							<TD>Portuguese (European)</TD>
						</TR>
						<TR><TD>p</TD>
							<TD>Portuguese (Brazilian)</TD>
						</TR>
						<TR><TD>f</TD>
							<TD>Finnish</TD>
						</TR>
						<TR><TD>n</TD>
							<TD>Chinese Traditional</TD>
						</TR>
						<TR><TD>o</TD>
							<TD>Chinese Simplified</TD>
						</TR>
						<TR><TD>k</TD>
							<TD>Korean</TD>
						</TR>
					</TBODY>
				</TABLE>
			</GeneralSection>
			<GeneralSection><SectionTitle>C-languages</SectionTitle>
				<TABLE border="1"><TBODY><TR><TD>a</TD>
							<TD>Arabic</TD>
						</TR>
						<TR><TD>b</TD>
							<TD>Bulgarian</TD>
						</TR>
						<TR><TD>c</TD>
							<TD>Catalan</TD>
						</TR>
						<TR><TD>d</TD>
							<TD>Polish</TD>
						</TR>
						<TR><TD>e</TD>
							<TD>Elladi (Greek)</TD>
						</TR>
						<TR><TD>E</TD>
							<TD>Estonian</TD>
						</TR>
						<TR><TD>h</TD>
							<TD>Hebrew</TD>
						</TR>
						<TR><TD>H</TD>
							<TD>Hrvatski (Croat)</TD>
						</TR>
						<TR><TD>L</TD>
							<TD>Latvian</TD>
						</TR>
						<TR><TD>M</TD>
							<TD>Magyar (Hungarian)</TD>
						</TR>
						<TR><TD>q</TD>
							<TD>Canadian French</TD>
						</TR>
						<TR><TD>r</TD>
							<TD>Romanian</TD>
						</TR>
						<TR><TD>R</TD>
							<TD>Russian</TD>
						</TR>
						<TR><TD>s</TD>
							<TD>Slovenian</TD>
						</TR>
						<TR><TD>t</TD>
							<TD>Czech</TD>
						</TR>
						<TR><TD>T</TD>
							<TD>Turkish</TD>
						</TR>
						<TR><TD>v</TD>
							<TD>Lithuanian</TD>
						</TR>
					</TBODY>
				</TABLE>
			</GeneralSection>
			<GeneralSection ID="D"><SectionTitle>To convert applications from one component to another</SectionTitle>
				<Paragraph>First, to be able to convert from one component release to another you need to administer a conversion table via the <Link href="/baanerp/tg/brg/tgbrg5150m000" role="session">Conversion of Applications (tgbrg5150m000)</Link> session.</Paragraph>
				<Paragraph>Then, via the <Link href="/baanerp/tg/brg/tgbrg5251m000" role="session">Convert Used Applications (tgbrg5251m000)</Link> session you can convert the applications that are used in support applications or activities of type application.</Paragraph>
			</GeneralSection>
			<GeneralSection ID="E"><SectionTitle>To merge component and release codes</SectionTitle>
				<Paragraph>Via the <Link href="/baanerp/tg/brg/tgbrg5220m000" role="session">Rename Cmp. &amp; Release Codes in Activities and Supp. App's (tgbrg5220m000)</Link> session you can change the component and component release that is used in activities, sub-applications and support applications. It is assumed that both components contain the same applications because of the references to these applications. If not a report is generated.</Paragraph>
			</GeneralSection>
		</GeneralSection>
	</GeneralSection>
</ManualTopic>
