Addition of variant in MB51

hi all,
as we know we can derive the data for material movement with T code mb51 tcode.
we have serial number profile assign to some materials.
now i want which serial number assign to material w r t mvt type in MB51 tcode only. so can i add a column in MB51 column which can show me the serial number ?
Thanks in advance.

Dear Sing,
Develop your own Z program by copying the MB51 program and then you can add another field to include the Serial Number columns. Take the help of you ABAPER, it should be very easy development.
Thanks
Murtuza

Similar Messages

Variant Creation in Transaction MB51

Dear All,
I faced one Issue during creation of Variant in MB51 Transaction is like Below.
In Posting date field From to To in that i required from date is fixed and To date is Dynamic (Current date - 3)
So how can i set this?
In Variants we can give dynamic date calculator to calculate date as we required.
Does there is a option to add more selection option (ie if I have to add a Fixed date , Current date -3).
Where I can do this?
Regards,
Murari Shah

Hi,
> In Posting date field From to To in that i required from date is fixed and To date is Dynamic (Current date - 3)
Follow as following,enter your From date & Select Save as Variant, New window appears, there enter your Variant Name & Short Text,
Now Select Posting date from the Selection Screen-Field Name, there go to 3rd last column for "Selection variable" in posting date line & press F4 over there & select "D: Dynamic date calculation",
Now go to last column " Name of Variable" press F4, new screen appears, in that scroll down & double click on "Date - xxx, Date + yyy (work days)" or also you can use "Current date - xxx,current date + yyy", New window opens, here enter the values in numbers w.r.t. date,
If you want to Consider today's date always then put 0 in the first field or you can put addition of no. off days as per your choice, then in second field put 3(system will add 3 days from today date),
Then in field " Work days are determined according to factory calndr." enter "IN", press enter & save your variant, then execute again MB51 after coming out of all screens & check whether you requirement is achieved.

MB51 variant deleted

Hi Gurus,
Please advice how variants in MB51 are deleted. Yesterday we used the variants but today no variant was availble. is there a ways to recover those variants? How were they deleted?
Thank you.

Hi
Variants cannot be retreived if they are deleted, you need to maintain the varaints again for the transaction code.
Thanks & Regards
Kishore

Re:variants in processchains

Hi Gurus,
can anyone explain me in detail what is really a variant in process chains with any example if possible.
Thanks

Hi Apo,
Creating Process Chains
Prerequisites
If you want to include a load process in the process chain, you need to have already created an InfoPackage.
You cannot load flat file data from a client workstation in the background. For this reason, you have stored your data on an application server.
Creating Process Chains
You have the option of creating a process chain in the process chain maintenance screen directly or by using a maintenance dialog for a process:
Creating a Process Chain Directly in the Process Chain Maintenance Screen
You are in the BW Administrator Workbench.
1. Click on the Process Chain Maintenance icon in the AWB toolbar.
The Process Chain Selection dialog window appears.
2. Choose Create.
3. Enter the technical name and a description of the chain, and confirm your entry.
The Add Start Process dialog window appears.
4. Create a variant for a start process.
1. a. On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
2. b. If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
3. c. Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
5. Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
1. Choose the Process Chain Maintenance pushbutton and create a process variant.
2. Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
3. Confirm your entries.
The Add Start Process dialog window appears.
4. Create a variant for a start process.
1. a. On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
2. b. If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
3. c. Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
5. Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
6. When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process Function Information
Maintain Variants With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message You can also send messages to an application process of the chain, depending on the success or failure of the process.
1. 1. From the context menu of a process, create an additional process variant of the Send Message type.
2. 2. If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3. 3. You arrive at a window, in which you can select an existing process variant or create a new one.
4. 4. If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5. 5. Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process You use this function to remove a process from a process chain.
Manage Data Target You use this function in connection with the following types of process variants
1. constructing indexes
2. deleting indexes
3. constructing database statistics
4. rolling up filled aggregates
5. compressing InfoCubes
6. activating ODS object data
to call up the administration for each of the data targets.
7. Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
8. If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
9. Under Attributes ®Display Components assign a display component to the process chain.
10. Maintain additional process chain attributes if necessary.
11. Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
12. Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.
Regards,
Yokesh.

MB51 runtime error

Hello Gurus,
I am getting runtime error for a particular variant in MB51 report which gives 101 material document list for a particular dates.
we did not had any issue earlier for same variant.
helpfull answers will be rewarded
regards
suresh

everyday you get more material documents in the tables, means the runtime increases with each new document.
You are probably exceeding the limit define as maximum runtime of a transaction.
You better schedule the report as background job.
A tipp, fill the selection screen from top to down. If you leave the material number empty, then it searches thru the entire table. The table has as well material documents for receipts done without material number. So you can reduce the runtime already by entering 1 to 999999999999.. in the material number field if you are searching only 101 movements to stock items.

SAP DELIVERED COSTING VARIANT

Is there an SAP delivered costing variant, valuation variant and costing type for group valuation and profit center valuation??
Is it necessary to have additional costing variants for group valuation and profit centre valuations if the busibess decideds to activate multiple valuation approaches??

Is there some way I could see what the settings and config would be. Ofcourse no two organization are same and the settings would be different but one can atleast get a general idea and logic.
I would like to know what the settings would be for costing variants valuation variants and the valuation type, both for group valuation and profit center valuation.
Thanks

Variants for SAP reports

Hi All,
In my client Shop Floor Users are daily using the transaction COOIS to know the order information. We created a variant for that, even though every time users has to select the variant from the list to execute the transaction.
Working Environment: ECC 5.0
Question: 1
Is there can we set this variant globally i.e., when ever (who ever) getting in to the screen will automatically executed with the defined variant value.
Additional info: Variant values have to be populated in the selection screen of the transaction COOIS automatically, who ever enter in to the screen.
Question: 2
Is there can I define variant specific to the user i.e., when ever the corresponding user login in to system with the specific user id and get in to the transaction will automatically executed with the user specific variant value.
Additional info: Variant values have to be populated in the selection screen of the transaction COOIS automatically, when the specific users enter in to the screen.
Please guide me the step by step procedure to the above (Question 1 & Question 2)
Thanks in Advance.

Variants can be of 2 types.
1: Global: This means it can be used by anyone whoever logs in
2: User Specific: This means it can be user specific and other users may not see it.
Create user specific variants for individual users.

Write data to table

hallow i have table yhr_1
and i wont to write data to her
how can i do that?
just from progran or other option.
regards

Use insert command:
Inserting into the Database
Variants:
1. INSERT INTO dbtab VALUES wa. oder
INSERT INTO (dbtabname) VALUES wa. oder
INSERT dbtab FROM wa. oder
INSERT (dbtabname) FROM wa.
2. INSERT dbtab FROM TABLE itab. oder
INSERT (dbtabname) FROM TABLE itab.
3. INSERT dbtab. oder
INSERT *dbtab.
Effect
Inserts new lines in a database table (see relational database). You can specify the name of the database table either in the program itself in the form dbtab or at runtime as the contents of the variable dbtabname. In both cases, the database table must be defined in the ABAP Dictionary. By default, data is only inserted in the current client. Data can only be inserted using a view if the view refers to a single table and was defined in the ABAP Dictionary with the maintenance status "No restriction".
INSERT belongs to the Open SQL command set.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs.See Open SQL and Unicode.
Notes
You cannot insert a line if a line with the same primary key already exists or if a UNIQUE index already has a line with identical key field values (with regard to this UNIQUE index).
When inserting lines using a view, all fields of the
database table that are not in the view are set to their initial value
(see TABLES) - if they were defined with NOT NULL in the ABAP Dictionary. Otherwise they are set to NULL.
Authorization checks (see The SAP Authorization Concept) are not supported by the INSERT statement. You must include these in the program yourself.
Lines specified with the INSERT command are not finally added to the database table until after a database commit (see Logical Unit of Work (LUW)). Prior to this, you can cancel any changes to the database with a database rollback (see Programming Transactions).
In the dialog system, you cannot rely on the locking mechanism used by the database system (see Database Locking) to synchronize simultaneous access to the same database by several users. Therefore, it is often necessary to use SAP's locking mechanism (see SAP Locking).
Variant 1
INSERT INTO dbtab VALUES wa. or
INSERT INTO (dbtabname) VALUES wa. or
INSERT dbtab FROM wa. or
INSERT (dbtabname) FROM wa.
Extras:
1. ... CLIENT SPECIFIED
2. ... CONNECTION con
Effect
Inserts one line into a database table. The line to be inserted is taken from the work area wa and the data read from left to right according to the line structure of the database table dbtab. Here, the structure of wa is not taken into account. For this reason, the work area wa must be at least as wide (see DATA) as the line structure of dbtab, and the alignment of the work area wa must correspond to the alignment of the line structure. Otherwise, a runtime error occurs.
If the database table dbtab or the work area wa contain strings, wa must be compatible with the line structure of dbtab.
When the command has been executed, the system field SY-DBCNT contains the number of inserted lines (0 or 1).
The Return Code is set as follows:
SY-SUBRC = 0:
Line was successfully inserted.
SY-SUBRC = 4:
Line could not be inserted since a line with the same key already exists.
Example
Insert the customer Robinson in the current client:
DATA: wa TYPE scustom.
wa-id = '12400177'.
wa-name = 'Robinson'.
wa-postcode = '69542'.
wa-city = 'Heidelberg'.
wa-custtype = 'P'.
wa-discount = '003'.
wa-telephone = '06201/44889'.
INSERT INTO scustom VALUES wa.
Addition 1
... CLIENT SPECIFIED
Effect
Automatic client handling is switched off. This allows
you to process data on a cross-client basis for client-specific tables. The client field is then treated like a normal table field which the program must fill with values in the work area wa.
The addition CLIENT SPECIFIED must be specified directly after the name of the database table.
Example
Insert the customer Robinson in client 2:
DATA: wa TYPE scustom.
wa-mandt = '002'.
wa-id = '12400177'.
wa-name = 'Robinson'.
wa-postcode = '69542'.
wa-city = 'Heidelberg'.
wa-custtype = 'P'.
wa-discount = '003'.
wa-telephone = '06201/44889'.
INSERT scustom CLIENT SPECIFIED FROM wa.
Addition 2
... CONNECTION con
Effect
The Open SQL command is not executed on the
standard database, but on the secondary database connection specified with con. con is the name of the databse connection as it was specified in the table DBCON in the column CON_NAME. The database connection con can also be specified dynamically in the form (source_text), where the field source_text contains the name of the database connection and must be type C or STRING. The CONNECTION con addition must be specified directly after the name of the database table or after the CLIENT SPECIFIED addition.
Variant 2
INSERT dbtab FROM TABLE itab. oder
INSERT (dbtabname) FROM TABLE itab.
Extras:
1. ... CLIENT SPECIFIED
2. ... ACCEPTING DUPLICATE KEYS
3. ... CONNECTION con
Effect
Mass insert: All lines of the internal table itab are inserted in one single operation. The lines of itab must fulfill the same conditions as the work area wa in variant 1.
When the command has been executed, the system field SY-DBCNT contains the number of inserted lines.
The Return Code is set as follows:
SY-SUBRC = 0:
All lines successfully inserted. Any other result causes a runtime error.
Note
If the internal table itab is empty, SY-SUBRC and SY-DBCNT are set to 0 after the call.
Addition 1
... CLIENT SPECIFIED
Effect
As with variant 1.
Addition 2
... ACCEPTING DUPLICATE KEYS
Effect
If a line cannot be inserted, the system does not
terminate with a runtime error but only sets the return value SY-SUBRC to 4. All other lines are inserted after the command is executed.
Addition 3
... CONNECTION con
Effect
As with variant 1.
Variant 3
INSERT dbtab. or
INSERT *dbtab.
Extras:
1. ... CLIENT SPECIFIED
2. ... CONNECTION con
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See Cannot Use Short Forms and Cannot Use * Work Areas.
Note
This variant is obsolete.
Effect
These are the SAP-specific short forms of variant 1. They have the same effect as variant 1, but the work area is not specified explicitly. Instead, the system implicitly uses the table work area dbtab or *dbtab declared using a TABLES statement.
INSERT dbtab. bzw.
INSERT *dbtab.
is equivalent to
INSERT INTO dbtab VALUES dbtab. or
INSERT INTO dbtab VALUES *dbtab.
When the command has been executed, the system field SY-DBCNT contains the number of lines inserted (0 or 1).
The Return Code is set as follows:
SY-SUBRC = 0:
Line successfully inserted.
SY-SUBRC = 4:
Line could not be inserted, since a line with the same key already exists.
Example
Add a line to a database table:
TABLES sairport.
sairport-id = 'NEW'.
sairport-name = 'NEWPORT APT'.
INSERT sairport.
Notes
You should always use variant 1 where you specify an explicit work area wa instead of using the implicit TABLES work area.
If a work area is not explicitly specified, the values for the line to be inserted are taken from the table work area dbtab if the statement is in a FORM or FUNCTION where the table work area is stored in a formal parameter or local variable of the same name.
Addition 1
... CLIENT SPECIFIED
Effect
As with variant 1.
Addition 2
... CONNECTION con
Effect
As with variant 1.

How to create messages in process chains?

Dear Gurus,
I want to use the alert system in the process chains. like when one process fails i have to receive the message on my mail or as an SMS on my mobile.
I tried the same thing with one of my process chain. When i right click one of my process in my process chain i will get the create message option. But my problem is i dont know how to use that option. If u have any solutions or any material please try to send me to the following ID [email protected]
Thanks in advance
Mohan Kumar

Hi,
You can also send messages to an application process of the chain, depending on the success or failure of the process.
1. From the context menu of a process, create an additional process variant of the Send Message type.
2. If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3. You arrive at a window, in which you can select an existing process variant or create a new one.
4. If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5. Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Hareesh

Calling ALV report in BAPI

Hi All There ,
I am calling ALV report in my bapi but it is not gettin called it is not giving screen of parameter selection derectly selectin all parameter
coding is as below
points assured.
Data: MTAB_REPORT_HTML type standard table of W3HTML WITH HEADER LINE.
Submit ZSDRUSHORDERSRPT with SELECTION-TABLE SELTAB
        exporting list to Memory and return.
CALL FUNCTION 'LIST_FROM_MEMORY'
TABLES
    listobject = list_tab
EXCEPTIONS
    not_found = 1
    OTHERS     = 2.
CALL FUNCTION 'WWW_HTML_FROM_LISTOBJECT'
EXPORTING
   TEMPLATE_NAME       = 'WEBREPORTING_REPORT'
CHARSET             = 'UTF8'
TABLES
    html                = MTAB_REPORT_HTML
    listobject          = list_tab.
FREE MEMORY.
CLEAR LIST_TAB[].
loop at MTAB_REPORT_HTML.
concatenate htmlstring
             MTAB_REPORT_HTML-LINE into htmlstring.
endloop.

No, It is not specific to ALV. If you can give the example of that SUBMIT then it can be analyzed. It can be for other additions that is used in the submit statement.
Like:
1. ... USING SELECTION-SCREEN dynnr
2. ... VIA SELECTION-SCREEN
Effect
The addition USING SELECTION-SCREEN specifies the selection screen, VIA SELECTION-SCREEN specifies whether it is displayed. The additions selscreen_parameters provide values for the parameters, selection criteria, and the free selection of the called selection screen.
The values are transferred to the selection screen between the events INITIALIZATION and AT SELECTION-SCREEN OUTPUT The following hierarchy applies for transferring values:
1.     First, the variant of the addition USING SELECTION-SET is transferred, which sets all parameters and selection criteria to the values of the variant. The values previously set in the called program are overwritten.
2.     The values of the table of the addition WITH SELECTION-TABLE are then transferred. All parameters and selection criteria specified there are overwritten accordingly.
3.     Finally, the values of the additions WITH sel value are transferred. All parameters and selection criteria are overwritten accordingly. If the addition WITH sel value is used more than once for the same parameter, this is overwritten with the last specified value. If the addition WITH sel value is used more than once for the same selection criterion, a selection table with the corresponding number of lines is transferred.
Providing values for free selections is independent of this hierarchy.
Notes
     The options for parameter transfer enable a selection screen to be viewed as a parameter interface of an executable program. This applies particularly for background selection screen processing and for parameters and selection criteria that are defined without screen elements using the addition NO-DISPLAY
     When transferring data, note that any adjustments made to the screen format, such as abbreviations or the execution of conversion routines, are not executed for fields for which there are no screen elements on the selection screen. This applies for all parameters and selection criteria defined with NO DISPLAY. It also applies for all lines of a selection table with the exception of the first line.
     The additions selscreen_parameters only work the first time the called program is executed. If a selection screen is displayed in the called program, the runtime environment calls the program again after it is finished, thereby replacing the values specified in selscreen_parameters with the previous input values.
Addition 1
... USING SELECTION-SCREEN dynnr
Effect
This addition specifies which selection screen is called. dynnr is a data object that must contain the screen number of a selection screen defined in the called program when the SUBMIT statement is called.
     If the addition USING SELECTION-SCREEN is omitted or the screen number 1000 is entered, the standard selection screen is called. If no standard selection screen is defined in the called program, no selection screen is called.
     If a screen number that is not 1000 is entered in the addition USING SELECTION-SCREEN, the corresponding independent selection screen is called. If no selection screen with this screen number is defined in the called program, this leads to an untreatable exception.
Addition 2
... VIA SELECTION-SCREEN
Effect
If this addition is specified, the selection screen is displayed on the screen. Otherwise, background selection screen processing takes place. In background selection screen processing, the selection screen events are triggered without the selection screen being displayed.
SUBMIT - selscreen_parameters
Syntax
... [USING SELECTION-SET variant]
    [USING SELECTION-SETS OF PROGRAM prog]
    [WITH SELECTION-TABLE rspar]
    [WITH expr_syntax1 WITH expr_syntax2 ...]
    [WITH FREE SELECTIONS texpr] ... .
Extras:
1. ... USING SELECTION-SET variant
2. ... USING SELECTION-SETS OF PROGRAM prog
3. ... WITH SELECTION-TABLE rspar
4. ... WITH expr_syntax1 WITH expr_syntax2 ...
5. ... WITH FREE SELECTIONS texpr
Effect
USING-SELECTION-SET supplies all the selection screen components by means of a Variant variant. If you specify USING-SELECTION-SETS OF PROGRAM, you can use a variant from a different program; if you specify WITH SELECTION-TABLE, values for several selection screen components are transferred as the content of an internal table rspar; WITH expr_syntax supplies individual selection screen components with values. The addition WITH FREE SELECTIONS allows you to transfer free selections to the selection screen for alogical database.
Addition 1
... USING SELECTION-SET variant
Effect
If you specify this edition, the parameters and selection criteria for the selection screen are supplied with values from a variant. For variant, you must specify a character-like data object that contains the name of a variant for the program accessed when the statement is executed. If the variant does not exist, the system sends an error message. If the variant belongs to a different selection screen, it is ignored.
Note
You can create and manage variants for every program in which selection screens are defined, either in the ABAP Workbench or during execution of the program by choosing Goto - Variants on a selection screen.
Addition 2
... USING SELECTION-SETS OF PROGRAM prog
Effect
If you specify this addition, the variants of the program prog are used in the program accessed. For prog, you must specify a character-like data object that contains the name of a program when the statement is executed. The addition has the following effect:
     If a variant variant is specified with USING SELECTION-SET, the system searches for this variant in the program prog.
     If the selection screen is displayed with VIA SELECTION-SCREEN, all the functions that can be accessed by means of the menu path Goto - Variants affect the variants of the program prog. However, these functions are only active if prog is an executable program.
Note
The program prog should contain a selection screen that has the same parameters and selection criteria as the selection screen used in the program accessed.
Addition 3
... WITH SELECTION-TABLE rspar
Effect
If you specify this addition, parameters and selection criteria on the selection screen are supplied from an internal table rspar. You must specify an internal table with the row type RSPARAMS for rspar. The structured data type RSPARAMS is defined in the ABAP Dictionary and has the following components, all of which are data type CHAR:
     SELNAME (length 8),
     KIND (length 1),
     SIGN (length 1),
     OPTION (length 2),
     LOW (length 45),
     HIGH (length 45).
To supply parameters and selection criteria for the selection screen with specific values, the lines in the internal table rspar must contain the following values:
     SELNAME must contain the name of a parameter or selection criterion for the selection screen in block capitals
     KIND must contain the type of selection screen component (P for parameters, S for selection criteria)
     SIGN, OPTION, LOW, and HIGH must contain the values specified for the selection table columns that have the same names as the selection criteria; in the case of parameters, the value must be specified in LOW and all other components are ignored.
If the name of a selection criterion is repeated in rspar, this defines a selection table containing several lines and passes it on to the selection criterion. If parameter names occur several times, the last value is passed on to the parameter.
The contents of the parameters or selection tables for the current program can be entered in the table by the function module RS_REFRESH_FROM_SELECTOPTIONS.
Notes
In contrast to selection tables, the data types of the components LOW and HIGH in table rspar are always of type CHAR and are converted to the type of the parameter or selection criterion during transfer, if necessary.
     When entering values, you must ensure that these are entered in the internal format of the ABAP values, and not in the output format of the screen display.
Addition 4
... WITH expr_syntax1 WITH expr_syntax2 ...
Effect
This addition supplies values to individual parameters or selection criteria for the selection screen. Parameters are supplied with single values and selection criteria with selection tables that overwrite values already specified in the program accessed. The selection table to be transferred is compiled from all the expr_syntax additions that address the same selection criterion sel. You can specify the following statements for expr_syntax, where you have to specify the name of a parameter or a selection criterion directly for sel:
     sel {EQ|NE|CP|NP|GT|GE|LT|LE} dobj [SIGN sign]
Transfer of a single value.
The operators before dobj correspond to the values specified for column OPTION for selection tables. For dobj, you must specify a data object whose data type can be converted to the data type of the selection screen component sel. For sign, you can specify a character-like field that must contain 'I' or 'E'. The standard value is 'I'.
If sel is a selection criterion, the system appends a line in the selection table to be transferred, placing the operator in column OPTION, the content of dobj in column LOW, and the content of sign in column SIGN.
If sel is a parameter, it is set to the value of dobj in the program accessed. The operator and the value of sign are not taken into account.
     sel [NOT] BETWEEN dobj1 AND dobj2 [SIGN sign]
Transfer of an interval.
In this case, sel must be a selection criterion. For dobj, you must specify data objects whose data type can be converted to that of the columns LOW and HIGH for the selection criterion sel. For sign, you can specify a character-like field that must contain 'I' or 'E'. The standard value is 'I'.
A line is appended in the selection table to be transferred. If NOT is specified, the value 'NB' is placed in column OPTION; otherwise, the value entered is 'BT'. The content of the data objects dobj and sign is placed in the columns LOW, HIGH, and SIGN.
     sel IN rtab
Transfer of a ranges table.
In this case, sel must be a selection criterion. For rtab, you must specify an internal table that has the same structure as the selection table for selection criterion sel. A table of this type can be created using the addition RANGE OF to the statements TYPES and DATA.
The lines in table rtab are appended to the selection table to be transferred.
You can specify the addition expr_syntax more than once, and you can also specify the same selection screen component more than once.
Notes:
     = or INCL can also be used instead of the operator EQ.
     When entering values, you must ensure that these have the internal format of the ABAP values, and not the output format of the screen display.
Example
The program report1 has a stand-alone selection screen with the screen number 1100. In the program report2, an internal table with row type RSPARAMS and a ranges table are filled for this selection screen. These are transferred at SUBMIT together with a single condition.
Program accessed
REPORT report1.
DATA text TYPE c LENGTH 10.
SELECTION-SCREEN BEGIN OF SCREEN 1100.
SELECT-OPTIONS: selcrit1 FOR text,
                  selcrit2 FOR text.
SELECTION-SCREEN END OF SCREEN 1100.
Calling program
REPORT report2.
DATA: text       TYPE c LENGTH 10,
      rspar_tab TYPE TABLE OF rsparams,
      rspar_line LIKE LINE OF rspar_tab,
      range_tab LIKE RANGE OF text,
      range_line LIKE LINE OF range_tab.
rspar_line-selname = 'SELCRIT1'.
rspar_line-kind    = 'S'.
rspar_line-sign    = 'I'.
rspar_line-option = 'EQ'.
rspar_line-low     = 'ABAP'.
APPEND rspar_line TO rspar_tab.
range_line-sign   = 'E'.
range_line-option = 'EQ'.
range_line-low    = 'H'.
APPEND range_line TO range_tab.
range_line-sign   = 'E'.
range_line-option = 'EQ'.
range_line-low    = 'K'.
APPEND range_line TO range_tab.
SUBMIT report1 USING SELECTION-SCREEN '1100'
               WITH SELECTION-TABLE rspar_tab
               WITH selcrit2 BETWEEN 'H' AND 'K'
               WITH selcrit2 IN range_tab
               AND RETURN.
Result
After report1 has been accessed by report2, the selection tables for the selection criteria selcrit1 and selcrit2 in the program accessed contain the following entries:
Addition 5
... WITH FREE SELECTIONS texpr
Effect
This addition supplies values to the dynamic selections for the selection screen for a logical database. The program accessed must be linked to a logical database that supports dynamic selections. texpr must be an internal table of the type RSDS_TEXPR from type group RSDS.
In texpr, the selections for the dynamic selections are specified in an internal format (Reverse Polish Notation). You can use function modules FREE_SELECTIONS_INIT, FREE_SELECTIONS_DIALOG, and FREE_SELECTIONS_RANGE_2_EX from the function group SSEL to fill texpr in the calling program. While the first two function modules execute a user dialog, you can transfer ranges tables to FREE_SELECTIONS_RANGE_2_EX for each node in the dynamic selection in an internal table of the type RSDS_TRANGE. These are then converted to a table of the row type RSDS_TEXPR. If the calling program contains a selection screen with the same dynamic selections, you can transfer its content beforehand to a table of the type RSDS_TRANGE using the function module RS_REFRESH_FROM_DYNAMICAL_SEL.
The lines in the internal table type RSDS_TRANGE contain a flat component TABLENAME for each node and a table-like component FRANGE_T of the type RSDS_FRANGE_T for the fields in the node. The lines in RSDS_FRANGE_T contain a flat component FIELDNAME for each field and a table-like component SELOPT_T of the row type RSDSSELOPT from the ABAP Dictionary. RSDSSELOPT contains the four components SIGN, OPTION, LOW, and HIGH and can include the ranges table.
Example
Program report1 is linked to the logical database F1S, which supports dynamic selections for the node SPFLI. Program report2 enters conditions in a nested internal table of the type rsds_trange with selection conditions for field CONNID in node SPFLI; this is then converted to a table of the type rsds_texpr, which is transferred at SUBMIT.
Program accessed
REPORT report1.
NODES: spfli, sflight, sbook.
Calling program
REPORT report2.
TYPE-POOLS rsds.
DATA: trange TYPE rsds_trange,
      trange_line
        LIKE LINE OF trange,
      trange_frange_t_line
        LIKE LINE OF trange_line-frange_t,
      trange_frange_t_selopt_t_line
        LIKE LINE OF trange_frange_t_line-selopt_t,
      texpr TYPE rsds_texpr.
trange_line-tablename = 'SPFLI'.
trange_frange_t_line-fieldname = 'CONNID'.
trange_frange_t_selopt_t_line-sign   = 'I'.
trange_frange_t_selopt_t_line-option = 'BT'.
trange_frange_t_selopt_t_line-low    = '0200'.
trange_frange_t_selopt_t_line-high   = '0800'.
APPEND trange_frange_t_selopt_t_line
TO trange_frange_t_line-selopt_t.
trange_frange_t_selopt_t_line-sign   = 'I'.
trange_frange_t_selopt_t_line-option = 'NE'.
trange_frange_t_selopt_t_line-low    = '0400'.
APPEND trange_frange_t_selopt_t_line
TO trange_frange_t_line-selopt_t.
APPEND trange_frange_t_line TO trange_line-frange_t.
APPEND trange_line TO trange.
CALL FUNCTION 'FREE_SELECTIONS_RANGE_2_EX'
EXPORTING
    field_ranges = trange
IMPORTING
    expressions = texpr.
SUBMIT report1 VIA SELECTION-SCREEN
               WITH FREE SELECTIONS texpr.

What are process types in process chain

hi any one tell me what are process types in Process chains

Hi,
In the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
1. Choose the Process Chain Maintenance pushbutton and create a process variant.
2. Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
3. Confirm your entries.
The Add Start Process dialog window appears.
4. Create a variant for a start process.
1. a. On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
2. b. If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
3. c. Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
5. Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
6. When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process Function Information
Maintain Variants With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message You can also send messages to an application process of the chain, depending on the success or failure of the process.
1. 1. From the context menu of a process, create an additional process variant of the Send Message type.
2. 2. If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3. 3. You arrive at a window, in which you can select an existing process variant or create a new one.
4. 4. If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5. 5. Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process You use this function to remove a process from a process chain.
Manage Data Target You use this function in connection with the following types of process variants
1. constructing indexes
2. deleting indexes
3. constructing database statistics
4. rolling up filled aggregates
5. compressing InfoCubes
6. activating ODS object data
to call up the administration for each of the data targets.
7. Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
8. If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
9. Under Attributes ®Display Components assign a display component to the process chain.
10. Maintain additional process chain attributes if necessary.
11. Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
12. Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.
Hope it helps.
Regards,
Amith

Need information about SUBMIT statement

Hi,
 I am submitting program1 in program2 by using SUBMIT keyword.My requirement is want to pass selection screen.
parameters of program2 to program1 without using variant bcz that parameter
values are not constant.
Thanks for ur information in advance..
hari...

hI
SUBMIT - selscreen_parameters
USING-SELECTION-SET supplies all the selection screen components by means of a Variante variant. If you specify USING-SELECTION-SETS OF PROGRAM , you can use a variant from a different program; if you specify WITH SELECTION-TABLE, values for several selection screen components are transferred as the content of an internal table rspar; WITH sel value supplies individual selection screen components sel with values value. The addition WITH FREE SELECTIONS allows you to transfer dynamic selections to the selection screen for a logical database.
... USING SELECTION-SET variant
If you specify this edition, the parameters and selection criteria for the selection screen are supplied with values from a variant. For variant, you must specify a character-like data object that contains the name of a variant for the program accessed when the statement is executed. If the variant does not exist, the system sends an error message. If the variant belongs to a different selection screen, it is ignored.
You can create and manage variants for every program in which selection screens are defined, either in the ABAP Workbench or during execution of the program by choosing Goto - Variants on a selection screen.
... USING SELECTION-SETS OF PROGRAM prog
If you specify this addition, the variants of the program prog are used in the program accessed. For prog, you must specify a character-like data object that contains the name of a program when the statement is executed. The addition has the following effect:
If a variant variant is specified with USING SELECTION-SET, the system searches for this variant in the program prog.
If the selection screen is displayed with VIA SELECTION-SCREEN, all the functions that can be accessed by means of the menu path Goto - Variants affect the variants of the program prog. However, these functions are only active if prog is an executable program.
The program prog should contain a selection screen that has the same parameters and selection criteria as the selection screen used in the program accessed.
... WITH SELECTION-TABLE rspar
If you specify this addition, parameters and selection criteria on the selection screen are supplied from an internal table rspar. You must specify an internal table with the row type RSPARAMS for rspar. The structured data type RSPARAMS is defined in the ABAP Dictionary and has the following components, all of which are data type CHAR:
SELNAME (length 8),
KIND (length 1),
SIGN (length 1),
OPTION (length 2),
LOW (length 45),
HIGH (length 45).
To supply parameters and selection criteria for the selection screen with specific values, the lines in the internal table rspar must contain the following values:
SELNAME must contain the name of a parameter or selection criterion for the selection screen in block capitals
KIND must contain the type of selection screen component (P for parameters, S for selection criteria)
SIGN, OPTION, LOW, and HIGH must contain the values specified for the selection table columns that have the same names as the selection criteria; in the case of parameters, the value must be specified in LOW and all other components are ignored.
If the name of a selection criterion is repeated in rspar, this defines a selection table containing several lines and passes it on to the selection criterion. If parameter names occur several times, the last value is passed on to the parameter.
The contents of the parameters or selection tables for the current program can be entered in the table by the function module RS_REFRESH_FROM_SELECTOPTIONS.
In contrast to selection tables, the data types of the components LOW and HIGH in table rspar are always of type CHAR and are converted to the type of the parameter or selection criterion during transfer, if necessary.
... WITH sel1 value1 WITH sel2 value2 ...
This addition supplies values to individual parameters or selection criteria sel for the selection screen. For sel, you must specify the name of a parameter or selection criterion directly. Parameters are supplied with single values and selection criteria with selection tables that overwrite values already specified in the program accessed. The selection table to be transferred is compiled from all the WITH sel additions that address the same selection criterion sel. You can specify the following statements for value:
{EQ|NE|CP|NP|GT|GE|LT|LE} dobj [SIGN sign]
Transfer of a single value.
The operators before dobj correspond to the values specified for column OPTION for selection tables. For dobj, you must specify a data object whose data type can be converted to the data type of the selection screen component sel. For sign, you can specify a character-like field that must contain 'I' or 'E'. The standard value is 'I'.
If sel is a selection criterion, the system appends a line in the selection table to be transferred, placing the operator in column OPTION, the content of dobj in column LOW, and the content of sign in column SIGN.
If sel is a parameter, it is set to the value of dobj in the program accessed. The operator and the value of sign are not taken into account.
[NOT] BETWEEN dobj1 AND dobj2 [SIGN sign]
Transfer of an interval.
In this case, sel must be a selection criterion. For dobj, you must specify data objects whose data type can be converted to that of the columns LOW and HIGH for the selection criterion sel. For sign, you can specify a character-like field that must contain 'I' or 'E'. The standard value is 'I'.
A line is appended in the selection table to be transferred. If NOT is specified, the value 'NB' is placed in column OPTION; otherwise, the value entered is 'BT'. The content of the data objects dobj and sign is placed in the columns LOW, HIGH, and SIGN.
IN rtab
Transfer of a ranges table.
In this case, sel must be a selection criterion. For rtab, you must specify an internal table that has the same structure as the selection table for selection criterion sel. You can create a table like this using the addition RANGE OF to the statements TYPES and DATA.
The lines in table rtab are appended to the selection table to be transferred.
You can also use = or INCL instead of the operator EQ.
You can specify the addition WITH sel value more than once, and you can also specify the same selection screen component more than once.
Example The program report1 has a stand-alone selection screen with the screen number 1100. In the program report2, an internal table with row type RSPARAMS and a ranges table are filled for this selection screen. These are transferred at SUBMIT together with a single condition.
Program accessed
REPORT report1.
DATA text(10) TYPE c.
SELECTION-SCREEN BEGIN OF SCREEN 1100.
SELECT-OPTIONS: selcrit1 FOR text,
 selcrit2 FOR text.
SELECTION-SCREEN END OF SCREEN 1100.
Calling program
REPORT report2.
DATA: text(10) TYPE c,
 rspar_tab TYPE TABLE OF rsparams,
 rspar_line LIKE LINE OF rspar_tab,
 range_tab LIKE RANGE OF text,
 range_line LIKE LINE OF range_tab.
rspar_line-selname = 'SELCRIT1'.
rspar_line-kind = 'S'.
rspar_line-sign = 'I'.
rspar_line-option = 'EQ'.
rspar_line-low = 'ABAP'.
APPEND rspar_line TO rspar_tab.
range_line-sign = 'E'.
range_line-option = 'EQ'.
range_line-low = 'H'.
APPEND range_line TO range_tab.
range_line-sign = 'E'.
range_line-option = 'EQ'.
range_line-low = 'K'.
APPEND range_line TO range_tab.
SUBMIT report1 USING SELECTION-SCREEN '1100'
 WITH SELECTION-TABLE rspar_tab
 WITH selcrit2 BETWEEN 'H' AND 'K'
 WITH selcrit2 IN range_tab
 AND RETURN.
Result
After report1 has been accessed by report2, the selection tables for the selection criteria selcrit1 and selcrit2 in the program accessed contain the following entries:
SIGN OPTION LOW HIGH
selcrit1 I EQ ABAP
selcrit2 I BT H K
selcrit2 E EQ H
selcrit2 E EQ K
... WITH FREE SELECTIONS texpr
This addition supplies values to the dynamic selections for the selection screen for a logical database. The program accessed must be linked to a logical database that supports dynamic selections. texpr must be an internal table of the type RSDS_TEXPR from type group RSDS.
In texpr, the selections for the dynamic selections are specified in an internal format (stack formula). You can use the function modules FREE_SELECTIONS_INIT, FREE_SELECTIONS_DIALOG, and FREE_SELECTIONS_RANGE_2_EX from the function group SSEL to fill texpr in the calling program. While the first two function modules execute a user dialog, you can transfer ranges tables to FREE_SELECTIONS_RANGE_2_EX for each node in the dynamic selection in an internal table of the type RSDS_TRANGE. These are then converted to a table of the row type RSDS_TEXPR. If the calling program contains a selection screen with the same dynamic selections, you can transfer its content beforehand to a table of the type RSDS_TRANGE using the function module RS_REFRESH_FROM_DYNAMICAL_SEL.
The lines in the internal table type RSDS_TRANGE contain a flat component TABLENAME for each node and a table-like component FRANGE_T of the type RSDS_FRANGE_T for the fields in the node. The lines in RSDS_FRANGE_T contain a flat component FIELDNAME for each field and a table-like component SELOPT_T of the row type RSDSSELOPT from the ABAP Dictionary. RSDSSELOPT contains the four components SIGN, OPTION, LOW, and HIGH and can include the ranges table.
Example Program report1 is linked to the logical database F1S, which supports dynamic selections for the node SPFLI. Program report2 enters conditions in a nested internal table of the type rsds_trange with selection conditions for field CONNID in node SPFLI; this is then converted to a table of the type rsds_texpr, which is transferred at SUBMIT.
Program accessed
REPORT report1.
NODES: spfli, sflight, sbook.
Calling program
REPORT report2.
TYPE-POOLS rsds.
DATA: trange TYPE rsds_trange,
 trange_line
 LIKE LINE OF trange,
 trange_frange_t_line
 LIKE LINE OF trange_line-frange_t,
 trange_frange_t_selopt_t_line
 LIKE LINE OF trange_frange_t_line-selopt_t,
 texpr TYPE rsds_texpr.
trange_line-tablename = 'SPFLI'.
trange_frange_t_line-fieldname = 'CONNID'.
trange_frange_t_selopt_t_line-sign = 'I'.
trange_frange_t_selopt_t_line-option = 'BT'.
trange_frange_t_selopt_t_line-low = '0200'.
trange_frange_t_selopt_t_line-high = '0800'.
APPEND trange_frange_t_selopt_t_line
TO trange_frange_t_line-selopt_t.
trange_frange_t_selopt_t_line-sign = 'I'.
trange_frange_t_selopt_t_line-option = 'NE'.
trange_frange_t_selopt_t_line-low = '0400'.
APPEND trange_frange_t_selopt_t_line
TO trange_frange_t_line-selopt_t.
APPEND trange_frange_t_line TO trange_line-frange_t.
APPEND trange_line TO trange.
CALL FUNCTION 'FREE_SELECTIONS_RANGE_2_EX'
EXPORTING
 field_ranges = trange
IMPORTING
 expressions = texpr.
SUBMIT report1 VIA SELECTION-SCREEN
 WITH FREE SELECTIONS texpr.
SUBMIT - selscreen_options
... [USING SELECTION-SCREEN dynnr]
 [VIA SELECTION-SCREEN]
 [selscreen_parameters] ... .
1. ... USING SELECTION-SCREEN dynnr
2. ... VIA SELECTION-SCREEN
The addition USING SELECTION-SCREEN specifies the selection screen, VIA SELECTION-SCREEN specifies whether it is displayed. The additions selscreen_parameters provide values for the parameters, selection criteria, and the free selection of the called selection screen.
The values are transferred to the selection screen between the events INITIALIZATION and AT SELECTION-SCREEN OUTPUT The following hierarchy applies for transferring values:
First, the variant of the addition USING SELECTION-SET is transferred, which sets all parameters and selection criteria to the values of the variant. The values previously set in the called program are overwritten.
The values are then transferred to the table of the addition WITH SELECTION-TABLE. All parameters and selection criteria specified there are overwritten accordingly.
Finally, the values of the additions WITH sel value are transferred. All parameters and selection criteria are overwritten accordingly. If the addition WITH sel value is used more than once for the same parameter, this is overwritten with the last specified value. If the addition WITH sel value is used more than once for the same selection criterion, a selection table with the corresponding number of lines is transferred.
Providing values for free selections is independent of this hierarchy.
The options for parameter transfer enable a selection screen to be viewed as a parameter interface of an executable program. This applies particularly for background selection screen processing and for parameters and selection criteria that are defined without screen elements using the addition NO-DISPLAY.
The additions selscreen_parameters only work the first time the called program is executed. If a selection screen is displayed in the called program, the runtime environment calls the program again after it is finished, thereby replacing the values specified in selscreen_parameters with the previous input values.
... USING SELECTION-SCREEN dynnr
This addition specifies which selection screen is called. dynnr is a data object that must contain the screen number of a selection screen defined in the called program when the SUBMIT statement is called.
If the addition USING SELECTION-SCREEN is omitted or the screen number 1000 is entered, the standard selection screen is called. If no standard selection screen is defined in the called program, no selection screen is called.
If a screen number that is not 1000 is entered in the addition USING SELECTION-SCREEN, the corresponding independent selection screen is called. If no selection screen with this screen number is defined in the called program, this leads to an untreatable exception.
... VIA SELECTION-SCREEN
If this addition is specified, the selection screen is displayed on the screen. Otherwise, background selection screen processing takes place. In background selection screen processing, the selection screen events are triggered without the selection screen being displayed.
Reward if usefull

Request to let me know replacement command for the Translate command.

Hi,
Code Inspector show that Translate command is obsolete. please let me know the alternate command to be used for the Translate.
Thanks & Regards,
Madhuri.

Hi,
no alternative command for translate , use set language before using the translate command .
Regards
Appana
Check this :
TRANSLATE c TO UPPER/LOWER CASE: Additional Information
Variants:
TRANSLATE c TO UPPER CASE.
TRANSLATE c TO LOWER CASE.
The way in which the TRANSLATE statement works depends on the R/3 logon language. In general, users log on to the R/3 System in the same language as that in which the data they want to edit was created. Logging on in the wrong language causes loss of data, unless a conversion has been defined to deal with a different language environment.
For example, if German umlauts are processed in a Russian environment, the TRANSLATE statement returns a '|' for an 'ö' and a '¶' for a 'Ö'. Such discrepancies occur in particular:
If the wrong language environment has been set inSET LOCALE LANGUAGE
If the user edits data that was not written in the logon language (without using SET LOCALE LANGUAGE)
If, for example, the data to be converted is stored in a structure struwith the language key languand the text field text, then you can work round the problem in one of two ways:
Example
DATA: BEGIN OF stru,
        langu TYPE sy-langu,
        text TYPE sy-xcode,
      END   OF stru.
SET LOCALE LANGUAGE stru-langu.
TRANSLATE stru-text TO UPPER CASE.
SET LOCALE LANGUAGE SPACE.
This solution ensures that every conversion is made in the appropriate language. If struis an internal table, it should be sorted beforehand, to reduce the number of times the system switches between languages. Depending on the table's range, this can substantially reduce processing time, since SET LOCALE LANGUAGE has a long processing time. The runtime is similar to the runtime for SQL statements.
Example
IF stru-langu = sy-langu.
TRANSLATE stru-text TO UPPER CASE.
ELSE.
ENDIF.
The above solution ensures that only texts created in the logon language are edited. If you want, you can bundle all other text lines in another internal table using COLLECT and then convert them using the first solution above.
Note
It is important to reset the language explicitly using SPACE, since SET LOCALE LANGUAGE also changes the system field sy-langu. Note also that a language key may not be meaningful, or a language may not be installed correctly, or you may not be able to edit data from a specific application server. In these special circumstances, the following function modules can be used:
SCP_MIXED_LANGUAGES_1_INIT
SCP_MIXED_LANGUAGES_1_SWITCH
SCP_MIXED_LANGUAGES_1_NORMAL
SCP_MIXED_LANGUAGES_1_FINISH

Details about Process chain

Details about Process chain

Hi Vijay,
            Well the major components of Process chain is mentioned as under:-
A process Chain is a sequence of processes in BI system that executes in the Background.
Commonly Used Process Types
1. Start
2. Execute InfoPackage
3. DTP
4. Attribute Change Run
5. Save Hierarchy
6. Delete Index
7. Generate Index
8. Activate DSO data
9. Update DSO data
10. Complete Deletion of Data Target Content
11. Delete Entire Content of Linked Transactional DSO/ODS
12. Initial Fill of New Aggregates
13. Roll up of Filled Aggregates/BIA indexes
14. Compression of InfoCubes
15. Read PSA and Update Data Target
16. AND
17. OR
18. XOR
If you want to include a load process in the process chain, you need to have already created an InfoPackage.
You cannot load flat file data from a client workstation in the background. For this reason, you have stored your data on an application server.
Creating Process Chains
You have the option of creating a process chain in the process chain maintenance screen directly or by using a maintenance dialog for a process:
Creating a Process Chain Directly in the Process Chain Maintenance Screen
You are in the BW Administrator Workbench.
       1.      Click on the Process Chain Maintenance icon in the AWB toolbar.
The Process Chain Selection dialog window appears.
       2.      Choose Create.
       3.      Enter the technical name and a description of the chain, and confirm your entry.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
       5.      Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
       1.      Choose the Process Chain Maintenance pushbutton and create a process variant.
       2.      Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
       3.      Confirm your entries.
The Add Start Process dialog window appears.
       4.      Create a variant for a start process.
a.       On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
b.       If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
c.       Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
       5.      Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
       6.      When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process
Function Information
Maintain Variants
With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants
You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs
Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs
After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message
You can also send messages to an application process of the chain, depending on the success or failure of the process.
1.       From the context menu of a process, create an additional process variant of the Send Message type.
2.       If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3.       You arrive at a window, in which you can select an existing process variant or create a new one.
4.       If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5.       Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process
You use this function to remove a process from a process chain.
Manage Data Target
You use this function in connection with the following types of process variants
·         constructing indexes
·         deleting indexes
·         constructing database statistics
·         rolling up filled aggregates
·         compressing InfoCubes
·         activating ODS object data
to call up the administration for each of the data targets.
       7.      Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
       8.      If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
       9.      Under Attributes ®Display Components assign a display component to the process chain.
   10.      Maintain additional process chain attributes if necessary.
   11.      Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
   12.      Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.

Append to Ztable

i create a ztable, i 'm running the prog and it insert rows.
when i running the report againg it is not inserting rows, it not making append to the data in the table
this is a new ztable that i create what wrong?

hi
chk the following sap help
Inserting into the Database
Variants:
1. INSERT INTO dbtab      VALUES wa. oder
INSERT INTO (dbtabname) VALUES wa. oder
INSERT dbtab      FROM wa. oder
INSERT (dbtabname) FROM wa.
2. INSERT dbtab      FROM TABLE itab. oder
INSERT (dbtabname) FROM TABLE itab.
3. INSERT dbtab. oder
INSERT *dbtab.
Effect
Inserts new lines in a database table (see relational database). You can specify the name of the database table either in the program itself in the form dbtab or at runtime as the contents of the variable dbtabname. In both cases, the database table must be defined in the ABAP Dictionary. By default, data is only inserted in the current client. Data can only be inserted using a view if the view refers to a single table and was defined in the ABAP Dictionary with the maintenance status "No restriction".
INSERT belongs to the Open SQL command set.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs.See Open SQL and Unicode.
Notes
You cannot insert a line if a line with the same primary key already exists or if a UNIQUE index already has a line with identical key field values (with regard to this UNIQUE index).
When inserting lines using a view, all fields of the
database table that are not in the view are set to their initial value
(see TABLES) - if they were defined with NOT NULL in the ABAP Dictionary. Otherwise they are set to NULL.
Authorization checks (see The SAP Authorization Concept) are not supported by the INSERT statement. You must include these in the program yourself.
Lines specified with the INSERT command are not finally added to the database table until after a database commit (see Logical Unit of Work (LUW)). Prior to this, you can cancel any changes to the database with a database rollback (see Programming Transactions).
In the dialog system, you cannot rely on the locking mechanism used by the database system (see Database Locking) to synchronize simultaneous access to the same database by several users. Therefore, it is often necessary to use SAP's locking mechanism (see SAP Locking).
Variant 1
INSERT INTO dbtab      VALUES wa. or
INSERT INTO (dbtabname) VALUES wa. or
INSERT dbtab      FROM wa. or
INSERT (dbtabname) FROM wa.
Extras:
1. ... CLIENT SPECIFIED
2. ... CONNECTION con
Effect
Inserts one line into a database table. The line to be inserted is taken from the work area wa and the data read from left to right according to the line structure of the database table dbtab. Here, the structure of wa is not taken into account. For this reason, the work area wa must be at least as wide (see DATA) as the line structure of dbtab, and the alignment of the work area wa must correspond to the alignment of the line structure. Otherwise, a runtime error occurs.
If the database table dbtab or the work area wa contain strings, wa must be compatible with the line structure of dbtab.
When the command has been executed, the system field SY-DBCNT contains the number of inserted lines (0 or 1).
The Return Code is set as follows:
SY-SUBRC = 0:
Line was successfully inserted.
SY-SUBRC = 4:
Line could not be inserted since a line with the same key already exists.
Example
Insert the customer Robinson in the current client:
DATA: wa TYPE scustom.
wa-id        = '12400177'.
wa-name      = 'Robinson'.
wa-postcode = '69542'.
wa-city      = 'Heidelberg'.
wa-custtype = 'P'.
wa-discount = '003'.
wa-telephone = '06201/44889'.
INSERT INTO scustom VALUES wa.
Addition 1
... CLIENT SPECIFIED
Effect
Automatic client handling is switched off. This allows
you to process data on a cross-client basis for client-specific tables. The client field is then treated like a normal table field which the program must fill with values in the work area wa.
The addition CLIENT SPECIFIED must be specified directly after the name of the database table.
Example
Insert the customer Robinson in client 2:
DATA: wa TYPE scustom.
wa-mandt     = '002'.
wa-id        = '12400177'.
wa-name      = 'Robinson'.
wa-postcode = '69542'.
wa-city      = 'Heidelberg'.
wa-custtype = 'P'.
wa-discount = '003'.
wa-telephone = '06201/44889'.
INSERT scustom CLIENT SPECIFIED FROM wa.
Addition 2
... CONNECTION con
Effect
The Open SQL command is not executed on the
standard database, but on the secondary database connection specified with con. con is the name of the databse connection as it was specified in the table DBCON in the column CON_NAME. The database connection con can also be specified dynamically in the form (source_text), where the field source_text contains the name of the database connection and must be type C or STRING. The CONNECTION con addition must be specified directly after the name of the database table or after the CLIENT SPECIFIED addition.
Variant 2
INSERT dbtab      FROM TABLE itab. oder
INSERT (dbtabname) FROM TABLE itab.
Extras:
1. ... CLIENT SPECIFIED
2. ... ACCEPTING DUPLICATE KEYS
3. ... CONNECTION con
Effect
Mass insert: All lines of the internal table itab are inserted in one single operation. The lines of itab must fulfill the same conditions as the work area wa in variant 1.
When the command has been executed, the system field SY-DBCNT contains the number of inserted lines.
The Return Code is set as follows:
SY-SUBRC = 0:
All lines successfully inserted. Any other result causes a runtime error.
Note
If the internal table itab is empty, SY-SUBRC and SY-DBCNT are set to 0 after the call.
Addition 1
... CLIENT SPECIFIED
Effect
As with variant 1.
Addition 2
... ACCEPTING DUPLICATE KEYS
Effect
If a line cannot be inserted, the system does not
terminate with a runtime error but only sets the return value SY-SUBRC to 4. All other lines are inserted after the command is executed.
Addition 3
... CONNECTION con
Effect
As with variant 1.
Variant 3
INSERT dbtab. or
INSERT *dbtab.
Extras:
1. ... CLIENT SPECIFIED
2. ... CONNECTION con
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas.
See Cannot Use Short Forms and Cannot Use * Work Areas.
Note
This variant is obsolete.
Effect
These are the SAP-specific short forms of variant 1. They have the same effect as variant 1, but the work area is not specified explicitly. Instead, the system implicitly uses the table work area dbtab or *dbtab declared using a TABLES statement.
INSERT dbtab. bzw.
INSERT *dbtab.
is equivalent to
INSERT INTO dbtab VALUES dbtab. or
INSERT INTO dbtab VALUES *dbtab.
When the command has been executed, the system field SY-DBCNT contains the number of lines inserted (0 or 1).
The Return Code is set as follows:
SY-SUBRC = 0:
Line successfully inserted.
SY-SUBRC = 4:
Line could not be inserted, since a line with the same key already exists.
Example
Add a line to a database table:
TABLES sairport.
sairport-id   = 'NEW'.
sairport-name = 'NEWPORT APT'.
INSERT sairport.
Notes
You should always use variant 1 where you specify an explicit work area wa instead of using the implicit TABLES work area.
If a work area is not explicitly specified, the values for the line to be inserted are taken from the table work area dbtab if the statement is in a FORM or FUNCTION where the table work area is stored in a formal parameter or local variable of the same name.
Addition 1
... CLIENT SPECIFIED
Effect
As with variant 1.
Addition 2
... CONNECTION con
Effect
As with variant 1.
regards
ganesh

Addition of variant in MB51

Similar Messages

Maybe you are looking for