SAP ASSIGNMENT_SKOART_SKOTYP_TABLE Function Module for









ASSIGNMENT_SKOART_SKOTYP_TABLE is a standard assignment skoart skotyp table 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 assignment skoart skotyp table FM, simply by entering the name ASSIGNMENT_SKOART_SKOTYP_TABLE into the relevant SAP transaction such as SE37 or SE38.

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



Function ASSIGNMENT_SKOART_SKOTYP_TABLE 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 'ASSIGNMENT_SKOART_SKOTYP_TABLE'"
  EXPORTING
   IP_SIKOTYP =  "
*  IP_CHECK_NONAMBIG = 'X' "
*  IP_EMESSAGES_SHOW = ' ' "
*  IP_EMESSAGES_ITAB = 'X' "

CHANGING
*  EFLG_NONAMBIGUOUS =  "

TABLES
   ET_SKOTYPART_TAB =  "
*  ET_MESG =  "

EXCEPTIONS
   NO_SIKOTYP_ASSIGNED = 1    NO_SKOART_ASSIGNED = 2    NO_SKOARTTYP_MAINTAINED = 3    NO_SKOTYP_MAINTAINED = 4    ERROR_IN_MESSAGE_SET_DEF = 5    ERROR_IN_MESSAGE_STORE = 6    ERROR_IN_MESSAGE_SHOW = 7
.



IMPORTING Parameters details for ASSIGNMENT_SKOART_SKOTYP_TABLE

IP_SIKOTYP -

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

IP_CHECK_NONAMBIG -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

IP_EMESSAGES_SHOW -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

IP_EMESSAGES_ITAB -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ASSIGNMENT_SKOART_SKOTYP_TABLE

EFLG_NONAMBIGUOUS -

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

TABLES Parameters details for ASSIGNMENT_SKOART_SKOTYP_TABLE

ET_SKOTYPART_TAB -

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

ET_MESG -

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

EXCEPTIONS details

NO_SIKOTYP_ASSIGNED -

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

NO_SKOART_ASSIGNED -

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

NO_SKOARTTYP_MAINTAINED -

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

NO_SKOTYP_MAINTAINED -

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

ERROR_IN_MESSAGE_SET_DEF -

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

ERROR_IN_MESSAGE_STORE -

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

ERROR_IN_MESSAGE_SHOW -

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

Copy and paste ABAP code example for ASSIGNMENT_SKOART_SKOTYP_TABLE 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_ip_sikotyp  TYPE SIKOTYP, "   
lt_et_skotypart_tab  TYPE STANDARD TABLE OF RFVISKOTYPARTASSIGN, "   
lv_eflg_nonambiguous  TYPE XFELD, "   
lv_no_sikotyp_assigned  TYPE XFELD, "   
lt_et_mesg  TYPE STANDARD TABLE OF SMESG, "   
lv_ip_check_nonambig  TYPE XFELD, "   'X'
lv_no_skoart_assigned  TYPE XFELD, "   
lv_ip_emessages_show  TYPE XFELD, "   SPACE
lv_no_skoarttyp_maintained  TYPE XFELD, "   
lv_ip_emessages_itab  TYPE XFELD, "   'X'
lv_no_skotyp_maintained  TYPE XFELD, "   
lv_error_in_message_set_def  TYPE XFELD, "   
lv_error_in_message_store  TYPE XFELD, "   
lv_error_in_message_show  TYPE XFELD. "   

  CALL FUNCTION 'ASSIGNMENT_SKOART_SKOTYP_TABLE'  "
    EXPORTING
         IP_SIKOTYP = lv_ip_sikotyp
         IP_CHECK_NONAMBIG = lv_ip_check_nonambig
         IP_EMESSAGES_SHOW = lv_ip_emessages_show
         IP_EMESSAGES_ITAB = lv_ip_emessages_itab
    CHANGING
         EFLG_NONAMBIGUOUS = lv_eflg_nonambiguous
    TABLES
         ET_SKOTYPART_TAB = lt_et_skotypart_tab
         ET_MESG = lt_et_mesg
    EXCEPTIONS
        NO_SIKOTYP_ASSIGNED = 1
        NO_SKOART_ASSIGNED = 2
        NO_SKOARTTYP_MAINTAINED = 3
        NO_SKOTYP_MAINTAINED = 4
        ERROR_IN_MESSAGE_SET_DEF = 5
        ERROR_IN_MESSAGE_STORE = 6
        ERROR_IN_MESSAGE_SHOW = 7
. " ASSIGNMENT_SKOART_SKOTYP_TABLE




ABAP code using 7.40 inline data declarations to call FM ASSIGNMENT_SKOART_SKOTYP_TABLE

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_ip_check_nonambig) = 'X'.
 
 
DATA(ld_ip_emessages_show) = ' '.
 
 
DATA(ld_ip_emessages_itab) = 'X'.
 
 
 
 
 


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!