SAP PLANT_DATA_ANALYZE Function Module for Analysis and Processing of Confirmations for the Applications HR/PP/PM









PLANT_DATA_ANALYZE is a standard plant data analyze SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Analysis and Processing of Confirmations for the Applications HR/PP/PM 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 plant data analyze FM, simply by entering the name PLANT_DATA_ANALYZE into the relevant SAP transaction such as SE37 or SE38.

Function Group: COPD
Program Name: SAPLCOPD
Main Program: SAPLCOPD
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function PLANT_DATA_ANALYZE 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 'PLANT_DATA_ANALYZE'"Analysis and Processing of Confirmations for the Applications HR/PP/PM
EXPORTING
* DIALOG_FLAG = ' ' "Indicator That the Invocation Takes Place from a Dialog Transaction
APPLICATION_FLAG = "
* EXTERN_FLAG = ' ' "Indicator That the Calling Program Executes the COMMIT
* CPROT_FLAG = ' ' "Indicator 'Display Cost Log'
* GPROT_FLAG = ' ' "Indicator 'Display Error Log for Goods Movements'
* NO_BACK_FLUSH_FLAG = ' ' "Indicator 'No Backflushing'
* NO_GOODS_RECEIPT_FLAG = ' ' "
* ORDER_FLAG = ' ' "Indicator That Confirmation Carried Out from Within Order Maintenance Transact.
* SUPPRESS_DIALOG_FLAG = 'X' "Indicator 'Suppress Dialog Messages'
* TRANS_TYP = ' ' "Transaction type

IMPORTING
N_ITEMS_OK_BACK_FLUSH = "
N_ITEMS_TOTAL_BACK_FLUSH = "
N_ITEMS_FAILED_COSTS = "

TABLES
* IPDCOM = "Table Structure for Confirmation Data
* IPDERR_TAB = "Error message table

EXCEPTIONS
TABLE_EMPTY = 1 WRONG_APPLICATION_FLAG = 2
.



IMPORTING Parameters details for PLANT_DATA_ANALYZE

DIALOG_FLAG - Indicator That the Invocation Takes Place from a Dialog Transaction

Data type: PDCOM-LEK01
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

APPLICATION_FLAG -

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

EXTERN_FLAG - Indicator That the Calling Program Executes the COMMIT

Data type: RC27X-FLG_SEL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

CPROT_FLAG - Indicator 'Display Cost Log'

Data type: TCORU-CPROT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

GPROT_FLAG - Indicator 'Display Error Log for Goods Movements'

Data type: TCORU-CPROT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_BACK_FLUSH_FLAG - Indicator 'No Backflushing'

Data type: RC27X-FLG_SEL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_GOODS_RECEIPT_FLAG -

Data type: RC27X-FLG_SEL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

ORDER_FLAG - Indicator That Confirmation Carried Out from Within Order Maintenance Transact.

Data type: RC27X-FLG_SEL
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SUPPRESS_DIALOG_FLAG - Indicator 'Suppress Dialog Messages'

Data type: RC27X-FLG_SEL
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TRANS_TYP - Transaction type

Data type: TC10-TRTYP
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for PLANT_DATA_ANALYZE

N_ITEMS_OK_BACK_FLUSH -

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

N_ITEMS_TOTAL_BACK_FLUSH -

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

N_ITEMS_FAILED_COSTS -

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

TABLES Parameters details for PLANT_DATA_ANALYZE

IPDCOM - Table Structure for Confirmation Data

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

IPDERR_TAB - Error message table

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

EXCEPTIONS details

TABLE_EMPTY - Int. Tab. IPDCOM is empty --> no processing

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

WRONG_APPLICATION_FLAG -

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

Copy and paste ABAP code example for PLANT_DATA_ANALYZE 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:
lt_ipdcom  TYPE STANDARD TABLE OF PDCOM, "   
lv_dialog_flag  TYPE PDCOM-LEK01, "   SPACE
lv_table_empty  TYPE PDCOM, "   
lv_n_items_ok_back_flush  TYPE SY-TABIX, "   
lv_application_flag  TYPE PDCOM-ORIND, "   
lt_ipderr_tab  TYPE STANDARD TABLE OF PDERR, "   
lv_extern_flag  TYPE RC27X-FLG_SEL, "   SPACE
lv_wrong_application_flag  TYPE RC27X, "   
lv_n_items_total_back_flush  TYPE SY-TABIX, "   
lv_cprot_flag  TYPE TCORU-CPROT, "   SPACE
lv_n_items_failed_costs  TYPE SY-TABIX, "   
lv_gprot_flag  TYPE TCORU-CPROT, "   SPACE
lv_no_back_flush_flag  TYPE RC27X-FLG_SEL, "   SPACE
lv_no_goods_receipt_flag  TYPE RC27X-FLG_SEL, "   SPACE
lv_order_flag  TYPE RC27X-FLG_SEL, "   SPACE
lv_suppress_dialog_flag  TYPE RC27X-FLG_SEL, "   'X'
lv_trans_typ  TYPE TC10-TRTYP. "   SPACE

  CALL FUNCTION 'PLANT_DATA_ANALYZE'  "Analysis and Processing of Confirmations for the Applications HR/PP/PM
    EXPORTING
         DIALOG_FLAG = lv_dialog_flag
         APPLICATION_FLAG = lv_application_flag
         EXTERN_FLAG = lv_extern_flag
         CPROT_FLAG = lv_cprot_flag
         GPROT_FLAG = lv_gprot_flag
         NO_BACK_FLUSH_FLAG = lv_no_back_flush_flag
         NO_GOODS_RECEIPT_FLAG = lv_no_goods_receipt_flag
         ORDER_FLAG = lv_order_flag
         SUPPRESS_DIALOG_FLAG = lv_suppress_dialog_flag
         TRANS_TYP = lv_trans_typ
    IMPORTING
         N_ITEMS_OK_BACK_FLUSH = lv_n_items_ok_back_flush
         N_ITEMS_TOTAL_BACK_FLUSH = lv_n_items_total_back_flush
         N_ITEMS_FAILED_COSTS = lv_n_items_failed_costs
    TABLES
         IPDCOM = lt_ipdcom
         IPDERR_TAB = lt_ipderr_tab
    EXCEPTIONS
        TABLE_EMPTY = 1
        WRONG_APPLICATION_FLAG = 2
. " PLANT_DATA_ANALYZE




ABAP code using 7.40 inline data declarations to call FM PLANT_DATA_ANALYZE

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 LEK01 FROM PDCOM INTO @DATA(ld_dialog_flag).
DATA(ld_dialog_flag) = ' '.
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_n_items_ok_back_flush).
 
"SELECT single ORIND FROM PDCOM INTO @DATA(ld_application_flag).
 
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_extern_flag).
DATA(ld_extern_flag) = ' '.
 
 
"SELECT single TABIX FROM SY INTO @DATA(ld_n_items_total_back_flush).
 
"SELECT single CPROT FROM TCORU INTO @DATA(ld_cprot_flag).
DATA(ld_cprot_flag) = ' '.
 
"SELECT single TABIX FROM SY INTO @DATA(ld_n_items_failed_costs).
 
"SELECT single CPROT FROM TCORU INTO @DATA(ld_gprot_flag).
DATA(ld_gprot_flag) = ' '.
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_no_back_flush_flag).
DATA(ld_no_back_flush_flag) = ' '.
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_no_goods_receipt_flag).
DATA(ld_no_goods_receipt_flag) = ' '.
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_order_flag).
DATA(ld_order_flag) = ' '.
 
"SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_suppress_dialog_flag).
DATA(ld_suppress_dialog_flag) = 'X'.
 
"SELECT single TRTYP FROM TC10 INTO @DATA(ld_trans_typ).
DATA(ld_trans_typ) = ' '.
 


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!