E1: 17: 90CD: CRM - Manage Work Order Parts - P90CD015 Does not Update the Actual Billable Unit (ALIAS: ACUNB) Field on the Fly When Changing Advanced Pricing Adjustment Schedules Values (Doc ID 2981598.1)

Last updated on MARCH 09, 2025

Applies to:

Symptoms

When the P90CD015 is used to create service order parts detail lines set with Advanced Pricing Adjustment Schedule, the fields Estimated Billable Unit (Alias: ESUNB), Estimated Billable Amount (Alias: EBILL), Actual Billable Unit (Alias: ACUNB) and Actual Billable Amount (Alias: TOTB) are saved correctly. However, if a change is done on the Adjustment Schedule (e.g. Factor Numeric Value) and the user access the P90CD015 to update the above fields by deleting and then re-applying the Bill. Adj. Schedule (Alias: ASN2), the Estimated Billable Unit and Estimated Billable Amount fields are updated with the new values retrieved from F4072 but the Actual Billable Unit and the Actual Billable Amount fields still show the previous value.
The issue occurs for both stock and non-stock items.

The issue can be reproduced at will with the following steps:

1. P4101 / P41026 - Create a non-stock item (Stk Ty = N, Nl Ty = N).
2. P40073 – Define Preference Hierarchy for the Advanced Pricing setup.
3. P4092 – Create a Type 5 - S&WM Order Detail Group; Use Company and Work Order Cat Code 02 as triggers for the Price Group.
4. P4071 – Define the price adjustment: Target Application = 2 – Service & Warranty Management. Use the previous Order Detail Group and the above Preference Hierarchy. Check the Override Price flag.
5. P4072 – Create the price adjustment detail. Set the field From Level = -99999, Factor Value Numeric = 200, BC = 5 – Add on Amount, Customer, Currency Code, and effectivity dates.
6. P4070 – Define the Adjustment Schedule. Use the previous price adjustment detail defined for e.g. Seq. No. 80.
7. P1782 – Set the Customer Number to use the above Adjustment Schedule during service order creation.
8. P1701 / P1702 – Create an equipment record.
9. P90CD020 – Click on Add button to create a service order; P90CD002 application will be called from the P90CD020 screen.
10. P90CD002 – Add the details of the service order created for the above equipment record.
11. P90CD002 > P90CD015 – Create the parts detail line. As a component, add the previous non-stock item. Populate both Estimated Quantity (Alias: UORG) and Actual Quantity (Alias: TRQT) fields with e.g. ‘1’. By default, the Bill Adj. Schedule is retrieved from the Customer Master. All fields Estimated Billable Unit (Alias: ESUNB), Estimated Billable Amount (Alias: EBILL), Actual Billable Unit (Alias: ACUNB) and Actual Billable Amount (Alias: TOTB) are populated with value ‘200.0000’.
12. P4074 – Price History shows correct details.
13. P90CD015 – Save the parts detail line.
14. P4072 – In the Price Adjustment Detail change the Factor Value Numeric from 200 to 255 USD; BC = 5 – Add on Amount. Save the changes.
15. P90CD020 > P90CD015 – Reopen the service order parts detail line and delete the Bill Adj. Schedule and then, tab down.
16. P90CD015 – Notice the system is re-applying the same Bill Adj. Schedule. Estimated Billable Unit and the Estimated Billable Amount fields are now blank. Actual Billable Unit (Alias: ACUNB) and Actual Billable Amount (Alias: TOTB) fields are still populated with the previous value: 200.0000. Hit Save Changes in the header of SV order Parts. Once the changes are saved, Estimated Billable Unit and the Estimated Billable Amount fields are populated with the new adjustment details: e.g. 255.0000. However, the Actual Billable Unit and Actual Billable Amount fields are still populated with the previous value: 200.0000. This is not correct. All 4 fields (ESUNB, EBILL, ACUNB and TOTB should have been updated with the same / new value. Save the changes.

Changes

Upgrade to UN6, which contains Bug 28363897 - ACTUAL BILLABLE AMOUNT IS NOT UPDATED AS MODIFIED ESTIMATED BILLABLE AMOUNT.

Cause

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