Mickael QUESNOT ©
Automatic Account Determination (Sales) (VKOA SAP PUBLIC CLOUD)
This activity provides you with all the settings that are needed for assigning accounts.
Use
For more information, see Automatic Account Determination.
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
1
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
2
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
3
Mickael QUESNOT ©
Check Master Data Relevant For Account Assignment
Set up your system so that account determination is dependent on specific master data
fields.
Use
You can set the system so that account determination is dependent upon the following
master data fields:
• Account group for material in the material master record
• Account group for customer in the customer master record
Reasonable subdivisions of materials can, for example, be:
• Revenues for services (material type DIEN)
• Revenues for packaging (material type VERP)
• Revenues for finished products (material type FERT)
• Revenues for trading goods (material type HAWA)
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
4
Mickael QUESNOT ©
Reasonable subdivisions for customers can, for example, be:
• Revenues for foreign customers at home
• Revenues for foreign customers abroad
• Revenues for affiliated companies (internal trading partners)
• Revenues for customers from EU member states
• Revenues for customers from EFTA states
Note
The revenue accounts are subdivided in financial accounting (FI System) to receive certain
reports and/or to coordinate data with the financial statement (CO System).
You therefore have to define account determination or account groups in cooperation with
financial accounting and cost accounting.
Actions
1. Define which account groups you need for materials and customers to be able to
group the master records together for account determination.
2. Specify for each material account group one alphanumeric key which can have up
to two characters and a description.
3. Specify for each customer account group one alphanumeric key which can have
up to two characters and a description.
4. Make sure that the account group keys are entered in the material master records
and customer master records.
Define Account Assignment Groups for Customers *
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
5
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
6
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
7
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
8
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
9
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
10
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
11
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
12
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
13
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
14
Mickael QUESNOT ©
Define Account Assignment Groups for Materials *
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
15
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
16
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
17
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
18
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
19
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
20
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
21
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
22
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
23
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
24
Mickael QUESNOT ©
Define Condition Types
Short Text
Set condition types for pricing in sales.
Use
In this step, you define condition types. In a business document, price elements are
represented by condition types. Price elements can be, for example, prices, surcharges,
discounts, taxes or freight, and are stored in the system in condition records. You can, for
example, define whether a discount is calculated as a percentage or a fixed amount using
the condition type.
If you use a condition type as price element, you specify an access sequence in every
condition type. In this way you define which fields the system checks when searching for a
valid condition record.
If you use a condition type as an inclusion point, you must set the Inclusion Point checkbox.
Once you have defined a formula for subprocedure determination, you must enter its
formula ID in the inclusion point in the Subprocedure Detn field. In this way you prepare
inclusion points to set up main procedures and subprocedures for a later subprocedure
determination:
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
25
Mickael QUESNOT ©
• If you add an inclusion point to a pricing procedure, the pricing procedure becomes
a main procedure.
• If you assign an inclusion point to a pricing procedure, the pricing procedure
becomes a subprocedure.
Note
• The pricing procedure groups all condition types together that the system is to take
into account automatically during pricing for a business transaction.
Remember that in a business document, you can only specify manually those
condition types that are contained in the pricing procedure.
• You can change the outcome of pricing in the business document manually.
Recommendation
• If you define your own condition types, the key must start with the letter Z as SAP
reserves this namespace for this purpose in the system.
Note:
You can change the value of certain fields in condition types that are delivered by SAP. If you
want to change the values of these fields, you should carefully consider that these changes
could affect existing documents and, therefore, change the pricing result.
Actions
1. Check to what extent you can use the condition types contained in the standard
system.
2. Create new condition types by copying a similar condition type and changing it
according to your requirements. One reason for creating a new condition type is that
you may require a calculation rule for a discount which is not available in the
standard system.
3. Specify a 4-character, alphanumeric key that starts with a Z and a textual
description.
4. Specify an access sequence for the condition types. You do not need to specify an
access sequence for header conditions.
5. Maintain the detail screen of the condition type. You can also assign a reference
condition type if the condition types you are working with are similar. Then you will
only have to maintain condition records for the reference condition type.
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
26
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
27
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
28
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
29
Mickael QUESNOT ©
Define And Assign Pricing Procedures
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
30
Mickael QUESNOT ©
Create, change, display, and delete pricing procedures, and configure pricing procedure
determination.
Use
In this activity, you definepricing procedures. In addition, you assign the pricing procedures
to transactions by defining the following dependencies:
• Customer
• Sales document type
• Sales area
In the pricing procedure, you define which condition types are to be taken into account and
in which sequence. During pricing, the system automatically determines which pricing
procedure is valid for a business transaction. The system then takes the condition types
contained in the pricing procedure into account, one after the other.
The determination of the procedure depends on how you configure the following:
Set Pricing Procedures
You create new pricing procedures, for example, by copying a similar pricing procedure. In
addition, you can change or delete your own pricing procedure.
Note: You can delete your own pricing procedure only in the following cases:
• If it has not yet been transported to the production system.
• If there is no condition exclusion allocated to this pricing procedure in the Maintain
Condition Exclusion for Pricing Procedure step.
• If the pricing procedure is not assigned to a condition type to control the use of
condition supplements.
Note: After saving your own pricing procedure, you can delete procedure steps only in the
following cases:
• If they have not yet been transported to the production system.
• If in the Set Pricing Procedure Determination step, you have not set the respective
condition type for your own pricing procedure as Proposed Condition Type for Fast
Entry.
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
31
Mickael QUESNOT ©
Modular Pricing Procedures for Automatic Inclusion of Price Elements
You can change a pricing procedure to a main procedure or a subprocedure by using
condition types that have been defined as inclusion points:
• If you add an inclusion point to a pricing procedure, the pricing procedure becomes
a main procedure.
• If you assign an inclusion point to a pricing procedure, the pricing procedure
becomes a subprocedure.
Role-Based Access to Price Elements
To control displaying or changing specific price elements in business documents, you can
select the respective access level in the control data of a pricing procedure.
Note: If you use access levels in a business document, there is no impact on the printing of
these price elements as printing is controlled by the print type setting in the respective
pricing procedure.
Set Customer Pricing Procedures
You specify the customer pricing procedure in the customer master record for each sales
area.
Note: You can delete your own customer pricing procedure only, if it is not allocated in
the Set Pricing Procedure Determination step.
Set Pricing Procedure Determination
You specify how the system determines pricing procedures for sales documents every time
you create a new pricing procedure.
Note: You can delete your own pricing procedure, your own customer pricing procedure,
and determinations only if they have not yet been transported to the production system.
To determine the procedure, you allocate the customer pricing procedure and the
document pricing procedure to a pricing procedure within a sales area.
Recommendation
• Define your own pricing procedures that contain only those condition types that you
actually use. Otherwise, the system makes unnecessary accesses to conditions.
• In pricing procedures that are delivered by SAP, you can change the value of certain
fields, for example, the Manual field, but you can neither add nor delete steps.
Note:
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
32
Mickael QUESNOT ©
o If you want to change the values of these fields, you should carefully consider
that these changes could affect existing business documents and therefore
change their pricing result.
o If you want to add or delete steps in a delivered pricing procedure, you must
copy the pricing procedure and adapt it in your custom pricing procedure.
• If you want to determine condition types for a sales rebate or a sales commission in
the order-to-cash process, you must add the condition types for rebate accruals and
commission accruals (for example, REA1, RCA1) to your pricing procedure used in
sales documents. To ensure the posting of the accrual amounts to accounting, you
must also maintain the corresponding accounting key for that condition type as well.
Warning: Do not add the condition types for rebates and commissions (for example,
RES1, RCS1) to your pricing procedure used in sales documents. This can influence
the pricing results and can lead to incorrect accounting data.
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
33
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
34
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
35
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
36
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
37
Mickael QUESNOT ©
Define And Assign Pricing Procedures
Short Text
Create, change, display, and delete pricing procedures, and configure pricing procedure
determination.
Use
In this activity, you definepricing procedures. In addition, you assign the pricing procedures
to transactions by defining the following dependencies:
• Customer
• Sales document type
• Sales area
In the pricing procedure, you define which condition types are to be taken into account and
in which sequence. During pricing, the system automatically determines which pricing
procedure is valid for a business transaction. The system then takes the condition types
contained in the pricing procedure into account, one after the other.
The determination of the procedure depends on how you configure the following:
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
38
Mickael QUESNOT ©
Set Pricing Procedures
You create new pricing procedures, for example, by copying a similar pricing procedure. In
addition, you can change or delete your own pricing procedure.
Note: You can delete your own pricing procedure only in the following cases:
• If it has not yet been transported to the production system.
• If there is no condition exclusion allocated to this pricing procedure in the Maintain
Condition Exclusion for Pricing Procedure step.
• If the pricing procedure is not assigned to a condition type to control the use of
condition supplements.
Note: After saving your own pricing procedure, you can delete procedure steps only in the
following cases:
• If they have not yet been transported to the production system.
• If in the Set Pricing Procedure Determination step, you have not set the respective
condition type for your own pricing procedure as Proposed Condition Type for Fast
Entry.
Modular Pricing Procedures for Automatic Inclusion of Price Elements
You can change a pricing procedure to a main procedure or a subprocedure by using
condition types that have been defined as inclusion points:
• If you add an inclusion point to a pricing procedure, the pricing procedure becomes
a main procedure.
• If you assign an inclusion point to a pricing procedure, the pricing procedure
becomes a subprocedure.
Role-Based Access to Price Elements
To control displaying or changing specific price elements in business documents, you can
select the respective access level in the control data of a pricing procedure.
Note: If you use access levels in a business document, there is no impact on the printing of
these price elements as printing is controlled by the print type setting in the respective
pricing procedure.
Set Customer Pricing Procedures
You specify the customer pricing procedure in the customer master record for each sales
area.
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
39
Mickael QUESNOT ©
Note: You can delete your own customer pricing procedure only, if it is not allocated in
the Set Pricing Procedure Determination step.
Set Pricing Procedure Determination
You specify how the system determines pricing procedures for sales documents every time
you create a new pricing procedure.
Note: You can delete your own pricing procedure, your own customer pricing procedure,
and determinations only if they have not yet been transported to the production system.
To determine the procedure, you allocate the customer pricing procedure and the
document pricing procedure to a pricing procedure within a sales area.
Recommendation
• Define your own pricing procedures that contain only those condition types that you
actually use. Otherwise, the system makes unnecessary accesses to conditions.
• In pricing procedures that are delivered by SAP, you can change the value of certain
fields, for example, the Manual field, but you can neither add nor delete steps.
Note:
o If you want to change the values of these fields, you should carefully consider
that these changes could affect existing business documents and therefore
change their pricing result.
o If you want to add or delete steps in a delivered pricing procedure, you must
copy the pricing procedure and adapt it in your custom pricing procedure.
• If you want to determine condition types for a sales rebate or a sales commission in
the order-to-cash process, you must add the condition types for rebate accruals and
commission accruals (for example, REA1, RCA1) to your pricing procedure used in
sales documents. To ensure the posting of the accrual amounts to accounting, you
must also maintain the corresponding accounting key for that condition type as well.
Warning: Do not add the condition types for rebates and commissions (for example,
RES1, RCS1) to your pricing procedure used in sales documents. This can influence
the pricing results and can lead to incorrect accounting data.
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
40
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
41
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
42
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
43
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
44
Mickael QUESNOT ©
Result
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
45
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
46
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
47
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
48
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
49
Mickael QUESNOT ©
Result
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
50
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
51
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
52
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
53
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
54
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
55
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
56
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
57
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
58
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
59
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
60
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
61
Mickael QUESNOT ©
Mickaël QUESNOT © - Copyright
https://www.linkedin.com/in/mickaelquesnot/
62
