Skip to main content

Hi,

In APPS10, we’re getting this error when trying to perform an inventory movement. Upon checking the inventory location, it appears that it’s because Bay Route Order, Row Route Order and Tier Route Order are NULL.

This is odd as the location’s Bay ID, Row ID and Tier ID are populated so I would expect the route orders to have the same value.

Bay ID, Row ID, Tier ID
Bay Route Order, Row Route Order, Tier Route Order

I’m not able to use a migration job to populate these fields as they’re not stored values. Is there a way to almost refresh/re-execute the package methods to update the route order fields with the correct values? The packages used for these fields are:

&AO.Warehouse_Bay_API.Get_Route_Order, &AO.Warehouse_Bay_Row_API.Get_Route_Order and &AO.Warehouse_Bay_Tier_API.Get_Route_Order

This seems to be happening to quite a lot of inventory location records. Any help would be appreciated.

This is solved now. For some reason, there were missing records in Warehouse Bays, Warehouse Rows, and Warehouse Tiers.

Had a similar challenge and realized this response just stated what had happened.

For anyone with a similar issue…
Check the IFS windows (Warehouse Bays, Warehouse Rows, and Warehouse Tiers) and create the missing Row/Bay/Tier Route Order

Hi,

i am facing something similar in IFSAPP9, i have checked the route order for bin, bay and tier and nothing is null.

 

Server error messages:
c8b6e065-0b26-4aa8-b8e2-750b5f2a1003

Ifs.Fnd.FndSystemException: Unexpected error while calling server method AccessPlsql/Invoke ---> Ifs.Fnd.FndServerFaultException: ORA-01400: cannot insert NULL into ("IFSAPP"."INVENTORY_PART_AVAIL_STOCK_TMP"."BIN_ROUTE_ORDER")

Null value not allowed. (ORA-01400: cannot insert NULL into ("IFSAPP"."INVENTORY_PART_AVAIL_STOCK_TMP"."BIN_ROUTE_ORDER")
ORA-06512: at line 13)
   at Ifs.Fnd.AccessProvider.FndConnection.ParseErrorHeader(FndBuffer buffer, FndManualDecisionCollection decisions)
   at Ifs.Fnd.AccessProvider.FndConnection.UnMarshalResponseHeader(Stream responseStream, FndManualDecisionCollection decisions)
   at Ifs.Fnd.AccessProvider.FndConnection.HandleHttpSuccessResult(HttpWebResponse result, FndManualDecisionCollection decisions, String operation, FndBodyType responseBodyType, Object responseBody)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync)
   --- End of inner exception stack trace ---
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(Object requestBody, Object responseBody, String intface, String operation, FndRequestContext requestContext, FndManualDecisionCollection decisions, Boolean forcedSync)
   at Ifs.Fnd.AccessProvider.FndConnection.InvokeInternal(String intface, String operation, Object requestBody, Object responseBody, FndRequestContext requestContext, Boolean forcedSync)
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommandCollection.Invoke()
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLCommand.ExecuteNonQuery()
   at Ifs.Fnd.AccessProvider.PLSQL.FndPLSQLSelectCommandReader.Read(Boolean prepare)
   at Ifs.Fnd.Data.ADONetProvider.FndAPCommand.ExecuteDbDataReader(CommandBehavior behavior)

Hello @FPayab 

Check and note the current Warehouse and its corresponding Bay under the Window giving you this error.

Then open Warehouse Bays from the navigation pane and search and see if you can find the noted Bay under the noted Warehouse.

Reply


Terms & ConditionsCookie settings