Loading

Manufacturing Cloud: Sales Agreement does not auto-activate on start date when custom statuses are used

Publish Date: May 27, 2026
Description

This article explains why an approved Sales Agreement [SalesAgreement] in Salesforce Manufacturing Cloud does not automatically change to Activated when its Start Date is reached, and how to resolve it.

Customers describe this as: "if I create a sales agreement with a start date in the future and approve it before the start date is reached, it does not pass to 'Activated' when the start date is reached" and "Sales Agreement approved but did not change to 'Activated' once the start date was reached". The daily automated activation job runs at 1:00 AM in the org's local time zone and selects only Sales Agreement records whose current Status [Status] picklist value is mapped to the Approved status code [StatusCode]. If the agreement is left in a custom status such as "In Approval", or in any value mapped to Draft, UnderRevision, or another non-Approved code, the daily job skips the record and the agreement stays in its current status indefinitely.

The Sales Agreement object enforces the lifecycle Draft → Approved → Activated through the StatusCode field; the Status picklist values are customizable but must each be mapped to one of the predefined status codes. The issue does not appear when an agreement is approved on the same day as the Start Date because the manual transition into a value mapped to Activated bypasses the daily job. 

Resolution

Use the steps below to ensure approved Sales Agreements are picked up by the daily 1:00 AM activation job and transition to Activated on their Start Date.

Cause 1: Custom Status value is not mapped to the Approved status code

  1. Navigate to Setup > Object Manager > Sales Agreement [SalesAgreement] > Fields & Relationships > Status [Status].
  2. In the Values section, open each custom value used by your approval process (for example, "In Approval", "Approved by Manager").
  3. Open the Status Category mapping and confirm the value's Status Code [StatusCode] is set to Approved. If the value is mapped to Draft or another code, change the mapping to Approved and click Save.
  4. Open the affected Sales Agreement record. On the Details tab, set the Status [Status] field to a value mapped to the Approved status code and click Save.
  5. Wait for the next daily activation job run at 1:00 AM in the org's local time zone, or move the Start Date to the current day and re-save to trigger activation on the next job run.

Cause 2: Custom approval process leaves the record in a non-Approved status

  1. Navigate to Setup > Approval Processes > select the Sales Agreement approval process.
  2. Open the Final Approval Actions and confirm a Field Update sets Status [Status] to a value mapped to the Approved status code [StatusCode]. If the field update sets a value mapped to Draft, Activated, or any non-Approved code, edit it to use a value mapped to Approved.
  3. If the approval process intentionally leaves the record in a custom "In Approval" status for downstream processing, add a final Field Update that sets Status [Status] to a value mapped to Approved before the Start Date arrives.
  4. Click Activate on the approval process.

Manually activate a Sales Agreement that was missed by the daily job

  1. Open the affected Sales Agreement record.
  2. On the Details tab, set the Status [Status] field to a value mapped to the Activated status code [StatusCode].
  3. Click Save.

Confirm the issue is resolved by creating a new Sales Agreement with a Start Date set to the next calendar day, submitting it through the approval process so it lands in a status mapped to Approved, then verifying the next morning (after 1:00 AM in the org's time zone) that the Status field has automatically changed to a value mapped to Activated.

Knowledge Article Number

005385142

 
Loading
Salesforce Help | Article