SAP SD_PCHECK_DPP_BLOCK Function Module for NOTRANSL: Prüfung auf Sperre: Personenbezogene Daten

Search SAP Function Modules

SD_PCHECK_DPP_BLOCK is a standard sd pcheck dpp block 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: Prüfung auf Sperre: Personenbezogene Daten 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 sd pcheck dpp block FM, simply by entering the name SD_PCHECK_DPP_BLOCK into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_PCHECK_DPP_BLOCK 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 'SD_PCHECK_DPP_BLOCK'"NOTRANSL: Prüfung auf Sperre: Personenbezogene Daten
  EXPORTING
   FIC_OBJECTTYPE =  "Object Type
   FIF_POSNR =  "Item Number of the SD Document
   FIS_SDORGDATA =  "Organizational Data for SD Documents
*  FIF_BEFORE = ' ' "New Input Values
   FIC_OBJECTKEY =  "Object Key
   FIF_CHECKTYPE =  "Checking type for check routines in SD partner processing
   FIF_MSGTYPE =  "Messages, Message Type
*  FIF_PARGR = ' ' "Partner Determination Procedure
*  FIF_PARVW = ' ' "Partner Role
*  FIF_NRART = ' ' "Type of Partner Number
*  FIF_PARNR = ' ' "Partner Number
*  FIF_RTYPE = ' ' "Function types in SD partner processing

CHANGING
*  FRF_MESSAGE_COUNT =  "
*  FRF_MESSAGES =  "

EXCEPTIONS
   CHECK_ERROR = 1    PARAMETER_INCOMPLETE = 2    NO_AUTHORITY = 3 

.

IMPORTING Parameters details for SD_PCHECK_DPP_BLOCK

FIC_OBJECTTYPE - Object Type

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

FIF_POSNR - Item Number of the SD Document

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

FIS_SDORGDATA - Organizational Data for SD Documents

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

FIF_BEFORE - New Input Values

Data type: XFLAG
Default: SPACE
Optional: No
Call by Reference: Yes

FIC_OBJECTKEY - Object Key

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

FIF_CHECKTYPE - Checking type for check routines in SD partner processing

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

FIF_MSGTYPE - Messages, Message Type

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

FIF_PARGR - Partner Determination Procedure

Data type: PARGR
Default: SPACE
Optional: No
Call by Reference: Yes

FIF_PARVW - Partner Role

Data type: PARVW_4
Default: SPACE
Optional: No
Call by Reference: Yes

FIF_NRART - Type of Partner Number

Data type: NRART
Default: SPACE
Optional: No
Call by Reference: Yes

FIF_PARNR - Partner Number

Data type: SD_PARTNER_PARNR
Default: SPACE
Optional: No
Call by Reference: Yes

FIF_RTYPE - Function types in SD partner processing

Data type: SD_PARTNER_ROLETYPE
Default: SPACE
Optional: No
Call by Reference: Yes

CHANGING Parameters details for SD_PCHECK_DPP_BLOCK

FRF_MESSAGE_COUNT -

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

FRF_MESSAGES -

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

EXCEPTIONS details

CHECK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_INCOMPLETE -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

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

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