SAP PB_PACKAGE_EDIT Function Module for

Search SAP Function Modules

PB_PACKAGE_EDIT is a standard pb package edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 pb package edit FM, simply by entering the name PB_PACKAGE_EDIT into the relevant SAP transaction such as SE37 or SE38.

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

Function PB_PACKAGE_EDIT 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 'PB_PACKAGE_EDIT'"
  EXPORTING
   P_OBJECTNAME =  "WB Request: Development Environment Object Type
   P_OPERATION =  "WB Request: Operation within the ABAP Workbench
   P_PB_INST =  "
   P_PACKAGE_STATE =  "

CHANGING
*  P_TRANSPORT_REQUEST =  "Request/Task

EXCEPTIONS
   OPERATION_NOT_SUPPORTED = 1    ACTION_CANCELLED = 2    ERROR_OCCURED = 3    OBJECT_NOT_FOUND = 4 

.

IMPORTING Parameters details for PB_PACKAGE_EDIT

P_OBJECTNAME - WB Request: Development Environment Object Type

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

P_OPERATION - WB Request: Operation within the ABAP Workbench

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

P_PB_INST -

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

P_PACKAGE_STATE -

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

CHANGING Parameters details for PB_PACKAGE_EDIT

P_TRANSPORT_REQUEST - Request/Task

Data type: E070-TRKORR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

OPERATION_NOT_SUPPORTED -

Data type:
Optional: No
Call by Reference: Yes

ACTION_CANCELLED - Canceled by User

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

ERROR_OCCURED - Error message

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

OBJECT_NOT_FOUND - Object does not exist

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

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

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