Best Of
Re: How to make Item Master F4101 Obsolete?
Hi @User_UT2XF,
The stocking type of an item can be updated to either "O" (Obsolete) or "U" (Use Up) based on business requirements in both Item Master (P4101/F4101) and Item Branch (P41026/F4102).
- Stocking Type ‘O’ (Obsolete):
The system does not allow Purchase Order Entry or Sales Order Entry. However, it allows inventory transactions such as Adjustments (P4114), Issues (P4112), Reclassification (P4116), and Transfers (P4113) to maintain accurate inventory tracking. - Stocking Type ‘U’ (Use Up):
The item cannot be purchased, but existing stock can still be sold until it is depleted.
When an obsolete item is used in Sales Order Entry:
- The warning “Item is Obsolete” (013M) is triggered.
- If a replacement item is defined in the Item Cross Reference, the system substitutes the obsolete item and cancels the original line.
- If no replacement is defined, the sales order line is automatically canceled.
- In Customer Service Inquiry (P4210), the line appears highlighted in blue with status 980 (Canceled in Order Entry).
For further details, refer to Oracle Note: E1: 41: FAQ Obsolete Items - Stocking Types U and O (Inactive Item) (FAQ4976)
Regards,
Mahesh
Re: Qty doesn't update automatically if only the amount is modified during PO receipt for non stock
Hi @User_B57A5,
For either non-stock lines or stock lines, changing only the extended amount during PO receipt does not auto-update or back-calculate the quantity.
If extended amount during PO receipt is changed then unit cost is recalculated based on ordered quantity and entered extended cost. This is standard JDE behavior.
Regards,
Mahesh
Re: Qty doesn't update automatically if only the amount is modified during PO receipt for non stock
Hi @User_B57A5,
These issues would be best handled through a Service Requests (SR), as we’ll need to review your configuration and a issue transactions.
Kindly attach a document with detailed issue information, including screenshots, to your SRs. This will help us troubleshoot efficiently.
Also note that as per Oracle policy, we should keep one Problem/Question per SR so that it becomes easier to track it. I appreciate your understanding on this.
Regards,
Mahesh
Re: F4111 and F41021 Qty Mismatch
It is recommended to run the rollback UBE during non-working hours to avoid any impact on transactions that may still be in progress.
For better understanding, refer Oracle Note: E1: 40: Manual Rollback Process of Item Location (F41021) File (P42210/R42210) (KB616755)
Regards,
Mahesh
(Note: If this answers your query, please mark it as answered so it can help other members facing a similar question.)
Re: E1 31 Do component cost "A2" can cause accounting variations?
Hi @User_MT0SE,
This query would be best handled through a Service Request (SR), as we’ll need to review your configuration and a issue transaction.
Kindly attach a document with detailed issue information, including screenshots, to your SR. This will help us troubleshoot efficiently
Regards,
Mahesh
Re: Receipt Routing for RMA Return Orders without Supplier Item Relationship
Hi @User_KUZ38,
Receipt Routing cannot be used in this scenario unless a Supplier Item Relationship is defined in advance. The system requires this relationship to be set up between the supplier (customer in case of RMA return) and the item before Receipt Routing can be applied.
Regards,
Mahesh
Re: Lot entry trough receipt routing
Hi @User_KUZ38,
Lot information is typically entered during the initial receipt using the Purchase Order Receipts (P4312) program, before the item progresses into receipt routing.
However, if the item has already entered the receipt routing process, the system still provides the ability to capture lot details. This can be done through the Receipt Routing Movement and Disposition (P43250) program. While performing a movement transaction, option 4 can be used to access the Multiple Locations screen, where the lot numbers can be entered.
This approach can be applied at any step within the receipt routing process.
Regards,
Mahesh
Re: Ho do we assign custom transaction reason codes to responsibilities
This works, Thanks a lot
Re: problem with "PSP Driver Workflow Process" WF
Hi Andre,
I already known it.
I also have followed the instructions of doc 788942.1, but this procedure has not resolved the issue.
Thanks for your answer,
Francesco

