Kontakt

Ansicht
Dokumentation

SIMG_CFMENUOLMEOMER - Define Document Types for RFQ

SIMG_CFMENUOLMEOMER - Define Document Types for RFQ

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

The following sections describe how the process of price determination is controlled. (In most cases, we are referring to the purchase price, but in some instances, "price" should be read as "cost".)

Check price determination criteria

Before setting up the price determination facility in the SAP System, you should acquaint yourself with the price determination criteria.

Check the dependencies involved in arriving at prices, discounts and surcharges. For example, stipulate whether different criteria apply to individual material groups and determine the basis upon which discounts and surcharges are calculated.

Then check your price determination dependencies against the criteria for price determination included in the SAP System. In doing so, work through the following sections.

Use this menu option to define the price dependencies. You can make prices, discounts and surcharges dependent on almost all the fields in a purchasing document. You define these dependencies with the aid of condition tables. In a condition table, you specify the combination of fields for which you can create condition records.

You should not change the condition tables that are included in the standard version of the SAP System.

  1. Check the extent to which you can use the condition tables that are supplied with the standard SAP System.
To do this, you can display these condition tables.
  1. Before creating a new condition table, you should check whether the existing fields of the field catalog are sufficient for your requirements. If you wish to use a field which is not defined for this usage in the price determination process, you must include it in the field catalog. You can only include fields that are included in one of the tables KOMG, KOMK or KOMP.
  2. Create new condition tables. To do so, copy a similar condition table and proceed as follows:
  • Enter the name of the table you wish to create.

Note that you can only choose names between 501 and 999. If you make no entry, the system will automatically assign a consecutive number.
  • Specify whether you wish to create the table with or without a validity period.

  • Enter the type of condition table (for example, transparent table).

  • Enter a description for the condition table.

  • From the list of allowed fields that are included in the field catalog and which can be extended there, choose your desired fields for the condition table.

  • Generate the new condition table.

  1. Specify the condition tables in the access sequences (see the section "Defining Condition Types and Access Sequences").
In this way, you establish the link between condition type, access sequence, and condition record.

How to include the fields in tables KOMK, KOMG, and KOMP is described in the following section.

  • The following communication structures are relevant to price determination:
  • KOMK (Pricing communication header)

  • KOMP (Pricing communication item)

  • KOMG (Allowed fields for condition structures)

For technical reasons, the communication structure KOMG is used. This represents the total of KOMK and KOMP, and contains all fields that are fundamentally capable of being used for pricing purposes. If new fields are included in KOMK or KOMP, they are automatically also included in KOMG.
  • Fields for price determination are included in the following INCLUDES:
  • Header data in KOMKAZ (INCLUDE in KOMK/KOMG)

  • Item data in KOMPAZ (INCLUDE in KOMP/KOMG)

  • The new fields in the processing of purchasing documents are filled via the following USER EXITS:
  • Extension of LMEKO001 with function module EXIT_SAPLMEKO_001 (for the header fields of table KOMK)

  • Extension of LMEKO002 with function module EXIT_SAPLMEKO_002 (for the item fields of table KOMP)

You must activate the USER EXITS via transaction CMOD.

The example describes the case where a document field is to be used in the price determination process, and there is no provision for such usage in the standard system supplied. If, for example, you wish to use the purchasing group for pricing purposes, you will have to include this field in the function. To do this, proceed as follows:

  1. Check whether there is a corresponding document field in the standard system supplied.
The purchasing group is included in the purchasing document at header level (= field EKGRP).
  1. Check whether a header or item field is involved.
Field EKGRP is stored in table EKKO and is thus a header field.
  1. Include the field name ZZEKGRP in the communication structure KOMK via the INCLUDE KOMKAZ and assign it to data element EKGRP.
Note that new data fields must begin with the letters "ZZ" or "YY" because SAP has left these name slots free to protect them from being overwritten during changeovers between releases.
  1. Activate the structure.
This causes the structures containing this INCLUDE structure to be generated as well.
  1. Check to see in which table the field EKGRP occurs.
The field occurs in table EKKO (purchasing document: header data).
  1. Supply the new field in program ZXM06U14, which is used in
    function module EXIT_SAPLMEKO_001, as follows:
    MOVE I_KOMK TO E_KOMK.
    MOVE I_EKKO-EKGRP TO E_KOMK-EKGRP.
  2. Assign the specifications A, M, and 001 to the field ZZEKGRP in table T681F. The usage "E" has been included for fields in "subsequent settlement".

Use this menu option to define access sequences and condition types.

An access sequence is a search strategy with the aid of which the SAP System searches for valid condition records.

For example, you can stipulate that the SAP System first searches for a price for a specific plant, and then for a generally applicable price.

The condition types are used to represent pricing elements such as prices, discounts, surcharges, taxes, or delivery costs, and are stored in the system in condition records.

In each condition type, you specify an access sequence. In this way, you stipulate the fields the SAP System is to check in its search for a valid condition record.

In a price calculation schema (which may also be termed a "pricing procedure"), you collect together all the condition types that are automatically to be taken into account by the SAP System in the process of price determination with regard to a business transaction.

Note that you can only also enter manually the condition types that are contained in the calculation schema.

You can alter the result of the price determination process manually in the purchasing document. You can limit the change options for a condition type via this menu option.

If you define your own condition types and access sequences, the key should begin with the letter Z, as SAP keeps these name slots free in the standard system supplied.

You should not change the access sequences and condition types that are included in the standard SAP System supplied.

  1. Check the extent to which you can use the condition types and access sequences that are included in the standard SAP System supplied.
  2. Create new access sequences by copying and changing similar existing ones.
In doing so, enter an alphanumeric key, which can have a maximum of 4 characters, and a descriptive text.
  1. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. The sequence indicates the order of priority of the accesses.
In doing this, you can display the defined combinations of key fields using the "possible entries" facility.
  1. Create new condition types by copying similar existing ones. In doing so, you must make the following specifications:
  • Specify an alphanumeric key for the condition type. This can have up to 4 characters. Also enter a descriptive text.

  • Specify an access sequence for the condition types. (You need not define an access sequence for header conditions.)

  1. Maintain the detail screen of the condition type

You have the following additional options:

  • To improve system performance, you can optimize the accesses for a condition type. In searching for condition records, the SAP System will then initially check only the document header fields.
  • You can define upper and lower limits for the value of a condition at condition type level. In this way, you limit the amounts or scale values in the associated condition records. Specify these limits.
  • You can set exclusion indicators for condition types in order to prevent the use of too many condition types in the price determination process. In the standard system, for example, exclusion indicator 'X' determines that either the automatic price or the manual price is used, but not both.

In this step you define the calculation schemas (also known as "pricing procedures") used in the price determination process.

In the calculation schema, you specify which condition types are to be taken into account in which order. During the price determination process, the SAP System automatically establishes which calculation schema is valid for a business transaction and successively takes into account the condition types it contains.

Transaction/event key (internal processing key)

To enable the system to find the relevant account for provisions (delivery costs or miscellaneous provisions, for example), you must assign a transaction/event key to each condition type that is relevant to provisions in the calculation schema.

If purchase account management is active within a company code, you must specify the transaction/event key in the field 'AccKy'. If not, you make this specification in the field 'Provis.'.

  • Use the transaction/event keys supplied with the standard system, since any new ones must first be set up within the account determination facility.
  • If you define your own calculation schemas, the key should begin with either the letter Z or the digit 9, since SAP keeps these name slots free in the standard system supplied.
  • You should not change the calculation schemas that are included in the standard SAP System.

The following calculation schemas are predefined in the standard system:

RM0000 and RM1000
Control the price determination process in purchase orders, quotations, and scheduling agreements.
Both calculation schemas require 2 condition types for the gross price: one for automatic price determination (standard: PB00) and one for manual maintenance (standard: PBXX).
RM0001 and RM1001
Determine which condition types you can enter in the headers of purchasing documents with master conditions (for example, contracts).
RM0002, RM1002
Determine which additional condition types you can enter in purchasing document items with master conditions or in the purchasing info record.
RMMP00
Defines the condition type for determining the market price, which can be entered for each material.
RM2000
Controls the process of determining delivery costs in stock transport orders and stock transport scheduling agreements.
Note
In the calculation schemas RM0000, RM1000, RM0001 and RM1001, the field "interim total" must contain the following values:
Gross value: 1
Effective value: 2
Net value: 3
  1. Check the extent to which you can use the calculation schemas that are included in the standard SAP System supplied.
  2. Create new calculation schemas by copying similar existing ones.
  • To do this, enter a key, which can have up to 6 characters, and a descriptive text.

  • For each schema, enter the condition types in the order of their usage.

Maintain the lines of the calculation schema.
  1. Then define schema groups for suppliers and purchasing groups.
  2. Assign schema groups to purchasing organizations.
  3. Assign the calculation schemas to purchasing documents/operations:
  • Standard purchase order (depending on the schema groups of supplier and purchasing organization)

  • Stock transport order (depending on supplying plant, document type, and schema group of the purchasing organization)

  • Market price (depending on the purchasing organization)

  1. Maintain transaction/event keys (internal processing keys)
  2. Assign transaction/event keys in the calculation schema.

If several condition records are valid in the price determination process, you must define rules stipulating which conditions are selected and which are disregarded. To do this, use the condition exclusion mechanism.

The exclusion of condition records is controlled via exclusion groups. An exclusion group is a list of condition types that are compared with each other during the price determination process. The result may be the exclusion of a whole group of conditions or the exclusion of individual conditions within a group.

The result of the price determination process can thus be influenced with regard to a desired criterion (for example, the lowest price) by the exclusion of certain condition types, whereas others are taken into account in this process.

Example
You can define a condition exclusion that determines the most favorable price and excludes less favorable but fundamentally possible pricing results. The lowest price then overrides the condition type priorities that would have been dictated by the access sequence.

In the calculation schema you define the procedure by which selection within or between the condition exclusion groups takes place. The following possibilities are available:

  • Selection of the most favorable condition type within a condition exclusion group.
  • Selection of the most favorable condition record of a condition type if more valid condition records exist (for example, selection from different condition records of condition type PR00)
  • Selection of the most favorable of two condition exclusion groups (in this case, all condition types of the two groups are cumulated and the totals compared with each other)

The tables for the exclusion of conditions are supplied empty. You must therefore work through the following points if you wish to use the condition exclusion facility:

  • Define condition exclusion groups
  • Assign condition types to condition exclusion groups
  • Enter condition exclusion groups in the calculation schema and define a procedure for the determination of the condition types to be excluded.
  1. Create a condition exclusion group by entering an alphanumeric key that is max. four characters long, together with a description.
  2. Assign the condition types to a condition exclusion group. A condition exclusion group can contain any number of condition types.
  3. Enter the condition exclusion group in the calculation schema that you will be using for price (or cost) determination purposes.
  4. In the process, note the sequence (consecutive numbers) in which the exclusion groups are to be processed.
You can use two exclusion groups for condition exclusion purposes. In this case, you must choose procedure "C", which determines the lowest price between two exclusion groups.





CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 18412 Date: 20240523 Time: 205856     sap01-206 ( 239 ms )