SAP /AIN/PUB_POBJ_BUNDLE_GET Function Module for Physical Object Bundle Retrieval by a Bundle Peer

Search SAP Function Modules

/AIN/PUB_POBJ_BUNDLE_GET is a standard /ain/pub pobj bundle get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Physical Object Bundle Retrieval by a Bundle Peer 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 /ain/pub pobj bundle get FM, simply by entering the name /AIN/PUB_POBJ_BUNDLE_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: /AIN/PUB_POBJ
Program Name: /AIN/SAPLPUB_POBJ
Main Program: /AIN/SAPLPUB_POBJ
Appliation area:
Release date: 10-May-2006
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /AIN/PUB_POBJ_BUNDLE_GET 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 '/AIN/PUB_POBJ_BUNDLE_GET'"Physical Object Bundle Retrieval by a Bundle Peer
  EXPORTING
   IV_POBJ_INTID =  "Physical Object Internal ID

TABLES
   ET_POBJ_INTID =  "Physical Object Internal ID
*  ET_RETURN =  "Table with BAPI Return Information

EXCEPTIONS
   TECHNICAL_LEVEL_ERROR = 1    BUSINESS_LEVEL_ERROR_INPUT = 2    BUSINESS_LEVEL_ERROR_BUNDLE = 3 

.

IMPORTING Parameters details for /AIN/PUB_POBJ_BUNDLE_GET

IV_POBJ_INTID - Physical Object Internal ID

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

TABLES Parameters details for /AIN/PUB_POBJ_BUNDLE_GET

ET_POBJ_INTID - Physical Object Internal ID

Data type: /AIN/PUB_POBJ_INTID_TAB
Optional: No
Call by Reference: Yes

ET_RETURN - Table with BAPI Return Information

Data type: BAPIRETTAB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

TECHNICAL_LEVEL_ERROR - TECHNICAL LEVEL ERROR

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

BUSINESS_LEVEL_ERROR_INPUT - BUSINESS LEVEL ERROR - Insufficient or Incorrect Input

Data type:
Optional: No
Call by Reference: Yes

BUSINESS_LEVEL_ERROR_BUNDLE - BUSINESS LEVEL ERROR - Incorrect Bundle Input

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for /AIN/PUB_POBJ_BUNDLE_GET 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 /AIN/PUB_POBJ_BUNDLE_GET

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