Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Details
Last Updated: 06 September 2018
In order to setup a pricing procedure in purchasing documents, you need access to the customizing
features.
IMG path to the available functions:
Transaction SPRO => Materials Management => Purchasing => Conditions => Define Price
determ.process
Following functions can be used to maintain the pricing procedure. There are more settings concerning
the pricing procedure, but we will cover the most used ones.
1. Choose the Access sequence you want to maintain (PB01 gross price).
2. Double click the Accesses folder in the dialog structure.
Step 2) In the next step you define access methods for the access sequence. You can see that several
access methods are present for one sequence.
Every one of them is exclusive. It means that if a record is found in first access (Contract item), meaning
that if the system finds a condition available from the Contract item, it will not search further, and that
value will be used. If not, system will follow the other accesses in order to find appropriate entry.
You can also set a requirement for an access method to be used. For example, there is a requirement 35
assigned to access 10, which uses condition table 17 - Material Info Record (Plant-Specific).
A requirement for access number 10 is 35 - Plant info record. If there is no plant info record for the
combination of the values in table 17, access 10 will not be used at all.
Step 3)
1. You can see we are located on the details screen for access sequence PB01, access 20 and table 18.
2. The key fields of a condition table used in the condition access are showed here.
Condition table consists of condition fields which have certain attributes assigned to them. When the
system tries to access a condition record it uses these attributes.
Special value source – this field contains a value to be used as default while accessing (e.g. using a fixed
info record category for the access sequence)
Init – if this box is checked system will allow initial value for this field while accessing the condition table. If
not system will not process the condition table lookup.
Atyp – processing type in access. You can specify if the field is relevant for condition access if it is part of a
free or fixed key type. Default is left blank (fixed key type).
Priority – priority of a field (characteristic), it can be set from 01 to 99. Most of the time this field is left blank.
1. Execute the transaction code V/05 and on the initial screen enter our table number - 18.
2. In the section 2, you can see our table definition, table number, description, and two options that can be
selected. First means use of the validity period (always recommended) and the other is a check for release
status of the record. If checked, only released info records will be taken into account while searching for the
condition.
3. Here is the list of fields you have already seen in the Define access sequence topic.
You can see how is the table defined for later use in customizing the access sequence.
You can also use right click to delete or add a field to your table, as well as to navigate the Field catalog
on the right side of the screen. Not all of the fields can be shown in a single page of field catalog.
After successful creation, you will be prompted to create a change request and afterwards, you will be
presented a log screen like you can see on the following screen.
You have successfully generated a condition table let's see if we can see it in the access sequence
maintenance screens.
It's there, so now we can create an access using this table. We will not cover this in detail as it is
extremely straight forward process.
On the accesses node of our access sequence, choose New entries button. You can create access like in
the below screen for Testing purposes.
Fields should also be assigned to our access PB01 – 96 in order for it to work properly
Step 3)
You can find all of the existing entries for condition types.
You have several more actions at your disposal: deletion, selecting all condition types, deselecting all
condition types.
If you select multiple condition types, you can edit them all by navigating through them in the following
screen (arrow left and right or F7 and F8).
This screen has a lot of settings for a condition type, let's review the most important.
Step 4)
First section of the screen contains condition type PB00, description, and access sequence used for
condition determination.
A) Control data 1 section contains the following:
1. Group condition (indicates if a condition calculates its value by more than one item in the
document)
2. RoundDiffComp (rounding difference comparison)
3. Group condition routine (routine that calculates the value)
1. Manual entries (e.g. no limitations, not possible, manual entry has priority)
2. Header condition (indicates if a condition can be used at header level)
3. Item condition (indicates if a condition can be used at item level)
4. Delete (indicates if a condition can be deleted)
5. Amount/percent (can amount/percentage be changed)
6. Value (can value be changed)
7. Qty. relation (can conversion factor between UoMs be changed during processing)
8. Calculat. Type (can calculation type be changed during processing)
Step 5)
The other section on the lower end of the same screen are:
D) Master data section:
1. Valid to (default date to use)
2. Pricing Proc. (pricing procedure to be used for this condition type)
3. Delete fr. DB (deletion procedure for this condition type)
E) Scales section:
When you are done with creating, changing or copying of the condition type, you can save your changes.
How to Define Calculation Schema in SAP
Details
Last Updated: 02 October 2018
As you saw in the previous topic, a condition type is assigned a calculation schema. It is defined in
customizing.
Step 1)
In IMG, Choose Define Calculation Schema option.
Step 2)
1. You can see that the initial screen contains a dialog structure with Schemas as the top
level.Additionally, you can drop down to Control data.
2. Right portion of the screen shows Usage and Application data.We can see that usage is to A –
Pricing, and application is set to M – Purchasing.
3. Contains a list of schemas and its short description
Step 3)
Step 1)
1. Choose Define Schema Group from SPRO IMG path like in the previous topics.
2. From the menu below, choose Schema Groups: Vendor.
Step 2)
On the next screen, you can define schema group for use in vendor master & maintain a description of
your vendor schema groups.
You define only schema group number and description. There are no settings as this is used to be
assigned to the vendor master record.
For example, we might need to create a new group 02 – Schema vendor 02.
Step 3)
Next, choose schema groups for purchasing organizations from main schema group menu.
Define your schema groups per your requirement. You define only schema group number and
description. No settings either, just an indicator assigned to a purchasing organization.
Step 4)
Choose Assignment of Schema Group to Purchasing Organization from schema group menu.
Assign desired schema group to purchasing organization. As you can see on the below screen, the field on the right
is left blank, that is because if you leave it blank, it means that the default purchase organization schema
should be used.
If you want to use a standard schema for group organization, leave the field in the previous screen blank,
and if you want to choose the Schema 0001 enter 0001 in the field marked in the upper screen. Screen
with the available schemas for assignment to purchasing organization is available in the previous step
(same as on below screen).
Step 5)
Assigning a schema group in the vendor master.
Go to the purchasing data view. You will see Schema group, Vendor field. You can choose whichever
schema group is suitable for this vendor, default is left blank for standard schema vendor.
You can see that this field is maintained at purchasing organization organizational level (0001), so in
combination with schema group for that purchasing organization, if we check tables, the selected
calculation schema will be RM0000 – Purchasing Document (Big), as you can see in the next topic.
Step 1)
Choose Determination Calculation schema for Standard Purchase Orders.
Step 2)
Choose schema group for purchasing organization.
Choose schema group for vendor.
Choose calculation schema to be assigned to the purch.org/vendor schema group combination.
1. In case 1, we have chosen default schema group for purchasing organization (first field is empty), also,
default schema group for vendor (second field is empty), for this combination of both default schema groups,
we assigned a RM0000 (Purchasing document - Big) calculation schema.
2. In case 2, we have chosen schema group for purchasing organization as 0001, and schema group for
vendor as 01, and assigned an RM1000 calculation schema to the combination.
In case we are creating a purchase order through purchasing group 0001 for vendor 1, our calculation
schema is going to be determined as RM0000.
If we are creating a PO for vendor 2 through purchasing organization 0001, calculation schema RM1000 will
be determined.
If we are creating a PO for any of the two vendors in purchasing organization 0002, in both cases there will
be determined calculation schema RM1000.