SAP VENDOR_PURCHASING_DEBLOCK Function Module for NOTRANSL: Aufheben Einkaufsperre Lieferantenstamm über Workflow

Search SAP Function Modules

VENDOR_PURCHASING_DEBLOCK is a standard vendor purchasing deblock 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: Aufheben Einkaufsperre Lieferantenstamm über Workflow 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 vendor purchasing deblock FM, simply by entering the name VENDOR_PURCHASING_DEBLOCK into the relevant SAP transaction such as SE37 or SE38.

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

Function VENDOR_PURCHASING_DEBLOCK 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 'VENDOR_PURCHASING_DEBLOCK'"NOTRANSL: Aufheben Einkaufsperre Lieferantenstamm über Workflow
  EXPORTING
   PI_LIFNR =  "Number of vendor
*  PI_EKORG = ' ' "Purchasing Organization
*  PI_LTSNR = ' ' "Vendor Subrange
*  PI_WERKS = ' ' "Plant

EXCEPTIONS
   VENDOR_LOCK_NOT_POSSIBLE = 1    VENDOR_NOT_FOUND = 2    NOT_BLOCKED = 3    UPDATE_ERROR = 4    NOT_AUTHORIZED = 5 

.

IMPORTING Parameters details for VENDOR_PURCHASING_DEBLOCK

PI_LIFNR - Number of vendor

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

PI_EKORG - Purchasing Organization

Data type: LFM1-EKORG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_LTSNR - Vendor Subrange

Data type: LFM2-LTSNR
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

PI_WERKS - Plant

Data type: LFM2-WERKS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

VENDOR_LOCK_NOT_POSSIBLE - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

VENDOR_NOT_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NOT_BLOCKED - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

UPDATE_ERROR - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

NOT_AUTHORIZED - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

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

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