topic Additions in Application Development and Automation Discussions

Additions

Former Member — Thu, 27 Sep 2007 10:55:11 GMT

wat r the additions of write statement

Re: Additions

Former Member — Thu, 27 Sep 2007 10:55:57 GMT

hi,

WRITE F

…AT P1 (POSITION AND LENGTH SPECIFICATION)

…AS CHECKBOX

…AS SYMBOL

…AS ICON

…AS LINE

…NO-ZERO

…NO-SIGN

…DD/MM/YY

…USING EDIT MASK MASK

…USING NO EDIT MASK

…UNDER G

…NO-GAP

…TO G

…TO ITAB INDEX IDX.

Please reward if useful...

Re: Additions

Former Member — Thu, 27 Sep 2007 10:58:46 GMT

WRITE [AT] [/][pos][(len||*)] dobj

[int_format_options]

[ext_format_options]

[list_elements]

[QUICKINFO info].

... [LEFT-JUSTIFIED|CENTERED|RIGHT-JUSTIFIED]

[NO-GAP]

[UNDER other_dobj]

{ { [EXPONENT exp]

[NO-GROUPING]

[NO-SIGN]

[NO-ZERO]

[CURRENCY cur]

{ { [DECIMALS dec]

[ROUND scale] }

| [UNIT unit] } }

| [TIME ZONE tz] }

[USING { {NO EDIT MASK}|{EDIT MASK mask} }]

[ DD/MM/YY | MM/DD/YY

| DD/MM/YYYY | MM/DD/YYYY

| DDMMYY | MMDDYY | YYMMDD ] ... .

Extras:

1. ... LEFT-JUSTIFIED|CENTERED|RIGHT-JUSTIFIED

2. ... NO-GAP

3. ... UNDER other_dobj

4. ... EXPONENT exp

5. ... NO-GROUPING

6. ... NO-SIGN

7. ... NO-ZERO

8. ... CURRENCY cur

9. ... DECIMALS dec

10. ... ROUND scale

11. ... UNIT unit

12. ... TIME ZONE tz

13. ... USING { {NO EDIT MASK}|{EDIT MASK mask} }

14. ... DD/MM/YY | MM/DD/YY

| DD/MM/YYYY | MM/DD/YYYY

| DDMMYY | MMDDYY | YYMMDD

Example

Output of three literals left, in the middle, and to the right of an output area 60 characters in length.

WRITE: /(60) 'Left' LEFT-JUSTIFIED,

/(60) 'Center' CENTERED,

/(60) 'Right' RIGHT-JUSTIFIED.

Example

Table-type output of flight connections.

DATA: carrid TYPE spfli-carrid,

connid TYPE spfli-connid.

WRITE: 10 'Carrier', 40 'Connection'.

ULINE.

SELECT carrid connid

FROM spfli

INTO (carrid,connid).

WRITE: / carrid UNDER 'Carrier',

connid UNDER 'Connection'.

ENDSELECT.

Example

Output of a UTC time stamp in Tasmanian time. In daylight-saving time, the output is "28.06.2002 04:00:00".

DATA: time_stamp TYPE timestamp,

tzone TYPE timezone.

time_stamp = 20020627180000.

tzone = 'AUSTAS'.

WRITE / time_stamp TIME ZONE tzone.

Here are some of the examples............

Regards,

Pavan

Re: Additions

varma_narayana — Thu, 27 Sep 2007 10:59:01 GMT

Hi ...

To find the additions of any statement place the Cursor on the statement and press F1. It will show all the additions.

For write statement additions.

Some:

WRITE:/ <FIELD> LEFT-JUSTIFIED.

WRITE:/ <FIELD> right-JUSTIFIED.

WRITE:/ <FIELD> CENTERED.

WRITE:/ <FIELD> AS CHECKBOX.

WRITE:/ <FIELD> COLOR COL_POSITIVE.

reward if Helpful.

Re: Additions

Former Member — Thu, 27 Sep 2007 11:03:30 GMT

Hi,

WRITE

Syntax

WRITE [AT] [/][pos][(len||*)] dobj

[int_format_options]

[ext_format_options]

[list_elements]

[QUICKINFO info].

WRITE - int_format_options

Syntax

... [LEFT-JUSTIFIED|CENTERED|RIGHT-JUSTIFIED]

[NO-GAP]

[UNDER other_dobj]

{ { [EXPONENT exp]

[NO-GROUPING]

[NO-SIGN]

[NO-ZERO]

[CURRENCY cur]

{ { [DECIMALS dec]

[ROUND scale] }

| [UNIT unit] } }

| [TIME ZONE tz] }

[USING { {NO EDIT MASK}|{EDIT MASK mask} }]

[ DD/MM/YY | MM/DD/YY

| DD/MM/YYYY | MM/DD/YYYY

| DDMMYY | MMDDYY | YYMMDD ] ... .

WRITE - ext_format_options

Syntax

... [COLOR {{{color [ON]}|OFF}|{= col}}]

[INTENSIFIED [{ON|OFF}|{= flag}]]

[INVERSE [{ON|OFF}|{= flag}]]

[HOTSPOT [{ON|OFF}|{= flag}]]

[INPUT [{ON|OFF}|{= flag}]]

[FRAMES [{ON|OFF}|{= flag}]]

[RESET] ... .

WRITE - list_elements

Syntax

... {AS CHECKBOX}

| {AS ICON}

| {AS SYMBOL}

| {AS LINE} ... .

WRITE /

Syntax

WRITE /.

Effect

This statement has the same effect as the statement SKIP.

Regards,

Bhaskar

Re: Additions

Former Member — Thu, 27 Sep 2007 11:05:21 GMT

WRITE [AT] [/][pos][(len||*)] dobj

[int_format_options]

[ext_form at_options]

[list_elements]

[QUICKINFO info].

1. ... [AT] [/][pos][(len||*)]

2. ... QUICKINFO info

This statement writes the content of the data object dobj to the current page of the current list in the list buffer. All flat data types and the data type string are allowed for dobj; flat structures are treated as a data object of type c. The data object dobj can be specified by a field symbol or a dereferenced data reference (for release 6.10 and later). The format of the output is predefined ( see predefined output formats), but can be modified with the additions AT and int_format_options. The output that has been formatted in this way, can be formatted further with ext_format_options, and list_elements allows specific list elements to be displayed.

The output position is either determined by the list cursor , or specified with pos after AT. At the start of every output, the output position in the list buffer is the same as that in the list representation. In Unicode systems, the positions of individual characters within an output field can differ between the list representation and the list buffer. In both cases, though, the output length is the same.

The output length is determined through the data type of dobj or can be specified with len||* after AT. len specifies an absolute length , whereas * or ** ensure that characters in Unicode systems are not truncated by mistake.

If the last line of the current page is reached and a subsequent line is output, a new page is generated. The maximum number of lines is determined with the addition LINE-COUNT of the introductory statement or the statement NEW-PAGE. For the basics list, the END-OF-PAGE event is triggered when the area reserved for the page footer is reached, and a new page is subsequently generated.

After positioning of the list cursor with a previous output statement, if the output length is larger than the area available in the current line of the list buffer, the output goes to the next line. If this line is also not sufficient for a complete output, the output length is correspondingly shortened and the output is displayed in this line.

If the list cursor is positioned using the pos specification or a statement BACK, NEW-LINE, NEW-PAGE, POSITION or SKIP and not with a previous output statement, then the output is always displayed in the current line, and the output length is shortened, if necessary.

After the output is displayed, the list cursor is positioned by default in the second position after the output; the sy-colno and sy-linno system fields are set correspondingly.

If the data object dobj is declared with reference to a data type from the ABAP Dictionary, the field and input help defined there are available in th elist displayed on the screen.

In the default setting, the system does not place a new line in a list that contains only blank characters. Such a line is displayed only if the list cursor is directly positioned in an existing line, i.e. , not via a line break. You can change this setting with the statement SET BLANK LINES ON.

Addition 1

... [AT] [/][pos][(len||*)]

The output position and length for the current statement WRITE can be defined after AT. The output position of already existing outputs in the list buffer is overwritten with the output length of the new output. After overwriting an already existing output, the list cursor is placed at the next position, not two positions over.

The components of the position and length specification /,pos and len resp. * resp. ** must be listed with no spaces and in the specified sequence. If pos and len are not specified at all or are declared as numeric literals, the addition AT can be omitted.

With / , the output is displayed in the next line after the current line. If no position pos is specified, the output is written from the first column onward. The specification of / has no effect immediatel after positioning the list cursor in a list line (that is not the result of a previous output statement). This is the case during initial writing to a list page, and after explicit positioning with the statements SKIP, NEW-LINE, NEW-PAGE and BACK.

The output position is determined by pos. pos is expected to be a data object of the type i, which contains a value within the list width. No output is displayed if the value in pos is less than 1 or greater than the current list width.

The output length is determined by specifying len, * or ** in brackets. Using len, an absolute value can be specified. len is expected to be a data object of type i, which contains a value within the current list width. No output is displayed if the content of len is less than or equal to 0. In Unicode systems, the number of characters displayed in the list can be different than the number of characters stored in the list buffer by specifying len. By specifying * or **, the output length depends on the data type of the data object dobj, as shown in the following table.

Data type * **

c Number of columns needed in the list to display the entire content; no final blank characters are taken into account. In Unicode systems, this length can be greater than the implicit length. Doubled data object length.

string implicit length Doubled number of characters contained therein.

n, x, xtring implicit length implicit length

d 10 10

t 8 8

i, f, p Necessary length to output current value, including thousands separator; value determined after evaluating possible additions CURRENCY, DECIMALS, NO-SIGN, ROUND or UNIT. Necessary length to output maximum possible vlaue, including thousands separator; value determined after evaluating possible additions CURRENCY, DECIMALS, NO-SIGN, ROUND or UNIT.

When a conversion routine is executed with reference to a data type in the ABAP Dictionary, when len is specified, it is carried out for the lengths specified thereein, and when * or ** are specified, it is carried out for the output lengths specified in the ABAP Dictionary. When specifying * or **, the output length is then determined according to the aforementioned rules from the result of the conversion routine. The specification of * or ** when using formatting templates (USING EDIT MASK, DD/MM/YYYY etc.) is described in the respective section.

The specification of the output length len after AT should always be preferred over the use of a length specification for data object dobj (partial field access). In contrast to partial field access, the specification of the output length is not restricted to byte- and character-type data objects. Furthermore, the assignment of the list output to the data object is lost during a partial field access, in that it can no longer be addressed in the list.

The specification of * or ** for the output length ensures that, independent of data type, all characters from dobj are presented, even when more columns are needed in the list than positions in the list buffer. With *, the minimum possible length is used, and with **, the maximum possible length is used.

When an output position is specified within an already existing output, you should ensure that the position always refers to the characters stored in the list buffer. If characters that require more than one column in the list are displayed in a Unicode system, the displayed output position can differ from the specified output position. In addition, the displayed content of a partially overwritten output can be shifted, depending on the characters that overwrote the output.

Addition 2 ... QUICKINFO info

A Quickinfo is assigned to the output. If the mouse cursor is placed on the output area of dobj, the content of info appears in a coloured rectangle. For info, a character-type data object of the length 40 is expected.

The addition QUICKINFO has no effect on ready-for-input fields and line elements. If a list output is overwritten by another output, then no Quickinfo for the overwritten field appears beginning from the position at which the overwriting starts.

WRITE /.

This statement has the same effect as the statement SKIP.

WRITE - TO

WRITE {source|(source_name)} TO destination

[int_format_options].

This statement assigns the formatted content of the data object source, or the formatted content of the data object whose name is contained in source_name, to the data object destination. The data objects source_name and destination must be character type and flat. source_name can contain the name of the data object to be assigned in upper or lower case. If the data object specified in source_name does not exist, the assignment is not executed, and sy-subrc is set to 4.

The statement WRITE TO has the same effect as the statement WRITE for lists. This statement formats the content of source or the source field specified in source_name as described in the field. It does not, however, store the result in an output area of a list in the list buffer, but instead stores it in a variable. The output length is determined by the length of the variable.

The same additions int_format_options can be specified for formatting the content as in the statement WRITE for lists, except for NO-GAP and UNDER.

System fields

sy-subrc Meaning

0 The data object specified in source_name was found and the assignment was executed.

4 The data object specified in source_name was not found and the assignment was not executed.

For the static specification of source, sy-subrc is not set.

If destination is specified as an untyped field symbol or an untyped formal parameter, and is not flat and character-type when the statement is executed, this leads to an untreatable exception in a Unicode program. In non-Unicode programs, this only leads to an exception for deep types. Flat types are handled as character-type data types.

WRITE TO itab

WRITE dobj TO itab[+off][(len)] INDEX idx

[int_format_options].

This variant, forbidden in classes, of the statement WRITE TO has the same effect as the allowed variant, with the difference that the edited content is written to the row in the internal table itab in which idx is specified. The internal table must be a standard table. The same requirements apply for the row type as for the variable destination.

For idx, a data object of the data type i is expected. It must be a data type which, when the statement is executed, contains the index of the row to be overwritten. If the value of idx is less than or equal to 0, you have an exception that cannot be handled. If the value of idx is greater than the number of table rows, no row will be overwritten and sy-subrc will be set to 4.

After the table name itab, offset and length specifications off and len can be made. These refer to the specified table row.

System fields

sy-subrc Meaning

0 The data object specified in source_name and the row specified in idx were found and the statement was executed.

4 The data object specified in source_name or the row specified in idx were not found and the statement was not executed.

This form of statement WRITE TO is now only possible outside of classes and is replaced by field symols or data references through access to table rows. The following rows show the implementation with a field synmbol:

FIELD-SYMBOLS <line> LIKE LINE OF itab.

READ TABLE itab INDEX idx ASSIGNING <line>.

WRITE dobj TO <line>[+off][(len)][int_format_options].

REWARD IF USEFULL