SAP PJP_FWS_GET_NEXT_PROCESSOR Function Module for Get Next Processor
PJP_FWS_GET_NEXT_PROCESSOR is a standard pjp fws get next processor SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Next Processor 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 pjp fws get next processor FM, simply by entering the name PJP_FWS_GET_NEXT_PROCESSOR into the relevant SAP transaction such as SE37 or SE38.
Function Group: PJP_FWS_FG
Program Name: SAPLPJP_FWS_FG
Main Program: SAPLPJP_FWS_FG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function PJP_FWS_GET_NEXT_PROCESSOR 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 'PJP_FWS_GET_NEXT_PROCESSOR'"Get Next Processor.
EXPORTING
* IM_USER = "User Name
* IM_PERNR = "Personnel Number
* IM_COMMAND = "ESS Command
IM_DATE = "Start Date
IMPORTING
EX_PERSDATA = "Actor Data
EX_MESSAGES = "Message Table
IMPORTING Parameters details for PJP_FWS_GET_NEXT_PROCESSOR
IM_USER - User Name
Data type: SY-UNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_PERNR - Personnel Number
Data type: P_PERNROptional: Yes
Call by Reference: No ( called with pass by value option)
IM_COMMAND - ESS Command
Data type: PTREQ_COMMANDOptional: Yes
Call by Reference: No ( called with pass by value option)
IM_DATE - Start Date
Data type: BEGDAOptional: No
Call by Reference: Yes
EXPORTING Parameters details for PJP_FWS_GET_NEXT_PROCESSOR
EX_PERSDATA - Actor Data
Data type: PTREQ_ACTOR_STRUC_FLATOptional: No
Call by Reference: Yes
EX_MESSAGES - Message Table
Data type: PTREQ_MESSAGE_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for PJP_FWS_GET_NEXT_PROCESSOR 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_im_user | TYPE SY-UNAME, " | |||
lv_ex_persdata | TYPE PTREQ_ACTOR_STRUC_FLAT, " | |||
lv_im_pernr | TYPE P_PERNR, " | |||
lv_ex_messages | TYPE PTREQ_MESSAGE_TAB, " | |||
lv_im_command | TYPE PTREQ_COMMAND, " | |||
lv_im_date | TYPE BEGDA. " |
  CALL FUNCTION 'PJP_FWS_GET_NEXT_PROCESSOR' "Get Next Processor |
EXPORTING | ||
IM_USER | = lv_im_user | |
IM_PERNR | = lv_im_pernr | |
IM_COMMAND | = lv_im_command | |
IM_DATE | = lv_im_date | |
IMPORTING | ||
EX_PERSDATA | = lv_ex_persdata | |
EX_MESSAGES | = lv_ex_messages | |
. " PJP_FWS_GET_NEXT_PROCESSOR |
ABAP code using 7.40 inline data declarations to call FM PJP_FWS_GET_NEXT_PROCESSOR
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 UNAME FROM SY INTO @DATA(ld_im_user). | ||||
Search for further information about these or an SAP related objects