High volumn data send from R/3

Hi
I want to send the high volum data like 10 MB file (per day at once). Which is the better method to send the data? (RFC,IDOC,XML,PROXY...)
Ravi

Hi,
If you use a file for doing that, you can zip and unzip it using the steps explained in this blog:
SAP XI acting as a (huge) file mover
/people/alessandro.guarneri/blog/2007/02/21/sap-xi-acting-as-a-huge-file-mover
or
Zip or Unzip your Payload with the new PayloadZipBean module of the XI Adapter Framework
/people/stefan.grube/blog/2007/02/20/working-with-the-payloadzipbean-module-of-the-xi-adapter-framework
Hope this helps you.

Similar Messages

Encrypt data send from a non-SAP system to ECC.

Hi,
We are tryign to encrypt the credit card details send from web (non-sap system) via a xml file to ECC.
From Basis side, I have exported the public key from the ECC for the web server to encrypt the CC details while sending via xml.
The external web consultants encrypted the cc detail with the public key and send it via xml but that was not able to decrypt at the ECC side.
The developers were using the FM 'CCARD_DEVELOPE'at ECC to decrypt the data in the xml file. It was saying SSF error: No data transfered.
Meanwhile SAP CryptoLib is installed and credit card encryption/decryption is working fine for CC details entered via GUI interface.
Is there anything I am missing out here to encrypt CC details send from a Non-SAP system to ECC.? Do we need to load the SAP cryptolib in the non-SAP system to ecrypt this data at the senders end. Or is there a alternate solution for this ?
We are in ECC6.0/RHEL/Oracle10204.
Appreciate your help.
Thanks

Hi Nelis,
Thanks for your reply.
This note does not get any information regarding encrypting data from a non-SAP system to SAp system.
I am looking setup/information for encrypting data from a non-SAP system to SAP system.
Thanks

USB data manipulation from Java to all OS

Hello currently I'm developing on a software where I need to detect the USB Device and get access to the data send from the USB Devices. I googled but couldn't find the perfect library for usb for all platform. My program is used by many clients of different platform but I couldn't find solution. Please do you have known any library for this?
Thanks in advance.

Tracy,
<quote>â¦ only on row #40, the internet connection is lost. The only way the user can tell what happened is to look at the entire screen and reverify ALL the data in order to tell what got saved/resaved and what didn't</quote>
That would be "the only way" if the Java programmers had decided to totally bury the error â¦ what should happen here is the end-user should get a proper error message â¦ no need to re-verify at this point since all bets are off (in fact, nothing shouldâve been changed in the database).
Nonetheless, your concerns regarding the chosen approach are valid â¦ making multiple calls to the database after a Save makes controlling a business transaction rather complex (in an n-tier system) â¦ they should make one call only to the database passing in all the data to be saved â¦ one database transaction â¦ either all changes get applied or none.
The fact that lots of data may need to be passed in for one Save is of no relevance â¦ if you have to carry 500Kb of data for that screen then, well, you have to do it â¦ 1 bucket of 500Kb or 50 buckets of 10Kb? â¦ it doesnât really matter as far as the actual transport part is concerned.
As already answered, one can pass complex types in pl/sql â¦ so one database call per Save would be my first random thought. There are lots of suspect things in here â¦ some things you didnât mentioned at all â¦ like how is concurrency addressed? â¦ have you/they implemented some sort of optimistic locking mechanism? Of course the architecture of your system wonât be solved in a forum â¦ so, finding a good system/data/Oracle architect on site for the project would be my second random thought.
PS. One last random thought â¦ fight off that idea of packing and sending large strings (XML or not) â¦ if the data is structured then contemplate XML for no more than few seconds.

Acquiring High resolution data from usb mouse movement

Is there a way of acquiring high resolution data from the movement of a usb mouse? I have a NI PCI 6221 daq card to use. I have a Pentium 4 PC with 1 Gb of RAM. I need to get the position, velocity and acceleration of the mouse.
Is there a way to do it with the above hardware.
Thanks in advance

I don't see how you could use a PCI-6221 to get high resolution mouse movement measurements. The PCI-6221 can acquire voltages at up to 250kS/s, but what voltage would you measure? It could also read in digital data at 1MHz, but you would have to be able to understand the USB communication protocol your mouse uses, and I doubt that your mouse vendor will give out that information. You might be able to take your mouse apart and hook up leads to the sensors around the trackball and do a sort of quadrature encoder application, but there's no guarantee we're dealing with TTL digital signals here (you might even be using an optical mouse!).
Your best option - and I have no idea how good this option is - is to use the driver already installed for your usb mouse. What software application are you going to use to program your application that will measure the mouse movements?
If you would consider using LabVIEW, you could set up an event structure to capture mouse movements across the front panel. Each event registered includes a timestamp from the CPU's millisecond clock as well as the coordinates of the mouse. If you stored up a buffer of previous mouse positions and times, you could infer a velocity, perhaps with the help of interpolation functions.
All of this would have somewhere on the level of millisecond timing accuracy. Were you envisioning something else?
Jarrod S.
National Instruments

How do you change the position of email sender so that it's on the left (sender[from], subject and date received)

How do you change the position of email sender so that it's on the left (sender[from], subject and date received)

In the Thread Pane where your messages are listed?
You see that bar with the labels "From", "Subject", "Date" and so on? Well, they are buttons. You can click on them to sort your messages. You can also drag them with the mouse left and right to reposition them, and you can drag their ends to change the column widths.
These are standard computer actions; you can do all of this in Windows Explorer ("My Computer") too.
In Thunderbird, a right-click on any of these buttons will reveal a pop-up menu where you can select and deselect the columns to control what is shown.
More here: http://www.ramsden.org.uk/8_How_to_sort.html

Can we send the data into different data target from single datasource how

Hai
can we send the data into different data target from single datasource how ?

Hi,
Create the transformation for each target and connect through DTP if you are in BI 7.0
If it is BW 3.5 create transfer rules and load it Info source and then different update rules for different targets then load it using IP.
If you are speaking about loading data from R3 data source to multiple data sources in BI
Then follow the below step.
1)create init IP's and run the IP's with different selection to different DSO(With same selection it is not possible).
2)Then you will have different delta queues for the same data source in RSA7
3)Your delta loads will run fine to different data sources from same DS in R3.
Hope this helps
Regards,
Venkatesh

How to select the data efficiently from the table

hi every one,
i need some help in selecting data from FAGLFLEXA table.i have to select many amounts from different group of G/L accounts
(groups are predefined here which contains a set of g/L account no.).
if i select every time for each group then it will be a performance issue, in order to avoid it what should i do, can any one suggest me a method or a smaple query so that i can perform the task efficiently.

Hi ,
1.select and keep the data in internal table
2.avoid select inside loop ..endloop.
3.try to use for all entries
check the below details
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

Candidate Data transfer from E-Recruiting System to HR system for New Hiring.

Hi All,
Hope everyone doing in good Spirit.
We are implementing E-Recruiting as Standalone for one of our client.
Can any please help me in regards with Data transfer from E-Rec System to HR System for hiring once the candidate has been successfully completed recruiting process.
You inputs are highly appreciable.
Thank you.
Sekhar.

Hello Sekhar,
there are three different scenarios for transferring the data of an external candidate to the HR core for hiring.
the easiest and most commonly used is the RFC connection. When creating an activity of category data transfer the data of the candidate is transferred from eRec to HR core. There it is stored in table T752F. Then you can run transaction PA48. There you can select the candidate and run a hiring action. This is the same action like in PA40 only the system will preset the fields with the values from eRec (similar to batch input).
Instead of using the RFC solution you can transfer the data using PI (this can be activated using a switch in T77S0). To be honest none of my customers is using this. Either they had no PI server at all or they did not use it for eRec
The third was delivered with a business function HCM_HIRE_INT_CI_1. This is based on HCM processes and forms and targeted towards customers using Talent Management Core (e.g. data for education and work experience is transferred into the TM Core infotypes 740X as contrary to the hr core standard infotypes 0022 and 0023 they are structured like the eRec ones). Of course as you can do a lot of customer enhancements to HCMP&F you can replace the behavior nearly completely. One or two of my clients discussed this solution but as far as I know none is actually using it.
The simple truth is most customers seem to not use any integration at all. The first solution is easy to activate but only covers around 13 fields. Compared to a real full blow hiring action this is not even 10% of the fields which have to be entered. So the presetting this small number of fields is not a great help especially as you have to check every information anyways. Furthermore PA48 is not very nice and lacks functions to structure the incoming records which makes it difficult to handle in large distributed organizations.
The other two options require a lot of infrastructure for small functionality. What we discussed with a client was using the new hire integration to preset a full hiring form with eRec data and then send to the candidate as offline form to gather all missing information and use this for hiring. But there were to many issues on data privacy aspects when sending a form with social security data, bank account data, etc. via email. Furthermore they required actual signatures.
Kind regards
Roman

Provide simple example for Arbitrary data sending through NI4551(DSA)

We Converted NI-DSA function palette
in LabVIEW under Application
Examples>>Advanced>>Arbitrary Output Example.
But, We not exactly getting arbitrary wave. Our arbitrary data is correct. I think there is a problem with FFT settings. So Please Provide simple example for Arbitrary data sending through NI4551(DSA)

Hello Sateesh!
First, what versions of LabVIEW and NI-DSA are you using. I have been searching around for the example you are refering too and I am not able to find it. Are you creating and arb. wave in the frequency domain and then performing an FFT to get it to the time domain? Next, remember your wave will only be as exact as the AO specs. of the hardware...
The output conversions occur simultaneously at software-programmable rates from 1.25 to 51.2 kS/s in increments of 47.684 µS/s. The analog output circuitry uses eight-times oversampling interpolators with 64-times oversampling delta-sigma modulators to generate high-quality signals. Software-programmable attenuation of 0, -20, or -40 dB is available on the output channels. The PCI-4451 has excellent amplitude flatness of ±0.2 dB within DC to 23 kHz, and a THD of -90 dB at 1 kHz.
Now, as far as obtaining other examples If you use the LabVIEW example finder and goto Hardware Input and Output>>Traditional DAQ>>Analog Output. I would also in the lower right hand corner of the Example Finder select your 4451 this will show you all examples that work with your hardware. I hope this helps a little but please give me more details we will go from there. Have a great day!
Allan S.
National Instruments

No master data transmitted from ERP to GTS

We are using ERP 4.70 with the following settings:
SAP_APPL 470 SP-Level 0031
PI 2004_1_470 SP-Level 0016
PI_BASIS 2005_1_620 SP-Level 0017
SLL_PI 720_470 SP-Level 0007
together with SAP GTS 7.2 SP-Level 09
I created the message types /SAPSLL/DEBMAS_SLL and /SAPSLL/MATMAS_SLL manually and activated them.
I try to send an customer master data to GTS but the partner will not transmitted. In the log protocoll in GTS the error message appears that there was no data collected from table SAPSLL/TCOGVA
If I try to send a material master from ERP to GTS the RFC connection gets broken with error message:
RFC error (The transaction has dumped the connection). What I had found out is, that the error appears in the function /SAPSLL/API_1006_SYNCH_MASS.
Has this something to do maybe with a wrong IDOC type? Does I have to to something in some tables. Do I use the wrong programme? I use /SAPSLL/MATMAS_DISTRIBUTE_R3 and /SAPSLL/DEBMAS_DISTRIBUTE_R3.
I made absolutely the same customizing settings in another system at a customer and it worked fine there.
Does anybody has an idea? Thanks to all for the possible help.
Thanks very much in advance

Hi Andreas,
there are several possibilities why this is not working.
First of all you should check, if your RFC settings are correctly maintained.
Please bear in mind that the logical systems have to be assigned to logical system groups and that GTS and R/ shall not be in teh same group.
Please also ensure that the logical system name is the same in both systems, R/3 and GTS.
Secondly there is also the possibilites that necessary tables are not filled correctly.
Please run report /SAPSLL/PLUGIN_CHECK_R3
It could be thate.g. the tables TBD24 and TBD62 are not filled
for the relevant message type (in your case /SAPSLL/DEBMAS_SLL and /SAPSLL/MATMAS_SL)
To update this tables corretly pls. do the following:
- BD53
- select message type (/SAPSLL/MATMAS_SLL)and edit it
- select a segment
- save
- deselect segment again
- activate
- set in trx BD60 the FM to the correct value
(/SAPSLL/MATMAS_DISTRIBUTE_R3)
You can than check with the programm: '/SAPSLL/PLUGIN_CHECK_R3' if
all 4 required tables (TBD24, TBD62, TBDA2, TBDME) are filled, or not.
I hope this helps with the issue.

Using ale u can send from sap to sap and sap to non sap systems

hi,
using ale u can send from sap to sap and sap to non sap systems,
then what is diff b/w ALE and EDI

Hello KALYAN KUMAR,
Application Link Enabling (ALE)
1.You distribute data using ALE if you want to communicate from one system to one or more other (mostly internal) systems.
2.ALE transfers data in IDoc format and uses the methods of tRFC for data transfer.
3.ALE enables the integration of business processes across several SAP or non-SAP systems.
Electronic Data Interchange (EDI)
1.You use EDI if you want to exchange business application documents with an (external) partner system (for example, a customer or vendor).
2. The SAP system sends EDI messages in IDoc format to an EDI subsystem, where they are converted to a universal EDI standard (UN/EDIFACT or ANSI/X12).
3. This enables communication with non-SAP systems.
By definition, two partners are involved in the process in an EDI application scenario: The sender and the recipient of an EDI message
I hope u understands the difference:)

Data loading from DSO to Cube

Hi,
I have a question,
In book TBW10 i read about the data load from DSO to InfoCube
" We feed the change log data to the InfoCube, 10, -10, and 30 add to the correct 30 value"
My question is cube already have 10 value, if we are sending 10, -10 and 30 Values(delta), the total should be 40 instead of 30.
Please some one explaine me.
Thanks

No, it will not be 40.
It ll be 30 only.
Since cube already has 10, so before image ll nullify it by sending -10 and then the correct value in after immage ll be added as 30.
so it ll be like this 10-10+30 = 30.
Thank-You.
Regards,
Vinod

CRVS2010 beta - Date field from database does not display in report

Hi there - can someone please help?!
I am getting a problem where a date field from the database does not display in the report viewer (It displays on my dev machine, but not on the client machines...details given below)
I upgraded to VS 2010
I am using the CRVS2010 Beta
My development machine is Windows 7 - and so is my fellow developer's
We are using Microsoft SQL Server 2000
We run the queries within VS and then we send the data table to VS using .SetDataSource
We have a few reports which display the date on our dev machines (whether we run the EXE or from within Visual Studio)
When we roll out to the client machines (running Windows XP SP3) then everything works, except that the date does not display (on quite a few reports)
This is the only real issue I have had - a show stopper for me
The rest works well - any input will be greatly appreciated
Regards,
Ridwan

Hi Ridwan,
After much testing I have it all working now using CRDB_adoplus.dll as a data source ( XML )
Alter your Config file to look like this:
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0"/>
</startup>
Then using the code below, and CR requires the Schema to be able to read the date format.
private void SetToXML_Click(object sender, EventArgs e)
CrystalDecisions.CrystalReports.Engine.ReportDocument rpt = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
ISCDReportClientDocument rcd;
rcd = rptClientDoc;
string connString = "Provider=SQLOLEDB;Data Source=dwcb12003;Database=xtreme;User ID=sb;Password=password";
string sqlString = "Select * From Orders";
OleDbConnection oleConn = new OleDbConnection(connString);
OleDbDataAdapter oleAdapter = new OleDbDataAdapter(sqlString, oleConn);
//OleDbDataAdapter oleAdapter2 = new OleDbDataAdapter(sqlString2, oleConn);
DataTable dt1 = new DataTable("Orders");
oleAdapter.Fill(dt1);
System.Data.DataSet ds = new System.Data.DataSet();
// We need the schema to get the data formats
ds.WriteXml("c:
sc.xml", XmlWriteMode.WriteSchema);
//Create a new Database Table to replace the reports current table.
CrystalDecisions.ReportAppServer.DataDefModel.Table boTable = new CrystalDecisions.ReportAppServer.DataDefModel.Table();
//boMainPropertyBag: These hold the attributes of the tables ConnectionInfo object
PropertyBag boMainPropertyBag = new PropertyBag();
//boInnerPropertyBag: These hold the attributes for the QE_LogonProperties
//In the main property bag (boMainPropertyBag)
PropertyBag boInnerPropertyBag = new PropertyBag();
//Set the attributes for the boInnerPropertyBag
boInnerPropertyBag.Add("File Path ", @"C:\sc.xml");
boInnerPropertyBag.Add("Internal Connection ID", "{680eee31-a16e-4f48-8efa-8765193dccdd}");
//Set the attributes for the boMainPropertyBag
boMainPropertyBag.Add("Database DLL", "crdb_adoplus.dll");
boMainPropertyBag.Add("QE_DatabaseName", "");
boMainPropertyBag.Add("QE_DatabaseType", "");
//Add the QE_LogonProperties we set in the boInnerPropertyBag Object
boMainPropertyBag.Add("QE_LogonProperties", boInnerPropertyBag);
boMainPropertyBag.Add("QE_ServerDescription", "NewDataSet");
boMainPropertyBag.Add("QE_SQLDB", "False");
boMainPropertyBag.Add("SSO Enabled", "False");
//Create a new ConnectionInfo object
CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo boConnectionInfo =
new CrystalDecisions.ReportAppServer.DataDefModel.ConnectionInfo();
//Pass the database properties to a connection info object
boConnectionInfo.Attributes = boMainPropertyBag;
//Set the connection kind
boConnectionInfo.Kind = CrConnectionInfoKindEnum.crConnectionInfoKindCRQE;
//*EDIT* Set the User Name and Password if required.
boConnectionInfo.UserName = "";
boConnectionInfo.Password = "";
//Pass the connection information to the table
boTable.ConnectionInfo = boConnectionInfo;
//Get the Database Tables Collection for your report
CrystalDecisions.ReportAppServer.DataDefModel.Tables boTables;
boTables = rptClientDoc.DatabaseController.Database.Tables;
//For each table in the report:
// - Set the Table Name properties.
// - Set the table location in the report to use the new modified table
boTable.Name = "Orders";
boTable.QualifiedName = "Orders";
boTable.Alias = "Orders";
rptClientDoc.DatabaseController.SetTableLocation(boTables[0], boTable);
//Verify the database after adding substituting the new table.
//To ensure that the table updates properly when adding Command tables or Stored Procedures.
rptClientDoc.VerifyDatabase();
MessageBox.Show("Data Source Set", "RAS", MessageBoxButtons.OK, MessageBoxIcon.Information);
Thanks again
Don

How do I use the High Speed Data Logger with multiple I/O devices?

I am using the High Speed Data Logger vi to read from a 16 channel A/D card (NI PCI-MIO-16E). The project may require more than 16 channels. How can I use High Speed Data Logger to read from two A/D cards? Will it be able to write the data to one file?

The High Speed Data Logger vi will not acquire and right to multiple DAQ boards at the same time without modification. LabVIEW is more than capable of doing this what you are trying to do, but you will have to modify the code.
Regards,
Anuj D.

Unexpected database connector error, when data sent from POJO.. Plz Help Me

Hi, Please Help me about this, I have started learning to develop a crystal report with java swing in crystal report integrated eclipse IDE 3.5 but when i am trying to send data from pojo to report file its giving error like "Unexpected database connector error" and Error code:-2147215349 Error code name:docNotReady.... please hlep me... i uploaded my program and the link to download my file is :
http://www.4shared.com/file/mz8O4iQi/SimplePojoReport.html
and i am not using any database just setting the data in the pojo...
i wrote my problem here before, but nobody replied me... so this time i uploaded my project.. please help me...
thanks...

Hell Ted Ueda,
Thanks for your reply, and did you downloaded my project files ? if not then please download it first.. because i retrieving data from the POJO not from any database.. from database its working fine but in case of POJO its not, because i wanna retrieve data dynamically from directly fields to report, means that user will fill all the information in the text box (Swing) and when he click on the button then the data from the text box should be pushed to report file and also should have to saved in the database.. so please download my project file... and help me...
link : http://www.4shared.com/file/mz8O4iQi/SimplePojoReport.html
thanking you..
Arun...

High volumn data send from R/3

Similar Messages

Maybe you are looking for