SAP ID_GET_CGC_DATA Function Module for NOTRANSL: ID: CGC-Code Anteil des Buchungskreises
ID_GET_CGC_DATA is a standard id get cgc data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: ID: CGC-Code Anteil des Buchungskreises 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 id get cgc data FM, simply by entering the name ID_GET_CGC_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: ID_NF
Program Name: SAPLID_NF
Main Program: SAPLID_NF
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ID_GET_CGC_DATA 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 'ID_GET_CGC_DATA'"NOTRANSL: ID: CGC-Code Anteil des Buchungskreises.
EXPORTING
I_REQUNR = "Request Number: ID for a Data Request
* I_CHABASNM = "Name of Basic Characteristic
* I_MAXSIZE = "Maximum Number of Lines in Output Table
* I_INITFLAG = "Initialization 'X' or Data Transfer ' '
* I_UPDMODE = "Transfer Mode (See Domain Fixed Values)
* I_DATAPAKID = "Number of Incorrect Data Package
* I_S_TIMEINT = "Time Interval for Time-Dependent Master Data
TABLES
* I_T_SELECT = "Selection Criteria
* I_T_FIELDS = "Field List for SELECT
* E_T_IOBJ_CGC_COMPANY = "Output Table for Fixed Master Data
EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
IMPORTING Parameters details for ID_GET_CGC_DATA
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_CHABASNM - Name of Basic Characteristic
Data type: SBIWA_S_INTERFACE-CHABASNMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MAXSIZE - Maximum Number of Lines in Output Table
Data type: SBIWA_S_INTERFACE-MAXSIZEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_INITFLAG - Initialization 'X' or Data Transfer ' '
Data type: SBIWA_S_INTERFACE-INITFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_UPDMODE - Transfer Mode (See Domain Fixed Values)
Data type: SBIWA_S_INTERFACE-UPDMODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATAPAKID - Number of Incorrect Data Package
Data type: SBIWA_S_INTERFACE-DATAPAKIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_S_TIMEINT - Time Interval for Time-Dependent Master Data
Data type: SBIWA_S_TIMEINTOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ID_GET_CGC_DATA
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_IOBJ_CGC_COMPANY - Output Table for Fixed Master Data
Data type: IOBJ_CGC_COMPANYOptional: Yes
Call by Reference: No ( called with pass by value option)
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 ID_GET_CGC_DATA 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_chabasnm | TYPE SBIWA_S_INTERFACE-CHABASNM, " | |||
| 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_iobj_cgc_company | TYPE STANDARD TABLE OF IOBJ_CGC_COMPANY, " | |||
| lv_i_initflag | TYPE SBIWA_S_INTERFACE-INITFLAG, " | |||
| lv_i_updmode | TYPE SBIWA_S_INTERFACE-UPDMODE, " | |||
| lv_i_datapakid | TYPE SBIWA_S_INTERFACE-DATAPAKID, " | |||
| lv_i_s_timeint | TYPE SBIWA_S_TIMEINT. " |
|   CALL FUNCTION 'ID_GET_CGC_DATA' "NOTRANSL: ID: CGC-Code Anteil des Buchungskreises |
| EXPORTING | ||
| I_REQUNR | = lv_i_requnr | |
| I_CHABASNM | = lv_i_chabasnm | |
| I_MAXSIZE | = lv_i_maxsize | |
| I_INITFLAG | = lv_i_initflag | |
| I_UPDMODE | = lv_i_updmode | |
| I_DATAPAKID | = lv_i_datapakid | |
| I_S_TIMEINT | = lv_i_s_timeint | |
| TABLES | ||
| I_T_SELECT | = lt_i_t_select | |
| I_T_FIELDS | = lt_i_t_fields | |
| E_T_IOBJ_CGC_COMPANY | = lt_e_t_iobj_cgc_company | |
| EXCEPTIONS | ||
| NO_MORE_DATA = 1 | ||
| ERROR_PASSED_TO_MESS_HANDLER = 2 | ||
| . " ID_GET_CGC_DATA | ||
ABAP code using 7.40 inline data declarations to call FM ID_GET_CGC_DATA
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 CHABASNM FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_chabasnm). | ||||
| "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). | ||||
| "SELECT single DATAPAKID FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_datapakid). | ||||
Search for further information about these or an SAP related objects