| # Importing a component model in XML format To import application information into a component release you have defined, use the XML Import Component Model data. To import the application information into the component release, the application information must be structured in the following XML import scheme: Example ERP Enterprise
    <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">Quoations</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 SCS planner
    <applications>
     <application>
     <attr name="application.id">Demand Plan</attr>
     <attr name="description">View and edit demand orders and dependent demand.</attr>
     </application>
    <application>
    <attr name="application.id">Order Promising</attr>
     <attr name="description">Lets you view the quantity available to promise (ATP) over time for any item or confirm that there is enough to cover a demand.</attr>
     </application>
    <application>
    <attr name="application.id">Items</attr>
    <attr name="description">Displays all item-related information including routing, supply method, and inventory.</attr>
     </application>
     <application>
    <attr name="application.id">Item Groups</attr>
     <attr name="description">Allows the definition of grouping by Items.</attr>
    </application>
     <application>
     <attr name="application.id">Site/Warehouse</attr>
    <attr name="description">View and control site properties.</attr>
     </application>
     <application>
     <attr name="application.id">Distribution Network</attr>
     <attr name="description">Distribution Network</attr>
    </application>
    </applications>
Example Microsoft Outlook
    <applications>
     <application>
    <atr name="id">New Message</atr>
    <atr name="main">true</atr>
    <atr name="text">Application 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 sub applications can be nested, as shown in the above example. For an application to have sub applications, it must be a main application. The application description can be given in multiple languages. The language codes must be consistent with the ERP Enterprise standards. See Language codes. |