Import identifiers

Topic overview

This article describes procedures for using the Import data application with regard to identifier data.

For description of the Import data application, including descriptions of fields, buttons, etc., see the Import data article.

General

The import of identifier data is based mainly on the current data model stored in the repository database.

Importing as well as exporting of identifiers support the same attributes. For this reason, you only have to define a single filter for importing as well as for exporting.

1:1 relationships are typically based on a technical GUID attribute in the data model. Depending on the application, either the technical GUID attribute or the identification from the destination object (usually code or number) can be used
for the import.

Note
If you are not certain which import file format is suitable, proceed as follows: Use the Identifiers application to create a new identifier or open an existing identifier and export it with the import filter in the desired format and with the desired attributes. The example file produced in this way can be used as a template for the import files to be generated.

With regard to defaults and checks, the same rules apply for the import as for processing using the Identifiers  application.

Procedure

  1. Open the Import data application
  2. Display the filter, or one of the filters, for the business object cisag.app.inventory.obj.InventoryIdentifier
  • The filter for the import of the identifier is displayed.
    (If required, you can also create a new filter for this business object).
  1. The selected attributes of the filter are already activated. If required, you can still adapt the attributes.
  2. Select the [Import data] button in the standard toolbar
  • The Import data dialog window opens.
  1. You can make settings for the import file in this dialog box. A detailed description of the fields can be found in the Import data documentation in the section of the same name.
  2. In this dialog window, you can make the settings for the import file. For a detailed description of the fields, see the section of the same name in the article Import data.
  3. To start the import, select the [In batch] or [Immediately] button

Necessary attributes for the import from legacy systems

The minimum attributes required for importing an identifier are:

  • Items item
  • Identifier number number
  • Identifier description description

If you also want to import the supplier item identifier for an identifier, you must specify the following attributes for each data record:

  • Identification of the supplier item identifier number

The supplier item identifier is located in the filter under the technical name InventoryIdentifierExternal, which has the description External identifier.

A corresponding minimal XML with technical attributes for importing a batch looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<semiramis xmlns="com.cisag.app.inventory.obj.InventoryIdentifier"
xsi:schemaLocation="com.cisag.app.inventory.obj.InventoryIdentifier
InventoryIdentifier.xsd" created="2005-03-21T07:33:23.323Z" locale="en-US-XMLSchemaCompliant"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <InventoryIdentifierxmlns="com.cisag.app.inventory.obj.InventoryIdentifier">
  <Item>BATCH_01</Item>
  <number>CH_01</number>
  <description>Batch 01</description>
  <qcStatus>RELEASED</qcStatus>
  <_timeZone>CET</_timeZone>
 </InventoryIdentifier>
</semiramis>

In the case of an import for which only the mandatory attributes have been specified, all other data are calculated using the data entered for the item, including the Weights and dimension and the Defaults for identifiers, or are taken directly from the item. In the case of legacy data transfer, if these values are not to be generated using the item data, these must be specified as part of the import. In addition, the transfer of weights and dimensions is dependent on settings in the Customizing application.

Overview: Supported attributes for the import

This chapter lists all attributes supported for importing identifiers. The corresponding relationship name is included in the external key attributes. The attributes may be subject to changes and may also be extended as a result of adaptations.

Since there are four different types of identifiers, all attributes that apply to only one identifier type are identified separately. The attribute identifications are as follows: (CH) – Batch attribute, (LOS) – Lot attribute, and (SN) – Serial number attribute of an inventoried serial number. Some serial number attributes are updated when inventory postings are made. These attributes have the serial number identification, extended to include _B (SN_B).

The identification attributes (key attributes) are also identified using a (K).

Identifier data (InventoryIdentifier)

Attribute Relationship Explanation
guid (K) Technical identification
item (K) Item Item of the identifier to be imported.
You must specify an item for all identifier types.
number (K) Identifier number.
You must specify the identifier number for all identifier types.
Description Identifier description.
You must specify a description for all identifier types.
qcStatus Quality status (QA status) of the identifier to be imported.
You must specify a QA status except for the serial number without inventory management.
Possible values for the QS status are:

  • RELEASED (released)
  • QUARANTINE  (in quarantine)
  • ON_HOLD (blocked)
bestBeforeDate (CH) Expiration date
The expiration date is the date up to which the usability of a batch is guaranteed.
When withdrawal is according to the FIFO principle, the batches are considered according to their expiration date. Therefore, an expiration date must be specified for batches.
holdDate (CH) Retaining date
The retaining date is the time point up to which the batch is not available for withdrawal. This
means that the inventory of the identifier will not be considered for picking for the automatic batch assignment during this time.
Note
If you are using an import filter for which a retaining date is required, you must always specify a date. However, you can also use
the date 31.12.0001 and time 23:00:01, which is equivalent to no specification. This date will not be displayed later in the Identifiers application. However, if you are using a filter for which a retaining date is not required, then a retaining date is calculated automatically and set for the imported batch, based on the retaining term located in the defaults for identifiers in the item master data. 
warnDate1 (CH) Warning date 1
The advance warning period is entered in two steps. It allows the expiration date of batches to be checked in a timely manner, e.g., using a workflow activity definition.
Note
If you are using an import filter for which warning date 1 is required, you must always specify a date. However, you can also use
the date 31.12.0001 and time 23:00:01, which is equivalent to no specification. This date will not be displayed later in the Identifiers application. However, if you are using a filter for which warning date 1 is not required, then warning date 1 is calculated automatically and set for the imported batch, based on advance warning period 1 located in the defaults for identifiers in the item master data.
warnDate2 (CH) Warning date 2
The advance warning period is entered in two steps. It allows the expiration date of batches to be checked in a timely manner, e.g., using a workflow activity definition.
Note
If you are using an import filter for which warning date 2 is required, you must always specify a date. However, you can also use
the date 31.12.0001 and time 23:00:01, which is equivalent to no specification. This date will not
be displayed later in the Identifiers application. However, if you are using a filter for which warning date 2 is not required, then warning date 2 will be calculated automatically and set for the imported batch, based on advance  warning period 2 located in the defaults for identifiers in the item master data. 
creationDate Date on which the characteristic was created.
Note
If you are using an import filter for which the generation date is required, you must specify a date in the import file. If you are using a filter for which the generation date is not required, the current date will be used for the imported identifier.
partner  (SN_B) Partner Partner of the last inventory posting for which a partner was specified. See note at end of this chapter.
costCenter (SN_B) CostCenter Cost center of the last inventory posting for which a cost center was specified. See note at end of this chapter.
costObjective (SN_B) Cost
Objective
Cost unit of the last inventory posting for which a cost unit was specified. See note at end of this chapter.
guaranteeFromDate (SN) Guarantee from date
guaranteeUntilDate (SN) Guarantee until date
beginOfOperation (SN) Start-up
The start-up date is not currently used and can accompany a serial number for informational purposes only.
If you are using an import filter for which the start-up attribute is required, you must always specify a date. However, you can also use
the date 31.12.0001 and time 23:00:01, which is equivalent to no specification. This date will not be displayed later in the Identifiers application. If a filter is used in which the start-up date is not required, this date will not be set.
Note
Some attributes that apply only to serial numbers with inventory management are there in order to add supplementary information to the inventory postings that have resulted in an inventory change or inventory value change in the case of a serial number. While importing this supplementary information (partner, cost center, cost unit, and posting key) does not lead to inconsistent data, it can cause misunderstandings if, for example, the serial number does not affect inventory but a receipt posting key is indicated.

Supplier item identifier (InventoryIdentifierExternal)

Attribute Relationship Meaning
identifier (K) identifier Identifier to which the supplier identifier belongs
number  (K) Identifier number
Description Description

Weights and dimensions (InventoryIdentifierMeasurements)

The weights and dimensions may only be specified if you want to enter your own weights and dimensions for the identifier and thus remove the reference to the item master data.

Note
This setting cannot be undone. If you specify weights and dimensions for an identifier during import, the weights and dimensions of the associated item can no longer be used for the identifier.
Attribute Relationship Meaning
guid (K) Technical identification
measurements Part, in which the weights and dimensions of the item are saved for the respective identifier.

Part in which the weights and dimensions are saved (ItemMeasurementsData)

Attribute Relationship Meaning
netWeight Net weight of the item for the respective identifier.
netVolume Net volume of the item for the respective identifier.
grossWeight The gross weight is the maximum weight of the item for the respective identifier. In
addition to the net weight, this includes the weight of any packaging and  additional accessories.
grossVolume The gross volume is the maximum volume of the item for the respective identifier. This also includes the volume of any packaging and additional accessories.
length Length of the item for the respective identifier.
The length also includes the length of any packaging.
diameter Diameter of the item for the respective identifier.
The diameter also includes the diameter of any packaging.
height Height of the item for the respective identifier.
The height also includes the height of any packaging.
density Density of the item for the respective identifier.
width Width of the item for the respective identifier.
The width also includes the width of any packaging.
area Area of the item for the respective identifier.

 

Czy ten artykuł był pomocny?