SAP ABAP IMG Activity SIMG_EXG_0009 (Define purchase fees)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ OIA (Package) Exg exchanges

IMG Activity

ID	SIMG_EXG_0009	Define purchase fees
Transaction Code	S_SO5_65000050	IMG activity: SIMG_EXG_0009
Created on	19990913
Customizing Attributes	SIMG_EXG_0009	Define purchase fees
Customizing Activity	SIMG_EXG_0009	Define purchase fees

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	SIMG_CFMENUOLMEOMER2

In this step you define condition types.

The condition types are used to represent pricing elements such as prices, discounts, surcharges, taxes, or delivery costs in the SAP System. These are stored in the system in condition records.
You also have the option of entering conditions requiring subsequent (end-of-period rebate) settlement. A separate topic "Subsequent Settlement" in the Purchasing IMG covers this functionality.

For condition types for which you wish to maintain conditions with their own validity period, you must 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.

Example:

An access sequence has been assigned to condition type PB00 so that prices can be maintained in purchasing info records and contracts.

No access sequence has been assigned to condition type RC00 because it does not have a validity period of its own. In the standard system, it is always maintained simultaneously with the price and is valid for the period of the price.

Note

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 in the purchasing document manually. You can limit the change options for a condition type in this step.

SAP recommendation

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

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

Actions

1. Check the extent to which you can use the condition types that are included in the standard SAP system supplied.
2. Create new access sequences by copying and changing similar existing ones.
   In doing so, you must specify the following:

• enter an alphanumeric key (which can have a maximum of 4 characters) for the condition type, together with a descriptive text.
• Specify an access sequence for the condition types. (For header conditions, you need not specify an access sequence.)

1. Maintain the detail screen for the condition type.

Note:
To improve performance, you can optimize the accesses for a condition type. In searching for condition records, the SAP System will then initially check the header fields in the document only.

Business Attributes

ASAP Roadmap ID	201	Make global settings
Mandatory / Optional	2	Optional activity
Critical / Non-Critical	2	Non-critical
Country-Dependency	A	Valid for all countries

Assigned Application Components

Documentation Object Class	Documentation Object Name	Current line number	Application Component	Application Component Name
SIMG	SIMG_CFMENUOLMEOMER2	0	HLA0006038	Vendor-Material Relationships and Conditions

Maintenance Objects

Maintenance object type

C

Customizing Object

Assigned objects
Customizing Object	Object Type	Transaction Code	Sub-object	Do not Summarize	Skip Subset Dialog Box	Description for multiple selections
VV_T685A_MA	V - View	SM30		☐	☐	Condition Type: (Purchasing)

History

Last changed by/on	SAP	20041026
SAP Release Created in