SAP SDDIC_ATC_GET_SOURCE Function Module for Get source
SDDIC_ATC_GET_SOURCE is a standard sddic atc get source SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get source 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 sddic atc get source FM, simply by entering the name SDDIC_ATC_GET_SOURCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SDDIC_ATC_REMOTE
Program Name: SAPLSDDIC_ATC_REMOTE
Main Program: SAPLSDDIC_ATC_REMOTE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function SDDIC_ATC_GET_SOURCE 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 'SDDIC_ATC_GET_SOURCE'"Get source.
EXPORTING
I_OBJECT_NAME = "
I_OBJECT_TYPE = "
* I_OBJECT_STATE = 'A' "
* I_DATE_MODIFIED = "
* I_TIME_MODIFIED = "
IMPORTING
E_SOURCE_CONTENT = "
E_GOT_STATE = "
E_GOT_DATE_MODIFIED = "
E_GOT_TIME_MODIFIED = "
E_TAKE_LOCAL = "
E_FORMAT_VERSION = "
EXCEPTIONS
NO_AUTHORIZATION = 1 INVALID_INPUT = 2 NOT_SUPPORTED_OBJECT_TYPE = 3 SOURCE_NOT_FOUND = 4
IMPORTING Parameters details for SDDIC_ATC_GET_SOURCE
I_OBJECT_NAME -
Data type: CHAR40Optional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT_TYPE -
Data type: CHAR4Optional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT_STATE -
Data type: DDOBJSTATEDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_MODIFIED -
Data type: AS4DATEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TIME_MODIFIED -
Data type: AS4TIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SDDIC_ATC_GET_SOURCE
E_SOURCE_CONTENT -
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
E_GOT_STATE -
Data type: DDGOTSTATEOptional: No
Call by Reference: No ( called with pass by value option)
E_GOT_DATE_MODIFIED -
Data type: AS4DATEOptional: No
Call by Reference: No ( called with pass by value option)
E_GOT_TIME_MODIFIED -
Data type: AS4TIMEOptional: No
Call by Reference: No ( called with pass by value option)
E_TAKE_LOCAL -
Data type: SYCHAR01Optional: No
Call by Reference: No ( called with pass by value option)
E_FORMAT_VERSION -
Data type: CHAR4Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_SUPPORTED_OBJECT_TYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SOURCE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SDDIC_ATC_GET_SOURCE 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_i_object_name | TYPE CHAR40, " | |||
| lv_e_source_content | TYPE XSTRING, " | |||
| lv_no_authorization | TYPE XSTRING, " | |||
| lv_e_got_state | TYPE DDGOTSTATE, " | |||
| lv_invalid_input | TYPE DDGOTSTATE, " | |||
| lv_i_object_type | TYPE CHAR4, " | |||
| lv_i_object_state | TYPE DDOBJSTATE, " 'A' | |||
| lv_e_got_date_modified | TYPE AS4DATE, " | |||
| lv_not_supported_object_type | TYPE AS4DATE, " | |||
| lv_i_date_modified | TYPE AS4DATE, " | |||
| lv_source_not_found | TYPE AS4DATE, " | |||
| lv_e_got_time_modified | TYPE AS4TIME, " | |||
| lv_e_take_local | TYPE SYCHAR01, " | |||
| lv_i_time_modified | TYPE AS4TIME, " | |||
| lv_e_format_version | TYPE CHAR4. " |
|   CALL FUNCTION 'SDDIC_ATC_GET_SOURCE' "Get source |
| EXPORTING | ||
| I_OBJECT_NAME | = lv_i_object_name | |
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_OBJECT_STATE | = lv_i_object_state | |
| I_DATE_MODIFIED | = lv_i_date_modified | |
| I_TIME_MODIFIED | = lv_i_time_modified | |
| IMPORTING | ||
| E_SOURCE_CONTENT | = lv_e_source_content | |
| E_GOT_STATE | = lv_e_got_state | |
| E_GOT_DATE_MODIFIED | = lv_e_got_date_modified | |
| E_GOT_TIME_MODIFIED | = lv_e_got_time_modified | |
| E_TAKE_LOCAL | = lv_e_take_local | |
| E_FORMAT_VERSION | = lv_e_format_version | |
| EXCEPTIONS | ||
| NO_AUTHORIZATION = 1 | ||
| INVALID_INPUT = 2 | ||
| NOT_SUPPORTED_OBJECT_TYPE = 3 | ||
| SOURCE_NOT_FOUND = 4 | ||
| . " SDDIC_ATC_GET_SOURCE | ||
ABAP code using 7.40 inline data declarations to call FM SDDIC_ATC_GET_SOURCE
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.| DATA(ld_i_object_state) | = 'A'. | |||
Search for further information about these or an SAP related objects