Multimapping problem

[Former Member]

Hi,

I have a new scenario of File -> Idoc

                                           -> File

Here Source file (# separated) will be like that -

1#a1#a2#a3#a4

1#a1#a2#a3#a4

1#a1#a2#a3#a4

9#3

For this I have done a multi-mapping -

But when the source file is picked up through communication channel its creating an additional tag <Recordset> , that's why giving an mapping error -

Please give any suggestion to remove this extra tag

[Former Member · Accepted solution]

Hello,

Try this in ur FCC:

ignoreRecordsetName  = true

Thanks

Amit Srivastava

[Former Member · Accepted solution]

Hi,

The splitting problem is solved now .

But the problem is that as in target side I have used two different adapters (Idoc and File) , Its not working .

In spite of normal Idoc adapter I have used Idoc_AAE adapter provided in PI 7.3.

But now the problem is that its not creating any idoc in the target side for the correct file .

[abhradeepbasu · Accepted solution]

Hi Apu,

Your target structure (from your scrrenshot) doesn't look like the Idoc type. Are you refering to some other structure?

/AB

[Former Member · Accepted solution]

Hi Abradeep,

We have used custom Idoc in message1  and   File in message2.

Now the problem is that as we are running the interface it not showing any error in the sxmb_moni , but it is not creating any idoc in receiver side.

And the file is also not created .

[former_member190624 · Accepted solution]

Hi Apu,

Can you  provide screen shoot of conditions you provided for parent nodes (

Message1 , ZME_SBM_TYP and Message2 , MT_SBMAuditFile)?

BTW, are you able to see output in message mapping ?

Regards

Hari.

[Muniyappan · Accepted solution]

Hi Appu,

Now the problem is that as we are running the interface it not showing any error in the sxmb_moni , but it is not creating any idoc in receiver side.

Take the payload from sxmb_moni.

Test this in the message mapping.

See if you get the required idoc output message.

it this is producing correct output. then check the receiver idoc adapter channel.

message is successful here then you need to check in the ECC side.

Hope this helps you..

Regards,

Muniyappan.

[former_member190624]

Hi ,

Cross check your message mapping again , whether you mapped all parent nodes (Idoc) or not .

Regards

Hari.

[abhradeepbasu]

Hi Apu,

Did you put 'RecordSet' as RecordSet Name in your File adapter configuration? Try ignoring that part, I think that is optional part in File adapter configuration.

/AB

[MichalKrawczyk]

Hi,

>>>>But when the source file is picked up through communication channel its creating an additional tag <Recordset>

you cannot remove the recordset structure

quickest solution:

update your data type with recordset node

Regards,

Michal Krawczyk