SAP SCRMFR_APPEND_DATA Function Module for









SCRMFR_APPEND_DATA is a standard scrmfr append data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 scrmfr append data FM, simply by entering the name SCRMFR_APPEND_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function SCRMFR_APPEND_DATA 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 'SCRMFR_APPEND_DATA'"
  EXPORTING
   IM_RES_DATA =  "Check Results Management: the Copy of Structure of CRMCHKRES
*  IM_SOFTWARECOMP =  "Software Components Versions
*  IM_EXPVERS =  "Components' Exports
*  IM_ENV_ID =  "Check Results Management: ID of Object Set to Be Checked
   IM_WHORU =  "User name in user master record
   IM_RESL_DATA =  "Check Results Management: the Copy of Struct. of CRMCHKRESL
   IM_IPMSG_DATA =  "Result of Comparision Between Actual Chckres & Reference DB
   IM_T100_LINES =  "Check Results Management: Texts of Messages from T100
   IM_TPOOL_LINES =  "Check Results Management: Text Pool Items
   IM_TRMSG_LINES =  "Check Results Management: Texts of Messages of Syntax Checks
   IM_DOKIL_LINES =  "Check Results Management: Index for Doc. Table DOKHL
   IM_DOKTL_LINES =  "Check Results Management: Documentation - Text Lines
*  IM_ENV_INFO =  "Check Results Management: Environment Info

 IMPORTING
   EX_ENV_ID =  "Check Results Management: ID of Object Set to Be Checked
   EX_ERR_DUP_KEYS =  "Single-Character Flag

EXCEPTIONS
   NO_ENVINFO = 1    GET_NEXT_ENVID_FAULT = 2    INVALID_ENVID = 3    AUTHORITY_CHECK_FAILED = 4
.



IMPORTING Parameters details for SCRMFR_APPEND_DATA

IM_RES_DATA - Check Results Management: the Copy of Structure of CRMCHKRES

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

IM_SOFTWARECOMP - Software Components Versions

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

IM_EXPVERS - Components' Exports

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

IM_ENV_ID - Check Results Management: ID of Object Set to Be Checked

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

IM_WHORU - User name in user master record

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

IM_RESL_DATA - Check Results Management: the Copy of Struct. of CRMCHKRESL

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

IM_IPMSG_DATA - Result of Comparision Between Actual Chckres & Reference DB

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

IM_T100_LINES - Check Results Management: Texts of Messages from T100

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

IM_TPOOL_LINES - Check Results Management: Text Pool Items

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

IM_TRMSG_LINES - Check Results Management: Texts of Messages of Syntax Checks

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

IM_DOKIL_LINES - Check Results Management: Index for Doc. Table DOKHL

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

IM_DOKTL_LINES - Check Results Management: Documentation - Text Lines

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

IM_ENV_INFO - Check Results Management: Environment Info

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

EXPORTING Parameters details for SCRMFR_APPEND_DATA

EX_ENV_ID - Check Results Management: ID of Object Set to Be Checked

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

EX_ERR_DUP_KEYS - Single-Character Flag

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

EXCEPTIONS details

NO_ENVINFO -

Data type:
Optional: No
Call by Reference: Yes

GET_NEXT_ENVID_FAULT -

Data type:
Optional: No
Call by Reference: Yes

INVALID_ENVID -

Data type:
Optional: No
Call by Reference: Yes

AUTHORITY_CHECK_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SCRMFR_APPEND_DATA 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_ex_env_id  TYPE CRMOBSETID, "   
lv_no_envinfo  TYPE CRMOBSETID, "   
lv_im_res_data  TYPE CRM_RDCHKRES, "   
lv_im_softwarecomp  TYPE CRM_COMPS, "   
lv_im_expvers  TYPE CRM_EXPVRS, "   
lv_im_env_id  TYPE CRMOBSETID, "   
lv_im_whoru  TYPE XUBNAME, "   
lv_im_resl_data  TYPE CRM_RDCHKRESL, "   
lv_ex_err_dup_keys  TYPE CHAR1, "   
lv_get_next_envid_fault  TYPE CHAR1, "   
lv_im_ipmsg_data  TYPE CRM_RDIPMSG, "   
lv_invalid_envid  TYPE CRM_RDIPMSG, "   
lv_im_t100_lines  TYPE CRM_RDT100, "   
lv_authority_check_failed  TYPE CRM_RDT100, "   
lv_im_tpool_lines  TYPE CRM_RDTPOOL, "   
lv_im_trmsg_lines  TYPE CRM_RDTRMS, "   
lv_im_dokil_lines  TYPE CRM_RDBDKIL, "   
lv_im_doktl_lines  TYPE CRM_RDBDKTL, "   
lv_im_env_info  TYPE CRMCHKENVX. "   

  CALL FUNCTION 'SCRMFR_APPEND_DATA'  "
    EXPORTING
         IM_RES_DATA = lv_im_res_data
         IM_SOFTWARECOMP = lv_im_softwarecomp
         IM_EXPVERS = lv_im_expvers
         IM_ENV_ID = lv_im_env_id
         IM_WHORU = lv_im_whoru
         IM_RESL_DATA = lv_im_resl_data
         IM_IPMSG_DATA = lv_im_ipmsg_data
         IM_T100_LINES = lv_im_t100_lines
         IM_TPOOL_LINES = lv_im_tpool_lines
         IM_TRMSG_LINES = lv_im_trmsg_lines
         IM_DOKIL_LINES = lv_im_dokil_lines
         IM_DOKTL_LINES = lv_im_doktl_lines
         IM_ENV_INFO = lv_im_env_info
    IMPORTING
         EX_ENV_ID = lv_ex_env_id
         EX_ERR_DUP_KEYS = lv_ex_err_dup_keys
    EXCEPTIONS
        NO_ENVINFO = 1
        GET_NEXT_ENVID_FAULT = 2
        INVALID_ENVID = 3
        AUTHORITY_CHECK_FAILED = 4
. " SCRMFR_APPEND_DATA




ABAP code using 7.40 inline data declarations to call FM SCRMFR_APPEND_DATA

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!