INCORRECT PRICE PER UNIT ON STOCK TRANSFER INVOICE
(Doc ID 2512849.1)
Last updated on JANUARY 08, 2020
Applies to:PeopleSoft Enterprise SCM Inventory - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On the GST Stock Transfer Invoice page, the field "Price Per Unit in GST UOM" does not show the correct cost expected by customer.
The customer expectation is for this field to show the cost that they have used when creating the transfer and when the unit cost used was X INR (where X is the unit cost amount).
The Transfer price was used on the Express Issue in the Transfer Price Override field, is the Transfer Price Override field= X INR
Then, we can see that the Price Per Unit in GST UOM is Y INR instead of X INR.
Y INR is the Default Actual Cost of the item, on the page Define Business Unit Item page.
1. Check the Item Balance by All Units before transaction.
2. Create an Express Issue for Interunit transfer. Click on “Add”.
3. Input other details. Source BU IND01 and Destination BU IND04. Transfer Price Override field= X INR.
4. Upon saving the request gets shipped.
5. Using Deplete on Hand Qty link quantity depleted.
6. Receiving the stock by putaway. Click on Search. Input source BU i.e. IND01. Select the appropriate line. Receipt line tab.
7. Receipt details tab. Putaway Details tab. Upon Save receipt number generated.
8. Autoputaway processing begins. Process in success. After transaction, check item balance in all units.
9. Preparing Stock Transfer Invoice. Adding new lines. Click on “Add new lines”. Page opens. Input the Source Business Unit and the Shipping ID. Click Search.
10. Select appropriate line and click on return. Line is now populated. Input the Vehicle number , Lorry receipt and the lorry receipt date. Able to select the rate of GST.
11.Here is the problem. Field Price per unit in GST UOM is “Y” and not what we have input at the transaction level i.e “X”. As we transferred the product at X amount.
Because it is picking per unit price as Y amount, GST calculated on this is incorrect.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document