SAP PARTNER_GET_BLOCK_FLAGS Function Module for Function for SCM-ERP blocking flag synchronization

Search SAP Function Modules

PARTNER_GET_BLOCK_FLAGS is a standard partner get block flags SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Function for SCM-ERP blocking flag synchronization 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 partner get block flags FM, simply by entering the name PARTNER_GET_BLOCK_FLAGS into the relevant SAP transaction such as SE37 or SE38.

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

Function PARTNER_GET_BLOCK_FLAGS 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 'PARTNER_GET_BLOCK_FLAGS'"Function for SCM-ERP blocking flag synchronization
  EXPORTING
   IT_CVPNOS =  "Customer/Vendor Number (Range)
   IV_CVPTYPE =  "CVP Type (Customer/Vendor)

 IMPORTING
   ET_CVPS =  "Table of Customer/Vendor Blocking Flags

EXCEPTIONS
   BUSINESS_FUNCTION_DISABLED = 1    EMPTY_CVP_TABLE = 2    NOT_AUTHORIZED = 3    BAD_CVP_TYPE = 4 

.

IMPORTING Parameters details for PARTNER_GET_BLOCK_FLAGS

IT_CVPNOS - Customer/Vendor Number (Range)

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

IV_CVPTYPE - CVP Type (Customer/Vendor)

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

EXPORTING Parameters details for PARTNER_GET_BLOCK_FLAGS

ET_CVPS - Table of Customer/Vendor Blocking Flags

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

EXCEPTIONS details

BUSINESS_FUNCTION_DISABLED - CVP blocking related BP is not enabled on system.

Data type:
Optional: No
Call by Reference: Yes

EMPTY_CVP_TABLE - An empty CVP table was passed to FM.

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED - The caller is not authorized to read blocking flags.

Data type:
Optional: No
Call by Reference: Yes

BAD_CVP_TYPE - The CVP type is not one of the 3 handled in this FM.

Data type:
Optional: No
Call by Reference: Yes

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

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