SAP COM_PARTNER_CHECK_SET_OW Function Module for Prüfen aller Partner in einem Set sowie das Set selbst

Search SAP Function Modules

COM_PARTNER_CHECK_SET_OW is a standard com partner check set ow SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prüfen aller Partner in einem Set sowie das Set selbst 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 com partner check set ow FM, simply by entering the name COM_PARTNER_CHECK_SET_OW into the relevant SAP transaction such as SE37 or SE38.

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

Function COM_PARTNER_CHECK_SET_OW 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 'COM_PARTNER_CHECK_SET_OW'"Prüfen aller Partner in einem Set sowie das Set selbst
  EXPORTING
   IV_PARTNERSET_GUID =  "GUID for a Partner Set (Partner Quantity)
   IS_PARTNER_CONTROL =  "Control Data for Partner Processing
   IS_BP_ACCESS_STRUCTURE =  "
*  IV_INTERNAL_USAGE = ' ' "New input values
*  IV_NO_COUNT_CHECK = ' ' "Keine erneute Prüfung des Auftretens von Funktionen
*  IV_COUNT_WITH_HARD_ERROR = ' ' "New Input Values

 IMPORTING
   ET_PARTNER_COM =  "Transfer Table for Partners to Partner Processing
   ET_INPUT_FIELDS =  "Table of Partner-Specific Input Fields
   ET_ATTRIBUTES_COM =  "Transfer Table for Attributes to Partner Processing

EXCEPTIONS
   ERROR_OCCURRED = 1 

.

IMPORTING Parameters details for COM_PARTNER_CHECK_SET_OW

IV_PARTNERSET_GUID - GUID for a Partner Set (Partner Quantity)

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

IS_PARTNER_CONTROL - Control Data for Partner Processing

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

IS_BP_ACCESS_STRUCTURE -

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

IV_INTERNAL_USAGE - New input values

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

IV_NO_COUNT_CHECK - Keine erneute Prüfung des Auftretens von Funktionen

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

IV_COUNT_WITH_HARD_ERROR - New Input Values

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

EXPORTING Parameters details for COM_PARTNER_CHECK_SET_OW

ET_PARTNER_COM - Transfer Table for Partners to Partner Processing

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

ET_INPUT_FIELDS - Table of Partner-Specific Input Fields

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

ET_ATTRIBUTES_COM - Transfer Table for Attributes to Partner Processing

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

EXCEPTIONS details

ERROR_OCCURRED -

Data type:
Optional: No
Call by Reference: Yes

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

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