SAP BAPI_INVPROGRAM_GET_REQUESTS Function Module for Output Appropriation Requests and End Nodes of an Investment Program
BAPI_INVPROGRAM_GET_REQUESTS is a standard bapi invprogram get requests SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Output Appropriation Requests and End Nodes of an Investment Program 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 bapi invprogram get requests FM, simply by entering the name BAPI_INVPROGRAM_GET_REQUESTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: 1057
Program Name: SAPL1057
Main Program:
Appliation area: A
Release date: 27-Oct-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_INVPROGRAM_GET_REQUESTS 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 'BAPI_INVPROGRAM_GET_REQUESTS'"Output Appropriation Requests and End Nodes of an Investment Program.
EXPORTING
CAPINVPROGRAM = "Name of Investment Program
APPROVALYEAR = "Approval Year of the Investment Program
* FROM_POSITION = ' ' "Point of Entry Position of Investment Program
* LANGU = SY-LANGU "Logon Language in SAP Format
* LANGU_ISO = "Logon Language in ISO Format
IMPORTING
RETURN = "Information about Errors which Occurred
TABLES
* PROG_LEAVES = "Program End Nodes with Description
* REQUESTS = "Appropriation Requests for End Nodes
* AUTHORIZATION_ERRORS = "Error during Authorization Check
IMPORTING Parameters details for BAPI_INVPROGRAM_GET_REQUESTS
CAPINVPROGRAM - Name of Investment Program
Data type: BAPI1057ID-INV_PROGOptional: No
Call by Reference: No ( called with pass by value option)
APPROVALYEAR - Approval Year of the Investment Program
Data type: BAPI1057ID-APPR_YEAROptional: No
Call by Reference: No ( called with pass by value option)
FROM_POSITION - Point of Entry Position of Investment Program
Data type: BAPI1057ID-FROM_POSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGU - Logon Language in SAP Format
Data type: BAPI1057C0-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
LANGU_ISO - Logon Language in ISO Format
Data type: BAPI1057C0-LANGU_ISOOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_INVPROGRAM_GET_REQUESTS
RETURN - Information about Errors which Occurred
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_INVPROGRAM_GET_REQUESTS
PROG_LEAVES - Program End Nodes with Description
Data type: BAPI1057CPOptional: Yes
Call by Reference: No ( called with pass by value option)
REQUESTS - Appropriation Requests for End Nodes
Data type: BAPI1057CROptional: Yes
Call by Reference: No ( called with pass by value option)
AUTHORIZATION_ERRORS - Error during Authorization Check
Data type: BAPIRETURN1Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_INVPROGRAM_GET_REQUESTS 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_return | TYPE BAPIRETURN1, " | |||
| lt_prog_leaves | TYPE STANDARD TABLE OF BAPI1057CP, " | |||
| lv_capinvprogram | TYPE BAPI1057ID-INV_PROG, " | |||
| lt_requests | TYPE STANDARD TABLE OF BAPI1057CR, " | |||
| lv_approvalyear | TYPE BAPI1057ID-APPR_YEAR, " | |||
| lv_from_position | TYPE BAPI1057ID-FROM_POS, " SPACE | |||
| lt_authorization_errors | TYPE STANDARD TABLE OF BAPIRETURN1, " | |||
| lv_langu | TYPE BAPI1057C0-LANGU, " SY-LANGU | |||
| lv_langu_iso | TYPE BAPI1057C0-LANGU_ISO. " |
|   CALL FUNCTION 'BAPI_INVPROGRAM_GET_REQUESTS' "Output Appropriation Requests and End Nodes of an Investment Program |
| EXPORTING | ||
| CAPINVPROGRAM | = lv_capinvprogram | |
| APPROVALYEAR | = lv_approvalyear | |
| FROM_POSITION | = lv_from_position | |
| LANGU | = lv_langu | |
| LANGU_ISO | = lv_langu_iso | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| PROG_LEAVES | = lt_prog_leaves | |
| REQUESTS | = lt_requests | |
| AUTHORIZATION_ERRORS | = lt_authorization_errors | |
| . " BAPI_INVPROGRAM_GET_REQUESTS | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_INVPROGRAM_GET_REQUESTS
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 INV_PROG FROM BAPI1057ID INTO @DATA(ld_capinvprogram). | ||||
| "SELECT single APPR_YEAR FROM BAPI1057ID INTO @DATA(ld_approvalyear). | ||||
| "SELECT single FROM_POS FROM BAPI1057ID INTO @DATA(ld_from_position). | ||||
| DATA(ld_from_position) | = ' '. | |||
| "SELECT single LANGU FROM BAPI1057C0 INTO @DATA(ld_langu). | ||||
| DATA(ld_langu) | = SY-LANGU. | |||
| "SELECT single LANGU_ISO FROM BAPI1057C0 INTO @DATA(ld_langu_iso). | ||||
Search for further information about these or an SAP related objects