SAP SOURCE_DETAILS_GET_VIA_AS_GD13 Function Module for

Search SAP Function Modules

SOURCE_DETAILS_GET_VIA_AS_GD13 is a standard source details get via as gd13 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 source details get via as gd13 FM, simply by entering the name SOURCE_DETAILS_GET_VIA_AS_GD13 into the relevant SAP transaction such as SE37 or SE38.

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

Function SOURCE_DETAILS_GET_VIA_AS_GD13 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 'SOURCE_DETAILS_GET_VIA_AS_GD13'"
  EXPORTING
*  I_RLDNR =  "Ledger Name
*  I_ARCH_OBJECT =  "Archiving Object
*  I_SUMMARY_REC_READ = GUSL_C_TRUE "X = Field Catalogs / Files for Totals Records
*  I_NO_MESSAGES = GUSL_C_FALSE "X = No Warnings or I Messages Output

TABLES
   I_SELECTIONS =  "Technical Names of Fields with Selection Conditions
   E_FIELDCAT =  "Field Catalogs for Archive Access Via SAP AS
*  E_FIELDCAT_ACCESS_FAILED =  "Field Catolog Via Which no AS Access was Possible

EXCEPTIONS
   PARAMETERS_INVALID = 1    CUSTOMIZING_ENTRIES_NOT_FOUND = 2    ARCH_OBJECT_OR_LEDGER_INVALID = 3 

.

IMPORTING Parameters details for SOURCE_DETAILS_GET_VIA_AS_GD13

I_RLDNR - Ledger Name

Data type: GLU1-RLDNR
Optional: Yes
Call by Reference: Yes

I_ARCH_OBJECT - Archiving Object

Data type: ADMI_RUN-OBJECT
Optional: Yes
Call by Reference: Yes

I_SUMMARY_REC_READ - X = Field Catalogs / Files for Totals Records

Data type: GUSL_BOOL
Default: GUSL_C_TRUE
Optional: Yes
Call by Reference: Yes

I_NO_MESSAGES - X = No Warnings or I Messages Output

Data type: GUSL_BOOL
Default: GUSL_C_FALSE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for SOURCE_DETAILS_GET_VIA_AS_GD13

I_SELECTIONS - Technical Names of Fields with Selection Conditions

Data type: GUSL_T_SELECTION
Optional: No
Call by Reference: No ( called with pass by value option)

E_FIELDCAT - Field Catalogs for Archive Access Via SAP AS

Data type: AIND_TT_ARCHINDEX
Optional: No
Call by Reference: No ( called with pass by value option)

E_FIELDCAT_ACCESS_FAILED - Field Catolog Via Which no AS Access was Possible

Data type: AIND_TT_ARCHINDEX
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

PARAMETERS_INVALID - Parameters are Incorrect

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CUSTOMIZING_ENTRIES_NOT_FOUND - Customizing Entries are not Complete

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ARCH_OBJECT_OR_LEDGER_INVALID - Wrong Archiving Object or Ledger

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SOURCE_DETAILS_GET_VIA_AS_GD13 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.

ABAP code using 7.40 inline data declarations to call FM SOURCE_DETAILS_GET_VIA_AS_GD13

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