Database selection through use of a parameter

Post Author: jmetaxas
CA Forum: Publishing
I am currently using Crystal Server. I would like to know if there is a way to use parameters to allow the end user to select which database source to use when running a report. We have a number of databases with identical Schemas. Being able to select the database to use as a parameter would be ideal.
Thanks in advance,
John Metaxas

Post Author: colin mackenzie
CA Forum: Publishing
Hey Denny,
I had thought about the same thing for changing data sources at Runtime. But I don't want to get into custom code just for something this simple. I figured there must be a way to do this, quite quickly and effeciently.
Instead of publishing 3 reports (test.rpt) all the same report but all 3 objects are pointed to different databases.In folder "Prod" Test.rpt > Production (Database)In folder "Test" Test.rpt > Test (Database)In folder "Dev" Test.rpt > Dev(Database)

Similar Messages

Deleting a MS Access database table record using JOptionPane

hi!
just want some help here..
is there a way to delete a MS Access database record through using JOptionPane?? i've gone through some, probably alot of examples on SELECT, INSERT, UPDATE, DELETE statements but none came up to the stuff i need.
so far i've seen the DELETE statement like this and also this is a common DELETE statement..
statement.executeUpdate("DELETE FROM tableName WHERE fieldName01 = 'blablabla' AND fieldName02 = 'etcetcetc'");like INSERT, there's a coding somewhat like this:
String asd = JOptionPane.showInputDialog(null, "Enter blablabla stuff");
statement.executeUpdate("INSERT INTO whatEverTableName (tableFieldName) VALUES('"+asd.getText()+"')");so, is it possible using the same method for DELETE??
help and advices are appreciated in advanced..

Here's how I did it. Research does help, but sometimes looking at others code does too... You do have to have a dummy file that you made with access though. You can't just make a file file.mdb (it will be corrupt)
     public void createDatabase(String database) throws SQLException{
          try{
               // This file needs to have been created with MS Access
               File dbfile = new File(this.dataBaseDir + "dummy.mdb");
               // This is the new database file being made
               File newFile = new File(this.dataBaseDir + database + ".mdb");
               // Copy all bytes from dummy file to new DB file.
               FileInputStream instream = new FileInputStream(dbfile);
               FileOutputStream ostream = new FileOutputStream(newFile);
               int numBytes = instream.available();
               byte inBytes[] = new byte[numBytes];
               instream.read(inBytes, 0, numBytes);
               ostream.write(inBytes, 0, numBytes);
          catch(FileNotFoundException e) { e.printStackTrace();}
          catch(IOException e) { e.printStackTrace();}
          if(DEBUG) System.out.println("creating the " + database + " database");
     }

Default sales org on selection screen using set and get parameter!!

Hi,
I need to default value on selection screen using SET n GET parameter...logic to be used should be:
Sales Organisation:
This field should be filled by default using the user parameter id VKO. (using sentence GET PARAMETER and SET PARAMETER)...
Hope i need to write the code in initialisation and what shud b the content?
Regards
Gunjan

hi,
TABLES <table name>.
SET PARAMETER ID VKO FIELD <tablename-fieldname>.
call transaction 'zxx'.
try this sample program,
REPORT BOOKINGS NO STANDARD PAGE HEADING.
TABLES SBOOK.
START-OF-SELECTION.
WRITE: 'Select a booking',
SKIP.
GET SBOOK.
WRITE: SBOOK-CARRID, SBOOK-CONNID,
 SBOOK-FLDATE, SBOOK-BOOKID.
HIDE: SBOOK-CARRID, SBOOK-CONNID,
 SBOOK-FLDATE, SBOOK-BOOKID.
AT LINE-SELECTION.
SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,
 'CON' FIELD SBOOK-CONNID,
 'DAY' FIELD SBOOK-FLDATE,
 'BOK' FIELD SBOOK-BOOKID.
CALL TRANSACTION 'BOOK'.
regards,
siva
Message was edited by:
 Shan

Dynamic select-options using parameter

Hi experts,
It the user selects one value from dropdown list, it should generate one select-option using that name. Is it possible?
for example, (pls see my code).
If user selects 'Malek' from parameter, and press 'ENTER'
select-option should display with that name like
Malek malek-low malek-high
And if user selects some other like 'Amran'. It should generate(and append)
Malek malek-low malek-high
amran amran-low amran-high
and so on....
report c.
data: t_return like ddshretval occurs 0 with header line.
data: begin of t_names occurs 0,
 name like usr01-bname,
 end of t_names.
parameters : i_inspec like usr01-bname.
at selection-screen on value-request for i_inspec.
perform get_names.
form get_names.
t_names-name = 'Malek'.
append t_names.
t_names-name = 'Amran'.
append t_names.
t_names-name = 'Ow CC'.
append t_names.
t_names-name = 'titbit'.
append t_names.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
 exporting
 retfield = 'T_NAMES-NAME'
 dynpprog = sy-cprog
 dynpnr = sy-dynnr
 dynprofield = 'I_INSPEC'
 value_org = 'S'
 tables
 value_tab = t_names.
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno with
 sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
read table t_return index 1.
endform. "GET_NAMES
Reward guaranteed,
thanks
kaki

Use At selection-screen output,use screen internal table..
User Dynamic Selection
at selection-screen output.
select single * from t000md.
loop at screen.
 case screen-group1.
 when 'REL'.
 if not p_old is initial.
 screen-input = '0'.
 screen-required = '0'.
 screen-invisible = '1'.
 endif.
 modify screen.
 when 'BEL'.
 if not p_new is initial.
 screen-input = '0'.
 screen-required = '0'.
 screen-invisible = '1'.
 endif.
 modify screen.
 when 'ARB'.
 if p_new is initial.
 screen-input = '0'.
 screen-required = '0'.
 screen-invisible = '1'.
 endif.
 modify screen.
 when 'MTA'.
 if p_new is initial.
 screen-input = '0'.
 screen-required = '0'.
 screen-invisible = '1'.
 endif.
 modify screen.
 endcase.
endloop.

How to select first several records from a database table by using select?

Hi,
 I want to select first 100 records from a database table by using select clause. How to write it?
 Thanks a lot!

hai long!
 well select statement is used to retrive
records from the database.
following is the syntax to be used.
1) select * into corresponding fields of itab from basetable where condition.
endselect.
ex: select * into corresponding fields of itab from mara
 where matnr >= '1' and matnr <= '100'.
 append itab.
 endselect.
select * is a loop statement.it will execute till matnr is less than or equal to 100.
note: you can also mention the required field names in the select statement otherwise it will select all the field from table mara.
note: itab means your internal table name.
hope you got the required thing.if it really solved u r problem then award me the suitable points.

Two commands in the report using the same parameter - fail under Java

I have a report that contains 2 SQL commands.
Both of these commands use one parameter X of type Number in their 'WHERE' clause.
When i'm viewing the report in CR 2008, i'm asked for a value of this parameter and all data is filled in the report - OK
The problem occurs when the same report is printed through Crystal Java Runtime:
Report is printed without data! - it's empty.
What we noticed in the debug information thrown by the Crystal libraries is that parameter value is set only in one of these commands:
Original statement 1:
select a.something
from ANM_T a
where a.anmid = {?PARAMETER01Id}
Original statement 2:
SELECT * from ANM_T a
WHERE a.anmid={?PARAMETER01Id}
OUTCOME of Statement 1:
select a.something
from ANM_T a
where a.anmid = 0
OUTCOME of Statement 2:
SELECT * from ANM_T a
WHERE a.anmid=9825
In above example we may see that crystal set the value only in the second statement - first one got 0 - i suspect its some default value.
Parameter in the Java code is set in the right way. In case of using only one statement it works. If we use two separate parameters (whose values are equal ) it also works.
// we have also the loop over the parameters
ParameterFieldController paramFieldController =
 report.getDataDefController().getParameterFieldController();
paramFieldController.setCurrentValue( "", paramName, paramValue );
What is strange for me is that Crystal Reports enables to use the same parameter in two commands but if you edit one of them you may change the type of this parameter for a command ( for example from Number to String) but the parameter type in the second command remains unchanged ( it's strange because in my opinion it is the same parameter). In the Field Explorer under the Parameter Fields i still see one parameter of type used in the second command.

Hello all,
We have prepared some sample code to illustrate the issue.
We have modified the sample application (Link: [http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/c07fec3e-3e11-2c10-1991-8c0fb0b82b75]) to that it also changes the parameter value. Parameter is used in two commands saved in report.
The code changing the parameters value looks like this:
private static void changeParameters(ReportClientDocument reportClientDoc) throws ReportSDKException {
 DataDefController dataDefController = reportClientDoc.getDataDefController();
 Fields fields = dataDefController.getDataDefinition().getParameterFields();
 for( int i = 0; i < fields.size(); i++ ){
 Field field = (Field)fields.getField( i );
 if( field.getKind() == FieldKind.parameterField ){
 setParameter( ((ParameterField)field).getName(), "9825" , reportClientDoc);
private static void setParameter( String paramName, String paramValue, ReportClientDocument document ) throws ReportSDKException {
 ParameterFieldController paramFieldController =
 document.getDataDefController().getParameterFieldController();
 paramFieldController.setCurrentValue( "", paramName, paramValue );
We have tried the following codes to change the connection info used in commands:
Attempt 1
 Tables tables = databaseController.getDatabase().getTables();
 //Set the datasource for all main report tables.
 for (int i = 0; i < tables.size(); i++) {
 ITable table = tables.getTable(i);
 //Keep existing name and alias.
 table.setName(table.getName());
 table.setAlias(table.getAlias());
 //Change connection information properties.
 IConnectionInfo connectionInfo = table.getConnectionInfo();
 //Set new table connection property attributes.
 connectionInfo.setAttributes(propertyBag);
 //Set database username and password.
 //NOTE: Even if these the username and password properties don't change when switching databases, the
 //database password is *not* saved in the report and must be set at runtime if the database is secured.
 connectionInfo.setUserName(DBUSERNAME);
 connectionInfo.setPassword(DBPASSWORD);
 connectionInfo.setKind(ConnectionInfoKind.SQL);
 table.setConnectionInfo(connectionInfo);
 //Update old table in the report with the new table.
 databaseController.setTableLocation(table, tables.getTable(i));
 //databaseController.setTableLocation(tables.getTable(i), table);
Attempt 2
 newConnectionInfo.setAttributes(propertyBag);
 connectionInfo.setUserName(DBUSERNAME);
 connectionInfo.setPassword(DBPASSWORD);
 //preserve subreport links
 SubreportController src = doc.getSubreportController();
 Map<String, SubreportLinks> linkMapper = new HashMap<String,SubreportLinks>();
 for(String subreportName : src.getSubreportNames()){
 linkMapper.put(subreportName,
 (SubreportLinks) src.getSubreportLinks(subreportName).clone(true));
 //If this connection needed parameters, we would use this field.
 Fields<IParameterField> pFields = doc.getDataDefController().getDataDefinition().getParameterFields();
 replaceConnectionInfos(doc.getDatabaseController(), newConnectionInfo, pFields);
 IStrings strs = src.getSubreportNames();
 Iterator<String> it = strs.iterator();
 while (it.hasNext()) {
 String name = it.next();
 ISubreportClientDocument subreport = src.getSubreport(name);
 pFields = subreport.getDataDefController().getDataDefinition().getParameterFields();
 replaceConnectionInfos(subreport.getDatabaseController(), newConnectionInfo, pFields);
 //reconnect subreport links since when using replaceConnection links are erased
 for(String subreportName : src.getSubreportNames())
 src.setSubreportLinks(subreportName, linkMapper.get(subreportName));
private static void replaceConnectionInfos(DatabaseController aDc, IConnectionInfo aNewConnInfo, Fields<IParameterField> aParameterField) throws ReportSDKException {
 ConnectionInfos cis = aDc.getConnectionInfos(null);
 for (IConnectionInfo oldConnInfo : cis)
 aDc.replaceConnection(oldConnInfo, aNewConnInfo, aParameterField, DBOptions._useDefault
 + DBOptions._doNotVerifyDB);
In both cases, the observed problem occurred. In one query the parameter was set properly, while on the other it was set to 0 (or empty string in case of string parameters). What is more, no data appeared on the print.
Do you happen to know the reason of this issue?How can we fix the problem?
Best regards
Mateusz Błaż

How to use Dynamic cascading parameter in crystal Report XI ?

Hi,
I want to use Dynamic cascading parameter in crystal Report XI which is to be viewed through the infoview without using the Business View.Is it possible?
I could implemented Dynamic cascading parameter using the CR XI developer without using Business View, but cannot view the report when uploaded it to BOXI, through infoview.
Please suggest..
Thanks in advance..
Rajneesh

In the crystal reports field explorer>right click on parameter field>create new-->name the parameter field and select the type as dynamic. Now in the value field click the row and add the database field also add another field below that by clicking on the next row so..on. The order should be like this parent field first and then child field next...... Also click on the last column to add parmater for each level.
Regards,
Raghavendra

Performance optimization during database selection.

hi gurus,
pls any explain about this...
Strong knowledge of performance optimization during database selection.
regards,
praveen

Hi Praveen,
Performance Notes
1.Keep the Result Set Small
You should aim to keep the result set small. This reduces both the amount of memory used in the database system and the network load when transferring data to the application server. To reduce the size of your result sets, use the WHERE and HAVING clauses.
Using the WHERE Clause
Whenever you access a database table, you should use a WHERE clause in the corresponding Open SQL statement. Even if a program containing a SELECT statement with no WHERE clause performs well in tests, it may slow down rapidly in your production system, where the data volume increases daily. You should only dispense with the WHERE clause in exceptional cases where you really need the entire contents of the database table every time the statement is executed.
When you use the WHERE clause, the database system optimizes the access and only transfers the required data. You should never transfer unwanted data to the application server and then filter it using ABAP statements.
Using the HAVING Clause
After selecting the required lines in the WHERE clause, the system then processes the GROUP BY clause, if one exists, and summarizes the database lines selected. The HAVING clause allows you to restrict the grouped lines, and in particular, the aggregate expressions, by applying further conditions.
Effect
If you use the WHERE and HAVING clauses correctly:
 There are no more physical I/Os in the database than necessary
 No unwanted data is stored in the database cache (it could otherwise displace data that is actually required)
 The CPU usage of the database host is minimize
 The network load is reduced, since only the data that is required by the application is transferred to the application server.
Minimize the Amount of Data Transferred
Data is transferred between the database system and the application server in blocks. Each block is up to 32 KB in size (the precise size depends on your network communication hardware). Administration information is transported in the blocks as well as the data.
To minimize the network load, you should transfer as few blocks as possible. Open SQL allows you to do this as follows:
Restrict the Number of Lines
If you only want to read a certain number of lines in a SELECT statement, use the UP TO <n> ROWS addition in the FROM clause. This tells the database system only to transfer <n> lines back to the application server. This is more efficient than transferring more lines than necessary back to the application server and then discarding them in your ABAP program.
If you expect your WHERE clause to return a large number of duplicate entries, you can use the DISTINCT addition in the SELECT clause.
Restrict the Number of Columns
You should only read the columns from a database table that you actually need in the program. To do this, list the columns in the SELECT clause. Note here that the INTO CORRESPONDING FIELDS addition in the INTO clause is only efficient with large volumes of data, otherwise the runtime required to compare the names is too great. For small amounts of data, use a list of variables in the INTO clause.
Do not use * to select all columns unless you really need them. However, if you list individual columns, you may have to adjust the program if the structure of the database table is changed in the ABAP Dictionary. If you specify the database table dynamically, you must always read all of its columns.
Use Aggregate Functions
If you only want to use data for calculations, it is often more efficient to use the aggregate functions of the SELECT clause than to read the individual entries from the database and perform the calculations in the ABAP program.
Aggregate functions allow you to find out the number of values and find the sum, average, minimum, and maximum values.
Following an aggregate expression, only its result is transferred from the database.
Data Transfer when Changing Table Lines
When you use the UPDATE statement to change lines in the table, you should use the WHERE clause to specify the relevant lines, and then SET statements to change only the required columns.
When you use a work area to overwrite table lines, too much data is often transferred. Furthermore, this method requires an extra SELECT statement to fill the work area. Minimize the Number of Data Transfers
In every Open SQL statement, data is transferred between the application server and the database system. Furthermore, the database system has to construct or reopen the appropriate administration data for each database access. You can therefore minimize the load on the network and the database system by minimizing the number of times you access the database.
Multiple Operations Instead of Single Operations
When you change data using INSERT, UPDATE, and DELETE, use internal tables instead of single entries. If you read data using SELECT, it is worth using multiple operations if you want to process the data more than once, other wise, a simple select loop is more efficient.
Avoid Repeated Access
As a rule you should read a given set of data once only in your program, and using a single access. Avoid accessing the same data more than once (for example, SELECT before an UPDATE).
Avoid Nested SELECT Loops
A simple SELECT loop is a single database access whose result is passed to the ABAP program line by line. Nested SELECT loops mean that the number of accesses in the inner loop is multiplied by the number of accesses in the outer loop. You should therefore only use nested SELECT loops if the selection in the outer loop contains very few lines.
However, using combinations of data from different database tables is more the rule than the exception in the relational data model. You can use the following techniques to avoid nested SELECT statements:
ABAP Dictionary Views
You can define joins between database tables statically and systemwide as views in the ABAP Dictionary. ABAP Dictionary views can be used by all ABAP programs. One of their advantages is that fields that are common to both tables (join fields) are only transferred once from the database to the application server.
Views in the ABAP Dictionary are implemented as inner joins. If the inner table contains no lines that correspond to lines in the outer table, no data is transferred. This is not always the desired result. For example, when you read data from a text table, you want to include lines in the selection even if the corresponding text does not exist in the required language. If you want to include all of the data from the outer table, you can program a left outer join in ABAP.
The links between the tables in the view are created and optimized by the database system. Like database tables, you can buffer views on the application server. The same buffering rules apply to views as to tables. In other words, it is most appropriate for views that you use mostly to read data. This reduces the network load and the amount of physical I/O in the database.
Joins in the FROM Clause
You can read data from more than one database table in a single SELECT statement by using inner or left outer joins in the FROM clause.
The disadvantage of using joins is that redundant data is read from the hierarchically-superior table if there is a 1:N relationship between the outer and inner tables. This can considerably increase the amount of data transferred from the database to the application server. Therefore, when you program a join, you should ensure that the SELECT clause contains a list of only the columns that you really need. Furthermore, joins bypass the table buffer and read directly from the database. For this reason, you should use an ABAP Dictionary view instead of a join if you only want to read the data.
The runtime of a join statement is heavily dependent on the database optimizer, especially when it contains more than two database tables. However, joins are nearly always quicker than using nested SELECT statements.
Subqueries in the WHERE and HAVING Clauses
Another way of accessing more than one database table in the same Open SQL statement is to use subqueries in the WHERE or HAVING clause. The data from a subquery is not transferred to the application server. Instead, it is used to evaluate conditions in the database system. This is a simple and effective way of programming complex database operations.
Using Internal Tables
It is also possible to avoid nested SELECT loops by placing the selection from the outer loop in an internal table and then running the inner selection once only using the FOR ALL ENTRIES addition. This technique stems from the time before joins were allowed in the FROM clause. On the other hand, it does prevent redundant data from being transferred from the database.
Using a Cursor to Read Data
A further method is to decouple the INTO clause from the SELECT statement by opening a cursor using OPEN CURSOR and reading data line by line using FETCH NEXT CURSOR. You must open a new cursor for each nested loop. In this case, you must ensure yourself that the correct lines are read from the database tables in the correct order. This usually requires a foreign key relationship between the database tables, and that they are sorted by the foreign key. Minimize the Search Overhead
You minimize the size of the result set by using the WHERE and HAVING clauses. To increase the efficiency of these clauses, you should formulate them to fit with the database table indexes.
Database Indexes
Indexes speed up data selection from the database. They consist of selected fields of a table, of which a copy is then made in sorted order. If you specify the index fields correctly in a condition in the WHERE or HAVING clause, the system only searches part of the index (index range scan).
The primary index is always created automatically in the R/3 System. It consists of the primary key fields of the database table. This means that for each combination of fields in the index, there is a maximum of one line in the table. This kind of index is also known as UNIQUE.
If you cannot use the primary index to determine the result set because, for example, none of the primary index fields occur in the WHERE or HAVING clause, the system searches through the entire table (full table scan). For this case, you can create secondary indexes, which can restrict the number of table entries searched to form the result set.
You specify the fields of secondary indexes using the ABAP Dictionary. You can also determine whether the index is unique or not. However, you should not create secondary indexes to cover all possible combinations of fields.
Only create one if you select data by fields that are not contained in another index, and the performance is very poor. Furthermore, you should only create secondary indexes for database tables from which you mainly read, since indexes have to be updated each time the database table is changed. As a rule, secondary indexes should not contain more than four fields, and you should not have more than five indexes for a single database table.
If a table has more than five indexes, you run the risk of the optimizer choosing the wrong one for a particular operation. For this reason, you should avoid indexes with overlapping contents.
Secondary indexes should contain columns that you use frequently in a selection, and that are as highly selective as possible. The fewer table entries that can be selected by a certain column, the higher that columns selectivity. Place the most selective fields at the beginning of the index. Your secondary index should be so selective that each index entry corresponds to at most five percent of the table entries. If this is not the case, it is not worth creating the index. You should also avoid creating indexes for fields that are not always filled, where their value is initial for most entries in the table.
If all of the columns in the SELECT clause are contained in the index, the system does not have to search the actual table data after reading from the index. If you have a SELECT clause with very few columns, you can improve performance dramatically by including these columns in a secondary index.
Formulating Conditions for Indexes
You should bear in mind the following when formulating conditions for the WHERE and HAVING clauses so that the system can use a database index and does not have to use a full table scan.
Check for Equality and Link Using AND
The database index search is particularly efficient if you check all index fields for equality (= or EQ) and link the expressions using AND.
Use Positive Conditions
The database system only supports queries that describe the result in positive terms, for example, EQ or LIKE. It does not support negative expressions like NE or NOT LIKE.
If possible, avoid using the NOT operator in the WHERE clause, because it is not supported by database indexes; invert the logical expression instead.
Using OR
The optimizer usually stops working when an OR expression occurs in the condition. This means that the columns checked using OR are not included in the index search. An exception to this are OR expressions at the outside of conditions. You should try to reformulate conditions that apply OR expressions to columns relevant to the index, for example, into an IN condition.
Using Part of the Index
If you construct an index from several columns, the system can still use it even if you only specify a few of the columns in a condition. However, in this case, the sequence of the columns in the index is important. A column can only be used in the index search if all of the columns before it in the index definition have also been specified in the condition.
Checking for Null Values
The IS NULL condition can cause problems with indexes. Some database systems do not store null values in the index structure. Consequently, this field cannot be used in the index.
Avoid Complex Conditions
Avoid complex conditions, since the statements have to be broken down into their individual components by the database system.
Reduce the Database Load
Unlike application servers and presentation servers, there is only one database server in your system. You should therefore aim to reduce the database load as much as possible. You can use the following methods:
Buffer Tables on the Application Server
You can considerably reduce the time required to access data by buffering it in the application server table buffer. Reading a single entry from table T001 can take between 8 and 600 milliseconds, while reading it from the table buffer takes 0.2 - 1 milliseconds.
Whether a table can be buffered or not depends its technical attributes in the ABAP Dictionary. There are three buffering types:
 Resident buffering (100%) The first time the table is accessed, its entire contents are loaded in the table buffer.
 Generic buffering In this case, you need to specify a generic key (some of the key fields) in the technical settings of the table in the ABAP Dictionary. The table contents are then divided into generic areas. When you access data with one of the generic keys, the whole generic area is loaded into the table buffer. Client-specific tables are often buffered generically by client.
 Partial buffering (single entry) Only single entries are read from the database and stored in the table buffer.
When you read from buffered tables, the following happens:
1. An ABAP program requests data from a buffered table.
2. The ABAP processor interprets the Open SQL statement. If the table is defined as a buffered table in the ABAP Dictionary, the ABAP processor checks in the local buffer on the application server to see if the table (or part of it) has already been buffered.
3. If the table has not yet been buffered, the request is passed on to the database. If the data exists in the buffer, it is sent to the program.
4. The database server passes the data to the application server, which places it in the table buffer.
5. The data is passed to the program.
When you change a buffered table, the following happens:
1. The database table is changed and the buffer on the application server is updated. The database interface logs the update statement in the table DDLOG. If the system has more than one application server, the buffer on the other servers is not updated at once.
2. All application servers periodically read the contents of table DDLOG, and delete the corresponding contents from their buffers where necessary. The granularity depends on the buffering type. The table buffers in a distributed system are generally synchronized every 60 seconds (parameter: rsdisp/bufreftime).
3. Within this period, users on non-synchronized application servers will read old data. The data is not recognized as obsolete until the next buffer synchronization. The next time it is accessed, it is re-read from the database.
You should buffer the following types of tables:
 Tables that are read very frequently
 Tables that are changed very infrequently
 Relatively small tables (few lines, few columns, or short columns)
 Tables where delayed update is acceptable.
Once you have buffered a table, take care not to use any Open SQL statements that bypass the buffer.
The SELECT statement bypasses the buffer when you use any of the following:
 The BYPASSING BUFFER addition in the FROM clause
 The DISTINCT addition in the SELECT clause
 Aggregate expressions in the SELECT clause
 Joins in the FROM clause
 The IS NULL condition in the WHERE clause
 Subqueries in the WHERE clause
 The ORDER BY clause
 The GROUP BY clause
 The FOR UPDATE addition
Furthermore, all Native SQL statements bypass the buffer.
Avoid Reading Data Repeatedly
If you avoid reading the same data repeatedly, you both reduce the number of database accesses and reduce the load on the database. Furthermore, a "dirty read" may occur with database tables other than Oracle. This means that the second time you read data from a database table, it may be different from the data read the first time. To ensure that the data in your program is consistent, you should read it once only and then store it in an internal table.
Sort Data in Your ABAP Programs
The ORDER BY clause in the SELECT statement is not necessarily optimized by the database system or executed with the correct index. This can result in increased runtime costs. You should only use ORDER BY if the database sort uses the same index with which the table is read. To find out which index the system uses, use SQL Trace in the ABAP Workbench Performance Trace. If the indexes are not the same, it is more efficient to read the data into an internal table or extract and sort it in the ABAP program using the SORT statement.
Use Logical Databases
SAP supplies logical databases for all applications. A logical database is an ABAP program that decouples Open SQL statements from application programs. They are optimized for the best possible database performance. However, it is important that you use the right logical database. The hierarchy of the data you want to read must reflect the structure of the logical database, otherwise, they can have a negative effect on performance. For example, if you want to read data from a table right at the bottom of the hierarchy of the logical database, it has to read at least the key fields of all tables above it in the hierarchy. In this case, it is more efficient to use a SELECT statement.
Work Processes
Work processes execute the individual dialog steps in R/3 applications. The next two sections describe firstly the structure of a work process, and secondly the different types of work process in the R/3 System.
Structure of a Work Process
Work processes execute the dialog steps of application programs. They are components of an application server. The following diagram shows the components of a work process:
Each work process contains two software processors and a database interface.
Screen Processor
In R/3 application programming, there is a difference between user interaction and processing logic. From a programming point of view, user interaction is controlled by screens. As well as the actual input mask, a screen also consists of flow logic. The screen flow logic controls a large part of the user interaction. The R/3 Basis system contains a special language for programming screen flow logic. The screen processor executes the screen flow logic. Via the dispatcher, it takes over the responsibility for communication between the work process and the SAPgui, calls modules in the flow logic, and ensures that the field contents are transferred from the screen to the flow logic.
ABAP Processor
The actual processing logic of an application program is written in ABAP - SAPs own programming language. The ABAP processor executes the processing logic of the application program, and communicates with the database interface. The screen processor tells the ABAP processor which module of the screen flow logic should be processed next. The following screen illustrates the interaction between the screen and the ABAP processors when an application program is running.
Database Interface
The database interface provides the following services:
 Establishing and terminating connections between the work process and the database.
 Access to database tables
 Access to R/3 Repository objects (ABAP programs, screens and so on)
 Access to catalog information (ABAP Dictionary)
 Controlling transactions (commit and rollback handling)
 Table buffer administration on the application server.
The following diagram shows the individual components of the database interface:
The diagram shows that there are two different ways of accessing databases: Open SQL and Native SQL.
Open SQL statements are a subset of Standard SQL that is fully integrated in ABAP. They allow you to access data irrespective of the database system that the R/3 installation is using. Open SQL consists of the Data Manipulation Language (DML) part of Standard SQL; in other words, it allows you to read (SELECT) and change (INSERT, UPDATE, DELETE) data. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) parts of Standard SQL are performed in the R/3 System by the ABAP Dictionary and the authorization system. These provide a unified range of functions, irrespective of database, and also contain functions beyond those offered by the various database systems.
Open SQL also goes beyond Standard SQL to provide statements that, in conjunction with other ABAP constructions, can simplify or speed up database access. It also allows you to buffer certain tables on the application server, saving excessive database access. In this case, the database interface is responsible for comparing the buffer with the database. Buffers are partly stored in the working memory of the current work process, and partly in the shared memory for all work processes on an application server. Where an R/3 System is distributed across more than one application server, the data in the various buffers is synchronized at set intervals by the buffer management. When buffering the database, you must remember that data in the buffer is not always up to date. For this reason, you should only use the buffer for data which does not often change.
Native SQL is only loosely integrated into ABAP, and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted, but instead are sent directly to the database system. Programs that use Native SQL are specific to the database system for which they were written. R/3 applications contain as little Native SQL as possible. In fact, it is only used in a few Basis components (for example, to create or change table definitions in the ABAP Dictionary).
The database-dependent layer in the diagram serves to hide the differences between database systems from the rest of the database interface. You choose the appropriate layer when you install the Basis system. Thanks to the standardization of SQL, the differences in the syntax of statements are very slight. However, the semantics and behavior of the statements have not been fully standardized, and the differences in these areas can be greater. When you use Native SQL, the function of the database-dependent layer is minimal.
Types of Work Process
Although all work processes contain the components described above, they can still be divided into different types. The type of a work process determines the kind of task for which it is responsible in the application server. It does not specify a particular set of technical attributes. The individual tasks are distributed to the work processes by the dispatcher.
Before you start your R/3 System, you determine how many work processes it will have, and what their types will be. The dispatcher starts the work processes and only assigns them tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resources on your application servers.
The following diagram shows again the structure of an application server, but this time, includes the various possible work process types:
The various work processes are described briefly below. Other parts of this documentation describe the individual components of the application server and the R/3 System in more detail.
Dialog Work Process
Dialog work processes deal with requests from an active user to execute dialog steps.
Update Work Process
Update work processes execute database update requests. Update requests are part of an SAP LUW that bundle the database operations resulting from the dialog in a database LUW for processing in the background.
Background Work Process
Background work processes process programs that can be executed without user interaction (background jobs).
Enqueue Work Process
The enqueue work process administers a lock table in the shared memory area. The lock table contains the logical database locks for the R/3 System and is an important part of the SAP LUW concept. In an R/3 System, you may only have one lock table. You may therefore also only have one application server with enqueue work processes.
Spool Work Process
The spool work process passes sequential datasets to a printer or to optical archiving. Each application server may contain several spool work process.
The services offered by an application server are determined by the types of its work processes. One application server may, of course, have more than one function. For example, it may be both a dialog server and the enqueue server, if it has several dialog work processes and an enqueue work process.
You can use the system administration functions to switch a work process between dialog and background modes while the system is still running. This allows you, for example, to switch an R/3 System between day and night operation, where you have more dialog than background work processes during the day, and the other way around during the night.
ABAP Application Server
R/3 programs run on application servers. They are an important component of the R/3 System. The following sections describe application servers in more detail.
Structure of an ABAP Application Server
The application layer of an R/3 System is made up of the application servers and the message server. Application programs in an R/3 System are run on application servers. The application servers communicate with the presentation components, the database, and also with each other, using the message server.
The following diagram shows the structure of an application server:
The individual components are:
Work Processes
An application server contains work processes, which are components that can run an application. Work processes are components that are able to execute an application (that is, one dialog step each). Each work process is linked to a memory area containing the context of the application being run. The context contains the current data for the application program. This needs to be available in each dialog step. Further information about the different types of work process is contained later on in this documentation.
Dispatcher
Each application server contains a dispatcher. The dispatcher is the link between the work processes and the users logged onto the application server. Its task is to receive requests for dialog steps from the SAP GUI and direct them to a free work process. In the same way, it directs screen output resulting from the dialog step back to the appropriate user.
Gateway
Each application server contains a gateway. This is the interface for the R/3 communication protocols (RFC, CPI/C). It can communicate with other application servers in the same R/3 System, with other R/3 Systems, with R/2 Systems, or with non-SAP systems.
The application server structure as described here aids the performance and scalability of the entire R/3 System. The fixed number of work processes and dispatching of dialog steps leads to optimal memory use, since it means that certain components and the memory areas of a work process are application-independent and reusable. The fact that the individual work processes work independently makes them suitable for a multi-processor architecture. The methods used in the dispatcher to distribute tasks to work processes are discussed more closely in the section Dispatching Dialog Steps.
Shared Memory
All of the work processes on an application server use a common main memory area called shared memory to save contexts or to buffer constant data locally.
The resources that all work processes use (such as programs and table contents) are contained in shared memory. Memory management in the R/3 System ensures that the work processes always address the correct context, that is the data relevant to the current state of the program that is running. A mapping process projects the required context for a dialog step from shared memory into the address of the relevant work process. This reduces the actual copying to a minimum.
Local buffering of data in the shared memory of the application server reduces the number of database reads required. This reduces access times for application programs considerably. For optimal use of the buffer, you can concentrate individual applications (financial accounting, logistics, human resources) into separate application server groups.
Database Connection
When you start up an R/3 System, each application server registers its work processes with the database layer, and receives a single dedicated channel for each. While the system is running, each work process is a user (client) of the database system (server). You cannot change the work process registration while the system is running. Neither can you reassign a database channel from one work process to another. For this reason, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. This has important consequences for the programming model explained below.
Dispatching Dialog Steps
The number of users logged onto an application server is often many times greater than the number of available work processes. Furthermore, it is not restricted by the R/3 system architecture. Furthermore, each user can run several applications at once. The dispatcher has the important task of distributing all dialog steps among the work processes on the application server.
The following diagram is an example of how this might happen:
 1. The dispatcher receives the request to execute a dialog step from user 1 and directs it to work process 1, which happens to be free. The work process addresses the context of the application program (in shared memory) and executes the dialog step. It then becomes free again.
 2. The dispatcher receives the request to execute a dialog step from user 2 and directs it to work process 1, which is now free again. The work process executes the dialog step as in step 1.
 3. While work process 1 is still working, the dispatcher receives a further request from user 1 and directs it to work process 2, which is free.
 4. After work processes 1 and 2 have finished processing their dialog steps, the dispatcher receives another request from user 1 and directs it to work process 1, which is free again.
 5. While work process 1 is still working, the dispatcher receives a further request from user 2 and directs it to work process 2, which is free.
From this example, we can see that:
 A dialog step from a program is assigned to a single work process for execution.
 The individual dialog steps of a program can be executed on different work processes, and the program context must be addressed for each new work process.
 A work process can execute dialog steps of different programs from different users.
The example does not show that the dispatcher tries to distribute the requests to the work processes such that the same work process is used as often as possible for the successive dialog steps in an application. This is useful, since it saves the program context having to be addressed each time a dialog step is executed.
Dispatching and the Programming Model
The separation of application and presentation layer made it necessary to split up application programs into dialog steps. This, and the fact that dialog steps are dispatched to individual work processes, has had important consequences for the programming model.
As mentioned above, a work process can only make database changes within a single database logical unit of work (LUW). A database LUW is an inseparable sequence of database operations. The contents of the database must be consistent at its beginning and end. The beginning and end of a database LUW are defined by a commit command to the database system (database commit). During a database LUW, that is, between two database commits, the database system itself ensures consistency within the database. In other words, it takes over tasks such as locking database entries while they are being edited, or restoring the old data (rollback) if a step terminates in an error.
A typical SAP application program extends over several screens and the corresponding dialog steps. The user requests database changes on the individual screens that should lead to the database being consistent once the screens have all been processed. However, the individual dialog steps run on different work processes, and a single work process can process dialog steps from other applications. It is clear that two or more independent applications whose dialog steps happen to be processed on the same work process cannot be allowed to work with the same database LUW.
Consequently, a work process must open a separate database LUW for each dialog step. The work process sends a commit command (database commit) to the database at the end of each dialog step in which it makes database changes. These commit commands are called implicit database commits, since they are not explicitly written into the application program.
These implicit database commits mean that a database LUW can be kept open for a maximum of one dialog step. This leads to a considerable reduction in database load, serialization, and deadlocks, and enables a large number of users to use the same system.
However, the question now arises of how this method (1 dialog step = 1 database LUW) can be reconciled with the demand to make commits and rollbacks dependent on the logical flow of the application program instead of the technical distribution of dialog steps. Database update requests that depend on one another form logical units in the program that extend over more than one dialog step. The database changes associated with these logical units must be executed together and must also be able to be undone together.
The SAP programming model contains a series of bundling techniques that allow you to group database updates together in logical units. The section of an R/3 application program that bundles a set of logically-associated database operations is called an SAP LUW. Unlike a database LUW, a SAP LUW includes all of the dialog steps in a logical unit, including the database update.
Happy Reading...
shibu

Error: Invalid interruption of a database selection

Hi,
When i execute the below code, the output is displayed without any problem.
tables lfa1.
select * from lfa1 order by lifnr.
write / lfa1-lifnr.
endselect.
But however when i debug this piece of code, i get an error as below.
ShrtText - Invalid interruption of a database selection
Runtime Errors - DBIF_RSQL_INVALID_CURSOR
Exceptn - CX_SY_OPEN_SQL_DB
Can anybody help me with the reason for the occurence of this problem.

Hi Vijay,
Just go through the following link:
Re: DBIF_RSQL_INVALID_CURSOR dump during debugging
As Sooness pointed out, SELECT-ENDSELECT dumps only the first time. Try re-executing it and it will work fine.
Meanwhile, it is always better to use INTO TABLE OF instead of SELECT-ENDSELECT, as this minimizes database hits.
Regards
Anil Madhavan

DBIF_RSQL_INVALID_CURSOR: Invalid interruption of a database selection.

I have created an external program that extracts a very large table from SAP 7.0 through RFC using the NetWeaver SDK APIs. This program repeatedly calls an RFC-enabled function written in ABAP. On the first
call the function does "OPEN CURSOR WITH HOLD" and a "FETCH". On each subsequent call the function does a "FETCH". The cursor is declared as "STATICS".
When I run the program I am getting the following error:
DBIF_RSQL_INVALID_CURSOR: Invalid interruption of a database selection.
This error manifests itself in two ways.
1) When time interval between RfcInvoke() calls is about 0.5 sec., it takes 30 sec. to 90 sec. for the error to come out.
2) When time interval between RfcInvoke() calls is about 0.2 sec. or lower, it takes 8 min. to 17 min. for the error to come out, but sometimes the program completes successfully in 25 min.
1) What is causing this error?
2) If it has something to do with SAP configuration, how it be modified to extract this particular table.
3) Is it possible in general to extract a table of any size (on the magnitude of gigabytes) using such an approach, that is, a "pull".
4) If the answer is negative, what approach do you think is appropriate.
Any help will be appreciated.

Hi Andrew Coleman ,
This error sounds like problem is in the way you are calling the RFC Function module (n -number of times). Looks like during the subsequent calls the Select / ENDSELECT is failing need to check that logic.
Thanks,
Greetson

Ora-02020 too many database links in use

Hi All,
While trying to update Table through datalink in my program I am getting the above error. Without modifying the v$parameter value ( 'open_links' ) in database how to use this feature to close Inactive sessions in BPEL ?

Yes, I set the init.ora parameters on all servers and then restarted them. I still get the error.
Note that, for convenience, all my servers have public database links to all other servers in my private network.
This procedure (described at the start) works for one run of copying 50 tables from one server to one other server:
server1 runs the procedure and copies data from server2 to server3 (total of 3 servers in the process)But I get the error when I run the procedure to copy 40 tables from multiple servers to one other server:
server1 runs the procedure and copies data from server2, server3, and server4 to server5The error occurs when only four (or five) servers are involved in the process.
Any suggestions are greatly appreciated.
Edited by: user652257 on Nov 1, 2009 12:40 PM

Parameter Form-How to use a user parameter to retrieve list of values for another par

I am developing a report in Reports 6i. There are 2 parameters on parameter form namely year and month.
LOV for Year is retrieved from database. After user selects a value from LOV for year, I want to retrieve another LOV for month parameter based on selected year. That is how can we use a user parameter's value to dynamically retrieve an LOV for another parameter on the same parameter form.
Pl. guide.
Thanks in anticipation.

You can't restrict the "List of Values" of one parameter based on the value of another parameter within the Reports Builder/Runtime parameter form.
The SQL select statements within LOV's are only executed once. They aren't re-calculated when you enter, leave or change other field values in the parameter form. This is mainly because there is no event model in the Reports parameter form and it only supports basic form functionality.
To do what you're after in a client-server environment you need to create an Oracle Forms "parameter form" and use that to execute the Report using the run_product() call. Actually, you should probably use Oracle Forms for any more generic "form" functionality such as radio buttons or check boxes.
If you're in a Web rather than Client-Server environment, it may be easier to create a JSP based parameter form. You can then use Reports 9i since it has JSP support to assist here.

Seed mailbox database copy through replication network (DAG members on different subnets in different sites)

Good afternoon
I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication
network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the
moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.
According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.
'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'
http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx
Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary
site and I would like to keep that traffic to the replication network I have configured.
Any insight would be helpful.

Hi,
If you want to specify the networks for seeding, you can use the
Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use.
If you don't use the Network parameter, then the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
So please use the Update-MailboxDatabaseCopy cmdlet with
NetWork parameter to specify which DAG network should be used for seeding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Reading the record and displaying when u select it using checkbox

hi,
 how to read the particilar record and display it in a popup screen when u select it using checkbox and then press 'DISP' button in alv(normal alv not with oops concepts).
like i select a row which is checked (checkbox) it and i have to read that particular record and display (value of keyfield say vbeln) details in a popup screen.

hi,
go through the faloowing code.
this for normal popup.
*& Report ZGS_ALV_POPUP_2_SELECT
REPORT ZGS_ALV_POPUP_2_SELECT.
TYPE-POOLS: slis.
PARAMETERS: p_title TYPE sy-title default 'Sales Document:item data'.
DATA: itab TYPE vbap OCCURS 0 WITH HEADER LINE,
 selfield TYPE slis_selfield.
START-OF-SELECTION.
SELECT *
 FROM vbap
 INTO TABLE itab
 UP TO 20 ROWS.
CALL FUNCTION 'REUSE_ALV_POPUP_TO_SELECT'
 EXPORTING
 i_title = p_title
* I_SELECTION = 'X'
 I_ZEBRA = 'X '
* I_SCREEN_START_COLUMN = 0
* I_SCREEN_START_LINE = 0
* I_SCREEN_END_COLUMN = 0
* I_SCREEN_END_LINE = 0
* I_CHECKBOX_FIELDNAME =
* I_LINEMARK_FIELDNAME =
* I_SCROLL_TO_SEL_LINE = 'X'
 i_tabname = 'ITAB'
 i_structure_name = 'VBAP'
* IT_FIELDCAT =
* IT_EXCLUDING =
* I_CALLBACK_PROGRAM =
* I_CALLBACK_USER_COMMAND =
* is_private =
 IMPORTING
 es_selfield = selfield
* e_exit =
 TABLES
 t_outtab = itab
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 MESSAGE i000(8I) WITH sy-subrc.
ENDIF.
WRITE:
 / 'Table Index : ', 20 selfield-tabindex,
 / 'Table Name : ', 15 selfield-tabname,
 / 'Field Name : ', 15 selfield-fieldname,
 / 'Table-Field : ', 15 selfield-sel_tab_field,
 / 'Field Value : ', 15 selfield-value.
the falowing code is for how to put checkbox and how to display the selected recods.you combine both codes.
*& Report ZRP_SALES
REPORT ZRP_SALES NO STANDARD PAGE HEADING.
DATA: TEMP_DATE_STR TYPE STRING.
*DATA: TEMP_NETP LIKE VBAK-NETWR.
DATA: TEMP_NETWR(10).
*DATA: TEMP_VBELN LIKE VBAK-VBELN.
DATA: CHECK TYPE C VALUE ' '.
*DATA: WA_VBELN LIKE VBAK-VBELN.
DATA: TEMP_DATE LIKE VBAK-ERDAT.
*DATA: TEMP_NETP_STR TYPE STRING.
DATA:FNAM(20), FVAL(20).
TYPES: BEGIN OF MY_VBAK,
 VTWEG TYPE VTWEG,
 VKORG TYPE VKORG,
 SPART TYPE SPART,
 NETWR TYPE NETWR_AK,
 VBELN TYPE VBELN_VA,
 ERDAT TYPE ERDAT,
 END OF MY_VBAK.
DATA: IT_VBAK TYPE MY_VBAK OCCURS 0 WITH HEADER LINE.
DATA: WA_VBAK TYPE MY_VBAK.
DATA: V_VBELN TYPE VBELN,
 V_ERDAT TYPE ERDAT.
SELECT-OPTIONS:S_VBELN FOR V_VBELN,
 S_ERDAT FOR V_ERDAT.
AT SELECTION-SCREEN.
*Check for Sales Order number to be non-initial.
IF S_VBELN IS INITIAL.
*Checking for Date to be non-nitial.
 IF S_ERDAT IS INITIAL.
 MESSAGE E003(ZRP_MSG). " Please enter either SO number or Date.
 ELSE.
*Validating the right low values for Date select option
 SELECT SINGLE ERDAT
 FROM VBAK INTO TEMP_DATE
 WHERE VBELN EQ S_VBELN-LOW OR ERDAT EQ S_ERDAT-LOW.
 IF SY-SUBRC NE 0.
 MESSAGE E004(ZRP_MSG).
 ENDIF.
*Validating the right high values for Date select option
 SELECT SINGLE ERDAT
 FROM VBAK INTO TEMP_DATE
 WHERE ERDAT EQ S_ERDAT-HIGH OR VBELN EQ S_VBELN-HIGH.
 IF SY-SUBRC NE 0.
 MESSAGE E005(ZRP_MSG).
 ENDIF.
 ENDIF.
ELSE.
*Checking for Date to be non-nitial.
 IF S_ERDAT IS NOT INITIAL.
 MESSAGE E003(ZRP_MSG). " Please enter either SO number or Date.
 ENDIF.
*Validating the right low values
 SELECT SINGLE VBELN
 FROM VBAK INTO S_VBELN
 WHERE VBELN EQ S_VBELN-LOW.
 IF SY-SUBRC NE 0.
 MESSAGE E001(ZRP_MSG).
 ENDIF.
*Validating the right high values
 IF S_VBELN-HIGH IS NOT INITIAL.
 SELECT SINGLE VBELN
 FROM VBAK INTO S_VBELN
 WHERE VBELN EQ S_VBELN-HIGH.
 IF SY-SUBRC NE 0.
 MESSAGE E002(ZRP_MSG).
 ENDIF.
 ENDIF.
ENDIF.
START-OF-SELECTION.
*First Screen.
SET PF-STATUS 'DISP'.
IF S_VBELN IS NOT INITIAL.
 SELECT VTWEG VKORG SPART NETWR VBELN ERDAT
 FROM VBAK
 INTO TABLE IT_VBAK
 WHERE VBELN IN S_VBELN.
ENDIF.
IF S_ERDAT IS NOT INITIAL.
 SELECT VTWEG VKORG SPART NETWR VBELN ERDAT
 FROM VBAK
 INTO TABLE IT_VBAK
 WHERE ERDAT IN S_ERDAT.
ENDIF.
SORT IT_VBAK BY VKORG VTWEG SPART.
END-OF-SELECTION.
LOOP AT IT_VBAK.
 MOVE IT_VBAK-NETWR TO TEMP_NETWR.
 MOVE IT_VBAK-ERDAT TO TEMP_DATE.
 WRITE:/6 CHECK AS CHECKBOX.
 FORMAT COLOR 1.
 WRITE: IT_VBAK-VBELN UNDER 'SALES ORDER NO.' .
 WRITE: IT_VBAK-ERDAT UNDER 'DATE'.
 FORMAT COLOR OFF.
 FORMAT COLOR 2.
 WRITE: TEMP_NETWR UNDER 'NET PRICE'.
 FORMAT COLOR OFF."TEMP_NETWR,
 FORMAT COLOR 3.
 WRITE:IT_VBAK-VKORG UNDER 'SALES ORG',
 IT_VBAK-VTWEG UNDER 'DIST CHANNEL',
 IT_VBAK-SPART UNDER 'DIVISION'.
 FORMAT COLOR OFF.
 SKIP 1.
*FOR SUBTOTALS
 AT END OF SPART.
 SUM.
 FORMAT COLOR 5.
 WRITE:/6 'SUB TOTOAL OF NET PRICE IS : '.
 WRITE: 32 IT_VBAK-NETWR CURRENCY 'INR'.
 FORMAT COLOR OFF.
 SKIP 2.
 ENDAT.
*FOR GRAND TOTALS
 AT LAST.
 SUM.
 FORMAT COLOR 6.
 WRITE:/6 'GRAND TOTOAL OF NET PRICE IS : ',
 32 IT_VBAK-NETWR CURRENCY 'INR'.
 FORMAT COLOR 6.
 ENDAT.
ENDLOOP.
TOP-OF-PAGE.
FORMAT COLOR 6.
WRITE:/8 'SALES ORDER NO.',
 27 'DATE',
 42 'NET PRICE',
 57 'SALES ORG',
 70 'DIST CHANNEL',
 87 'DIVISION'.
FORMAT COLOR OFF.
SKIP 1.
*WHEN SALES ORDER IS SELECTED
AT LINE-SELECTION.
CASE :SY-LSIND.
 WHEN '2'.
 GET CURSOR FIELD FNAM VALUE FVAL.
 IF FNAM <> 'WA_VBAK-VBELN'.
 MESSAGE E006(ZRP_MSG).
 ELSE.
 SET PARAMETER ID 'MAT' FIELD FVAL.
 CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN.
ENDIF.
 ENDCASE.
*WHEN CLICKED ON PUSH BUTTON IN THE APPLICATION BAR
AT USER-COMMAND.
CASE:SY-UCOMM.
 WHEN 'DISP'.
 DO.
 CLEAR CHECK.
 CLEAR: WA_VBAK,TEMP_DATE_STR.
 READ LINE SY-INDEX FIELD VALUE CHECK
 IT_VBAK-VTWEG INTO WA_VBAK-VTWEG
* IT_VBAK-NETWR INTO TEMP_NETP_STR
 IT_VBAK-VBELN INTO WA_VBAK-VBELN
 IT_VBAK-ERDAT INTO TEMP_DATE_STR
 IT_VBAK-VKORG INTO WA_VBAK-VKORG
 IT_VBAK-SPART INTO WA_VBAK-SPART.
 IF SY-SUBRC <> 0.
 EXIT.
 ELSEIF CHECK = 'X'.
 FORMAT COLOR 1.
 WRITE: 8 WA_VBAK-VBELN HOTSPOT. "UNDER 'SALES ORDER NO'
 WRITE: 25 TEMP_DATE_STR." UNDER 'DATE'.
 FORMAT COLOR OFF.
* FORMAT COLOR 2.
* WRITE: 44 TEMP_NETP_STR." UNDER 'NET PRICE'.
* FORMAT COLOR OFF.
 FORMAT COLOR 3.
 WRITE:44 WA_VBAK-VKORG," UNDER 'SALES ORG',
 59 WA_VBAK-VTWEG," UNDER 'DIST CHANNEL',
 72 WA_VBAK-SPART." UNDER 'DIVISION'.
 FORMAT COLOR OFF.
 SKIP 1.
 ENDIF.
 ENDDO.
ENDCASE.
TOP-OF-PAGE DURING LINE-SELECTION.
CASE:SY-LSIND.
 WHEN 1.
 FORMAT COLOR 6.
 WRITE:/8 'SALES ORDER NO.',
 25 'DATE',
* 44 'NET PRICE',
 44 'SALES ORG',
 58 'DIST CHANNEL',
 72 'DIVISION'.
 SKIP 1.
 FORMAT COLOR OFF.
if helpful reward some points.
Message was edited by:
 suredarreddy pulimamidi

To find out the min and max memory been used by each parameter under SGA_MA

Hi,
Can any please tell me how to find out the min and max memory been used by each parameter under SGA_MAX and SGA_TARGET ? below is the db CRMS65T. If any such script is there please provide me
SQL> select name from v$database;
NAME
CRMS65T
SQL> show parameter sga
NAME                                 TYPE        VALUE
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 1000M
sga_target                           big integer 1000MThanks in advance

Can any please tell me how to find out the min and max memory been used by each parameter under SGA_MAX and SGA_TARGET ? below is the db CRMS65T. If any such script is there please provide meI guess your question is, each memory components of SGA? if so
SQL> select * from v$sgainfo;
NAME                                  BYTES RES
Fixed SGA Size                      2088504 No
Redo Buffers                       18882560 No
Buffer Cache Size                 616562688 Yes
Shared Pool Size                  301989888 Yes
Large Pool Size                     4194304 Yes
Java Pool Size                      4194304 Yes
Streams Pool Size                         0 Yes
Granule Size                        4194304 No
Maximum SGA Size                  947912704 No
Startup overhead in Shared Pool   125829120 No
Free SGA Memory Available                 0Also check
SQL> select COMPONENT,CURRENT_SIZE,MIN_SIZE,MAX_SIZE,USER_SPECIFIED_SIZE from v$sga_dynamic_components;
shared pool                                                         301989888 301989888          0           209715200
large pool                                                            4194304    4194304          0             4194304
java pool                                                             4194304    4194304          0             4194304
streams pool                                                                0          0          0                   0
DEFAULT buffer cache                                                616562688 616562688          0           603979776
KEEP buffer cache                                                           0          0          0                   0
RECYCLE buffer cache                                                        0          0          0                   0
DEFAULT 2K buffer cache                                                     0          0          0                   0
DEFAULT 4K buffer cache                                                     0          0          0                   0
DEFAULT 8K buffer cache                                                     0          0          0                   0
DEFAULT 16K buffer cache                                                    0          0          0                   0
DEFAULT 32K buffer cache                                                    0          0          0                   0
ASM Buffer Cache                                                            0          0          0           603979776
13 rows selected.
SQL>Edited by: CKPT on Sep 19, 2011 8:55 AM

Database selection through use of a parameter

Similar Messages

Maybe you are looking for