Hierarchy
SAP_AP (Software Component) SAP Application Platform⤷
AP-PRC-PR (Application Component) Pricing⤷
PRICING_CUSTOMIZING_C (Package) Customizing for Pricing
IMG Activity
| ID | CRM_CON_FELDPR | BADI for Field Checks, Default Values, Conversions, and so on |
| Transaction Code | S_A2C_40000168 | (empty) |
| Created on | 20001011 | |
| Customizing Attributes | CRM_CON_FELDPR | Badi for Field Checks, Default Values, Conversions, and so on |
| Customizing Activity | CRM_CON_FELDPR | Badi for Field Checks |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /SAPCND/ROLLNAME |
Use
The /SAPCND/ROLLNAME BAdI is available to you if you wish to maintain conditions on the basis of user-defined condition tables and user-defined fields. Using single methods, you can set up the following functions for application fields in the condition table, that define the search criteria for determination:
Field conversion
Field check
Short text determination
Default values
Input help (F4 help)
Locking and unlocking
Authorization check
The /SAPCND/ROLLNAME BAdI has the /SAPCND/ROLLNAME_CONTEXTNAME structure as a filter that comprises three components:
- Data element names of each field in the given condition table
- Condition maintenance context from the /SAPCND/CONTEXT table
- Application from table /SAPCND/T681A
The appropriate BAdI implementation is called using the data element name, and the condition maintenance context. The context dependency for implementation ensures that the above mentioned functions within condition maintenance result in different behavior depending on the context.
As a result of the optional application dependency of the BAdI filter, standard implementations of the the application platform can be overridden, if necessary. Note that the application should remain initial in the filter characteristics, although initial represents an application that has not been more specifically defined. The value '*' is not supported as a value for the application in the filter characteristic of the implementation.
The implementations listed are required for condition record maintenance or display where there are user-defined fields. Condition maintenance produces a runtime error, if BAdI implementations are missing for user-defined fields.
Requirements
User-defined fields must first be listed in the field catalog for the condition technique. If a field is flagged as an access field only in the field catalog, no BAdI implementations are necessary, as such fields never occur in condition records, but only in the field assignment for the access sequence (for example, the price product field in CRM).
In some simple cases, implementation of this BAdI can be omitted, as the fields are checked and processed generically by condition maintenance. You can find details and prerequisites for this in the Release Note on generic processing.
Standard settings
All necessary BAdI implementations have been made to fields in the SAP standard.
Activities
For user-defined fields, implement methods according to the Interface Documentation.
Example
For a typical context specific implementation: Context XYZ permits the maintenance of condition records that contain a specific field in its own XYZ context. In this case, a context-specific implementation of the 'lock' function is considered. (For details, see Interface Documentation for this method).
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20020906 |
| SAP Release Created in | 20C |
