About statment Tables: *(TableName).

Hi,
In a SAP program, I saw a statement like this:
TABLES: *KNA1.
Can someone explain to me what that * means?
Thanks a lot!

Hai Yun
'*KNA1' Means Any single Character followed by KNA1.
Basic form
TABLES dbtab.
Effect
Makes the database table , view or structure dbtab known to the program. These objects are created by selecting Development -> ABAP/4 Dictionary . This transaction automatically defines an identical field string - the table work area - in the program. The names and the sequence of the fields of the table work area dbtab correspond exactly to the names and the sequence of the fields when declaring the database table or view in the ABAP/4 Dictionary . The ABAP/4 data type (see DATA ) and the length of the fields are derived from the data types in the ABAP/4 Dictionary as follows:
Dict. data type ABAP/4 data type
ACCP -> N(6)
CHAR n -> C(n)
CLNT -> C(3)
CUKY -> C(5)
CURR n, m, s -> P((n + 2) / 2) DECIMALS m [NO-SIGN]
DEC n, m, s -> P((n + 2) / 2) DECIMALS m [NO-SIGN]
DATS -> D
FLTP -> F
INT1 -> No correspondence
INT2 -> No correspondence
INT4 -> I
LCHR n -> C(n)
LRAW n -> X(n)
LANG -> C(1)
NUMC n -> N(n)
PREC -> X(2)
QUAN n, m, s -> P((n + 2) / 2) DECIMALS m [NO-SIGN]
RAW n -> X(n)
TIMS -> T
UNIT n -> C(n)
VARC n -> C(n)
The fields of the table work area are set to the initial values for their ABAP/4 data types (see DATA ). For the ABAP/4 Dictionary data types INT1 and INT2 , whole number fields of length 1 or 2 are created with the initial value 0 in the table work area.
The length of the table work area is not just the sum of the lengths of the individual fields. Depending on how different fields have to be aligned (Alignment ), the structure can contain nameless "holes".
Example
TABLES SPFLI.
SELECT * FROM SPFLI.
WRITE: / SPFLI-CARRID, SPFLI-CONNID.
ENDSELECT.
Notes
You can display the structure of the table work area in the ABAP/4 Editor by double-clicking on the table name.
The divisions for determining ABAP/4 field lengths are whole number divisions without rounding. The field of the table work area can accept numbers which contain one digit more than the ABAP/4 Dictionary data type allows. Such a situation results in a runtime error when writing to the database.
The table work area always has a global validity area. Even if the TABLES statement is specified in a FORM or FUNCTION , the work area is known when the subroutine has been defined. However, changes to the work area in a subroutine remain local to the FORM or FUNCTION . Therefore, it is advisable to specify the TABLES statement globally. You can keep changes to the table work area local to the subroutine with LOCAL .
Related DATA , TYPES
Thanks & regards
Sreenivasulu P

Similar Messages

I NEED TO KNOW ABOUT DRIVING TABLE...PLEASE

Well, My name is Adan. I am from Panama.. my english is not
good. But I'll try. I need to know about driving tables and how
have to choose a driving table and how optimizer proccess an sql
statment.
Example:
Employees have (1,000,000 rows),
dept have (100 rows)
Category have (100 rows)...
I need retrieved all employees with category and dept name for
those employee with salary > 100000
Well, What is the driving table and where i have to put this one
in the from clause ? What about order in the where predicate...
First ?
Select E.name, C.category, D.Departement
from Employees e, dept d, category c
where
and d.cat = c.cat
and e.deptno = d.deptno
and e.salary > 100000
Last ?
Select E.name,C.category, D.Departement
from dept d, category c ,Employees e
where
and d.cat = c.cat
and e.deptno = d.deptno
and e.salary > 100000
I apreciate your help....Thanks and sorry for my english....
Bye..

Adam,
If you set your optimizer = choose and analyze the tables and
indexes to generate statistics, then your system can use the
Cost Based Optimizer (CBO) and, like David said, it will
automatically choose the best access path, and the order of
things will not matter.
If your optimizer is not set to choose or if there are no
statistics, then it will use the Rule Based Optimizer (RBO), in
which case, the only thing that matters is the order of the
tables in the from clause. When using RBO, the driving table
should be at the end of the from clause, in the right-most
position. The driving table is the one such that, after the
restrictions have been applied, returns the smallest number of
rows. You would have to compare the number of rows in the
employees table where salary > 100000 to the number of rows in
the dept table (100) and the number of rows in the category
table (100).
In RBO, if there are more than 100 rows in the employees table
where salary > 100000, then your from clause would be:
FROM employees e, dept d, category c
In RBO, if there are less than 100 rows in the employees table
where salary > 100000, then your from clause would be:
FROM category c, dept d, employees e
This is all that applies to the example you have given, however
there are other things that can apply in other situations. For
example, if there is an outer join to a table, the table that
has the (+) cannot be used as the driving table.
Barbara

Run Rebuild Index Task daily on database but about 77 tables still highly fragmented over 80% !!!

Hello everyone
On our particular database server, we run the Rebuild Index Task (Using classic Maintenance Plan Designer) every night. Running the script below, I saw that about 77 tables had an avg_fragmentation_in_percentage between 80% and 99% !!
SELECT OBJECT_NAME(ind.OBJECT_ID) AS TableName,
ind.name AS IndexName, indexstats.index_type_desc AS IndexType,
indexstats.avg_fragmentation_in_percent
FROM sys.dm_db_index_physical_stats(DB_ID(), NULL, NULL, NULL, NULL) indexstats
INNER JOIN sys.indexes ind
ON ind.object_id = indexstats.object_id
AND ind.index_id = indexstats.index_id
WHERE indexstats.avg_fragmentation_in_percent > 30--You can specify the percent as you want
ORDER BY indexstats.avg_fragmentation_in_percent DESC
I dont understand why these tables are highly fragmented after a daily index rebuild! Unless the users are doing heavy inserts/updates/deletes during the day.
Anyone has an idea of the possible causes of these results??
Thank you all in advance

Hallo Efyuzegeekgurl,
this is a normal behaviour when your table is only a small one. The reason for that behaviour is the following:
The dmv sys.dm_db_index_physical_stats counts each page which is not located at the very next one of the same table as a "fragment". If the first data page is 1700 and the second one is located on 1705 SQL server will count it as a fragment.
The basic allocation algorithm of Microsoft SQL Server is that new data pages will be created in "mixed extents". An extent is a contigious line of 8 consecutive data pages. This is for historical reasons when storage was expensive and data should
use as much as possible of allocated storage.
If a new table will be created the very first 8 pages are not located one after the other but "could" be located on different extents. If your table has only 9 data pages than 8 pages will count as "fragmented" because of their non consecutive
allocation. After 8 pages have been allocated Microsoft SQL Server will ALWAYS use a full extent for the next 8 pages (and so on!).
To understand this behaviour use the following example which creates a table with a record length of 8K. The next command will create 10 records (which means 10 data pages).
CREATE TABLE dbo.foo
Id INT NOT NULL IDENTITY (1, 1),
c1 CHAR(8000) NOT NULL DEFAULT ('filler')
GO
SET NOCOUNT ON;
GO
INSERT INTO dbo.foo DEFAULT VALUES
GO 10
When you check the page allocation you'll find the first 8 data pages not in a consecutive row but "scrambled" into different pages:
SELECT database_id,
index_id,
partition_id,
allocation_unit_type_desc,
extent_page_id,
allocated_page_page_id,
is_mixed_page_allocation,
page_type_desc
FROM sys.dm_db_database_page_allocations
DB_ID(),
OBJECT_ID('dbo.foo', 'U'),
0,
NULL,
'DETAILED'
) AS DDDPA
WHERE
DDDPA.is_allocated = 1
ORDER BY
DDDPA.is_iam_page DESC,
DDDPA.page_level DESC;
GO
You will see that the first 8 pages are located in a MIXED extent. Although the pages are in a consecutive order in the extent 221112 it is not guaranteed!
You can see from the very first three records that they are not in a consecutive row stored.
Now the fragmentation of the data seems to be quite high because we have 4 breaks in the rows. If we compare this value to the "fragmentation in sys.dm_db_index_physical_stats we will see at least the same result:
SELECT index_type_desc,
alloc_unit_type_desc,
DDIPS.avg_fragmentation_in_percent,
DDIPS.fragment_count,
DDIPS.page_count,
avg_page_space_used_in_percent
FROM sys.dm_db_index_physical_stats
DB_ID(),
OBJECT_ID('dbo.foo', 'U'),
NULL,
NULL,
'DETAILED'
) AS DDIPS;
So - just from my point of view - don't count only to the fragmentation in percent because if the table is to small it will ALWAYS be over 30%. Take more into account the density of the pages and - as all others have mentioned - the number of pages of the
index.
I would consider indexes with more or equal to 1.000 pages.
Another tip: Forget about the f... maintenance plans. These "plans" are not worth the time and money because you cannot control it in a more precise way. Have a look to the solution of Ola Hallengren and implement his solution - a great master
piece of index maintenance:
http://ola.hallengren.com
All the best to the community :)
MCM - SQL Server 2008
MCSE - SQL Server 2012
db Berater GmbH
SQL Server Blog (german only)

About Fact Tables and Image Tables

Not sure, if this is correct forum for Oracle BI 10.x EE, but still
I couldn't find another forum, quickly, hence posting here.
Pardon me.
Here is the main Q's
I need little help.
Our company is implementing Oracle BI 10.x. We don't have much experience in Siebel Analytics/OBI.
We have few fact tables e.g. W_XXXX_F, which we need/wish to extend. We are not sure about which methodology we should implement. When we talked with few SA experts they mentioned we need to extend based on ROW_WID. Well, this column doesn't exists anymore in many fact tables, so currently we are thinking of creating ROW_WID on this F table manually and then create WC_XXXX_FX and take these two tables in physical layer of RPD.
Additially, we need to create few Informatica mappings, again SA experts pointed out to use Image tables. Our data source is Oracle Applications, I don't have much idea about Image tables, but clearly there is not S_ETL_I_IMGAGe or so tables in Oracle Apps
Please guide us as how to proceed on these two issues.
Rajat

Not sure, if this is correct forum for Oracle BI 10.x EE, but still
I couldn't find another forum, quickly, hence posting here.
Pardon me.
Here is the main Q's
I need little help.
Our company is implementing Oracle BI 10.x. We don't have much experience in Siebel Analytics/OBI.
We have few fact tables e.g. W_XXXX_F, which we need/wish to extend. We are not sure about which methodology we should implement. When we talked with few SA experts they mentioned we need to extend based on ROW_WID. Well, this column doesn't exists anymore in many fact tables, so currently we are thinking of creating ROW_WID on this F table manually and then create WC_XXXX_FX and take these two tables in physical layer of RPD.
Additially, we need to create few Informatica mappings, again SA experts pointed out to use Image tables. Our data source is Oracle Applications, I don't have much idea about Image tables, but clearly there is not S_ETL_I_IMGAGe or so tables in Oracle Apps
Please guide us as how to proceed on these two issues.
Rajat

Confused about logical table source

Hi,
I'm confused about logical table source(LTS), there are 'General', 'Column Mapping', 'Content' tabs in
LTS, in General tab ,there are some information,like 'Map to there tables' and 'joins',
just here, we have created relationships in physical layer and BMM layer, so I would like to ask what's the use of the 'joins' here?

Hi Alpha,
Valid query, when you establish a complex join it is always between a logical fact and dimension table.Consider a scenario,
Example:w_person_dx is an extension table not directly joined to a fact but joins to a dimension w_person_d.
When you model the person_d tables in BMM, you ll have a single logical table with w_person_d as source.If you have to pull columns from both w_person_d and w_person_dx tables in a report, you add dx table as inner join to persond table in the general tab.Now when you check your physical query, you can see the inner join fired between the two dimensions.
Rgds,
Dpka

Need information about Internal Tables

Hi Every one!
I Need some information about Internal tables. Pls help be above the same.
Thanks & with Regards,
Chandra.

Hi..,

Internal tables 
Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
Internal Tables as Data Types
Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type.
Line type
The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
Key
The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves internal tables. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.

Table type
The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.

Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be unique or not. Standard tables and sorted tables are known generically as index tables.

Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.

Generic Internal Tables
Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols and the interface parameters of procedures . You cannot use them to declare data objects.
Internal Tables as Dynamic Data Objects
Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.

Choosing a Table Type
The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.

Standard tables
This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.
Sorted tables
This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.

Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
regards,
sai ramesh

About important tables in FI

Hi Friends,
I would like to know something about the tables and the data flow. I've not been a part of customising a "Z" report as yet, and I'm sure I would have to do it any time.
Please suggest to me as to where do I need to start off and the importance of learning the table names pertaining to FI/CO. Important factors that I need to bear in my mind before I could attempt to do so.
What information I need to give to the ABAPer or how do I prepare a Functional(or Technical) spec.
Would highly appreciate if there are any links pertaining to this and also if anyone could share some tips.
Regards,
Soujanya.

http://www.abap.es/Descargas/TAB%20-%20Relacion%20de%20las%20tablas%20por%20modulos.PDF
you may please search in search engines with
sap tables .pdf
sap tables .doc
You should be able to identify the tables and field names to be populated.
Technical spec. is more of technical in nature with table and field names, whereas functional spec. is more of explaining the functionality required. A lay man should be able to understanding functionality when they read the FS. Whereas, Technical spec. if purely for technical purposes with lot of table and field names and other technical stuff.
Check on google for some sample documents.
Regards,
Ravi

What does a BI Developer need to know about SAP tables and why?

Hi,
i.
As a BI Developer, to what extent do you need to know about SAP tables?
e.g. if you work mainly in the functional areas LO and FI
ii.
For example, I know that in Finance, GL relates to the tables BSEG and BKPF.
And if it is important to know about them, then which other tables need to be known and for what reasons?
e.g. do I need to know all these tables: http://www.erpgenie.com/sap/abap/tables_fi.htm
iii.
I thought as a BI Developer, knowing that a particular datasource, e.g. 0FI_GL_4 contains line items is enough and you replicate it to BW and work with it. Why is there the need to know the tables from which this datasource gets is data?
iv. What is the main difference between the FI datasources and the LO datasource?
Thanks.

Hi,
i. As a BI Developer, to what extent do you need to know about SAP tables?
e.g. if you work mainly in the functional areas LO and FI
Not required, but today business demands so you required this Knowelgde.
ii.
For example, I know that in Finance, GL relates to the tables BSEG and BKPF.
And if it is important to know about them, then which other tables need to be known and for what reasons?
e.g. do I need to know all these tables: http://www.erpgenie.com/sap/abap/tables_fi.htm
We can't say yes or No, so based on your requirement you need to sit with Functional COnsultanst and the understand the Business Requirements and develop the OBjetcs.
iii.
I thought as a BI Developer, knowing that a particular datasource, e.g. 0FI_GL_4 contains line items is enough and you replicate it to BW and work with it. Why is there the need to know the tables from which this datasource gets is data?
If you want to know the data flow and reconsilization then you need to know it else not required
iv. What is the main difference between the FI datasources and the LO datasource?
Yes, one main difference is There is no setup table concept for FI DataSource*
Note: If you want to become a good BW consulatnt you must know about Tables for normal BW consultant it is not required.
Thanks
Reddy

Doubts about Temporary Table.

Hi,
I am using Temporary Table.
But the insert command takes too much time compare to insert in Normal table.
One more doubt about Temporary Table is:
Suppose there are two different users. They connect and first insert rows of their use .Now they go for select.
Does select of one user goes to check the rows of second user also or the temporary table treats 2 users data as inserted in 2 different tables?
Help!!!

Nested structure (not deep - deep means their a string or a table as a component)
TYPES: BEGIN OF tp_header_type,
         BEGIN OF d,
           empresa TYPE ...
           num_docsap TYPE ...
        END OF d,
        awkey TYPE ...
      END OF tp_header_type.
matt

About Read table

Can any body explain about Read table and when it can use.

Hi,
When u want to read a record based on some condition then u can use READ.
LOOP AT itab.
READ TABLE itab WITH KEY matnr = itab-matnr.
IF sy-subrc = 0.
ENDIF.
ENDLOOP.
U can read only a single record.
U can also use
READ TABLE itab INDEX 1.
Reward points if this is helpful.

Briefly about internal tables

briefly about internal tables
standerd internal tables
hash internal tables
sorted internal tables
index internal tables

Hi,
Internal tables : Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs.
Types of internal tables :
The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.
Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be UNIQUE or NON-UNIQUE. Standard tables and sorted tables are known generically as index tables.
Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.
Creating Internal Tables
You define internal tables first as an abstract data type in the program or ABAP Dictionary, and then as a data object based on that, or they are declared directly as a fully specified data object. When you create an internal table as a data object, you should ensure that only the administration entry which belongs to an internal table is declared statically. The size of table headers for initial tables is currently 8 bytes. This should be heeded whenever internal tables occur as components of complex data objects. Also, empty tables can use up a relatively high amount of storage space as components of tables. The size of the entire storage space required for an internal table is not defined in the declaration as is the case for data objects of the type string or xstring. Table rows are added to and deleted from the table dynamically at runtime by the various statements for adding and deleting records.
Structure of internal tables :
STRUCTURE OF INTERNAL TABLE
TYPES : BEGIN OF ITAB,
                PERNR TYPE PERSNO,
                WERKS TYPE WERKS,
               END OF ITAB.
INTERNAL TABLE DECLARATION FOR THE ABOVE STRUCTURE
DATA : INT_TAB TYPE STANDARD TABLE OF ITAB,
            WA_TAB TYPE ITAB.        "WORK AREA OF THE INTERNAL TABLE
Thanks,
Sakthi C
Rewards if useful *

About Aggregated Tables?

Hi,
I would like to know about Aggregated tables.. like What are Aggregated tables? Why we need to use them?
Please help me....

http://www.justfuckinggoogleit.com/search.pl?query=Aggregate+table+OBIEE

How to realize about List Table

Hello,
How can I realize about list table, how can I add the image logo in it ? for the details that you can follow my enclosed, I have marked with red circle drawing ,from NI example finder, that we can see, there are an image logo side by every title at the list table, how NI append it ?
who knows ? thanks in advance.
Attachments:
how to realize.JPG ‏24 KB

Hi Gilbert
It is possible to add a cutom image to a tree control, please look at the following KB
How Do I Load and Use Custom Symbols for My Tree Control Items?
This should take you through the steps you need to set this up correctly.
Regards
JamesC
NIUK and Ireland

RSRV - Database Information about InfoProvider Tables

Hello Experts,
I have a question regarding the RSRV. I have run the check "Database Information about InfoProvider Tables " to see number of entries of the dimension tables for a cube. Afterwards I checked directly the dimension table /BIC/D* with the TC SE16. And the number of entries differs. In the RSRV I get around 26 MIO entries, but in the dimension table I get around 25 MIO entries.
Can anybody explain me this ? For my understanding the RSRV result for the dimension table and the number of entries (SE16) should match.
Thx in advance.
AK

hi,
Please refer
SAP Note Number: 941933 - RSRV: Incorrect values for database info on InfoProvider
RSRV - Database information about Infoprovider
Dim tables
Hope this helps.
Regards
Raj

Question about Update Tables

Hello Gurus,
I have a question about "update table" entries. I read somewhere that an entry in update table is done at the time of the OLTP transaction. Is this correct? If so, does this happen on a V1 update or V2 update? Please clarify. Similarly, an entry in the "extraction queue" (incase you are using "queued delta" will happen on V1 update. I just want to get a clarification on both these methods. Any help in this matter is highly appreciated.
Thanks,
Sreekanth

Hi
update tables are temporary table that are refreshed by v3 job.update table is like buffer, it gets filled after updation of application table and statistical table through v1 v2 update . we can bypass this process by delta methods.
M Kalpana

About statment Tables: *(TableName).

Similar Messages

Maybe you are looking for