Allocation Process (RMSSUB_SOSTATUS) Doesn't Convert The Configured Wh In RMS (RIB-RMS Process Flow) (Doc ID 2939756.1)

Last updated on APRIL 04, 2023

Applies to:

Symptoms

On : 16.0.2 version, Other

ACTUAL BEHAVIOR
---------------
Allocation process (RMSSUB_SOSTATUS) doesn't doesn't updating the item_loc_soh expected quantity.


EXPECTED BEHAVIOR
-----------------------
Allocation process (RMSSUB_SOSTATUS) doesn't doesn't updating the item_loc_soh expected quantity.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Have an allocation movement generated from WMS between two warehouses.
2. Validate from the item_loc_soh table that the quantity in the tsf_expected_qty field is correct according to the selected assignment.
3. Generate an 'EX-Expected' movement with the amount generated in the selected allocation in WMS.
4. Verify the integration process in RIB-RMS in which we will be validating:
  a. The canceled amount update was generated in the alloc_detail table.
  b. The quantity in the tsf_expected_qty field has not been updated by subtracting the quantity from the movement generated in the WMS for the receiving location as indicated in the RMSSUB_SOSTATUS packet.
  c. The item_loc_soh table only reflects the return movement for the place of origin of the merchandise.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.