SAP VHUPODB_PACKOBJ_READ_EXT Function Module for NOTRANSL: Packobjekt lesen mit externer Identifikation

Search SAP Function Modules

VHUPODB_PACKOBJ_READ_EXT is a standard vhupodb packobj read ext 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: Packobjekt lesen mit externer Identifikation 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 vhupodb packobj read ext FM, simply by entering the name VHUPODB_PACKOBJ_READ_EXT into the relevant SAP transaction such as SE37 or SE38.

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

Function VHUPODB_PACKOBJ_READ_EXT 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 'VHUPODB_PACKOBJ_READ_EXT'"NOTRANSL: Packobjekt lesen mit externer Identifikation
  EXPORTING
   POBJID_I =  "
   PACKTYP_I =  "
   PRE_LOCK_MODE_I =  "
   POST_LOCK_MODE_I =  "
   ALL_LANGU_I =  "
*  GET_ITEMS = ' ' "
*  GET_TEXT = ' ' "

 IMPORTING
   PACKKP_E =  "
   DB_STATUS_E =  "Database status of packing object

TABLES
*  TPACKPO =  "
*  TPACKKPS =  "

EXCEPTIONS
   POBJ_IN_UPDATE_RUN = 1    FOREIGN_LOCK = 2    ERROR = 3 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLVHUPODB_001

IMPORTING Parameters details for VHUPODB_PACKOBJ_READ_EXT

POBJID_I -

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

PACKTYP_I -

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

PRE_LOCK_MODE_I -

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

POST_LOCK_MODE_I -

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

ALL_LANGU_I -

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

GET_ITEMS -

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

GET_TEXT -

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

EXPORTING Parameters details for VHUPODB_PACKOBJ_READ_EXT

PACKKP_E -

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

DB_STATUS_E - Database status of packing object

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

TABLES Parameters details for VHUPODB_PACKOBJ_READ_EXT

TPACKPO -

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

TPACKKPS -

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

EXCEPTIONS details

POBJ_IN_UPDATE_RUN -

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

FOREIGN_LOCK -

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

ERROR -

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

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

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