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

Function BAPI_0050_CREATE_REQUEST 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_0050_CREATE_REQUEST'"Create FM Budgeting Request.
EXPORTING
* LANGUAGE = "Language
HEADER_DATA = "Header data
HEADER_DATA_ADD = "Additional header data
IMPORTING
FMAREA = "Financial management area
CHANGING
* REQUESTNUMBER = "Temporary Document Number (for Incomplete Documents )
TABLES
ITEM_DATA = "Line item
* PERIOD_DATA = "Periods
RETURN = "Return messages
* EXTENSION_IN = "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
IMPORTING Parameters details for BAPI_0050_CREATE_REQUEST
LANGUAGE - Language
Data type: BAPI_0050_FIELDS-LANGUAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
HEADER_DATA - Header data
Data type: BAPI_0050_HEADEROptional: No
Call by Reference: No ( called with pass by value option)
HEADER_DATA_ADD - Additional header data
Data type: BAPI_0050_HEADER_ADDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_0050_CREATE_REQUEST
FMAREA - Financial management area
Data type: BAPI_0050_FIELDS-FM_AREAOptional: No
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for BAPI_0050_CREATE_REQUEST
REQUESTNUMBER - Temporary Document Number (for Incomplete Documents )
Data type: BAPI_0050_REQUEST-REQNROptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_0050_CREATE_REQUEST
ITEM_DATA - Line item
Data type: BAPI_0050_ITEMOptional: No
Call by Reference: Yes
PERIOD_DATA - Periods
Data type: BAPI_0050_PERIODOptional: Yes
Call by Reference: Yes
RETURN - Return messages
Data type: BAPIRET2Optional: No
Call by Reference: Yes
EXTENSION_IN - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_0050_CREATE_REQUEST 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_fmarea | TYPE BAPI_0050_FIELDS-FM_AREA, " | |||
| lv_language | TYPE BAPI_0050_FIELDS-LANGUAGE, " | |||
| lt_item_data | TYPE STANDARD TABLE OF BAPI_0050_ITEM, " | |||
| lv_requestnumber | TYPE BAPI_0050_REQUEST-REQNR, " | |||
| lv_header_data | TYPE BAPI_0050_HEADER, " | |||
| lt_period_data | TYPE STANDARD TABLE OF BAPI_0050_PERIOD, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_header_data_add | TYPE BAPI_0050_HEADER_ADD, " | |||
| lt_extension_in | TYPE STANDARD TABLE OF BAPIPAREX. " |
|   CALL FUNCTION 'BAPI_0050_CREATE_REQUEST' "Create FM Budgeting Request |
| EXPORTING | ||
| LANGUAGE | = lv_language | |
| HEADER_DATA | = lv_header_data | |
| HEADER_DATA_ADD | = lv_header_data_add | |
| IMPORTING | ||
| FMAREA | = lv_fmarea | |
| CHANGING | ||
| REQUESTNUMBER | = lv_requestnumber | |
| TABLES | ||
| ITEM_DATA | = lt_item_data | |
| PERIOD_DATA | = lt_period_data | |
| RETURN | = lt_return | |
| EXTENSION_IN | = lt_extension_in | |
| . " BAPI_0050_CREATE_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_0050_CREATE_REQUEST
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 FM_AREA FROM BAPI_0050_FIELDS INTO @DATA(ld_fmarea). | ||||
| "SELECT single LANGUAGE FROM BAPI_0050_FIELDS INTO @DATA(ld_language). | ||||
| "SELECT single REQNR FROM BAPI_0050_REQUEST INTO @DATA(ld_requestnumber). | ||||
Search for further information about these or an SAP related objects