My Oracle Support Banner

E1: 17: Contract Revisions - P1721 & BSFN B1700550 Do not Save Business Unit (Alias: MCU) Changes in the Header of the Service Contract (Doc ID 2880473.1)

Last updated on JUNE 30, 2022

Applies to:

JD Edwards EnterpriseOne Service Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When using P1720 application to update the Business Unit (Alias: MCU) in the header of a service contract, the system does not retain the changes and upon re-inquiring and reviewing the same contract, the old value for the Business Unit is still displayed.
However, the F1721 - Contract Detail File has the newest value updated to the Business Unit field.
It seems that Bug 28758883 - 'R17024 EQUIP MASTER UPDATE IS UPDATING BU MCU IN EXISTING CONTRACT HEADER P1721' changed the way that system uses BSFN B1700550 and once commenting the code of Bug 28758883 in the BSFN B1700550, the users can update the Business Unit correctly in both service contract header and detail lines.

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

  1. P1720 - select the contract
  2. Open the P1720 details (Row Exit > Contract Header)
  3. In the P1721, form W1721L change the Business Unit (Alias: MCU); Save the changes
  4. Warning 084X - Review Order Header Data Before Accept pops up in P1721, form W1721L; accept the warning
  5. The system then opens the P1721, form W1721A; Press OK to save the changes
  6. P1720 - Row Exit > Contract Header >>>> Notice that the previous value of the Business Unit is still there
  7. Both F1720 and F1721 are still having the original value of the Business Unit field.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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