SAP AFODR_INTEGRATION_BDT_SAVE_DB Function Module for FO Integration: Save the Settings (BDT Transactions)









AFODR_INTEGRATION_BDT_SAVE_DB is a standard afodr integration bdt save db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FO Integration: Save the Settings (BDT Transactions) 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 afodr integration bdt save db FM, simply by entering the name AFODR_INTEGRATION_BDT_SAVE_DB into the relevant SAP transaction such as SE37 or SE38.

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



Function AFODR_INTEGRATION_BDT_SAVE_DB 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 'AFODR_INTEGRATION_BDT_SAVE_DB'"FO Integration: Save the Settings (BDT Transactions)
EXPORTING
I_OBJAP = "Application Object for Integration of FO into CFM

IMPORTING
E_ORDER = "Request/Task

EXCEPTIONS
TRANSPORT_ERROR = 1 DATABASE_ERROR = 2
.



IMPORTING Parameters details for AFODR_INTEGRATION_BDT_SAVE_DB

I_OBJAP - Application Object for Integration of FO into CFM

Data type: CFM_OBJAP
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for AFODR_INTEGRATION_BDT_SAVE_DB

E_ORDER - Request/Task

Data type: TRKORR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

TRANSPORT_ERROR - Error while inserting transport request

Data type:
Optional: No
Call by Reference: Yes

DATABASE_ERROR - Error when updating the database

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for AFODR_INTEGRATION_BDT_SAVE_DB 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:
lv_e_order  TYPE TRKORR, "   
lv_i_objap  TYPE CFM_OBJAP, "   
lv_transport_error  TYPE CFM_OBJAP, "   
lv_database_error  TYPE CFM_OBJAP. "   

  CALL FUNCTION 'AFODR_INTEGRATION_BDT_SAVE_DB'  "FO Integration: Save the Settings (BDT Transactions)
    EXPORTING
         I_OBJAP = lv_i_objap
    IMPORTING
         E_ORDER = lv_e_order
    EXCEPTIONS
        TRANSPORT_ERROR = 1
        DATABASE_ERROR = 2
. " AFODR_INTEGRATION_BDT_SAVE_DB




ABAP code using 7.40 inline data declarations to call FM AFODR_INTEGRATION_BDT_SAVE_DB

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!