ABAP REPORTS

Data flow between SAP and BW

Syntax for modify data in internal table

Modify Syntax for change list line part two

noreply@blogger.com (suresh) — Tue, 10 Mar 2009 00:30:45 PDT

This post is in continuation with Modify Syntax for change list line part ONE and going through that will give more comfort in understanding the present post.

Addition 3

... FIELD VALUE f1 FROM g1 ... fn FROM gn

Effect

Overwrites the contents of the fields f1 , f2 , ... in the list line with the current contents of the fields g1 , g2 , ... (type conversion as for MOVE g1 , g2 , ... to type C). The field contents of f1 , f2 , ... themselves remain unchanged.

If a field (e.g. f2 ) is output several times in the line to be modified, only the first occurrence is modified.

If the field is not output in the line at all, it is ignored.

You can omit the addition FROM g2 if the field f2 in the list line is to be modified from the current contents of f2 .

This means that ... FIELD VALUE f2 has the same effect as ... FIELD VALUE f2 FROM f2 .The return code value of SY-SUBRC is not affected by the addition FIELD VALUE and so only depends on the existence of the selected list line.

Addition 4

... FIELD FORMAT f1 fmt11 ... fmt1m
... fn fmtn1 ... fmtnm

Effect

Modifies the output format of the field f1 according to the format specifications fmt11 ... fmt1m . Similar to f2 , ..., fn . For a list of valid format specifications, see FORMAT . Fields that occur several times or not at all in the line are treated as in the addition FIELD VALUE .

If you combine the additions LINE FORMAT and FIELD FORMAT , the format set by LINE FORMAT is always valid for the whole line initially. After wards, it is changed by the format specifications for the individual fields.

Example

DATA: FLAG VALUE 'X',
TEXT(20) VALUE 'Australia',
I TYPE I VALUE 7.
FORMAT INTENSIFIED OFF.
WRITE: / FLAG AS CHECKBOX, TEXT COLOR
COL_NEGATIVE.
AT LINE-SELECTION.
MODIFY CURRENT LINE
LINE FORMAT INTENSIFIED
FIELD VALUE FLAG FROM SPACE
FIELD FORMAT FLAG INPUT OFF
TEXT COLOR = I.

When the user selects the displayed list line by double-clicking, the checkbox for FLAG is reset and can no longer accept values. The format of the entire line is set to "intensified" and TEXT is
displayed in a different color. (97.4)

SAP BW TOPICS

Data flow between SAP and BW

Syntax for modify data in internal table

Syntax Modify Change list line

noreply@blogger.com (suresh) — Fri, 06 Mar 2009 02:22:57 PST

Variant 1

MODIFY LINE n.

Additions

1. ... INDEX idx
2. ... LINE FORMAT fmt1 ... fmtn
3. ... FIELD VALUE f1 FROM g1 ... fn FROM gn
4. ... FIELD FORMAT f1 fmt11 ... fmt1m ... fn fmtn1 ... fmtnm

Effect

Changes the n th line of the list. This could be, for example, after line selection ( AT LINE-SELECTION , AT PFxx , AT USERCOMMAND ).

The current contents of the system field SY-LISEL are restored to the list as the line contents and the HIDE area for the line is re-determined from the current contents of the fields hidden
with HIDE .

The return code value is set as follows:

SY-SUBRC = 0 Line was successfully changed.
SY-SUBRC <> 0 Line does not exist.

With multiple-level line selection, the modification is always performed in the list where the (last) line selection was made, except in the case of the addition ... INDEX idx and MODIFY CURRENT LINE .

Addition 1

... INDEX idx

Effect

Changes the relevant line in the list to list level idx (0, 1, 2, ...) with multiple line selection ( SY-LSIND ).

Addition 2

... LINE FORMAT fmt1 ... fmtn

Effect

The output format of the selected line is determined by the format specifications fmt1 , fmt2 ... . For a list of valid format specifications .

Example

DATA I TYPE I VALUE 2.

WRITE: / 'Intensified' INTENSIFIED,

'Input' INPUT,

'color 1' COLOR 1,

'intensified off' INTENSIFIED OFF.

* Line selection

AT LINE-SELECTION.

MODIFY CURRENT LINE

LINE FORMAT INVERSE

INPUT OFF

COLOR = I.

After you have selected the the output list line (by doubleclicking), the whole line is set to COLOR 2 and INVERSE and all INPUT fields are set to INPUT OFF . The fields with the attribute INTENSIFIED or INTENSIFIED OFF retain this because the attribute is not addressed here.(96.8)

SAP BW TOPICS

Data flow between SAP and BW

Syntax for modify data in internal table

Thank you for visiting SAP ABAP REPORTS.If you liked the post, please subscribe to RSS FEED or get the updates directly into your mail box through EMAIL SUBSCRIPTION.If you want to contact me click here.

Challenges in SAP Testing

noreply@blogger.com (suresh) — Wed, 04 Mar 2009 08:49:35 PST

Established commercial implementation methodologies for SAP typically fail to address how requirements will be met, the criteria for testing, the framework for utilizing test tools, necessary resources for testing, estimating testing budgets, specific testing roles and responsibilities, and how test defects will be managed and resolved.

Many factors hamper successful testing at most SAP projects such as unclear requirements, inability to trace the system design to requirements, missing dedicated test teams, waiving defects without appropriate workarounds, and inadequate involvement of needed participants for testing such as subject matter experts (SMEs) for capturing requirements and end users for user acceptance testing.

Industry data shows that removing system defects in a live production environment is at least 20 to 40 times more expensive than doing so in the unit-testing phase or during the requirements gathering phase. Many defects can be eliminated or prevented altogether with thorough evaluation and peer review of requirements.

Many corporations pay expensive consulting fees to fix production problems arriving at the production help desk rather than address these problems or defects during the applicable testing phase.

The main reason that this occurs is that SAP projects often do not spend the time or have the appropriate resources to ensure that the captured requirements are peer reviewed and evaluated with objective criteria, or to construct an RTM to provide coverage for all requirements and establish objective testing criteria for each testing phase.

Another overlooked reason that causes defects that should have been resolved during testing to slip into the production environment is that individuals acting as SAP testers cannot reach consensus on testing nomenclature or the test approach.

Another challenge for testing SAP is inadequate training at all levels for either cross-matrixed testing resources or dedicated testing resources. Training is needed for testers who are participating in one-time testing efforts such as user acceptance testing, or participating in all testing efforts for execution of test cases and resolution of defects.

The test manager needs to develop the procedures for mentoring and educating all project resources who are expected to participate in testing activities.

Training consists of the following activities:

Training dedicated testers on how to maintain and install automated test tools, test management tools, and develop automated test cases.
Training testing participants on test procedures for logging defects and reporting test results.
Training on how to evaluate and peer review requirements.
Training on testing nomenclature to standardize testing terms for all project members.
Training for roles and responsibilities for resolving defects.(25.8)

SAP BW TOPICS