Deploying Effective Sales Order Management and Configuration

SAP Sales Cloud Version 2 helps record and view sales interactions related to sales orders. Let's look at the configuration of Sales Orders in SAP Sales Cloud Version 2. Find all the settings for Sales Orders using the path User Menu→Settings→All Settings, then search for "Sales Order."

Alan, as an Administrator, configures and customizes its usage based on Best Run Bikes' requirements.

Configure the following features:

• Number Range
• Document Types
• Item Types
• Party Schema
• Reason for Orders
• Reason for Rejection

The system uses the number range to assign unique numbers to database records, including a predefined set of unique character strings.

Alan configures the following options when keeping the Number Range for sales orders:

1. Edit the Number Range.
2. Keep the Prefix.
3. Keep "From" and "To Range."

The Document Types for sales orders are predefined templates you can use to create sales orders for different types of business scenarios.

Define and choose the Maintenance Mode, the validity of asynchronous pricing (available only for external and internal maintenance modes), the Pricing Date, and the Item Increment values.

Alan configures the following options when keeping the Document Type for sales orders:

1. Create new entries for extra document types for sales orders.
2. Change the description.
3. Select the Maintenance Mode from the drop-down. These options include:
   • Internal: Create and edit sales orders only in SAP Sales Cloud Version 2. These sales orders exist only in SAP Sales Cloud Version 2 and don't support the "Simulate" and "Transfer" features with external SAP systems. Preview and print these types of orders. You can't integrate or replicate these sales orders with external SAP systems.
   • External: Replicate sales orders from external SAP systems and show them in SAP Sales Cloud Version 2. You can only view, not edit them, because the external systems are responsible for creating and managing these sales orders.
   • Internal & External: Replicate sales orders and get continuous updates on them from external SAP systems. It includes creating, replicating, and changing sales orders, with bidirectional data transfer between an external SAP system and SAP Sales Cloud Version 2. Create sales orders in SAP Sales Cloud Version 2 and replicate them to external SAP systems, which then trigger the relevant processes. It automatically changes in one system and updates in the other. These sales orders support the Simulate and Transfer features.
4. Turn on the Internal Pricing switch to use the native pricing in sales orders. The native pricing uses price configurations and pricing master data based on the maintenance mode and scope of each configuration.
5. Enter the increments in the Item Increment by which the line for items needs to increase.
6. Select the source from the Pricing Date drop-down and determine the pricing date for the document type. The following are the options:
   • Current Date: The pricing date of the new sales order defaults to the current date.
   • Requested Date: The pricing date for the new sales order automatically defaults to the requested date specified in the header.
7. Choose the date from the Product Proposal Date drop-down based on which the system proposes the list of products for sales orders.
8. Delete a previously created document type if necessary (This is the Administrator's task).

Item Types are different types of products or services included in a sales order. Item Types determine the function of item categories in sales documents.

Alan configures the following options when keeping the Item Type for sales orders:

1. Create new entries for extra Item Types for sales orders.
2. Change the description.
3. Select the base Item Type from the drop-down and link it with an existing one.
4. Turn on the Pricing Relevant switch to enable the pricing process for the Item Type.

The Party Schema configuration determines the structure and organization of parties involved in the sales order process. It defines relationships between parties, their roles, and the information captured for each party. This configuration improves the ability to manage and track the parties involved in the sales order process.

Alan configures the following options when keeping the Party Schema for sales orders:

1. Edit the Party Role Assignment.
2. Activate or deactivate specific values.
3. Select which party role is mandatory.
4. Review the determination steps for each Party Role and activate or deactivate steps based on the requirements.

Configuring the Reasons for Orders offers a customizable list of options for selecting the specific reasons for changes in a sales order's status. Tailor these reasons to align with the organization's sales processes. It helps gain deeper insights into the underlying factors influencing the progression or outcome of a sales order.

Alan configures the following options when keeping the Reason for Orders:

1. Create new entries.
2. Change the description.
3. Delete existing reasons that you don't need.

Configuring the Reasons for Rejection offers a customizable list of options to indicate the specific reasons for a sales order rejection.

Alan configures the following options when keeping the Reasons for Rejections:

1. Create new entries.
2. Change the description.
3. Delete existing reasons that you don't need.