| # Import, export and conversion of components You can move component data, for example, between companies or systems via the following: To export component To import component You can import application information, other than ERP sessions (ERP sessions can be imported from the ERP session tables), via the following: To import applications other than LN 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. To convert applications from one component to another Reference in activities, sub-applications and support applications to a component and component release 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. To merge component and release codes To export component Via the Export Component Model Data (tgbrg5257m000) session you can export component information from your current company. To import component Via the Import Component Model Data (tgbrg5256m000) session you can import component information into your current company. To import applications other than LN Via the XML Import Component Model Data (tgbrg5254m000) session you can import application information into a component you have defined. To be able to import the application information into the component the application information must be structured in a XML format. The XML import scheme:
    Example ERP:

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

    Example Ms Outlook:

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