SAP EA_GHO_EXTRACT_OWN_SSM Function Module for Template: Transfer Transaction Data
EA_GHO_EXTRACT_OWN_SSM is a standard ea gho extract own ssm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Template: Transfer Transaction Data 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 ea gho extract own ssm FM, simply by entering the name EA_GHO_EXTRACT_OWN_SSM into the relevant SAP transaction such as SE37 or SE38.
Function Group: EA_GHO_ANL_EXTRACTOR
Program Name: SAPLEA_GHO_ANL_EXTRACTOR
Main Program: SAPLEA_GHO_ANL_EXTRACTOR
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EA_GHO_EXTRACT_OWN_SSM 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 'EA_GHO_EXTRACT_OWN_SSM'"Template: Transfer Transaction Data.
EXPORTING
I_REQUNR = "Request Number: ID for a Data Request
* I_ISOURCE = "Maximum Number of Lines in Output Table
* I_MAXSIZE = "Initialization 'X' or Data Transfer ' '
* I_INITFLAG = "
* I_UPDMODE = "Indicator: Remote Call by BW
TABLES
* I_T_SELECT = "Selection Criteria
* I_T_FIELDS = "Field List for SELECT
* E_T_GHO_S_OWN_SSM = "Output Table for Fixed InfoSources
EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
IMPORTING Parameters details for EA_GHO_EXTRACT_OWN_SSM
I_REQUNR - Request Number: ID for a Data Request
Data type: SBIWA_S_INTERFACE-REQUNROptional: No
Call by Reference: No ( called with pass by value option)
I_ISOURCE - Maximum Number of Lines in Output Table
Data type: SBIWA_S_INTERFACE-ISOURCEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MAXSIZE - Initialization 'X' or Data Transfer ' '
Data type: SBIWA_S_INTERFACE-MAXSIZEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INITFLAG -
Data type: SBIWA_S_INTERFACE-INITFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_UPDMODE - Indicator: Remote Call by BW
Data type: SBIWA_S_INTERFACE-UPDMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EA_GHO_EXTRACT_OWN_SSM
I_T_SELECT - Selection Criteria
Data type: SBIWA_T_SELECTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_T_FIELDS - Field List for SELECT
Data type: SBIWA_T_FIELDSOptional: Yes
Call by Reference: No ( called with pass by value option)
E_T_GHO_S_OWN_SSM - Output Table for Fixed InfoSources
Data type: GHO_S_OWN_SSMOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_MORE_DATA - Data Was Completely Transferred
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_PASSED_TO_MESS_HANDLER - Exit due to error; message in Message Handler
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EA_GHO_EXTRACT_OWN_SSM 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_requnr | TYPE SBIWA_S_INTERFACE-REQUNR, " | |||
| lt_i_t_select | TYPE STANDARD TABLE OF SBIWA_T_SELECT, " | |||
| lv_no_more_data | TYPE SBIWA_T_SELECT, " | |||
| lv_i_isource | TYPE SBIWA_S_INTERFACE-ISOURCE, " | |||
| lt_i_t_fields | TYPE STANDARD TABLE OF SBIWA_T_FIELDS, " | |||
| lv_error_passed_to_mess_handler | TYPE SBIWA_T_FIELDS, " | |||
| lv_i_maxsize | TYPE SBIWA_S_INTERFACE-MAXSIZE, " | |||
| lt_e_t_gho_s_own_ssm | TYPE STANDARD TABLE OF GHO_S_OWN_SSM, " | |||
| lv_i_initflag | TYPE SBIWA_S_INTERFACE-INITFLAG, " | |||
| lv_i_updmode | TYPE SBIWA_S_INTERFACE-UPDMODE. " |
|   CALL FUNCTION 'EA_GHO_EXTRACT_OWN_SSM' "Template: Transfer Transaction Data |
| EXPORTING | ||
| I_REQUNR | = lv_i_requnr | |
| I_ISOURCE | = lv_i_isource | |
| I_MAXSIZE | = lv_i_maxsize | |
| I_INITFLAG | = lv_i_initflag | |
| I_UPDMODE | = lv_i_updmode | |
| TABLES | ||
| I_T_SELECT | = lt_i_t_select | |
| I_T_FIELDS | = lt_i_t_fields | |
| E_T_GHO_S_OWN_SSM | = lt_e_t_gho_s_own_ssm | |
| EXCEPTIONS | ||
| NO_MORE_DATA = 1 | ||
| ERROR_PASSED_TO_MESS_HANDLER = 2 | ||
| . " EA_GHO_EXTRACT_OWN_SSM | ||
ABAP code using 7.40 inline data declarations to call FM EA_GHO_EXTRACT_OWN_SSM
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 REQUNR FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_requnr). | ||||
| "SELECT single ISOURCE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_isource). | ||||
| "SELECT single MAXSIZE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_maxsize). | ||||
| "SELECT single INITFLAG FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_initflag). | ||||
| "SELECT single UPDMODE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_updmode). | ||||
Search for further information about these or an SAP related objects