SAP PROXY_GET_STATUS Function Module for Proxy get status

Search SAP Function Modules

PROXY_GET_STATUS is a standard proxy get status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Proxy get status 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 proxy get status FM, simply by entering the name PROXY_GET_STATUS into the relevant SAP transaction such as SE37 or SE38.

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

Function PROXY_GET_STATUS 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 'PROXY_GET_STATUS'"Proxy get status
  EXPORTING
   EVENTCONTAINER =  "IC Event container
   LOGICAL_PORT =  "Logical Port Name

 IMPORTING
   OUTPUT_DATA =  "

EXCEPTIONS
   APPLICATION_ERROR = 1    COMMUNICATION_ERROR = 2 

.

IMPORTING Parameters details for PROXY_GET_STATUS

EVENTCONTAINER - IC Event container

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

LOGICAL_PORT - Logical Port Name

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

EXPORTING Parameters details for PROXY_GET_STATUS

OUTPUT_DATA -

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

EXCEPTIONS details

APPLICATION_ERROR - Application Error

Data type:
Optional: No
Call by Reference: Yes

COMMUNICATION_ERROR - Communication error

Data type:
Optional: No
Call by Reference: Yes

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

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