Topic overview

This article describes procedures for using the Import data application in relation to the identifier where-used list.

The description of the Import data application, which also includes field and button descriptions, can be found in the Import data article.

General information

The import of the identifier where-used list is essentially based on the current data model, which is stored in the repository database.

1:1 relationships are generally based on a technical GUID attribute in the data model. Depending on the use case, either the technical GUID attribute or the identification from the target object (usually code or number) can be used during import.

The import of identifier where-used list data is also used to create an identifier where-used list for external production. From this point on, Comarch ERP Enterprise can no longer track identifier-managed items that were delivered to a supplier (external manufacturer) by delivery order and delivery slip. The supplier refines the product with these marked items. The production item contains these items. If an identifier where-used list is required for these products, you need to know which identifiers were used. It is therefore necessary to import this information from the supplier.

The attributes required for this and the corresponding validations are indicated for each attribute.

Procedures

1. Open the Import data application
2. Display the filter for the business object cisag.app.inventory.obj.IdentifierTracking

• The filter for importing the identifier where-used list is displayed.
  (If required, you can also create a new filter for this business object)

3. The attributes of the filter are already selected. You can still adjust the attributes if required.
4. Select the [Import Data] button in the standard toolbar

• The Import data dialog window opens

5. You can make settings for the import file in this dialog window. A detailed description of the fields can be found in the Import data article in the chapter of the same name.
6. You can carry out the import by selecting the [In background] or [Immediately] button

Attributes required for importing from older systems

The minimum attributes required for importing identifier where-used list data are:

• Item: item
• Identifier: identifier
• Warehouse: storageArea
• Posting key: transactionType
• Date: date

A corresponding minimum XML file with attributes for importing an identifier where-used list looks as follows:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.inventory.obj.IdentifierTracking" xsi:schemaLocation="com.cisag.app.inventory.obj.IdentifierTracking IdentifierTracking.xsd" created="2006-01-06T08:23:06.767Z" locale="en-US-XMLSchemaCompliant" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <IdentifierTracking xmlns="com.cisag.app.inventory.obj.IdentifierTracking">
  <storageArea>
   <warehouse>100</warehouse>
  </storageArea>
  <date>2006-01-10T23:00:00.000Z</date>
  <quantity index="0">
   <amount>15.000000</amount>
   <Uom>pc</Uom>
  </quantity>
  <quantity index="1" xsi:nil="true"/>
  <quantity index="2" xsi:nil="true"/>
  <quantity index="3" xsi:nil="true"/>
  <_timeZone>CET</_timeZone>
  <CostCenter xsi:nil="true"/>
  <CostObjective xsi:nil="true"/>
  <Partner>0001</Partner>
  <TransactionType>02</TransactionType>
  <Identifier>
   <number>0001</number>
   <Item>CHARGE_01</Item>
  </identifier>
 </IdentifierTracking>
</semiramis>

Overview: Supported attributes during import

This section lists all the attributes supported when importing an identifier where-used list. The corresponding relationship name is also shown for foreign key attributes. The attributes can be subject to changes and can also be extended through adjustments.

The identification attributes (key attributes) are also marked with a (K).

Special features of legacy data transfer

When transferring legacy data, special handling is carried out for the transfer of voucher relationships, which makes it necessary to specify both the technical key and the number of the order or order line item when specifying a voucher relationship. This information is necessary so that voucher reorganization data can be generated if a voucher relationship does not exist in the destination system.

The noPlausibilityCheck attribute must be set to true for the legacy data transfer, as this is used to recognize the import for a legacy data transfer. The export for the V1R2M2 system has been extended so that this attribute is included in the export file with the value true. The attributes for specifying a voucher relationship are already set for exporting from a V1R2M2 system in accordance with the specifications for a legacy data transfer.

Validating the imported data

Identification attributes
All identification attributes, except for order and orderDetail, are validated to see whether they have been specified and whether they exist in the system.

Optional attributes
When specifying a non-identification attribute that represents a reference to a business object, the existence of the object is validated.

Posting key
When importing the identifier where-used list, no posting keys may be used that have the process Receipt transfer posting or Issue transfer posting.

Plausibility checks
If the noPlausibilityCheck attribute is set to false in the import file or is not imported, a plausibility check is carried out on the specified order. When importing identifier where-used list data for materials provided to vendor (external production), the system also checks whether a matching production order exists for the specified delivery slip and whether the production order has the status Released or Completed. The system also checks whether the specified item is in both the delivery slip line item and the associated production order line item.