SAP ADFSH_MAP_DETAIL_DB_TO_BAPI Function Module for Flight Scheduling: Map the fields of DB tables to BAPI structure









ADFSH_MAP_DETAIL_DB_TO_BAPI is a standard adfsh map detail db to bapi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Flight Scheduling: Map the fields of DB tables to BAPI structure processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for adfsh map detail db to bapi FM, simply by entering the name ADFSH_MAP_DETAIL_DB_TO_BAPI into the relevant SAP transaction such as SE37 or SE38.

Function Group: ADFSH_OTHER
Program Name: SAPLADFSH_OTHER
Main Program: SAPLADFSH_OTHER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ADFSH_MAP_DETAIL_DB_TO_BAPI pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ADFSH_MAP_DETAIL_DB_TO_BAPI'"Flight Scheduling: Map the fields of DB tables to BAPI structure
TABLES
* T_DB_FLGTDET = "Flight Scheduling: Flight Schedule Details
* T_DB_PRTDET = "Flight Scheduling: PRT Detail
* T_BAPI_FLGTDET = "Flight Scheduling BAPI Interface: Flight Detail records
* T_BAPI_PRTDET = "Flight Scheduling BAPI Interface: PRT for Detail records
.



TABLES Parameters details for ADFSH_MAP_DETAIL_DB_TO_BAPI

T_DB_FLGTDET - Flight Scheduling: Flight Schedule Details

Data type: ADFSH_FLGTDET
Optional: Yes
Call by Reference: Yes

T_DB_PRTDET - Flight Scheduling: PRT Detail

Data type: ADFSH_PRTDET
Optional: Yes
Call by Reference: Yes

T_BAPI_FLGTDET - Flight Scheduling BAPI Interface: Flight Detail records

Data type: BAPI_ADFSH_FLGTDET
Optional: Yes
Call by Reference: Yes

T_BAPI_PRTDET - Flight Scheduling BAPI Interface: PRT for Detail records

Data type: BAPI_ADFSH_PRTDET
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for ADFSH_MAP_DETAIL_DB_TO_BAPI Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lt_t_db_flgtdet  TYPE STANDARD TABLE OF ADFSH_FLGTDET, "   
lt_t_db_prtdet  TYPE STANDARD TABLE OF ADFSH_PRTDET, "   
lt_t_bapi_flgtdet  TYPE STANDARD TABLE OF BAPI_ADFSH_FLGTDET, "   
lt_t_bapi_prtdet  TYPE STANDARD TABLE OF BAPI_ADFSH_PRTDET. "   

  CALL FUNCTION 'ADFSH_MAP_DETAIL_DB_TO_BAPI'  "Flight Scheduling: Map the fields of DB tables to BAPI structure
    TABLES
         T_DB_FLGTDET = lt_t_db_flgtdet
         T_DB_PRTDET = lt_t_db_prtdet
         T_BAPI_FLGTDET = lt_t_bapi_flgtdet
         T_BAPI_PRTDET = lt_t_bapi_prtdet
. " ADFSH_MAP_DETAIL_DB_TO_BAPI




ABAP code using 7.40 inline data declarations to call FM ADFSH_MAP_DETAIL_DB_TO_BAPI

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!