system fields

[Former Member]

where are the system fields stored?could u plzz tell

[Former Member]

SYST table.

Thanks,

SKJ

[Former Member]

Hi,

We have a table SYST to store the System fields

Regards

Sudheer

[Former Member]

sumit,

system fields are stored in the standard table syst.

Regards...

Arun.

Reward points if useful.

[Former Member]

The structure SYST stores the <b>system runtime data</b> not a permanent table.

[Former Member]

Hi Sumit,

All the system fields are stored in a structure called 'SYST'.

Example: SY-DATUM for System: Date.

Hope this helps.

Thanks,

Srinivas

[ferry_lianto]

Hi,

ABAP system fields are always available in ABAP programs. The runtime system fills them according to context. They can then be used in programs to query the system status. System fields are variables but you should always treat them as though they were constants, and only read them. If you change their values, important information for the flow of the program may be lost. In exceptional circumstances, system fields may be overwritten in an ABAP program to control the system – for example, SY-LSIND (for navigating to a detail list).

With one exception the names and data types of the system fields are stored in the ABAP Dictionary in the SYST structure and realized as components of the predefined structure SY in ABAP programs.

The system field SY-REPID is not part of SYST or SY. Instead, every program contains the predefined constants SY-REPID and SYST-REPID, which both contain the name of the corresponding program. Furthermore, there are two predefined types of the same name, SY-REPID and SYST-REPID.

All system fields are addressed using SY field name and their types using SYST field name.

For more information, please check this link.

http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/fb96c8882811d295a90000e8353423/content.htm

Regards,

Ferry Lianto

[Former Member]

what r the Modes in Call Transaction?plzz tell

[Former Member]

hi Sumit,

Call transaction <tcode> using <BDCTAB>

Mode <A/N/E>

Update <S/A>

Messages into <MSGTAB>.

Parameter – 1 is transaction code.

Parameter – 2 is name of BDCTAB table.

<b>Parameter – 3 here you are specifying mode in which you execute transaction

A is all screen mode. All the screen of transaction are displayed.

N is no screen mode. No screen is displayed when you execute the transaction.

E is error screen. Only those screens are displayed wherein you have error record.</b>

Parameter – 4 here you are specifying update type by which database table is updated.

S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.

A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).

Parameter – 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:

Regards,

Santosh

[Former Member]

what r the Modes in Call Transaction?plzz tell

[Former Member]

Hi..

<b>

Mode A -- All screens, N - No display ( background ), , E -onli errors</b>

regards,

sai ramesh

[ferry_lianto]

Hi,

There are three modes of Call Transaction method:

1) A – Display All Screens

2) E – Display Errors

3) N – Background Processing

Regards,

Ferry Lianto