Hierarchy

⤷

⤷

IMG Activity
ID | ISPAM_ARCHV_COND | Archiving Control For Conditions |
Transaction Code | S_KK4_74001533 | IMG Activity: ISPAM_ARCHV_COND |
Created on | 19990816 | |
Customizing Attributes | ISPAM_ARCHV_COND | Archiving Control For Conditions |
Customizing Activity | ISPAM_ARCHV_COND | Archiving Control For Conditions |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ISPAM_ARCHV_COND |
In this IMG activity, you define price dependencies. You can make prices, surcharges, and discounts dependent on almost all the fields in a document. You define these dependencies using the condition tables. In a condition table, you define the combination of fields for which you can create condition records.
Recommendation
Do not change the condition tables in the standard system.
Activities
- Check to what extent you can use the condition tables contained in the standard system.
To do this, you can display the condition tables.
- Before you create a new condition table, you should check whether the fields listed in the field catalog meet your requirements. If you require a field in pricing which is not intended for this usage in the standard system, you must enter it in the field catalog. You can only enter fields from tables KOMG, KOMK or KOMP.
- Create new condition tables. Copy a similar condition table and proceed as follows:
- Enter the name of the table you want to create.
- Bear in mind that you can only choose names between 501 and 999. If you do not make a specification, the system automatically assigns a sequential number.
- Specify whether you would like to create the table with or without a validity period.
- Enter a description for the condition table.
- Select the required fields for the condition table from the list of the permitted fields listed in the field catalog.
- Generate the new condition table.
Note
If, for example, you want to make pricing dependent on the ship-to party, you can only select the customer field in the condition table. You cannot specify the ship-to party in the condition tables since only customer master records exist. It is not until you create an order document that you have the specific function 'ship-to party'. When you subsequently define the access, you can assign the ship-to party source field to the customer field.
- Specify the condition tables in the access sequences.
This way, you establish the link between condition type, access sequence and condition record.
Note
For information on entering fields in the tables KOMK, KOMG, and KOMP, see the System modification section.
Business Attributes
ASAP Roadmap ID | 208 | Establish Archiving Management |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | 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 | ISPAM_ARCHV_COND | 0 | I170007100 | SAP Media |
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 |
OV36 | T - Individual transaction object | OV36 | 0000000001 | Archiving Control For Conditions |
History
Last changed by/on | SAP | 19990816 |
SAP Release Created in |