Application Import data allows for importing selected data from the system knowledge store, for example as an .xml file, with the use of a service called Business Integration Service (BIS). Such data can be exported from the system to a file with the use of Export data application, and then, after applying changes, imported to the same or another (e.g., newer) system.
This article contains procedures for using the Import data application in the context of the data regarding kits.
General information
In the Comarch ERP Enterprise system, kits allow for combining items.
There are two types of data exchange:
- data exchange between existing Comarch ERP Enterprise systems
- data import from an earlier system version to its newer version
This article contains information regarding the process of importing kits from a previous system version. Detailed description of data exchange between the Comarch ERP Enterprise system can be found in documents Import data and Export data.
[Indicator] If the user is not sure about which format is suitable for the import file, the best solution is to use the application for creating an exemplary kit and export that kit in required format and with required template attributes. Such exemplary file can be used as a template for generated import files.[/indicator]
The conditions that must be fulfilled when importing country data and procedures regarding the work with the Import data application are presented in the following chapters:
- Data import
- Attributes necessary for the import
Data import
Preconditions:
- availability of filter for business object: cisag.app.general.obj.Kit, which contains attributes to export.
- the user must possess a file previously exported from another Comarch ERP Enterprise environment
To import kit data, it is necessary to:
1. Open Import data application.
2. In the identification pane of the application, in the Filter filed, with the use of the [Value assistant] button, select KIT filter (business entity: cisag.app.general.obj.Kit)
3. In the work pane, predefined attributes to be imported are selected. At this stage, it is possible to mark additional attributes.
4. Click on the [Import data] button on the standard toolbar. Batch application Import data is opened.
5. In the Import data application, it is necessary to:
- in Source file field, select the source file which is supposed to be imported and from the system knowledge store it is necessary to:
- select the file type. The following file extensions are available:
- XML (*.xml)
- Comma separated values (*.csv)
- UNICODE text (*.xls)
- JSON (*.json)
- select the file type. The following file extensions are available:
- select processing queue in the Batch settings tab
- configure processing settings at own discretion, e.g., define system’s behavior in case of an error or change application server
6. Click on the [In batch] button.
Attributes necessary for the import
To import a file from a previous system version, it is necessary to define at least the following attributes for each business entity:
- identification attributes (business key)
[Indicator] Business key is the attribute number for the Kit object. Main key is the technical identifier (specified as GUID), generated automatically during the import. [/indicator]
- mandatory fields
Below, a table with attributes can be found:
| Attribute/Relation | Description | Notes |
| OrganizationalUnit | Organization | Optional |
| Item | Item | Mandatory, alternatively, through an item line it is also possible to specify Guid |
| type | Structure | Optional, default value: Variable |
| priceDetermination | Price determination | Optional, default value: Components |
| printComponents | Components printout on external documents | Optional, default value: False |
Attributes related to components belonging to kits:
| Attribute/Relation | Description | Notes |
| sequence | Numeration | Mandatory, must be greater than 0 |
| Item | Item | Mandatory, can be also specified through Guid |
| quantity | Quantity | Mandatory, must be greater than 0 |
| validFrom | Valid from | Optional, default value: current date |
| validUntil | Valid until | Optional, default value: maximal system date |
Example of import file in XML format for a kit with two components:
<?xml version=”1.0″ encoding=”UTF-8″?>
<semiramis xmlns=”com.cisag.app.general.obj.Kit”
xsi:schemaLocation=”com.cisag.app.general.obj.Kit Kit.xsd”
created=”2005-12-12T14:28:07.983Z” locale=”en-USXMLSchemaCompliant”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<Kit xmlns=”com.cisag.app.general.obj.Kit”>
<Item>KITITEM</Item>
<Details>
<Item>10010</Item>
<quantity>10.000000</quantity>
<sequence>10</sequence>
</Details>
<Details>
<Item>10020</Item>
<quantity>20.000000</quantity>
<sequence>20</sequence>
</Details>
</Kit>
</semiramis>
Example of a file in XML format with all handled attributes:
<?xml version=”1.0″ encoding=”UTF-8″?>
<semiramis xmlns=”com.cisag.app.general.obj.Kit”
xsi:schemaLocation=”com.cisag.app.general.obj.Kit Kit.xsd”
created=”2005-12-12T14:28:07.983Z” locale=”en-USXMLSchemaCompliant”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
<Kit xmlns=”com.cisag.app.general.obj.Kit”>
<OrganizationalUnit>SALORG</OrganizationalUnit>
<Item>KITITEM</Item>
<type>VARIABLE</type>
<priceDetermination>COMPONENTS</priceDetermination>
<printComponents>true</printComponents>
<Details>
<Item>10010</Item>
<quantity>10.000000</quantity>
<sequence>10</sequence>
<validFrom>2005-11-30T23:00:00.000Z</validFrom>
<validUntil>2005-12-31T23:00:00.000Z</validUntil>
</Details>
<Details>
<Item>10020</Item>
<quantity>20.000000</quantity>
<sequence>20</sequence>
<validFrom>2005-09-20T22:00:00.000Z</validFrom>
<validUntil>4712-12-31T00:00:00.000Z</validUntil>
</Details>
</Kit>
</semiramis>