SOS_MAPPING_UPDATE SAP Function module

SOS_MAPPING_UPDATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SOS_MAPPING_UPDATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: OSMA
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SOS_MAPPING_UPDATE - SOS MAPPING UPDATE

CALL FUNCTION 'SOS_MAPPING_UPDATE' "
  EXPORTING
    clsname =                   " seoclskey     Name of Class
*   recordname = ' '            " objectname    Name of ABAP Dictionary Object
*   version = '0'               " seoversion    Version
  TABLES
    new_header_tab =            " seomapcls_tab
    new_attribute_tab =         " seomapatt_tab
  EXCEPTIONS
    OP_FAILURE = 1              "               Operation failed
    NO_MAPPING_FOUND = 2        "
    .  "  SOS_MAPPING_UPDATE

ABAP code example for Function Module SOS_MAPPING_UPDATE

The ABAP code below is a full code listing to execute function module SOS_MAPPING_UPDATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_new_header_tab  
 
 TYPE STANDARD TABLE OF SEOMAPCLS_TAB,"TABLES PARAM
wa_new_header_tab
 
 LIKE LINE OF it_new_header_tab
,
it_new_attribute_tab  
 
 TYPE STANDARD TABLE OF SEOMAPATT_TAB,"TABLES PARAM
wa_new_attribute_tab
 
 LIKE LINE OF it_new_attribute_tab
.


DATA(ld_clsname) = 'Check type of data required'.

DATA(ld_recordname) = 'Check type of data required'.

DATA(ld_version) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_new_header_tab to it_new_header_tab.
 

"populate fields of struture and append to itab
append wa_new_attribute_tab to it_new_attribute_tab.
.

CALL FUNCTION 'SOS_MAPPING_UPDATE'
  EXPORTING
    clsname =                    ld_clsname
*   recordname =                 ld_recordname
*   version =                    ld_version
  TABLES
    new_header_tab =             it_new_header_tab
    new_attribute_tab =          it_new_attribute_tab
  EXCEPTIONS
    OP_FAILURE =                 1
    NO_MAPPING_FOUND =           2
    .  "  SOS_MAPPING_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_clsname
 
 TYPE SEOCLSKEY ,
it_new_header_tab
 
 TYPE STANDARD TABLE OF SEOMAPCLS_TAB ,
wa_new_header_tab
 
 LIKE LINE OF it_new_header_tab,
ld_recordname
 
 TYPE OBJECTNAME ,
it_new_attribute_tab
 
 TYPE STANDARD TABLE OF SEOMAPATT_TAB ,
wa_new_attribute_tab
 
 LIKE LINE OF it_new_attribute_tab,
ld_version
 
 TYPE SEOVERSION .


ld_clsname = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_new_header_tab to it_new_header_tab.
ld_recordname = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_new_attribute_tab to it_new_attribute_tab.
ld_version = 'Check type of data required'.