SAP BAPI_CRMISUPROP_GETLIST Function Module for Determine List of Profiles (Header Data) at Point of Delivery
BAPI_CRMISUPROP_GETLIST is a standard bapi crmisuprop getlist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine List of Profiles (Header Data) at Point of Delivery 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 crmisuprop getlist FM, simply by entering the name BAPI_CRMISUPROP_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_ISU_PROFILES_BAPI
Program Name: SAPLCRM_ISU_PROFILES_BAPI
Main Program: SAPLCRM_ISU_PROFILES_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_CRMISUPROP_GETLIST 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_CRMISUPROP_GETLIST'"Determine List of Profiles (Header Data) at Point of Delivery.
EXPORTING
* POD_INT_UI = "
* FIND_PODINSTANCE = "
* POD_EXT_UI = "Point of Delivery ID
* POD_INSTANCE_GUID = "GUID for IBase Components of Point of Delivery
* DELETED = "
* ARCHIVED = "Archived Profiles
* INITIALIZE_BUFFER = 'X' "
IMPORTING
EV_POD_INSTANCE = "IB: Component (Instance)
TABLES
* RETURN = "Return Parameter
* EXTENSIONOUT = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* HEAD_DATA_ALL = "Profiles Table
IMPORTING Parameters details for BAPI_CRMISUPROP_GETLIST
POD_INT_UI -
Data type: BAPICRMISUPROFILEAUX-POD_INT_UIOptional: Yes
Call by Reference: No ( called with pass by value option)
FIND_PODINSTANCE -
Data type: BAPICRMISUPROFILEAUX-PODINSTANCEOptional: Yes
Call by Reference: No ( called with pass by value option)
POD_EXT_UI - Point of Delivery ID
Data type: BAPICRMISUPROFILEAUX-POD_EXT_UIOptional: Yes
Call by Reference: No ( called with pass by value option)
POD_INSTANCE_GUID - GUID for IBase Components of Point of Delivery
Data type: BAPICRMISUPROFILEAUX-POD_INSTANCE_GUIDOptional: Yes
Call by Reference: No ( called with pass by value option)
DELETED -
Data type: BAPICRMISUPROFILEAUX-DELETEDOptional: Yes
Call by Reference: No ( called with pass by value option)
ARCHIVED - Archived Profiles
Data type: BAPICRMISUPROFILEAUX-ARCHIVEDOptional: Yes
Call by Reference: No ( called with pass by value option)
INITIALIZE_BUFFER -
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_CRMISUPROP_GETLIST
EV_POD_INSTANCE - IB: Component (Instance)
Data type: BAPICRMISUPROFILEAUX-PODINSTANCEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_CRMISUPROP_GETLIST
RETURN - Return Parameter
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
EXTENSIONOUT - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
HEAD_DATA_ALL - Profiles Table
Data type: BAPICRMISUPROFILEPODHEADOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_CRMISUPROP_GETLIST 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.| DATA: | ||||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_pod_int_ui | TYPE BAPICRMISUPROFILEAUX-POD_INT_UI, " | |||
| lv_ev_pod_instance | TYPE BAPICRMISUPROFILEAUX-PODINSTANCE, " | |||
| lt_extensionout | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
| lv_find_podinstance | TYPE BAPICRMISUPROFILEAUX-PODINSTANCE, " | |||
| lv_pod_ext_ui | TYPE BAPICRMISUPROFILEAUX-POD_EXT_UI, " | |||
| lt_head_data_all | TYPE STANDARD TABLE OF BAPICRMISUPROFILEPODHEAD, " | |||
| lv_pod_instance_guid | TYPE BAPICRMISUPROFILEAUX-POD_INSTANCE_GUID, " | |||
| lv_deleted | TYPE BAPICRMISUPROFILEAUX-DELETED, " | |||
| lv_archived | TYPE BAPICRMISUPROFILEAUX-ARCHIVED, " | |||
| lv_initialize_buffer | TYPE BOOLEAN. " 'X' |
|   CALL FUNCTION 'BAPI_CRMISUPROP_GETLIST' "Determine List of Profiles (Header Data) at Point of Delivery |
| EXPORTING | ||
| POD_INT_UI | = lv_pod_int_ui | |
| FIND_PODINSTANCE | = lv_find_podinstance | |
| POD_EXT_UI | = lv_pod_ext_ui | |
| POD_INSTANCE_GUID | = lv_pod_instance_guid | |
| DELETED | = lv_deleted | |
| ARCHIVED | = lv_archived | |
| INITIALIZE_BUFFER | = lv_initialize_buffer | |
| IMPORTING | ||
| EV_POD_INSTANCE | = lv_ev_pod_instance | |
| TABLES | ||
| RETURN | = lt_return | |
| EXTENSIONOUT | = lt_extensionout | |
| HEAD_DATA_ALL | = lt_head_data_all | |
| . " BAPI_CRMISUPROP_GETLIST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_CRMISUPROP_GETLIST
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.| "SELECT single POD_INT_UI FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_pod_int_ui). | ||||
| "SELECT single PODINSTANCE FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_ev_pod_instance). | ||||
| "SELECT single PODINSTANCE FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_find_podinstance). | ||||
| "SELECT single POD_EXT_UI FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_pod_ext_ui). | ||||
| "SELECT single POD_INSTANCE_GUID FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_pod_instance_guid). | ||||
| "SELECT single DELETED FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_deleted). | ||||
| "SELECT single ARCHIVED FROM BAPICRMISUPROFILEAUX INTO @DATA(ld_archived). | ||||
| DATA(ld_initialize_buffer) | = 'X'. | |||
Search for further information about these or an SAP related objects