Hierarchy
⤷ SD-BF-PR (Application Component) Pricing and Conditions
⤷ VF_PRC_PRICEINQUIRY (Package) Mass Processing of Price Inquiries
IMG Activity
ID | SDPIQRELATTRUE_PL | Define Fields Used in BAdI: Price Inquiry Preparation |
Transaction Code | S_EBJ_98000410 | (empty) |
Created on | 20131111 | |
Customizing Attributes | SDPIQRELATTRUE_PL | Define Fields Used in BAdI: Price Inquiry Preparation |
Customizing Activity | SDPIQRELATTRUE_PL | Define Fields Used in BAdI: Price Inquiry Preparation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SDPIQRELATTRUE_PL |
Use
In this Customizing activity, you can display or edit fields that need to be fed with data for the execution of BAdI: Price Inquiry Preparation.
The price inquiry does not feed all fields of 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 your 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 KOMK and KOMP. You can include or remove fields that have been found by the code scan.
Note: Since 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 manually add any fields that need to be fed with data but are not detected by the system during the code scan.
Requirements
This activity is relevant, if you use an implementation of BAdI: Price Inquiry Preparation, methodADAPT_KOMK_KOMP_DATA.
Standard settings
Activities
The system scans the active BAdI implementation class for method ADAPT_KOMK_KOMP_DATA and suggests relevant fields to apply for optimized pricing.
- Double-click BAdI implementation class to get the fields of the enhanced communication structure.
- Icon and text show how the system found each document field, Not Selected (found by using code scan) or Selected (found by using code scan), for example.
- You can edit the list of fields, create a new entry manually or delete an entry for combination of document structure and document field, for example.
- If you want to apply fields for optimized pricing, select fields and choose Select Field.
Hint: By using Select Field, you can apply the proposals from the code scan.
Hint:
For your convenience, you can display an implemented method for customer-defined fields.
Choose an entry and double-click ABAP coding. The coding shows which fields from structure KOMK and structure KOMP are used, KUNNR (Sold-To Party) for example.
Example
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-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 | SDPIQRELATTRUE_PL | 0 | HLA0006561 | Pricing and Conditions |
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 |
IMGDUMMY | D - Dummy object | SDPIQRELATTRUE_PL | 1 |
History
Last changed by/on | SAP | 20131120 |
SAP Release Created in | 618 |