When LOC ID is Specified on CA_BI_INTFC Run Control, The System Should Process Bill Plan's That Match This LOC ID
Last updated on MAY 24, 2016
Applies to:PeopleSoft Enterprise FIN Contracts - Version 9.2 and later
Information in this document applies to any platform.
On : 9.2 version, Billing
Per the documentation received from Oracle the Letter of Credit ID populated in the CA_BI_INTFC run control (LOC_REFERENCE_ID), post PUM 11, should look to the Bill Plan's to determine what transactions to pick up and process through to billing.
From Letter of Credit Draw Enhancements required to support Detailed Award Draws (UG) presentation;
"The CA to BI interface process has been enhanced to select the Letter of Credit ID from the Bill Plan rather than the Billing Options page for grouping in the Billing module. This will allow customers who have multi line Contracts to enter and store multiple LOC Pin Numbers on one Contract so they do not have to set up new Contracts when sponsors change from pooled to detailed draw methods during the award lifecycle. "
This is not what is happening. The Run Control is only picking up transactions associated to contract lines/bill plans that have matching LOC_REFERENCE_ID's on the Run Control, Bill Plan and Billing Options.
The current functionality doesn't support the pooled/non pooled by Contract draw flexibility required by UG.
As long as the CA_BI_INTFC and Bill Plan LOC ID matches, the system should process Bills associated with that project/contract
The issue can be reproduced at will with the following steps:
1. Create a Sponsor with 2 LOC ID associated with it. Say A and B
2. Create a Proposal and Generate the award
3. Make the contract active
4. Create a 'ACT' transaction for the associated Project/Activity and process to generate a BIL row.
5. Run tests with the following combination for LOC in CA_BI_INTFC, Billing Plan Options, Bill Plan
CA_BI_INTFC -- Billing Plan Options -- Bill Plan -- Actual Result -- Expected Result
A --- B ---- A -- Data not processed -- Data should get processed --- Not OK
A --- A ---- A -- Data processed -- Data should processed --- OK
A --- A ---- B -- Data not processed -- Data should not get processed --- OK
B --- A ---- B -- Data not processed -- Data should get processed --- Not OK
Case 1 and 4 are not working as per expectation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms