What are the parameters of run_product?

What are the parameters of run_product?
Please help me.
Regards,
Arjun

http://download.oracle.com/otn_hosted_doc/forms/forms/A73074_01.pdf

Similar Messages

I have created a quotation in CRM system. I want that to be downloaded into ECC, so that, I can create a sales order there with reference to that quotation. So, what are the parameters that I need to set in CRM system so that my quotation gets replicated?

Dear Experts,
I have created a quotation in CRM system. I want that to be downloaded into ECC, so that, I can create a sales order there with reference to that quotation. What are the parameters that I need to set in CRM system so that my quotation gets replicated without any error?
Please help me in this regard. An early and in detail step by step guidance is highly appreciated.
Thanks,
SMTP

It may be best to recreate the folder and the smart playlists from scratch.
tt2

What are the parameters in Call transaction method?

Hi ABAPER'S,
Please give me what are the parameters in call transaction method?
Thanks,
Prakash

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
Syntax:
CALL TRANSACTION <tcode>
USING <bdc_tab>
MODE <mode>
UPDATE <update>
<tcode> : Transaction code
<bdc_tab> : Internal table of structure BDCDATA.
<mode> : Display mode:
A
Display all
E
Display errors only
N
No display
<update> : Update mode:
S
Synchronous
A
Asynchronous
L
Local update
A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION 'TFCA' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
The MODE Parameter
You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
A Display all. All screens and the data that goes in them appear when you run your program.
N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The UPDATE Parameter
You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
The MESSAGES Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
(This example uses a flight connection that does not exist to trigger an error in the transaction.)
DATA: BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.
BDCDATA-PROGRAM = 'SAPMTFCA'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CARRID'.
BDCDATA-FVAL = 'XX'.
APPEND BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CONNID'.
BDCDATA-FVAL = '0400'.
APPEND BDCDATA.
CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
LOOP AT MESSTAB.
WRITE: / MESSTAB-TCODE,
MESSTAB-DYNAME,
MESSTAB-DYNUMB,
MESSTAB-MSGTYP,
MESSTAB-MSGSPRA,
MESSTAB-MSGID,
MESSTAB-MSGNR.
ENDLOOP.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Return codes:
Value
Explanation
0
Successful
<=1000
Error in dialog program
> 1000
Batch input error
System fields:
Name:
Explanation:
SY-MSGID
Message-ID
SY-MSGTY
Message type (E,I,W,S,A,X)
SY-MSGNO
Message number
SY-MSGV1
Message variable 1
SY-MSGV2
Message variable 2
SY-MSGV3
Message variable 3
SY-MSGV4
Message variable 4
Error Analysis and Restart Capability
Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
write out or save the message table
use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

What are the parameters which control the pop up of sales area

Hi Experts
What are the parameters which control the pop up of sales area along with sales office when Sold to party is fed in to the CRM order .
I have an issue   that, though the distribution channel and division is maintained in the sales org it is not   appearing in the pop up.
The BP   is extended to the sales area .
If any one can give me details / documentataion   on the setting , it is highly appreciated.
Regards
Raj

Dear Srikanth
Thank for your up date . in my case   the customer is assigned with   two sales area. The org model , nothing is maintained in the attributes , still one is appearing in the pop up and and other one is not . It is surpricing.
if you can mention the logic of maintaining the   division and distribution channel inthe attribute it is of great help.
Regards
Raj

What are the parameters of Function Module

Hi,
What are the parameters of Function Module?

Function Modules are special external subroutine stored in a central library. The R/3 system provides numerous predefined function modules that you can call from the ABAP/4 programs.
All the function Modules are created under the Function Groups. Function Groups are nothing but the related group of function modules.
The function modules can be maintained through T.CodeSE37 and T.Code SE80.
In general the function module has the following components.
Documentation:
This is the place where you can find the discription/purpose of the function module.
Import & Export Parameters.
Import parameters correspond to the formal input parameters of subroutines. They pass data from the calling program to the function module.
Export parameters correspond to the formal input parameters of subroutines. They pass data from the function module back to the calling program.
Table Parameters.
Table parameters are internal tables. Internal tables are treated like changing parameters and are always passed by reference.
Exceptions.
Exceptions are used to handle error scenarios which can occur in the function modules. The function modules checks for any type of error and raise exception and returns SY-SUBRC value to the calling program.
Source Code:
the programming logic of the function module is written in this source code.
Rewards if useful.

What are the parameters for DB2 / JDBC Connetivity?

I have insert IDoc data from SAP > XI > DB2.
What are the connection parameters for the Reeiver JDBC channel to connect from XI to a DB2 database?
Regards,
Bhaskar

Hey
please have a look at the following thread
JDBC connection to DB2 Database
also please search SDN for DB2 drivers,there is lots of material for it
thanx
Aamir

What are the parameters have to pass to bapi material creation?

can any one help me in creating material by using bapi.....
which is 'BAPI_MATERIAL_SAVEDATA'.....by using the above bapi wen i am creating material....how to pass data to that bapi....what are the thing s i ahve to pass.........

hi
please chk this code
TYPES : BEGIN OF S_BAPI,
        MATNR LIKE MARA-MATNR,
        MBRSH LIKE MARA-MBRSH,
        MTART LIKE MARA-MTART,
        MAKTX LIKE MAKT-MAKTX,
        MEINS LIKE MARA-MEINS,
        MATKL LIKE MARA-MATKL,
        END OF S_BAPI.
DATA : I_BAPI TYPE STANDARD TABLE OF S_BAPI WITH HEADER LINE.
PARAMETER : P_FILE LIKE RLGRAP-FILENAME DEFAULT 'C:\Documents and Settings\mansi_makhijani\Desktop\upload.txt'.
CALL FUNCTION 'WS_UPLOAD'
EXPORTING
CODEPAGE                      = ' '
   FILENAME                      = P_FILE
   FILETYPE                      = 'DAT'
HEADLEN                       = ' '
LINE_EXIT                     = ' '
TRUNCLEN                      = ' '
USER_FORM                     = ' '
USER_PROG                     = ' '
DAT_D_FORMAT                  = ' '
IMPORTING
FILELENGTH                    =
TABLES
    DATA_TAB                      = I_BAPI
EXCEPTIONS
CONVERSION_ERROR              = 1
FILE_OPEN_ERROR               = 2
FILE_READ_ERROR               = 3
INVALID_TYPE                  = 4
NO_BATCH                      = 5
UNKNOWN_ERROR                 = 6
INVALID_TABLE_WIDTH           = 7
GUI_REFUSE_FILETRANSFER       = 8
CUSTOMER_ERROR                = 9
NO_AUTHORITY                  = 10
OTHERS                        = 11
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
DATA : S_HEADDATA TYPE BAPIMATHEAD,
       S_CLIENTDATA TYPE BAPI_MARA,
       S_CLIENTDATAX TYPE BAPI_MARAX,
       I_MAKT TYPE STANDARD TABLE OF BAPI_MAKT WITH HEADER LINE.
LOOP AT I_BAPI.
S_HEADDATA-MATERIAL = I_BAPI-MATNR.
S_HEADDATA-IND_SECTOR = I_BAPI-MBRSH.
S_HEADDATA-MATL_TYPE = I_BAPI-MTART.
S_CLIENTDATA-MATL_GROUP = I_BAPI-MATKL.
S_CLIENTDATA-BASE_UOM = I_BAPI-MEINS.
S_CLIENTDATAX-MATL_GROUP ='X'.
S_CLIENTDATAX-BASE_UOM ='X'.
I_MAKT-MATL_DESC = I_BAPI-MAKTX.
I_MAKT-LANGU_ISO ='EN'.
I_MAKT-LANGU ='EN'.
I_MAKT-DEL_FLAG =' '.
CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
    EXPORTING
      HEADDATA                  = S_HEADDATA
   CLIENTDATA                  = S_CLIENTDATA
   CLIENTDATAX                 = S_CLIENTDATAX
PLANTDATA                   =
PLANTDATAX                  =
FORECASTPARAMETERS          =
FORECASTPARAMETERSX         =
PLANNINGDATA                =
PLANNINGDATAX               =
STORAGELOCATIONDATA         =
STORAGELOCATIONDATAX        =
VALUATIONDATA               =
VALUATIONDATAX              =
WAREHOUSENUMBERDATA         =
WAREHOUSENUMBERDATAX        =
SALESDATA                   =
SALESDATAX                  =
STORAGETYPEDATA             =
STORAGETYPEDATAX            =
FLAG_ONLINE                 = ' '
FLAG_CAD_CALL               = ' '
NO_DEQUEUE                  = ' '
IMPORTING
RETURN                      =
TABLES
   MATERIALDESCRIPTION         = I_MAKT
UNITSOFMEASURE              =
UNITSOFMEASUREX             =
INTERNATIONALARTNOS         =
MATERIALLONGTEXT            =
TAXCLASSIFICATIONS          =
RETURNMESSAGES              =
PRTDATA                     =
PRTDATAX                    =
EXTENSIONIN                 =
EXTENSIONINX                =
NFMCHARGEWEIGHTS            =
NFMCHARGEWEIGHTSX           =
NFMSTRUCTURALWEIGHTS        =
NFMSTRUCTURALWEIGHTSX       =
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT          =
IMPORTING
RETURN        =
ENDLOOP.
~hitesh
If your queries are solved try to close the thread

What are the parameters? can u say what type of parameters regularly used?

what are the perameters? can u say what type of perameters regularly used?

Dear Srikanth
Thank for your up date . in my case the customer is assigned with two sales area. The org model , nothing is maintained in the attributes , still one is appearing in the pop up and and other one is not . It is surpricing.
if you can mention the logic of maintaining the division and distribution channel inthe attribute it is of great help.
Regards
Raj

What are the parameters "page-forward" and "page-backward" used for?

In the LIMITS section of the Netscape Calendar Server configuration
documentation, there are two parameters called "page-forward" and
"page-backward." The default setting for these parameters is FALSE. However,
it is unclear what these parameters are used for.
<P>
With previous versions of Calendar Server, you could scroll one page forward
or one page backward through the user search screens. However, with the
implementation of LDAP in later versions, the options have been disabled in
the client.
<P>
Although the page-forward and page-backward parameters are documented in the
Administrator guides for Calendar Server versions 3.5 and 4.0, the guides
state that the default value of FALSE for both parameters cannot be
changed. In actuality, the parameters can be changed. However, the reason
that users should not change these parameters is that versions 3.5 and 4.0
do not support the page-forward and page-backward capabilities. So to avoid
errors, please do not change these parameters from the default value of FALSE.

if AdobeRGB is the more professional working space, then why not use that profile?
on the web (and in unmanaged and broken work flows) sRGB is the safest profile (source space)
just open your tagged Adobe RGB and tagged ProPhoto RGB document (use the embedded profile in each document)
and go to View> Proof Setup: Monitor RGB (notice the loss in saturation? that's how most of the people on the Internet will be viewing your color, assuming you have a standard-gamut monitor like most people)
always CONVERT to sRGB for the World Wide Web
i didn't read your link
anyone who recommends "disable color management in Photoshop" -- set Working RGB to "Monitor RGB" -- AND MOST UNBELIEVABLY -- "Don't color manage this document" (ignore embedded profiles) ------ is pretty mixed up (in my opinion)
i will recommend reading JEFF SCHEWE and BRUCE FRASER for professional color management information

Dbms_stats.gather_table_stats; What are the parameters you gurus use?

DB Version :10.2.0.1.0
Sometimes i want to collect the stats of just few tables. I use the following script to gather individual table stats. Are these parameters OK?
begin
dbms_stats.gather_table_stats(user, upper('table_name'), estimate_percent=>100,
no_invalidate=>false);
end;
/

Hi,
Check this links
[GATHER_TABLE_STATS Procedure|http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_stats.htm#i1036461]
[Using the DBMS_STATS-package|http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:735625536552]
[Analyze and DBMS_STATS|http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:4347359891525]
Regards,

What are the parameters of mobileUpgradetarget.exe?

Hi CRM Gurus,
does someone know the parameters of clientupgradetarget.exe?
Because i get an error during executing of a mup-file, which was inside of a SAP UNIT.
Synchronously starting command : "C:\Programme\SAP\Mobile\Bin.Net\ClientUpgradeTarget.exe" /MUP["C:\Programme\SAP\Mobile\5.00.SP.15\MobileComponentUpgrade\HotFix\MandatoryFix.mup"] /COC[Yes] /UTS[HotFixMCLOnly]
                            Return value of command : -532459699
regards
Wolfgang

Hello Wolfgang,
The command options of ClientUpgradetarget.exe are:
/MUP[.....] - Path of MUP file OR folder where MUP file is stored
/COC[Yes or No] - Close on completion of upgrade
/SUI[Yes or No] - Show UI of the tool
/SMD[] - Silent Mode
/APP[Short name of application] - To choose application to be deployed
                                  if there are multiple applications in
                                  the upgrade package
/LAN[DE or EN etc.] - To choose language to be deployed if files and
                      folders related to multiple languages are present
/UTS[BOL or UI etc] - To choose specific units contained in the upgrade
Example -
ClientUpgradeTarget.exe /MUP["& strDir & "\SAPCRMUpgrade.mup] /COC[Yes] /UTS[UnitName1UnitName2UnitName3] /APP[MSA] /LAN[EN]
Thanks,
Rohit

What are the parameters of clientupgradetarget.exe?

Hi CRM Gurus,
does someone know the parameters of clientupgradetarget.exe?
Because i get an error during executing of a mup-file, which was inside of a SAP UNIT.
Synchronously starting command : "C:\Programme\SAP\Mobile\Bin.Net\ClientUpgradeTarget.exe" /MUP["C:\Programme\SAP\Mobile\5.00.SP.15\MobileComponentUpgrade\HotFix\MandatoryFix.mup"] /COC[Yes] /UTS[HotFixMCLOnly]
                            Return value of command : -532459699
regards
Wolfgang

Hello Wolfgang,
The command options of ClientUpgradetarget.exe are:
/MUP - Path of MUP file OR folder where MUP file is stored
/COC - Close on completion of upgrade
/SUI - Show UI of the tool
/APP - To choose application to be deployed
                                 if there are multiple applications in
                                 the upgrade package
/LAN - To choose language to be deployed if files and
                     folders related to multiple languages are present
/UTS - To choose specific units contained in the upgrade
For the error you're facing, please check if the MUP file is located under the location C:\Programme\SAP\Mobile\5.00.SP.15\MobileComponentUpgrade\HotFix\MandatoryFix.mup
If 'yes' , then you can also try deploying the MUP manually by double clicking and selecting only the unit 'HotFixMCLOnly'
Thanks,
Rohit

What are the parameters for the processes menu items

Is there anywhere that lists out what the exact parameters of the process menu items are. i.e "Make Louder, Normalize, Hard Limit, Equalize Volume Levels",
For instance when you use "Make Louder" you see the dialog box title change from "Analyzing peeks" to "Applying Hard Limit". What exactly is happening when these processes are being applied? I realize that the Hard limiter is being applied, but with what paramaters and what does "Analyzing peeks" really mean and is there a way to do that by its self and if so what can be learned by the results.
I would also like to know the paramaters for the others as well. It would be helpfull to know, so one could dial up or down the paramaters to achieve a similar result, but with slightly more or less effect.
Regards,
Don T

Nothin?

What are the parameters for the FM

hi can any one help me how to use this FM HR_ECM_GET_NUMBER_OF_MONTHS
Edited by: kopparapu suresh on Jun 16, 2008 11:15 AM

hi see this..
report .
parameters: p_sdate type sy-datum,
            p_edate type sy-datum.
data: l_days type i,
      l_months type i,
      l_years type i.
CALL FUNCTION 'HR_SGPBS_YRS_MTHS_DAYS'
EXPORTING
BEG_DA = p_sdate
END_DA = p_edate
IMPORTING
NO_DAY = l_days
NO_MONTH = l_months
NO_YEAR = l_years .
write:/ 'Days = ', l_days.
write:/ 'Months = ', l_months.
write:/ 'Years = ', l_years.
or see this..
REPORT ZDATEDIFF.
DATA: EDAYS   LIKE VTBBEWE-ATAGE,
      EMONTHS LIKE VTBBEWE-ATAGE,
      EYEARS LIKE VTBBEWE-ATAGE.
PARAMETERS: FROMDATE LIKE VTBBEWE-DBERVON,
            TODATE   LIKE VTBBEWE-DBERBIS DEFAULT SY-DATUM.
call function 'FIMA_DAYS_AND_MONTHS_AND_YEARS'
exporting
    i_date_from          = FROMDATE
    i_date_to            = TODATE
I_FLG_SEPARATE       = ' '
IMPORTING
    E_DAYS               = EDAYS
    E_MONTHS             = EMONTHS
    E_YEARS              = EYEARS.
WRITE:/ 'Difference in Days   ', EDAYS.
WRITE:/ 'Difference in Months ', EMONTHS.
WRITE:/ 'Difference in Years ', EYEARS.
INITIALIZATION.
FROMDATE = SY-DATUM - 60.

What are the different functions used in sap script?

Hi,
What are the different functions used in sap script? What are the parameters used in each Function?
Regards,
Mahesh

he print program is used to print forms. The program retieves the necesary data from datbase tables, defines the order of in which text elements are printed, chooses a form for printing and selects an output device and print options.
Function modules in a printprogram:
When you print a form you must used the staments OPEN_FORM and CLOSE_FORM. To combine forms into a single spool request use START_FORM and END_FORM.
To print textelements in a form use WRITE_FORM. The order in which the textelements are printed, is determined by the order of the WRITE_FORM statements. Note: for printing lines in the body, you can also use the WRITE_FORM_LINES function module.
To transfer control command to a form use CONTROL_FORM.
Structure of a print program
Read data
Tables: xxx.
SELECT *
FROM xxx.
Open form printing - Must be called before working with any of the other form function modules.
Must be ended with function module CLOSE FORM
call function 'OPEN_FORM'.....
To begin several indentical forms containing different data within a single spool request, begin each form using START_FORM, and end it using END_FORM
call funtion 'START_FORM'.....
Write text elements to a window of the form
call function 'WRITE_FORM'.....
Ends spool request started with START_FORM
call funtion 'END_FORM'.....
Closes form printing
call function 'CLOSE_FORM'...
OPEN_FORM function
Syntax:
CALL FUNCTION 'OPEN_FORM'
EXPORTING
APPLICATION                       = 'TX'
ARCHIVE_INDEX                     =
ARCHIVE_PARAMS                    =
DEVICE                            = 'PRINTER'
DIALOG                            = 'X'
FORM                              = ' '
LANGUAGE                          = SY-LANGU
OPTIONS                           =
MAIL_SENDER                       =
MAIL_RECIPIENT                    =
MAIL_APPL_OBJECT                  =
RAW_DATA_INTERFACE                = '*'
IMPORTING
LANGUAGE                          =
NEW_ARCHIVE_PARAMS                =
RESULT                            =
EXCEPTIONS
CANCELED                          = 1
DEVICE                            = 2
FORM                              = 3
OPTIONS                           = 4
UNCLOSED                          = 5
MAIL_OPTIONS                      = 6
ARCHIVE_ERROR                     = 7
INVALID_FAX_NUMBER                = 8
MORE_PARAMS_NEEDED_IN_BATCH       = 9
SPOOL_ERROR                       = 10
OTHERS                            = 11
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Some important parameters:
FORM      Name of the form
DEVICE
PRINTER : Print output using spool
TELEFAX: Fax output
SCREEN: Output to screen
OPTIONS      Used to control attrubutes for printing or faxing (Number of copies, immediate output....
The input for the parameter is structure ITCPO.
CLOSE_FORM function
CALL FUNCTION 'CLOSE_FORM'
IMPORTING
RESULT                         =
RDI_RESULT                     =
TABLES
OTFDATA                        =
EXCEPTIONS
UNOPENED                       = 1
BAD_PAGEFORMAT_FOR_PRINT       = 2
SEND_ERROR                     = 3
SPOOL_ERROR                    = 4
OTHERS                         = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Paramerters:
RESULT      Returns status information and print/fax parameters after the form has been printed. RESULT is of structure ITCPP.
WRITE_FORM function
CALL FUNCTION 'WRITE_FORM'
EXPORTING
ELEMENT                        = ' '
FUNCTION                       = 'SET'
TYPE                           = 'BODY'
WINDOW                         = 'MAIN'
IMPORTING
PENDING_LINES                  =
EXCEPTIONS
ELEMENT                        = 1
FUNCTION                       = 2
TYPE                           = 3
UNOPENED                       = 4
UNSTARTED                      = 5
WINDOW                         = 6
BAD_PAGEFORMAT_FOR_PRINT       = 7
SPOOL_ERROR                    = 8
OTHERS                         = 9
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Some important parameters:
ELEMENT      Specifies which textelement is printed
WINDOW      Specifies which window is printed
TYPE      Specifies the output area of the main window. This can be:
TOP - Used for headers
BODY
BOTTOM - Used for footers
FUNCTION      Specifies whether text is to be appended, replaced or added
Example of how to use the WRITE_FORM function module together with a script.
Form layout of the MAIN window
/E INTRODUCTION
Dear Customer
/E ITEM_HEADER
IH Carrier, Departure
/E ITEM_LINE
IL &SBOOK-CARRID&, &SPFLI-DEPTIME&
/E CLOSING_REMARK
The print program
Writing INTRODUCTION
CALL FUNCTION 'WRITE_FORM'
     EXPORTING
          ELEMENT                  = 'INTRODUCTION'
          FUNCTION                 = 'SET'
          TYPE                     = 'BODY'
          WINDOW                   = 'MAIN'
    EXCEPTIONS
         OTHERS                   = 8
Writing ITEM_HEADER
CALL FUNCTION 'WRITE_FORM'
     EXPORTING
          ELEMENT                  = 'ITEM_HEADER'
          FUNCTION                 = 'SET'
          TYPE                     = 'BODY'
          WINDOW                   = 'MAIN'
    EXCEPTIONS
         OTHERS                   = 8
Set ITEM_HEADER into TOP area of main window for subsequent pages
CALL FUNCTION 'WRITE_FORM'
     EXPORTING
          ELEMENT                  = 'ITEM_HEADER'
          FUNCTION                 = 'SET'
          TYPE                     = 'TOP'
          WINDOW                   = 'MAIN'
    EXCEPTIONS
         OTHERS                   = 8
Write ITEM_LINE
LOOP AT .....
   CALL FUNCTION 'WRITE_FORM'
        EXPORTING
             ELEMENT               = 'ITEM_LINE'
             FUNCTION              = 'SET'
             TYPE                  = 'BODY'
             WINDOW                = 'MAIN'
       EXCEPTIONS
            OTHERS                 = 8.
ENDLOOP.
Delete ITEM_HEADER from TOP area of main window
CALL FUNCTION 'WRITE_FORM'
     EXPORTING
          ELEMENT                  = 'ITEM_HEADER'
          FUNCTION                 = 'DELETE'
          TYPE                     = 'TOP'
          WINDOW                   = 'MAIN'
    EXCEPTIONS
         OTHERS                    = 8
Print CLOSING_REMARK
CALL FUNCTION 'WRITE_FORM'
     EXPORTING
          ELEMENT                  = 'CLOSING_REMARK'
          FUNCTION                 = 'SET'
          TYPE                          = 'BODY'
          WINDOW                   = 'MAIN'
    EXCEPTIONS
         OTHERS                    = 8
START_FORM function
CALL FUNCTION 'START_FORM'
EXPORTING
ARCHIVE_INDEX          =
FORM                   = ' '
LANGUAGE               = ' '
STARTPAGE              = ' '
PROGRAM                = ' '
MAIL_APPL_OBJECT       =
IMPORTING
LANGUAGE               =
EXCEPTIONS
FORM                   = 1
FORMAT                 = 2
UNENDED                = 3
UNOPENED               = 4
UNUSED                 = 5
SPOOL_ERROR            = 6
OTHERS                 = 7
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
END_FORM function
CALL FUNCTION 'END_FORM'
IMPORTING
RESULT                         =
EXCEPTIONS
UNOPENED                       = 1
BAD_PAGEFORMAT_FOR_PRINT       = 2
SPOOL_ERROR                    = 3
OTHERS                         = 4
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CONTROL_FORM function
The CONTROL_FORM function module alows you to create SapScript control statements from within an APAB program.
Syntax:
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
    command         =
EXCEPTIONS
UNOPENED        = 1
UNSTARTED       = 2
OTHERS          = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Example:
Protecting the text element ITEM_LINE
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
    COMMAND = 'PROTECT'.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
    TEXELEMENT = 'ITEM_LINE'.
CALL FUNCTION 'CONTROL_FORM'
EXPORTING
    COMMAND = 'ENDPROTECT'.

What are the parameters of run_product?

Similar Messages

Maybe you are looking for