SAP CRM_IST_SO_GET_FIELDTAB Function Module for Ermitteln der Feldnamen zum TSO









CRM_IST_SO_GET_FIELDTAB is a standard crm ist so get fieldtab SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ermitteln der Feldnamen zum TSO 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 fieldtab FM, simply by entering the name CRM_IST_SO_GET_FIELDTAB 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_FIELDTAB 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_FIELDTAB'"Ermitteln der Feldnamen zum TSO
EXPORTING
* IV_H_HEADER_GUID = "GUID of a CRM Order Object
* IV_I_DIVISION = "Division
* IV_I_ITEM_GUID = "GUID of a CRM Order Object
* IV_I_PRODUCT_GUID = "Internal Unique Identifier of Product
* IV_MODE = "Function code that PAI triggered

IMPORTING
ET_FIELDS = "TT to Structure Relevant Attributes in the Service Object
ET_ERROR_TAB = "Error messages

CHANGING
* CT_FIELDS = "TT to Structure Relevant Attributes in the Service Object

EXCEPTIONS
DIVISION_NOT_FOUND = 1
.



IMPORTING Parameters details for CRM_IST_SO_GET_FIELDTAB

IV_H_HEADER_GUID - GUID of a CRM Order Object

Data type: CRMT_OBJECT_GUID
Optional: Yes
Call by Reference: Yes

IV_I_DIVISION - Division

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

IV_I_ITEM_GUID - GUID of a CRM Order Object

Data type: CRMT_OBJECT_GUID
Optional: Yes
Call by Reference: Yes

IV_I_PRODUCT_GUID - Internal Unique Identifier of Product

Data type: CRMT_PRODUCT_GUID_DB
Optional: Yes
Call by Reference: Yes

IV_MODE - Function code that PAI triggered

Data type: SYUCOMM
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CRM_IST_SO_GET_FIELDTAB

ET_FIELDS - TT to Structure Relevant Attributes in the Service Object

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

ET_ERROR_TAB - Error messages

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

CHANGING Parameters details for CRM_IST_SO_GET_FIELDTAB

CT_FIELDS - TT to Structure Relevant Attributes in the Service Object

Data type: CRMT_IST_SO_RELATTR_TAB
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

DIVISION_NOT_FOUND - Die Sparte konnte nicht gefunden werden.

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

Copy and paste ABAP code example for CRM_IST_SO_GET_FIELDTAB 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_ct_fields  TYPE CRMT_IST_SO_RELATTR_TAB, "   
lv_et_fields  TYPE CRMT_IST_SO_RELATTR_TAB, "   
lv_iv_h_header_guid  TYPE CRMT_OBJECT_GUID, "   
lv_division_not_found  TYPE CRMT_OBJECT_GUID, "   
lv_et_error_tab  TYPE BAPIRET2_TAB, "   
lv_iv_i_division  TYPE SPART, "   
lv_iv_i_item_guid  TYPE CRMT_OBJECT_GUID, "   
lv_iv_i_product_guid  TYPE CRMT_PRODUCT_GUID_DB, "   
lv_iv_mode  TYPE SYUCOMM. "   

  CALL FUNCTION 'CRM_IST_SO_GET_FIELDTAB'  "Ermitteln der Feldnamen zum TSO
    EXPORTING
         IV_H_HEADER_GUID = lv_iv_h_header_guid
         IV_I_DIVISION = lv_iv_i_division
         IV_I_ITEM_GUID = lv_iv_i_item_guid
         IV_I_PRODUCT_GUID = lv_iv_i_product_guid
         IV_MODE = lv_iv_mode
    IMPORTING
         ET_FIELDS = lv_et_fields
         ET_ERROR_TAB = lv_et_error_tab
    CHANGING
         CT_FIELDS = lv_ct_fields
    EXCEPTIONS
        DIVISION_NOT_FOUND = 1
. " CRM_IST_SO_GET_FIELDTAB




ABAP code using 7.40 inline data declarations to call FM CRM_IST_SO_GET_FIELDTAB

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!