SAP HRWPC_RQ_POST_REQ_OBJECT Function Module for Post Requisiiton Data- Follow-up Function
HRWPC_RQ_POST_REQ_OBJECT is a standard hrwpc rq post req object SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Post Requisiiton Data- Follow-up Function 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 hrwpc rq post req object FM, simply by entering the name HRWPC_RQ_POST_REQ_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRWPC_RQ_FORM_ACTIONS
Program Name: SAPLHRWPC_RQ_FORM_ACTIONS
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRWPC_RQ_POST_REQ_OBJECT 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 'HRWPC_RQ_POST_REQ_OBJECT'"Post Requisiiton Data- Follow-up Function.
EXPORTING
* I_VIQMEL = "
* I_CUSTOMIZING = "
* I_MANUM = "
* I_FBCALL = "
IMPORTING
E_QNQMASM0 = "
E_QNQMAQMEL0 = "
E_BUCH = "
E_QNQMAMA0 = "
TABLES
* TI_IVIQMFE = "
* TI_IVIQMUR = "
* TI_IVIQMSM = "
* TI_IVIQMMA = "
* TI_IHPA = "
* TE_CONTAINER = "
* TE_LINES = "
EXCEPTIONS
ACTION_STOPPED = 1
IMPORTING Parameters details for HRWPC_RQ_POST_REQ_OBJECT
I_VIQMEL -
Data type: VIQMELOptional: Yes
Call by Reference: Yes
I_CUSTOMIZING -
Data type: V_TQ85Optional: Yes
Call by Reference: Yes
I_MANUM -
Data type: QMSM-MANUMOptional: Yes
Call by Reference: Yes
I_FBCALL -
Data type:Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HRWPC_RQ_POST_REQ_OBJECT
E_QNQMASM0 -
Data type: QNQMASM0Optional: No
Call by Reference: No ( called with pass by value option)
E_QNQMAQMEL0 -
Data type: QNQMAQMEL0Optional: No
Call by Reference: No ( called with pass by value option)
E_BUCH -
Data type: QKZOptional: No
Call by Reference: No ( called with pass by value option)
E_QNQMAMA0 -
Data type: QNQMAMA0Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for HRWPC_RQ_POST_REQ_OBJECT
TI_IVIQMFE -
Data type: WQMFEOptional: Yes
Call by Reference: No ( called with pass by value option)
TI_IVIQMUR -
Data type: WQMUROptional: Yes
Call by Reference: No ( called with pass by value option)
TI_IVIQMSM -
Data type: WQMSMOptional: Yes
Call by Reference: No ( called with pass by value option)
TI_IVIQMMA -
Data type: WQMMAOptional: Yes
Call by Reference: No ( called with pass by value option)
TI_IHPA -
Data type: IHPAOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_CONTAINER -
Data type: SWCONTOptional: Yes
Call by Reference: No ( called with pass by value option)
TE_LINES -
Data type: TLINEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ACTION_STOPPED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for HRWPC_RQ_POST_REQ_OBJECT 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_viqmel | TYPE VIQMEL, " | |||
| lv_e_qnqmasm0 | TYPE QNQMASM0, " | |||
| lt_ti_iviqmfe | TYPE STANDARD TABLE OF WQMFE, " | |||
| lv_action_stopped | TYPE WQMFE, " | |||
| lt_ti_iviqmur | TYPE STANDARD TABLE OF WQMUR, " | |||
| lv_e_qnqmaqmel0 | TYPE QNQMAQMEL0, " | |||
| lv_i_customizing | TYPE V_TQ85, " | |||
| lv_e_buch | TYPE QKZ, " | |||
| lv_i_manum | TYPE QMSM-MANUM, " | |||
| lt_ti_iviqmsm | TYPE STANDARD TABLE OF WQMSM, " | |||
| lv_i_fbcall | TYPE WQMSM, " | |||
| lv_e_qnqmama0 | TYPE QNQMAMA0, " | |||
| lt_ti_iviqmma | TYPE STANDARD TABLE OF WQMMA, " | |||
| lt_ti_ihpa | TYPE STANDARD TABLE OF IHPA, " | |||
| lt_te_container | TYPE STANDARD TABLE OF SWCONT, " | |||
| lt_te_lines | TYPE STANDARD TABLE OF TLINE. " |
|   CALL FUNCTION 'HRWPC_RQ_POST_REQ_OBJECT' "Post Requisiiton Data- Follow-up Function |
| EXPORTING | ||
| I_VIQMEL | = lv_i_viqmel | |
| I_CUSTOMIZING | = lv_i_customizing | |
| I_MANUM | = lv_i_manum | |
| I_FBCALL | = lv_i_fbcall | |
| IMPORTING | ||
| E_QNQMASM0 | = lv_e_qnqmasm0 | |
| E_QNQMAQMEL0 | = lv_e_qnqmaqmel0 | |
| E_BUCH | = lv_e_buch | |
| E_QNQMAMA0 | = lv_e_qnqmama0 | |
| TABLES | ||
| TI_IVIQMFE | = lt_ti_iviqmfe | |
| TI_IVIQMUR | = lt_ti_iviqmur | |
| TI_IVIQMSM | = lt_ti_iviqmsm | |
| TI_IVIQMMA | = lt_ti_iviqmma | |
| TI_IHPA | = lt_ti_ihpa | |
| TE_CONTAINER | = lt_te_container | |
| TE_LINES | = lt_te_lines | |
| EXCEPTIONS | ||
| ACTION_STOPPED = 1 | ||
| . " HRWPC_RQ_POST_REQ_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM HRWPC_RQ_POST_REQ_OBJECT
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 MANUM FROM QMSM INTO @DATA(ld_i_manum). | ||||
Search for further information about these or an SAP related objects