Hierarchy

⤷

⤷

IMG Activity
ID | CONFIRM_CUST_SUBSCR | BAdI: Change Customer-Specific Fields |
Transaction Code | S_E36_82000164 | (empty) |
Created on | 20070823 | |
Customizing Attributes | CONFIRM_CUST_SUBSCR | Change Part of Screen for Customer-Specific Fields |
Customizing Activity | CONFIRM_CUST_SUBSCR | Change Part of Screen for Customer-Specific Fields |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | WORKORDER_CONFIRM_CUST_SUBSCR |
Use
This BAdI enables you to change the subscreen for customer-specific fields in the time ticket (single-screen entry CO11N/COR6N and in the order header confirmation CO15/CORK).
You can use this BAdI in the software component EA-APPL only.
The following methods are available:
- Method PUT_DATA_TO_SCREEN:
This method is for the transfer of order, operation, and confirmation data to a dynpro with customer-specific data:
- Parameter IV_ACTIVITY_CATEGORY:
- Activity category of transaction ('H' = creation of a confirmation, 'A' = display of a confirmation, 'L' = cancellation of a confirmation).
- Parameter IV_HEADER_CONF:
- This indicator is set when an order header confirmation is generated, displayed, or cancelled.
- Parameter IS_ORDER_HEADER:
- This structure contains order header data.
- Parameter IS_OPERATION:
- This structure contains operation data and is not populated in the case of an order header confirmation.
- Parameter IS_CONFIRMATION:
- This structure contains the confirmation data.
- Parameter IT_CUST_FIELDS:
- This table contains technical information on the customer-specific fields in customer include CI_AFRU.
- Method GET_DATA_FROM_SCREEN:
This method is for transferring back customer-specific data:
- Parameter ES_CONFIRMATION:
- This structure contains the confirmation data. However, only the values of the customer-specific fields of the customer include CI_AFRU are taken into account from this structure.
Requirements
You have specified the data elements that are to be displayed as customer-specific fields in the confirmation in the database table AFRU in the customer include CI_AFRU.
Standard settings
- The Business Add-In is active in the standard system.
- The Business Add-In cannot be used multiple times.
- The Business Add-In is not filter-dependent.
Activities
SAP supplies the default implementation WORKORDER_CONF_CUST_SUBSCR_DEF as active implementation. If you want to define a partial screen of your own, you must change this BAdI implementation.
Example
Further notes
Note that the 'COMMIT_WORK' statement must not be executed within the methods because this would inevitably lead to database inconsistencies.
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
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 | 20070911 |
SAP Release Created in | 603 |