In traditional sales cycles, outbound delivery documents are generated subsequent to the creation of a sales order. For my example, when you create a sales order, the system automatically proposes the current date as the date for delivery. After you post the order, the SAP system creates a delivery immediately in the background (Figure 1).

Figure 1

Creation of a sales order in the standard SAP system with options for delivery immediately

I describe a scenario in which you make a business cycle with the sales document configured with the options set to immediate delivery, thereby reducing the steps in the generation of a logistics document (delivery). To view a sales analysis report through the incoming sales order available in SAP S/4HANA, you need to make some inquiries and configure personalization settings to record the layout obtained. These activities are held in the Incoming Sales Order application available in SAP S/4HANA.

To implement sales to order with immediate outbound delivery, you configure the following settings in the IMG in the appropriate sections.

Step 1. Set Up Sales to Order

The configuration of the document type can be performed in a web environment (web browser) or through the traditional SAP GUI.

For my example you use a web browser. First, you need to create a user logon and password to log on to SAP S/4HANA. Enter a name in the User field and a password in the Password field (Figure 2).

Figure 2

Log on to the SAP S/4HANA system

By accessing the system, you exit the main home for the transaction code SPRO in menu path SPRO > Sales and Distribution > Sales > Sales Document > Sales Document Header > Define Sales Document Types (Figure 3).

Figure 3

Define sales document types

After you click the Define Sales Document Types link in Figure 3, the system displays a screen in which you need to copy the standard order into the new sales order (Figure 4). To complete this process, select the document type OR and follow menu options Menu > Edit > Copy As.

Figure 4

Copy the OR sales order type

After you copy the document, you have the new document type and fields that determine how it works in the business cycle. The first step is to enter the nomenclature document class and denomination, keeping SAP’s recommendations in mind to start your configurations settings with the letter Z. For my example, the document class is ZSOR Standard Order – New. Enter this information in the Sales document type field.

In addition to entering a name for the sales document type, populate the following fields for your document (Figure 5):

Figure 5

Configure settings for the sales document

• No. range int assigt. (number range internal assignment) and No. range ext assig. (number range external assignment): These fields are for categories for number ranges to be used internally and externally.

• Item no. Increment (ítem number increments): This field is for the number range jump between each item.

• Reference mandatory: This field refers to whether the document should be a mandatory reference to another document, such as a quote. In my example, leave this field empty.

• Check division: In this field you enter a setting that controls how the system reacts during sales order processing when a division that is entered or proposed at the item level differs from the division in the document header.

• Check credit limit and Credit group: In these fields you specify whether the system runs credit checks and how it responds to the check during sales order processing. In my example, because you use a cash document, do not activate these fields.

Scroll further down the screen and populate the following fields shown in Figure 6:

Figure 6

Settings for the sales document

• Screen sequence grp. (screen sequence group): In this field you enter a setting that controls which screens you see during a particular transaction (for example, creating a quotation). I recommend that you enter AU for sales order.

• Doc. Price Procedure: In this field you enter the key that specifies the pricing procedure for the type of sales document that you are using.

• Incomplet.messages: If you select this indicator and then try to save a sales document in which information is missing, the system advises you that the document is incomplete. For certain types of documents (for example, rush orders and complaints), you can leave the field blank.

• Delivery type: This field contains the delivery type that the system automatically proposes for this type of sales document during delivery processing. For my example enter delivery type LF (delivery).  

• Immediate delivery: The Immediate delivery field is the key for the automatic generation of delivery when recording the Sales Order field. This indicator controls whether the delivery should be created as soon as the order is saved. You can differentiate between whether this process happens generally for all items or just for items that have a confirmed quantity on that date. After you click this field, a pop-up screen appears with three options that you can choose (Figure 7): Create delivery separately, Create delivery immediately, and Create delivery immediately if quantity confirmed for today.

Figure 7

Select the Create delivery immediately option

For my example, choose the option to create the delivery immediately and then press the Enter key. This action displays the dependent entries for copying control (Figure 8). 

Figure 8

Dependent entries for copying control

In this screen you can make your sales document relevant for copying control. For my example, you copy the standard order (ZSOR) to your new document. The copy control in the sales document is responsible for managing the data to be copied from one document to another (i.e., the behavior of the document flow). Click the Yes button.

Step 2. Perform the Business Cycle

You now have a business cycle starting with creating a sales order. To create the sales order, return to the SAP S/4HANA home page and click the Create Sales Order tile (Figure 9). After you select the Create Sales Order tile, the system performs the same activity as the traditional transaction code VA01 present in the SAP GUI environment web transaction. The Fiori app was developed to complete this process with fewer steps than in the standard SAP system. In my example the Create Sales Order app is by default present in SAP S/4HANA (Business Suite).

Figure 9

Select Create Sales Order

After you click the Create Sales Order tile, the system displays the screen shown in Figure 10 in which you input values in the following fields:

Figure 10

Enter values for order type ZSOR

• Order Type: ZSOR Standard Order – New.

• Sales Organization: 1010 Dom. Sales Org DE

• Distribution Channel: 10 Direct Sales

• Division: 10 Product Division 00

• Sales Office: 100 Sales Office 100

• Sales Group: A group of sales people who are responsible for processing sales of certain products or services.

After you enter the data in Figure 10, press Enter to save your entries and create the sales order. This action opens the next screen (Figure 11) in which you enter values for the sales document at the header level in the following fields:

Figure 11

Create a sales order

• Sold-To Party: In this field you enter the customer who orders the goods or services. The sold-to party is contractually responsible for sales orders.

• PO Number: In this field, you enter the number that the customer uses to uniquely identify a purchasing document (e.g., an inquiry or a purchase order).

• PO date: In this field you enter the date the purchase order was posted.

• Payment terms: This is the field for defining payment terms composed of cash discount percentages and payment periods.

Now go to the All Items section of Figure 11 and populate the fields in the Material and Order Quantity columns (Figure 12). The values in these fields form the positions of sales order documents. In the field in the Material column, you enter an alphanumeric key that uniquely identifies the material (e.g., TG11). In the field in the Order Quantity column, you enter the total (rounded) order quantity for this ítem (e.g., 2).

Figure 12

Order quantity

To verify the item’s prices, click the item condition icon located at the bottom of Figure 12 to display the price conditions that make up the value in the next screen (Figure 13). Note that in Figure 13 you see that the fields in the CnTy (condition type) column indicate the condition classes containing this item inserted (material TG11). For example, PPRO Price has the value of 119,00 euros per unit.

Figure 13

Condition types

Now you need to check to see if the sales document has all the required fields before you record it. To complete this process, click the Back button in Figure 13 and select Menu > Edit > Incompletion Log to run the Incompletion Log (Figure 14).

Figure 14

Run the Incompletion Log

After verifying that the document is complete, you are ready to record it. To record the document, click the Save button (Figure 15).

Figure 15

Save the sales order

After you click the Save button, the sytem generates the sales order and outbound delivery documents immediately and displays the message shown in Figure 16.

Figure 16

Message generated by the SAP system

Step 3. Personalize Settings in the Incoming Sales Order Application

SAP S/4HANA has new features, including applications developed on the Fiori platform that can be used on desktop, tablet, and mobile platforms. In my example you use the Incoming Sales Order app. The sales manager can use this app to gain an understanding of the monthly rolling trend of incoming sales orders.

In the Home menu in SAP S/4HANA, you enter the Incoming Sales Order Group applications in your Sales Order Processing Group. This process is explained in the following video:

The app executes the incoming sales order. On the left side a navigation panel allows you to enter additional fields in the report. In my example I entered Sold-To Party Name. Then I entered a filter called Define Filter Values for the Sold-to Party. Thus, you can observe the sales of a particular customer. You observe the values ??in different chart types, culminating with saving your selection.

This process is explained in the following video:

Diony J. Ruiz R.

Diony J. Ruiz R. is an SAP architect and senior consultant at Group Intellego. He has 12 years’ experience in SAP Sales and Distribution and SCE (Supply Chain Execution), Logistic Execution (LE), transportation, and warehouse management picking. He has additional knowledge in SAP MM (Materials Management).

He has worked in industries such as manufacturing, pharmaceuticals, logistics, third-party logistics distribution, services, public government, chemical, maritime and customs, metallurgy, automotive, and mining industries.

His roles have included SAP Consultant Specialist, Project Leader, and Area Leader.

He is an SAP Certified Professional.

 

You may contact the author at dionyruiz@gmail.com.

If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.