SAP CRM_TOOLS_SYSTEM_GET Function Module for Ermittlung der Externen Systeme









CRM_TOOLS_SYSTEM_GET is a standard crm tools system 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 Ermittlung der Externen Systeme 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 crm tools system get FM, simply by entering the name CRM_TOOLS_SYSTEM_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_TOOLS_SYSTEM_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 'CRM_TOOLS_SYSTEM_GET'"Ermittlung der Externen Systeme
  EXPORTING
*  IV_HEADER_GUID =  "GUID eines CRM-Order-Objekts, not used
*  IV_ITEM_GUID =  "GUID der Position, not used
*  IS_PARTNER_EXT =  "Übergabestruktur für die Partner, not used
*  IS_ORGMAN =  "Orgdaten Set: Struktur der Workarea und der Puffer, not used
*  IS_CREDIT_DATA =  "Daten für externe Kreditprüfungen (1. Eintrag), not used

 IMPORTING
   EV_BILLING_LOGSYS =  "Logical System
   EV_CUST_FACT_SHEET_OLTP_DEST =  "Standard RFC Destination for Synchronous BAPI Calls
   EV_MAX_NUMBER_CHECKS =  "max. Anzahl ATP Pruefungen pro Durchlauf
   EV_BILLING_DEST =  "Standard RFC Destination for Synchronous BAPI Calls
   EV_REPLICATION_LOGSYS =  "Logical System
   EV_REPLICATION_DEST =  "Standard RFC Destination for Synchronous BAPI Calls
   EV_CREDIT_CHECK_DEST =  "Standard RFC Destination for Synchronous BAPI Calls
   EV_APOATP_DEST =  "Standard RFC Destination for Synchronous BAPI Calls
   EV_PARVAL2 =  "Parameter value 2
   EV_PURCH_AGREEMENT_DEST =  "Standard RFC Destination for Synchronous BAPI Calls
   EV_CUST_FACT_SHEET_BW_DEST =  "Standard RFC Destination for Synchronous BAPI Calls

EXCEPTIONS
   PARAMETER_ERROR = 1    ERROR_OCCURRED = 2    DESTINATION_NOT_DEFINED = 3
.



IMPORTING Parameters details for CRM_TOOLS_SYSTEM_GET

IV_HEADER_GUID - GUID eines CRM-Order-Objekts, not used

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

IV_ITEM_GUID - GUID der Position, not used

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

IS_PARTNER_EXT - Übergabestruktur für die Partner, not used

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

IS_ORGMAN - Orgdaten Set: Struktur der Workarea und der Puffer, not used

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

IS_CREDIT_DATA - Daten für externe Kreditprüfungen (1. Eintrag), not used

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

EXPORTING Parameters details for CRM_TOOLS_SYSTEM_GET

EV_BILLING_LOGSYS - Logical System

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

EV_CUST_FACT_SHEET_OLTP_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EV_MAX_NUMBER_CHECKS - max. Anzahl ATP Pruefungen pro Durchlauf

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

EV_BILLING_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EV_REPLICATION_LOGSYS - Logical System

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

EV_REPLICATION_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EV_CREDIT_CHECK_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EV_APOATP_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EV_PARVAL2 - Parameter value 2

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

EV_PURCH_AGREEMENT_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EV_CUST_FACT_SHEET_BW_DEST - Standard RFC Destination for Synchronous BAPI Calls

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

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURRED -

Data type:
Optional: No
Call by Reference: Yes

DESTINATION_NOT_DEFINED -

Data type:
Optional: No
Call by Reference: Yes

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

DATA:
lv_iv_header_guid  TYPE CRMT_OBJECT_GUID, "   
lv_parameter_error  TYPE CRMT_OBJECT_GUID, "   
lv_ev_billing_logsys  TYPE LOGSYS, "   
lv_ev_cust_fact_sheet_oltp_dest  TYPE BDBAPIDST, "   
lv_ev_max_number_checks  TYPE SYTABIX, "   
lv_iv_item_guid  TYPE CRMT_OBJECT_GUID, "   
lv_error_occurred  TYPE CRMT_OBJECT_GUID, "   
lv_ev_billing_dest  TYPE BDBAPIDST, "   
lv_is_partner_ext  TYPE CRMT_PARTNER_EXTERNAL_WRK, "   
lv_ev_replication_logsys  TYPE LOGSYS, "   
lv_destination_not_defined  TYPE LOGSYS, "   
lv_is_orgman  TYPE CRMT_ORGMAN_WRK, "   
lv_ev_replication_dest  TYPE BDBAPIDST, "   
lv_is_credit_data  TYPE CRMT_CREDITCALLS, "   
lv_ev_credit_check_dest  TYPE BDBAPIDST, "   
lv_ev_apoatp_dest  TYPE BDBAPIDST, "   
lv_ev_parval2  TYPE CHAR255, "   
lv_ev_purch_agreement_dest  TYPE BDBAPIDST, "   
lv_ev_cust_fact_sheet_bw_dest  TYPE BDBAPIDST. "   

  CALL FUNCTION 'CRM_TOOLS_SYSTEM_GET'  "Ermittlung der Externen Systeme
    EXPORTING
         IV_HEADER_GUID = lv_iv_header_guid
         IV_ITEM_GUID = lv_iv_item_guid
         IS_PARTNER_EXT = lv_is_partner_ext
         IS_ORGMAN = lv_is_orgman
         IS_CREDIT_DATA = lv_is_credit_data
    IMPORTING
         EV_BILLING_LOGSYS = lv_ev_billing_logsys
         EV_CUST_FACT_SHEET_OLTP_DEST = lv_ev_cust_fact_sheet_oltp_dest
         EV_MAX_NUMBER_CHECKS = lv_ev_max_number_checks
         EV_BILLING_DEST = lv_ev_billing_dest
         EV_REPLICATION_LOGSYS = lv_ev_replication_logsys
         EV_REPLICATION_DEST = lv_ev_replication_dest
         EV_CREDIT_CHECK_DEST = lv_ev_credit_check_dest
         EV_APOATP_DEST = lv_ev_apoatp_dest
         EV_PARVAL2 = lv_ev_parval2
         EV_PURCH_AGREEMENT_DEST = lv_ev_purch_agreement_dest
         EV_CUST_FACT_SHEET_BW_DEST = lv_ev_cust_fact_sheet_bw_dest
    EXCEPTIONS
        PARAMETER_ERROR = 1
        ERROR_OCCURRED = 2
        DESTINATION_NOT_DEFINED = 3
. " CRM_TOOLS_SYSTEM_GET




ABAP code using 7.40 inline data declarations to call FM CRM_TOOLS_SYSTEM_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!