Regarding Database Tables

[former_member758419]

Hi,,

I've several doubts regarding Database tables in SAP. Please send me the answers for the same and also some links where i can get further information about the topics..

1) What are Application tables, Customizing tables? This is with regard to the Delivery class used for creating tables. <u>In what cases should we select application tables and customizing tables?</u>

2) If its a customizing table why should a table be client dependent. why not for appln table?

3) What does APPL0, APPL1,APPL2 specify in Data class, Please tell me in what cases it should be used..

Thanks in Advance,

Sachi

[Former Member]

See this answer:

3)There are five size categories (0-4) and 11 data classes only three of which are appropriate for application tables:

· APPL0- Master data (data frequently accessed but rarely updated).

· APPL1- Transaction data (data that is changed frequently).

· APPL2- Organizational data (customizing data that is entered when system is configured and then rarely changed).

The other two types are:

· USR

· USR1 – Intended for customer’s own developments

Refer this link

http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html

[Former Member]

Hi Sachidanand,

1) Application tables are used mainly for tables that may vary their content with business transactions. Customizing tables store configurations that should stay the same in order for the system to work in a given way.

For example, a typical case of an application table is BKPF, which stores header data for financial documents. Every day, this table is populated with data, every time you post an FI document.

On the other hand, a typical case of a customizing table is T001, which stores data for company codes. This data is not normally changed, unless you create a new company in your installation, or unless you want to change the behaviour of an existing company code (for example, currency code)

2) Well, you should perform a further analysis to decide if a table should be client-dependent or -independent (no matter if it's a customizing one or an application one). In a general way (in my humble opinion), every table should be client-dependent if possible. BUT this is not possible for tables that store data which is closely related to the file-system of the server in which SAP is installed. For example, table FILENAMECI stores logical filenames together with physical filenames. As two clients on the same server access the same file directories in the server, it's logical to define this table as client-independent, because if a directory in the file system is changed, this will affect every client in the system.

3) (already answered; nice link!)

I hope it helps. Best regards,

Alvaro