My Oracle Support Banner

EBI 9.2: Project Id Field Grays Out in Revenue Distribution Line if Line-Project Info Page Is Filled Which Stops Saving a Bill With Combo Edit Rule. (Doc ID 2718076.1)

Last updated on JANUARY 20, 2021

Applies to:

PeopleSoft Enterprise SCM Billing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

When trying to create a Standard Invoice in Billing module, where the Project ID ChartField, and related other Fields, (Such as PC Business Unit, Activity ID, Source Type, Category, etc...), from the Revenue Distribution page are greyed out, and cannot be edited if the Line - Proj Info page has data entered into the Project ChartFields section.

A Combination Editing Error Message is thrown by the system when saving the Invoice because the Revenue Distribution Project ID ChartField gets blanked out, and the Combination Editing Rules do not accept a blank Project ID.



REPLICATION STEPS:
-------------------------
  1: Navigate to: Billing > Maintain Bills > Standard Billing
  2: Add a new Invoice transaction from scratch
  3: Go to the Line - Info 1 tab, and enter the Invoice Line transaction data (Description, Quantity, Unit of Measure, etc...)
  4: Click on the Accounting link
  5: This displays the Revenue Distribution page, where one can define the Bill Line Distribution for Revenue, and define all needed ChartFields, including Project ID.
  6: Save the transaction, and confirm that the Invoice ID is being generated
  7: Go to the 'Line - Proj Info' page, and enter Project ChartFields such as PC Business Unit, Project ID, Activity, Source Type, Category, Analysis Type
  8: Save the changes
  9: The system is throwing a Combination Edit Error Message
  10: Go to the Revenue Distribution page, and confirm that the ChartField Project ID is now blank, and grayed out (can no longer be edited)
  11: Query Record PS_BI_LINE_DST for the Billing Invoice affected, and confirm that Field PROJECT_ID is still populated
  12: The problem is therefore online, as the system cannot allow the changes to save, the tables are not being affected if a prior save was done



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
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.