SAP UA_BATCH_PDCE_CAL_STAT Function Module for

Search SAP Function Modules

UA_BATCH_PDCE_CAL_STAT is a standard ua batch pdce cal stat 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 ua batch pdce cal stat FM, simply by entering the name UA_BATCH_PDCE_CAL_STAT into the relevant SAP transaction such as SE37 or SE38.

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

Function UA_BATCH_PDCE_CAL_STAT 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 'UA_BATCH_PDCE_CAL_STAT'"
  EXPORTING
   IT_OBJECTLIST =  "
   ID_DATABASIS =  "

.

IMPORTING Parameters details for UA_BATCH_PDCE_CAL_STAT

IT_OBJECTLIST -

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

ID_DATABASIS -

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

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

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