regards:Scripts

[Former Member]

hi i am david,

1, scripts are client dependent & smart forms are client indipendent....WHY?.

2.what is R/3 architecture?

3.what is diffarent between reports and ALV?

4.what is R/3 flow?

5.how to debugg scripts?

6.what si Index and where it is using?

7.what is diffarent between transparent table and pool table, cluster table?

8.Scripts are supports to mailling,why and How?

Regards,

David raju.

[Former Member]

Hi David,

1.If you create a table in 010 client in DEV server with CLNT as its first fields type, then you will find that table structure in all clients in DEV server. (i.e client independent)

example: function module, abap program, smart form.

If you create a record in that table in 010 client, you will not find that record in other clients. (i.e client dependent)

Example: script.

Sap script was developed a long back.

smartform is developed to avoid these type of some restrictions

Also:

Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients

Like SAP SCRIPTS and STD texts data

where as Client Independent means the data if you create in one client that is available in that as well as in other clients

Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..

There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!

As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.

Few more reasons why....? Please read below:

SAPscript technology is based on a mainframe product from the 1980s.SAPscript forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports;

if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean.

Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.

MANDT is the field which differenciates the table from Client Dependent and Client Independent Tables.

All the Scripts are Client Dependent Objects

Smart Forms, Function Modules are Client Independent Objects.

2.SAP R/3 system is to provide a suite of tightly integrated, large scale business applications. Following are the standard set of applications or functional module in R/3 system:

Please check these links

http://www.ryerson.ca/~ppille/sap/Resources/EnterpriseResourcePlanningSAP2.htm

http://www.sapfans.com/sapfans/sapr3con.htm

3. There are 2 type of reports. They are:

Interactive report

Classic reports

In classic reports,we can see the output in single list where as in interactive reports we can see the output in multiple list.

Classical Reports

These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a loop.

Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT.

Events In Classical Reports.

INTIALIZATION: This event triggers before selection screen display.

AT-SELECTION-SCREEN: This event triggers after proccesing user input still selection screen is in active mode.

START OF SELECTION: Start of selection screen triggers after proceesing selection screen.

END-OF-SELECTION : It is for Logical Database Reporting.

[Edit section]

Interactive Reports

As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers.

And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed.

We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).

Events associated with Interactive Reports are:

AT LINE-SELECTION

AT USER-COMMAND

AT PF<key>

TOP-OF-PAGE DURING LINE-SELECTION.

HIDE statement holds the data to be displayed in the secondary list.

sy-lisel : contains data of the selected line.

sy-lsind : contains the level of report (from 0 to 21)

Interactive Report Events:

AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sublist is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sublist.

AT PFn: For predefined function keys...

AT USER-COMMAND : It provides user functions keys.

TOP-OF-PAGE DURING LINE-SELECTION :top of page event for secondary list.

5. Debugging of Scripts

This can done in two ways:

In the form Utilities->debugger / RSTXDBUG FM for debugging script

The Procedure for debugging SAP script is:

Generally SAP script contains the Layout and corresponding print program.

First go to SE71 and enter ur script name. In the same screen go to Utilities->click on activate debugger option.

Now go to SE 38 and enter ur Print Program name and execute the program.

Now you can debug the script Page wise and window wise.

6.Indexes speed up access to rows in a table. They can be created for a single column or for a series of columns. When defining indexes, you specify whether the indexed column values in the different rows must be unique or not.

Please check this link

http://www.sapdb.org/7.4/htmhelp/48/8af59ea54f11d2a97100a0c9449261/content.htm

7. Transparent Table : Exists with the same structure both in dictionary as well as in database exactly with the same data and fields.

Pooled Table : Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data. Several pooled tables can be cominied in a table pool. The data of these pooled tables are then sorted in a common table in the database.

Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to strore control data. They can also be used to store temporary data or texts, such as documentation.

reward if helpful

raam