There is no attachment to split.

[Former Member]

Hello.

I'm working with EDI, and I have a problem with the splitter.

In the channel communication I see the message: "There is no attachment to split. So there is nothing to do".

I noticed that the splitter is configured correctly.

In the Message Monitoring I see the MainDocument is incomplete. In the "Functional_Acknowledgment" there isn't "Transaction_Set_Header" which identifies the type of message.

¿Can be this the problem?

Thank you.

[Former Member]

Hello.

I aren't using 7.1. I think that isn't my problem. My messages are:

SEEBURGER/CLASSIFIER: Successfully read message and configuration data. The analysing and classifing starts now

SEEBURGER/CLASSIFIER: exiting SeeClassifier successfully

SEEBURGER BICXIADAPTER.MODULE Message entered Module (CallBicXIRaBean) and will be passed to the adapter now.

SEEBURGER BICXIADAPTER +++ starting conversion with mapping: Edifact_CEGASA +++

SEEBURGER BICXIADAPTER +++ CONVERSION SUCCESSFUL +++

SEEBURGER BICXIADAPTER.MODULE BIC Module (CallBicXIRaBean) is exiting succesfully.

SEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do.

SEEBURGER/MSGSPLITTER: Finished splitting!

This is de MainDocument of the correct message.

<Functional_Acknowledgment>

<Creation_Date>20090520</Creation_Date>

<Format>EDIFACT</Format>

...

- <Functional_Group_Header>

<Functional_Identifier_Code />

<Application_Sender_Code />

<Application_Receiver_Code />

<Group_Control_Number />

<Version />

- <Transaction_Set_Header>

<Transaction_Set_Identifier_Code>GENRAL</Transaction_Set_Identifier_Code>

<Message_Type_Version_Number>D</Message_Type_Version_Number>

<Message_Type_Release_Number>96A</Message_Type_Release_Number>

<Controlling_Agency>UN</Controlling_Agency>

<Association_assigned_code>EAN003</Association_assigned_code>

<Transaction_Set_Control_Number>EW93279542</Transaction_Set_Control_Number>

<Implementation_Convention_Reference />

<Sequence_of_Transfer />

<First_and_last_tansfer />

- <Notes>

<ID>2</ID>

<Acknowlegdement_Code>7</Acknowlegdement_Code>

</Notes>

</Transaction_Set_Header>

- <Functional_Group_Trailer>

<Number_of_Transaction_Sets_Included>1</Number_of_Transaction_Sets_Included>

</Functional_Group_Trailer>

</Functional_Group_Header>

</Interchange_Control_Header>

</Functional_Acknowledgment>

This is the MainDocument of the incorrect message. There isn't this part.

<Functional_Acknowledgment>

<Creation_Date>20090520</Creation_Date>

<Format>EDIFACT</Format>

<Message_Type />

- ...

- <Functional_Group_Header>

<Functional_Identifier_Code>1</Functional_Identifier_Code>

<Application_Sender_Code />

<Application_Receiver_Code />

<Group_Control_Number />

<Version>EW921250634</Version>

</Functional_Group_Header>

</Interchange_Control_Header>

</Functional_Acknowledgment>

I think that can be the problem, but I'm not sure.

I have asked Seeburguer, but I havent' been answer yet.

Thank you.

[Former Member]

Carmen,

Are you using PI 7.1...does it go through these steps atleast and fail or before even establishing CCI connection...

Information MP: processing local module localejbs/Seeburger/MessageSplitter

Information SEEBURGER/MESSAGESPLITTER: Trying to establish CCI Connection to Message Splitter Adapter

Information SEEBURGER/MESSAGESPLITTER: Creating CCI Interaction

Warning SEEBURGER/MESSAGESPLITTER: There is no attachment to split. So there is nothing to do.

Information SEEBURGER/MESSAGESPLITTER: Finished splitting!

Information SEEBURGER/MESSAGESPLITTER: Message Splitter Module (CallMessageSplitterXIRaBean) is exiting succesfully.

Thanks,

Srini

[Former Member]

Hey

This could be because of pre-delivered message mapping delivered by SeeBurger,just ask them to have a look at it,its possible that mapping might not be deployed correctly or need some patch or upgrade from seeburger.

secondly try the same scenario with other sets of sample files,sometimes it could an issue with file as well.

Thanx

Aamir