Condition Technique in SAP

September 17, 2017 | Author: Anupa Wijesinghe | Category: Subroutine, Sequence, Areas Of Computer Science, Business, Technology
Share Embed Donate


Short Description

Condition technique is the most common method used in SAP to determine certain records/values during various processes s...

Description

Contents Introduction .............................................................................................................................................. 2 Overview ................................................................................................................................................... 2 Step 1: Determine "Document pricing procedure" .................................................................................. 2 Step 2: Determines "Customer pricing procedure" .................................................................................. 3 Step 3: Determine sales area .................................................................................................................... 4 Step 4: Determine pricing procedure ....................................................................................................... 5 Step 5: Determine all condition types ...................................................................................................... 6 Step 6: Determine "Access Sequence" ..................................................................................................... 7 Step 7: Determine condition tables .......................................................................................................... 8 Step 8: Determine correct condition values ........................................................................................... 11

Introduction Condition technique is the most common method used in SAP to determine certain records/values during various processes such as sales order, output, VAS. Most popular areas of condition technique can be seen in sales order pricing conditions, text determination, and output determination areas.

Overview

Step 1: Determine "Document pricing procedure" In VA01 initial screen, when user enters the sales document type, system determine the "Document pricing procedure" from the sales document type configuration. Eg: Let's take sales document type "OR"

IMG Path:

Therefore it determine the "Document pricing procedure" as "A" for the sales document type "OR"

Step 2: Determines "Customer pricing procedure" In the next screen of the sales document, when user enters the sold to party, system determines the "Customer pricing procedure" from the customer master. (Customer master -> Sales area data / Sales tab) Eg: Let's take my customer as "A300"

From the customer master ->

Therefore it determine "customer pricing procedure" as "M" for my customer "A300"

Step 3: Determine sales area Based on the sales area entered in the initial screen of VA01 (Or finally based on the sold to party) system determine the sales area of the sales order (Sales organization / Distribution Channel and Division)

Step 4: Determine pricing procedure With above mentioned data (Document pricing procedure, customer pricing procedure and sales area) system goes to below configuration node to find the correct pricing procedure which needs to be determined.

For my example, system find below pricing procedure.

Therefore now you can see in my sales order header the pricing procedure is "J_3A01".

Step 5: Determine all condition types With the determination of pricing procedure all condition types attached to it, get determined to the sales document. IMG Path:

Therefore above shown condition types will be determined in the sales order.

Step 6: Determine "Access Sequence" Now system goes through each condition type and gets the "Access Sequence" attached to it. Eg: Let's take condition "J3AP" as an example.

IMG Path:

->

Step 7: Determine condition tables Based on the access sequence attached to each condition type in the pricing procedure, system will determine its condition tables from the configuration. Eg: For my example, condition "J3AP" determine the access sequence "J3AS". Now let's see the tables available in access sequence "J3AS" IM G Path:

->

You can select each table and see which fields are used for that table under the node "Fields" Eg: Condition table 499 in the Step 40 has below fields

This is the level that you maintain your condition master records in transaction VK11. The options appear in the pop up screen in transaction VK11 is equal to the tables in the access sequence of that condition type. Eg: See VK11 for condition type "J3AP". Below options are coming from the access sequence "J3AS" attached to condition type "J3AP" (compare with the above "J3AS" access sequence)

When you create a condition record in VK11, data will be saved in the respective condition table. You can access same in the transaction SE11 with a prefix "A". For example if you want to see the condition table 499 in SE11, you can use "A499" as the table name

Step 8: Determine correct condition values When you enter the material in the sales document item, system goes to each condition table attached to access sequence of each condition type in the pricing procedure and finds the correct value. During this execution, requirement routines attached to condition type or access sequence comes in to play as well.

Once the right condition value is found, system posts it to the sales document item. When you use the "Analysis" function in the sales document item level, you can see from which condition table, the value got determined.

Analysis Details:

As explained above, same steps will be carried out with each condition type in the pricing procedure to determine values for the sales document line item.

Author: Anupa Wijesinghe E-Mail: [email protected] / [email protected] Website: www.learnsaptips.com View my profile in LinkedIn Follow me on Twitter

Disclaimer This article is done based on my research and readings, unless otherwise stated. The views expressed are my own and not of anyone else. Author accepts no liability for the content of the articles in this website or for the consequences of any actions taken on the basis of the information provided. Using this information is at the users own discretion and responsibility.

View more...

Comments

Copyright ©2017 KUPDF Inc.
SUPPORT KUPDF