SAP CRM_IST_SO_GET_FIELD_CUST Function Module for Einstellungen zu Datenfeldern eines Serviceobjekts lesen









CRM_IST_SO_GET_FIELD_CUST is a standard crm ist so get field cust SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Einstellungen zu Datenfeldern eines Serviceobjekts lesen 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 ist so get field cust FM, simply by entering the name CRM_IST_SO_GET_FIELD_CUST into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_IST_SO_GET_FIELD_CUST 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_IST_SO_GET_FIELD_CUST'"Einstellungen zu Datenfeldern eines Serviceobjekts lesen
EXPORTING
IV_DIVISION = "Division
* IV_LANGU = SY-LANGU "Language Key for Current Text Environment

IMPORTING
EV_INVISIBLE = "Single-Character Flag

CHANGING
CS_FIELDINFO = "Structure for Relevant Attributes in the Service Object
.



IMPORTING Parameters details for CRM_IST_SO_GET_FIELD_CUST

IV_DIVISION - Division

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

IV_LANGU - Language Key for Current Text Environment

Data type: SY-LANGU
Default: SY-LANGU
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CRM_IST_SO_GET_FIELD_CUST

EV_INVISIBLE - Single-Character Flag

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

CHANGING Parameters details for CRM_IST_SO_GET_FIELD_CUST

CS_FIELDINFO - Structure for Relevant Attributes in the Service Object

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

Copy and paste ABAP code example for CRM_IST_SO_GET_FIELD_CUST 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_division  TYPE SPART, "   
lv_cs_fieldinfo  TYPE CRMT_IST_SO_RELATTR_STRUC, "   
lv_ev_invisible  TYPE COMT_CHECKBOX, "   
lv_iv_langu  TYPE SY-LANGU. "   SY-LANGU

  CALL FUNCTION 'CRM_IST_SO_GET_FIELD_CUST'  "Einstellungen zu Datenfeldern eines Serviceobjekts lesen
    EXPORTING
         IV_DIVISION = lv_iv_division
         IV_LANGU = lv_iv_langu
    IMPORTING
         EV_INVISIBLE = lv_ev_invisible
    CHANGING
         CS_FIELDINFO = lv_cs_fieldinfo
. " CRM_IST_SO_GET_FIELD_CUST




ABAP code using 7.40 inline data declarations to call FM CRM_IST_SO_GET_FIELD_CUST

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 LANGU FROM SY INTO @DATA(ld_iv_langu).
DATA(ld_iv_langu) = SY-LANGU.
 


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!