SAP SD_PCHECK_PARTNER_ORIGIN_OK Function Module for NOTRANSL: Prüfung, ob ein Partner über das Partnerschema herleitbar ist

Search SAP Function Modules

SD_PCHECK_PARTNER_ORIGIN_OK is a standard sd pcheck partner origin ok 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, ob ein Partner über das Partnerschema herleitbar ist 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 partner origin ok FM, simply by entering the name SD_PCHECK_PARTNER_ORIGIN_OK into the relevant SAP transaction such as SE37 or SE38.

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

Function SD_PCHECK_PARTNER_ORIGIN_OK 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_PARTNER_ORIGIN_OK'"NOTRANSL: Prüfung, ob ein Partner über das Partnerschema herleitbar ist
  EXPORTING
   FIC_OBJECTTYPE =  "
*  FIF_POSNR =  "
*  FIS_SDORGDATA =  "
   FIC_OBJECTKEY =  "
   FIF_CHECKTYPE =  "
   FIF_MSGTYPE =  "
*  FIF_PARGR = ' ' "
*  FIF_PARVW = ' ' "
*  FIF_NRART = ' ' "
*  FIF_PARNR = ' ' "
*  FIF_RTYPE = ' ' "

CHANGING
*  FRF_MESSAGE_COUNT =  "
*  FRF_MESSAGES =  "

EXCEPTIONS
   CHECK_ERROR = 1    PARAMETER_INCOMPLETE = 2    NO_AUTHORITY = 3 

.

IMPORTING Parameters details for SD_PCHECK_PARTNER_ORIGIN_OK

FIC_OBJECTTYPE -

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

FIF_POSNR -

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

FIS_SDORGDATA -

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

FIC_OBJECTKEY -

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

FIF_CHECKTYPE -

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

FIF_MSGTYPE -

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

FIF_PARGR -

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

FIF_PARVW -

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

FIF_NRART -

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

FIF_PARNR -

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

FIF_RTYPE -

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

CHANGING Parameters details for SD_PCHECK_PARTNER_ORIGIN_OK

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: No ( called with pass by value option)

PARAMETER_INCOMPLETE -

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

NO_AUTHORITY -

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

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

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