Shipment was not fully allocated, difference in work quantity and shipment quantity.

(0) Share

Report

Posted on by JiwanWanji9

365

Hi Experts.

Is there anyway we can keep the shipment qty and work quantity in sync ?

My location directive is setup for certain types of locations as pickable but during SO reservations its irrespective of location type.

So during releasing there is mismatch in work qty and shipment qty as the order is reserved against non-pickable locations.

We have the location failures enabled for SOs as we dont want the system to create work without pick location.

Is there anyway we can reserve SO qty against specific location or auto-adjust the shipment quantity based on work qty?

Thanks.

Categories:

Warehouse Management

All responses (7)

Answers (1)

JiwanWanji9 365 on at

Like (0)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

Thanks again for all your suggestions, really helped.

We deal with 100s of orders and locations per/day so doing it manually would be tough.

Looks like blocking stock at receive bay location and making it available after putaway seems to be better option to avoid unwanted release of order qty, I will have to test the impact of this feature especially from the stock planning perspective.

Believe this must be common requirement across industry, hope all are blocking stocks at inbound locs and change it to available post putway in pickable locations.

Thanks.

Was this reply helpful? Yes No
Suggested answer

AliceBarendregt 1,470 on at

Like (0)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

The load id is defaulted when I click on release load to warehouse and I'm unable to use any filters like open Open loads? Do we have a setup form for this batch job to run for load which are not released?

Apologies, you are right that a default value will be defined and you are not able to override this. For some reason I imagined that there was a batch button available after opening the release load to warehouse dialog. However, it seems like you indeed don't have the possibility to create a batch job for all loads which are partially released OOB. Sorry for any confusion caused!

When I manually release, the work is created for remaining qty but i got an error "load XXXX not valid. Please see Release Errors for details." on release error it says "The load must be assigned a load template. I've defined the item load mapping.

When you navigate to the load you've built as part of your test run, the load template ID is still empty. When this field is empty when you release the load to the warehouse, the above error message will appear. I believe the item load mapping only comes into play when you use the load planning workbench. E.g. if you have configured the item load mapping form the system will automatically populated a load template ID when you are assigning your order lines to a new load via the load planning workbench. However, this config will not be evaluated when you use the release to warehouse process and automatically create a load upon release.

In your scenario, if you want to resolve the error message, I think the only option is to manually assign the load template via the load form.

Besides, for other test runs, a functionality that you could review in order to automatically assign a load template to your load upon release is the new wave load building functionality (https://www.linkedin.com/pulse/learn-how-use-wave-load-building-templates-dynamics-365-karnaukhov/)

Was this reply helpful? Yes No
JiwanWanji9 365 on at

Like (0)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

Thanks again for the help Alice, much appreciated.

I tested above process, got couple of queries.

1. The load id is defaulted when I click on release load to warehouse and I'm unable to use any filters like open Open loads? Do we have a setup form for this batch job to run for load which are not released?

2. When I manually release, the work is created for remaining qty but i got an error "load XXXX not valid. Please see Release Errors for details." on release error it says "The load must be assigned a load template."

I have defined the "Item load mapping".

Thanks.

Was this reply helpful? Yes No
Suggested answer

AliceBarendregt 1,470 on at

Like (1)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

Out of curiosity, for what type of locations will the above logic not work in your case?

Release load to warehouse

To come back to the scenario you forwarded, if the shipment and load was created for 100, the release to load batch job will make sure that the remaining 40 in your scenario will be associated with the same shipment and load, see example below (note: some different quantities have been used).

Figure 1. Shipment creation for a quantity of 20; however, work has only be created for a quantity of 10

Figure 2. Sales order picking work for a quantity of 10 only

A warehouse worker later on puts the remaining 10 quantities away to a suitable picking location. As a result, this quantity can be released now as well. In order to make sure this quantity will be part of the same shipment and load, the release load to warehouse batch job will be used.

Figure 3. Release the load to the warehouse

Note: if it occurs frequently in your case that for a particular reason you have partially released loads you could configure the release to load as a batch job as well.

After releasing the load to the warehouse, the system will create work for the remaining 10 quantities against the same load and shipment.

Figure 4. Sales order picking work for the same shipment and load

Was this reply helpful? Yes No
JiwanWanji9 365 on at

Like (0)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

Thanks Alice, That helps for certain type of location.

Is there anyway we can automate the below process

SO qty 100, all reserved but only 60 available at pickable location.

Shipment created for 100 but work created only for 60.

40 qty is transferred to pickable location, the next release to warehouse batch should create new work for 40 qty against same shipment.

Was this reply helpful? Yes No
Verified answer

AliceBarendregt 1,470 on at

Like (0)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

Hi Jiwan,

Have you considered using the fill entire shipment parameter (https://stoneridgesoftware.com/fill-entire-shipment-in-dynamics-ax-warehouse-management/)?

Besides, to prevent that the system reserves against for instance a receipt location/non-pickable location, have you considered to receive your purchase orders for example against a status which is not equal to available? Assuming that you are reserving your sales order against for instance a status of available, the earlier mentioned option prevents that inventory is being reserved which is not part of your storage location yet. An example of how you could achieve this is by means of the following steps:

1. Create an inventory status of e.g. on-hold

2. Create a disposition code of e.g. on-hold and associate this disposition code with the earlier create inventory status

3. Activate the use default data parameter via your receiving menu item

4. Define the disposition code via the default data form

5. Run a test, receive a PO and validate that the status upon receipt is equal to on-hold

6. Create a sales order and reserve the items. Validate that the items that have just been received are not available for reservation

7. Put the items away to storage/pick locations

8. Run the inventory status change batch job from on-hold to available. Note: configure this batch job in such a way that it only takes for instance storage locations into account

9. Create a sales order and reserve the items. Validate that the items that have been received and putaway are available for sale now

The above status change logic could of course be used in other scenarios as well.

Hope this helps. Any questions, let me know.

Alice Barendregt

Was this reply helpful? Yes No
JiwanWanji9 365 on at

Like (0)

Report

RE: Shipment was not fully allocated, difference in work quantity and shipment quantity.

Re-posting as no response.

Was this reply helpful? Yes No