Kontakt

Ansicht
Dokumentation

PRICING_FIELDS - Edit Fields Used in Pricing Enhancements

PRICING_FIELDS - Edit Fields Used in Pricing Enhancements

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, for each routine or user exit, you can display or edit fields that need to be fed with data for the execution of customer-owned implementations.

When executing pricing, the business transaction in Service does not feed all fields of the communication structures KOMK and KOMP, but only the ones that are relevant for a specific process. Therefore, it is possible that a BAdI implementation evaluates a KOMK field or a KOMP field that is not fed. To prevent this, you can list the pricing-relevant KOMK fields and KOMP fields that you need in your coding as input fields.

  • The system uses a code scan to find fields of the communication structures KOMKand KOMP. You can include or remove fields that have been found by the code scan.
Note: As the code scan uses a simple algorithm (string search for KOMK and KOMP, only the first level of the code), there is no guarantee that all relevant KOMK and KOMP fields can be detected by the system. For this reason, also carry out manual checks.
  • You can add any fields manually that need to be fed with data but are not detected by the system during the code scan.
  • Processing level: You can choose the level for which the system checks the requirement during pricing.

The following fields of the communication structure KOMK are not displayed but are fed with data by default:

  • BELNR
  • KALSM
  • KAPPL
  • KNUMV
  • MANDT
  • TRTYP

The following fields of the communication structure KOMP are not displayed but are fed with data by default:

  • CEPOK
  • FXMSG
  • KPOSN
  • KZNEP
  • KZWI1
  • KZWI2
  • KZWI3
  • KZWI4
  • KZWI5
  • KZWI6
  • MWSBP
  • NETPR
  • NETWR
  • PRSOK
  • WAVWR

  1. On the Fields Used in Pricing Enhancementsscreen, in the Pricing Procedurefields, you can restrict the search for the used fields to one or more pricing procedures. If you leave these fields blank, the system searches in all pricing procedures.
  2. On the Edit Fields Used in Pricing Enhancementsscreen, you can expand the Routines (VOFM) node and the User Exits node to display the routines and the user exits.
  3. Double-click a routine or user exit.
  4. Mark the fields that the system found during the code scan and then choose Select Fieldor Deselect Field. You can also add new fields by choosing Add Field Manually.
  5. To see which routines or user exits you have already checked, you can mark each routine or user exit as checked by choosing Mark Implementation as Checked.
  6. Under the Requirements (KOBED)node, choose Processing Level. You can then display or change the processing level (header, item, or condition level) of the requirement routine.
  7. Save your settings.

Note

You can display an implemented method for customer-defined fields.

Choose an entry and double-click ABAP coding. The coding shows which fields from the KOMK and the KOMP structures are used, KUNNR (Sold-To Party), for example.

You have implemented a routine that calls a function module that uses a field of the communication structure KOMP itself. For the execution of this routine, this field must be fed with data. The system is unable to find this field by using a code scan because a function module is called. You can add these fields manually so that they are fed with data for the routine execution.






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 4677 Date: 20240523 Time: 215218     sap01-206 ( 109 ms )