This service creates locations in a zone within a node in the warehouse. These locations specify the physical space where inventory is stored. It calls the manageLocation() API.
Attribute | Description | Sequence | Data Type | Size |
---|---|---|---|---|
LOCAHEDR | The location header identifier | 1 | String | 8 |
LocationId | The unique identifier for the location. This in conjunction with NODE_KEY identifies a unique location in the node | 2 | String | 40 |
Node | The node to which the location belongs. | 3 | Key | 24 |
LocationType | The system defined classification of location to aid association of locations of certain types for certain other operations. The supported types are: INTRANSIT (Mobile locations), STAGING, VIRTUAL, REGULAR and DOCK. For example, all equipment locations should be of type INTRANSIT. If LocationType is passed blank or passed unallowed values then default LocationType is taken as REGULAR | 4 | String | 40 |
ZoneId | The zone to which the location belongs. This in conjunction with the node key identifies a unique zone within the node. | 5 | String | 40 |
AisleNumber | The aisle number of the location. Locations belong to zones, which have travel aisle's between them. A zone could belong to multiple aisles and multiple zones could belong to an aisle. But a location in a zone belongs to one and only one aisle. | 6 | Integer | 9 |
LevelLocation | The level number of the location. This indicates the height of the location (y-co-ordinate of the location from the floor) classified as levels. Level attribute of the location is used in arriving at locations nearest to the dedicated locations algorithm used in put away. Typically, the level attribute is contained within the location ID. | 7 | Integer | 9 |
BayNumber | The bay number of the location. Typically, the aisle, level and bay put together gives the physical location of the location in the node if they are based on coordinate system. Bay attribute of the location (x-coordinate from the beginning of the aisle) is used in arriving at locations nearest to the dedicated locations algorithm used in put away. Typically, the bay attribute is contained within the location ID. | 8 | Integer | 9 |
MoveInSequence |
The move in sequence number of the location. This is used by task management for location suggestion while moving in inventory (put away). The put away location selection algorithm uses this information to select locations amongst a list of locations based on its move in sequence. | 9 | Integer | 9 |
MoveOut |
The move out sequence number of the location. This is used by task management for location suggestion while moving out inventory (picking). The pick location selection algorithm uses this information to select locations amongst a list of locations based on its move in sequence. | 10 | Integer | 9 |
InStaging |
The in staging location id indicates the Drop off location (For moves coming into a location, they may be dropped here) | 11 | String | 40 |
OutStaging |
The out staging location id indicates the Out Drop off Location (Location where moves originated at this location, may be dropped). | 12 | String | 40 |
VelocityCode |
The velocity code of the location classifies items as A, B or C class items based on whether they are fast selling, not so fast selling and low selling item. These item classifications are typically followed by all enterprises to optimize certain operations such as sourcing and stocking. The reason we have locations preferring certain velocity codes is that, we could have locations closer to dock stocking A class items, and locations furthest away from the dock stocking C class items. Velocity code is a preference on the location and not a constraint. If A class items fill up all locations meant for A class items, then they can go in to B and then C. Similarly C can go to B and then A for lack of space in the respective locations preferred for a specific velocity code. B class items go into C and then into A. If VelocityCode is passed blank or passed unallowed values then default VelocityCode is taken Last VelocityCode in the alphabetic sequence in common code of type VELOCITY_CODE. | 13 | String | 40 |
LocationSize |
The location size code defines the capacity of a location. All locations having the same size (dimensions and ability to hold the same weight) are classified under the same size code. This maps to the primary key attribute of the YFS_LOCATION_SIZE_CODE table. | 14 | String | 40 |
StorageCode | Storage code is an attribute of the location that allows the warehouse to store items that have the same storage profile as that of the location. For example, hazardous inflammable items need locations close to fire extinguishers. In this case the locations are marked as having a storage code, which is suitable for storing Inflammable items. This ensures that only inflammable items get to these locations. | 15 | String | 40 |
X Co-ordinate | X Co-ordinate for a location in the warehouse | 16 | Number | 14 |
Y Co-ordinate | Y Co-ordinate for a location in the warehouse | 17 | Number | 14 |
Z Co-ordinate | Z Co-ordinate for a location in the warehouse | 18 | Number | 14 |
The schema files used by each component of the service and the API called by the service are as follows: