Skip to main content

 I am running into an issue where a one-time product component inside a bundle is dropping off during the contract renewal process in Agentforce Revenue Management (ARM) / Revenue Cloud.

 

Scenario

  • We create a renewal from an existing contract.
  • The bundle contains both recurring and one-time products.
  • During the renewal process, the one-time product remains part of the bundle on both the Renewal Quote and the Renewal Order, which is the expected behavior.

The Problem

  • The issue appears after the Renewal Order is activated.
  • The new Renewal Contract is created successfully, but the one-time product is missing from the contract structure. After investigating, I found that the platform does not create an AssetContractRelationship (ACR) record for the one-time asset on the new contract, even though the ACR was created correctly for the original contract.

What we have already verified/troubleshot:

  1. Asset Generation: An Asset record was successfully generated for the one-time item from the initial order.
  2. Lifecycle End Date: The Lifecycle End Date on the specific one-time Asset record is Blank (it is not expired).
  3. Asset Records: Both Asset State Periods and Asset Action Source records are fully available and populated.

 

Has anyone experienced this behavior? 

 

It looks like the contract activation process is excluding assets associated with a One-Time Product Selling Model Category when creating the Renewal Contract, even though the product is still part of the Renewal Order and bundle. 

 

Is there a known limitation, configuration, or mapping rule that controls whether an AssetContractRelationship is created during contract activation? Are there any fields on the Asset, Order Item, or Product Selling Model that I should verify? 

 

I'd really appreciate any insights or workarounds. Thanks in advance! 

 

@* Salesforce Revenue Cloud * 

2 answers
  1. Jul 7, 8:02 PM

    I'd expect you're seeing expected behavior here. Since it's a one-time product it shouldn't "renew". This was an issue in SF CPQ depending on how you looked at it. I'm unsure if there's a lever you can pull within ARM to address this but you should be able to create a flow that creates the record you're looking for.  

     

    Cheers!

0/9000