SAP PFO_CHECK_DATA Function Module for NOTRANSL: Datenkonsistentprüfung gegen DB

Search SAP Function Modules

PFO_CHECK_DATA is a standard pfo check data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Datenkonsistentprüfung gegen DB 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 pfo check data FM, simply by entering the name PFO_CHECK_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function PFO_CHECK_DATA 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 'PFO_CHECK_DATA'"NOTRANSL: Datenkonsistentprüfung gegen DB
  EXPORTING
   IS_OBJECTDATA =  "Structure of DB Table TPFO_OBJECT
   IR_STRUCTURE =  "Generic Type
   ID_NOW =  "Time Stamp (YYYY.MM.DD hh:mm:ss)
   IO_BUFFER =  "Memory for Mass Processing

CHANGING
   CO_BAL =  "CACS: Application Log

EXCEPTIONS
   ILLEGAL_ENTRY_DOMANE = 1    ILLEGAL_ENTRY_CHECKTABLE = 2    NOT_BOUND = 3    TABLE_NOT_FOUND = 4    ASSIGN_ERROR = 5    INCONSISTENT_ASSIGNMENT = 6 

.

IMPORTING Parameters details for PFO_CHECK_DATA

IS_OBJECTDATA - Structure of DB Table TPFO_OBJECT

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

IR_STRUCTURE - Generic Type

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

ID_NOW - Time Stamp (YYYY.MM.DD hh:mm:ss)

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

IO_BUFFER - Memory for Mass Processing

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

CHANGING Parameters details for PFO_CHECK_DATA

CO_BAL - CACS: Application Log

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

EXCEPTIONS details

ILLEGAL_ENTRY_DOMANE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_ENTRY_CHECKTABLE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

NOT_BOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

TABLE_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

ASSIGN_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

INCONSISTENT_ASSIGNMENT -

Data type:
Optional: No
Call by Reference: Yes

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

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