SAP AD_TRANSF_SAC Function Module for transfer SAC to GRID









AD_TRANSF_SAC is a standard ad transf sac SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for transfer SAC to GRID 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 ad transf sac FM, simply by entering the name AD_TRANSF_SAC into the relevant SAP transaction such as SE37 or SE38.

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



Function AD_TRANSF_SAC 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 'AD_TRANSF_SAC'"transfer SAC to GRID
EXPORTING
P_KEY = "key for add. A&D data tables

TABLES
P_TB_ALL = "all additional A&D data
.



IMPORTING Parameters details for AD_TRANSF_SAC

P_KEY - key for add. A&D data tables

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

TABLES Parameters details for AD_TRANSF_SAC

P_TB_ALL - all additional A&D data

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

Copy and paste ABAP code example for AD_TRANSF_SAC 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_key  TYPE ADSPCM_TAB_ALL_KEY, "   
lt_p_tb_all  TYPE STANDARD TABLE OF ADSPCM_TAB_ALL. "   

  CALL FUNCTION 'AD_TRANSF_SAC'  "transfer SAC to GRID
    EXPORTING
         P_KEY = lv_p_key
    TABLES
         P_TB_ALL = lt_p_tb_all
. " AD_TRANSF_SAC




ABAP code using 7.40 inline data declarations to call FM AD_TRANSF_SAC

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!