Is It Possible to Set Different GLID When Calling pcm_op_ar_event_adjustment With Reason Code?
(Doc ID 3018415.1)
Last updated on MAY 01, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.6.0 and laterInformation in this document applies to any platform.
Goal
Document says it will use the same General Ledger ID (GLID) for original/adjustment event:
https://docs.oracle.com/en/industries/communications/billing-revenue/12.0/opcode-guide/accounts-receivable-opcode-workflows1.html#GUID-6D166FFA-CC17-4D1A-A0FE-3ACD4E43E526
Reason code validation produces these results:
For all instances where the reason code is valid for the event and associated service, the opcode proceeds with the adjustment.
For each instance where the reason code is not valid, the opcode indicates the failure in the PIN_FLD_RESULTS field for the output flist and describes the problem in the PIN_FLD_DESCR field.
Assigning G/L IDs for an Adjustment
The G/L ID for an adjustment event is assigned like other pre-rated events in the BRM system. PCM_OP_ACT_POL_SPEC_GLID assigns the G/L ID for the adjustment. Based on the event type, this opcode retrieves a G/L ID from the /config/map_glid object. The PIN_FLD_GL_ID field in the /event/billing/adjustment/event object points to the same G/L ID as the original event, ensuring that both the original event and the adjustment are correctly recorded in the general ledger.
Solution
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
Goal |
Solution |
References |