Field length not updated

[Former Member]

Hi,

My scenario is RFC ---> JDBC

First I import and made my scenario with a BAPI called Z_Test. For some reasons we changed the size of one the field. We passed from 2 to 4 caracters.

So I imported again and went to the message mapping to save again. I actived and launch the test.

Unfortunatly, the size of the field has not been updated.

We have refresh all caches CPA and so on but nothing change.

Any Idear ?

 PB is here ---> <CONTRACT>CD</CONTRACT>  <-----
  <RYTHME_BEGDA>I 20-09-03</RYTHME_BEGDA> 
  <RYTHME_ENDDA>0199-99-12</RYTHME_ENDDA> 
  <FLAG_NEW>3</FLAG_NEW> 

Regards

[former_member206760 · Accepted solution]

Dear Joseph,

Did u agaain select your new rfc in the message mapping..if not do that save and activate

If this doesnot work create a new MM and activate and chk

[Former Member · Accepted solution]

Hi,

I tried what you said but nothing changed.

I do not want to recreate my mapping because it is a hudge one. If you have an easy manner to do... I'm open

Regards

[former_member206760]

just copy the message mapping with a new name and activate and chk

[Former Member]

Done, but still the problem

[Former Member]

I will wait the restar this weekend.

[Former Member]

gud luck

Rajesh

[Former Member]

The restart corrected my issue

It works

tahnks guyes

[Former Member]

Unless you are using PI 7.1 along with validation using XSD, it does not matter. Sender structure is never validated until PI 7.0. Your scenario will run just fine.

[Former Member]

Hi

Check the client wat u r using from u r ID to import RFC, check if it is correct and active in the source system se37.

Better delete RFC from IR and re-import

rgds

srini

[Former Member]

In my re-import process I deleted the RFC and Import again.

No change !

[Former Member]

Hi,

just ask your ABAP guys whether the modified RFC is released in r/3 or not........if it is not released, then release it..........again reimport your RFC in IR and update the mapping......also in your JDBC structure the target field length should be changed to 4 ......activate everything and rerun your scenario.

Regards,

Rajeev Gupta

[Former Member]

My BAPI has been well active.

[Former Member]

As there is only change in the field length go to your Message mapping and update the RFC message there ,unless there is a change in root structure mapping will not get change

once this is done activate and rerun the scenario and are you sure that the length of field changes has been reflected in PI during import if not reimport once again

Rajesh

[Former Member]

Here is my WSDL :

<xsd:element name="CONTRACT" minOccurs="0">
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
         <xsd:maxLength value="4" />
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>

[Former Member]

From where WSDL come into picture?

Rajesh

[Former Member]

In the imported object, I selected my BAPI and open the WSDL tab

[Former Member]

did a change in mapping and activation worked..

are you sure that the input for the field changed is passed with 4 characters instead of 2

Rajesh

[Former Member]

Ok this is weird.

I change my BAPI, I have deleted the field to recreate it at the end of my structure.

Then I updeted my MM et IM. I launched again my BAPI and in my Inbound Message I have the same struture than before changes.

Where Is the cache ???

:'(