C OLM - Mapping Billing Dates

This appendix provides information about how dates are set in Oracle Billing and Revenue Management (Oracle BRM) as part of the Bill Fulfillment Order flow.

This appendix contains the following section:

• Section C.1, "How Dates are Set in Oracle BRM"

C.1 How Dates are Set in Oracle BRM

Table C-1 provides information about how dates are set in Oracle BRM. These terms and abbreviations are used in the table:

• ODT: Order Datetime:

  The date that the order was placed by the customer and is captured on the order in the order capture system (Siebel CRM). Siebel CRM defaults this date, but it can be changed by the user.

• RDDT: Requested Delivery Datetime:

  The delivery date requested by the customer; it is captured on the order in the order capture system (Siebel CRM). It is also known as Due Date.

• ADDT: Actual Delivery Datetime:

  The actual delivery date time; it is supplied by the order management system that fulfills the order, and is updated in the order capture system (Siebel CRM).

• Purchase Start Date:

  The date as of which Oracle BRM applies purchase fees.

• Cycle Start Date:

  The date as of which Oracle BRM applies cycle fees.

• Usage Start Date:

  The date as of which Oracle BRM rates usage and applies usage fees.

Table C-1 Mapping Billing Dates

Operation Being Performed in BRM	Dates Set by AIA When the Service is Called	BRM Opcodes Invoked	Expectations of the Order Management System
For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingAccountList service	For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingAccountList service	For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingAccountList service	For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBillingAccountList service
Customer data creation	Oracle AIA uses order date as the effective date for customer data creation	PCM_OP_CUST_COMMIT_CUSTOMER	Pass Order Date coming from Siebel CRM.
For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBilling service	For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBilling service	For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBilling service	For the CommunicationsBillingEBSV1.ProcessFulfillmentOrderBilling service
Single Phase Billing - Billing Fulfillment Promotion Purchase	Oracle AIA passes the Purchase Date as the Valid From date for bundle purchase (that represents purchased promotion). If Purchase Date is null, then it passes Requested Delivery Date and if that is null, it passes no date and Oracle BRM defaults current date.	PCM_OP_SUBSCRIPTION_SET_BUNDLE	Pass Order Date and Requested Delivery Date coming from Siebel CRM. Set Purchase Date to Actual Delivery Datetime.
Single Phase Billing - Billing Fulfillment	If all three of the billing dates are set, then Oracle AIA uses Order Date as Effective Date, and sets respective offset (Order Date - respective billing date). Billing dates are: Purchase Date, Cycle Start Date and Usage Start Date. If any of the three billing dates are not set, then Oracle AIA passes no dates to Oracle BRM and lets Oracle BRM default the Purchase, Cycle Start and Usage Start dates. For purchase of a service bundle, this check for existence of billing dates applies to ALL products and discounts included in the service bundle.	PCM_OP_CUST_MODIFY_CUSTOMER PCM_OP_SUBSCRIPTION_PURCHASE_DEAL	Pass Order Date and Requested Delivery Date coming from Siebel CRM. Set Purchase Date, Start Cycle, and Start Usage to Actual Delivery Datetime to explicitly control setting of billing dates.
Single Phase Billing - Billing Fulfillment. Time Based Account or Service level Subscription Product/Discount Purchase	In addition to setting of billing dates as described previously, if Service End Date is passed, then Oracle AIA additionally sets the Purchase, Cycle and Usage end date offsets (difference between the respective billing date and service end date). If any of the billing dates (Purchase, Cycle, or Usage start) are not set then Oracle AIA uses the Order Date to calculate the Purchase, Cycle and Usage end date offsets (difference between the Order Date and Service End Date).	PCM_OP_MODIFY_CUSTOMER PCM_OP_SUBSCRIPTION_PURCHASE_DEAL	Populate Purchase, Cycle and Usage Start dates (this is required for enabling time-based offerings (TBO). Calculate the Service End Date based on TBO attributes as documented in TBO section. For more information about TBO attributes, see Section 12.6, "Supporting Time-Based Offerings."
Single Phase Billing - Billing Fulfillment. Time Based Account or service-level Subscription Product/Discount Update (of end date due to promotion upgrade or downgrade, or other pricing changes).	If Service End Date is passed (and prior value is set), then Oracle AIA uses that to reset the Purchase, Cycle and Usage end dates.	PCM_OP_SUBSCRIPTION_SET_PRODINFO PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO	Calculate the Service End Date based on TBO attributes as documented in TBO section. Populate prior value to trigger update. For more information about TBO attributes, see Section 12.6, "Supporting Time-Based Offerings."
Single Phase Billing - Billing Fulfillment. Promotion Cancellation	If ADDT is passed, Oracle AIA uses that to set the VALID_TO date in Oracle BRM for the bundle. If ADDT is not passed then Oracle AIA uses the Requested Delivery Datetime. If Requested Delivery Datetime is not passed then Oracle AIA does not set the VALID_TO date.	PCM_OP_SUBSCRIPTION_SET_BUNDLE	Pass Order Date and Requested Delivery Date coming from Siebel CRM. Set Actual Delivery Datetime
Single Phase Billing - Billing Fulfillment Application of Promotion Penalties or MACD One Time Charge (Suspend, Resume, Disconnect, or Move charge) Note - These are processed only in Billing Fulfillment.	If ADDT (on service bundle line) is passed, Oracle AIA sets the effective date to ADDT (from service bundle line). If ADDT (on service bundle line) is not passed, then Oracle AIA lets Oracle BRM default the purchase date (to current date).	PCM_OP_SUBSCRIPTION_PURCHASE_DEAL	Set Actual Delivery Datetime
Single Phase Billing - Billing Fulfillment. Suspend, Resume, or Cancellation of Service or account-level or service-level Subscription Product/Discount.	If ADDT is passed, then Oracle AIA uses that as the effective date for the operation, else it lets BRM default the date (to current date)	PCM_OP_SUBSCRIPTION_SET_PRODUCT_STATUS PCM_OP_SUBSCRIPTION_SET_DISCOUNT_STATUS PCM_OP_CUST_SET_STATUS	Set Actual Delivery DateTime.
Two-Phase Billing - Billing Initiation. Promotion Purchase.	Oracle AIA passes Purchase Date as the Valid From date. If Purchase Date is null, then Oracle AIA passes Requested Delivery Date and if that is null, Oracle AIA passes no date and Oracle BRM defaults current date	PCM_OP_SUBSCRIPTION_SET_BUNDLE	Pass Order Date and Requested Delivery Date coming in from Siebel CRM. Set Purchase Date to Expected Delivery Date.
Two Phase Billing - Billing Initiation. Account-level or service-level Item Type Product Purchase.	Oracle AIA validates that Purchase Date is set to future (based on value of configuration property - FutureTimeThreshold). Uses Order Date as Effective Date, and sets respective offset for each billing date (calculated as Order Date - respective billing date). Billing Dates are - Purchase Date, Cycle Start Date and Usage Start Date.	PCM_OP_CUST_MODIFY_CUSTOMER PCM_OP_SUBSCRIPTION_PURCHASE_DEAL	Pass Order Date coming in from Siebel CRM. Set Purchase, Cycle, and Usage Date to Future (one year out to match default threshold).
Two Phase Billing - Billing Initiation. Account-level or service-level Subscription Type Product/Discount Purchase.	Oracle AIA validates that Cycle Start Date is set to future (based on value of configuration property - FutureTimeThresholdForBillingDates). Uses Order Date as Effective Date, and sets respective offset for each billing date (calculated as Order Date - respective billing date). Billing Dates are - Purchase Date, Cycle Start Date, and Usage Start Date	PCM_OP_CUST_MODIFY_CUSTOMER PCM_OP_SUBSCRIPTION_PURCHASE_DEAL	Pass Order Date coming in from Siebel CRM. To support validation mode, set all three billing dates to the future (one year out to match default threshold). To support latency mode, set Purchase and Usage Start Date to Current, but set Cycle Start Date to Future (one year out to match threshold).
Two-Phase Billing - Billing Fulfillment. Promotion Purchase.	Oracle AIA uses purchase date to reset Valid From date.	PCM_OP_SUBSCRIPTION_SET_BUNDLE	If purchase date had been set to Expected Delivery Date in Billing Initiation, reset purchase date to Actual Delivery Date
Two Phase Billing - Billing Fulfillment. Account-level or service-level Item Type Product Purchase.	If prior values are set, Oracle AIA resets respective billing date by passing in absolute values for each billing date that must be reset. Billing Dates are - Purchase Date, Cycle Start Date, and Usage Start Date.	PCM_OP_SUBSCRIPTION_SET_PRODINFO	Reset all three billing dates to Actual Delivery Datetime (set prior values to trigger update).
Two Phase Billing - Billing Fulfillment. Account-level or service-level Subscription Type Product/Discount Purchase.	If prior values are set, Oracle AIA resets respective billing date by passing in absolute values for each billing date that must be reset. Billing Dates are - Purchase Date, Cycle Start Date, and Usage Start Date.	PCM_OP_SUBSCRIPTION_SET_PRODINFO PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO	To support validation mode, reset all three billing dates to Actual Delivery Datetime (set prior values to trigger update). To support latency mode, reset Cycle date to Actual Delivery Datetime (set prior value to trigger update).
Two Phase Billing - Billing Fulfillment. Time-Based account-level or service-level Subscription Product/Discount Purchase.	If Service End Date is passed, then Oracle AIA uses that to set the Purchase, Cycle, and Usage end dates for products/discounts purchased.	PCM_OP_SUBSCRIPTION_SET_PRODINFO PCM_OP_SUBSCRIPTION_SET_DISCOUNTINFO	Calculate the Service End Date based on TBO attributes as documented in TBO section. Populate Purchase, Cycle, and Usage start dates. For more information about TBO attributes, see Section 12.6, "Supporting Time-Based Offerings."