Kontakt

Ansicht
Dokumentation

OFTV_ESA_BADI_01 - BAdI: Mapping for ExpenseArrangementExternalInputTransmitRequest

OFTV_ESA_BADI_01 - BAdI: Mapping for ExpenseArrangementExternalInputTransmitRequest

rdisp/max_wprun_time - Maximum work process run time   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

PTRM_SE_EXPARR_CONV is the BAdI for proxy class CL_PTRM_SE_EXPARREXTINTRAN_REQ. The various interface methods of the BAdI help you extend the functionality of the class.

The BAdI offers the following methods :

  • GET_MASSN_FROM_EVENTS
  • DETERMINE_EMAIL_MAIN_SYSTEM
  • DETERMINE_CRDTCARD_MAIN_SYSTEM
  • COMMUNICATION_DATA_MAPPING
  • DETERMINE_EMAIL_SUBTY
  • DETERMINE_CRDTCARD_SUBTY
  • INBOUND_MAPPING_ADMIN_DETAILS
  • INBOUND_MAPPING_BANK_DETAILS
  • INBOUND_MAPPING_COMM_DATA
  • INBOUND_MAPPING_PERS_ADDRESS
  • INBOUND_MAPPING_PERS_DETAILS
  • INBOUND_MAPPING_EXPARR_ASSGN
  • INBOUND_MAPPING_EXPARR_CST

GET_MASSN_FROM_EVENTS: This method provides standard mapping between personnel_event_type_code and MASSN. MASSN is obtained from table T529A using a particular logic which involves the FUNCH, STAT2 and NAMEN values.

You can override this logic using the above mentioned BAdI method.

DETERMINE_EMAIL_MAIN_SYSTEM: In a data sharing scenario, you need to determine which is the main system. In this method, e-mail data comes in from both the e-mail system and Travel Mini master. The data that is finally replicated should be from the main system.

This BAdI method allows the customer to set the main system for e-mail.

DETERMINE_CRDTCARD_MAIN_SYSTEM: In a data sharing scenario, you need to determine which is the main system. In this method, payment card data comes in from both the credit card system and Travel Mini master. The data that is finally replicated should be from the main system.

This BAdI method allows the customer to set the leading system for payment cards.

COMMUNICATION_DATA_MAPPING: Standard SAP delivery updates the following subtypes of infotype 0105, 0020, CELL, MPHN, PAGR, 0005, and 0006. If you add a new subtype or change the communication subtypes, you can use this BAdI method to change the SAP standard delivery.

DETERMINE_EMAIL_SUBTY: You can map e-mail either to subtype 0010 or MAIL of the infotype. Standard SAP delivery uses 0010 as the e-mail subtype. You can use this BAdI method to change this.

DETERMINE_CRDTCARD_SUBTY: Credit card data is mapped to subtype 0011 in standard SAP delivery. This BAdI method allows you to change this to any subtype.

INBOUND_MAPPING_< > : The implementing class CL_PTRM_SE_EXPARREXTINTRAN_REQ uses the PAITF adapter to access the new (decoupled) Infotype Framework. This is done via "R" structures (HCMT_BSP_PA_XX_Rnnnn). The standard SAP delivery contains mapping between elements of the "R" structure and elements of the message interface.

You can customize both the "R" structure and the message interface. To support this option, you can change/extend/add mappings at each infotype level through the following methods

  • INBOUND_MAPPING_ADMIN_DETAILS,, -> Change/enhance std &lt;Admin_details - IT0001> mapping
  • INBOUND_MAPPING_BANK_DETAILS ,, -> Change/enhance std < bank_details - IT0009> mapping
  • INBOUND_MAPPING_COMM_DATA ,, -> Change/enhance std < Comm_data - IT0105> mapping
  • INBOUND_MAPPING_PERS_ADDRESS ,, -> Change/enhance std < pers address - IT0006> mapping
  • INBOUND_MAPPING_PERS_DETAILS ,, -> Change/enhance std < personal_details - IT0002> mapping
  • INBOUND_MAPPING_EXPARR_ASSGN ,, -> Change/enhance std < ExpArrAssignment - IT0017> mapping
  • INBOUND_MAPPING_EXPARR_CST ,, -> Change/enhance std < ExpArrCostDist - IT0027> mapping






CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 4236 Date: 20240523 Time: 221850     sap01-206 ( 63 ms )