In this article, you can familiarize yourself with the functionality and the ability to generate the "KM Aggregation" document in the personal account of the NIS MPT "ASL BELGISI".
- Glossary
- KM Aggregation Report Creation
- Viewing Reports
- General Principles of Aggregation Report Validation by the System
- Disaggregation Status
Glossary
Term |
Description |
---|---|
KI | Identification code of the consumer package |
KIGU | Identification code of the group package |
KITU | Identification code of the transport package (box, pallet) |
SSCC |
Serial Shipping Container Code — serial code of the transport package (in system shown as KITU) |
KM Aggregation Report Creation
To perform operations in the personal account of NIS “ASL BELGISI,” go to the “Code Operations” section and then to the subsection “Own Operations.” In the current section, click the button “Create Operation” → “KM Aggregation.”
The “KM Aggregation” operation can be performed only if the user has the “Document Creator – Aggregation” role activated. For more details on assigning roles, refer to the article: xTrace: User Profile - Assigning a Role to a User
In the "General Information" section, the following required fields marked with * must be filled out:
- Emitter's Place of Business Activity (POBA) – selected from the list of added locations
- Packaging Date – the date of aggregation formation
- Production Order Number – optional
In the "Aggregation Data" section, the following required fields marked with * must be filled out:
- Packaging Code – SSCC aggregation code or group packaging code
- Extract from parent packaging
- Maximum quantity per package – maximum capacity of the package
- Details of aggregated products (upload a .csv file) – upload a file containing the list of KI codes to be included in the aggregation
❗IMPORTANT: In the CSV file for the “Aggregation” report, the key and verification code (crypto tail) must not be included.
When uploading the file, the following conditions are checked:
- The file is in CSV format and not empty
- Each code is listed on a new line
- Only the following characters are used:
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789!”%&’*+-./_,:;=<>?() - The codes in the file are unique (no duplicates)
- The number of lines does not exceed 30,000
Viewing Reports
To view “KM Aggregation” operations in your personal account, go to the “Code Operations” section and set the filter in the “Operation Type” field.
The list displays reports with the following statuses:
-
Under Review – The report is being checked by the system
-
Successfully Processed – The report was successfully processed
-
Processed with Errors – The report was processed with errors. The reason is shown in the report interface
⚠️ To view service provider operations, go to the “Service Provider Operations” subsection.
General Principles of Aggregation Report Validation by the System
The system does not allow partial processing of the “KM Aggregation” operation. If even one code does not meet the requirements, the entire report will be rejected.
In the user’s personal account, only one aggregation code can be used per KM Aggregation report.
All codes included in a single aggregation must be of the same GTIN (i.e., the same product type).
"Disaggregated" Status
Disaggregation – loss of integrity of the transport packaging.
If any KI code included in an aggregation is used in operations such as transfer/sale via e-invoice, retail sale, etc., the aggregation code loses its integrity and can no longer be used (becomes disaggregated).
If a KI code is moved into another KITU (and the source KITU still contains other KI codes), the source KITU is not disaggregated.
To maintain the integrity of the transport packaging, a KITU must contain at least one consumer code (KI)
Comments
Please sign in to leave a comment.