Topic overview
This article describes the procedure for using the Import data application in relation to inventory requisitions. You will be informed about possible preconditions, effects and special features.
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 an inventory requisition is essentially based on the current data model, which is stored in the repository database. More attributes are available for data export than for data import. It therefore makes sense to define separate filters for export and import.
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 business key from the target object (usually code or number) can be used for the import. For some business objects, an organization is required to convert the functional key to the technical key. The relevant organization is usually not directly in the import source, but is specified via the voucher context. Further information on this can be found under Overview: Attributes.
Certain inventory requisition data such as the status fields and internal auxiliary attributes cannot be imported.
If you are not sure which format is suitable for the import file, proceed as follows: Enter a sample inventory requisition via the Inventory requisitions application and export it using the filter for import in the desired format with the desired attributes. The resulting sample file can be used as a template for the import files to be generated.
The same rules apply when importing as when editing via the application. For example, the item in a saved line item can no longer be subsequently changed. Attribute values are ignored if they cannot be adopted in the current context. The same logic is applied when determining the default value, so that import and application behave identically. The same applies to validations.
Procedure: Importing inventory requisitions
- Open the Import data application
- Display the filter for this business object:
com.cisag.app.inventory.obj.WarehouseOrderThe filter for importing inventory requisitions is opened.
- Duplicate or create a new filter for this business object if required
- Change the already selected attributes of the filter if required
- Select the [Import data] button in the standard toolbar
The Import data dialog box opens.
- You can make settings for the import file in the Import data dialog box. A description of the fields can be found in the Import data article.
- Select one of the buttons [In background] or [Immediately]
The import is executed.
Generaing new inventory requisitions
The minimum required attributes per base object:
| Attribute description | Attribute |
| Location | inventoryOrganization |
| Inventory owner | owner |
| Number | number |
| Text | description |
| Entry date | date |
The minimum required attributes per line item object:
| Attribute description | Attribute |
| Line item number | number |
| Warehouse, warehouse zone, storage location, slot | warehouse, zone, storageLocation, slot |
| Source warehouse, source warehouse zone, source storage location, source slot
|
referemceWarehouse, referenceZone, referenceStorageLocation, referenceSlot |
| General status | status |
| Number of storage units | storageUnitCount |
| Quantity in the 1st item unit | totalQuantity |
| Quantity in the other item units | totalQuantities |
Overview: Attributes
The attributes of the individual business objects that are available for import are listed below. The corresponding relationship name is also included for foreign key attributes. The attributes are subject to change and can be extended by making adjustments.
The identification attributes (key attributes) are marked with a (K).
Basic data
Inventory requisitions (WarehouseOrder)
The identification of an inventory requisition consists of an inventory requisition type and a number from the number range stored for the type.
| Attribute | Relationship | Explanation |
date |
Entry date | |
description |
Text, e.g. reason for an inventory movement | |
guid (K) |
Technical identification for changing/Deletion of already stored data – if known | |
inventoryOrganization |
InventoryOrganization |
Inventory logistics organization (location) |
number (K) |
Number (technical identification), optional for new generation – otherwise determined automatically.
Mandatory if the was not specified when changing/deleting. |
|
owner |
Owner |
Inventory owner |
sourceOwner |
SourceOwner |
Source Inventory owner |
type (K) |
Type |
Inventory requisition type (functional identification):
Mandatory if the was not specified when changing/deleting |
Line item data
| Attribute | Relationship | Explanation |
Ean |
Ean European Article Number (EAN)
Further information can be found in this article: Importing a voucher line item using an EAN |
|
guid (K) |
Technical identification (item) for changing/deleting already saved data – if known | |
item |
Item |
Item |
number (K) |
Item number (technical identification), optional for new creation – otherwise determined automatically.
Mandatory if the |
|
referenceSlot |
Source slot | |
referenceStorage |
ReferenceStorage. |
Source storage location |
referenceWarehouse |
ReferenceStorage. |
Source warehouse |
referenceZone |
ReferenceStorage. |
Source warehouse zone |
slot |
Slot | |
status |
General status | |
storageLocation |
Storage.location |
Storage location |
storageUnit |
StorageUnit |
Storage unit |
storageUnitCount |
Storage unit count | |
totalQuantity
|
|
Quantity of the inventory requisition
|
totalQuantities [0..3]
|
|
Quantity in other item units
|
unitLoad |
UnitLoad |
Loading unit |
uomObligation |
Binding unit
|
|
warehouse |
Storage.warehouse |
Warehouse |
zone |
Storage.zone |
Warehouse zone |