Batching different messages using Seeburger BIC

Hi Experts
I have an interesting requirement. I need to batch different messages e.g. ORDERS, ASN & Controls into a single Interchange. They are all EDIFACT messages and we are using Seeburger & BIC.
Any idea on how to do this?
regards

reject that nightmare requirement because it would be very difficult for the monitoring team to find error causes in such a message. Imagine BIC conversion will give some the infamous conversion errors because some string is too long. Now if you have dozens of messages in the same document, good luck
CSY

Similar Messages

EDI using Seeburger BIC

Hi,
I am using the BIC module provided by Seeburger for EDI to XML conversion. The input EDI message is a 850 version 4010 message. I have configured the sender communication channel for Functional Acknowledgement and configured the message splitter which is working fine.
When I run this scenario for a few of the test files with a 850 4010 message, the classifier module does not recognise the EDI message as a 850 4010 message and hence the mapping(See_E2X_ANSIX12_850_V4010) is not called. There are no errors in the sender communication channel monitoring and I get only the functional acknowledgement message.
There is a warning message in the CC monitoring which says SEEBURGER/MSGSPLITTER: There is no attachment to split. So there is nothing to do
Am is missing anything here? If so could you please throw some light on this issue.
I have seen this thread Re: SEEBURGER/MSGSPLITTER: There is no attachment to split., but could not get much info.
Thanks,
Chandra

Hi Frederic,
I have configured the message splitter in the seeburger work bench and the split parameter has been set to true in the module configuration. As per my understanding, the 997 message will have a rejected status only if the EDI mapping is called, but this apparently never happens and my guess is that the 850 4010 message is not recognised by the classifier.
The setting works perfectly with one of my test files which is a 850 message as well, so the configuration is right. The situation described in my query occurs for a few 850 messages, since the test data is obtained from several partner systems.
Thanks,
Chandra

Error in Oubound message using Seeburger Adapter

Hi,
I'm getting this error on the Adapter engine when trying to generate an outbound EDI message with Seeburger adapter:
2007-01-24 13:33:29      Error      Unable to forward message to JCA adapter. Reason:
Fatal exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException:
Entry rejected due to error in resource management: null, Entry rejected due to
error in resource management: null
2007-01-24 13:33:29      Error      MP: exception caught with cause
javax.resource.ResourceException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null
2007-01-24 13:33:29      Error      Exception caught by adapter framework: Fatal
exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry
rejected due to error in resource management: null, Entry rejected due to error
in resource management: null
2007-01-24 13:33:29      Error      Delivery of the message to the application using
connection File_http://sap.com/xi/XI/System failed, due to:
com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null: javax.resource.ResourceException: Fatal exception:
com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
to error in resource management: null, Entry rejected due to error in resource
management: null.
Any ideas?
Rgds,
Yves

Yves,
I think there is some problem in invoking the seeburger adapter. Have you installed the adapter? Also after installing you have to import the metadata. Check this document for further help:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
---Satish

IDoc to File[EDI] using seeburger BIC Mapping Tool

Hi Gurus,
I'm having a scenario of IDoc to EDI FIle, I'll be using IDoc DESADV.DELVRY03.ZDELVR0X; Kindly advise steps needed in BIC Mapping Tool. I've already referred to this post /people/dijesh.tanna/blog/2008/05/25/sap-pixi-content-conversion-using-generator-mapping-functionality-of-seeburger-part-1 but still can't get it right.
Thanks.

Thanks a lot experts :D....
I'll be using a file adapter for my scenario..
Any Idea on what Seeburger BIC mapping module should I use?
am I just use the ff module?
Module u2013 Processing Sequence
Number     1     Name     localejbs/CallBicXIRaBean     Type     Local Enterprise Bean     Module Key     bic
Number     2     Name     localejbs/CallSapAdapter     Type     Local Enterprise Bean     Module Key     exit
Module u2013 Module Configuration
Module Key     bic     Parameter name     destSourceMsg     Parameter value     MainDocument
Module Key     bic     Parameter name     destTargetMsg     Parameter value     MainDocument
Please advise.
Thanks.
Edited by: Devilbatz on Dec 8, 2010 8:31 AM

Validating UNB and UNH segment in EDIFACT using Seeburger BIC

Hi Experts,
Just a small thing if someone can help with. What's happening is if an interchange comes with wrong interchange number in UNB vs UNZ segment BIC is actually rectifying that automatically and it makes the UNZ same as UNB. However I don't want BIC to do this.
Any suggestions on how can i stop this from happening please?
regards

Hi Prateek,
Thank you for a quick help I will try that in the morning and I am positive that should settle it.
Hi Rajesh,
That was my understanding too. However for UNH segment the trailer is UNT so if UNH had 100 and UNT had 101 BIC is not throwing an error but it is not correcting it either. But I think I can handle it in messag mapping and itsn't a big deal I was meant to do that anyway.
However for UNB the trailer is UNZ and if I had UNB = 500 and UNZ = 499 BIC will automatically correct and I am positive the reason for that is what Prateek mentioned. And hence by the time I get it in Integration Engine I have no way of knowing it was incorrect. This odd behaviour it is almost like it is set to auto correct.
For UNT it is not doing the right thing either, e.g. if I had UNT = 36 but the real count should have been 38 it will actually autocorrect it to 38 and actually let it pass to message mapping, however the Control it is generating it is rejecting the message based on UNT was not correct.
But for the first two it even creates a control with status 'accepted'.
Thank you guys I will close the thread in the morning if things are working
regards

Seeburger BIC let errors pass

Hi,
We have a scenario where we read from a FTP site. We are using seeburger BIC to convert the messages to something readable.
Unfortantly there are also som junk messages in the file folder or they contain a UNA that Seeburger does not understand. This mean that the seeburger module throws an error. It seems like the FTP adapter cannot move the file to the error folder, so the next file can be processed.
Any ideas on how this can be changed so we can process the files even when some of the messages are failing..
Daniel
[figaf|http://figaf.com]

Hello Daniel,
It seems like the FTP adapter cannot move the file to the error folder, so the next file can be processed.
Any ideas on how this can be changed so we can process the files even when some of the messages are failing..
It could probably be also related to the issue of the file adapter archiving e.g processing mode is set to archive and when there are errors, the rest of the messages cannot be processed or at least some a stucked. What we have done is to set the mode to delete and disable archiving for the moment. Maybe if you also disable the archiving for faulty files, it could also work on your end.
Hope this helps,
Mark

Seeburger BIC module not working

I am using Seeburger BIC module in my sender file adapter. But when I pick up an EDI file using this file adapter, the BIC module is not called. The file adapter simply passes the EDI file to Integration Engine without passing it through the BIC module. Hence, message mapping fails at Integrating Engine as the Message is not in XML form. Also I am not getting any error in adapter monitoring/Message monitoring saying that the adapter module does not exist.
The BIC module is deployed on XI server. I have activated my communication channel. I have put the module names correctly and in proper sequence and also there are no typo errors in entering the parameter names.
Please help.
Regards,
Shweta

R u passing the correct mapping name under the parameter value in module configuration?
Regards,
Anoop

SEEBURGER BIC

Hi All,
I have a question regarding Seeburger BIC, I have read thru one of the Blogs (/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact) which tells that Native EDIFACT is converted into XML EDIFACT and the actual mapping is done in SAP XI. When Seeburger BIC has the capability of coversion from ANY to ANY format why it is preffered to do the mapping in SAP XI.
Can anybody explain what are the pros and cons of using Seeburger BIC for any to any conversion.
Regards,
Bharani

I feel SAP XI is a middleware tool and doesn't have the capabilities for the EDI Mapping
Without Seeburger there is a possibility for developing of adapter or adapter module for this conversion. Seeburger however provides many other functionalities like monitoring and supporting various protocols.
mapping in SEEBURGER would be lot more easier in SEEBURGER when compared to SAP XI.
This is possible. It is not mandatory to use Seeburger with XI. However when you post question in XI forum you will get replies related to Seeburger linked with XI only
There is a conversion engine present if you purchase Seeburger alone and have no XI associated with it. The problem here is seeburger can change the structure of message but does not have vast support of adapters as XI does. Therefore Seeburger with XI provides the best solution. This would be of your interest
http://www.seeburger.com/any-to-any/
Regards,
Prateek

EDI Integration---Using Seeburger Adapter

Hi All,
I have a below requirement.
EDI----->XI--
>SAP and vice versa.
I am new to EDI integration,i would like to know the procedure steps to do the above scenario.
Thanks in advance,
AVR

Hi,
How you want to communicate with the EDI system... If it is using AS2 adapter, then you need to purchase it from seeburger and configure it in the sender side and receiver side it'll be Idoc adapter. And in the ESR you need to import the xsd of EDI document under external definitions and map it to the idoc.Please refer the below links it may help you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005
http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
Handling EDI interfaces using Seeburger BIC modules
Regards,
Priyanka

Seeburger BIC Mapping-Small info required

Hi folks,
I am currently working on Seeburger BIC Mapping designer, Are there any forums for Seeburger BIC Mapping related Issues, can we discuss the Seeburger BIC Mapping related issues in this forum.
Please let me know.
Regards,
Varun

hi
check the link related to bic mapping
1./people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
2.Building own schemas in Seeburger bic mapper
3.BIC mapping names / classes
4.Seeburger - BIC configured as Module
BR
Kasturika

Seeburger BIC module

Hi all,
I am using seeburger BIC module to convert XML file to EDI.
My question is, can we configure BIC module parameter "srcDelimiter" dynamically rather than supplying any value?
Thanks

I dont think you can dynamically set the values for the parameters of the same..
There is an option which you can look for is how to pass dynamic parameters to the mapping using some other module..
In that direction you need to look for..but for bic and for delimiter parameter you cannot pass the values dynamically..
HTH
Rajesh

SAP GTS------- SAPPI with Seeburger BIC----- ATLAS using with SAP PI

Hi All,
I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
For mapping Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
Regards,
Ramesh

>
Ramesh Gulipalli wrote:
> Hi All,
>
> I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
>
> 1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
> 2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
>
> How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
>
> Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
>
> For mapping Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
>
> Regards,
> Ramesh
> .
for converting an XML to EDI or vice versa you can use the seeburger adapter.
http://www.seeburger.com/xi-pi-adapters/

How to re-use one SOAP Sender Channel for two different messages?

Hi!
I have an XI Proxy to SOAP Sync Scenario. 5 messages uses only 2 channels - cc_XI_Sender and cc_SOAP_Receiver. All messages comes from one Sender Channel and goes to one Receiver channel, and it works fine.
When I make the same for SOAP to XI Proxy Sync Scenario, I've got a problem. For example I have 2 different messages (mi_so_MSG_ONE and mi_so_MSG_TWO), so it works, if I had a two different sender channels (cc_SOAP_R1 and cc_SOAP_R2).
If I set the same Sender Channel in both Sender Agreements (cc_SOAP_R1), only one message (mi_so_MSG_ONE) goes without errors. When I send a second message (mi_so_MSG_TWO), in SXMB_MONI this message comes from Business System (BS_TEST) as message type one (mi_so_MSG_ONE), and then in stage of transformation in Interface Determination goes to message mapping program for other kind of messages (MM_MSG_ONE_to_XI_PROXY). And then - error in message mapping.
I try many URLs for both messages:
1) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=&Interface=
2) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=*
3) http://host:port/XISOAPAdapter/MessageServlet?channel=:BS_TEST:cc_SOAP_R1&version=3.0&Sender.Service=BS_TEST&Interface=...MyNameSpace...mi_so_MSG_TWO
Message in payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<MSG_TWO xmlns="urn:xxx:yyy:MyNameSpace" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">... some fields... </MSG_TWO>
But in SOAP Header I see that is NOT second message!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
< !-- Inbound Message   -->
<SAP:Main>
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
<SAP:MessageId>93233F70-3E2F-11DF-8CD3-00237D301CD6</SAP:MessageId>
<SAP:TimeSent>2010-04-02T08:13:09Z</SAP:TimeSent>
<SAP:Sender>
    <SAP:Service>BS_TEST</SAP:Service>
    <SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
</SAP:Sender>
<SAP:Interface namespace="urn:xxx:yyy:MyNameSpace">mi_so_MSG_ONE</SAP:Interface>
</SAP:Main>
Is it correct that many kinds of messages cannot goes through one Sender Channel ? If not... How can I reuse one SOAP Sender Channel for both this messages?
Thanks for helping.

Thanks for answers!
It means a webservice application will be deployed and exposed in PI using the associated Message Interface and its namespace information in the SOAP Sender channel.
It means only one Sender Channel per one pair of names (name of Message Interface and name of namespace). And it will fail if I change something. And question is: why URL for sending SOAP message contains parameter "Interface"?
"backward compatibility" or "for future use only"?
Nothing happens when I change this parameter, seems that name of Interface comes from first of founded Sender Agreements.
If the structures are the same
No. Structures are different.
Making one structure per all SOAP incoming messages looks workable, but... looks strange (in fact I have a lot of SOAP messages, more than 100 Sender channels).
I found an information, that I can use one Sender channel per many messages with different structures only if I make this messages like different Operations in one Service Interface (in PI 7.1).
But in this case in list of messages in SXMB_MONI I will see only a one name of Service Interface for all my messages and it's not so comfortably for supporting: to take a name of operation that fails I need to goes inside.
In older version of XI (prior 7.1) using one sender channel per many messages allowed without any hints.

[svn] 4290: Bug: BLZ-288 - Consumer is only receiving first pushed message when Consumer and RemoteObject that is used to push the messages use different channel sets but same channel .

Revision: 4290
Author: [email protected]
Date: 2008-12-11 14:24:37 -0800 (Thu, 11 Dec 2008)
Log Message:
Bug: BLZ-288 - Consumer is only receiving first pushed message when Consumer and RemoteObject that is used to push the messages use different channel sets but same channel.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* The bug app was arguably generating bogus test data (messages with duplicate ids), and 99.9% of applications won't be configured this way (using multiple ChannelSets with overlapping Channels, pointing at the same server) but it's still worth making this work just right anyways.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-288
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ConsumerMessageDispatcher.as

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

Editing is terminated message when running batch input error using lsmw

Any Idea why would I get the info message like
"Editing is terminated message when running batch input error using lsmw"
please suggest where to look at.
Thanks,
Edited by: mark_yellow mark on Jul 1, 2008 3:27 AM

Hi Mark,
Welcome.
This is lsmw batch input error.while uploading the G/L accounts using the Batch Input process (program name RFBISA00) in LSMW.this error mainly generates...
Fix the error using logs.
thanks
karthik

Batching different messages using Seeburger BIC

Similar Messages

Maybe you are looking for