Joule Mass Change of Sales Orders
A Joule transactional capability for SAP S/4HANA Cloud Private Edition that lets an internal sales representative request changes to multiple sales orders in natural language at header, item or schedule-line level. The user states the change and the selection attributes; Joule identifies the matching sales orders and, once the user confirms the number of sales orders to be changed, creates a job that runs asynchronously and applies the changes. SAP documents a fixed list of supported changes, including setting and removing delivery and billing blocks, rejecting sales orders and cancelling rejections, changing payment terms, order reason, billing date, shipping condition, requested delivery date, pricing date, plant and schedule line category, and updating price.
Recorded characteristics
- Function
- SAP documents that Joule enables mass changes of sales orders at header, item or schedule-line level. At header level the documented changes are: set delivery block, set billing block, set requested delivery date, remove delivery block, remove billing block, reject sales orders, cancel rejection, change payment terms, change order reason, change billing date, change shipping condition, change pricing date and update price. At item level: set delivery block, set billing block, remove delivery block, remove billing block, reject sales order, cancel rejection and change plant. At schedule-line level: set delivery block, set requested delivery date, set schedule line category and remove delivery block. The user determines the document level and specifies values for selection attributes (Sales Organization, Distribution Channel, Product, Sold-to Party, Ship-to Party, Created By, Created On, Division, Sales Group, Sales Office, Sales Order Type). Several changes require an explicit qualifying value, for example a delivery block reason, billing block reason, rejection reason, payment term, order reason, shipping condition, pricing type, plant or schedule line category. Item-level and schedule-line changes require the Product attribute; the change-plant use case additionally requires Sales Organization and Distribution Channel. After confirmation a job is created and runs asynchronously to perform the actual changes; a summary of job details is shown on the Joule screen, and full job details are opened in the Monitor Mass Changes of Sales Documents app.
- Data access
- The capability reads and writes SAP S/4HANA Cloud Private Edition sales document data through documented services: SD_MCC_SO_MASS_UPDATE_SRV, SD_MCC_SOW_MASS_UPDATE_SRV and UI_SLSDOCMASSCHANGEREQUEST must be activated, and SAP lists further APIs for the Sales area including API_SALES_ORDER_SRV, API_SALES_QUOTATION_SRV, API_CREDIT_MEMO_REQUEST_SRV, API_DEBIT_MEMO_REQUEST_SRV, API_CUSTOMER_RETURN_SRV, API_SALES_ORDER_SIMULATION_SRV, API_PRODUCT_SRV, API_SALESDOCUMENTS_AI_SRV, UI_SALESDOCUMENTLIST_AI, C_SALESORDERMANAGE_SRV and UI_SLSPRCGCNDNRECORDMANAGE_V2. The documented selection attributes define the data scope used to identify affected sales orders. SAP does not publish, in this documentation, what sales-order content is transmitted to the configured model or how it is retained.
- Actions
- Can take actions
- External actions
- No
- Human confirmation
- Required
- Permission basis
- Mixed
- Administrative control
- SAP documents administrator-side controls rather than end-user enablement: the APIs SD_MCC_SOW_MASS_UPDATE_SRV, SD_MCC_SO_MASS_UPDATE_SRV and UI_SLSDOCMASSCHANGEREQUEST must be activated; SAP Note 3691880 must be implemented; the business role SAP_BR_INTERNAL_SALES_REP must be assigned; and Intelligent Scenario Lifecycle Management (ISLM) must be enabled, with an intelligent scenario configured, deployed and activated in order to see job details on the Joule screen. SAP states that only one model can be activated at a time in the multi-model scenario and that customers choose which model to activate. Onboarding of AI-Assisted Mass Change of Sales Order V2 goes through Requesting Access to SAP Business Technology Platform (SAP BTP). Business AI activation and user assignment are handled through the AI Activation Dashboard in SAP for Me and Central Business Configuration. Parallel processing for the underlying mass change app is defined in Customizing.
- Default state
- Disabled
- Availability
- Documented for SAP S/4HANA Cloud Private Edition. The Release-Specific Capabilities matrix lists Perform Mass Change of Sales Orders as 2022 SP07+, 2023+ and 2025+. SAP also states that for SAP S/4HANA Cloud Private Edition 2023 all SAP Notes in SAP Note 3459573 must be implemented, and that 2022 or 2021 systems require at least 2022 SP07 or 2021 SP09.
- Licensing
- SAP states that use of this AI-assisted feature may require additional entitlement and authorization and directs customers to their account executive. Business AI activation documentation references the AI Unit SKU (8019164, released 20 May 2025) and the legacy AI Unit SKU (8018592). Exact commercial terms are not established in the documentation reviewed.
- External model or provider
- SAP publishes the underlying models in the ISLM scenario table: for the 2025 release, scenario SD_INT_AI with GEMINI (Remote Google Gemini 1.5 Pro), SD_INT_AI_GPT4O (Remote Azure OpenAI GPT-4o) and SD_INT_AI_MISTRAL (Mistral AI hosted and accessed through SAP AI Core); for 2023, 2022 SP07 and 2021 SP09, scenario SD_INT_AI_GEMINI (Remote Google Gemini 1.5 Pro) and SD_INT_AI_GPT (Remote Azure OpenAI GPT-4o), with SD_INT_AI_GPT prioritised when more than one scenario is active. Only one model can be activated at a time.
- Limitations and uncertainty
- Authority is bounded to the documented change use cases on sales orders; SAP does not document Joule-driven mass change of other sales document categories, even though the underlying Mass Change of Sales Documents app supports sales quotations, contracts, customer returns, scheduling agreements, sales orders without charge and credit and debit memo requests. The separate Mass Change of Sales Documents SAP Fiori app and the Monitor Mass Changes of Sales Documents app (F5210) are distinct products, not part of this capability, although Joule job details are viewed there. SAP documents that a job runs asynchronously and that failed jobs can be rescheduled or marked as completed in the monitor app, but does not publish partial-failure semantics, per-record error handling, maximum selection size, or rollback behaviour. No SAP-published record of a specific logging or audit enhancement for this capability was retrievable: the What's New for Joule page now redirects to a separate What's New viewer that could not be read as a static primary document. Model training, retention of sales-order content and immutable audit logging are not established in the documentation reviewed.
Evidence
- Transactional Capabilities (Joule Capabilities Guide)
Supports: External actions · Function · Primary source
Transactional capabilities are described as executing tasks within the SAP solution.
Defines transactional capabilities as tasks carried out directly in Joule without opening the SAP Fiori app.
- Perform Mass Change of Sales Orders (Joule Capabilities Guide)
Supports: Function · Data access · Actions · External actions · Human confirmation · Permission basis · Admin controls · Default state · Licensing · External model · Limitations · General · Primary source
Lists the supported mass changes at header, item and schedule-line level, states that the user determines the document level and selection attributes, and that a confirmed request creates a job that runs asynchronously.
Lists the selection attributes used to identify affected sales orders and the APIs and services required, including SD_MCC_SO_MASS_UPDATE_SRV and UI_SLSDOCMASSCHANGEREQUEST.
Documents write actions on sales orders: blocks, rejection and cancel rejection, payment terms, order reason, billing date, shipping condition, requested delivery date, pricing date, price update, plant and schedule line category, executed by the created job.
Documented actions are confined to SAP S/4HANA Cloud Private Edition sales documents; no third-party system actions are documented.
States that the job is created when the user confirms the number of sales orders to be changed, and requires explicit qualifying values such as block reason, rejection reason, payment term, pricing type or plant.
Requires the business role SAP_BR_INTERNAL_SALES_REP and states that use may require additional entitlement and authorization, with V2 onboarding through SAP BTP access request.
Requires activation of specific APIs, implementation of SAP Note 3691880, and ISLM scenario configuration, deployment and activation, with one model active at a time.
Availability depends on API activation, SAP Note implementation, role assignment and ISLM activation, so the capability is not available by default.
States that the AI-assisted feature may require additional entitlement and authorization.
Publishes the intelligent scenarios and models (Google Gemini 1.5 Pro, Azure OpenAI GPT-4o, Mistral AI through SAP AI Core) and states only one model can be activated at a time.
Documents only sales orders for the Joule mass change use cases.
Primary SAP documentation page for the capability.
- Sales (Joule for SAP S/4HANA Cloud Private Edition)
Supports: Function · Availability · Primary source
Names mass change of sales orders as a Sales use case for Joule in SAP S/4HANA Cloud Private Edition.
States SAP Note and support package prerequisites for 2023, 2022 and 2021 systems.
- Joule for SAP S/4HANA Cloud Private Edition
Supports: Availability · Primary source
Scopes Joule capabilities for SAP S/4HANA Cloud Private Edition from release 2021 onwards, with per-capability release limits.
- Release-Specific Capabilities (Joule for SAP S/4HANA Cloud Private Edition)
Supports: Availability · Primary source
Release matrix lists the capability as supported from 2022 SP07+, 2023+ and 2025+.
- Activating Business AI and Assigning Users
Supports: Permission basis · Admin controls · Default state · Licensing · Primary source
Describes Business AI activation and user assignment through SAP for Me and Central Business Configuration.
Documents the administrator activation dashboard and package activation flow.
Business AI features require explicit package activation and user assignment.
References the AI Unit SKU 8019164 and the legacy AI Unit SKU 8018592.
- Mass Change of Sales Documents (SAP S/4HANA app help)
Supports: Function · Data access · Actions · Admin controls · Limitations · Primary source
Describes the underlying mass change mechanism as a scheduled background job.
Describes search attributes and header, item and schedule-line fields available for mass change in the underlying app.
Confirms changes are applied in bulk through scheduled background jobs.
Documents Customizing settings for parallel processing of mass change jobs.
Shows the underlying app covers further sales document categories that are outside this Joule capability.
- Monitor Mass Changes of Sales Documents (App ID F5210)
Supports: Actions · Limitations · Primary source
Documents rescheduling failed jobs and marking them as completed.
Job outcomes are limited to in process, completed or failed, with rescheduling; per-record failure semantics are not published.