Sales Order Configuration

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

Alan, as an administrator, can configure and customize its usage based on Best Run Bikes requirements.

The following features can be configured:

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

Number range contains a defined set of unique character strings and is used to provide database records with unique numbers. As an administrator, you can define a number range for the sales orders.

Alan can configure the following options when maintaining Number Range for sales order:

1. Edit Number Range
2. Maintain Prefix
3. Maintain From and To range

Sales order document types are predefined templates with which you can create sales orders for different types of business scenarios.

Define sales order document types that you can use to choose the maintenance mode, validity of asynchronous pricing (available only for the external and internal maintenance mode), pricing date, and values for item increment.

Alan can configure the following options when maintaining Document Type for sales order:

1. Create new entries for additional sales order document types
2. Change the description
3. Select the Maintenance Mode from the dropdown.
   • Internal:You can create and edit sales orders only in SAP Sales Cloud Version 2. These sales orders exist only in SAP Sales Cloud Version 2 and do not support the simulate and transfer features using external SAP systems. The orders of this type can also be previewed and printed. These sales orders cannot be integrated with or replicated to external SAP systems.
   • External: You can replicate sales orders from external SAP systems, but cannot edit the sales orders in SAP Sales Cloud Version 2. In SAP Sales Cloud Version 2, you can only display these sales orders, which are created in external systems.
   • Internal & External: You can replicate sales orders and receive continuous updates on them from external SAP systems. You can create, replicate, and modify the sales orders with bidirectional data transfer between an external SAP system and SAP Sales Cloud Version 2. You can create sales orders in SAP Sales Cloud Version 2 and replicate them to the external SAP systems for the relevant processes to run, and the changes from one system automatically reflects in the other. These sales orders support the simulate and transfer features.
     Note

     SAP Sales Cloud Version 2 should be integrated with SAP S/4HANA as a prerequisite for using Simulate and Transfer functionality. SAP Sales Cloud Version2 supports simulation of Sales Orders in SAP S/4HANA and SAP S/4HANA Cloud Private Edition.
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 the pricing configuration.
5. In Item Increment, enter the increments in which the line for items must increase.
6. From the Pricing Date dropdown, select the source to 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 of the new sales order defaults to the requested date from the header.
7. From Product Proposal Date dropdown, select the date based on which the list of products are proposed for sales orders.
8. Administrators can delete a previously created document type.
   Note

   Customized Document Type codes must begin with the identifier Z.

Item types pertain to the different types of products or services that can be included within a sales order. Item types determine the function of item categories in sales documents.

Alan can configure the following options when maintaining Item Type for sales order:

1. Create new entries for additional sales order item types
2. Change the description
3. Select the base item type from the dropdown to associate the item type with an existing item type.
4. Turn on the Pricing Relevant switch to enable pricing process for the item type
   Note

   Customized Item Type codes must begin with the identifier Z.

The party schema configuration determines the structure and organization of parties involved in the sales order process. The party schema allows for defining the relationships between parties, their roles, and the information to be captured for each party. This configuration enhances the ability to manage and track the parties involved in the sales order process.

Alan can configure the following options when maintaining Party Schema for sales order:

1. Edit Party Role Assignment
2. Activate or deactivate certain values
3. Select which party role has to be mandatory
4. Review the determination steps of each party role and activate or deactivate steps based on the requirements
   Note

   With the current release, it is not allowed to create a new party schema and substitute the standard one.

Configuring reasons for orders provides a customizable list of options that users can select to indicate the specific reasons behind a change in the status of a sales order. These reasons can be tailored to align with the organization's sales processes and provide better insights into the underlying factors influencing the progression or outcome of a sales order.

A​lan can configure the following options when maintaining Reasons for Orders:

1. Create new entries.
2. Chane the description.
3. Delete existing reasons if they are not required.
   Note

   Customized Reason for Orders codes must begin with the identifier Z.

Configuring reasons for rejection provides a customizable list of options that users can select to indicate the specific reasons behind a rejection of a sales order.

A​lan can configure the following options when maintaining Reasons for Rejections:

1. Create new entries.
2. Chane the description.
3. Delete existing reasons if they are not required.
   Note

   Customized Reason for Rejection codes must begin with the identifier Z.