SAP AF_CONGLOMERATE_PREPARE Function Module for









AF_CONGLOMERATE_PREPARE is a standard af conglomerate prepare SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 af conglomerate prepare FM, simply by entering the name AF_CONGLOMERATE_PREPARE into the relevant SAP transaction such as SE37 or SE38.

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



Function AF_CONGLOMERATE_PREPARE 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 'AF_CONGLOMERATE_PREPARE'"
EXPORTING
P_BUSINESSKEY = "
T_TABNAME = "

IMPORTING
F_CONGLOMERATE = "
.



IMPORTING Parameters details for AF_CONGLOMERATE_PREPARE

P_BUSINESSKEY -

Data type: TARCHENGINE01-BUSINESSKEY
Optional: No
Call by Reference: Yes

T_TABNAME -

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

EXPORTING Parameters details for AF_CONGLOMERATE_PREPARE

F_CONGLOMERATE -

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

Copy and paste ABAP code example for AF_CONGLOMERATE_PREPARE 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_p_businesskey  TYPE TARCHENGINE01-BUSINESSKEY, "   
lv_f_conglomerate  TYPE BCA_F_CONGLOMERATE, "   
lv_t_tabname  TYPE TYP_T_TABNAME. "   

  CALL FUNCTION 'AF_CONGLOMERATE_PREPARE'  "
    EXPORTING
         P_BUSINESSKEY = lv_p_businesskey
         T_TABNAME = lv_t_tabname
    IMPORTING
         F_CONGLOMERATE = lv_f_conglomerate
. " AF_CONGLOMERATE_PREPARE




ABAP code using 7.40 inline data declarations to call FM AF_CONGLOMERATE_PREPARE

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.

"SELECT single BUSINESSKEY FROM TARCHENGINE01 INTO @DATA(ld_p_businesskey).
 
 
 


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!