EPBM 9.2: Staffing Assignment Contract Line Revenue Plan Has All Amount Allocated on First Event, With Subsequent Events Left With Zero Amount
(Doc ID 2914497.1)
Last updated on DECEMBER 09, 2022
Applies to:
PeopleSoft Enterprise FIN Pay/Bill Management - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
It has been detected that when creating a Staffing Order Assignment with a Billing Plan set as Amount based, and containing multiple Billing Events among which the original Amount is being spread, the subsequent Contract Line Revenue Plan is not generated accordingly. While the Revenue Plan has the same number of Events, the correct Event Dates, and status of Ready, the Amount is all allocated on the first Event line, while the subsequent Events have only zeroes.
The delivered codeline from Application Package PeopleCode object FORS_ASSIGNMENTS.Handlers.FOHandler.OnExecute has the below line stating that the Revenue Recognition Events will assume the same values as the Billing Plan Events:
/* Revenue Recognition Events - Assume same as Bill Plan */
However, the Percent option (Event Define By) still prevails, allocating the Amount incorrectly among the generated Events.
REPLICATION STEPS:
1.- Log into the FSCM Online Application as a Staffing Front Office User
2.- Navigate to: Staffing > Orders and Assignments > Add/Update Orders
3.- Create a new Staffing Order, with Order Type CAR, choose the Customer, and at the Request Resource tab enter a Job Code
4.- Make sure the new Order is set to Unfilled status, and save the changes
5.- Confirm that the system has automatically generated a new Project ID, and Customer ID
6.- Go to the PeopleMatch tab, and define a Candidate/Employee
7.- Save the changes
8.- Click on the Assign puppet icon for the Candidate/Employee just defined
9.- On the Assignment Header page, define the Placement Fee with an amount of 25,000.00 USD
10.- At the Billing tab, notice that by default, the Percent radio-button is selected, and the first Billing Schedule event row has a Percent to 100.00
11.- Manually change the Define Events By to Amount radio-button
12.- Enter a total of 5 Event rows, each with their own Event Date, and spread the original amount with 5,000.00 USD on each row
13.- Save the changes
14.- Go to the Cross Reference tab
15.- Find the link to the Contract Line #, and click on it
16.- The system brings a new window with the Contract Lines information
17.- Go to the Detail tab within the Contract Lines section
18.- Click on the Ready link under the Billing Plan column
19.- The system brings the Billing Plan General page
20.- Go to the Events tab
21.- Confirm that the system displays 5 Events, with proper Dates, Status, and Amounts
22.- Click on the link to ‘Return to General Information’
23.- Go to the Detail tab within the Contract Lines section
24.- Click on the Ready link under the Revenue Plan column
25.- ISSUE: At the Revenue Plan level, confirm that the Events have incorrect Amount values. All 25,000.00 USD value is on the first Event, while the subsequent Event rows have only zero
To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.
The Contract Line Revenue Plan Events contain the incorrect Amount values, and as such, when recognizing revenue, the complete amount will be booked when the first Event is processed, which would be incorrect. This generates incorrect Accounting Entries, and affects Billing, Accounts Receivables, and General Ledger modules.
If the Billing Plan has been defined as Amount based, and every Event has its own amount value, the same logic should be defaulted into the automatically generated Revenue Recognition Plan and its Events as well.
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 |