Hierarchy

⤷

⤷

IMG Activity
ID | _PFO_DB_CONVERSION | BAdI: Conversions for Database Access (Segment) |
Transaction Code | S_AER_95000151 | (empty) |
Created on | 20060214 | |
Customizing Attributes | _PFO_DB_CONVERSION | BAdI: Conversions for Database Access (Segment) |
Customizing Activity | _PFO_DB_CONVERSION | BAdI: Conversions for Database Access (Segment) |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | _PFO_DB_CONVERSION |
Use
This Business Add-In (BAdI) is used in the Incentive and Commission Management component.
You use this BAdI to make individual conversions for read access to segment table PFO_SEG. This is necessary when the attributes of data type CHAR are made up of numbers solely.
Requirements
You have transferred data for (customer include) attributes for the segment table (PFO_SEG) from other systems, such as ICM and have written them to the database according to the data type of the source system.
Example
The attribute "segment number" (SEGNR, CHAR 30) is filled from an operational system (data type CHAR 20) with the value 00000000001234567890, and written as such to the database. The selection criterion "segment number" is then used to search for the previously saved segment. For this purpose, the content of the corresponding selection option is read from the interface. Since the value only contains numbers, leading zeros are added. A search with 000000000000000000001234567890 does not produce any hits. A hit is only achieved when the first 10 leading zeros are deleted.
Standard settings
The BAdI implementation PFO_CONVERT_SEGNR is activated in the standard delivery (sample implementation). A default implementation is supplied for the attribute "segment number" for the current BAdI to make the necessary conversions. No differentiation is made for the segment type for which the attribute "segment number" was defined. If this is a requirement, you must implement your own customer logic.
Activities
If you have to carry out conversions of this type for specific attributes of segment table PFO_SEG, you should create an implementation for the required field. A filter value must be set so that the implementation is called during runtime.
Example
The default implementation PFO_CONVERT_SEGNR can be used as a sample implementation.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | _PFO_DB_CONVERSION | 0 | KK40000031 | Incentive and Commission Management (ICM) |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20060214 |
SAP Release Created in | 700 |