Store inventory management yfs.properties
Use the customer_overrides.properties file
to override properties in the Store Inventory Management category
of yfs.properties.
The following table contains Store Inventory Management yfs.properties and descriptions.
| Property | Values | Description |
|---|---|---|
| Store Inventory Management | ||
| yfs.allow.reuse.previouswave.slots | Valid values = Y or N Default = Y |
When dynamic slotting in configured, for the second and subsequent
wave releases, the previously slotted locations are considered in
order to minimize the number of locations. If this property is set
to N, the previously slotted locations are not considered for the
subsequent wave releases. Example: yfs.allow.reuse.previouswave.slots=Y |
| yfs.solver.iterations.wavecreate | The number of solver iterations for Create Wave. Use this property
to set the number of solver iterations through which the create wave
Agent will undergo to optimize wave creation. Example: yfs.solver.iterations.wavecreate=1 |
|
| yfs.cancelwave.offline.taskcount.greaterthan | Cancellation of wave happens in background depending upon the
value of the property yfs.cancelwave.offline.taskcount.greaterthan.
If the value of the property is for ex: 500 then cancellation of a
wave, which has open tasks more than 500 included in it then the wave
gets cancelled in offline mode. Waves that have open tasks equal to
or less than 500 gets cancelled online. Example: yfs.cancelwave.offline.taskcount.greaterthan=-1 |
|
| yfs.cancelwave.offline.shipmentcount.greaterthan | Cancellation of wave happens in background depending upon the
value of the property yfs.cancelwave.offline.shipmentcount.greaterthan.
If the value of the property is for ex: 500 then cancellation of a
wave, which has shipments more than 500 included in it then the wave
gets cancelled in offline mode. Waves that have shipments equal to
or less than 500 gets cancelled online. Example: yfs.cancelwave.offline.shipmentcount.greaterthan=-1 |
|
| yfs.cancelmove.offline.taskcount.greaterthan | Cancellation of move request happens in background depending
upon the value of the property yfs.cancelmoverequest.offline.taskcount.greaterthan.
If the value of the property is for ex: 500 then cancellation of a
move request, which has open tasks more than 500 included in it then
the move request gets cancelled in offline mode. Move requests that
have open tasks equal to or less than 500 gets cancelled online. Example: yfs.cancelmove.offline.taskcount.greaterthan=-1 |
|
| yfs.suggesttask.onshortpick.tasktypelist | If this property is enabled, the specified task
or tasks will be suggested even if onhand inventory is not available
at the pick location. You can specify multiple task type values for
this property; however, values must be separated by commas. Example: yfs.suggesttask.onshortpick.tasktypelist=<tasktype1>,<tasktype2>,<tasktype3> |
|
| yfs.canceltask.onshortpick.tasktypelist | Cancellation of specified tasktypes happens for the remaining
quantity on a short pick depending upon the value of the yfs.canceltask.onshortpick.tasktypelist.
You can specify multiple tasktype values for this property; however,
values must be separated by commas. Example: yfs.canceltask.onshortpick.tasktypelist=<tasktype1>,<tasktype2>,<tasktype3> Only tasktypes specified in yfs.canceltask.onshortpick.tasktypelist= are canceled, and if tasktype is not specified in this property, the task is moved to hold status. |
|
| yfs.containerization.maxshipmentsinoneround | The containerizeWave API will use this property to select number
of shipments to be considered for creating the outbound containers
in one round. API will consider default value as 75 if value is not
specified for this property. Example: yfs.containerization.maxshipmentsinoneround=75 |
|
| yfs.prevent.palletlabel.for.parcelshipment.tasktypelist | During containerization, the system creates
Pallet labels if the item has an alternate UOM with LPN type = Pallet
and the containerization quantity matches the alternate UOM quantity.
But for Parcel shipments, creation of Pallet labels can be prevented
by specifying the task type to this property. You can specify multiple
task type values for this property; however, values must be
separated by commas. If this property is not set or if the task is
not among the task types mentioned in the property value list, the
system will retain the default behavior. Example: |
|
| yfs.install.createWave.delayhours | The CREATE WAVE FOR SHIPMENT GROUP agent uses this property
to increase the Available date (in hours) of YFS_Task_Q records with
transaction key "CREATE_WAVE_TASK_Q.4001" against which no waves could
be created. Agent considers default value as 1 if value is not specified for this property. If set to -1, the YFS_Task_Q records with transaction key "CREATE_WAVE_TASK_Q.4001" for which no waves are generated, will be deleted. Example: yfs.install.createWave.delayhours=1 |
|
| yfs.createwave.dbRead.numShipmentLines | Default = 20000 | The CREATE WAVE agent uses this property to read maximum number
of shipment lines from database in a single query. Example: yfs.createwave.dbRead.numShipmentLines=20000 |
| yfs.createwave.process.numShipmentLines | Default = 50000 | The CREATE WAVE agent uses this property in order to determine
the maximum number of shipment lines for optimal memory utilization
during wave creation. Example: yfs.createwave.process.numShipmentLines=50000 |
| yfs.releasetask.ignore.wavesequence | Valid values = Y or N | If this property is set to “Y”, the RELEASE TASK agent ignores
the wave sequence when releasing tasks. For example, if there are
two waves having the same priority, but different sequence numbers,
and if the tasks for the wave having a lower sequence number cannot
be released, the tasks for the wave having a higher sequence number
will be released. Example: yfs.releasetask.ignore.wavesequence=Y |
| yfs.wms.resourceplanning.QueueName yfs.wms.resourceplanning.ProviderURL yfs.wms.resourceplanning.QCFLookUp |
Set these JMS properties to enable resource planning move. Examples: yfs.wms.resourceplanning.QueueName=DefaultAgentQueue yfs.wms.resourceplanning.ProviderURL=t3://localhost:7001 yfs.wms.resourceplanning.QCFLookUp=AGENT_QCF |
|
| yfs.wms.zonetransattr.refreshrate | Default = 600 seconds | getZoneDetails API uses the below mentioned property to refresh
the zone attributes: available volume, available weight, pending volume
and pending weight in the table YFS_TRAN_ZONE_ATTRS. These zone attributes
are aggregates of the location attributes. Zone attributes # are refreshed
after specified time intervals which is defined by this property. Example: yfs.wms.zonetransattr.refreshrate=600 |
| yfs.releaseWave.SortShipmentsByDateAndKey | Valid values = Y or N Default = N |
During Release wave, if shipments need to be allocated quantity
based on requested shipment dates, set this property to "Y". Example: yfs.releaseWave.SortShipmentsByDateAndKey=N |
| yfs.default.inventorystatus.for.newinventory | In case of counting through mobile application if user counts
new inventory, system currently displays first inventory status of
the node as defaulted. If this behavior needs to be overridden, then
the below property needs to be set with valid inventory status which
will be used as default inventory status for new inventory. If this
property is not set, system will retain the current behavior. Example: yfs.default.inventorystatus.for.newinventory= |
|
| yfs.closemanifest.online | Valid values = Y or N | Manifesting options. Set this property to N to close manifest
asynchronously using the CLOSE_MANIFEST Agent. Example: yfs.closemanifest.online=Y |
| yfs.confirmbatch.online | Valid values = Y or N | Batch completion options. Set this property to N to complete
batch asynchronously using the REQ_BATCH_COMPLETION Agent. Example: yfs.confirmbatch.online=Y |
| yfs.reopentask.time | Default = 1 hour | The re-open task agent will change the status of a suggested
task back to open status, if the task is not modified for the time
specified by this property. This property is specified in hours. Example: yfs.reopentask.time=1 |
| yfs.serial.receiving | Valid values = Y or N | Set this property to 'Y' to process one serial at a time during
receiving i.e on scanning one serial user is taken to Disposition
Code entry screen. Example: yfs.serial.receiving=N |
| yfs.releasetaskagent.mode | Valid values = 01: Location Driven. All the pending tasks from the location are evaluated. 02: Reference (eg. ShipmentNo) Driven. All the pending tasks for the reference are evaluated. Default = 01 |
releaseTaskAgent uses this property to select the mode of execution
for releasing tasks. Example: yfs.releasetaskagent.mode=01 |
| yfs.retain.pack.tasks.for.minute | Default = 60 minutes | In case of item driven packing, shipment level transaction
locks are created in order to reserve the shipment against the packer.
Once the shipment packing is complete, these transaction locks are
deleted from DB. If for some reason packing for this shipment cannot be completed by the packer, these transaction locks block other users from packing this shipment. This property can used to define maximum time, in minutes, for which the shipment level transaction locks are retained. If it is set to 120, and a user scans a Pallet in Pack HSDE, transaction locks created 120 minutes before will be deleted so that the unpacked blocked shipment becomes available to other users. Example: yfs.retain.pack.tasks.for.minutes=60 |
| yfs.override.user.constraints.for.manually.assigned.task | Valid values = Y or N Default = N |
Based on this property, the maximum user constraints defined
for a task type will be evaluated. If task is manually assigned to
a user and this property is set to Y, the maximum user constraint
defined for task type will not be honoured. To retain the existing
behavior, set this property to N. Example: yfs.override.user.constraints.for.manually.assigned.task=N |
| yfs.displayTaskInfoDetails | Valid values = Y or N Default = N |
Set this property to 'Y' to show the task details (Pick Location,
Item ID and Quantity) in RF mobile terminal when tasktype is defined
to say pick onto equipment. This provides user an ability to determine
whether he needs to carry a pallet/case to pick inventory even before
he goes to the pick location. Example: yfs.displayTaskInfoDetails=N |
| yfs.override.pendingallocations.for.adhocmoves | Valid values = Y or N Default = N |
If Delayed Inventory Allocation Support is configured in a
Node, the default behavior is that system will wait to complete the
pending allocation before creating new tasks. Setting this property
to Y allows ad-hoc move operations on Mobile Application to be processed
by the system without waiting for the Allocate Task agent to complete
the pending allocation. Example: yfs.override.pendingallocations.for.adhocmoves=Y |
| yfs.allow.container.quantity.adjustment | Valid values = Y or N | In case of picking through mobile application if user picks
a full LPN, system currently doesn't provide an option to adjust the
discrepancies. To allow user to adjust the discrepancies in the license
plates, the property needs to be set to Y. If this property is not
set or set to N, system will retain the current behavior. Example: yfs.allow.container.quantity.adjustment= |
| yfs.determine.shipmentgroup.for.shipment | Valid values = Y or N Default = Y |
Set this property to “N” to prevent the shipment group determination during shipment creation. The shipment group for these shipments is determined later by the CREATE WAVE FOR SHIPMENT GROUP agent. |
| yfs.split.reference.across.totes | Valid values = Y or N | If this property is set to “Y”, the system throws a warning when a user picks the same reference, such as shipment, move request, or batch into multiple to totes or target LPNs when performing cart picking through the Sterling Supply Chain Mobile Application. |
| yfs.createwave.lookforsimilarshipments | Valid values = Y | Set this property to “N” to avoid item ID IN clause during the Wave Creation process. It potentially results in an increased performance when a high number of similar shipments are being waved. |
| yfs.suggest.putaway.nearDedicatedLocation | Valid values = Y or N | Set this property to “Y” for allocating the inventory in the non-dedicated location nearer to the dedicated location based on Aisle-Bay-Level logic when the dedicated location is full. |