|
Application Guide for Oracle Self-Service E-Billing (Business Edition) > Split-Bill Detail Transactions >
Split-Bill Detail Transactions
During the ETL data load, Oracle Self-Service E-Billing uses split-billing rules to categorize business and personal expenses. Table 35 lists and describes features of the Business Split-Bill Detail Transactions use case.
Table 35. Split-Bill Detail Transactions
|
|
Name |
Split-Bill Detail Transactions |
Feature Area |
Split-Billing |
Primary User |
Oracle Self-Service E-Billing |
Trigger |
ETL loading of statement data source |
Preconditions |
None |
Alternate Paths |
If no rules are set in Oracle Self-Service E-Billing, then all detail transactions are set to the default category, business. Based on customer requirements, the default might be set to personal or to a custom category at the time of deployment. |
Exception Paths |
None |
Post conditions |
All detail transactions in the statement users is split between business and personal expenses. |
Note |
The service provider defines rules, which are applied in the same order for all companies and organizations. |
Main Path for Split-Bill Detail Transactions
Oracle Self-Service E-Billing applies split-billing rules to the details transaction within each service agreement.
- Oracle Self-Service E-Billing reads the transaction detail.
- Oracle Self-Service E-Billing determines whether the bill number is in the Personal Address Book (PAB) or the Corporate Address Book (CAB).
- If the bill number is in the PAB, Oracle Self-Service E-Billing sets the CDR as a Personal Transaction. If the bill number is in the CAB, Oracle Self-Service E-Billing sets the CDR as a Business Transaction.
- If there are more CDRs to evaluate, the use case begins again.
|
