How many types of ports are there which we use for data transfe in ale/idoc

friends let me know how many types of ports  are there which we use for transfering
data in ale/idocs?

Hello,
you can use file port,trnasactional RFC port.FI you are using IDOC-XML conversion combination,then you can XML port also.
Thanks

Similar Messages

  • How many types of rfcs are there

    Hello,
    Can any body explain about how many type of rfcs are there. give the difference also.
    Thanks.

    Hi,
    Check this info.
    These are the types of RFC
    Asynchronous RFC (aRFC)
    Synchronous RFC (sRFC)
    Transactional RFC (tRFC)
    Queued RFC (qRFC)
    Parallel RFC (pRFC)
    Asynchronous RFC :
    This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .
    Transactional RFC
    This let you group one or more function module call together o tRFC LUW and ensure that fucnction module within LUW is called once . In contrast to aRFC and sRFC the tRFC belonging to tRFC LUW are executed in order .
    tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls are
    1.Executed in the order in which they are called
    2.Executed in the same program context in the target system
    3.Run as a single transaction: they are either committed or rolled back as a unit.
    Implementation of tRFC is recommended if you want to guarantee that the transactional order of the calls is preserved
    Asynchronous remote function calls (aRFCs) are similar to transactional RFCs, in that the user does not have to wait for their completion before continuing the calling dialog. There are three characteristics, however, that distinguish asynchronous RFCs from transactional RFCs:
    • When the caller starts an asynchronous RFC, the called server must be available to accept the request.
    The parameters of asynchronous RFCs are not logged to the database, but sent directly to the server.
    • Asynchronous RFCs allow the user to carry on an interactive dialog with the remote system.
    • The calling program can receive results from the asynchronous RFC.
    You can use asynchronous remote function calls whenever you need to establish communication with a remote system, but do not want to wait for the function’s result before continuing processing. Asynchronous RFCs can also be sent to the same system. In this case, the system opens a new session (or window). You can then switch back and for between the calling dialog and the called session
    RECEIVE RESULTS FROM FUNCTION Remotefunction is used within a FORM routine to receive the results of an asynchronous remote function call. The following receiving parameters are available:
    IMPORTING
    TABLES
    EXCEPTIONS
    The addition KEEPING TASK prevents an asynchronous connection from being closed after receiving the results of the processing. The relevant remote context (roll area) is kept for re-use until the caller terminates the connection.
    Transactional RFC (tRFC) and Queued RFC (qRFC).
    tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
    Transactional RFC:
    If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
    To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
    Disadvantages of tRFC
    - tRFC processes all LUWs independent of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
    - In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
    Queued RFC:
    When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
    Therefore, Queued RFC is better than Transactional RFC.
    Remote Function Call:
    RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.
    RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.
    RFCs manage the communication process, parameter transfer and error handling.
    http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
    Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
    Synchronous RFC:
    The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.
    Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).
    Transactional RFC:
    If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.
    To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.
    Queued RFC:
    When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously
    For more information on RFC, please go through the link.
    http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm
    Have a look at this link.
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.
    Rewords some points.
    Rgds,
    P.Nag

  • How many  types of joins are there?

    how many  types of joins are there?
    Edited by: Alvaro Tejada Galindo on Feb 21, 2008 4:58 PM

    Hi,
    Joins are used to fetch data fast from Database tables:
    Tables are joined with the proper key fields to fetch the data properly.
    If there are no proper key fields between tables don't use Joins;
    Important thing is that don't USE JOINS FOR CLUSTER tableslike BSEG and KONV.
    Only use for Transparenmt tables.
    You can also use joins for the database VIews to fetch the data.
    JOINS
    ... FROM tabref1 INNER JOIN tabref2 ON cond
    The data is to be selected from transparent database tables and/or views determined by tabref1 and tabref2. tabref1 and tabref2 each have the same form as in variant 1 or are themselves Join expressions. The keyword INNER does not have to be specified. The database tables or views determined by tabref1 and tabref2 must be recognized by the ABAP Dictionary.
    In a relational data structure, it is quite normal for data that belongs together to be split up across several tables to help the process of standardization (see relational databases). To regroup this information into a database query, you can link tables using the join command. This formulates conditions for the columns in the tables involved. The inner join contains all combinations of lines from the database table determined by tabref1 with lines from the table determined by tabref2, whose values together meet the logical condition (join condition) specified using ON>cond.
    Inner join between table 1 and table 2, where column D in both tables in the join condition is set the same:
    Table 1 Table 2
    A  B  C  D    D  E  F  G  H 
    a1  b1  c1  1    1  e1  f1  g1  h1 
    a2  b2  c2  1    3  e2  f2  g2  h2 
    a3  b3  c3  2    4  e3  f3  g3  h3 
    a4  b4  c4  3    -
    Inner Join
    A  B  C  D  D  E  F  G  H 
    a1  b1  c1  1  1  e1  f1  g1  h1 
    a2  b2  c2  1  1  e1  f1  g1  h1 
    a4  b4  c4  3  3  e2  f2  g2  h2 
    Example
    Output a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
    DATA: DATE LIKE SFLIGHT-FLDATE,
    CARRID LIKE SFLIGHT-CARRID,
    CONNID LIKE SFLIGHT-CONNID.
    SELECT FCARRID FCONNID F~FLDATE
    INTO (CARRID, CONNID, DATE)
    FROM SFLIGHT AS F INNER JOIN SPFLI AS P
    ON FCARRID = PCARRID AND
    FCONNID = PCONNID
    WHERE P~CITYFROM = 'FRANKFURT'
    AND P~CITYTO = 'NEW YORK'
    AND F~FLDATE BETWEEN '20010910' AND '20010920'
    AND FSEATSOCC < FSEATSMAX.
    WRITE: / DATE, CARRID, CONNID.
    ENDSELECT.
    If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or a table alias.
    In order to determine the result of a SELECT command where the FROM clause contains a join, the database system first creates a temporary table containing the lines that meet the ON condition. The WHERE condition is then applied to the temporary table. It does not matter in an inner join whether the condition is in the ON or WHEREclause. The following example returns the same solution as the previous one.
    Example
    Output of a list of all flights from Frankfurt to New York between September 10th and 20th, 2001 that are not sold out:
    DATA: DATE LIKE SFLIGHT-FLDATE,
    CARRID LIKE SFLIGHT-CARRID,
    CONNID LIKE SFLIGHT-CONNID.
    SELECT FCARRID FCONNID F~FLDATE
    INTO (CARRID, CONNID, DATE)
    FROM SFLIGHT AS F INNER JOIN SPFLI AS P
    ON FCARRID = PCARRID
    WHERE FCONNID = PCONNID
    AND P~CITYFROM = 'FRANKFURT'
    AND P~CITYTO = 'NEW YORK'
    AND F~FLDATE BETWEEN '20010910' AND '20010920'
    AND FSEATSOCC < FSEATSMAX.
    WRITE: / DATE, CARRID, CONNID.
    ENDSELECT.
    Since not all of the database systems supported by SAP use the standard syntax for ON conditions, the syntax has been restricted. It only allows those joins that produce the same results on all of the supported database systems:
    Only a table or view may appear to the right of the JOIN operator, not another join expression.
    Only AND is possible in the ON condition as a logical operator.
    Each comparison in the ON condition must contain a field from the right-hand table.
    If an outer join occurs in the FROM clause, all the ON conditions must contain at least one "real" JOIN condition (a condition that contains a field from tabref1 amd a field from tabref2.
    In some cases, '*' may be specified in the SELECT clause, and an internal table or work area is entered into the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the FROM clause, according to the structure of each table work area. There can then be gaps between table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, not simply by counting the total number of fields. For an example, see below:
    Variant 3
    ... FROM tabref1 LEFT OUTER JOIN tabref2 ON cond
    Effect
    Selects the data from the transparent database tables and/or views specified in tabref1 and tabref2. tabref1 und tabref2 both have either the same form as in variant 1 or are themselves join expressions. The keyword OUTER can be omitted. The database tables or views specified in tabref1 and tabref2 must be recognized by the ABAP-Dictionary.
    In order to determine the result of a SELECT command where the FROM clause contains a left outer join, the database system creates a temporary table containing the lines that meet the ON condition. The remaining fields from the left-hand table (tabref1) are then added to this table, and their corresponding fields from the right-hand table are filled with ZERO values. The system then applies the WHERE condition to the table.
    Left outer join between table 1 and table 2 where column D in both tables set the join condition:
    Table 1 Table 2
    A  B  C  D    D  E  F  G  H 
    a1  b1  c1  1    1  e1  f1  g1  h1 
    a2  b2  c2  1    3  e2  f2  g2  h2 
    a3  b3  c3  2    4  e3  f3  g3  h3 
    a4  b4  c4  3    -
    Left Outer Join
    A  B  C  D  D  E  F  G  H 
    a1  b1  c1  1  1  e1  f1  g1  h1 
    a2  b2  c2  1  1  e1  f1  g1  h1 
    a3  b3  c3  2  NULL NULL NULL NULL NULL
    a4  b4  c4  3  3  e2  f2  g2  h2 
    Example
    Output a list of all custimers with their bookings for October 15th, 2001:
    DATA: CUSTOMER TYPE SCUSTOM,
    BOOKING TYPE SBOOK.
    SELECT SCUSTOMNAME SCUSTOMPOSTCODE SCUSTOM~CITY
    SBOOKFLDATE SBOOKCARRID SBOOKCONNID SBOOKBOOKID
    INTO (CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
    BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
    BOOKING-BOOKID)
    FROM SCUSTOM LEFT OUTER JOIN SBOOK
    ON SCUSTOMID = SBOOKCUSTOMID AND
    SBOOK~FLDATE = '20011015'
    ORDER BY SCUSTOMNAME SBOOKFLDATE.
    WRITE: / CUSTOMER-NAME, CUSTOMER-POSTCODE, CUSTOMER-CITY,
    BOOKING-FLDATE, BOOKING-CARRID, BOOKING-CONNID,
    BOOKING-BOOKID.
    ENDSELECT.
    If there are columns with the same name in both tables, you must distinguish between them by prefixing the field descriptor with the table name or using an alias.
    Note
    For the resulting set of a SELECT command with a left outer join in the FROM clause, it is generally of crucial importance whether a logical condition is in the ON or WHERE condition. Since not all of the database systems supported by SAP themselves support the standard syntax and semantics of the left outer join, the syntax has been restricted to those cases that return the same solution in all database systems:
    Only a table or view may come after the JOIN operator, not another join statement.
    The only logical operator allowed in the ON condition is AND.
    Each comparison in the ON condition must contain a field from the right-hand table.
    Comparisons in the WHERE condition must not contain a field from the right-hand table.
    The ON condition must contain at least one "real" JOIN condition (a condition in which a field from tabref1 as well as from tabref2 occurs).
    Note
    In some cases, '*' may be specivied as the field list in the SELECT clause, and an internal table or work area is entered in the INTO clause (instead of a list of fields). If so, the fields are written to the target area from left to right in the order in which the tables appear in the llen in der FROM clause, according to the structure of each table work area. There can be gaps between the table work areas if you use an Alignment Request. For this reason, you should define the target work area with reference to the types of the database tables, as in the following example (not simply by counting the total number of fields).
    Example
    Example of a JOIN with more than two tables: Select all flights from Frankfurt to New York between September 10th and 20th, 2001 where there are available places, and display the name of the airline.
    DATA: BEGIN OF WA,
    FLIGHT TYPE SFLIGHT,
    PFLI TYPE SPFLI,
    CARR TYPE SCARR,
    END OF WA.
    SELECT * INTO WA
    FROM ( SFLIGHT AS F INNER JOIN SPFLI AS P
    ON FCARRID = PCARRID AND
    FCONNID = PCONNID )
    INNER JOIN SCARR AS C
    ON FCARRID = CCARRID
    WHERE P~CITYFROM = 'FRANKFURT'
    AND P~CITYTO = 'NEW YORK'
    AND F~FLDATE BETWEEN '20010910' AND '20010920'
    AND FSEATSOCC < FSEATSMAX.
    WRITE: / WA-CARR-CARRNAME, WA-FLIGHT-FLDATE, WA-FLIGHT-CARRID,
    WA-FLIGHT-CONNID.
    ENDSELECT.

  • How many types of messages are there what are they?

    How many types of messages are there? what are they?

    Hi,
    Refer the Demo program this iwll help
    <b>DEMO_MESSAGES</b>
    1. MESSAGE xnnn.
    2. MESSAGE ID id TYPE mtype NUMBER n.
    3. MESSAGE xnnn(mid).
    Effect
    Sends a message. Messages are stored in table T100, and can be maintained using Transaction SE91. They are fully integrated in the forward navigation of the ABAP Workbench.
    The ABAP runtime environment handles messages according to the message type specified in the MESSAGE statement and the context in which the message is sent. There are six kinds of message type:
    A (Abend)
    Termination
    E (Error)
    Error
    I (Info)
    Information
    S (Status)
    Status message
    W (Warning)
    Warning
    X (Exit)
    Termination with short dump
    Messages are used primarily to handle user input on screens. The following table shows how each message type behaves in different contexts. The numbers are explained at the end of the table.
    A E I S W X
    PAI module 1 2 3 4 5 6
    PAI module at POH 1 7 3 4 7 6
    PAI module at POV 1 7 3 4 7 6
    AT SELECTION-SCREEN ... 1 8 3 4 9 6
    AT SELECTION-SCREEN at POH 1 7 3 4 7 6
    AT SELECTION-SCREEN at POV 1 7 3 4 7 6
    AT SELECTION-SCREEN ON EXIT 1 7 3 4 7 6
    AT LINE-SELECTION 1 10 3 4 10 6
    AT PFn 1 10 3 4 10 6
    AT USER-COMMAND 1 10 3 4 10 6
    INITIALIZATION 1 11 3 4 11 6
    START-OF-SELECTION 1 11 3 4 11 6
    GET 1 11 3 4 11 6
    END-OF-SELECTION 1 11 3 4 11 6
    TOP-OF-PAGE 1 11 3 4 11 6
    END-OF-PAGE 1 11 3 4 11 6
    TOP-OF-PAGE DURING ... 1 10 3 4 10 6
    LOAD-OF-PROGRAM 1 1 4 4 4 6
    PBO module 1 1 4 4 4 6
    AT SELECTION-SCREEN OUTPUT 1 1 4 4 4 6
    reward if this helps.

  • How many types of messages are there

    Hi,
    After using CALL TRANSACTION tcode USING gi_bdcdata
                     MODE   gv_ctumode
                     UPDATE gv_cupdate
                     MESSAGES INTO gi_messtab.
    I am looping gi_messtab for extracting messages.
    I know msgtyp = 'E'    -
    > means error message.
    I want to how many types of messages are there, tell me with the full forms.
    s -
    > means?
    LOOP AT gi_messtab.
    IF gi_messtab-msgtyp = 'E'.
    endif.
    endloop.

    HI Mohan
    A --> Termination Message
    The message appears in a dialog box, and the program terminates. When the user has confirmed the message, control returns to the next-highest area menu.
    E -->  Error Message
    Depending on the program context, an error dialog appears or the program terminates.
    I --> Information
    The message appears in a dialog box. Once the user has confirmed the message, the program continues immediately after the MESSAGE statement.
    S -->  Status Message and Sucess message
    The program continues normally after the MESSAGE statement, and the message is displayed in the status bar of the next screen.
    W --> Warning
    Depending on the program context, an error dialog appears or the program terminates.
    X --> Exit
    No message is displayed, and the program terminates with a short dump. Program terminations with a short dump normally only occur when a runtime error occurs. Message type X allows you to force a program termination. The short dump contains the message ID.
    Regards
    Sudheer

  • How many types of requests are there

    hai,
    how many types of requests are there plz explain it plzzzzzzzzzzz
    thanks and regards,
    pg babu

    Hi ,
    We are not at all clear about your query here. Please let us know what kind of requests you are telling about. Is it regarding data base requests?
    Regards,
    Abhisek

  • How many types of servlets are there

    posted June 12, 2006 03:36 AM
    HI EveryOne
    what are the different types of servlets.
    If we want to write our own servlet for particular protocol
    what to do ?

    I don't think it goes as far as needing to change the server. You just have to do a bunch of subclassing and servlet mapping.
    I would start with a subclass of GenericServlet that mimics the functionality of HttpServlet. For example, if I had an FtpServlet it might override the service method to read the FTP request and forward it to a doUser, doPass, doChangeWorkingDirectory, doQuit, doPort, doMode, doRetrieve, doStore, doAppend, etc... methods (there are a lot of commands for FTP.
    You would probably want to make FtpServletRequest and FtpServletResponse classes as well. For instance, your FtpServlet would probably make an FtpServletRequest (that would double as the user's FTP session since FTP really is a sequence of requests) that stores all the user's previous commands and their order. It is maintained (probably mapped to the user's IP address) on a per-user basis until they doQuit.
    The FtpServletResponse would be a a little more complicated. I would probably design it to do the data transfer part of FTP. It would then be a Thread that managed a URLConnection to the client to get or send data to.
    You design your servlets to extend your FtpServlet and override those methods whose default functionality you want to change and maybe design a good wrapping system to make it easy to do the different FtpResponses that would be required.
    You configure the server to listen to port 21, and your firewall to allow two way traffic on port 20. You would map all incoming calls to a default FtpServlet whose actual class you define in web.xml.
    I think you then have a working FtpServlet without the need to force the web server to recognize that it is doing it.
    Come to think of it, you probably wouldn't need a lot of subclassing of the FtpServlet. Probably just one for every site you want to host (would you want to have special cases for specific files?).
    I guess the real room for developement would be to get an FTP command that does one of the myriad of FTP actions. As you develope them you could probably use servlet parameters in web.xml to define which class to call for each of the actions...
    I digress. What meant to say was that all you have to do is some subclassing and URL mapping. No real change to the server itself.

  • How many types of exits are there...

    explain each exit with a simple easy example...
    Message was edited by:
            balaji velpuri

    explain each exit with a simple easy example...
    Message was edited by:
            balaji velpuri

  • What is buffer? how many types of buffers r there?

    how many types of joins r there?
    thank u.

    Whenever an Open SQL statement is used to read a record,
    the data buffer is checked first to see whether it is there. If not, the data is read from the database.
    If the table's attributes indicate that the data should be buffered,
    the record is saved in RAM on the application server in data buffers.
    Later, if that record is read again, it is read from the buffer instead of the database.
    By buffering data, you increase performance in two important ways:
    The programs using the buffered data run faster because they don't have to wait for it to come from the database. This reduces delays waiting for the database and the network that connects it.
    The other programs that need to access the database run faster because there is less load on the database and less traffic on the network.
    Three types of buffering are possible:
    Full Buffering
    With full buffering, either the entire table is in the buffer or the table is not in the buffer at all. All
    the records of the table are loaded into the buffer when one record of the table is read.
    In this example, a program reads the record highlighted in red from table
    SCOUNTER. If the table is fully buffered, all the records of the table are loaded into
    the buffer.
    Application server
    The buffered data records are sorted in the buffer by table key. Accesses to the
    buffered data can therefore only analyze field contents up to the last specified key
    field for restricting the dataset to be searched.
    The left-justified part of the key should therefore be as large as possible in such
    accesses. For example, if you do not define the first key field, the system has to scan
    the full table. In this case direct access to the database can be more efficient if the
    database has suitable secondary indexes [Page 61].
    When Should you Use Full Buffering?
    When deciding whether a table should be fully buffered, you should take into account the size of
    the table, the number of read accesses, and the number of write accesses. Tables best suited to
    full buffering are small, read frequently, and rarely written.
    Full buffering is recommended in the following cases:
    BC - ABAP Dictionary SAP AG
    Full Buffering
    36 December 1999
    • Tables up to 30 KB in size. If a table is accessed frequently, but all accesses are read
    accesses, this value can be exceeded. However, you should always pay attention to the
    buffer utilization.
    • Larger tables where large numbers of records are frequently accessed. If these mass
    accesses can be formulated with a very selective WHERE condition using a database
    index [Page 61], it could be better to dispense with buffering.
    • Tables for which accesses to non-existent records are frequently submitted. Since all the
    table records reside in the buffer, the system can determine directly in the buffer whether
    or not a record exists.
    SAP AG BC - ABAP Dictionary
    Generic Buffering
    With generic buffering, all the records in the buffer whose generic key fields match this record are
    loaded when one record of the table is accessed. The generic key is a part of the primary key of
    the table that is left-justified.
    In this example, the record highlighted in red is read by a program from table
    SCOUNTER. If the table is generically buffered, all the records read whose generic
    key fields (MANDT and CARRID) agree are loaded into the buffer.
    Application server
    When Should you Use Full Buffering?
    A table should be buffered generically if only certain generic areas of the table are normally
    needed for processing.
    Client-specific, fully-buffered tables are automatically generically buffered since normally it is not
    possible to work in all clients at the same time on an application server. The client field is the
    generic key.
    Language-specific tables are another example where generic buffering is recommended. In
    general, only records of one language will be needed on an application server. In this case, the
    generic key includes all the key fields up to and including the language field.
    How Should you Define the Generic Key?
    In generic buffering, it is crucial to define a suitable generic key.
    BC - ABAP Dictionary SAP AG
    Generic Buffering
    If the generic key is too small, the buffer will contain a few very large areas. During access, too
    much data might be loaded in the buffer.
    If the generic key is too large, the buffer might contain too many small generic areas. These can
    reduce buffer performance since there is an administrative entry for every buffered generic area.
    It is also possible that too many accesses will bypass the buffer and go directly to the database,
    since they do not fully define the generic key of the table. If there are only a few records in each
    generic area, it is usually better to fully buffer the table.
    Only 64 bytes of the generic key are used. You can specify a longer generic key, but the part of
    the key exceeding 64 bytes is not used to create the generic areas.
    Access to Buffered Data
    It only makes sense to generically buffer a table if the table is accessed with fully-specified
    generic key fields. If a field of the generic key is not assigned a value in a SELECT statement, it
    is read directly from the database, bypassing the buffer.
    If you access a generic area that is not in the buffer with a fully-specified generic key, you will
    access the database to load the area. If the table does not contain any records in the specified
    area ("No record found"), this area in the buffer is marked as non-existent. It is not necessary to
    access the database if this area is needed again.
    SAP AG BC - ABAP Dictionary
    Single-Record Buffering
    With single-record buffering, only the records that are actually read are loaded into the buffer.
    Single-record buffering therefore requires less storage space in the buffer than generic and full
    buffering. The administrative costs in the buffer, however, are greater than for generic or full
    buffering. Considerably more database accesses are necessary to load the records than for the
    other buffering types.
    In this example, the record highlighted in red is read by a program from table
    SCOUNTER. If single-record buffering is selected for the table, only the record that
    was read is loaded into the buffer.
    When Should you Use Single-Record Buffering?
    Single-record buffering should be used particularly for large tables where only a few records are
    accessed with SELECT SINGLE. The size of the records being accessed should be between 100
    and 200 KB.
    Full buffering is usually more suitable for smaller tables that are accessed frequently. This is
    because only one database access is necessary to load such a table with full buffering, whereas
    several database accesses are necessary for single-record buffering.
    Access to Buffered Data
    All accesses that are not submitted with SELECT SINGLE go directly to the database, bypassing
    the buffer. This applies even if the complete key is specified in the SELECT statement.
    BC - ABAP Dictionary SAP AG
    Single-Record Buffering
    40 December 1999
    If you access a record which is not yet buffered with SELECT SINGLE, there is a database
    access to load the record. This record is marked in the buffer as non-existent if the table does not
    contain a record with the specified key.

  • How many iPad charging cables are there?

    How many iPad charging cables are there?  Anyone know 'officially'?

    I suggest you ask the question you are really trying to discover the answer to; for example:
    "I need a new charging cable for my iPad 2.  I see there are three different charging cables at the Apple Store.  One has a lightning connector.  One has a 30 pin connector.  The third has an L-shaped connector.  Which one (or ones) of these would work for my iPad 2?"

  • How many standard business roles are there in CRM

    Hi Experts,
    I had a question in one of my exam.. please answer it
    question:- How many standard business roles are there in CRM?
    options were:- 2,3,4,5
    I think the options does not have the right answer , upto my knowledge it is more than 5. please help me with the appropriate answer
    Thanks
    Rahul Mathur

    Hi,
    There are approximately 40 standard business roles available in the latest version ehp3.
    As the version changes the business roles increases. Initially  there are only 3 std business roles..
    1.sales pro 2. marketing pro 3. service pro and along with IC Agent.
    Each BR above is loaded with huge no of transactions even though our aim is to for ex: create sales order...we use sales pro but all the sales related operations(transactions) are being loaded in to the system so along with the version improvements/releases SAP have divided each of these std BR as much as they can and thus the no of operations or transactions per BR is decreasing with each release....
    Thanks & Regards,
    Malleswar.

  • How can we find out the disk which is used for a mount point

    How can we find out the disk which is used for a mount point?
    one of our mount point(/u03/oracle/prod) was using high I/O and this was causing slowness in the server.
    I can see a disk operation error in errpt at the same time as below. Wanted to check whether the mount point /u03/oracle/prod is using the disk hdisk31
    $errpt|more
    IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
    DXB78877 1125032114 T H hdisk31 DISK OPERATION ERROR
    OS version:AIX 6.1
    DB:11.2.0.2

    this is the output for cat /etc/filesystem
    /u02:
            dev             = /dev/fslv00
            vfs             = jfs2
            log             = /dev/loglv00
            mount           = true
            options         = rw
            account         = false
    /u01:
            dev             = /dev/fslv01
            vfs             = jfs2
            log             = /dev/loglv00
            mount           = true
            options         = rw
            account         = false

  • HT5287 If DVD Movies, Audio CD's and even burning CD and DVD's are not supported, what is the point of DVD & CD Sharing then? Wouldn't it just be better to remote in or use a thumb drive if it's only able to be used for data transfer?

    If DVD Movies, Audio CD's and even burning CD and DVD's are not supported, what is the point of DVD & CD Sharing then? Wouldn't it just be better to remote in or use a thumb drive if it's only able to be used for data transfer?
    Or am I missing the bigger picture?

    As long as you have a Superdrive or an external burner/drive, burning, watching, installing, etc. from CD or DVD will work just fine. And so will sharing.

  • Message type for data transfer through ALE

    Hi Gurus,
    I am working on master data transfer throgh ALE.We want to transfer data from Dev. server to Quality server.Here the client is same that is 123.We have defined logical systems and RFC also.Now for transferring inspection characteristic what is the message type that should be used in transaction BD64.please help.
    Regards
    Amit

    not found any replies

  • Are there any timesten installation for data warehouse environment?

    Hi,
    I wonder if there is a way to install timesten as an in memory database for data warehouse environment?
    The DW today consist of a large Oralcle database and I wonder if and how a timesten implementation can be done.
    what kind of application changes involve with such an implementation and so on?
    I know that the answer is probably complex but if anyone knows about such an implementation and some information about it , it would be great to learn from that experience.
    Thanks,
    Adi

    Adi,
    It depends on what you want to do with the data in the TimesTen database. If you know the "hot" dataset that you want to cache in TimesTen, you can use Cache Connect to Oracle to cache a subset of your Oracle tables into TimesTen. The key is to figure out what queries you want to run and see if the queries are supported in TimesTen.
    Assuming you know the dataset you need to cache and you have control of your application code to change the connection to TimesTen (using ODBC or JDBC), you can give it a try. If you are using a third party tool, you need to see if the tool supports JDBC or ODBC access to the database and change the tool to point to your TimesTen database instead of the Oracle database.
    If you are using the TimesTen Cache Connect to Oracle product option, data synchronization between Oracle and TimesTen is handled automatically by the product.
    Without further details of what you'd like to do, it's difficult to provide more detailed recommendation.
    -scheung

Maybe you are looking for

  • Currency symbol in report

    Hi, Please let me know if there is any FM to convert USD to $ and also other country currency symbols. let me know if there are any standard tables in sap which are related to this. regards, Lakshmikanth.T.V

  • How about a hard-shell case for the Zen Mic

    I recently bought my Zen Micro and the one accessory that I still need to pick up for it is a case. Now I know there is a pouch for it, but what I really want is a something more protecti've to put up with the rigors of travelling. I see they have th

  • Adpatch gives relinking errors

    Hi, I am upgrading from 12.1.1 to 12.1.3 on RHEL 6.3. I have the following error when I ran adpatch for 9239089. Starting  link of product 'ad' on Mon Apr  8 11:37:07 CDT 2013 Current product is  ad Current product _TOP is  $AD_TOP Current prodarea i

  • Exception in thread "main" org.apache.axis2.AxisFault: Error in extracting

    I am getting this exception when I call the web service from the client. Please help me here. Exception in thread "main" org.apache.axis2.AxisFault: Error in extracting message properties      at org.apache.rampart.handler.RampartSender.invoke(Rampar

  • [SOLVED] Problem with adding package update count to dwm's status bar

    Following http://www.andreascarpino.it/blog/posts - s-part-ii/, I added: $ crontab -l */10 * * * * ~/bin/tempdb Along with #!/bin/bash # ~/bin/tempdb fakedb=/dev/shm/fakepacdb realdb=/var/lib/pacman [[ ! -d $fakedb ]] && { mkdir -p "$fakedb/sync" ||