placeholder Command:  ARTICLE PROOF OF ORIGIN ASSIGNMENTS 


Short version Long version Changes Example

Mandatory: no
max. Occurrence:  unbounded
Description:
This tag is used as container for commands regarding the assignment of proof of origin type to an article/item.
Notes:
The proof_of_origin fuctionality is implemented to the application first time in this version.
"Proof of origin" is an option which needs a licence-key to be enabled (uc3options.xml).
The XML command will be processed by the device whithout activiation.
The proof of origin functionality itself doesn't work with activation.
 
Mandatory: yes
max. Occurrence:  unbounded
Supported modes: delete Delete the named item.
read Read the named item.
write Write the named item.
Description:
This command is used to assign a proof of origin type to an article/item.
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 whithout a license key.

The proof of origin functionality itself doesn't work without a license key.
The modes 'read+', 'read+', 'read-' and 'deleteall' are supported with version 1.28.0 and higher.

For the mode 'readall' the following information can be helpful:
The table below shows values for the mandatory elements.
<department_no> <plu_no> Comment
0 0 The assigned proof of origin items of all articles over all departments will be returned.
0 unequal 0 The assigned proof of origin items of the article whose plu number is greater or equal than the value <plu_no> over all departments will be returned.
unequal 0 0 The assigned proof of origin items of all articles belonging to the department <department_no> will be returned.
unequal 0 unequal 0 The assigned proof of origin items of all articles whose plu number is greater or equal than the value <plu_no> belonging to the department <department_no> will be returned.

For the mode 'deleteall' the following information can be helpful:
The table below shows values for the mandatory elements.
<department_no> <plu_no> Comment
0 0 All proof of origin items of all articles in all departments will be deleted.
0 unequal 0 All proof of origin items whose plu number is greater or equal than the value <plu_no> over all departments will be deleted.
unequal 0 0 All proof of origin items of all articles that are belonging to the desired department <department_no> will be deleted.
unequal 0 unequal 0 All proof of origin items that are belonging to the desired plu <plu_no> and department <department_no> will be deleted.

   
Mandatory: yes
max. Occurrence: 1
Datatype: short
Range: 1 - 9 999
Nillable: no
Description:
The department number the article/items belongs to.
   
Mandatory: yes
max. Occurrence: 1
Datatype: int
Range: 1 - 999 999
Nillable: no
Description:
The number of the article/item.
   
Mandatory: no
max. Occurrence: 1
Datatype: string
Range: max. 20 characters
Nillable: no
Description:
The proof of origin type the article is assigned to.
The value is corresponding to the command <proof_of_origin_type_definition> of the proof of origin type definition
Notes:
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 name.
In this case there will be an exeption in the response file.
   
Mandatory: no
max. Occurrence: 1
Datatype: short
Range: (0/1)
Nillable: no
Description:
Boolean value (yes/no) to define if the proof_of_origin_type asigned to this artile is active or not.
When this information is missing (not sent via TransUC3) it's defined with the default value 0 (FALSE).
   
Mandatory: no
max. Occurrence: 1
Datatype: short
Range: 0 - 999
Nillable: no
Description:
The best_before_date_offset for the verification defined in the <proof_of_origin_type_definitions> is used for the indicated articles instead of all other defined best-before date offsets (in the <department_proof_of_origin_assignment> or the mode's <configuration_profiles>). The value will be interpreted as number of days.
Notes:
The offset is used to define a time period prior the best-before date of the lot. In this period the article is booked even though it is close to the end of its life. So the shelf life might be considered as too short to allow booking or at least to give the operator a warning.
   
Mandatory: no
max. Occurrence: 1
Datatype: dateTime
Range: -
Nillable: yes
Description:
The last time when the record was changed.
CCYY-MM-DDThh:mm:ss
The format is as following:
C = Century
Y = Year
M = Month
D = Day
T = Separator between date and time
h = hour
m = minute
s = second