Siebel Consumer Goods Guide > Trade Funds > About Configuring Trade Funds >

About Rolling Up Paid Payments


After the end user submits payments, the payments are sent to the back office for processing. After the payments are processed, the status of the payment is changed to Paid. When the payment status is changed to Paid in a back-office system, the following events occur, resulting in the aggregation, or rolling up, of payment data in Siebel Consumer Goods:

  1. CG Payment workflow policy (part of the CG Payment workflow group) is invoked.
  2. Workflow Monitor Agent task is started for the CG Payment workflow group, which monitors the CG Payment policy.
  3. When the payment status is updated to Paid, the workflow process is executed.
  4. The workflow policy invokes the CG Payment Process workflow.
  5. The workflow process invokes the CG Payment Business Service.
  6. The business service rolls up (aggregates) Paid payments in the plan, account promotion, promoted category, and promoted product (if the payment is associated with the promoted product):
    • If a paid payment is associated with an account promotion, the payment is rolled up to the account promotion and the plan that contains the account promotion (if a plan is available).
    • If a paid payment is associated with a promoted product, the payment is rolled up to the promoted product, promoted category that contains the promoted product, account promotion that contains the promoted category, and plan that contains the account promotion (if a plan is available).

When the CG Payment Business Service completes the rollup, you can verify if the workflow succeeded by looking at the Actual Total Spend field of the plan, account promotion, promoted category, and promoted product. The Actual Total Spend field is the sum of all the payments at that level and lower.

Siebel Consumer Goods Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.