Ansicht
Dokumentation
OFTV_ESA_BADI_12 - BAdI: Subtype Mapping for E-Mail and Credit Cards
BAL Application Log Documentation Fill RESBD Structure from EBP Component StructureThis documentation is copyright by SAP AG.
You can use this BAdI to enhance the inbound structures of the following proxies:
- EmployeeCommunicationDataEMailAddressRequest_In (Maintain E-Mail Address)
- You can implement the BAdI if you want to change the subtype for the e-mail address.
- EmployeePaymentCardDetailsCreateRequest_In (Create Payment Card)
- You can implement the BAdI if you want to change the subtype for credit cards.
This BAdI uses the interface IF_EX_PAD_SE_SUBTY_CONV. The interface contains the following methods:
- DETERMINE_EMAIL_SUBTY Define Subtype for E-Mail Address
- Implement the DETERMINE_EMAIL_SUBTY method to define a different subtype for the e-mail address in the Communication infotype (0105).
- DETERMINE_CREDITCARD_SUBTY Define Subtype for Credit Card
- Implement the DETERMINE_CREDITCARD_SUBTY method to define a different subtype for the credit card in the Communication infotype (0105).
The default implementation class CL_PAD_SE_SUBTY_CONV is also available. This class sets the following default subtypes:
- 0010 for E-Mail Address
- 0011 for Credit Card
In the standard system, the data for the e-mail address is saved in the E-Mail subtype 0010 of the Communication infotype (0105). The data for the credit card is saved in subtype 0011 Credit Card Number(s) of the Communication infotype (0105).
- In the standard system, there is no activated BAdI implementation.
- A default code is not executed automatically.
- The BAdI is filter-independent.
For information about the implementation of BAdIs in the context of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
BAL_S_LOG - Application Log: Log header data General Material Data
This documentation is copyright by SAP AG.
Length: 3016 Date: 20240523 Time: 202626 sap01-206 ( 94 ms )