SAP CRM_IC_SCRIPTING_GET_SCRBUNDLE Function Module for Get translation table for a give script









CRM_IC_SCRIPTING_GET_SCRBUNDLE is a standard crm ic scripting get scrbundle SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get translation table for a give script 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 ic scripting get scrbundle FM, simply by entering the name CRM_IC_SCRIPTING_GET_SCRBUNDLE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CRM_IC_SCRIPTING_PERSIST
Program Name: SAPLCRM_IC_SCRIPTING_PERSIST
Main Program: SAPLCRM_IC_SCRIPTING_PERSIST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CRM_IC_SCRIPTING_GET_SCRBUNDLE 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_IC_SCRIPTING_GET_SCRBUNDLE'"Get translation table for a give script
EXPORTING
OBJECTID = "Script ID
OBJECTTYPE = "IC Component ID

IMPORTING
BUNDLED_DATA = "Data bundled for download

EXCEPTIONS
OBJECT_NOT_FOUND = 1 ERROR_OCCURRED = 2
.



IMPORTING Parameters details for CRM_IC_SCRIPTING_GET_SCRBUNDLE

OBJECTID - Script ID

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

OBJECTTYPE - IC Component ID

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

EXPORTING Parameters details for CRM_IC_SCRIPTING_GET_SCRBUNDLE

BUNDLED_DATA - Data bundled for download

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

EXCEPTIONS details

OBJECT_NOT_FOUND - Object not found

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURRED - An error happened when creating the XML

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_IC_SCRIPTING_GET_SCRBUNDLE 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_objectid  TYPE CRM_IC_XMLNAME, "   
lv_bundled_data  TYPE STRING, "   
lv_object_not_found  TYPE STRING, "   
lv_objecttype  TYPE CRM_IC_COMID, "   
lv_error_occurred  TYPE CRM_IC_COMID. "   

  CALL FUNCTION 'CRM_IC_SCRIPTING_GET_SCRBUNDLE'  "Get translation table for a give script
    EXPORTING
         OBJECTID = lv_objectid
         OBJECTTYPE = lv_objecttype
    IMPORTING
         BUNDLED_DATA = lv_bundled_data
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        ERROR_OCCURRED = 2
. " CRM_IC_SCRIPTING_GET_SCRBUNDLE




ABAP code using 7.40 inline data declarations to call FM CRM_IC_SCRIPTING_GET_SCRBUNDLE

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!