SAP /IPRO/MULTITASK Function Module for rfc for multi tasking of assembly transformations









/IPRO/MULTITASK is a standard /ipro/multitask SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for rfc for multi tasking of assembly transformations 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 /ipro/multitask FM, simply by entering the name /IPRO/MULTITASK into the relevant SAP transaction such as SE37 or SE38.

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



Function /IPRO/MULTITASK 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 '/IPRO/MULTITASK'"rfc for multi tasking of assembly transformations
  EXPORTING
   INPUT_XSTRING =  "
   PIV_LEVEL =  "
   PIV_INTOC_CVAL =  "Single-Character Flag
   PIV_NEED_TITLE =  "Y or N
   PIV_ELEMNT_TYPE =  "1 fulltext 2 IBR
   PIV_TOC_ELEMNT =  "B for TOC
   PIV_CLAUSE_ID =  "
   PIV_TEXT_STYLE =  "
   PIV_ILFO =  "
   PIV_NUMBERED =  "
   PIV_TITLE =  "

 IMPORTING
   OUTPUT_XSTRING =  "
.



IMPORTING Parameters details for /IPRO/MULTITASK

INPUT_XSTRING -

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

PIV_LEVEL -

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

PIV_INTOC_CVAL - Single-Character Flag

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

PIV_NEED_TITLE - Y or N

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

PIV_ELEMNT_TYPE - 1 fulltext 2 IBR

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

PIV_TOC_ELEMNT - B for TOC

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

PIV_CLAUSE_ID -

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

PIV_TEXT_STYLE -

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

PIV_ILFO -

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

PIV_NUMBERED -

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

PIV_TITLE -

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

EXPORTING Parameters details for /IPRO/MULTITASK

OUTPUT_XSTRING -

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

Copy and paste ABAP code example for /IPRO/MULTITASK 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_input_xstring  TYPE XSTRING, "   
lv_output_xstring  TYPE XSTRING, "   
lv_piv_level  TYPE STRING, "   
lv_piv_intoc_cval  TYPE CHAR1, "   
lv_piv_need_title  TYPE CHAR1, "   
lv_piv_elemnt_type  TYPE CHAR1, "   
lv_piv_toc_elemnt  TYPE CHAR1, "   
lv_piv_clause_id  TYPE STRING, "   
lv_piv_text_style  TYPE STRING, "   
lv_piv_ilfo  TYPE STRING, "   
lv_piv_numbered  TYPE STRING, "   
lv_piv_title  TYPE STRING. "   

  CALL FUNCTION '/IPRO/MULTITASK'  "rfc for multi tasking of assembly transformations
    EXPORTING
         INPUT_XSTRING = lv_input_xstring
         PIV_LEVEL = lv_piv_level
         PIV_INTOC_CVAL = lv_piv_intoc_cval
         PIV_NEED_TITLE = lv_piv_need_title
         PIV_ELEMNT_TYPE = lv_piv_elemnt_type
         PIV_TOC_ELEMNT = lv_piv_toc_elemnt
         PIV_CLAUSE_ID = lv_piv_clause_id
         PIV_TEXT_STYLE = lv_piv_text_style
         PIV_ILFO = lv_piv_ilfo
         PIV_NUMBERED = lv_piv_numbered
         PIV_TITLE = lv_piv_title
    IMPORTING
         OUTPUT_XSTRING = lv_output_xstring
. " /IPRO/MULTITASK




ABAP code using 7.40 inline data declarations to call FM /IPRO/MULTITASK

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!