[Creating and Managing Payments] When a payment is made by a customer, it can impact their account's overall current balance. Which payment-related entity are financial transactions created directly against?

In Oracle BRM's event-driven architecture, financial transactions are initiated and contextualized by event objects. When a customer payment is processed, a /event/billing/payment object is created first. This event contains all the necessary details for the transaction. The core payment processing opcode, PCMOPPYMTCOLLECT, takes this event object as its direct input to perform the financial transaction. This process then creates other persistent records, such as the /payment and /item/payment objects, and updates the account balance. Therefore, the financial transaction is created directly against the /event/billing/payment object, which acts as the primary source and trigger.

A. Payment Advice: This is a notification about a payment (e.g., a remittance advice), not the BRM entity that initiates the financial transaction itself.
B. Payment: The /payment object is a persistent record that is an outcome of the financial transaction, created during the processing of the payment event.
D. Payment Segment: This is not a standard, recognized entity within the Oracle BRM data model for processing payments or creating financial transactions.
E. Payment Tender: This refers to the method of payment (e.g., credit card, check) and is an attribute within the payment event, not the entity the transaction is created against. ---

1. Oracle Communications Billing and Revenue Management Concepts

Release 12.0 (Part Number E51033-09)

Chapter 3

"About Events".

Section: "How Events Are Rated" - This section states

"Events are the source of all revenue-generating activity in the BRM system... For example

when a customer makes a payment

a payment event is generated and stored in the BRM database. Later

the payment is applied to the customer's account balance." This establishes the event as the primary source entity.

2. Oracle Communications Billing and Revenue Management Concepts

Release 12.0 (Part Number E51033-09)

Chapter 10

"About Payments".

Section: "How Payments Are Processed" - The documentation specifies the process flow: "When a payment is received

BRM creates a payment event (/event/billing/payment) and records the payment information in a /payment object." This confirms the event is the initial object against which the process runs.

3. Oracle Communications Billing and Revenue Management Developer's Guide

Release 12.0 (Part Number E51038-11)

Chapter 25

"Managing Payments".

Section: "Collecting Payments" - The description of the PCMOPPYMTCOLLECT opcode explicitly states that its function is to "process a payment event" and that its input flist requires the POID of the /event/billing/payment object. This directly links the financial operation to the event entity.