SAP PT_COR_POST_REQUESTS Function Module for

Search SAP Function Modules

PT_COR_POST_REQUESTS is a standard pt cor post requests 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 pt cor post requests FM, simply by entering the name PT_COR_POST_REQUESTS into the relevant SAP transaction such as SE37 or SE38.

Function Group: PT_COR_POST
Program Name: SAPLPT_COR_POST
Main Program: SAPLPT_COR_POST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PT_COR_POST_REQUESTS 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 'PT_COR_POST_REQUESTS'"
  EXPORTING
   IM_TRANSF_FOR_ALL_PERNR =  "
*  IM_PERNR_TAB =  "Table of Personnel Numbers
*  IM_COMMIT_WORK =  "
*  IM_TESTRUN =  "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*  IM_COMMIT_AFTER_NUMBER =  "Number of Data Records for Database Commit
*  IM_PROTOCOL =  "

 IMPORTING
   EX_MESSAGE_TAB =  "Table with Message Table for Each Pers. No. and Posting RC
   EX_PROT_TAB =  "

EXCEPTIONS
   NO_PERNR_PROVIDED = 1    SELECTION_ERROR = 2 

.

IMPORTING Parameters details for PT_COR_POST_REQUESTS

IM_TRANSF_FOR_ALL_PERNR -

Data type: BOOLE_D
Optional: No
Call by Reference: Yes

IM_PERNR_TAB - Table of Personnel Numbers

Data type: PTCOR_PERNR_TAB
Optional: Yes
Call by Reference: Yes

IM_COMMIT_WORK -

Data type: BOOLE_D
Optional: Yes
Call by Reference: Yes

IM_TESTRUN - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Optional: Yes
Call by Reference: Yes

IM_COMMIT_AFTER_NUMBER - Number of Data Records for Database Commit

Data type: TIM_REQ_UPD
Optional: Yes
Call by Reference: Yes

IM_PROTOCOL -

Data type: BOOLE_D
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for PT_COR_POST_REQUESTS

EX_MESSAGE_TAB - Table with Message Table for Each Pers. No. and Posting RC

Data type: PTCOR_PERNR_MESSAGE_T
Optional: No
Call by Reference: Yes

EX_PROT_TAB -

Data type: CL_PT_COR_CONST=>RPTCORPOST_PROT_TAB
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_PERNR_PROVIDED -

Data type:
Optional: No
Call by Reference: Yes

SELECTION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for PT_COR_POST_REQUESTS 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.

ABAP code using 7.40 inline data declarations to call FM PT_COR_POST_REQUESTS

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.

Search for further information about these or an SAP related objects