Access Sequence:

Access Sequence is a searching strategy for pricing to find the valid date for a particular
condition type. In the Access Sequence we can assign more than 1 condition table in a particular
sequence. As I earlier that Access Sequence is a searching strategy so to make the right search
we have to careful when assigning the Condition Table in Access Sequence.
For example if we assign a Access Sequence say ABC with Condition Table A and B where A is
Customer and B is Material. So if my organization is giving the priority for any condition type
for Material rather than Customer then in the Access Sequence we have to assign Table B 1
st

flowed by table A.

To create Pricing Access Sequence the menu path as under Sales and Distribution > Basic
Function > Pricing > Price Control > Define Access Sequence..


We can use any existing Access Sequence or can copy the exisiting and create a new starts with
Z.
To differentiate the Rebate Access Sequence and the Pricing Access Sequence the field Ty
(Relevant For Rebate) used. Use 1 to make the Access Sequence Relevant for Rebate.
Create a new Access Sequence Starts with Z and give a description.
Always use any existing Access Sequence and copy to create a new access sequence.
Assign the Condition table in a sequential order. The Tab NO. is like as step.
Use the Requirement field if we want to use any routine.
Exclusive tab is used if we want to stop the searching for a once the 1
st
requirement is meet.
Select the line and click on table and save.



Condition Type :

The pricing elements are define in SAP as condition type. Elements means Price, Discount ,
Fright etc.
In the Condition Type we define all the characteristic of a Pricing element. So its became very
important to understand the needs and use of the Condition Type before we configure any new
condition type.
Before start configuring any new condition type make sure the below points or the questions are
clear
Can we make use of any existing Condition Type.
What type of Condition it is i.e price , surcharge , fright etc
What will be the calculation type for this condition
Will we maintain it manually or automatic
Is that a header condition or item.


The above questions will make you more confident to start the configuration of a new condition
type.
As always create a new condition type starts with Z.

The Configuration Of Pricing Condition Type can be found under Sales and Distribution >
Basic Function > Pricing > Price Control > Define Condition Type.


We will take an example of PR00 which is Price condition type and will see all the fields on it.
If you want to create a new Condition Type copy the existing and create a new.



The above screen is the details screen of PR00.

1. 1. Next to the name of the condition type and self explanatory description there is a filed named
as Access Sequence which is the same Access Sequence which we created in the above step and
will assign the same here.


1. 2. Condition Class is differentiate the class of the condition like Price , Discount etc.. use this
filed to differentiate what pricing element this is..



1. Plus / Minus filed controls the amount of this condition will have a positive (for price ) ,
negative (for discount) or both the effect it has.
Make use of this filed carefully , if you use Positive (+) then that will effect an positive in
amount or other way around.

Controls whether the condition results in an amount, that is negative (a discount), positive (a
surcharge), or whether both positive and negative amounts are possible.

Calculation Type



Determines how the system calculates prices, discounts, or surcharges in a
condition. For example, the system can calculate a price as a fixed amount
or as a percentage based on quantity, volume, or weight.
Condition Category







Classification of conditions based on predefined categories.
Eg: Tax, freight etc.

Structure Condition



Controls whether the condition type should be a duplicated condition or a cumulated condition.
This control is only helpful when you use bill of materials or configurable materials.
A duplicated condition is duplicated into all assigned items.
A cumulated condition contains the net value of all assigned items.

Group Condition



Group condition
Indicates whether the system calculates the basis for the scale value from more than one item in
the document.
Use
For a group condition to be effective, the items must belong to a group. You can freely define the
group to meet the needs of your own organization. The items can, for example, all belong to the
same material group.
Example
A sales order contains two items. Both items belong to the material group 01.


The group condition indicator is set in the definition of the condition type for material group
discounts.
The condition record for material group 01 includes the following pricing scale:
Neither item alone qualifies for the 2% discount. However, when the items are combined as part
of a group condition, the combined quantity creates a basis of 250 pieces. This basis then
exceeds the scale value of 200 pieces, which is necessary to qualify for the higher discount.
Group Condition Routine








Routine number for creating group key
Identifies a routine that calculates the basis for the scale value when a group condition occurs in
pricing.
Example
You can specify a routine, for example, that totals the value of all items in a document in order to
determine the basis for a discount.



Rounding difference comparison





Indicator that controls whether rounding difference is settled for group conditions with a group
key routine.
If the indicator is set, the system compares the condition value at header level with the total of the
condition values at item level. The difference is then added to the largest item.




Changes which can be made




Entries Priorities


Making manual entries
Indicator which controls the priority within a condition type between a condition entered
manually and a condition automatically determined by the system.
Make the following entries according to your requirements:
_: No limitations
A: Freely definable
B: The automatic entry has priority. If a condition record exists, the condition cannot be
entered manually.
C: The manual entry has priority. When you enter the condition manually, the system does not
check whether a condition record exists.
D: Cannot be processed manually


Header Condition


Condition applies to header
If this condition is marked as a header condition, it is possible to enter the condition type in the
header condition screen. Checks for changing the condition manually are unaffected by this.



Condition rate of change for amount/percentage


Specifies whether the amount or percentage for the condition type can be changed during
document processing.

Quantity Relation

Specifies whether the conversion factors for the units of measure in conditions of this type can be
changed during document processing

Item Condition
Condition applies to items
Procedure
Mark this field if the conditions of this type are allowed to be entered in the document items. The
condition is then only valid for the particular item in which it is entered.

Delete
Indicator that controls whether the condition type can be deleted from the document.


Value & calculation Type
Value
Specifies whether the value of the condition type can be changed during document processing.

Calculation Type
Specifies whether the calculation type for the condition type can be changed during document
processing.



Master Data
Valid From
Proposed starting date for the rebate validity period
Specifies the beginning validity date that the system automatically proposes when you create a
rebate agreement of this type.
Example
You can, for example, specify that the system proposes the first day of the current week, month,
or year.
Procedure
If you want the system to propose the current date, leave the field blank. Otherwise, enter one of
the values predefined for your system.

Valid To
Date proposed as valid-to date
Proposed value for how long a condition should remain valid.
Use
The system proposes this value for the Valid to date when you create condition records.






Pricing procedure
Sales and Distribution: Pricing Procedure in Pricing
Determines which condition types can be used in a document and in which sequence they appear.
Use
The system uses the pricing procedure that you enter here to control the use of condition
supplements in records of this condition type. You can apply the discounts that are defined in the
pricing procedure as condition supplements during pricing.
Procedure
Enter one of the predefined pricing procedures that control condition supplements. If you leave
the field blank, the condition supplement function in the screens where you maintain the
corresponding condition records is inactive.
Example
You define a pricing procedure to control a condition supplement for a material price. The
condition supplement specifies discounts that you want the system to apply every time the
system accesses a material price condition record. When you define the condition type for a
material price, you enter the pricing procedure that you defined for the condition supplement.

Delete from database
Condition records should be deleted from the database
You can use this indicator to control how the system operates when deleting condition records.
You have the following options:
SPACE: You can set an indicator so that the condition record is no longer used in pricing. The
condition record is then archived in the archiving run.
A: You can delete the condition records from the database. You then receive a popup, asking
whether the condition record should actually be deleted or whether the deletion indicator should
simply be set.
B: You delete the condition records from the database. You only receive a popup if there are
condition supplements available.


Reference Condition Type
Reference condition type
A condition type which can be used as a reference so that you only have to create condition
records once for condition types that are very similar.
Use
You may need to use different condition types for the same condition. These can differ in the
access sequence, the description, the reference stage of the pricing procedure or the calculation
type, for example.
You can enter the condition type under which the condition records are created.
Example
Condition type MWSI only differs with condition type MWST in the calculation type. For this
reason and entry is made in field Reference Cond Type MWST for condition type MWSI. Now,
condition records only need be created for condition type MWST and not additionally for
MWSI.
Dependencies
Field Ref Application is used to refer to condition records from other applications.

Application, that can be used to refer to condition records from other
applications.











You only have to create condition records once for condition types that are
very similar. You can also refer to condition records from other applications.
Access Sequence
Define Access Sequences
You define access sequences in this IMG step.
The access sequence is a search strategy which the SAP System uses to
search for condition records valid for a condition type.
For example, you can define for a price that the SAP System first searches for
a customer-specific price and then for a price list price.
Recommendation
If you define your own access sequences, the key should start with the letter
Z since SAP reserves this letter for the standard system.
Do not change access sequences contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the access sequences contained in the
standard SAP R/3 System.
2. Create new access sequences by copying a similar access sequence and
changing it according to your needs. Specify an alphanumeric key which may
have up to 4 digits and a textual description
Access sequence - Access number
Indicates the number of the access within the access sequence.
Condition table
A combination of fields that defines the key of a condition record.
Use
For each condition type in a pricing procedure, you define an access
sequence. The access sequence tells the system where to look for relevant
condition records for a particular condition type (a rebate for a specific
customer, for example). Each access in the access sequence refers to a
condition table. The fields defined in the table (the key) help the system to
locate valid condition records.
Procedure
When you create a condition table, you specify one or more target fields as
the table key. You must also tell the system where to find the value for each
target field. You do this by specifying source fields. The source fields are
usually the same as the target fields, but they can differ. For example, if the
target field "Customer" is part of the key, you can specify that the system
uses "Ship-to party" as the source field and takes the value from there.
Requirement
Use
If the requirement is fulfilled (SY-SUBRC = 0), then output determination
also takes into consideration output type or the access sequence, for which
the requirement has been specified.
Examples
A possible requirement would be, for example, that a difference should be
made between document currency and local currency.
Indicator: Exclusive condition access
Controls whether the system stops searching for a record after the first
successful access for a condition type within an access sequence.
Fields in Access Sequence

Field for condition table
Name of the field from the condition record.
Definition
The symbols are used to display how the document data is used in the
condition access and how the data determined in the access is transferred
back to the document. Arrows indicate the direction of the data transfer, the
equal sign stands for an access with a direct value. The tools indicate that
the data transfer must be ensured when setting up pricing by adapting the
system using formulas and requirements. The green LED indicates automatic
processing and a red LED marks a line, where data for correct processing is
missing.
Table name of the document structure
Specifies an internal table in which condition information about documents is
stored

Fields in Access Sequence
Table field for document structure
Determines the data dictionary characteristics for new fields in data
dictionary structures.
Use
Reference fields are necessary for the generation of data dictionary structures
for conditions and information structures. A reference structure and a
reference field must always be entered.
Long Field Label
Definition
One of the following:
- Short field label
- Medium field label
- Long field label
Can be assigned as prefixed text to a screen field referring to the ABAP
Dictionary. The text is displayed on the screen in the logon language of the
user (if the text was translated into this language).
A heading can be defined to output the field values in lists. This heading is
automatically included in the list header row, in the logon language.
Source of constant
Value which the system automatically assigns to a field when it accesses the
condition record.
Dependencies
A field can contain either the value of the source field or the value of a
constant (a direct value).
Characteristic: Initial value allowed
The initial indicator has two functions within Customizing for access
sequences. Firstly, it controls that the system does not access the condition
if the field in the document header/item is blank or 0. Secondly, during
automatic return transfer of data that were determined in the access, it
allows an initial value to be returned
Processing type in access
Definition
The processing type determines how the corresponding field is used for the
access. The field can be marked as belonging to the fixed/free key part or
else as not relevant for the access.
Fields that are defined as data fields for the definition of condition tables are
automatically marked with an access type.
Define and assign pricing procedure
Define And Assign Pricing Procedures
You define the pricing procedures in this step. In addition, you assign the
pricing procedures to the transactions by defining the following
dependencies:
Customer
Sales document type
Sales area
In the pricing procedure, you define which condition types should be taken
into account and in which sequence. During pricing, the SAP System
automatically determines which pricing procedure is valid for a business
transaction and it takes the condition types contained in it into account one
after the other.
The determination of the procedure depends on the following factors:
Customer determination procedure
You specify the customer determination procedure in the customer master
record for each sales area.
Document pricing procedure
You specify the document pricing procedure for each sales document type
and billing type.
To determine the procedure, you allocate the customer determination
procedure and the document pricing procedure to a pricing procedure within
a sales area.
SAP Recommendation
Define your own pricing procedures which contain only those condition types
which you use. Otherwise, the system makes unnecessary accesses to
conditions.
Do not change the pricing procedures contained in the standard SAP R/3
System.
Actions
Create new pricing procedures by copying a similar pricing procedure.
Specify a key with up to 6 characters and a description.
For a procedure, specify the condition types in the sequence of their usage.
Maintain the lines of the pricing procedure
Afterwards define the customer determination procedures for determining the
procedure.
Define the document pricing procedures for determining the procedure.
Assign the procedure to the sales document types and billing types.
To determine the procedure, define the allowed combinations of:
Sales area
Customer determination procedure
Document pricing procedure
Pricing procedure
Check settings
You can check the settings for your pricing procedures. This is not a complete
check. It mainly checks the requirements and calculation formulas for
standard condition types. Refer to the report documentation for more
information.
Maintaining Pricing Procedure
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the
sequence in which they are used.
Example
Procedures are used, for example, in the following applications:

Pricing in sales and distribution
Applying overhead in Product Costing (costing sheets) and for CO internal
orders
Calculating accrued costs in Profitability Analysis
Output control (printed confirmations, EDI messages, electronic mail)
Account determination
Calculating taxes on sales/purchases
Calculating accruals in Cost Center Accounting
Pricing for resource planning
Pricing type
Specifies how the system treats pricing data when copying documents.
At the time of billing, the following pricing types are possible:
A: Copy pricing elements and update according to scale. The system
does not determine any new condition types
predetermines the scale prices for changed delivery quantities
B: Carry out completely new pricing. The system
carries out a completely new pricing (manually entered pricing elements are
not copied from the reference document)
redetermines the taxes
C: Copy manual pricing elements and carry out a new pricing for the others.
The system carries out a new pricing, copies the manually entered pricing
elements, Redetermine the taxes

16 Steps in Pricing Procedure



Step number
Number that determines the sequence of the conditions within a procedure.
Condition counter
Access number of the conditions within a step in the pricing procedure.
Use
During automatic pricing, the system takes into account the sequence
specified by the counter.


Condition type
The condition type is used for different functions. In pricing, for example, the
condition type lets you differentiate between different kinds of discount; in
output determination, between different output types such as order
confirmation or delivery note; in batch determination, between different
strategy types.
From reference step (for percentage conditions)
Condition step, the value of which is the basis for percentage surcharges.
If you specify a to reference step at the same time, the condition values of
the two steps specified and the conditions values of the steps in between are
totalled. In this case, percentage surcharges are calculated on the basis of
the total.
Example:

Level CType Description FromSt ToSt ActKy
10 A-B1 Wages
20 A-B2 Salaries
30 A-B3 Overtime/Wages
40 A-Z1 Vacation bonus 10 30 E11
The surcharge for step 40 is added to the total of steps 10 to 30.
To reference step (for percentages)
Condition step up to which the condition values of the previous steps are
totalled. Percentage surcharges are calculated on the basis of the total.
If you specify a from reference step at the same time, the condition values
of the two steps specified and the condition values of the steps in between
are totalled.
Example:
Step CType Description FromSt ToStep AcctKey
10 A-B1 Wages
20 A-B2 Salaries
30 A-B3 Overtime/Wages
40 A-Z1 Vacation bonus 10 30 E11
The surcharge for step 40 is added to the total of steps 10 to 30.
Condition determined manually
Use
Conditions, that are given this indicator in the pricing procedure, are only
included in determination (price determination, output determination, batch
determination) either if they are entered manually, for example, on the
condition overview screen in Pricing or if they are transferred from an
external process, such as costing.
Condition is mandatory
Indicates whether the condition is mandatory when the system carries out
pricing using this pricing procedure.
Example
If, for example, you always want to include a tax condition (VAT or sales
tax) during pricing, you can set this indicator for the appropriate tax
condition type.
Condition is used for statistics
This indicator causes a surchage or discount to be set in the document
statistically (that is, without altering the value).
Print ID for condition lines
Controls issue of condition lines when printing documents such as order
confirmations or invoices.
Use
In releases previous to 4.0, the following print indicators are available :
' ' : Condition line is not printed
'X' : Condition line is printed at item level
'S' : Condition line is printed in totals block
The following standard logic is set out for these printing indicators:
Item POS of the last condition line is determined with 'X'.
All condition lines that contain an item smaller than POS in the pricing
procedure are only printed if print indicators 'X' or 'S' are set.
All condition lines that contain an item larger than POS in the pricing
procedure, that come before the first tax condition line and which have a
non-statistical VAT condition, receive printing indicator 'S'. The same applies
for condition lines that contain an item larger than POS in the pricing
procedure, that come after the first tax condition line and an active non-
statistical VAT condition.
Condition lines that represent a tax condition type are always printed in
totals blocks with print indicator 'S' (set internally or externally).
Condition lines that represent a condition type that is not a tax condition
type are only printed with print indicator 'S' (set externally or internally) if
the condition value of the condition line is not zero. Condition lines that do
not represent a condition type (i.e. subtotals) are only printed with print
indicator 'S' or 'X' (set externally or internally) if the condition value of the
condition line is different from the condition value of the previous condition
line in the pricing procedure.
To provide a better overview of this process, 8 more print parameters are
available as of Release 4.0. These print indicators cannot, however be mixed
with the three previous print indicators ' ', 'X' and 'S' in the pricing
procedure. This means that the new indicators are only taken into account if
a no condition lines in the pricing procedure contain printing indicators 'X' or
'S'.
The new printing indicators have the following settings, and corresponding
influence on processing.
'A' : in total: general
'B' : in total: if value <> zero
'C' : in total: if value <> value of predecessor
'D' : in total: if value <> zero and value <> value of predecessor
'a' : at item : general
'b' : at item : if value <> zero
'c' : at item : if value <> value of predecessor
'd' : at item : if value <> zero and value <> value of predecessor
Condition subtotal
Controls whether and in which fields condition amounts or subtotals (for
example, a customer discount or the cost of a material) are stored.
Use
If the same fields are used to store different condition amounts, the system
totals the individual amounts.
Example
These condition amounts or subtotals are used as a starting point for further
calculations. You may, for example, want a subtotal of all the discounts
included in the pricing of a sales order.
Requirement
Use
If the requirement is fulfilled (SY-SUBRC = 0), then output determination
also takes into consideration output type or the access sequence, for
which the requirement has been specified.
Examples
A possible requirement would be, for example, that a difference should be
made between document currency and local currency.
Condition formula for alternative calculation type
Alternative formula to the formula in the standard system that determines a
condition.
Alternative formula for condition base value
Formula for determining the condition basis as an alternative to the
standard.
Example
An absolute header discount is, for example, distributed in the standard
system according to the cumulative value of the items.
If the system, however, distributes the absolute header discount according
to volume, a header discount of $30 results in the following discounts:

Item Value Volume Discount
Stand. disc. Volume disc.
1 $1000 2 cbm $20 $10
2 $500 4 cbm $10 $20
Account key
Key that identifies different types of G/L account.
Use
The account key enables the system to post amounts to certain types of
revenue account. For example, the system can post freight charges
(generated by the freight pricing condition) to the relevant freight revenue
account.
Account key - accruals / provisions
Key which identifies various types of G/L accounts for accruals or
provisions.
Use
With the aid of the account key, the system can post amounts to certain
types of accruals accounts. For example, rebate accruals which are
calculated from pricing conditions can be posted to the corresponding
account for rebate accruals.


Define Customer Pricing Procedure

Pricing procedure assigned to this customer
Determines which pricing procedure the system should apply when you create a sales document
for the customer.


Use
You can define different pricing procedures for your system. A pricing procedure determines the
type and sequence of conditions that the system uses for pricing in, for example, a sales order.













Document Pricing Procedure

Document procedure (for determining pricing procedure)

The key that specifies the pricing procedure for this type of sales document.
Use
During pricing, the system determines the pricing procedure by taking into account
The sales area
The pricing procedure key in the header of the sales document type
The pricing procedure key in the customer master record
The pricing procedure determines how the system carries out pricing for a particular sales
document (for example, which pricing condition records it accesses and in which sequence).

Pricing procedure determination

Pricing procedure is based on the sales area, document pricing procedure and customer pricing
procedure.