Troubleshooting Inbound Processing Common Problems [ID 1467558.

1]
Modified: Sep 18, 2012 Type: TROUBLESHOOTING Status: PUBLISHED Priority: 3

In this Document Purpose Troubleshooting Steps References

Applies to:
Oracle Warehouse Management - Version 11.5.10.CU2 to 12.1.3 [Release 11.5.10 to 12.1] Information in this document applies to any platform. Inbound Processing Common Problems

Purpose
Troubleshoot common problems facing during inbound processing

Troubleshooting Steps
1. User cannot generate a LPN for the Express receipts and confirmed receipts after giving the shipment number or the ASN but can generate in all other LPN fields. Express receipts / Confirm Receipts - On the first page user will not be able to generate a LPN as that is the field in which user can select the LPN which was shipped as part of the shipment/ASN. User can only do a Ctrl + L. 2. User trying to perform an inspection and receive the message No result found when scan the LPN. During inspection if user get the message No result found when enter the LPN, verify that the receipt user performed did happen. Perform the inquiry on the LPN and verify if the LPN exists in receiving. User cannot perform an LPN inspection if the LPN is not In Receiving or it does not require inspection. To verify this, re-query user purchase order and select the item user is attempting to receive. Then click Shipments, then Receiving Control. The receiving control should be set to Inspection. 3. User get the following message stating INV_ALL_SQL_ERROR If user get a message INV_ALL_SQL_ERROR most likely it will be that there is an invalid PL/SQL package. 4. While performing a receipt user receive the message Online transaction failed. Press any key to continue" If while performing the receipt user get the following message Online transaction failed. Press any key to continue, User should do the following: Verify whether the transaction managers are running. Please log on as system administrator, go to Concurrent, Manager, Administer and query the managers. User should see two entries - Receiving Transaction Manager and RCVTM . Against each of these there should be a non zero value for the actual processes. 5. User unable to see the purchase order in the purchase order LOV. If user unable to see purchase order in the LOV while trying to perform a receipt, check the shipment record when the purchase order was created.

The shipment record for each of the lines has a ship to organization field and it should be set to the organization user want to receive the purchase order in. The purchase order must also be approved and have shipment lines that are Open for Receiving for the current organization. 6. User unable to find blanket purchase order when user trying to perform a receipt. If user unable to see blanket purchase order on the mobile when try to receive against it, please make sure that user have created a release for the same before ready to receive it. 7. For a RMA receipt user receive a No result found message when user scan the RMA. If user receive a No result found for a RMA receipt then please verify that the RMA has the shipping organization set to the receiving organization. For this user will have to look at the shipping tab on the sales order pad. Also verify that the RMA is booked and that it hasnt already been received against. 8 . User trying to perform a transaction but loosing the connection to the server. If anytime loose the connection to the host while performing a transaction, it may be because the class file might not have recompiled when one of the base classes recompiled and changed. So user need to recompile the class file and start the server again. 9. User unable to perform any receipts. Make sure that the purchasing and the inventory periods are open before performing any receipts. User can open the purchasing periods from Purchasing Super User responsibility, Setup, Accounting and the inventory periods from Inventory responsibility in Accounting, accounting periods. Also make sure that the receiving parameters are set for the organization user is receiving the material in. For this please log on as Purchasing Super User and then navigate to Setup, Organization, Receiving Options. Please make sure that user have at least set up the receiving inventory account and there are other default receiving parameters which are required and should be setup prior to receiving. 10. Location is not defaulted in the location field when doing a receipt. When defining the organization please make sure user have given a location on the Organization form otherwise the location will not be defaulted when receiving the material 11. User trying to putaway after performing a direct receipt but it is failing. User have defined putaway rules. If user is trying to perform a put away after a direct receipt, it might fail if user have not defined a default picking rule that can be fulfilled. This is because, after perform a direct receipt, the material is already on hand and user will need to have a picking rule and a put away rule for the allocation to be successful. 12. User receive an error message when scan the LPN for putaway While trying to perform a putaway after a receipt if user get LPN not inspected after scanning LPN, make sure that

user first go and inspect the LPN user trying to putaway. User cannot perform a put away until it has inspected receipts that require inspection. User cannot over ride routing during the receiving process. 13. User unable to generate a LPN/Lot or a Serial Number. The LPN, lot or serial generation may fail because there may not be a sequence assigned to Organization and Item. User need to assign the starting sequence for these. These are again available when user are defining the Inventory Parameters for organization. The serial number has to be padded when giving the starting serial number with the number of zeroes equal to the number of digits user want to keep for user serial numbers. 14. User just performed a receipt but unable to see the transaction on the desktop. If user dont see the just completed transaction in the view transactions form, please make sure that the processing mode for receiving transaction is online. Please refer to the purchasing manual to see how to set this. It is possible that even though the transaction has been completed, it is still in the interface table waiting to be processed if it has not errored out already. It could be that the transaction failed in the background if the processing mode is set to a background mode. Check the Receiving Transaction Summary form to see if there are any transactions that have errors. 15. User trying to perform a direct receipt but getting the error message "Invalid LPN". If trying to perform a direct receipt, after scanning the item user get the message saying Invalid LPN then it might be because user is trying to receive the material into a LPN that has a status of Resides in Receiving. To perform a direct receipt, user must use either a new LPN or an LPN that has a state of Resides in Inventory 16. User do not see any receipt transactions after pressed <F2>. The transaction is committed only when select <Done> on the receipt header or receipt information page. Until user do that, user will not see any transaction. Selecting <F2> rolls back all the data entered after user entered the transaction from the menu and before going back to the menu. 17. User unable to see ASN in the ASN LOV on the mobile device. It is possible the ASN import process failed. Check the progress of the ASN using Oracle Purchasing to determine if there were errors in the ASN processing. 18. User unable to see any LPN information for ASN. If the LPN , lot or serial information from the ASN could not be processed because it voileted uniqueness constraints, User must receive the ASN using an ASN confirmed receipt. If the LPN , lot or serial already existed in the system at the time of import , that part of the import ASN process would have failed. The rest of the ASN import process would succeed, but if any of that information is missing from the ASN information, user cannot perform an Express Receipt on that ASN- the confirmed receipt must be used so that all the information can be properly collected.

Please refer to Note 1458061.1 for more details

References
NOTE:1458061.1 - WMS Brownbag Information: WMS Inbound Data Flow and Datafix Bugs Analysis