|
Mandatory: |
yes |
|
max. Occurrence: |
unbounded |
|
Supported modes: |
delete Delete the named item. read Read the named item. read+ Read the following item. read- Read the previous item. readall Read all items from the desired device(s). This doesn't mean comparable reading as in the L2 protocol. write Write the named item.
|
|
Description: For an existing proof of origin type definitions one or more lot(s) can be defined,
if the lot is a "Multiple lot" (value for single_lot="0") or "Auto lot id" (value for single_lot="2").
|
|
Notes: To use the proof of origin functionality on the device it is necessary to activate it.
"Proof of origin" is an option which needs a license key to be enabled (uc3options.xml).
The XML command will be processed by the device without a license key. The proof of origin functionality itself doesn't work without a license key.
If this <proof_of_origin_type> doesn't exist in the <proof_of_origin_type_definitions> then it's not possible to create a lot for this type.
In this case there will be an exception in the response file.
The values of the tags <start_date> and <end_date> can be set/reseted partially. The values for the apply range(s) can not be set/reseted partially. If the command contains the tag <apply_range> then an already existing apply range(s) will be deleted and replaced by the new one.
When using the mode ''write'' at least one lot field <proof_of_origin_lots> must be set. Otherwise the command has no effect. For the mode ''readall'' the following information can be helpful: The table below shows values for the mandatory elements.
proof_of_origin_type
|
lot_id
|
Comment
|
no value |
no value |
All lots independent on its proof of origin type will be returned. |
no value |
value |
All lots that are subsequent to the value of <lot_id> will be returned, independent on its proof of origin type. |
value |
no value |
All lots belonging to the proof of origin type <proof_of_origin_type> will be returned. |
value |
value |
All lots that are subsequent to the value of <lot_id> and belonging to the proof of origin type
<proof_of_origin_type> will be returned.
|
If a promotion validity is deleted its assigned articles/items set by the commands <article_promotions> will be deleted, too. This doesn't have influence on the article/items created by using the command <articles>.
|
|
 |