SAP CRM_IST_SO_FIELDTAB_SAVE Function Module for Ermitteln und Bearbeiten der Felder zu einem TSO
CRM_IST_SO_FIELDTAB_SAVE is a standard crm ist so fieldtab save 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 und Bearbeiten der Felder zu einem 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 fieldtab save FM, simply by entering the name CRM_IST_SO_FIELDTAB_SAVE 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_FIELDTAB_SAVE 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_FIELDTAB_SAVE'"Ermitteln und Bearbeiten der Felder zu einem TSO.
EXPORTING
* IV_HEADER_GUID = "GUID of a CRM Order Object
* IV_COMMIT = ' ' "Logical Variable
* IV_CHECK_ONLY = 'X' "Logical Variable
* IV_MODE = 'A' "Single-Character Flag
IMPORTING
ET_ERROR_TAB = "Error messages
ET_OBJLIST = "Service Industries: Assign Order Item to Object
ET_ITEM_ERROR_TAB = "Error List with Document Item Assignment
EXCEPTIONS
DIVISION_NOT_FOUND = 1 UNMAINTAINED_OBJECTS = 2
IMPORTING Parameters details for CRM_IST_SO_FIELDTAB_SAVE
IV_HEADER_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: Yes
IV_COMMIT - Logical Variable
Data type: CRMT_BOOLEANDefault: ' '
Optional: Yes
Call by Reference: Yes
IV_CHECK_ONLY - Logical Variable
Data type: CRMT_BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_MODE - Single-Character Flag
Data type: CHAR1Default: 'A'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for CRM_IST_SO_FIELDTAB_SAVE
ET_ERROR_TAB - Error messages
Data type: BAPIRET2_TABOptional: No
Call by Reference: Yes
ET_OBJLIST - Service Industries: Assign Order Item to Object
Data type: CRMT_SI_ITEM_OBJECT_REL_TABOptional: No
Call by Reference: Yes
ET_ITEM_ERROR_TAB - Error List with Document Item Assignment
Data type: CRMT_SI_ERROR_TABOptional: No
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)
UNMAINTAINED_OBJECTS - Ein oder mehrere Objekte wurden bisher nicht per FIELDTAB_MAINTAIN gepflegt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRM_IST_SO_FIELDTAB_SAVE 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_et_error_tab | TYPE BAPIRET2_TAB, " | |||
lv_iv_header_guid | TYPE CRMT_OBJECT_GUID, " | |||
lv_division_not_found | TYPE CRMT_OBJECT_GUID, " | |||
lv_iv_commit | TYPE CRMT_BOOLEAN, " ' ' | |||
lv_et_objlist | TYPE CRMT_SI_ITEM_OBJECT_REL_TAB, " | |||
lv_unmaintained_objects | TYPE CRMT_SI_ITEM_OBJECT_REL_TAB, " | |||
lv_iv_check_only | TYPE CRMT_BOOLEAN, " 'X' | |||
lv_et_item_error_tab | TYPE CRMT_SI_ERROR_TAB, " | |||
lv_iv_mode | TYPE CHAR1. " 'A' |
  CALL FUNCTION 'CRM_IST_SO_FIELDTAB_SAVE' "Ermitteln und Bearbeiten der Felder zu einem TSO |
EXPORTING | ||
IV_HEADER_GUID | = lv_iv_header_guid | |
IV_COMMIT | = lv_iv_commit | |
IV_CHECK_ONLY | = lv_iv_check_only | |
IV_MODE | = lv_iv_mode | |
IMPORTING | ||
ET_ERROR_TAB | = lv_et_error_tab | |
ET_OBJLIST | = lv_et_objlist | |
ET_ITEM_ERROR_TAB | = lv_et_item_error_tab | |
EXCEPTIONS | ||
DIVISION_NOT_FOUND = 1 | ||
UNMAINTAINED_OBJECTS = 2 | ||
. " CRM_IST_SO_FIELDTAB_SAVE |
ABAP code using 7.40 inline data declarations to call FM CRM_IST_SO_FIELDTAB_SAVE
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.DATA(ld_iv_commit) | = ' '. | |||
DATA(ld_iv_check_only) | = 'X'. | |||
DATA(ld_iv_mode) | = 'A'. | |||
Search for further information about these or an SAP related objects