Warning codes generated in UCCHECK

[Former Member]

Hi SDN'ers ,

I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a

problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by

checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block

"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can

be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end

I want to know

- Which are the warning codes which need resolution so that the program does not encounter any runtime

errors or during Integration testing ?

- Do all the offset related errors (For example ;variable A = B+offset(length)

or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.

- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.

The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to

non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.

S.No. Error Code Message

1 ABB Syntax Check Aborted

ABB Total

2 MESSAGEG!C check at runtime. at runtime.

statement because of untyped or generic operands. It can only carry out this

The system could not perform a static convertibility check on the current

MESSAGEG!C Total

3 MESSAGEG!D out this check at runtime. It can only carry out this check at runtime.

to a table line because of untyped or generic operands. It can only carry out

The system could not perform a static check on convertibility from a work area

MESSAGEG!D Total

4 MESSAGEG!E check at runtime. at runtime.

defined by a "DATA" statement. .

statement because of untyped or generic operands. It can only carry out this

Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor

The system could not perform a static comparability check on the current

MESSAGEG!E Total

5 MESSAGEG!F operand "<FELD1>" for the current statement. .

MESSAGEG!F Total

6 MESSAGEG!G current statement on incompletely typed operand "<DATA>". .

MESSAGEG!G Total

7 MESSAGEG!H for the incompletely typed operand "<S>". . - - - - - - - - -

The system cannot perform a static check on a character-type field data type

MESSAGEG!H Total

8 MESSAGEG!I incompletely-typed operand "<A>" in the current statement. .

The system cannot perform a static check on a character-type data type for the

MESSAGEG!I Total

9 MESSAGEG!J "<%_1_SYSINI>" in the current statement to check whether the operand can be

The system cannot perform a static check on incompletely-typed operand "VALUE"

MESSAGEG!J Total

Early response wil be highly appreciated.

10 MESSAGEG!K "<F_YEAR>" in the current statement to check whether the operand can be

The system cannot perform a static check for incompletely-typed operand "WINY2"

MESSAGEG!K Total

11 MESSAGEG!M .

at runtime. .

check will take place at runtime. .

entries for operand "<F_SOURCE>(2)". This check will take place at runtime. .

entries for operand "<F_SOURCE>+2(2)". This check will take place at runtime.

The system cannot perform a static check on the validity of the offset/length

MESSAGEG!M Total

12 MESSAGEG!P out this check at runtime. at runtime.

statement because of untyped or generic operands. The system can only carry

The system could not perform a static compatibility check on the current

MESSAGEG!P Total

Grand Total

[Former Member]

Hi Monica,

as bhaskar said no need to worry about warnings.

warnings will not lead to dump. only runtime errors will lead to dump.

if the system is unicode, remediate the objects without errors.

we can observe mainly,

open dataset, structure incompatibilty, offset, in byte or char mode etc

thanks

vinod

[Former Member]

Dear Monica,

As for as my 14 projects experience in upgrade projects, no need worry about the warning in UCCHECK, bcs unless and until if you resolve the error, that object wont works fine. its mandatory to resolve unicode related errors like for ex: type x problems, structure fileds unknown, etc.

So most probably we can ignore warnings comes in UCCHECK transaction. Still if you are facing issues please let me know.

Regards

Arani Bhaskar