Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MD05 (Package) Development class KANBAN
IMG Activity
| ID | PK_CALL_INTERFACE | BAdI: Displaying User-Specific Data When Creating Kanbans/SumJCs |
| Transaction Code | S_KA5_12001383 | (empty) |
| Created on | 20021220 | |
| Customizing Attributes | PK_CALL_INTERFACE | BAdI: Displaying User-Specific Data When Creating Kanbans/SumJCs |
| Customizing Activity | PK_CALL_INTERFACE | BAdI: Displaying User-Specific Data When Creating Kanbans/SumJCs |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | PK_CALL_INTERFACE |
Use
This Business Add-In (BAdI) is used in the KANBAN (PP-KAB) component.
You can use this BAdI in transaction PK23 to display or manage your own data. In the background, you can also manipulate data without having to display the data.
Requirements
You are recommended to created your own function group or a module pool in which you can define your own subscreens, modules and function modules (see example: Function group MPK_EXAMPLE).
Standard settings
Activities
First, create an implementation of the Business Add-In.
Assign your program and screen to the subscreen area CUSTSCR1 in screen 305 in Transaction SE19.
Method GET_DATA
The system fetches the data from the BAdI instance so that you can fetch the data from the standard program. You should access this method once in PBO and once in PAI of your subscreen before your data processing.
The importing parameters CUOBJ and JITOAD_T are only taken into account for the summarized JIT calls (not for event-drived kanban).
Method PUT_DATA
The data is put in the instance of the BAdI so that you can transfer the data to the standard program. You should access this method once in PAI of your subscreen after your data processing.
The importing parameters CUOBJ and JITOAD_T are only taken into account for summarized JIT calls (not for event-driven kanban).
Method SAVE
You can save your additional data. The method is accessed after all the standard changes have been executed. You may not use the instruction COMMIT WORK in the method. This instruction is accessed after the method has been accessed.
Example
You can use a subscreen implementation as an example from the function group MPK_EXAMPLE and screen 0300.
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 3 | Nonrequired 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 | PK_CALL_INTERFACE | 0 | HLA0006760 | KANBAN |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20030221 |
| SAP Release Created in | 470 |
