Repacking
The repacking process allows the user to consolidate, deconsolidate or replace the packaging units of deliveries. The amount of source and destination labels is determined by specifying a "Repack Indicator", which can point to a variety of flows. One To Many and Many To One flows can also have Initial and Subsequent calls depending on, if the current Repacking operation is the first in the workflow or if the included labels were already repacked once, and the current request a subsequent repacking.
Repacking does not modify the source label’s Quantity field. |
Business Logic Description
Repacking can be triggered using several RepackIndicators, which specify the operation’s behavior.
One To One Repacking (Replace)
One To One repacking repacks the contents of the Source Label to the given Destination Label.
RepackIndicator |
0 |
Number of source labels |
1 |
Number of destination labels |
1 |
Source label must exist |
Yes |
Destination label must not exist |
Yes |
One To Many Repacking (Deconsolidation/Split)
One To Many repacking repacks the contents of the existing Source Label to the given Destination Label(s).
RepackIndicator |
1 for Initial, 3 for Subsequent |
Number of source labels |
1 |
Number of destination labels |
N |
Source label(s) must exist |
Yes |
Destination label must not exist |
Yes for Initial call, No for Subsequent call |
Many To One Repacking (Consolidation/Merge)
Many To One repacking repacks the contents of multiple existing Source Labels to the given Destination Label.
RepackIndicator |
2 for Initial, 4 for Subsequent |
Number of source labels |
N |
Number of destination labels |
1 |
Source label(s) must exist |
Yes |
Destination label must not exist |
Yes for Initial call, No for Subsequent call |
Common validations
Location | Field | Validation |
---|---|---|
Repack Header |
Plant |
Required |
Repack Header |
Timestamp |
Required |
Repack Header |
LanguageISOCode |
Required |
Inbound Delivery |
Vendor Number |
Required |
Inbound Delivery |
External Delivery Identifier |
Required |
Inbound Delivery |
Delivery Identifier |
Required |
Inbound Delivery |
Delivery Date |
Required |
Goods Receipt |
Goods Receipt Identifier |
Required |
Goods Receipt |
Goods Receipt Date |
Required |
Goods Receipt |
Goods Receipt Timestamp |
Required |
Repack Request |
Dissolved Packaging Unit Identifiers (Source Labels) |
Required and not empty |
Repack Request |
New Packaging Units (Destination Labels) |
Required and not empty |
Repack Request |
Repack Indicator |
Value between 0 and 4 |
Fallback behaviors
Field | Fallback |
---|---|
Identifier missing in label fields |
Packaging Unit’s Identifier is used |
Quantity amount is missing |
Quantity amount is entered as 0 |
Package Identifier is missing from label fields |
The label’s identifier is entered as the package identifier |
Possible warnings
Warning Code | Warning Description |
---|---|
2001 |
Blocking rules check failed |
2002 |
Expiration date check failed |
2003 |
Quantity check failed |
Possible errors
Error Code | Error Description |
---|---|
3000 |
Duplicate material ID detected |
3010 |
Pre-validation failed |
3011 |
Required field is missing during pre-validation |
3012 |
Incorrect delivery note references in GTL Label |
3013 |
Subpackaging references link to a non-existing packaging unit |
3014 |
Subpackaging references have multiple parent units |
3015 |
Circular reference detected in subpackaging |
3016 |
Duplicate identifier found in message |
3017 |
Identifier already exists in the database |
3018 |
Identifier does not exist in the database |
3019 |
More batches than allowed |
3020 |
Operation prohibited by label state |
3021 |
Field value differs from parent label |
3024 |
Label field length is not acceptable |
3030 |
Data annotation validation failed |
3040 |
Parent object has a problem |
3050 |
Object conversion failed |
3051 |
Label cannot be parsed during object conversion |