SAP BAPI_PO_GETRELINFO Function Module for Display Detailed Release (Approval) Information on Purchase Order

Search SAP Function Modules

BAPI_PO_GETRELINFO is a standard bapi po getrelinfo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Detailed Release (Approval) Information on Purchase Order 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 bapi po getrelinfo FM, simply by entering the name BAPI_PO_GETRELINFO into the relevant SAP transaction such as SE37 or SE38.

Function Group: MEWP
Program Name: SAPLMEWP
Main Program: SAPLMEWP
Appliation area: M
Release date: 17-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_PO_GETRELINFO 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 'BAPI_PO_GETRELINFO'"Display Detailed Release (Approval) Information on Purchase Order
  EXPORTING
   PURCHASEORDER =  "Purchase Order Number
*  PO_REL_CODE =  "Release Code

 IMPORTING
   GENERAL_RELEASE_INFO =  "General Release Information
   RELEASE_PREREQUISITES =  "Release Prerequisites
   RELEASE_ALREADY_POSTED =  "Releases to Date

TABLES
*  RELEASE_FINAL =  "Final Release
*  RETURN =  "Return Messages

.

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_SAPLMEWP_001 Customer Exit for Object Determination (Procurement via Catalogs)
EXIT_SAPLMEWP_002 Customer Exit: Creation of Purchase Order via BAPI_PO_CREATE
EXIT_SAPLMEWP_003 Customer Exit to Determine Allowed Catalogs

IMPORTING Parameters details for BAPI_PO_GETRELINFO

PURCHASEORDER - Purchase Order Number

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

PO_REL_CODE - Release Code

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

EXPORTING Parameters details for BAPI_PO_GETRELINFO

GENERAL_RELEASE_INFO - General Release Information

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

RELEASE_PREREQUISITES - Release Prerequisites

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

RELEASE_ALREADY_POSTED - Releases to Date

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

TABLES Parameters details for BAPI_PO_GETRELINFO

RELEASE_FINAL - Final Release

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

RETURN - Return Messages

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

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

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