topic Re: Reg: Macros in Application Development and Automation Discussions

Reg: Macros

Former Member — Fri, 02 Feb 2007 11:44:25 GMT

Can any body tell me what r macros and where we use them and from

where i can learn macros.......

Re: Reg: Macros

Former Member — Fri, 02 Feb 2007 11:49:51 GMT

Macros

Definition

A series of commands and procedures that are carried out in response to a single command or keystroke, or identified by a single name.

Use

You use macros to configure UI patterns in CAF Core to calculate field values based on physical field properties in the Logical Data Source tab pages of the Flex Tree and History Log components. In these applications, you use macros to define field variants.

Structure

CAF Core uses the following predefined set of macro functions:

● @switch

This macro evaluates the contents of the mapped physical field and compares it with the logical field name until it makes a match. The result is the value contained in the logical field. The macro @switch returns value, default_value if there is no corresponding logical field. The macro returns the value nullif a default value is not specified.

@switch(@level(), “Category“, false, true)

● @format

This macro evaluates the aspect field and calls the java.Text.MessageFormat format. The macro @format combines the macro function with the logical field and array of arguments as parameters. The result is new formatting of a field aspect.

@format(

“CreatedAt:\n \nCreated By:\n \nDescription:\n “,

[createdAt],

[createdBy],

[description]

)

● @level

This macro returns the name of the level you are currently evaluating in the application.

● @component_mime

This macro returns the absolute web resource URL of the component’s mime. It takes the development component (DC) name, component name, and relative path as parameters.

@component_mime(

“sap.com/caf_UIptn~historylog”,

“com.sap.caf.ui.pt.historylog.components.log.HistoryLog”,

“buttons/buttons-preview.gif”

)

● @app_mime

The macro returns the absolute web resource URL of the application’s mime. It takes the DC name, application name, and relative path as parameters.

● @dc_mime

The macro returns the absolute web resource URL of the development component’s mime. It takes the DC name and relative path as parameters.

● @sap_mime

This macro returns the absolute web resource URL to the standard image.

@sap_mime(“s_b_disp.gif“)

● @substring

This macro returns substring expressions similar to the java.text.String substring function.

@substring([FullName], 0, 50)

refer....

http://help.sap.com/saphelp_nw04s/helpdata/en/64/fe4efc8d9c4b1a83eec2bbb14ea213/content.htm

Re: Reg: Macros

Former Member — Fri, 02 Feb 2007 11:52:18 GMT

Apart from their readability and efficiency, macros can be more effective than other modularisation techniques because of their versatility in replacing different ABAP statements in solving business problems.

ABAP provides only the syntax for creating macros. It's up to the programmer to devise ways that best suit the requirements. The power of macro programming lies in mastering the ways macros can be used in ABAP programs.

Please look at the following documentation and examples on macros

http://www.builderau.com.au/news/soa/Unleash_the_power_of_macros_in_ABAP/0,339028227,320276178,00.htm

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

http://www.sap-img.com/ab022.htm

Re: Reg: Macros

Former Member — Fri, 02 Feb 2007 12:06:21 GMT

Hi,

<b>Macros</b>

If you want to reuse the same set of statements more than once in a program, you can include them in a macro. For example, this can be useful for long calculations or complex WRITE statements. You can only use a macro within the program in which it is defined, and it can only be called in lines of the program following its definition.

The following statement block defines a macro <macro>:

DEFINE <macro>.

END-OF-DEFINITION.

You must specify complete statements between DEFINE and END-OF-DEFINITION. These statements can contain up to nine placeholders (&1, &2, ..., &9). You must define the macro before the point in the program at which you want to use it.

Macros do not belong to the definition part of the program. This means that the DEFINE...END-OF-DEFINITION block is not interpreted before the processing blocks in the program. At the same time, however, macros are not operational statements that are executed within a processing block at runtime. When the program is generated, macro definitions are not taken into account at the point at which they are defined. For this reason, they do not appear in the overview of the structure of ABAP programs.

A macro definition inserts a form of shortcut at any point in a program and can be used at any subsequent point in the program. As the programmer, you must ensure that the macro definition occurs in the program before the macro itself is used. Particular care is required if you use both macros and include programs, since not all include programs are included in the syntax check (exception: TOP include).

To use a macro, use the following form:

<macro> [<p1> <p2> ... <p9>].

When the program is generated, the system replaces <macro> by the defined statements and each placeholder &i by the parameter <p i >. You can use macros within macros. However, a macro cannot call itself.

DATA: RESULT TYPE I,

N1 TYPE I VALUE 5,

N2 TYPE I VALUE 6.

DEFINE OPERATION.

RESULT = &1 &2 &3.

OUTPUT &1 &2 &3 RESULT.

END-OF-DEFINITION.

DEFINE OUTPUT.

WRITE: / 'The result of &1 &2 &3 is', &4.

END-OF-DEFINITION.

OPERATION 4 + 3.

OPERATION 2 ** 7.

OPERATION N2 - N1.

The produces the following output:

The result of 4 + 3 is 7

The result of 2 ** 7 is 128

The result of N2 - N1 is 1

Here, two macros, OPERATION and OUTPUT, are defined. OUTPUT is nested in OPERATION. OPERATION is called three times with different parameters. Note how the placeholders &1, &2, ... are replaced in the macros.

The following example shows that a macro definition only works in the program lines following its definition. Do not copy it!

Suppose we have a program with a subroutine TEST:

PROGRAM MACRO_TEST.

...

FORM TEST.

WRITE '...'.

ENDFORM.

Suppose we then changed the program to the following:

PROGRAM MACRO_TEST.

...

FORM TEST.

DEFINE MACRO.

WRITE '...'.

ENDFORM.

END-OF-DEFINITION.

MACRO.

Inserting the macro changes nothing in the generated form of the program. Processing blocks - here a subroutine - are always indivisible. We could also write the program as follows:

PROGRAM MACRO_TEST.

...

DEFINE MACRO.

WRITE '...'.

ENDFORM.

END-OF-DEFINITION.

...

FORM TEST.

MACRO.

The most essential feature of a macro definition is that it should occur before the macro is used.

Please reward points if useful.

Re: Reg: Macros

Former Member — Fri, 02 Feb 2007 12:12:38 GMT

also refer below demo code for understanding Use of MAcros -

DEFINE fetch_data.

select * from mara into table &1 up to 20 rows.

END-OF-DEFINITION.

tables mara.

data: begin of itab occurs 0.

include structure mara.

data end of itab.

Fetch_data ITAB.

loop at itab.

write:/ itab-matnr.

endloop.