Vendor_to_wh_schedule_lookup Is Populated with Pack_sizes which Are Not in Warehouse_orderable_unit
(Doc ID 2454507.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Retail Advanced Inventory Planning - Version 15.0.3 and later
Information in this document applies to any platform.
During the pre_scale.sh script, there is a validation step on the scalable_assignment level to set the scalable flag to N where information is missing.
When the supplier or container constraint type is set to PALLETS, the procedure checks that the pallet_multiple table contains information necessary for the supplier/warehouse/commodity. If a pallet_multiple is not found, the IS_SCALABLE flag is set to N.
The pre_scale check, checks for all pack sizes of the commodity that exist in the vendor_to_warehouse_schedule and if it finds at least one date where the pallet_multiple is not available (for either pack size) in the scaling horizon, it marks the scalable assignment as IS_SCALABLE=N.
The pallet_multiple table is interfaced and it contains information only for the warehouse orderable unit pack sizes.
Consider an example where the scaling assignment is flagged as IS_SCALABLE=N and the commodity of this scaling group has 2 pack sizes in Commodity_pack_size Table: 1 & 8
pallet_multiple table contains information for pack_size 8
warehouse_orderable_unit contains information for pack_size 8
vendor_to_wh_schedule_lookup contains information for pack size 8 & 1
The issue is that even though the data are set up correctly the flag is_scalable will be set to N because of the vendor_to_wh_schedule_lookup containing information for pack_size 1 which is not being used.
Steps to reproduce:
1) Insert 2 pack sizes for a commodity in the commodity_pack_size
2) Create an entry in scaling_group, scaling_group_constraint, scaling_group_assignment, scalable_assignment with A vendor-warehouse-commodity combination
2) Insert that 1 specific Vendor-Warehouse-Commodity pack size in Table pallet_multiple (which functionally is the warehouse_orderable_unit)
3) Observe that after the schedule creation, the table VENDOR_TO_WH_SCHEDULE_LOOKUP contains information for both pack sizes
4)Following the flow of pre_scale.sh on step validate_sg_pallet_multiple, observe that the flag will be set to N
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!