1 of 157

Soumyadipta Das

Kolkata

13.09.2021

OTC Basic Functions

1

ERP & SAP S/4HANA Overview

2 of 157

Lesson Objectives

Purpose
Use
Challenges
SD Basic Functions-Concept

Partner Determination
Account Determination
Delivery & Transportation Scheduling
Output Control
Text Control
Incompletion Log
Dynamic Item proposal
Material Determination
Listing & Exclusion
Free Goods
Bonus Buy
Cross Selling

2

ERP & SAP S/4HANA Overview

3 of 157

Lesson Objectives

SD Basic Functions-Configuration

Partner Determination
Account Determination
Delivery & Transportation Scheduling
Output Control
Text Control
Incompletion Log
Dynamic Item proposal
Material Determination
Listing & Exclusion
Free Goods
Bonus Buy
Cross Selling

Important Transaction Codes
Additional Info

3

ERP & SAP S/4HANA Overview

4 of 157

SD Basic Functions-Concept

Output Control

Delivery & Transportation Scheduling

Text control

BRF+ Output

Account Determination

Partner Determination

Incompletion Log

Part I

4

ERP & SAP S/4HANA Overview

5 of 157

Partner Determination

SD Basic Functions-Concept

5

ERP & SAP S/4HANA Overview

6 of 157

Business Partners

Forwardin g Agent

Vendor

Others

Contact Person

Employee

Customer

Business Partner

Business partners do play different roles (functions) called Partner Functions in business transactions

6

ERP & SAP S/4HANA Overview

7 of 157

Partner Functions

Sold-to Party

Payer

Bill-to Party

Ship-to Party

Customer

A business partner like Customer can play many roles (functions) in a transaction The partner functions like of Sold-to Party, Ship-to Party, Bill-to Party and Payer are essential for sales document processing

7

ERP & SAP S/4HANA Overview

8 of 157

Partner Functions

Sold-to Party: Sold- to party is the business partner to whom the goods are sold. It needs only sales relevant data in customer master

Ship-to Party: Ship-to Party is the business partner to whom the goods are shipped. It needs only shipping relevant data such as unloading point

Bill-to Party: Bill-to Party is the business partner to whom the bills is sent, needs only the basic data such as address and output procedures

Payer: Payer is the individual or the company who settles the invoice

8

ERP & SAP S/4HANA Overview

9 of 157

Customer Master - Account Group

Account Group controls,

Which fields in the master record are required or optional
Number range for the customer account number (external or internal)
Whether it is one-time account
Default value for pricing procedure indicator

IMG 🡪 Logistics General 🡪Business Partner 🡪Customers 🡪Control

Account Group is a classification of customer master record,

Sold-to Party Ship-to Party

Bill-to Party

Payer

Customer

9

ERP & SAP S/4HANA Overview

10 of 157

Partner Determination

The idea behind partner determination is that the several SD activities from the customer point of view such as receiving of sales order or delivery document, payment of the invoices etc. can be done by separate entities or by a single entity which on holistic basis are customers to the business

The business then needs to decide as to what data pertaining to each business partners need to be maintained and also controlling the activities related to these partners in the entire sales and distribution process

Determination of Partner Functions in SAP can be broadly classified into three areas,

Master Data
Document Data and
Sales Activities

10

ERP & SAP S/4HANA Overview

11 of 157

Partner Determination

Partner function can be set up for :

Customer Master
Sales document header
Sales document item
Delivery
Shipment
Billing header
Billing item
Sales activities (CAS)

The Master data comprises of Customer Master data
The Document data consists of Sales document (header & item), Delivery, Billing (header & item), Shipment.
Sales activities comprise the computer aided selling

11

ERP & SAP S/4HANA Overview

12 of 157

Partner Determination

SD Basic Functions-

Configurations

12

ERP & SAP S/4HANA Overview

13 of 157

Partner Determination - Configuration

Partner Determination is maintained for various Partner Objects

IMG -> SD -> Basic Functions -> Set up partner determination

13

ERP & SAP S/4HANA Overview

14 of 157

Partner Determination

Partner functions are defined first

IMG > SD > Basic Functions > Set up partner determination > Set Partner Determination for Customer Master > Partner functions

The partner type specifies if the partner is a customer, contact person, vendor etc

The error group is the incompletion procedure used by the system to register partner fields that are not filled in the relevant partner object

14

ERP & SAP S/4HANA Overview

15 of 157

Partner Determination

Partner Functions are assigned to Account Groups to ensure only relevant Partner Functions are allowed for a specific Account Group

15

ERP & SAP S/4HANA Overview

16 of 157

Partner Determination

IMG > SD > Basic Functions > Set up partner determination > Set Up Partner Determination for Customer Master > Partner determination procedure

Partner Determination Procedure is maintained for each Partner Object E.g. Customer Master

16

ERP & SAP S/4HANA Overview

17 of 157

Partner Determination

IMG > SD > Basic Functions > Set up partner determination > Set Up Partner Determination for Set Up Partner Determination for Sales Document Header > Partner determination procedures

Partner Determination Procedure is maintained for each Partner Object E.g. Sales Document Header

17

ERP & SAP S/4HANA Overview

18 of 157

Partner Determination

Partner Determination Procedure is assigned with relevant Partner Functions. Eg: Customer Master

Indicates that the system must allow only one entry of this partner function in the partner object

The mandatory field indicates the partner function is mandatory for setting up the partner function for that particular

record

IMG > SD > Basic Functions > Set up partner determination > Set Partner Determination for Customer Master > Partner functions in Procedure

18

ERP & SAP S/4HANA Overview

19 of 157

Partner Determination

Partner Determination Procedure is assigned with relevant Partner Functions. E.g. Sales Document Header

To make the partner functions Not modifiable the sales document

The fields for source and sequence are used where the system needs to obtain a partner record from any associated partner in the sales document other than that of the sold to party

IMG > SD > Basic Functions > Set up partner determination > Set Up Partner Determination for Set Up Partner Determination for Sales Document Header > Partner determination procedures > Partner functions in procedure

To make the partner functions Mandatory in the sales document

19

ERP & SAP S/4HANA Overview

20 of 157

Partner Determination

Partner Determination Procedure is assigned to the Partner Object Eg: Customer Account Group

Partner Determination Procedure

Account Group

IMG > SD > Basic Functions > Set up partner determination > Set Up Partner Determination for Customer Master > Partner determination procedures > Partner Determination Procedure Assignment

20

ERP & SAP S/4HANA Overview

21 of 157

Partner Determination

IMG > SD > Basic Functions > Set up partner determination > Set Up Partner Determination for Sales Document Header > Partner determination procedures > Partner Determination Procedure Assignment

Sales Document Type

Partner Determination Procedure

Partner Determination Procedure is assigned to the Partner Object E.g.: Document Type (Sales Document Header)

21

ERP & SAP S/4HANA Overview

22 of 157

Partner Functions – Customer Master

PARTNER FUNCTIONS IN CUSTOMER MASTER

22

ERP & SAP S/4HANA Overview

23 of 157

Partner functions - Sales order

PARTNER FUNCTIONS

23

ERP & SAP S/4HANA Overview

24 of 157

Account Determination

SD Basic Functions-Concept

24

ERP & SAP S/4HANA Overview

25 of 157

Revenue Account Determination

Whenever a sale is posted to accounting, SAP must determine the account where the revenues and discounts should be posted. For e.g. revenue from domestic sales shall go to an account and export sales shall go to a different account. Depending upon various conditions the relevant accounts shall be determined
Through Revenue Account Determination the billing values are transferred from the SD to FI. Revenue account determination is carried out using the condition technique
The following steps are involved in the Revenue Account assignment :

Check master data relevant for account assignment
Define dependencies for revenue account determination
Define access sequence and account determination types
Define and assign account determination procedures
Define and assign account keys

25

ERP & SAP S/4HANA Overview

26 of 157

Check master data relevant for

Account Assignment

Through check master data relevant for account assignment, one can create Account Assignment Grouping criteria

This grouping then provides the system with an extra variable to determine the required G/L account

After creation of the account assignment groups, they must be assigned to the Material Master and Customer Master records

26

ERP & SAP S/4HANA Overview

27 of 157

Account Determination Procedure - Steps

Account determination table

In the account determination table, you define the criteria on which account determination should depend

Access sequence

Here, you define in which sequence fields are read from the billing document (header and item). An access sequence refers to the permitted field combinations stored in the condition table.

Account determination type

The account determination type is a module of the conditions technique. You have to create at least one account determination type and allocate it to an account determination procedure.

27

ERP & SAP S/4HANA Overview

28 of 157

Account Determination Procedure - Steps

Account determination procedure

The account determination procedure contains the necessary account determination types with which the SAP System can automatically find the revenue accounts

Account key

With the three-digit account key, you finally allocate the revenue account

28

ERP & SAP S/4HANA Overview

29 of 157

Account Determination

SD Basic Functions-

Configurations

29

ERP & SAP S/4HANA Overview

30 of 157

Master data relevant for Account

Assignment

Path : IMG > SD > Basic Functions > Account assignment > Check master data relevant for account assignment

30

ERP & SAP S/4HANA Overview

31 of 157

Define Condition Table

Path : IMG > SD > Basic Functions > Account assignment > Define dependencies for revenue account determination

Fields to select from

Selected Fields

31

ERP & SAP S/4HANA Overview

32 of 157

Define Access Sequence

IMG > SD > Basic Functions > Account assignment > Define access sequence and account determination types > Maintain access seq. for account determination

The SAP standard access sequence is KOFI

To create a new, make a copy of KOFI

Here we assign the condition table we created earlier

The access no signifies the sequence in which the control would move top to bottom

32

ERP & SAP S/4HANA Overview

Define and assign Account Keys

The account key is a 3 character alpha numeric key with a short description
The account keys specify the nature of G/L accounts whether it is sales revenue or discount

The assignment of the account key is the process of assigning the account key to the condition type as done in the pricing procedure maintenance

IMG > SD > Basic Functions > Account assignment > Define access sequence and account determination types > Define and assign account determination procedures > Define and assign account keys

36

ERP & SAP S/4HANA Overview

37 of 157

Assign G/L accounts

IMG > SD > Basic Functions > Account assignment > Define access sequence and account determination types > Define and assign account determination procedures > Assign GL account

Here the assignment of the GL accounts to the condition tables as specified in the access sequence are done

Standard G/L account is determined based on :

Condition Type
Chart of Accounts
Sales Organization
Account assignment group of material
Account assignment group of customer

37

ERP & SAP S/4HANA Overview

38 of 157

Master data to be maintained for Account

Determination

Customer Master

Material Master

Customer Account Assignment Group

Material Account Assignment Group

38

ERP & SAP S/4HANA Overview

39 of 157

Delivery & Transportation Scheduling

SD Basic Functions-Concept

39

ERP & SAP S/4HANA Overview

40 of 157

Delivery & Transportation Scheduling

Shipping activities and transportation can be scheduled automatically in sales documents
Scheduling helps to confirm a delivery date to a customer. Pick/Pack time, Loading time, Transportation Lead time & Transit time are used to determine the delivery date

Order Date

Loading Date

Material Availability Date

Goods Issue date

Transportation Planning Date

Delivery Date

Sales Order

40

ERP & SAP S/4HANA Overview

41 of 157

Delivery Scheduling

Delivery Scheduling includes Pick/Pack time and the Loading time
These times depend on the shipping point that delivers the order item. A shipping point is defined with pick/pack time and loading time. These times can be in terms of days or hours

A sales document type can be made relevant for delivery scheduling or not. When you specify delivery scheduling, the system automatically determines

The pick/pack time and
The loading time

for each schedule line, according to shipping point from which an item is shipped. The system uses the pick/pack time and the loading time to help determine the material availability date & the loading date respectively

41

ERP & SAP S/4HANA Overview

42 of 157

Transportation Scheduling

Transportation scheduling includes the determination of the transportation lead time and transit time
Both time periods are proposed from the route determined for the order item
Sales document type can be made relevant for transportation scheduling or Not. When you specify transportation scheduling, the system proposes the following times for each schedule line:

Transportation lead time
Transit time

These times are defined by route. The system uses the transportation lead time and the transit time to help determine the transportation planning date and the goods issue date respectively

42

ERP & SAP S/4HANA Overview

43 of 157

Delivery & Transportation Scheduling

SD Basic Functions-

Configurations

43

ERP & SAP S/4HANA Overview

44 of 157

Define Scheduling by Sales Document Type

IMG > Logistics execution > Shipping > Basic shipping functions > Scheduling >

Delivery & transportation scheduling > Define scheduling by sales document type

In this configuration activity you define for sales document type whether delivery scheduling and/or transportation scheduling should be carried out.

44

ERP & SAP S/4HANA Overview

45 of 157

Define Scheduling by Shipping Point

IMG > Logistics execution > Shipping > Basic shipping functions > Scheduling >

Delivery & transportation scheduling > Define scheduling by shipping point

Delivery scheduling takes pick/pack times and loading times into account. These times are dependent on the shipping point which is responsible for delivering the order item.

In this menu option you define the type of delivery scheduling for each shipping point

45

ERP & SAP S/4HANA Overview

46 of 157

Maintain Duration

IMG > Logistics execution > Shipping > Basic shipping functions > Scheduling > Delivery & transportation scheduling > Maintain duration

Transit time in Days or hours/minutes

Transportation Lead Time in Days or hours / minutes

Depending on the shipping point, the system uses the lead times either in calendar days or in hours/minutes (if the working hours have been maintained in the referring shipping point)

46

ERP & SAP S/4HANA Overview

47 of 157

Output Control

SD Basic Functions-Concept

47

ERP & SAP S/4HANA Overview

48 of 157

Output Control

Output is the information that is sent to the customer using various media, such as mail, EDI, or fax
Examples include: the printout of a quotation or an order confirmation, order confirmations using EDI, or invoices by fax
Output can be sent for various sales and distribution documents - order, delivery, billing document
Output types include, for example: quotation, order confirmation, invoice
In the output master data, you define the transmission medium, the time, and the partner function for an output type
Output Determination is

carried out using SAP

condition technique

Output mediums

Printer

Fax

48

ERP & SAP S/4HANA Overview

49 of 157

Output Determination

Output Masterdata

Output type :

Partner function Transmission Medium Language

Output

Determination

Procedure

Sales order

Output type : Order confirmation Trans medium : Print output Partner func : AG 3000

Language : EN

PRINT

Order confirmation

Customer : 3000

Qnt

We will deliver Item Material

1 Mat 100

100

Customer Printer

49

ERP & SAP S/4HANA Overview

50 of 157

Output Control

SD Basic Functions-

Configurations

50

ERP & SAP S/4HANA Overview

51 of 157

Output Determination

ORDER

DEIVERY

Maintain Output control for sales order

Maintain Output control for delivery doc.

BILLING

Maintain Output control for billing doc.

Apart from that output can be maintained for Sales Activities !

Output determination is configured through SAP Condition Technique for the following :-

51

ERP & SAP S/4HANA Overview

52 of 157

Maintain Condition Tables

IMG > SD > Basic Functions > Output control > Output determination > Maintain output determination for sales documents

Here we define the combination of fields for which we want to create output condition records in a condition table (Eg: for sales documents)

Field catalogue to select field

Key fields for output determination

52

ERP & SAP S/4HANA Overview

53 of 157

Maintain Access Sequence

The condition tables

The exclusive indicator signifies once the condition record is found, the control will not move to any other access

Condition tables with key fields for output determination

53

ERP & SAP S/4HANA Overview

54 of 157

Maintain Output Types

Output

types

Output Type specifies the kind of output to be produced

A description (maximum of 50 lines long) of a document, folder, distribution list or link
When faxing or printing, you can use parameters in the title, which are then evaluated when the document is sent. As a result, the sent documents can be identified more easily, for e.g., if you have specified the document number as a parameter
If you send faxes via SAP connect, the title appears in your outbox. If you print the message, the title appears in the spool list

54

ERP & SAP S/4HANA Overview

55 of 157

Maintain Output Types

The program that the

system calls up to process the output

Routine to be called up in the processing program

A Form in the sap script is used for page layout

Partner functions defined for output types

55

ERP & SAP S/4HANA Overview

56 of 157

Assign Output Types to Partner functions

Here we assign each partner function to output type and medium. The medium signifies as to how the output is to be produced. For example, 1 is print output whereas 2 is fax

56

ERP & SAP S/4HANA Overview

57 of 157

Maintain Output Determination Procedures

Output types assigned to the procedure

Requirements are routines which signify that the output determination takes into account the output type, if the reqmt. is fulfilled. E.g. :- 2 is order confirmation

Here we maintain output determination procedures. We incorporate the previously created output types within the procedure by clicking “control data” tab

57

ERP & SAP S/4HANA Overview

58 of 157

Assign Output Determination Procedure to

Sales Document Header & Items

Output Determination procedure

58

ERP & SAP S/4HANA Overview

59 of 157

Output Condition Record - Create

Transaction Code: VV11

59

ERP & SAP S/4HANA Overview

60 of 157

BRF+ Output

SD Basic Functions-Concept

60

ERP & SAP S/4HANA Overview

61 of 157

Output Management via BRF+

SAP S/4 HANA a new Output Management approach is in place. The complete configuration differs from the configuration that is used when output management is based on NAST (condition technique). The configuration is based on BRF+. In SAP S/4 HANA, the target architecture is based on Adobe Document Server and Adobe Forms only. For the form determination rules (along with other output parameters) BRF+ functionality is used.

Simplified output control

# Before we know S4 BRF+ as a consultant we should have ECC Output Control hands on.

Purpose

61

ERP & SAP S/4HANA Overview

62 of 157

Prerequisites for BRF+

Uploading XML for importing output determination application in BRF+ (Ref note 2248229).
BRF+ is active and usable
Background RFC configuration has been set up
Adobe Document Server is available – ADS needs to be implemented to allow SAP to fetch PDF properties for rendering output form
KPRO has been maintained – KPRO allows to store PDF attachments on physical location.

Steps for uploading XML

New Transaction code: BRF+ or BRFPLUS

BRF+ workbench will be displayed. For importing output application, we need to change layout to “Expert” mode.

62

ERP & SAP S/4HANA Overview

63 of 157

BRF+ Workbench

63

ERP & SAP S/4HANA Overview

64 of 157

BRF+ Workbench

64

ERP & SAP S/4HANA Overview

65 of 157

BRF+ Output

SD Basic Functions-

Configurations

65

ERP & SAP S/4HANA Overview

66 of 157

BRF+ Configuration

Configuration steps are relevant for all application areas (Sales Order, Purchase Order, Billing Documents and Outbound Delivery)

SPRO Node for output configuration

Define Output types –

IMG Path –> Cross Application Components

-> Output Control -> Define Output Types

-> Output Control -> Assign Output channels

-> Output Control -> Define Determination of Form Master Templates

66

ERP & SAP S/4HANA Overview

67 of 157

BRF+ Configuration

Define Output types –

IMG Path –> Cross Application Components

-> Output Control -> Define Output Types

67

ERP & SAP S/4HANA Overview

68 of 157

BRF+ Configuration

Define Output types –

IMG Path –> Cross Application Components

-> Output Control -> Assign Output channels

68

ERP & SAP S/4HANA Overview

69 of 157

BRF+ Configuration

Define Output types –

IMG Path –> Cross Application Components

-> Output Control -> Define Determination of Form Master Templates

69

ERP & SAP S/4HANA Overview

70 of 157

BRF+ Configuration

Define Output types –

IMG Path –> Cross Application Components

-> Output Control -> Define Determination of Form Master Templates

1.Enter a rule ID, preferably an ID that indicates the logic of the rule.

2.Enter an ordinal number to specify the position of the rule in the determination sequence.

3.Following parameters are optional –

Organization Type
Organizational unit
Channel
Sender country
Form Template

During document output, the master form template is determined by comparing each defined rule with the current data provided by the application. If a parameter is not defined (no value entered), this parameter is considered as a match, and else, system determines the rule where all parameters match. Master form template is used corresponding to this rule.

70

ERP & SAP S/4HANA Overview

71 of 157

BRF+ Configuration

Business Rules for Output Determination

SPRO – > Cross-Application Components -> Output Control -> Define Business Rules for Output Determination (Transaction: OPD)

In this Customizing activity, you can define how the system determines output parameters during document processing. You can define business rules for the determination of output parameters, such as output types, recipients, and form templates.

Continue…

71

ERP & SAP S/4HANA Overview

72 of 157

BRF+ Configuration

Following are the Determinations

72

ERP & SAP S/4HANA Overview

73 of 157

BRF+ Configuration

Transaction: OPD

Select Rules for relevant document, example Purchase Order
Select determination, example Channel to be used for triggering output type.
Input parameters could be changed by adding input columns to determination table. Each determination table consists of input columns (condition columns) and result columns. You can add new input columns via the table settings.
Maintain relevant input combination to determine the channel needed. Multiple channel can be selected for the same combination.

73

ERP & SAP S/4HANA Overview

Texts

Master

Customer Master Central Texts S&D texts

Contact person texts

Material Master Basic texts Sales text

PO Text

Customer Material

info’

Info Record texts

Item

Master Data

Header

•Header Text

•Header notice

•Shipping requirements

•Contractual requirements

•Material Sales text

•Packing note

•Shipping requirements

Document (sales / delivery / Billing)

Texts are proposed from the master records in the sales and distribution documents, if you have made the appropriate setting.
You can integrate standard texts into the sales and distribution documents.
Texts can be copied from a reference sales and distribution document into another sales and distribution document (e.g. from an inquiry into a sales order or from an order into a delivery).
The copying of texts can be made language dependent, if required.
You can change copied texts
In a Sales Document Texts can be maintained as Header or Item Text
Text Determination is carried out by SAP Condition Technique

80

ERP & SAP S/4HANA Overview

81 of 157

Text Sources

Customer – material Texts

Customer Material

Info

Header Texts

Item Texts

Basic Texts

Sales Texts

Purchase Texts

Material Master

Central Texts

Customer Master

Financial Accounting Texts

Sales & Distribution Texts

Contact Person Texts

Sales order

----------

81

ERP & SAP S/4HANA Overview

82 of 157

Text Determination

Select a text object and define the rules for text determination for this object. Text objects are, for example, the sales texts in the customer master record or the sales document header.

Define the permitted text types for every text object. If the text types contained in the standard SAP R/3 System are not sufficient, create new ones.

Define the access sequences. This way, you define how the SAP System should determine the texts for a text type.

``

Group the text types together in text determination

procedures.

Allocate the text determination procedures so that a

procedure applies to the following criteria in each case: account group – customer; sales & distribution document; item category

The following steps are involved in text determination

82

ERP & SAP S/4HANA Overview

83 of 157

Text Control

SD Basic Functions-

Configurations

83

ERP & SAP S/4HANA Overview

84 of 157

Text ID (Text Type)

The text ID defines the various types of texts related to a text object

Click here to maintain Text ID

Text Object Text Id

IMG > SD > Basic Functions > Text Control > Define Text Types

84

ERP & SAP S/4HANA Overview

85 of 157

Text Procedure

Click here to maintain

/ change Text Procedure

Text Procedure

Text Procedure identifies a group of text types that you can use in, for example, a sales document header. The text procedure also determines the sequence in which the text types appear in the document

85

ERP & SAP S/4HANA Overview

86 of 157

Access Sequence

Access sequence identifies an access sequence that the system uses to determine which text (s) should be copied into a sales, shipping, or billing document
Determines

Which text types are llowed
The sequence in which the text types are checked by the system

When you create a new access sequence, the system automatically assigns a new number

86

ERP & SAP S/4HANA Overview

87 of 157

Text Procedure Assignment

Here we can assign the text procedures to sales document types or item categories or account groups

IMG > SD > Basic Functions > Text Control > Define and assign Text determination Procedure

87

ERP & SAP S/4HANA Overview

88 of 157

Incompletion Log

SD Basic Functions-Concept

88

ERP & SAP S/4HANA Overview

89 of 157

Incompletion Procedure

The data maintained in Sales document is passed through to delivery and finally to billing. So it is imperative that SAP has a specific control system to see that the requisite data is maintained at different SD levels.

For this reason, SAP has an incompletion procedure to highlight missing data in sales and delivery documents as well as sales activities and partner functions

89

ERP & SAP S/4HANA Overview

90 of 157

Incompletion Procedure - How it works…?

Order

0001

Sold to party Order no.

200

Item 10

Material M1 Plant

Schedule line

Item 20

Material M2 Plant P1

Schedule line

X

Item 10

Missing Data Plant

Order : Incompletion log

Incompletion log is called up

When saved

When called up from menu

90

ERP & SAP S/4HANA Overview

91 of 157

Status Groups

It is a grouping of different kinds of status. A group can consist of any combination of general, delivery, billing, & pricing status
Using status groups, you can determine which status messages appear when you process different documents. The status group also provides the link, during sales order processing, between the incompletion log (where the system prompts you to enter data in required fields) and the header and item status screens in the sales document
The fields that appear in the incompletion log are defined for each sales document by an incompletion procedure, where you assign a status group to each field
Then, during sales order processing, if you omit to fill a required field, the system prompts you for the relevant information in the incompletion log records the status messages in the sales document, according the assigned status group

91

ERP & SAP S/4HANA Overview

92 of 157

Defining Incompletion Procedure

Incompletion groups

Sales header

✔Sales item

Sales schedule line
Delivery header
Delivery item
Partner
Sales activity

Here we group together the fields that are to be checked for completeness

For every field in the procedure, we

also have to define whether warning message is to be issued during processing if no data is entered in this field

Incompletion Procedure is carried out by SAP condition Technique. It is defined for various incompletion groups

92

ERP & SAP S/4HANA Overview

93 of 157

Incompletion Log

SD Basic Functions-

Configurations

93

ERP & SAP S/4HANA Overview

94 of 157

Incompletion Procedure – Configuration

The following steps are involved in configuring incompletion procedure

Define incompletion procedures

Assign incompletion procedures

Define status groups

94

ERP & SAP S/4HANA Overview

95 of 157

Define Incompletion Procedure

IMG > SD > Basic Functions > Log of Incomplete Items > Define incompletion procedures

Define an incompletion procedure, for example 11 - procedure for sales order

Select an incompletion group & click procedures to define a procedure

95

ERP & SAP S/4HANA Overview

96 of 157

Define Incompletion Procedure

In the next step in incompletion procedure definition, we assign the fields to the procedure which should be checked for incompleteness as also if any warning message is to be issued if there are no data in the fields.

The fields assigned to procedure to check incompletion

The screen in which the correction can be done

The status groups, to be discussed later in this section

if checked gives a warning message if the field has no input

96

ERP & SAP S/4HANA Overview

97 of 157

Assign Incompletion Procedures

Incompletion procedures are assigned to various incompleteness objects

IMG > SD > Basic Functions > Log of Incomplete Items >Assign incompleteness procedures

97

ERP & SAP S/4HANA Overview

98 of 157

Define Status Groups

IMG > SD > Basic Functions > Log of Incomplete Items > Define Status Groups

For example, setting “General” status in the status group and assigning the same to a field will cause the sales document to be incomplete, but will allow the document to be further processed

In the status groups we define which functions may be carried out by an incomplete SD documents or items

98

ERP & SAP S/4HANA Overview

99 of 157

SD Basic Functions-Concept

Free Goods

Listing & Exclusion

Cross Selling

Bonus Buy

Material Determination

Part II

Dynamic Product proposal

99

ERP & SAP S/4HANA Overview

100 of 157

Dynamic Product proposal

SD Basic Functions-Concept

100

ERP & SAP S/4HANA Overview

101 of 157

Dynamic Product Proposal

Product A

Product B

Product C

Product D

Product E

SALES DOCUMENT PROCESS

Product Proposal

Business

Customer

A product proposal is a list of products for a specific customer that is automatically proposed during sales document processing. The business can decide for themselves which materials should be displayed as product proposals in the sales document. We can also determine the sequence in which the materials appear in the product proposal.

101

ERP & SAP S/4HANA Overview

102 of 157

Dynamic Product Proposal

During sales document processing, the system displays a product proposal in the item overview according to the customer and the business transaction
It displays the material number, material description, and historical order quantities in the sales unit last used. To use a material again, you just have to copy it
The system does not run the standard checks (pricing, availability, incompletion, material determination, free goods determination and so on) until you have entered the order quantities

x

Sales order

Order no Customer no

101

2000

Material no E600

E700

Material description Qnt Cds 25

Dvds 45

Customer

Business transaction E.g..- Sales order

Product pro. parameters

+

Product proposal

102

ERP & SAP S/4HANA Overview

103 of 157

Dynamic Product Proposal

SD Basic Functions-

Configurations

103

ERP & SAP S/4HANA Overview

104 of 157

Dynamic Product Proposal

The following steps are involved in configuring dynamic product proposal

ORDER

Customer master

1 Define Customer Procedure for Product Proposal

2 Define Document Procedure for Product Proposal

PP

Procedure

Sales doc. type

“OR”

4 Assign Document Procedure to Sales Doc. Type

3 Define PP Procedure & Determine Access Sequence

PP

Procedure

104

ERP & SAP S/4HANA Overview

105 of 157

Customer Procedure for Product Proposal

IMG > SD > Basic Functions > Dynamic product proposal > Define customer procedure for product proposal

PP Cust Proc field in Customer master.

Define the Customer Procedures for Product Proposal

105

ERP & SAP S/4HANA Overview

106 of 157

Document Procedure for Product Proposal

Assign the Document Procedures

to Doc. Types

Define the Document Procedures for Product Proposal

IMG > SD > Basic Functions > Dynamic product proposal > Define document procedure for product proposal

106

ERP & SAP S/4HANA Overview

107 of 157

Table of Origin (Source Indicator) for PP

Source Indicator that specifies which data source (for e.g., order history, item proposal, listing) system uses to determine the product proposal. The indicator is displayed in the sales document
If the same material for the product proposal is determined from several data sources (for e.g., from both the listing & the order history), the system always displays the data source that it accessed first

IMG > SD > Basic Functions > Dynamic product proposal > Maintain Table of Origin for Product Proposal

107

ERP & SAP S/4HANA Overview

108 of 157

Dynamic PP Procedure

IMG > SD > Basic Functions > Dynamic product proposal > Define PP procedure and determine access sequence

Number of periods that should be displayed in sales document

Source Indicator

Name of function module that is to be called up within the access sequences for the product proposal procedure

108

ERP & SAP S/4HANA Overview

109 of 157

Dynamic PP Procedure Determination

Sales Organization

Distribution Channel

Division

Cus PP Procedure

PP

Procedure

During a sales document processing the PP Procedure is determined for the combination of Sales Area and the Cus PP Procedure

IMG > SD > Basic Functions > Dynamic product proposal > Maintain Procedure

Determination

109

ERP & SAP S/4HANA Overview

110 of 157

Material Determination

SD Basic Functions-Concept

110

ERP & SAP S/4HANA Overview

111 of 157

Material Determination

With material determination, the material entered is replaced automatically by the material found during document creation

This material determination is dependent on the sales document and can, for example, be used in a promotion when a product is only to be sold with special packaging

During order processing, the system can then automatically exchange the material with the normal packaging for the material with the special packaging for a given period of time

111

ERP & SAP S/4HANA Overview

112 of 157

Material Determination

112

ERP & SAP S/4HANA Overview

113 of 157

Material Determination

Determination procedure

Sales doc.

type

Substitution strategy

x

Sales order

Description Qnt

Order no : 100 Customer : 200

Item Material

1 M001

Toothpaste

25

1

M002

combo pack

25

It is carried out using condition technique
It can be achieved just against any key word & not necessarily against an existing material no. It can also be considered against available quantities of the materials to be replaced

113

ERP & SAP S/4HANA Overview

114 of 157

Material Determination

SD Basic Functions-

Configurations

114

ERP & SAP S/4HANA Overview

115 of 157

Material Determination

The following steps are involved in configuring material determination

	Defining Condition Tables, Access Sequence, Condition Type and Maintaining Determination Procedure Assigning Determination Procedure to sales document types.
	3 Define Substitution Reasons and Strategies.

115

ERP & SAP S/4HANA Overview

116 of 157

Material Determination

IMG > SD > Basic Functions > Material determination > Maintain pre requisites for material determination

Maintain pre requisites for determination procedure

Maintain Determination Procedure

116

ERP & SAP S/4HANA Overview

117 of 157

Material Determination

IMG > SD > Basic Functions > Material determination > Assign procedures to sales document type

Assign Determination procedures to sales document types.

Determination procedure

Sales doc type

117

ERP & SAP S/4HANA Overview

118 of 157

Substitution Reasons

IMG > SD > Basic Functions > Material determination > Define substitution reasons

This is a reason for material substitution and specifies the reason why the system automatically carried out material substitution

Controls whether product selection should occur automatically in the background or whether the alternative materials should be offered for

selection in a dialog box

Controls whether the outcome of product selection should replace the original entry or whether it should be recorded as a sub item of the original entry

Indicates whether the system prints the name or number of the original material (before substitution) on corresponding output (for example, on order confirmations).

Indicates whether the system displays a warning message before substituting a material.

118

ERP & SAP S/4HANA Overview

119 of 157

Condition Record - Create

T Code : VB11

Material entered in the order

Material for Substitution

119

ERP & SAP S/4HANA Overview

120 of 157

Listing & Exclusion

SD Basic Functions-Concept

120

ERP & SAP S/4HANA Overview

121 of 157

Listing & Exclusion

With material listing or exclusion we can control which materials can be sold to each customer
If a material listing is created for a customer, the customer can only buy the materials contained in the list. The system does not allow any materials to be entered if they are not contained in the material listing
Material exclusion lists which materials a customer cannot buy

121

ERP & SAP S/4HANA Overview

122 of 157

Listing & Exclusion

122

Listing & Exclusion

Procedures assigned to sales document types

Maintain Procedure

IMG > SD > Basic Functions > Listing & Exclusion

126

ERP & SAP S/4HANA Overview

127 of 157

Condition Record - Create

T Code : VB01

Listed / Excluded materials

127

ERP & SAP S/4HANA Overview

128 of 157

Free Goods

SD Basic Functions-Concept

128

ERP & SAP S/4HANA Overview

129 of 157

Free Goods

Buy 1 get 1

free

BUSINESS

Customers

Free goods refer to the process where the business offers a scheme where the customers can get free goods if they buy certain products of certain quantities

Buy 1 get 1 free

129

ERP & SAP S/4HANA Overview

130 of 157

Free Goods

Inclusive	The customer only pays for some of the goods requested. The rest of the goods are free of charge. Two out of eight eggs are free goods. Therefore, if you order 8 eggs, 8 will be delivered and you will not be charged for 2 of them. So in this case, you have ordered an inclusive bonus quantity.	2 from 8
Exclusive	The customer pays for the goods ordered and is given extra goods free of charge. The exclusive bonus quantity is also called exclusive free goods and means that in addition to the purchase order, a certain quantity of materials are guaranteed as free goods. In other words, a larger quantity is delivered than is ordered, whereby no charge is made for the additional quantity delivered.	3 + 1
Exclusive different material	The materials delivered as free goods do not necessarily have to be the same as the materials orders. When a customer orders 3 large trays of eggs, the customer would be offered a chicken for free!	3 + 1
The free goods can also be in the form of discount to the extent of the goods value The free goods quantity can be defined as a quantity proportional to the sold quantity. For the delivery you can control whether the free goods are processed independently or whether they are only copied to the delivery for partial delivery or full delivery.

130

ERP & SAP S/4HANA Overview

131 of 157

Free Goods

SD Basic Functions-

Configurations

131

ERP & SAP S/4HANA Overview

132 of 157

Free Goods

The following steps are involved in free goods determination

Condition technique

1 Condition Technique – Defining Tables, Access Sequence,

Condition Type and maintaining Free Goods determination procedure

Item categories

2 Determine item categories for free goods

Free goods pricing

3 Control free goods pricing

Copy control

4 Maintain copy control

132

ERP & SAP S/4HANA Overview

133 of 157

Free Goods Determination Procedure

IMG > SD > Basic Functions > Free goods > Condition technique for free goods

Access sequence for free goods

Access sequence assigned to Condition type.

133

ERP & SAP S/4HANA Overview

134 of 157

Free Goods Determination Procedure

Pricing procedure for free goods

Pricing procedure determination for

free goods

Free goods Pricing

Procedure Determination is dependent on

Sales org
D chnl.

▪Division

Doc. Pri. Pro.

▪Cust. Pri. Pro.

134

ERP & SAP S/4HANA Overview

135 of 157

Determine Item Categories for Free Goods

IMG > SD > Basic Functions > Free goods > Determine item categories for free goods items

The Item Category for Free Goods (standard TANN) is determined as below. The determination combination has Usage as FREE and a Higher Level Item Category as TAN

135

ERP & SAP S/4HANA Overview

136 of 157

Control Free Goods Pricing

Pricing for Inclusive Free Goods without item generation

IMG > SD > Basic Functions > Free goods > Control free goods pricing

136

ERP & SAP S/4HANA Overview

137 of 157

Maintain Copy Control

IMG > SD > Basic Functions > Free goods > Maintain copying control

We maintain the copy controls at item category level. The control with the 'Structure/ NewFreeGoods' field is most relevant for free goods. Here we can control whether the free goods should also be transferred when you copy from one order to another, or whether we should re-determine them.

137

ERP & SAP S/4HANA Overview

138 of 157

Free Goods – Condition Data

VBN1 – Create Free goods VBN2 – Change Free goods VBN3 – Display Free goods

Screen display

138

ERP & SAP S/4HANA Overview

139 of 157

Bonus Buy

SD Basic Functions-Concept

139

ERP & SAP S/4HANA Overview

140 of 157

Bonus Buy

Bonus buys are deals, which grant special prices, discounts or free articles, if certain prerequisites and general conditions are fulfilled
In the Bonus Buy, Coupons can be assigned as prerequisite
Coupons in SAP R/3 Retail are treated like articles

Business

Customers

140

ERP & SAP S/4HANA Overview

141 of 157

Bonus Buy

Bonus buy deals are :-

Based on certain prerequisites
Based on certain scales
Resulting in certain conditions being granted
General requirements

If you buy 5 promotion articles ...

... spending over a total amount of 50 USD...

We‘ll give you a certain article with 10 % discount ...

... 5 % discount for 3 articles ... 10 % discount for 5 articles...

141

ERP & SAP S/4HANA Overview

142 of 157

Bonus Buy

SD Basic Functions-

Configurations

142

ERP & SAP S/4HANA Overview

143 of 157

Bonus Buy

The following steps are involved in configuring bonus buy

1 Defining Condition Tables, Access Sequence, Condition Type

Maintaining Pricing Schema.

Activation of Bonus Buy Determination.

143

ERP & SAP S/4HANA Overview

144 of 157

Bonus Buy - Configuration

Condition table in access sequence

IMG > SD > Basic Functions > Bonus Buy

144

ERP & SAP S/4HANA Overview

145 of 157

Bonus Buy Procedure

Activation of Bonus Buy Determination

Bonus Buy

IMG > SD > Basic Functions > Bonus Buy

145

ERP & SAP S/4HANA Overview

146 of 157

Cross Selling

SD Basic Functions-Concept

146

ERP & SAP S/4HANA Overview

147 of 157

Cross Selling

Cross selling allows us to establish, for example, whether a given product is always sold in combination with another product or several other products

Knowledge about such relationships

between products opens up new opportunities in the way we arrange your product offering

We can then place the products concerned adjacent to each other in our catalog, on the supermarket shelf, or indeed in the Web shop, or conduct advertising campaigns aimed specifically at promoting these products

147

ERP & SAP S/4HANA Overview

148 of 157

Cross Selling

SD Basic Functions-

Configurations

148

ERP & SAP S/4HANA Overview

149 of 157

Define Cross-selling Determination Procedure

IMG > SD > Basic Functions > Cross selling > Define determination procedure for cross selling

149

ERP & SAP S/4HANA Overview

150 of 157

Maintain Customer / Document Procedure

IMG > SD > Basic Functions > Cross selling > Maintain customer/document procedures for cross selling

Define customer procedures for cross selling

Define document procedures for cross selling

Assign document procedures to document types

150

ERP & SAP S/4HANA Overview

151 of 157

Define / Assign Cross Selling Profile

IMG > SD > Basic Functions > Cross selling > Define and assign cross selling profiles

Define Cross Selling Profile

Assign profiles

151

ERP & SAP S/4HANA Overview

152 of 157

Customer Master data for Cross Selling

T Code : VD02

The field, 'PP cust Proc' in Customer Master Data needs to be updated in if the Cross-Selling is to be active

152

ERP & SAP S/4HANA Overview

153 of 157

Condition Master Data

VB41 – Create Cross Selling VB42 – Change Cross Selling VB43 – Display Cross Selling

You can set up the system so that if a customer orders a specific article, a list of other suggested articles appears as well.

153

ERP & SAP S/4HANA Overview

154 of 157

Important Transaction Codes

Transaction Codes	Application
VA01 / 02 / 03	Create / Change / Display Sales Order
VV11 / 12 / 13	Create / Change / Display Output for Sales Docs
SO10	Maintain Standard Text
VB11 / VB12 / VB13	Create / Change / Display – Material Determination
VB01 / VB02 / VB03	Create / Change / Display – Listing / Exclusion
VBN1 / VBN2 / VBN3	Create / Change / Display – Free
VA51 / VA52 / VA53	Create / Change / Display – Item Proposal
VB41 / VB42 / VB43	Create / Change / Display – Cross Selling

154

ERP & SAP S/4HANA Overview

155 of 157

Additional Info

Item Proposal:

If a customer frequently buys the same product pallet, you can specify the item proposal number in the customer master record. Item proposals are stored independently of customers. The materials of an item proposal can be proposed by the SAP System as an entry tool during order processing

You can then:

Copy the materials as they are
Change the specifications and only copy some materials or partial quantity

You can only include the products in a product proposal for which you created a material master record

Item Proposal Types are technically stored as Sales Documents and are controlled by Item Proposal Type ( standard PV / MS )

155

ERP & SAP S/4HANA Overview

156 of 157

Additional Info

The item proposal number thus generated can be added to a Customer Master Record and automatically called while creating an order
VA51- Create

VA52-Change

VA53-Display

VA55-List of Item Proposals

156

ERP & SAP S/4HANA Overview

157 of 157

A global leader in consulting, technology services and digital transformation, Capgemini is at the forefront of innovation to address the entire breadth of clients’ opportunities in the evolving world of cloud, digital and platforms. Building on its strong 50-year heritage and deep industry-specific expertise, Capgemini enables organizations to realize their business ambitions through an array of services from strategy to operations. Capgemini is driven by the conviction that the business value of technology comes from and through people. It is a multicultural company of over 200,000 team members in more than 40 countries. The Group reported 2018 global revenues of EUR 13.2 billion.

About Capgemini

Learn more about us at

www.capgemini.com

This presentation contains information that may be privileged or confidential and is the property of the Capgemini Group.

157

ERP & SAP S/4HANA Overview