Which object is replicated from SAP S/4HANA to SAP Convergent Charging?

Question

Options

• AProvider contract
• BSubscription order
• CPartner agreement
• DSubscription contract

• A
  88% (21)
• C
  8% (2)
• D
  4% (1)

Explanation

Provider Contract is the object replicated from SAP S/4HANA to SAP Convergent Charging because it carries the commercial terms, pricing parameters, and service details that Convergent Charging needs to perform rating and billing. When a subscription order is processed in S/4HANA, it generates a Provider Contract, and that contract is then pushed to Convergent Charging to drive the actual charging logic.

Why the distractors are wrong:

• B (Subscription Order): The subscription order lives in S/4HANA and triggers the process, but it is not the object sent to Convergent Charging - it produces the Provider Contract, which is.
• C (Partner Agreement): This is not part of the standard S/4HANA ↔ Convergent Charging integration flow; it belongs to partner/channel management contexts.
• D (Subscription Contract): A plausible-sounding distractor, but SAP's integration architecture specifically uses the Provider Contract (not a generic "subscription contract") as the replicated object.

Memory tip: Think of it as "the Provider provides the terms to Convergent Charging" - the Provider Contract is the handoff document that tells CC how to charge, so it must travel from S/4HANA to CC. The subscription order stays behind as the originating business document.

No community discussion yet for this question.