Warning Message while activating Dictionary Object

[Former Member]

Hi,

As part of our Upgrade project from 4.6c version to ECC 6.0, we have successfuly completed the SPDD and SPAU activities. Now when we are activating the dictionary and repository objects, we are getting some warning messages mostly relating to the calculated and the output length mismatch of the Data Elements.

Can anyone suggest me what is the best thing to do in this scenario and what is the main reason for such warning messages. What will be the implication in case we are ignoring these messages.

jayadeep.

[Former Member]

In the first wave check SPDD with dictionary objects.

The best way is to start with the simplest objects to the most difficult. In our case domain, elements, structures.

In the second wave check SPAU with code objects.

The reasons are obviouslly. All the reports use dictionary objects and there are dictionary objects that contains others. Fix the simplest objects in most cases solves the problem of the complex objects too

[rejish_balakrishnan]

Hi,

"We are getting some warning messages mostly relating to the calculated and the output length mismatch of the Data Elements. "

There r many reason for this ..

1.Is there an unicode conversion problem ... because unicode length varies with nonunicode types.

2.The output tests case what u hav made seems to be off the track ...(the test case and the original data captured in ECC 6.0 might have been different)

3.Did the before upgrade program worked well with unicode check "on" ?

4.Even more ....

"Can anyone suggest me what is the best thing to do in this scenario . "

Check with unicode conversion throughly .

Identify the possible data that might fill up the fields (A case of early prediction of possible data is highly important in upgrade systems)

" What will be the implication in case we are ignoring these messages."

1.It might give u a dump .

2. unwamted messages arise .if that particular data element is being used elsewhere ...

[rejish_balakrishnan]

Hi

Also try to Simulate the scenario with other lesser version systems .

[Former Member]

Hi RBK,

Our upgrade is not unicode compliant and secondly the data elements that are found to be having some warnings messages regarding the output length and the calculated length, have the same specified length in the older versions also, that is the 4.6c.

So in this case can we ignore the warning messages and proceed ahead ?