Renewing Expiring Prices with Joule

As illustrated, Joule allows you to proactively manage price validity periods without the need for complex reports or manual data entry. By leveraging natural language processing, you can simply instruct Joule to find and renew prices based on your specific business requirements.

Now that you understand the value proposition, the next video demonstrates the practical steps to execute this process within the SAP S/4HANA Cloud environment. Watch how to interact with Joule to identify expiring prices, extend their validity, and even apply price adjustments in a few simple steps.

By utilizing Joule for price management, you can:

• Reduce manual effort and the risk of human error.

• Quickly identify and filter prices nearing expiration using natural language.

• Perform mass updates to validity dates and condition amounts simultaneously.

• Monitor the progress of background creation jobs directly within the chat interface.

In the domain of Sales and Distribution, the accuracy of master data is critical for operational continuity. Specifically, pricing condition records dictate the value captured in sales orders and billing documents. A common challenge for Pricing Specialists is the management of validity periods. Prices are often set for a finite time—a fiscal year, a promotion period, or a contract term. When these dates expire without renewal, business processes halt: orders cannot be priced, and invoices cannot be generated.

Joule enables you, as a pricing specialist, to manage price expiration more efficiently by acting as an intelligent orchestration layer between you and the database. Instead of relying on passive reports that you must remember to run, you can engage in an active dialogue with the system. You can ask Joule to fetch prices (stored as condition records for pricing in sales in the system) that will expire soon. This capability shifts the user experience from "navigating and clicking" to "requesting and reviewing".

The core value proposition of using Joule for this task lies in its ability to combine multiple steps into a single fluid interaction. For expiring prices, Joule can help renew them by extending their validity periods and adjusting the condition amounts or ratios according to your requirements. This means that the identification of the problem (expiring price) and the resolution of the problem (renewal and adjustment) happen in the same interface context.

Joule is designed to assist you with tasks throughout the entire process of managing and renewing expiring prices. The scope of its capabilities includes five distinct actions that mirror the pricing lifecycle:

• Fetch and Display: Retrieval of prices approaching expiration based on flexible criteria like dates, organizations, or products.

• Extend Validity: Modification of the "Valid To" date, either by a relative period (e.g., +1 year) or an absolute date.

• Adjust Commercials: Proportional adjustment of condition amounts or ratios for the new validity period (e.g., +3% uplift).

• Mass Creation: Generation of new condition records for the price renewal in a single background job.

• Monitoring: Tracking the job progress and providing direct navigation to the "Manage Prices - Sales" app.

To be able to use this capability, you must have the following business catalog assigned: Master Data - Prices (SAP_SD_BC_PRICE_MANAGE_MC). The Pricing Specialist (SAP_BR_PRICING_SPECIALIST) is one of the business role templates that contain this business catalog by default. Ensuring this prerequisite is met is the first step in adopting this new workflow.

The renewal process is logical and sequential. The tasks should be performed sequentially, starting with identification. You cannot renew what you have not identified. Therefore, the interaction with Joule always begins with a search intent. To search for prices approaching expiration, you must specify a date or time frame. This is the primary filter that tells the system which records are relevant.

A basic query might be "Show expiring prices". However, in a production environment with tens of thousands of condition records, such a broad request is inefficient. For best results, you should also include at least one of the following criteria in your request: Condition type, Sales organization, Distribution channel, Product, Customer, or Customer project ID. By providing this context, you help Joule retrieve a precise and manageable dataset.

If your initial query is too broad, Joule will present a list but may prompt for refinement. Effective communication with the AI involves layering your criteria. Consider the difference between a vague request and a specific one:

• Basic Request: "Show me prices expiring soon." This relies on system defaults and may return irrelevant data.

• Advanced Request: "Show prices for condition types PPR0 and PCP0 that expire on May 1, 2025." This targets specific pricing elements (Price and Cost) for a specific date.

• Organizational Request: "Show prices for sales organization 1710 that are due to expire before December 31, 2025". This targets a specific sales entity.

Once Joule executes the search, it displays the results in a card or list format within the chat window. This allows you to review the data—checking the current rates, the validity dates, and the product assignments—before proceeding to the next step of renewal.

Once you have identified the target prices, you must define the rules for their renewal. Joule offers a high degree of flexibility here, allowing you to manipulate both the timeline and the commercial value of the records. You can extend the valid-to date of the expiring prices to a new date or by a period, such as 30 days, one week, three quarters, or one year. This flexibility caters to different business scenarios, such as short-term extensions for negotiations or long-term annual renewals.

Simultaneously, you can adjust the condition amount or ratio of the expiring prices by applying a specific percentage. This is particularly powerful for handling annual inflation adjustments or strategic price increases. These changes can be made individually for each price or for all prices in the search results at once. For example, you can issue a compound command like "Extend the validity period by 1 month and adjust the condition amounts by -10%".

After you verbally define these parameters, Joule will ask for confirmation. Upon your approval, the system does not process the updates synchronously in the foreground, as this could freeze your screen. Instead, it creates new condition records for the price renewal in a single job. This background processing ensures high system performance and user stability.

You can immediately ask Joule to "Check job progress". Joule will query the background job and report its status (e.g., Scheduled, Running, Finished). Once the job is successful, the loop is closed by verifying the data. You can open prices and job details in the Manage Prices - Sales app directly from a link provided by Joule. This allows you to audit the newly created records to ensure the dates and amounts match your intent.

We have explored how Joule revolutionizes the maintenance of pricing master data. By shifting from manual entry to conversational interaction, you gain speed, accuracy, and ease of use. The process follows a strict sequence: identification of expiring records, refinement of the selection, definition of renewal parameters (dates and amounts), and finally, the execution of a mass creation job.

• Do: Always start your interaction by searching for prices based on a date range. This provides the necessary context for Joule.

• Do: Use specific filtering criteria like Sales Organization or Condition Type to avoid overwhelming the system with results.

• Do: Verify the job status using the "Check job progress" command to ensure all records were created successfully.

• Avoid: Issuing renewal commands without first reviewing the fetched prices to ensuring you are updating the correct records.

• Avoid: Creating overlapping validity periods if your specific condition type configuration does not support it.