Seeburger Splitter Config

Hello Experts,
I have configured Seebuger Splitter as per the documentation:
I am getting following error
SEEBURGER BICXIADAPTER.MODULE Message entered Module (CallBicXIRaBean) and will be passed to the adapter now.
2008-04-02 18:32:28SuccessSEEBURGER BICXIADAPTER +++ starting conversion with mapping: See_E2X_ANSIX12_855_V4010 +++
2008-04-02 18:32:29SuccessSEEBURGER BICXIADAPTER +++ CONVERSION SUCCESSFUL +++
2008-04-02 18:32:29SuccessSEEBURGER BICXIADAPTER.MODULE BIC Module (CallBicXIRaBean) is exiting succesfully.
2008-04-02 18:32:29WarningSEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do.
2008-04-02 18:32:29SuccessSEEBURGER/MSGSPLITTER: Finished splitting!
2008-04-02 18:32:29SuccessApplication attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System.
2008-04-02 18:32:29SuccessTrying to put the message into the send queue
.2008-04-02 18:32:29SuccessMessage successfully put into the queue.
I have configured everything on SB and have used same mapping name (See_E2X_ANSIX12_855_V4010) and same sender id as in EDI document.
Chandra

Hi Chandra,
there is no problem with the configuration the mapping you mentioned is properly working "See_E2X_ANSIX12_855_V4010"
It may be a problem with the input document...
just check the Segemnt "SE" where you have to mention the number of segments from ST to SE including both.
If this count is not a valid one the splitter will not split the child message.
"29WarningSEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do."
cheers,
Sunil.

Similar Messages

Error with Seeburger Splitter module

Hi all,
I had configured Seeburger Splitter and using seeburger splitter module in file adapter with classifier,convertor and splitter in same sequence.But,while testing i m getting null
error for sender file adapter in communication channel monitoring.It isn't able to process the file placed in directory.
When audit log of same is seen,it shows
ERROR : getXmlContentFromMessage()
ERROR : process()
ERROR : Attempt to process file failed with null
Any inputs why is it so.
Regards,
Anoop

Hello Ravi,
We have seen this issue on a few occasions. It might be related to the ConverterJNI class.
In the defaulttrace file you can check for error such as
Caused by: com.sap.i18n.cp.ConverterRuntimeException........
Got exceptions: null
at com.sap.i18n.cp.ConverterJNI.<clinit>(ConverterJNI.java:46).....
If this is the case, Then the problems is within the Startup Framework. I would advise you to update the Startup Framework as described in note #710914.
Thanks,
David

Seeburger splitter configuration issue

Dear All,
I am trying to configure the Seeburger splitter for my outbound EDI interfaces, i enteredmapping Name, clicked on Search Services for the Sender-Sercvice, clicked on Search Channels for the 850 channel i am not able to get the channels automatically.
we have same configuration in DEV and QAS but they are working correctly same objects has been transported to PRD and we are not getting those channels automatically.
Note:but with same configuration objects we are able to get channels automatically in DEV and QAS .. any ideas?
Your help will be appreciated.
Thanks,
Naveen

Hi Naveen,
The channel is populated based on party and service. In your case if you have issue only for one interface (one inbound EDI interface), then it might related to cache.
But if you have problem with all interface, then you need to check the seeburger workbench configuration.
regards,
Harish

Seeburger Splitter adapter!!

hi,
what is Seeburger splitter adapter ?how does it function?
can configure splitter adapter as a module like BIC adapter and Module?
thank you,
babu

Hi Babu,
The splitter is configured with the Functional Acknowledment in Seeburger, this component works in combination with the Seeburger Classifier. For example:
1. You receive a document EDI with the Classifier in a communication channel and this execute the map with the document type sand the version number.
2. The Functional Ack. is generate from the result of the conversion in the map.
3. You have other communication channel configured with the Splitter in a mode Sender.
4. With this, you can map the Functional Ack of Seeburger to a document 997.
5. You have other communication channel with a Receiver mode, to send the result of the mapping process to a SAP or any destination.
This funcionality works with the XI FTP adapter(File), with the FTP Adapter or any other Adapter to receive a document EDI.
You need deploy the 997SplitterMetadata.xml from installation CD with Integration Design and loaded as Adapter Metadata.
To use the splitter, you need configure in the communication channel in the module chain, the BIC and the classifier, in the bic parameters, you define the splitter with true value.
For a example to this component, you can use the Functional Acknowledgement documentation from Seeburger manuals, this have a example to this funcionality.
Greetings,
Hervey

Seeburger Splitter:Fatal error in user mapping . java.lang.StackOverflowErr

Hello,
I have created a mapping E2X_SLSRPT_UN_D96A as we didnt have the standard mapping(See_) from Seeburger
In my scenario when I give hardcoded mapping name ,it works fine,so I assume mapping is correctly created and deployed.
But I need to use it with splitter,and in doing so,I am getting this error:
Message initiation failed: Adapter call failed. Reason: --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=not set;LEVEL=1] Fatal error in user mapping ... java.lang.StackOverflowError at com.seeburger.jucon.dochandler.SegmentDescription.semanticCheck(SegmentDescription.java:444) at com.seeburger.jucon.dochandler.SegmentDescription.semanticCheck(SegmentDescription.java:460) at com.seeburger.jucon.dochandler.SegmentDescription.semanticCheck(SegmentDescription.java:460) at com.seeburger.jucon.dochandler.InhouseDocReader.doSyntaxCheck(InhouseDocReader.java:1555) at com.seeburger.jucon.dochandler.InhouseDocReader.moveNext(InhouseDocReader.java:1852) at com.seeburger.jucon.dochandler.EdifactDocReader.moveNext(EdifactDocReader.java:457) at com.seeburger.jucon.dochandler.InhouseDocReader.moveNext(InhouseDocReader.java:1859) at com.seeburger.jucon.dochandler.EdifactDocReader.moveNext
My splitter configuration is :
classifier     classifierMappingID     Abc
classifier     destSourceMsg     MainDocument
classifier     showInAuditLog     true
bic     destSourceMsg     MainDocument
bic     destTargetMsg     MainDocument
bic     logAttID                          ConverterLog
bic     mappingName     AUTO
bic     saveSourceMsg     ORIGINAL_EDI
bic     split     true
splitter     mode     ASYNC
splitter     transaction     MESSAGE
The same configuration works fine with ORDERS message.
Also,I have configured same mapping name in Splitter section in Seeburger Workbench.
Has anyone encountered this error before?
Kindly let me know
Thanks.
Regards,
Shweta

Hi,
    I understand that you need to use Custom mapping for your EDIFACT Message...
Then did you created the generic mapping with Clasasifier ID...i.e ABC_edifact... (By default it will be See_Edifact)
so you need to create the generic mapping by Name provided in classifier ID of settings then....
need to create the child mapping in such a way that it calls the same (developed one...)
in default cases See_Edifact frames the child mapping name to be called based on the messages received ...
similarly your generic mapping need to call your child mapping....
Hope this clears you
Rajesh

Seeburger Splitter

Hi experts,
i understand that the 997 is used
1. for generating ACK back to sender
2. to split multiple messages like 850,860 comin in the same EDI document.
I referred the blog by Rajesh
/people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
But in my scenario the sample EDI file that I have recieved had a 824 message and a 997 message and the user has told
to map the 824 msg to BANSTA idoc and 997 to Control idoc
My question is how many sender agreement will be there in my case as I think 997 is also a part of my EDI document
pls reply
Edited by: Tarang Shah on Apr 15, 2010 5:15 PM

3 sender areements...
Agrrement 1 --with outbound interface as 824 and sender CC as 997 split
Agreement 2 ---with outbound interface as 997 and sender CC as 997 split
Agreement 3 --- with outbound interface as 997 and sender CC as channel which picks p the file..
and then there would be mappin between 824 and bansta and 997 and control
solved

SeeBurger Message Splitter State accepted or partially accepted

Hi,
The requirement is that if we receive an EDI interchange with multiple transaction sets and if some of them are rejected due to EDI data errors, only those transaction sets in error should be ignored for processing and the ones without errors should successfully come to the integration engine. I suppose this can be achieved by having all our inbound Seeburger splitter configurations in u201CPartially acceptedu201D status.
currently we have set our configurations in accepted state.
Could you please confirm if we change state to partially accepted it wil solve our purpose?
Best Regards,
Harleen Kaur Chadha

Hi.
Create both partial and partial accepted.

Seeburger problem for Custom Mappings..!!!

Hi All,
File to Idoc using seeburger adapters(BIc & split)
When I use standard mapping (Which starts with See_.. )in seeburger splitter configuration, ,the scenario is working perfectly.The idoc is posting in R/3 and Funcack is sending to Partner.
But When I do for customised mappings (Like the ones which we will develop in BIC and deploy into XI and we will use the mapping name like E2X_DT_INVOICE).. then its not working.
I tried by keeping custom mappings (E2X_DT_ORDERS) in splitter configuration. But it didnt work.. !!
Can anyone please tell the changes what I need to do in the modules or in splitter configuration..??
Here is the Module parameters which i mentioned in sender File adapter.
localejbs/SeeClassifier            C
localejbs/CallBicXIRaBean   BIC
localejbs/Seeburger/MessageSplitter   S
C         attID                classifierAtt
C         destSourceMsg        MainDocument
C         showInAuditLog       true
BIC       classifierAttID          classifierAtt
BIC       destSourceMsg       MainDocument
BIC       destTargetMsg         MainDocument
BIC       mappingName           AUTO
BIC       split                          true
1. mappingName I kept as AUTO for standard mappings..
I need to change anything here for Custom Mappings???
2. I didnt mention anything here in split adapter in modules.
Did I need to mention anything here when we do for custom mappings??
Kindly let me know anyone has idea on this.
Thanks&Regards
Seema.

You will also have to create this mapping on the BIC site.
check the documentation on the classifier and functional acknowledgements
Seeburger Classifier with customer mappings.
In the manual Functional Acknowledgement For SAP XI3.0, Configuration Guide this is described. I add a description of how I have configured it at another customer
In the Sender Communication Channel the classifier modules are configured (localejbs/SeeClassifier). This module expects some parameters:
Parameter               Value
attID                    ClassifierAtt
classifierMappingID          XXXX (Choose something for XXXX)
destSourcMsg               MainDocument
showInAuditLog          true
The parameter mappingName of module localejbs/Seeburger/CallBicXIRaBean should be set to AUTO otherwise the classifier functionality wont work.
In the BIC Mapping Designer now you have to create a program called Edifact_XXXX (have a look at page 40 of the manual)
I generated a mapping called Edifact_XXXX from the message Edifact_service with the programs CreateXMLMessage, CreateMappingXMLToEdi, CreateMappingEdiToXML.
After this I adjusted the generated program in the UNH segment I added the following rules:
if name$ = "See_E2X_ORDERS_UN_D96B"
   copy "E2X_ORDERS_UN_D96B" to name$;
endif
With this code you change the mapping name that is called in the BIC to convert the EDIFACT message to XML. Or other functionalities.
The mapping that you use here should be the same as configured in the Splitter of the Seeburger FrontEnd
Screen prints:
Configuration of Sender Communication Channel
BIC MD: Generation programs
BIC MD: New generated mapping Edifact_xxxx from message Edifact_Service
BIC MD:Adjustment in mapping program Edifact_XXXX
Seeburger FrontEnd Splitter configuration

EDI Seeburger problem

Hey,
I'm testing an invoice EDI file which contains 3 invoices. I'm putting the edi file in the ftp but nothing happens. When I check the channel it says this:
Error: com.sap.engine.interfaces.messaging.api.exception.MessagingException: MESSAGESPLITTER:Adapter call failed. Reason: javax.resource.ResourceException: MessageSplitter failed. MESSAGESPLITTER:No configuration found for the source file 7310XXXXXXXXX|See_E2X_INVOIC_UN_D96A|PARTLY_ACCEPTED|1. Please make sure you have configured <Sender>|<MappingName>|<ACCEPTED> in the module configuration or you have used BIC, split is enabled and corresponding splitting configuration is configured in the splitter frontend
The sender IS already setup in Message splitter. I've tried to modify the edi file and it works if it only contains 1 invoice so my best guess is there's some problem with the edifact syntax, but I cant find what it is. What do you think?

Hi Stefan,
you found the solution? I have the same problem and could not find the error.
Fehler:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
MESSAGESPLITTER:Adapter call failed. Reason: javax.resource.ResourceException:
MessageSplitter failed. MESSAGESPLITTER:No configuration found for the source
file 40xxxxxxxxxxxxx|Z_E2X_ORDERS_UN_D93A_2_1|ACCEPTED|1. Please
make sure you have configured
<Sender>|<MappingName>|<ACCEPTED> in the module configuration
or you have used BIC, split is enabled and corresponding splitting configuration
is configured in the splitter frontend.
I checked the splitter configuration twice but the same sender with (customized) mapping and also ACCEPTED is configured.
What does the 1 mean after ACCEPTED?
Does anyone have another hint how to check?
UPDATE / SOLVED : I configured the Seeburger Splitter Configuration on the AAE, but because I have only access
to the filesystem of the Central Adapter Engine I set up the used File Adapter to this and he tried to find the
Splitter Configuration in Seeburger of the PI (CAE).
After configuring it in the other workbench he found it without problem.
regards
Chris

Seeburger AS2 Adapter sending message error

I have configured a FAck scenario as described by the Seeburger Manual and am testing a AS2 messaging scenario with a vendor (basically the inbound EDI message is passed to the Seeburger splitter to create a new message for the inbound order, and then the existing payload is mapped to a Funcational Acknowledgement and sent back to the vendor). I receive the message fine and the message split to create the order works fine, however when the FAck is passed to the AS2 receiver adapter (for transmission to the 3rd party) I get the following error:
LOCATION [null, null, 91fcf4f0-5223-11dd-9c8d-5cd90a641602] >> ERROR TYPE [, COMPONENT_ERROR, not retryable, not fatal]] >> DESCRIPTION [AS2 Adapter failure >> MID
MID <[email protected]22.2> already exists. - Duplicate will not be sent [LOC: com.seeburger.as2.component.AS2Client.storeMID]
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]22.2> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
If I extract the same inbound message from the payload and pass it in using a file adapter (rather than the AS2 sender adapter) then the functional acknowledgement is created and transmitted to the vendor without any issues ...
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Regards,
Jason

Hello ,
same issue occurred in my system
Exception caught by adapter framework: Fatal exception: com.sap.aii.af.ra.cci.XIDeliveryException: SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent, SEEBURGER AS2: AS2 Adapter failure # MID <[email protected]> already exists. - Duplicate will not be sent
I'm not sure where the "duplicate" message comes from as this message definitely has not been sent before.
Has anyone who has had some experience with the Seeburger AS2 adapter got any possible suggestions for resolving this issue?
Please advise asap.

Seeburger - async receiving MDN problem- no binding found for AS2

Hi guys!
We have configured AS2 receiver adapter but during receiveing Async MDN we get following error (sending of message is successful) :
Cannot receive async MDN: com.seeburger.as2.exception.AS2PluginException: Inbound communication from 90586 to 22266 not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No binding found for: AS2, http://seeburger.com/xi, Gloria, R3
Note: Gloria & R3 are names of XI identifiers (scheme: XIParty) and 22266 & 90586 are names from AS2ID scheme - alternative identifiers.
22266 - is sender of original message
90586 - is receiver
What is wrong on the settings? Why the sending message uses alternative identifiers and incoming MDN does not?
Thanx for answers & suggestions!
Peter

Hi Peter
checkm this thread discuss the same ..... hope it will solve ur all querry
Seeburger AS2 Adapter No binding found for: AS2, http://seeburger.com/xi
Thanks !!!
Questions are welcome here!!
<b>Also mark helpful answers by rewarding points</b>
Thanks,
Abhishek Agrahari

Seeburger error - No matching inbound binding found

Hi
I am trying to buld a interface using Seeburger AS2 adapter. I have done all the config in XI and Seeburger level. But when customer sent the message he gets following error.
HTTP/1.1 403 Forbidden^M
server: SAP J2EE Engine/7.00^M
content-type: text/html^M
content-length: 826^M
date: Tue, 18 Nov 2008 23:50:04 GMT^M
^M
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
   <head>
      <title>SEEBURGER AS2 Server: Forbidden </title>
   </head>
   <body bgcolor="#ffffff" text="#000000" link="#0000ee" alink="#0000ee" vlink="
#551a8b">
      <table cellpadding="0" cellspacing="0" border="0" width="100%" bgcolor="#dc4560">
         <tbody>
            <tr><td> </td></tr>
            <tr>
               <td> </td>
               <td valign="middle">
                  <h3>
                     <font face="sans-serif" color="#ffffff">SEEBURGER AS2 Controller</font>
                  </h3>
               </td>
            </tr>
         </tbody>
      </table>
      <br/>
         <font face="sans-serif" size="-1">
           <b>
403 Forbidden
           </b>
         </font>
      <br/>
   </body>
</html>
When I checked the Seebuger log I noticed following
seeburger.as2.AS2Plugin#Plain###Inbound communication from TESTEDI to GFB2BDPI not allowed: com.seeburger.conf.BackingStoreException: Unable to execute query because: com.seeburger.xi.config.ConfigException: No matching inbound binding (message) found for FromParty:PT_TOLL ToParty:PT_GOODMANFIELDER subject:<20081119091602.651278.2248792@> [LOC: com.seeburger.as2.component.AS2Server.checkInboundRelation]#
If someone can help that will be great.
Thanks
Shantha Bandara

Hi,
403 is a standard error if the AS2-IDs are not setup correct. You can also seet his in your log-file:
"Inbound communication from TESTEDI to GFB2BDPI not allowed"
Looks like the SenderAgreement is not referring to the correct parties...
Greetings
Stefan

Without using Seeburger Adapter can we convert EDI 864 TC to XML

Hello Friends,
Can we convert 864 Transaction code (Text Message) to XML with out an External adapter like Seeburger Adapter? I mean can we write a code in JAVA for conversion? If so, what should i use in that Java code?

Hi
These blog can help u....
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/srinivas.vanamala2/blog/2006/12/11/edi-basics
Already discussed thread:
EDI Conversion
Re: Seeburger Splitter adapter!!
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

Comparison between split Adapter in Seeburger and EDI Separator

Hello All,
Currently we are designing EDI interfaces using B2B Add-On.
I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
In Seeburger Splitter configuration:
The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
In B2B Add-On:
The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
Your inputs highly appreciated.
Thanks.
Regards,
Sudharshan N A

Dear Sudharshan,
yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
Kind Regards
Stefan
Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

Seeburger 997 Issue

Hello All,
I am having an issue with the Seeburger adapter especailly with 997 or Functional Acknowledgments.
Whenever I receive a X12 997 message, the adapter is sending out a 997 for it. Is there a way, I can tell the Seeburger splitter adapter to disable this?
Thank you in advance for your help.
Sumant.

Sura,
Aamir is talking about the segment ST and D_143 field. So basically you need to check this field to see whether the transactin is 997 or others. If it is 997 then ignore as aamir told else do the original functionality you are doing.
Just for your reference see this field in the file:
ST9977493~
Regards,
---Satish

Seeburger Splitter Config

Similar Messages

Maybe you are looking for