Tables Statement in ABAP HR

Hi,
I came across a statment of Table declaration using * with the table name.
Example: TABLES: *PA0001.
Can somebody please let me know what does this mean exactly.
Thanks in advance.
Somu

Hi Somu,
There might be a case where this code which you would have seen has a typo error.
Tables : * PA0001 is not correct syntax.
Hope this helps.
Rohit

Similar Messages

URGENT : select from table statement in ABAP OO

Hi all,
I am an absolute ABAP OO beginner and need some quick help from an expert. How can I make a selection from an existing table (eg MARA) in an BADI which is programmed according to ABAP OO principles.
In the old ABAP school you could make a TABLES statement at the beginning and the do a SELECT¨* FROM but this does not work in ABAP OO.
How should i define such simple selections from existing tables. Anyone ?
Thanks a lot,
Eric Hassenberg

*define internal table
data: i_mara like standard table of mara.
*select to this table
select * from mara into table i_mara.
Also you have to define work area for this internal table in order to use it.
data:w_mara like line of i_mara.

Describe statement in abap

how to use this descibe statement.can any one please explain me with example

Hi Rajeev, write Describe and press F1 in the ABAP editor..u ll get the different functionalities for describe..
this is one of them
DESCRIBE - Return attributes of an internal table
Basic form
DESCRIBE TABLE itab.
Effect
Returns the attributes of the internal table itab. You must use at least one of the additions listed below:
Note
The DESCRIBE statement cannot be used for all ABAP types. In connection with ABAP Objects, SAP has introduced a RTTI concept based on system classes to determine type attributes at runtime. This concept applies to all ABAP types and as such covers all the functions of the DESCRIBE TABLE statement.
Extras:
1. ... LINES n
2. ... OCCURS n
3. ... KIND   k
Addition 1
... LINES n
Effect
Places the number of filled lines of the table t in the field lin. The value returned to lin has type I.
Note
The number of filled lines of the table itab can also be ascertained using the predefined function lines( itab ).
Example
DATA: N    TYPE I,
      ITAB TYPE TABLE OF I.
CLEAR ITAB.
APPEND 36 TO ITAB.
DESCRIBE TABLE ITAB LINES N.
Result: N contains the value 1.
Addition 2
... OCCURS n
Effect
Passes the size of the OCCURS parameter from the table definition (as defined with DATA) to the variable n. The value returned to n has type I.
Example
DATA: N1    TYPE I,
      N2    TYPE I,
      ITAB1 TYPE TABLE OF I INITIAL SIZE 10,
      ITAB2 TYPE I OCCURS 5.
DESCRIBE TABLE ITAB1 OCCURS N1.
DESCRIBE TABLE ITAB2 OCCURS N2.
Result: OCC contains the value 10 and N2 the value 5.
Addition 3
... KIND k
Effect
Writes the table type from itab to the variables n. The value returned to k is of type C. The constants SYDES_KIND-STANDARD, SYDES_KIND-SORTED and SYDES_KIND-HASHED are defined in the type group SYDES for the return values.
Example
Generic FORM routine any table type
TYPE-POOLS: SYDES.
FORM GENERIC_FORM USING ITAB TYPE ANY TABLE.
DATA: K TYPE C.
DESCRIBE TABLE ITAB KIND K.
CASE K.
    WHEN SYDES_KIND-STANDARD.
    WHEN SYDES_KIND-SORTED.
    WHEN SYDES_KIND-HASHED.
ENDCASE.
ENDFORM.
Notes
Performance: The runtime for executing the DESCRIBE TABLE statement is approximately 4 msn (standardized microseconds).
The DESCRIBE TABLE statement also passes values to the SY-TFILL and SY-TLENG System fields
Additional help
Determining the Attributesof Internal Tables

SQL Statements in ABAP and meaning

Hello Friends,
Please, can anybody provide me a documentation on the different ABAP SQL statements and there usage/meanings.
Thanks,
Shreekant

hi,
goto abapdocu->abap Database access->open Sql you will get examples.
for documnetation got se38->specify the command and press F1.
SELECT:
Put the curson on that word and press F1 . You can see the whole documentation for select statements.
SELECT result
FROM source
INTO|APPENDING target
[[FOR ALL ENTRIES IN itab] WHERE sql_cond]
Effect
SELECT is an Open-SQL-statement for reading data from one or several database tables into data objects.
The select statement reads a result set (whose structure is determined in result ) from the database tables specified in source, and assigns the data from the result set to the data objects specified in target. You can restrict the result set using the WHERE addition. The addition GROUP BY compresses several database rows into a single row of the result set. The addition HAVING restricts the compressed rows. The addition ORDER BY sorts the result set.
The data objects specified in target must match the result set result. This means that the result set is either assigned to the data objects in one step, or by row, or by packets of rows. In the second and third case, the SELECT statement opens a loop, which which must be closed using ENDSELECT. For every loop pass, the SELECT-statement assigns a row or a packet of rows to the data objects specified in target. If the last row was assigned or if the result set is empty, then SELECT branches to ENDSELECT . A database cursor is opened implicitly to process a SELECT-loop, and is closed again when the loop is ended. You can end the loop using the statements from section leave loops.
Up to the INTO resp. APPENDING addition, the entries in the SELECTstatement define which data should be read by the database in which form. This requirement is translated in the database interface for the database system´s programming interface and is then passed to the database system. The data are read in packets by the database and are transported to the application server by the database server. On the application server, the data are transferred to the ABAP program´s data objects in accordance with the data specified in the INTO and APPENDING additions.
System Fields
The SELECT statement sets the values of the system fields sy-subrc and sy-dbcnt.
sy-subrc Relevance
0 The SELECT statement sets sy-subrc to 0 for every pass by value to an ABAP data object. The ENDSELECT statement sets sy-subrc to 0 if at least one row was transferred in the SELECT loop.
4 The SELECT statement sets sy-subrc to 4 if the result set is empty, that is, if no data was found in the database.
8 The SELECT statement sets sy-subrc to 8 if the FOR UPDATE addition is used in result, without the primary key being specified fully after WHERE.
After every value that is transferred to an ABAP data object, the SELECT statement sets sy-dbcnt to the number of rows that were transferred. If the result set is empty, sy-dbcnt is set to 0.
Notes
Outside classes, you do not need to specify the target area with INTO or APPENDING if a single database table or a single view is specified statically after FROM, and a table work area dbtab was declared with the TABLES statement for the corresponding database table or view. In this case, the system supplements the SELECT-statement implicitly with the addition INTO dbtab.
Although the WHERE-condition is optional, you should always specify it for performance reasons, and the result set should not be restricted on the application server.
SELECT-loops can be nested. For performance reasons, you should check whether a join or a sub-query would be more effective.
Within a SELECT-loop you cannot execute any statements that lead to a database commit and consequently cause the corresponding database cursor to close.
SELECT - result
Syntax
... lines columns ... .
Effect The data in result defines whether the resulting set consists of multiple rows (table-like structure) or a single row ( flat structure). It specifies the columns to be read and defines their names in the resulting set. Note that column names from the database table can be changed. For single columns, aggregate expressions can be used to specify aggregates. Identical rows in the resulting set can be excluded, and individual rows can be protected from parallel changes by another program.
The data in result consists of data for the rows lines and for the columns columns.
SELECT - lines
Syntax
... { SINGLE }
| { { } } ... .
Alternatives:
1. ... SINGLE
2. ... { }
Effect
The data in lines specifies that the resulting set has either multiple lines or a single line.
Alternative 1
... SINGLE
Effect
If SINGLE is specified, the resulting set has a single line. If the remaining additions to the SELECT command select more than one line from the database, the first line that is found is entered into the resulting set. The data objects specified after INTO may not be internal tables, and the APPENDING addition may not be used.
An exclusive lock can be set for this line using the FOR UPDATE addition when a single line is being read with SINGLE. The SELECT command is used in this case only if all primary key fields in logical expressions linked by AND are checked to make sure they are the same in the WHERE condition. Otherwise, the resulting set is empty and sy-subrc is set to 8. If the lock causes a deadlock, an exception occurs. If the FOR UPDATE addition is used, the SELECT command circumvents SAP buffering.
Note
When SINGLE is being specified, the lines to be read should be clearly specified in the WHERE condition, for the sake of efficiency. When the data is read from a database table, the system does this by specifying comparison values for the primary key.
Alternative 2
Effect
If SINGLE is not specified and if columns does not contain only aggregate expressions, the resulting set has multiple lines. All database lines that are selected by the remaining additions of the SELECT command are included in the resulting list. If the ORDER BY addition is not used, the order of the lines in the resulting list is not defined and, if the same SELECT command is executed multiple times, the order may be different each time. A data object specified after INTO can be an internal table and the APPENDING addition can be used. If no internal table is specified after INTO or APPENDING, the SELECT command triggers a loop that has to be closed using ENDSELECT.
If multiple lines are read without SINGLE, the DISTINCT addition can be used to exclude duplicate lines from the resulting list. If DISTINCT is used, the SELECT command circumvents SAP buffering. DISTINCT cannot be used in the following situations:
If a column specified in columns has the type STRING, RAWSTRING, LCHAR or LRAW
If the system tries to access pool or cluster tables and single columns are specified in columns.
Note
When specifying DISTINCT, note that you have to carry out sort operations in the database system for this.
SELECT - columns
Syntax
| { {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ... }
| (column_syntax) ... .
Alternatives:
1. ... *
2. ... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
3. ... (column_syntax)
Effect
The input in columns determines which columns are used to build the resulting set.
Alternative 1
Effect
If * is specified, the resulting set is built based on all columns in the database tables or views specified after FROM, in the order given there. The columns in the resulting set take on the name and data type from the database tables or views. Only one data object can be specified after INTO.
Note
If multiple database tables are specified after FROM, you cannot prevent multiple columns from getting the same name when you specify *.
Alternative 2
... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
Effect
A list of column labels col1 col2 ... is specified in order to build the resulting list from individual columns. An individual column can be specified directly or as an argument of an aggregate function aggregate. The order in which the column labels are specified is up to you and defines the order of the columns in the resulting list. Only if a column of the type LCHAR or LRAW is listed does the corresponding length field also have to be specified directly before it. An individual column can be specified multiple times.
The addition AS can be used to define an alternative column name a1 a2 ... with a maximum of fourteen digits in the resulting set for every column label col1 col2 .... The system uses the alternative column name in the additions INTO|APPENDING CORRESPONDING FIELDS and ORDER BY. .
http://help.sap.com/saphelp_nw04/helpdata/en/62/10a423384746e8bf5f15ccdd36e8b1/content.htm

Why we use Tables statement in case of using SELECT-OPTIONS:

hi all,
Why we use Tables statement in case of using the following coding in an ABAP program ...
tables: vbak.
SELECT-OPTIONS: s1 for vbak-vbeln.
here if we dont provide the tables statement why it does not work ????
pls answwer ....???

Hi
This statement is not allowed in classes and declares a data object table_wa as a table work area whose data type is adopted from the identically named structured data type table_wa from the ABAP Dictionary. table_wa must be defined as a flat structure in the ABAP Dictionary. You can specify database tables or Views for table_wa.
Work table areas declared with TABLES are interface work areas and should only be declared in the global declaration section of a program for the following purpose:
reward if usefull
The statement TABLES is required for exchanging data between screen fields that were defined in a program screen when transferring from the ABAP Dictionary and the ABAP program. For the screen event PBO, the content of the table work area is transferred to identically named screen fields; for PAI, the system adopts the data from identically named screen fields.
In executable programs, flat table work areas can be used for adopting data that were provided for the event GET table_wa from a linked logical database. TABLES is synonymous with the statement NODES for this purpose.
Work table areas declared with TABLES behave like the data declared with the addition COMMON PART, meaning the data are used by the programs of a program group.
Table work areas declared with TABLES can be declared in subroutines and
function modules. However, this is not recommended. A table work area declared in a procedure is not local but belongs to the context of a framework program. The table work area can be viewed starting from the declaration in the framework program and lives as long as the framework program. In contrast to normal program-global data, the content of the table work areas declared in subroutines and function modules is stored temporarily when these subroutines and function modules are called. Value assignments that were made during runtime of the procedure are preserved until the procedure is completed. When exiting the procedure, the table work areas are filled with the contents that they contained when the procedure was called. Table work areas declared in procedures behave like global data to which the statement LOCAL is applied in the procedure.
The form TABLES * is obsolete.

How to avaoid tables declaration in abap object 's

Hi Folks,
I realised that in abap objects we should not declare tables statement, instead we have to declare wa type dbtable. But my qsn is i am using select single * from dbtable in at selection-screen for validation, in that situation in that situation how to avoid table declaration, i tried with select single * dbtable into wa , but still its asking table declaration.
Pls help me out, thanks.
Regards
Vishal

<b>method GET_VENDOR_4_USER .
Get the Vendor for the User
data: x_lfa1 type lfa1.
clear vendor.
select
    lifnr
    into VENDOR
    from zsiacvendor
    up to 1 rows
    where bname = sy-uname.
endselect.
get the name of the vendor
select single *
           into x_lfa1
           from lfa1
          where lifnr = vendor.
endmethod.</b>
The above code works fine for me.

Alternate for tables statement

hi friends
If i use dictionary fields in the screen i am using tables statement of that corresponding structure.
but i think tables statement is obsolete one is it right so what is the alternative for tables statement
how to move the values of fields between screen and abap program, help me
thanks in advance

Fields are moved from your program to the screen when the field names match. There is no explicit transport command needed.
I do not think that the TABLES command is considered obsolete when used in screen programming. That is the only time that I use it. There was some training material in regards to the TABLES command being required for proper transport between the program and the screen. I do not know if this has changed with 4.7.

When will UniverseDesigner support SAP ERP Tables,InfoSets and ABAP Func. ?

Hi there,
to the SAP guys in this Forum to keep the rumour mill running: is it planned to extend the connectivity of the Universe Designer to access to SAP ERP Tables, Infosets and ABAP Functions ?! Is there any date when this will happen ?!
Thanks,
Sebastian
Edited by: smenzl on Apr 15, 2010 9:08 AM

Hi,
if you need an official statement i would recommend you open a SAP OSS Message for that.
Regards
-Seb.

Which SAP table stores the ABAP program Source Code

Hi All,
Which SAP table stores the ABAP source code .
Is it possible to retrieve the abap program code from database table
wherein it is stored .
Scenario :
In our project SAP got decommissioned and SAP database is migrated to Oracle . As SAP is decomissioned , we are not able to access the SAP frontend . But we need a program code to service a request . Is it possible to retrieve the program code from the database
which is migrated to oracle .
Thanks
Shikha

This is an interesting question as the answer is may be different depending on your version. For example, in new releases the table REPOSRC appears to hold a compress version of the course code in the DATA field, but you would need to be able to decompress it if trying to read this directly out of the DB. I would assume that it uses gZip to do the compression, and there are ABAP utilities built in to do the compress/decompress. Of course you can always read the source code by using the READ REPORT statement in any release, but of course this will not help you if you can not log on to your system. Basically, if you system is corrupt for some reason, the best option is to restore from a backup.
REgards,
Rich Heilman

How to get the number of hits ("returned rows") in read table statement

Hi Experts
I have the statement shown below, which seems not to work as I would like it to. My problem is that I would like to do two different things depending on weather or not a read table statement results in 0 hits or 1 (or more) hits.
    READ TABLE g_ship_item
        WITH KEY
     l_ztknum = DATA_PACKAGE-/bic/ztknum
     BINARY SEARCH.
      IF sy-subrc is initial.
      no hits found
        DATA_PACKAGE-/BIC/ZSTAGEERR = 1.
      ELSE.
      hits where found and we will do something else...
        DATA_PACKAGE-/BIC/ZSTAGEERR = 0.
Hope someone can help me out of my problem...
Thanks in advance, regards
Torben

Hi,
As you are using READ statement with Binary search, check whether the internal table g_ship_item is sorted with field /bic/ztknum or not. If it is not sorted then the result of this READ statement is not correct.
Below is the correct code.
sort g_ship_item by /bic/ztknum.
READ table g_ship_item with key g_ship_item = xxx.
Thanks,
Satya

Creating a better update table statement

Hello,
I have the following update table statement that I would like to make more effecient. This thing is taking forever. A little background. The source table/views are not indexed and the larger of the two only has 150k records. Any ideas on making more effecient would be appreciate.
Thanks.
Ryan
Script:
DECLARE
V_EID_CIV_ID SBI_EID_W_VALID_ANUM_V.SUBJECT_KEY%TYPE;
V_EID_DOE     DATE;
V_EID_POE     SBI_EID_W_VALID_ANUM_V.POINT_OF_ENTRY%TYPE;
V_EID_APPR_DATE DATE;
V_CASE_CIV_ID     SBI_DACS_CASE_RECORDS.CASE_EID_CIV_ID%TYPE;
V_CASE_DOE     DATE;
V_CASE_POE SBI_DACS_CASE_RECORDS.CASE_CODE_ENTRY_PLACE%TYPE;
V_CASE_APPR_DATE           DATE;
V_CASE_DEPART_DATE           DATE;
V_SBI_UPDATE_STEP SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP%TYPE;
V_SBI_CIV_ID SBI_DACS_CASE_RECORDS.SBI_CIV_ID%TYPE;
CURSOR VALID_CIV_ID_FROM_EID IS
     SELECT EID.SUBJECT_KEY,
          TO_DATE(EID.PROCESS_ENTRY_DATE),
          EID.POINT_OF_ENTRY,
          TO_DATE(EID.APPREHENSION_DATE),
          DACS.CASE_EID_CIV_ID,
          TO_DATE(DACS.CASE_DATE_OF_ENTRY,'YYYYMMDD'),
          DACS.CASE_CODE_ENTRY_PLACE,
          TO_DATE(DACS.CASE_DATE_APPR,'YYYYMMDD'),
          TO_DATE(DACS.CASE_DATE_DEPARTED,'YYYYMMDD'),
          DACS.SBI_UPDATE_STEP,
          DACS.SBI_CIV_ID
     FROM SBI_EID_W_VALID_ANUM_V EID,
SBI_DACS_CASE_RECORDS DACS
WHERE DACS.CASE_NBR_A = EID.ALIEN_FILE_NUMBER;
     BEGIN
          OPEN VALID_CIV_ID_FROM_EID;
SAVEPOINT A;
          LOOP
               FETCH VALID_CIV_ID_FROM_EID INTO V_EID_CIV_ID, V_EID_DOE, V_EID_POE,V_EID_APPR_DATE,V_CASE_CIV_ID, V_CASE_DOE,V_CASE_POE,V_CASE_APPR_DATE,V_CASE_DEPART_DATE,V_SBI_UPDATE_STEP,V_SBI_CIV_ID;
DBMS_OUTPUT.PUT_LINE('BEFORE');
               EXIT WHEN VALID_CIV_ID_FROM_EID%FOUND;
DBMS_OUTPUT.PUT_LINE('AFTER');
          UPDATE SBI_DACS_CASE_RECORDS
SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_CASE_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 1
WHERE V_CASE_CIV_ID IS NOT NULL
AND V_CASE_CIV_ID <> 0;
UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 2
WHERE V_SBI_CIV_ID IS NULL AND V_SBI_UPDATE_STEP = 0
               AND V_EID_DOE = V_CASE_DOE
               AND V_EID_POE = V_CASE_POE
               AND V_EID_APPR_DATE = V_CASE_APPR_DATE
               AND V_EID_APPR_DATE = V_CASE_DEPART_DATE;
               UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 3
WHERE V_SBI_UPDATE_STEP = 0
               AND V_EID_DOE = V_CASE_DOE
               AND V_EID_POE = V_CASE_POE
               AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 4
WHERE V_SBI_UPDATE_STEP = 0
               AND V_EID_DOE = V_CASE_DOE
               AND V_EID_POE = V_CASE_POE
               AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) > -4
               AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) < 4 ;
     UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 5
WHERE V_SBI_UPDATE_STEP = 0
               AND V_EID_DOE = V_CASE_DOE
               AND V_EID_POE <> V_CASE_POE
               AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 6
WHERE V_SBI_UPDATE_STEP = 0
               AND V_EID_POE = V_CASE_POE
               AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 7
WHERE V_SBI_UPDATE_STEP = 0
     AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
          UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 8
WHERE V_SBI_UPDATE_STEP = 0
AND V_EID_DOE = V_CASE_DOE
               AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) > -4
               AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) < 4;
               UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 9
WHERE V_SBI_UPDATE_STEP = 0
AND V_EID_DOE = V_CASE_DOE
               AND V_EID_POE = V_CASE_POE;
          UPDATE SBI_DACS_CASE_RECORDS
          SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
               SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 10
WHERE V_SBI_UPDATE_STEP = 0
AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) > -4
               AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) < 4;
          END LOOP;
          CLOSE VALID_CIV_ID_FROM_EID;
     COMMIT;
     END;
-----Thats it. Thanks for your help.
Ryan

Please use [ code] or [ pre] tags to format code before posing:
DECLARE
     V_EID_CIV_ID SBI_EID_W_VALID_ANUM_V.SUBJECT_KEY%TYPE;
     V_EID_DOE DATE;
     V_EID_POE SBI_EID_W_VALID_ANUM_V.POINT_OF_ENTRY%TYPE;
     V_EID_APPR_DATE DATE;
     V_CASE_CIV_ID SBI_DACS_CASE_RECORDS.CASE_EID_CIV_ID%TYPE;
     V_CASE_DOE DATE;
     V_CASE_POE SBI_DACS_CASE_RECORDS.CASE_CODE_ENTRY_PLACE%TYPE;
     V_CASE_APPR_DATE DATE;
     V_CASE_DEPART_DATE DATE;
     V_SBI_UPDATE_STEP SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP%TYPE;
     V_SBI_CIV_ID SBI_DACS_CASE_RECORDS.SBI_CIV_ID%TYPE;
     CURSOR VALID_CIV_ID_FROM_EID IS
          SELECT EID.SUBJECT_KEY,
           TO_DATE(EID.PROCESS_ENTRY_DATE),
           EID.POINT_OF_ENTRY,
           TO_DATE(EID.APPREHENSION_DATE),
           DACS.CASE_EID_CIV_ID,
           TO_DATE(DACS.CASE_DATE_OF_ENTRY,'YYYYMMDD'),
           DACS.CASE_CODE_ENTRY_PLACE,
           TO_DATE(DACS.CASE_DATE_APPR,'YYYYMMDD'),
           TO_DATE(DACS.CASE_DATE_DEPARTED,'YYYYMMDD'),
           DACS.SBI_UPDATE_STEP,
           DACS.SBI_CIV_ID
          FROM SBI_EID_W_VALID_ANUM_V EID,
           SBI_DACS_CASE_RECORDS DACS
          WHERE DACS.CASE_NBR_A = EID.ALIEN_FILE_NUMBER;
BEGIN
     OPEN VALID_CIV_ID_FROM_EID;
     SAVEPOINT A;
LOOP
     FETCH VALID_CIV_ID_FROM_EID INTO V_EID_CIV_ID, V_EID_DOE,
          V_EID_POE,V_EID_APPR_DATE,V_CASE_CIV_ID, V_CASE_DOE,
               V_CASE_POE,V_CASE_APPR_DATE,V_CASE_DEPART_DATE,V_SBI_UPDATE_STEP,V_SBI_CIV_ID;
     DBMS_OUTPUT.PUT_LINE('BEFORE');
     EXIT WHEN VALID_CIV_ID_FROM_EID%FOUND;
     DBMS_OUTPUT.PUT_LINE('AFTER');
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_CASE_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 1
     WHERE V_CASE_CIV_ID IS NOT NULL
      AND V_CASE_CIV_ID <> 0;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 2
     WHERE V_SBI_CIV_ID IS NULL AND V_SBI_UPDATE_STEP = 0
      AND V_EID_DOE = V_CASE_DOE
       AND V_EID_POE = V_CASE_POE
        AND V_EID_APPR_DATE = V_CASE_APPR_DATE
         AND V_EID_APPR_DATE = V_CASE_DEPART_DATE;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 3
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_DOE = V_CASE_DOE
       AND V_EID_POE = V_CASE_POE
        AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 4
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_DOE = V_CASE_DOE
       AND V_EID_POE = V_CASE_POE
        AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) > -4
         AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) < 4 ;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 5
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_DOE = V_CASE_DOE
       AND V_EID_POE <> V_CASE_POE
        AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 6
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_POE = V_CASE_POE
       AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 7
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_APPR_DATE = V_CASE_APPR_DATE;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 8
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_DOE = V_CASE_DOE
       AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) > -4
        AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) < 4;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 9
     WHERE V_SBI_UPDATE_STEP = 0
      AND V_EID_DOE = V_CASE_DOE
       AND V_EID_POE = V_CASE_POE;
     UPDATE SBI_DACS_CASE_RECORDS
      SET SBI_DACS_CASE_RECORDS.SBI_CIV_ID = V_EID_CIV_ID,
       SBI_DACS_CASE_RECORDS.SBI_UPDATE_STEP = 10
     WHERE V_SBI_UPDATE_STEP = 0
      AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) > -4
       AND (V_EID_APPR_DATE - V_CASE_APPR_DATE) < 4;
END LOOP;
CLOSE VALID_CIV_ID_FROM_EID;
COMMIT;
END;Peter D.

How to specify tablespace for a primary key inde in create table statement

How to specify the tablespace for a primary key index in a create table statement?
Does the following statement is right?
CREATE TABLE 'GPS'||TO_CHAR(SYSDATE+1,'YYYYMMDD')
            ("ID" NUMBER(10,0) NOT NULL ENABLE,
            "IP_ADDRESS" VARCHAR2(32 BYTE),
            "EQUIPMENT_ID" VARCHAR2(32 BYTE),
            "PACKET_DT" DATE,
            "PACKET" VARCHAR2(255 BYTE),
            "PACKET_FORMAT" VARCHAR2(32 BYTE),
            "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
             CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") TABLESPACE "INDEX_DATA"
             TABLESPACE "SBM_DATA";   Thank you
Edited by: qkc on 09-Nov-2009 13:42

As orafad indicated, you'll have to use the USING INDEX clause from the documentation, i.e.
SQL> ed
Wrote file afiedt.buf
1 CREATE TABLE GPS
2              ("ID" NUMBER(10,0) NOT NULL ENABLE,
3              "IP_ADDRESS" VARCHAR2(32 BYTE),
4              "EQUIPMENT_ID" VARCHAR2(32 BYTE),
5              "PACKET_DT" DATE,
6              "PACKET" VARCHAR2(255 BYTE),
7              "PACKET_FORMAT" VARCHAR2(32 BYTE),
8              "SAVED_TIME" DATE DEFAULT CURRENT_TIMESTAMP,
9               CONSTRAINT "UDP_LOG_PK" PRIMARY KEY ("ID") USING INDEX TABLESP
ACE "USERS"
10               )
11*              TABLESPACE "USERS"
SQL> /
Table created.Justin

Merge Statement in ABAP

Dear Gurrus,
i am having a trouble in using oracle merge statement in abap, the moment i use where clause in the bottom it gives me an oracle error
EXEC SQL.
MERGE INTO SAP_GL_ACCOUNT@GETZDB a
USING SKA1 b
    ON (A.gl_code= B.SAKNR)
WHEN MATCHED THEN
    UPDATE SET a.posting_block = B.XSPEB,
               a.locked        = B.XSPEA,
               A.BALANCE_SHEET = B.XBILK
     WHEN NOT MATCHED THEN
       insert   (gl_code,
                 DESCRIPTION,
                 posting_block,
                 locked,
                 balance_sheet)
      VALUES (b.SAKNR,'shadab',B.XSPEB,B.XSPEA,B.XBILK)
      where b. mandt = 950      I am talking about this line
         ENDEXEC.
the Moment i include WHERE clause in the botton before ENDEXEC it generates as error
" Database error text........: "ORA-00904: "A3"."MANDT": invalid identifier#ORA-02063: preceding line from GETZDB".
although its a basic feature of Oracle to inclue where clauses in insert or update in merge, but here it is generating an error.

Hello Shadab,
As per my understanding of this oracle native sql code.
everything is fine except the use of direct value i.e 950 .
System is not able to process this value .
This normally happens even in normal abap sql statements also.
The better solution could be to declare a variable with the
same data type as "mandt" and then pass this "950" value into that
variable and then use this variable in the where clause instead of directly
passing the value.
i.e data:l_var type mandt vlaue '950'.
The other option could be to use the same hard coded
value but use this value in the where clause in quotations i.e.,
'950' instead of 950.
I hope this would solve your purpose, If not please reply me back.
thanks,
M.Naveen Kumar.

To know the functionality of table control in ABAP Objects

Hi,
Is there any technique to achieve the functionality of table conrol in ABAP Objects?
Thanks.

Hello Raja
If you are using an editable ALV grid then you have the functionality of a table control and much much more.
ABAP-OO based ALV grids are much more powerful (and easier) than simple table controls.
Regards
Uwe

A Select statement with Appending table statement in it.

Hi,
How can I use a select statement with a <Appening table> statement in it.
SELECT DISTINCT <field Name>
                FROM <DB table name>
                APPENDING TABLE <itab>
                WHERE <fieldname> EQ <Itab1-fieldname>
                  AND <fieldname> EQ <itab2-fieldname>.
Can I use the above select statement.If I'm using this...how this works?
Regards
Dharmaraju

Hi, Dharma Raju Kondeti.
I found this in the SAP online help, hope this can help you.
Specifying Internal Tables
When you read several lines of a database table, you can place them in an internal table. To do this, use the following in the INTO clause:
SELECT ... INTO|APPENDING [CORRESPONDING FIELDS OF] TABLE <itab>
                          [PACKAGE SIZE <n>] ...
The same applies to the line type of <itab>, the way in which the data for a line of the database table are assigned to a table line, and the CORRESPONDING FIELDS addition as for flat work areas (see above).
The internal table is filled with all of the lines of the selection. When you use INTO, all existing lines in the table are deleted. When you use APPENDING; the new lines are added to the existing internal table <itab>. With APPENDING, the system adds the lines to the internal table appropriately for the table type. Fields in the internal table not affected by the selection are filled with initial values.
If you use the PACKAGE SIZE addition, the lines of the selection are not written into the internal table at once, but in packets. You can define packets of <n> lines that are written one after the other into the internal table. If you use INTO, each packet replaces the preceding one. If you use APPENDING, the packets are inserted one after the other. This is only possible in a loop that ends with ENDSELECT. Outside the SELECT loop, the contents of the internal table are undetermined. You must process the selected lines within the loop.
Regards,
feng.
Edited by: feng zhang on Feb 21, 2008 10:20 AM

Tables Statement in ABAP HR

Similar Messages

Maybe you are looking for