My Oracle Support Banner

E1: 42: Credit Orders From History Are Not Retrieving The Exchange Rate From Original Order (Doc ID 2886924.1)

Last updated on AUGUST 08, 2022

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.


When credit orders are created from Sales Order History in foreign currency using Work With Sales Ledger Inquiry (P42025), the domestic unit price of credit orders are incorrect. This happens when the exchange rate is different from original sales order history and current exchange rate in the Exchange Rate Master table (F0015A). In the credit order, the exchange rate of order detail is as same as its original sales order. However, the exchange rate of the order header comes from the Exchange Rate Master (F0015A). The domestic Unit price is calculated using the header exchange rate instead of the detail. As a result, the original sales order and its credit order cannot be offset in the Sales Order Detail table (F4211) but also A/R (F03B11) and G/L (F0911).
This issue doesn’t happen when creating credit orders version (P4210/ZJDE0002).
It occurs when creating credit orders from Returned Material Authorization Revisions (P400511)

Steps to Duplicate:

1. Check Currency Exchange Rates between USD and JPY (P0015A)
    Current rate is 1 USD =102 JPY
2. Create a sales order in JPY company (P4210).
    Transaction currency is USD. And populate 100 instead of 102 as Exchange Rate manually.
    Quantity Ordered is 1EA.
    Unit price is 10 USD.
    SO#91 is added.
3. Run Confirm Shipment (P4205)
4. Run Print Invoice (R42565). Invoice number RI#9 is assigned.
5. Run Sales Update (R42800)
6. Check RI#9 (P03B11)
    Foreign amount is 10 USD.
    Domestic amount is 1,000 JPY (=10 USD *100 transaction exchange rate). This is correct.
7. Create a CASE (P90CG504). Case#463 is added.
8. Inquire Case#463 (Work With Case Management P17500). Select it.
9. Select RMA in Related Actions tab and click Add button.
10. Returned Material Authorization Revisions (P400511) screen appears. Populate Branch/Plant that is as same as SO#91.
11. Click Sales Ledger exit to Form.
12. Inquire SO#91 in Sales Ledger Inquiry (P42025)
13. Select the detail line of SO#91 in the grid and click Select Line of Credit Memo exit to Row. After that, click Cancel button.
14. Back to Returned Material Authorization Revision screen. CO#14 is assigned in the grid. Click OK.
15. Check CO#14 using P42101. Inquire CO#14 and select.
      In the Edit Sales Order screen, the exchange rate in the header is 102 which comes from the F0015A. The exchange rate in the order detail is 100 which comes from SO#91.
      This is correct. However, the unit price and the extended price in the domestic currency are calculated using the header exchange rate instead of the detail.
      Check the SO Detail (F4211). The unit price of CO#14 is 1,020 JPY. This is wrong. It should be 1,000 JPY, because its foreign unit price is 10 USD and the exchange rate is 100.
16. Run Confirm Shipment (P4205) for CO#14.
17. Run Invoice Print (R42565) for CO#14. Invoice number RI#10 is assigned.
18. Run Sales Update (R42800) for CO#14 to add the A/R transaction (F03B11).
19. Check A/R transactions RI#9 (original SO#91) and RI#10 (CO#14) (P03B2002).
      In the A/R (F03B11) and G/L (F0911) , the foreign amount (USD) is correct. The exchange rate of 100 is also correct for both RI#9 and 10.
      However, the domestic amount (JPY) of RI#10 is wrong.

      RI#9 / foreign amount 10 USD / exchange rate 100 / domestic amount 1,000 (=10USD*100)
      RI#10 / foreign amount 10 USD / exchange rate 100 / domestic amount 1,020 (=10USD*100)

As a result, the original sales order and its credit order cannot be offset correctly in the F4211 as well as the F03B11 and F0911.



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.