SAP IBAPI_C_COMPONENT_GETDETAIL Function Module for NOTRANSL: Liest die Detailinformationen zu einer Komponente
IBAPI_C_COMPONENT_GETDETAIL is a standard ibapi c component getdetail 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: Liest die Detailinformationen zu einer Komponente 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 ibapi c component getdetail FM, simply by entering the name IBAPI_C_COMPONENT_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBAPI_C
Program Name: SAPLIBAPI_C
Main Program: SAPLIBAPI_C
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IBAPI_C_COMPONENT_GETDETAIL 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 'IBAPI_C_COMPONENT_GETDETAIL'"NOTRANSL: Liest die Detailinformationen zu einer Komponente.
EXPORTING
* IV_INIT_LOG = CC_X "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
IV_AUFNR = "Order Number
IV_VORNR = "Operation Number
IV_RSNUM = "Number of Reservation / Dependent Requirement
IV_RSPOS = "Item Number of Reservation/Dependent Requirement
* IV_RSART = ' ' "Record Type
IMPORTING
ET_MESSAGES = "Error Messages
ES_RESBD = "Reservation/Dependent Requirements
EXCEPTIONS
LOG_ERROR = 1 COMPONENT_NOT_FOUND = 2
IMPORTING Parameters details for IBAPI_C_COMPONENT_GETDETAIL
IV_INIT_LOG - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEDefault: CC_X
Optional: Yes
Call by Reference: Yes
IV_AUFNR - Order Number
Data type: AUFNROptional: No
Call by Reference: Yes
IV_VORNR - Operation Number
Data type: VORNROptional: No
Call by Reference: Yes
IV_RSNUM - Number of Reservation / Dependent Requirement
Data type: RESBD-RSNUMOptional: No
Call by Reference: Yes
IV_RSPOS - Item Number of Reservation/Dependent Requirement
Data type: RESBD-RSPOSOptional: No
Call by Reference: Yes
IV_RSART - Record Type
Data type: RESBD-RSARTDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for IBAPI_C_COMPONENT_GETDETAIL
ET_MESSAGES - Error Messages
Data type: PS_MESSAGESOptional: No
Call by Reference: Yes
ES_RESBD - Reservation/Dependent Requirements
Data type: RESBDOptional: No
Call by Reference: Yes
EXCEPTIONS details
LOG_ERROR -
Data type:Optional: No
Call by Reference: Yes
COMPONENT_NOT_FOUND - Component not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IBAPI_C_COMPONENT_GETDETAIL 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_log_error | TYPE STRING, " | |||
| lv_et_messages | TYPE PS_MESSAGES, " | |||
| lv_iv_init_log | TYPE BOOLE-BOOLE, " CC_X | |||
| lv_es_resbd | TYPE RESBD, " | |||
| lv_iv_aufnr | TYPE AUFNR, " | |||
| lv_component_not_found | TYPE AUFNR, " | |||
| lv_iv_vornr | TYPE VORNR, " | |||
| lv_iv_rsnum | TYPE RESBD-RSNUM, " | |||
| lv_iv_rspos | TYPE RESBD-RSPOS, " | |||
| lv_iv_rsart | TYPE RESBD-RSART. " SPACE |
|   CALL FUNCTION 'IBAPI_C_COMPONENT_GETDETAIL' "NOTRANSL: Liest die Detailinformationen zu einer Komponente |
| EXPORTING | ||
| IV_INIT_LOG | = lv_iv_init_log | |
| IV_AUFNR | = lv_iv_aufnr | |
| IV_VORNR | = lv_iv_vornr | |
| IV_RSNUM | = lv_iv_rsnum | |
| IV_RSPOS | = lv_iv_rspos | |
| IV_RSART | = lv_iv_rsart | |
| IMPORTING | ||
| ET_MESSAGES | = lv_et_messages | |
| ES_RESBD | = lv_es_resbd | |
| EXCEPTIONS | ||
| LOG_ERROR = 1 | ||
| COMPONENT_NOT_FOUND = 2 | ||
| . " IBAPI_C_COMPONENT_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM IBAPI_C_COMPONENT_GETDETAIL
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 BOOLE FROM BOOLE INTO @DATA(ld_iv_init_log). | ||||
| DATA(ld_iv_init_log) | = CC_X. | |||
| "SELECT single RSNUM FROM RESBD INTO @DATA(ld_iv_rsnum). | ||||
| "SELECT single RSPOS FROM RESBD INTO @DATA(ld_iv_rspos). | ||||
| "SELECT single RSART FROM RESBD INTO @DATA(ld_iv_rsart). | ||||
| DATA(ld_iv_rsart) | = ' '. | |||
Search for further information about these or an SAP related objects