Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Warning Message becomes an Error Message in a different SAP instance!

Former Member
0 Likes
1,217

The following code is run in 2 different systems (Both are ECC 6.0). 

TABLES: bape_vbap.
DATA: gw_extensionin TYPE bapiparex.
MOVE bape_vbap TO gw_extensionin-valuepart1.

***In one system, we are getting an error message like below***

gw_extensionin-valuepart1 and bape_vbap are not mutually convertible in unicode program:.

***In the other system, we are getting a warning message like below***

after a structure enhancement, assignment or comparison may not be permitted.

Can anyone tell me why is this difference?

Regards

Tanmoy
SAP Consulting

1 ACCEPTED SOLUTION
Read only

RaymondGiuseppi
Active Contributor
0 Likes
1,106
  • Are both systems Unicode ?
  • Are BAPE_VBAP structures identical in both systems (non character types, length > 254, etc.)

Also ask Abaper to look at form ms_move_extensionin in include LVBAKF0C.

Regards,

Raymond

4 REPLIES 4
Read only

RaymondGiuseppi
Active Contributor
0 Likes
1,107
  • Are both systems Unicode ?
  • Are BAPE_VBAP structures identical in both systems (non character types, length > 254, etc.)

Also ask Abaper to look at form ms_move_extensionin in include LVBAKF0C.

Regards,

Raymond

Read only

0 Likes
1,106

Hello Raymond!

Thanks for the quick response!

First of all, both the systems are unicode.

Secondly,

The structures are not identical in nature.

The system that gives warning message has length > 254.

The system that gives error message has length < 254. I have also tried with a length > 254; but then also it gives me an error message.

Regards,

Tanmoy

Read only

0 Likes
1,106

Are there not-character type fields in any of the structure, as it is no longer allowed to MOVE those in Unicode, and how is the length > 254 managed in the current MOVE statement(s)

Better convert now to Unicode coding, with either same tool than SAP (*) look in the include I provided or find it with where-used on BAPI extension structure as

methods cl_abap_container_utilities=>read_container_c and fill_container_c

Read only

UweFetzer_se38
Active Contributor
0 Likes
1,106

See how SAP is working with these kind of extensions now in an UC system:

CALL METHOD cl_abap_container_utilities=>fill_container_c

           EXPORTING

             im_value      = da_bape_vbap

           IMPORTING

              ex_container = us_extensionout+lenstruc(da_length_bape_vbap)

           EXCEPTIONS

             illegal_parameter_type = 1

             OTHERS                 = 2.

(ie. search in a "where used" list for BAPE_VBAP)