SAP FI_REQUEST_NEW_VERSION_STORE Function Module for
FI_REQUEST_NEW_VERSION_STORE is a standard fi request new version store SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fi request new version store FM, simply by entering the name FI_REQUEST_NEW_VERSION_STORE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FPIS
Program Name: SAPLFPIS
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FI_REQUEST_NEW_VERSION_STORE 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 'FI_REQUEST_NEW_VERSION_STORE'".
EXPORTING
PI_FI_MESSAGE_OBJECT_ID = "
* PI_SEND_TIME = "
* PI_FI_REQUEST_GUID = "
IMPORTING
PE_NEW_FI_REQUEST_OBJECT_ID = "
TABLES
* PT_NEW_FILE_CONTENT_ASCII = "
PT_NEW_FILE_ACCESS_INFO = "
EXCEPTIONS
REQUEST_NOT_CREATED = 1 REQUEST_ENQUEUE_FAILED = 2 REQUEST_CONTENT_NOT_STORED = 3 OLD_REQUEST_NOT_FOUND = 4
IMPORTING Parameters details for FI_REQUEST_NEW_VERSION_STORE
PI_FI_MESSAGE_OBJECT_ID -
Data type: SDOKOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
PI_SEND_TIME -
Data type: FIEB_SENDTIMEOptional: Yes
Call by Reference: No ( called with pass by value option)
PI_FI_REQUEST_GUID -
Data type: SDOKPHIO-PHIO_IDOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FI_REQUEST_NEW_VERSION_STORE
PE_NEW_FI_REQUEST_OBJECT_ID -
Data type: SDOKOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FI_REQUEST_NEW_VERSION_STORE
PT_NEW_FILE_CONTENT_ASCII -
Data type: SDOKCNTASCOptional: Yes
Call by Reference: No ( called with pass by value option)
PT_NEW_FILE_ACCESS_INFO -
Data type: SDOKFILACIOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
REQUEST_NOT_CREATED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REQUEST_ENQUEUE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
REQUEST_CONTENT_NOT_STORED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OLD_REQUEST_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FI_REQUEST_NEW_VERSION_STORE 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_request_not_created | TYPE STRING, " | |||
| lv_pi_fi_message_object_id | TYPE SDOKOBJECT, " | |||
| lt_pt_new_file_content_ascii | TYPE STANDARD TABLE OF SDOKCNTASC, " | |||
| lv_pe_new_fi_request_object_id | TYPE SDOKOBJECT, " | |||
| lv_pi_send_time | TYPE FIEB_SENDTIME, " | |||
| lv_request_enqueue_failed | TYPE FIEB_SENDTIME, " | |||
| lt_pt_new_file_access_info | TYPE STANDARD TABLE OF SDOKFILACI, " | |||
| lv_pi_fi_request_guid | TYPE SDOKPHIO-PHIO_ID, " | |||
| lv_request_content_not_stored | TYPE SDOKPHIO, " | |||
| lv_old_request_not_found | TYPE SDOKPHIO. " |
|   CALL FUNCTION 'FI_REQUEST_NEW_VERSION_STORE' " |
| EXPORTING | ||
| PI_FI_MESSAGE_OBJECT_ID | = lv_pi_fi_message_object_id | |
| PI_SEND_TIME | = lv_pi_send_time | |
| PI_FI_REQUEST_GUID | = lv_pi_fi_request_guid | |
| IMPORTING | ||
| PE_NEW_FI_REQUEST_OBJECT_ID | = lv_pe_new_fi_request_object_id | |
| TABLES | ||
| PT_NEW_FILE_CONTENT_ASCII | = lt_pt_new_file_content_ascii | |
| PT_NEW_FILE_ACCESS_INFO | = lt_pt_new_file_access_info | |
| EXCEPTIONS | ||
| REQUEST_NOT_CREATED = 1 | ||
| REQUEST_ENQUEUE_FAILED = 2 | ||
| REQUEST_CONTENT_NOT_STORED = 3 | ||
| OLD_REQUEST_NOT_FOUND = 4 | ||
| . " FI_REQUEST_NEW_VERSION_STORE | ||
ABAP code using 7.40 inline data declarations to call FM FI_REQUEST_NEW_VERSION_STORE
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 PHIO_ID FROM SDOKPHIO INTO @DATA(ld_pi_fi_request_guid). | ||||
Search for further information about these or an SAP related objects