SAP RP_BUILD_PSP Function Module for









RP_BUILD_PSP is a standard rp build psp 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 rp build psp FM, simply by entering the name RP_BUILD_PSP into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRTIM00WORK-SCHED-CONVERT
Program Name: SAPLHRTIM00WORK-SCHED-CONVERT
Main Program: SAPLHRTIM00WORK-SCHED-CONVERT
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RP_BUILD_PSP 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 'RP_BUILD_PSP'"
  EXPORTING
*  ACTIV = 0 "Indicator for processing status fields
   BEGDA =  "
   ENDDA =  "
   ERROR =  "
   INPUT =  "

 IMPORTING
   OUTPUT =  "

TABLES
   I550AN =  "
   PP2001 =  "
   PP2002 =  "
   PP2003 =  "
   I550AO =  "
   I550PN =  "
   I550PO =  "
   PPSP =  "
   PP0000 =  "
   PP0001 =  "
   PP0002 =  "
   PP0007 =  "
.



IMPORTING Parameters details for RP_BUILD_PSP

ACTIV - Indicator for processing status fields

Data type:
Optional: Yes
Call by Reference: No ( called with pass by value option)

BEGDA -

Data type: PTPRG-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

ENDDA -

Data type: PTPRG-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INPUT -

Data type: PTPRG
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RP_BUILD_PSP

OUTPUT -

Data type: PTPRG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for RP_BUILD_PSP

I550AN -

Data type: T550A
Optional: No
Call by Reference: No ( called with pass by value option)

PP2001 -

Data type: P2001
Optional: No
Call by Reference: No ( called with pass by value option)

PP2002 -

Data type: P2002
Optional: No
Call by Reference: No ( called with pass by value option)

PP2003 -

Data type: P2003
Optional: No
Call by Reference: No ( called with pass by value option)

I550AO -

Data type: T550A
Optional: No
Call by Reference: No ( called with pass by value option)

I550PN -

Data type: T550P
Optional: No
Call by Reference: No ( called with pass by value option)

I550PO -

Data type: T550P
Optional: No
Call by Reference: No ( called with pass by value option)

PPSP -

Data type: PTPSP
Optional: No
Call by Reference: No ( called with pass by value option)

PP0000 -

Data type: P0000
Optional: No
Call by Reference: No ( called with pass by value option)

PP0001 -

Data type: P0001
Optional: No
Call by Reference: No ( called with pass by value option)

PP0002 -

Data type: P0002
Optional: No
Call by Reference: No ( called with pass by value option)

PP0007 -

Data type: P0007
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for RP_BUILD_PSP 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_activ  TYPE STRING, "   0
lt_i550an  TYPE STANDARD TABLE OF T550A, "   
lv_output  TYPE PTPRG, "   
lt_pp2001  TYPE STANDARD TABLE OF P2001, "   
lt_pp2002  TYPE STANDARD TABLE OF P2002, "   
lt_pp2003  TYPE STANDARD TABLE OF P2003, "   
lv_begda  TYPE PTPRG-DATUM, "   
lt_i550ao  TYPE STANDARD TABLE OF T550A, "   
lv_endda  TYPE PTPRG-DATUM, "   
lt_i550pn  TYPE STANDARD TABLE OF T550P, "   
lv_error  TYPE T550P, "   
lt_i550po  TYPE STANDARD TABLE OF T550P, "   
lt_ppsp  TYPE STANDARD TABLE OF PTPSP, "   
lv_input  TYPE PTPRG, "   
lt_pp0000  TYPE STANDARD TABLE OF P0000, "   
lt_pp0001  TYPE STANDARD TABLE OF P0001, "   
lt_pp0002  TYPE STANDARD TABLE OF P0002, "   
lt_pp0007  TYPE STANDARD TABLE OF P0007. "   

  CALL FUNCTION 'RP_BUILD_PSP'  "
    EXPORTING
         ACTIV = lv_activ
         BEGDA = lv_begda
         ENDDA = lv_endda
         ERROR = lv_error
         INPUT = lv_input
    IMPORTING
         OUTPUT = lv_output
    TABLES
         I550AN = lt_i550an
         PP2001 = lt_pp2001
         PP2002 = lt_pp2002
         PP2003 = lt_pp2003
         I550AO = lt_i550ao
         I550PN = lt_i550pn
         I550PO = lt_i550po
         PPSP = lt_ppsp
         PP0000 = lt_pp0000
         PP0001 = lt_pp0001
         PP0002 = lt_pp0002
         PP0007 = lt_pp0007
. " RP_BUILD_PSP




ABAP code using 7.40 inline data declarations to call FM RP_BUILD_PSP

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 DATUM FROM PTPRG INTO @DATA(ld_begda).
 
 
"SELECT single DATUM FROM PTPRG INTO @DATA(ld_endda).
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!