In the output control of SAP, we sometimes need to add fields that are not defined by the system as the criteria table, and we need to modify the enhancements in order to achieve that requirement.
The communication structure used in the output control
- KOMKBK1 (Output determination Communication Area CAS APPL. K1)
- KOMKBV1 (Output determination Communication Area Header APPL. V1)
- KOMKBV2 (Output determination Communication Area Header APPL. V2)
- KOMKBV3 (Output determination Communication Area Header APPL. V3)
- KOMKBV5 (communication Structure for Output Control Groups Appl. V5)
- KOMPBV1 (Output determination Communication Area Item APPL. V1)
- KOMPBV2 (Output determination Communication Area Item APPL. V2)
- KOMPBV3 (Output determination Communication Area Item APPL. V3)
SAP has reserved includes in these structures, and users can add new fields to these structures
- Sales Activities:komkbz1 (in KOMKBK1)
- Sales document HEADER:KOMKBZ3 (in KOMKBV1)
- Delivery header:komkbz4 (in KOMKBV2)
- Groups Header:komkbzf (in KOMKBV5)
- Billing document HEADER:KOMKBZ5 (in KOMKBV3)
- Sales document ITEM:KOMPBZ1 (in KOMPBV1)
- Delivery item:kompbz3 (in KOMPBV2)
- Billing document ITEM:KOMKBZ5 (in KOMPBV3)
If you need to create a condition table with new fields, we need to add the field to the KOMBZ structure at the same time (Kombz is included in the communication structure Komb).
After completing the above two, we also need to enhance the SAP code to assign values to the fields of the communication structure. SAP has a lot of exits in Rvcomfzz, RVCOMFZ1 and RVCOMFZ4 units.
The export in RVCOMFZ1 is as follows:
userexit_kompbv2_fill (item fields in delivery)
- userexit_kompbv2_partner (item fields for partners in delivery)
- userexit_kompbv3_fill (item fields in billing document)
- userexit_kompbv3_partner (item fields for partners in billing document) /span>
The export in Rvcomfzz is as follows:
- Userexit_komkbk1_fill (header fields in sales activities)
- Userexit_komkbk1_partner (header fields for partners in Sales Activ.)
- Userexit_komkbv1_fill (header fields for sales documents)
- Userexit_komkbv1_partner (header fields for partners in sales documents)
- Userexit_komkbv2_fill (header fields in delivery)
- Userexit_komkbv2_partner (header fields for partners in delivery)
- Userexit_komkbv3_fill (header fields in billing document)
- Userexit_komkbv3_partner (header fields for partners in billing Doc.)
The export in RVCOMFZ4 is as follows:
- Userexit_komkbv5_fill (header field for groups)
In output determination, communication table Komb contains all key fields, can is used for conditions for output deter Mination.
When you create the new fields for output determination, you can distinguish between and types of fields:
- Fields is used in condition tables
- Fields which is only used to query conditions.
Both Types of field has to is included in KOMKBV1. Fields which is used to query conditions does not has the to is included in Komb and t681f or in the field catalog.
The detailed steps for adding custom fields to the order output control are as follows;
1. Add custom fields to the KOMKBZ3 in KOMKBV1 with SE11;
2. Add custom fields to the KOMBZ in Komb with SE11;
3. Add the custom field to the Allowed field with V/86 (the field must be from Komb, otherwise it will not be visible when the table is being constructed);
4, define the condition table with V/57;
5. Define the order of condition storage;
6, the condition storage order is assigned to the condition type;
7. Modify sub-procedures in code RVCOMFZZ Userexit_komkbv1_fill
sd--How to add custom fields in output control