 |
Command:
DEPARTMENT TURNOVERS
 |
Node: department_turnovers |
|
Mandatory: |
no |
|
max. Occurrence: |
unbounded |
|
Description: This tag is used as container for commands regarding turnovers of article groups.
|
|
 |
|
|
 |
Node: department_turnover |
|
Mandatory: |
yes |
|
max. Occurrence: |
unbounded |
|
Supported modes: |
read Read the named item.
|
|
Description: This command is used for the turnover of departments.
|
|
Notes: The TAF (TransActionFile) and the cumulated turnover reports are only disposed if one UC3 is configured to be the TAF-Server of this network (NSM item 841).
|
|
 |
|
|
|
 |
Tag: application_type |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
0
|
|
Nillable: |
no |
|
Description: The application type.
Value |
Description |
0
|
Sales application and cash register application |
|
|
 |
|
|
|
 |
Tag: layer_no |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
1 - 4
|
|
Nillable: |
no |
|
Description: The number of the turnover level .
|
|
Notes: It's possible to define for the TAF-Server (NSM Item 841) from 1 to 4 turnover levels. The turnovers are always accumulated to each level separately and afterwards there is a report for each level. Each turnover level can be deleted separately.
Normally the turnover levels are used in the following way: Level 1 - Turnover per DAY
Level 2 - Turnover per WEEK
Level 3 - Turnovers per MONTH
Level 4 - Turnover per YEAR
|
|
 |
|
|
|
 |
Tag: department_no_first |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
1 - 9 999
|
|
Nillable: |
no |
|
Description: The first department number the turnovers are desired. If both, the first and the last department number are set to 0 then the turnovers of all departments are replied.
|
|
 |
|
|
|
 |
Tag: department_no_last |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
1 - 9 999
|
|
Nillable: |
no |
|
Description: The last department number the turnovers are desired. If both, the first and the last department number are set to 0 then the turnovers of all departments are replied.
|
|
 |
|
|
|
 |
Choice: |
|
|
|
|
 |
Node: turnover_info |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
 |
|
|
|
|
|
 |
Tag: turnover_state |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
0 - 2
|
|
Nillable: |
no |
|
Description: The state the turnovers are replied by the device.
Value |
Description |
0 |
The data are complete and valid. |
1 |
The data may incomplete. This can happen when e.g. at least one device is missing/inactive in the scale network.
|
2 |
The data are invalid. This can happen when a device is still transfering its taf entries to the central TAF and hasn't finished it yet.
|
|
|
 |
|
|
|
|
|
 |
Tag: sequence_no |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The sequence number of the last TAF entry that has been involved in the current turnover accumulation.
|
|
 |
|
|
|
|
|
|
|
|
 |
Node: department_info |
|
Mandatory: |
no |
|
max. Occurrence: |
1 |
|
 |
|
|
|
|
|
 |
Tag: department_no |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
short |
|
Range: |
1 - 9 999
|
|
Nillable: |
no |
|
Description: The number of the department.
|
|
 |
|
|
|
|
|
 |
Tag: name |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
string |
|
Range: |
max. 20 characters
|
|
Nillable: |
no |
|
Description: The name of the department.
|
|
 |
|
|
|
|
|
|
|
|
 |
Node: department_values |
|
Mandatory: |
no |
|
max. Occurrence: |
unbounded |
|
Description: Turnover values of a department.
|
|
 |
|
|
|
|
|
 |
Tag: amount |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The amount. This is the product of the weight multiplied by the baseprice. The value is always stored in the primary currency.
|
|
 |
|
|
|
|
|
 |
Tag: weight |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The weight of the accumulated items belonging to the article group.
|
|
 |
|
|
|
|
|
 |
Tag: number_of_items |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The number of the accumulated items belonging to the article group.
|
|
 |
|
|
|
|
|
 |
Tag: number_of_customers |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The number of customers.
|
|
 |
|
|
|
|
|
 |
Tag: special_offer_amount |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The amount of that items that have been marked as special offer at the moment of its registration. The value is always stored
in the primary currency
|
|
 |
|
|
|
|
|
 |
Tag: special_offer_weight |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The weight of that items that have been marked as special offer at the moment of its registration. The value is always stored
in the primary currency
|
|
 |
|
|
|
|
|
 |
Tag: special_offer_number_of_items |
|
Mandatory: |
yes |
|
max. Occurrence: |
1 |
|
Datatype: |
int |
|
Range: |
See the range of the datatype.
|
|
Nillable: |
no |
|
Description: The number of items that have been marked as special offer at the moment of its registration.
|
|
 |
|
|
|
|
|
|