Hi Kathy,

It is not possible to allow transfers for held lots to any specific branch plant. Once a lot is on hold, transfers are restricted across all branches.

Regards,
Mahesh

Hi @User_AKPF8,

This issue 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

Hi @AkkMo,

This issue 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

Hi Mo,

Thanks for raising the Service Request.

We’ll review the details shared in the SR and get back to you shortly with our findings.

Have a nice day.

Regards,
Mahesh

Hi @User_G9BIK,

Yes, in JD Edwards EnterpriseOne, it is possible to configure a single Purchase Approval Route Code that can be applied across multiple companies and currencies.

The approval route itself is not restricted by company or currency. However, in a multi-currency environment, please note that the approval amount defined in the route will be evaluated based on the base currency of the purchase order, not the transaction currency.

As long as the approval limits are aligned with the base currency, the same route code can be effectively used across different companies and currencies.

Hope this clarifies.

Regards,
Mahesh

(Note: If this answers your query, please mark it as answered so it can help other members facing a similar question.)

Hi @User_G9BIK,

Please refer below Oracle KM document for better understanding on approval processing in JDE E1:

E1: 43: Approval Processing in EnterpriseOne (KA857)

Regards,
Mahesh

Hi Amy,

Thanks for the detailed explanation of the scenario.

This behavior is working as designed. The error occurs because a voucher was previously posted, which creates a permanent record in the Supplier Ledger (F0411) associated with the PO number and the earlier supplier.

Once a voucher has been posted, even if it is later voided and the receipt is reversed, the system retains that linkage in the Supplier Ledger. Due to this, the system does not allow changing the supplier on the existing PO.

In such cases, the recommended approach is to cancel the existing purchase order, and create a new purchase order with the correct supplier.

For reference, if the voucher had not been posted, it would have been possible to reverse the voucher, which removes the Supplier Ledger (F0411) record. In that scenario, the supplier on the PO could be updated.

As an alternative option, it is technically possible to remove the related record from the Supplier Ledger (F0411) table directly through SQL. However, this is not a standard or recommended approach, as it involves direct database updates and may lead to data integrity issues if not handled carefully.

If you choose to explore this option, it is strongly advised to:

• Perform thorough testing in a non-production environment first, and
• Ensure proper validation and backups are in place before making any changes in production.

Best regards,
Mahesh