topic Re: general in Application Development and Automation Discussions

general

Former Member — Fri, 06 Jul 2007 05:00:14 GMT

hi,

difference between opensql/native sql?

wht isdifference bt client dependent and independent?

what is macro?difrrence bt macro and subroutine?

what is value table in domain?

Re: general

Former Member — Fri, 06 Jul 2007 05:03:04 GMT

Open SQL:

Open SQL consists of a set of ABAP statements that perform operation on central database in the R/3 System. The results of the operations and any error messages are independent of the database system in use. Open SQL thus provides a uniform syntax and semantics for all of database systems supported by SAP. ABAP programs that only use Open SQL statements will work in any SAP R/3 System, regardless of the database system in use. Open SQL statements can work with database tables that have been created in the ABAP Dictionary.

Native SQL:

Native SQL is real SQL for database in use. It means beside OPEN SQL, if you need you can use the native SQL for databases. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.

As a rule, an ABAP program containing database-specific SQL statements will not run under different database systems. If your program will be used on more than one database platform, only use Open SQL statements.

Re: general

Former Member — Fri, 06 Jul 2007 05:08:25 GMT

Hi,

Client Dependent means all data is specific to the client number at which you login,

e.g 800 or 400,

If you create a table, it would be visible across all clients in the server,

but when you put some data into that table, the other clients cannots see this data,

Client Independent means tables having data which is shared across all clients,

eg.

Customizing tables like T000, etc.

Regards,

Samson Rodrigues.

Re: general

Former Member — Fri, 06 Jul 2007 05:13:20 GMT

hi,

Open SQL:

Native SQL:

Client independent data is valid accross the clients whereas client dependent data is valid for the current client.

Technical:

when we add a field MANDT of type MANDT then our table is client dependent and is visible to only that client. But if this Field is not added to the table then we can access the table using any client number.

tables which can be access by all user are client independent (no mandt field in table)

tables which can be access by some specific user are client dependent (use mandt field in table)

Value Table.

This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator.

Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . .

To be maintained as a customization object.

This mean that if you want to enter values to this table you have to create a development request & transport the same.

Macro.

A macro is evaluated during compile time. The generated code can not be debugged. Just do not use macros. They make programs less transparent and difficult to understand in debug mode.

Subroutine.

Subroutines are procedures that you can define in any ABAP program and also call from any program. Subroutines are normally called internally, that is, they contain sections of code or algorithms that are used frequently locally. If you want a function to be reusable throughout the system, use a function module.

Message was edited by:

Roja Velagapudi

Re: general

Former Member — Fri, 06 Jul 2007 05:13:47 GMT

good

diff bet open and native sql->

http://help.sap.com/saphelp_46c/helpdata/en/fc/eb2e7d358411d1829f0000e829fbfe/content.htm

diff bet cliet dependent and client independent->

CLIENT DEPENDENT tables contain the column mandt as the first column wheras

CLIENT INDEPENDENT TABLES don't have this column.

thanks

mrutyun^

Re: general

Former Member — Fri, 06 Jul 2007 05:16:40 GMT

Hi Priya,

(i)Open SQL & Native SQL:

Open SQL consists of a set of ABAP statements that perform operation on the central database in R/3 System. Open SQL provides a uniform syntax and semantics for all the database systems supported by SAP.

Native SQL is SQL for database in use. Besides OPEN SQL, if you need you can use the native SQL for databases.But an ABAP program containing database-specific SQL statements, i.e., native sql statements, it will not run under different database systems. If your program is to be used on more than one database platform, then use only Open SQL statements.

(ii)Client dependent & independent:

Client dependent means all the data is specific to a particular client at which we have logged in.Eg. client 100, whereas in case of client independent, the data can be accessed across all the clients.

(iii)Value table:

When ever we create a domain , we can enter only certain values. When ever we use this domain, the system will force us to enter only these values. These values ar stored in a table named as value table.So value table is the table which contains all the valid values for a field.It is maintained at the domain level.

Reward if useful.

Regards

Sayee

Re: general

Former Member — Fri, 06 Jul 2007 05:26:01 GMT

Hi,

difference between opensql/native sql?

Open SQL allows you to access database tables declared in the ABAP Dictionary regardless of the database platform that you R/3 System is using. Native SQL allows you to use database-specific SQL statements in an ABAP program. This means that you can use database tables that are not administered by the ABAP Dictionary, and therefore integrate data that is not part of the R/3 System.

u can also have a look at the foll. link if u need more details:

http://help.sap.com/saphelp_46b/helpdata/en/fc/eb3b8b358411d1829f0000e829fbfe/content.htm

wht isdifference bt client dependent and independent?

Client dependent means the things which are in client 100 will not be available in the client 200.

Client independent means the things which are in client 100 will be available even in client 200.

Note:- the client numbers given here and for your understanding.

what is macro?difrrence bt macro and subroutine?

Macros are like subroutines..but not used i guess

DEFINE INCREMENT.

ADD 1 TO &1.

END-OF-DEFINITION.

DATA: NUMBER TYPE I VALUE 1.

...

INCREMENT NUMBER.

1. As a rule, you should use subroutines (FORM, FUNCTION)

instead of macros. This is because subroutines - unlike

macros - are supported by all of the ABAP Workbench tools

(debugging, runtime analysis, runtime error handling, ...).

2. You cannot define a macro within a macro using the DEFINE

statement.

3. You cannot use an ABAP keyword as a macro name.

4. The validity of a macro definition is determined by its

position in the source code. You can use a given macro in

any line of code following its definition. There is no

distinction between global and local macros. For example,

the fact that a macro is defined within a subroutine has no

effect on its validity.

5. If you redefine a macro, that is, assign a new meaning to

an existing name, the new meaning takes effect from the

position in the program where the macro was redefined.

Macros can only be used in the program the are defined in and only after the definition.

Macros can take max 9 parameters.

Macros are expanded at compilation / generation.

Subroutines (FORM) can be called from both the program the are defined in and other programs ('perform

' of 'perform in program ').

Subroutines can take any amount of parameters.

Subroutines are 'expanded' at runtime.

Functions are just like FORMs, but are intended to be called external.

Some differences between FUNCTIONs and FORMs:

The name of a FORM must be unique within the program (two programs can have different FORMs with the same name). A FORM is intended to be called internal (from within the program, however by a 'trick' you can call them external).

The name of a FUNCTION has to be unique throughout the system. A FUNCTION is intended to be called external (and is thus shared by 'many' programs).

The latter is more important for programmers and maintenance. Since a FUNCTION is called external, it is important to keep the interface (parameters) the same. The interface of a FORM (which is intended to be called internal) is check when debugging a program (but it is only checked within the program that is debugged). So if the interface of a FORM is changed, but the call to the FORM (perform ) is not, the debugger will notice this and issue an error message.

In general:

A MACRO is more or less an abbreviation for some lines of code that are used more than once or twice.

A FORM is a local subroutine (which can be called external).

A FUNCTION is (more or less) a subroutine that is called external.

Since debugging a MACRO is not really possible, prevent the use of them (I've never used them, but seen them in action). If the subroutine is used only local (called internal) use a FORM. If the subroutine is called external (used by more than one program) use a FUNCTION.

--Excerpt from http://sap.ittoolbox.com/documents/popular-q-and-a/macro-vs-subroutine-1594#

DATA p_c(10).

FIELD-SYMBOLS: <fs> TYPE ANY.

DATA p_old1 TYPE i VALUE 10.

DATA p_old2 TYPE i VALUE 11.

DATA p_old3 TYPE i VALUE 12.

DATA p_old4 TYPE i VALUE 13.

DATA p_old5 TYPE i VALUE 14.

DATA p_old6 TYPE i VALUE 15.

DATA p_old7 TYPE i VALUE 16.

DATA p_old8 TYPE i VALUE 17.

DATA p_old9 TYPE i VALUE 18.

DATA p_old10 TYPE i VALUE 19.

DATA p_old11 TYPE i VALUE 21.

DATA p_old12 TYPE i VALUE 22.

DATA p_old13 TYPE i VALUE 23.

DATA p_old14 TYPE i VALUE 24.

DEFINE ADD_MAPPING.

p_c = &1.

CONDENSE p_c.

CONCATENATE 'p_old' p_c INTO p_c.

ASSIGN (p_c) TO <fs>.

WRITE <fs>.

END-OF-DEFINITION.

DO 14 TIMES.

ADD_MAPPING sy-index.

ENDDO.

http://sap.ittoolbox.com/documents/popular-q-and-a/macro-vs-subroutine-1594

http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/db972835c111d1829f0000e829fbfe/frameset.htm

Regards,

Priyanka.

Re: general

Former Member — Fri, 06 Jul 2007 05:32:42 GMT

Hi,

1)From the help on "open SQL"

Open SQL

Open SQL is a set of ABAP/4 commands which perform operations on database tables. The results of these operations and associated error messages are independent of the database system used. Open SQL thus offers you unified SQL syntax and semantics for different database systems (see Portability). An ABAP/4 program which uses these commands can be run on database systems supported by SAP without modification.

From the help on Native SQL

Native SQL

Native SQL allows you to perform operations on databases over and above those in the Open SQL command set. In contrast to Open SQL, Native SQL supports not only operations on the local database active in the R/3 System, but also on any external databases.

We normally use open SQL, but in some case when you want to say look at the upper case value of an upper/lower case field in a database, you can use native SQL.

Native SQL seems somewhat slower and you have to know which databse you will be using it on before coding.

For more information type EXEC in the editor and press F1.

tables which can be access by all user are client independent (no mandt field in table)

tables which can be access by some specific user are client dependent (use mandt field in table)

3)macro is just like a template.we can't debug a macro but subroutiene we can debug.

define add.

data:res type i.

res = &1 &2 &3.

write:/ res.

end-of-definition.

add 10 + 30.

4)This is maintained at Domain Level.

When ever you create a domain , you can entered allowed values. For example you go to Domain SHKZG - Debit/credit indicator. Here only allowed values is H or S.

When ever you use this Domain, the system will forces you to enter only these values.

This is a sort of master check . To be maintained as a customization object. This mean that if you want to enter values to this table you have to create a development request & transport the same.

rgds,

bharat.

Re: general

Former Member — Fri, 06 Jul 2007 06:00:54 GMT

hi,

1.open sql statements are independent of database used. the database interface converts open sql statements into native sql statements with respect to database used. open sql statements are written in normal language and can be understood by any one.

native Sql statements are database specific. there is no need of any interfece for them to convert. they works more faster than open sql statements. in sap we can use native sql statements using keyword

EXEC

..............

...............

ENDEXEC.

2.client dependent[ local] means accessed only by that client. for ex sap scripts are client dependent. i.e when a user logged in 800 client and developed a script that script can be used by himself. another user logged on 810 client can't use the script developed by 800 client. in sap there are client depenedent and client independent objects.

for ex: sap scripts, tables with mandt field, subroutines,......... are client dependent.

smart forms, tables, data domains, data elements, ....... are client independent.

client independent-> can be accessed by any client or any user in sap. simply they are global .

3.macro is a single line substitution. macro is one form of modularization technique in sap. macro reduces the source code in abap. they are useful for single line substitutions.

for ex: define add.

data: res type i.

write:/10 res

&10 &20 &30

end -of-selection.

10+20.

macros cant be used for code which has more lines.[ single line substitutions]

macros cant be debuggged.

macros cant have more parameters. there is limitation

subroutines are useful for larger code for reusability purposes.

subroutines can be debugged.

subroutines have such limitations.

4. value table is a table which contains values. they are useful in situations where u wanna provide a list of possible values. the user must select any one of the provided values as input.