Sap Sd Tutorials : Pricing Status Maintenance
In the next sections you volition find information nearly the primary transactions, primary tables, dealing amongst inconsistencies, in addition to generation in status maintenance.
Main transactions
Different products dissimilar pricing as well as SAP tin handgrip it so good at the corporation level .
The following figure shows the principal transactions inward condition maintenance:
Maintain status tables (Customer namespace is between 501 too 999):
- V/03 Create Condition Table (or full general transaction VK03)
- V/04 Change Condition Table (or general transaction VK04)
- V/05 Display Condition Table (or full general transaction VK05)
Maintain condition records:
- VK11 or VK31 Create Condition Record
- VK12 or VK32 Change Condition Record
- VK13 or VK33 Display Condition Record* *
- VK14 or VK34 Create Condition Record amongst Reference
Main tables
The next figure shows the principal tables in condition maintenance.
Condition Table (e.g. A304)
Key: Client, Application, Condition Type, VAKEY, Validity stop date (optional), Release Status (optional)
VAKEY: Variable central fields (fields like Sales Organization, Material Number, Ship-To Party) must be function of the plain catalog (tabular array T681F) too construction KOMG.
Non-Key: Validity starting time appointment (optional), VADAT (Variable data part), KNUMH (Link to KONH too KONP, most unique)
Conditions (Header)
Key: Client, KNUMH
Contains additional header information (created past, created on, sales bargain or advertisement number,…) too the VAKEY every bit string.
Key: Client, KNUMH
Contains additional header information (created past, created on, sales bargain or advertisement number,…) too the VAKEY every bit string.
Conditions (Item)
Key: Client, KNUMH, KOPOS (if status supplements exists)
Contains important pricing information (rate, unit of measurement, calculation type, deletion indicator...)
Key: Client, KNUMH, KOPOS (if status supplements exists)
Contains important pricing information (rate, unit of measurement, calculation type, deletion indicator...)
Quantity Scales (KONM) (optional)
Value Scales (KONW) (optional)
Value Scales (KONW) (optional)
The following figure shows an example of a status tape inward tables A304, KONH too KONP:
When the user creates a new condition tape in VK11 with the same keys too same validity catamenia, the system issues a popular-up alert that the existing condition record volition live deleted when saving. If the user clicks on ‘OK’, the entry in tabular array Axxx is deleted. The entry inward tables KONH in addition to KONP remains. They tin can live removed by archiving.
When the user creates a novel status tape inwards VK11 alongside the same keys too validity period overlapping the existing condition tape, the system splits the existing status record inward tabular array Axxx.
For farther information please run into SAP Note 66943: Validity periods inward status records.
The deletion modus depends on the field ‘delete fr. DB’ (V_T685A-KDELE) inwards the customizing of condition type (transaction V/06). If it is ‘ ‘ (infinite), when the user deletes a status tape inwards VK12, the deletion indicator is fix inward tabular array KONP (KONP-LOEVM_KO). The entries inwards tabular array Axxx, KONH and KONP rest. Conditions marked for deletion tin live removed from database by archiving.
Dealing alongside inconsistencies
When fault message VK067 occurs inward condition maintenance, this is due to inconsistency. Report VK+C can live used to discover inconsistencies inward status tables. Example of inconsistency: entry exists in table Axxx just not inward table KONH or KONP.
To repair, you can overwrite the inconsistent tape by creating a novel status tape alongside the same fundamental together with same validity menstruum.
For farther data, delight encounter SAP Note 94443.
Generation in condition maintenance
SAP Note 886771 : Generation inward condition maintenance explains the iii generation reports inwards status maintenance:
- Report RV12A001: generates condition tables, fast entry screens, selection reports.
- Report RV12D001: generates the reports to “Display Condition Records”
- Report RV14ALLE: generates the pricing reports
In VK12 for example, the program mention contains the tabular array number: RV13Axxx where 30 is the tabular array issue.
In the fast entry screen of VK12 for example, the screen number contains the table number: 1xxx where xxx is the table number. You can check the screen number by going to menu System -> Status.
Post a Comment
Post a Comment