Académique Documents
Professionnel Documents
Culture Documents
One of the uses of the Condition Index tables is to maintain and display condition records for multiple condition types or multiple access sequences at
the same time. This allows for functionality in VK12 and VK13 that is similar to using the new VK32 and VK33 transactions with a pricing report.
When clicked, the Select Using Index button will display each active index table that is configured in SAP, similar to how SAP displays the various
condition tables available in the access sequence assigned to a Condition Type when clicking the Key Combination box.
Pricing indexes are not condition type, or condition table, specific. This allows for the maintenance of multiple condition types across multiple condition
tables, all at the same time. This can be particularly useful when updating all prices for a given customer or material.
Example
A customer / material discount is created for 10% using condition type ZZ01.
A customer specific discount is offered to the same customer, but for only 5%, using condition type ZZ02.
Using normal condition record maintenance these two records will always need to be maintained separately, as they are two different condition types,
even if they were the same they are in two different condition tables.
Using standard condition index 2, which is not activated by default, it is possible to maintain both of these conditions at the same time.
On the selection screen there are no required fields, meaning that condition records for even multiple customers could be selected, or across multiple
sales areas.
In the example above condition type ZZ01 would not have been visible in condition index 2 if requirement 001 was selected instead of requirement
002.
SAP Help Information
Challenges
Set up condition indices – V/I2
In order to populate the condition index table with condition records that were previously created it is necessary to Set up the condition indices, which is
the 4th activity in Maintain Condition Index and can also be launched using Transaction V/I2 or program RV15F001. The first step that SAP performs
when executing this process is to regenerate each pricing condition table, if any pricing condition table fails then the whole process fails with a Short
Dump that can be viewed in transaction ST22.
An issue I have run into has to do with the Pricing communication structure KOMG. If a pricing condition table exists in SAP, and for some reason the
fields in the table are no longer in structure KOMG then a short dump would have been generated during the Set up condition indices step. The short
dump references Program RV15F001 and program RV13AXXX, where AXXX is the condition table that SAP is having trouble regenerating.
In the example above SAP had trouble regenerating condition table A144 and it was due to the custom component PRODH1 being missing from
KOMG. PRODH1 was a material specific attribute that should have been included in a customer specific append structure to the Pricing
Communication Item structure KOMPAZ.
Once the problems running RV12A001 have been resolved it should be possible to successfully run the Set up of condition indicies.