BIC Seeburger

Hi all,
What is use of BIC tool, is this BIC tool is mandatory if we use the Seeburger Adapter(any type AS2, OFTP etc).
BIC mapping programs are deployed as SDA files, how to test this these Mappings.
Is there any possibility to get the list of Depolyed files to use them in Module processor.
regards
Hasini

BIC is a client application. Its like yahoo or any other client software.
Once you install u will se the BIC from start->program->seeburger.
The SEEBURGER Business Integration Converter (BIC) is an any-to-any format converter, used to translate EDI data and legacy data formats into XML and vice versa. It can also be used for complex, high performance XML-to-XML mappings or to interface to existing JDBC data sources.
Supported EDI formats include:
ANSI
EDIFACT
INHOUSE
IDOC
XML Schema
XML DTD
CSV
Delimited Data
positional data
SWIFT
EANCOM
and many more.
See for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program at the adapter module which does the conversion. For this module you need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
please look in to this links u will come to know about seeburger adapter.
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://help.sap.com/saphelp_nw04/helpdata/en/e6/2eb540e4c5782ae10000000a155106/frameset.htm
Edited by: Ashok Reddy Thatigutla on Apr 13, 2008 12:27 PM

Similar Messages

Error in BIC MODULE BIC MODULE modules: trigger file [not specified] conta

Hello, i have a problem with the BIC Seeburger MD
Scenario overview:
IDoc Invoice02 => Message Mapping (Seeburger content) => FTP Seeburger Comm. Canal integrated with BIC adapter. This works correctly. Then I tested the field mapping and the BIC Adapter brings no more errors in field mapping.
BUT NOW THIS ERROR MESSAGE IS:
Error in BICMODULE modules: Temporary error: BIC XI Adapter call failed. Reason: Error: [Error: ID = 1104; LEVEL = 3] trigger file [not specified] contains no valid trigger. DESCRIPTION: You have specified no valid trigger for that mapping. Please change this within BIC Mapping Designer.
Destination Message is the Edifact Invoic D96A
I hope one of you can help me
Kind regards
Tobias

Hi Tobias,
there is a either a problem with your XML Message or with the BIC Mapping which converts XML to EDI.
What's the name of the BIC-Mapping that you use in your FTP Module chain?
You can also check the following to make sure, your BIC Mapping works correctly:
a) Take your Invoice Idoc and convert it with the Message Mapping into Edifact-XML
b) Use BIC Mapping Designer and open the Mapping that you use in the Module Chain (Should be XML-->Edifact)
c) Take the Edifact-XML Message from your PI Message Mapping and convert it in the Test Environment of BIC Maping Designer.
If you get the same error, there's something wrong with your Edifact-XML message
If the mapping works, there's something wrong in your module configuration. (Maybe you can post your module configuration)
regards,
Daniel

Seeburger Parameters "DestDelimiter"

Hi dear Experts
I have an scenario Outbound I'm generating and EDI File and I use BIC Seeburger. The scenario works fine . However I have a new requeriment I need to pass an hexadecimal(1A) value in the parameter destDelimiter in the Terminator.
My actual value is
* ~\n\r
I need to replace ~ with new value hexadecimal (1A) Is it possible?
Thanks and Regards
Edited by: Luis Ortiz on Oct 6, 2009 3:07 PM

This doesn't seems possible in the module parameters as you can only have 6 characters for destDelimiter (excluding the escape sequence character). May be you can try some settings in BIC mapping like setSourceDelimiter.
Regards,
Prateek

Seeburger help required for 850, 810, Dispatch Advice (DESADV IDOC)

Hi All,
Pls let me know for below 4 points:
1. Please let me know blogs which clearly shows settings for Seeburger components for 850 or 810.
--- Seeburger Workbench
--- Seeburger Mapping Designer (BIC)
--- Seeburger Counter and Varaibles
--- Seeburger AS2 Spoke
--- Any other Seeburger Component setting required
I have understand blog for 850 -- /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
4. I have heard that Seeburger now provides standard mappings for PI/XI for 850, 810 , DESADV etc. so we do not require to do mappings in PI/XI now as it is already done. Any one knows about it.
Regards

> Pls let me know for below 4 points:
>
> 1. Please let me know blogs which clearly shows settings for Seeburger components for 850 or 810.
> --- Seeburger Workbench
> --- Seeburger Mapping Designer (BIC)
> --- Seeburger Counter and Varaibles
> --- Seeburger AS2 Spoke
> --- Any other Seeburger Component setting required
Hello Rickk,
There is no blog for the 810 scenario ...
you need to configure the partner related stuff in seeburger workbench if it is inbound only like 850,852,860..
not for outbound like 810,856...i.e no need to configure the partner data in seeburger workbench for this..
You need to look for developing mappings if EDI message is other than Version 4010 by default there are mappings available for
810,856,850,997..if your edi messages are other than this then you need to look for BIC tool for developing mappings.
There is no need to set anything for counter and varaibles
..no idea about AS2 spoke,,,
Apart from thjis no need to do anythings in seeburger ...
HTH
Rajesh

Seeburger help required for 810 and Dispatch Advice (IDOC type DESADV).

Hi All,
1. Please let me know blogs which clearly shows settings for Seeburger components for 850 (Purchase Order) to IDOC Scenario
--- Seeburger Workbench
--- Seeburger Mapping Designer (BIC)
--- Seeburger Counter and Varaibles
--- Seeburger AS2 Spoke
--- Any other Seeburger Component setting required
I have understand blog for 850 -- /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
Regards

Hi Rickkk,
1. Please let me know blogs which clearly shows settings for Seeburger components for 850 (Purchase Order) to IDOC Scenario
--- Seeburger Workbench
--- Seeburger Mapping Designer (BIC)
--- Seeburger Counter and Varaibles
--- Seeburger AS2 Spoke
--- Any other Seeburger Component setting required
For SEEBURGER workbench please go through this blog and navigate the enbebbed links furthur to know about Seeburger workbench too.
/people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
2
2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
For 810 i think the procedure would be the same but themseeburger mapping program that validates the ANSX 810 would be different.As far as 997is concerned 997 is a functional acknowledgement.Its a genric format that is used to send acknowledgement for any EDI transaction set that has been sent.
3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
The logic will be based on the trading partner guidelines which will contain the description of all the semantic and syntactiic description about the segments ,its feilds.we need to consider the guidelines and target side specifications too while mapping.
Thanks,
Ram.

Unable to find localejbs/CallBicXIRaBean

Hell All,
As a part of Seeburger installation we have deployed the bicXIRaSCA.sca to XI server. The SDM log confirms about the successful deployment of the same.
07/08/24 18:06:48 - ***********************************************************
07/08/24 18:06:48 - Start deploying library JAR D:\usr\sap\X7G\DVEBMGS01\SDM\root\origin\seeburger.com\SEEBURGER-BIC\SEEBURGER AG\0\20051019171958\bicXIRa-lib.sda...
07/08/24 18:07:37 - Library D:\usr\sap\X7G\DVEBMGS01\SDM\root\origin\seeburger.com\SEEBURGER-BIC\SEEBURGER AG\0\20051019171958\bicXIRa-lib.sda successfully deployed on the server.
Aug 24, 2007 6:07:37 PM Info: End of log messages of the target system.
Aug 24, 2007 6:07:37 PM Info: ***** End of SAP J2EE Engine Deployment (Library component of SAP J2EE Engine) *****
Aug 24, 2007 6:07:37 PM Info: Finished successfully: development component
I have also checked the
usr\sap\X7G\DVEBMGS01\j2ee\cluster\server0\apps\seeburger.com\com.seeburger.bicxiadapter.module\EJBContainer\applicationjars folder. There we have the CallBicXIRa.jar available.
Now when I am trying to use the bic (Converter) module with a file sender adapter. The problem is the adapter is giving the following error.
Attempt to process file failed with com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of localejbs\CallBicXIRaBean.
Any idea why this error is coming?
Thanks
Abinash

Hello All,
I have tried giving the module name as both localejbs/CallBicXIRaBean and CallBicXIRaBean (Without localejbs) still the adapter is showing the error throwModuleException().
I have also checked the j2EE Admin tool and I can see the CallBicXIRaBean in Services -->Deploy --> Application --> seeburger.com/com.seebuger.bicxiadapter.module
Should I reinstall the bicXIRaSCA.sca as I don't see a reason why should I reinstall it again?
Any pointer on this is highly appreciated.
Thanks
Abinash

Seeburger BIC Mapping deployment issue in PI 7.1

Hi experts
We have upgraded from XI 3.0 to PI 7.1 and seeburger is also upgraded to a compatible version.(2.x).
Mappings_user.sda was used in 3.0 environment.
But we are not able to deploy the same in 7.1. I think sda format is not supported in 7.1.
Is there any way to convert .sda to .sca and deploy?
Or how can we generate a compatible deployment file for 7.1?
I have tried using BIC mapping designer,but it shows the option for .sda and .jar only.
Thanks in advanceDhanish Joseph

Hi
I have installed BICMD 632 version and imported .BICMD project file.
Then assigned sda/sca number to it and created deploy file.(Mapping_user00.sda).
Then installed this in PI system using JSPM.
I have tested allmost all the mappings successfully except one in PI system.(EDI 990 message).
When i send data to PI data comes to channel and it shows conversion error. But detailed information not available.
In seeburger monitoring the message goes to recovery mode.
I have used the input 990 X12 and tested in Seeburger BIC MD. And there it is success!!!!!! So i am confused what is happening when it comes to PI system.
I faced some issues>>>
1. while importing project file into BIC MD it asked for apply some autocorrection for one map.(different than this). I have clicked on cancel
2. When i assigned SDA number to my project i have selected 2.1.0 SDA version( 1.8.0 option was also there).
Your prompt reply is greatly appreciated .
Thanks

Seeburger bic module mapping parameter

Hi all,
I'm implementing a Invoice02 to 810 scenario, my mapping name in repository is MM_xyz..
But I'm using the standard content of Seeburger...there are lot of mapping transformation..
So do I need to create 1:1 mapping in BIC mapper or can I use See_X2E_ANSIX12_810_V4010 as my mappingName in bic module config...
Thanks,
Srini

>
Srinivas Davuluri wrote:
> Hi all,
>
> I'm implementing a Invoice02 to 810 scenario, my mapping name in repository is MM_xyz..
> But I'm using the standard content of Seeburger...there are lot of mapping transformation..
> So do I need to create 1:1 mapping in BIC mapper or can I use See_X2E_ANSIX12_810_V4010 as my mappingName in bic module config...
>
> Thanks,
>
> Srini
Dont confuse yourself with the data mapping and the BIC mapping.
Note that the data mapping transforms your IDoc XML to 810 EDI XML. Here you have a transformation logic via the business rules. The BIC mapping is nothing but a structure conversion something you can say like FCC in file adapter which will convert the EDI XML to the EDI flat file
The BIC is at an adapter level conversion as it is part of a module. You actual IDOC to EDI XML transformation is done by your message mapping.

Error in Seeburger BIC Mapping

Hi all,
I am working on Seeburger BIC Mapping Designer.
As i am starting off with it, i have planned to do a very simple scenario File to file.
Source would be an XML and target also would be an xml.
Compilation is fine, but while converting I am gettuing an error
"[Error:ID=2023;LEVEL=1] InhouseDocReader readNextSegment(): offset[4(read Segment : KA\)]: caught ReadingException: Length limit exceeded - no SEG. delim. found!!!
DESCRIPTION: InhouseDocReader causes an ReadingException while trying to read the next segment of current file, abort
<<ErrorStreamEnd>>
Conversion error "
Please let me know what should be done.
Even I have enabled SetIngnoreCRLF option in the source options.
Cheers,
Karthick

Hi Karthick,
Where do you get this error?
In BICMD ?
Have you created the E2X and/or X2E mapping programs in BICMD tool?
Test it locally in the tool intself before deploying the mappings to XI server.
Follow these steps to create a 1;1 mapping for XML to EDI and EDI to XML conversion program:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948;jsessionid=(J2EE3414900)ID2060961950DB01298938248398894809End
Regards,
Ravi

Seeburger BIC Mapping Designer: Special Character (German Umlaut) Problem

Hi,
i have created a Mapping with Seeburger Mapping Designer (Invoicd96a to XML). I started the test environment, compiled the mapping and converted the Message to XML. I got a syntax error in the destination file so i added the setSourceEncoding("UTF-8") option and i got a working xml file.
My problem is that all special characters, will be displayed as ? So the word "Beträge" will be converted to "Betr?ge".
What i have to di, to fix this problem ?
Thanks in advance
Matthias

hi,
i have to create an Edifact to XML Mapping with the BIC Mapping Designer. After creation i can deploy this mapping to SAP XI and calling it by using it as module in the specified adapter.
My idea is that the mapping should working correct in test enviroment before i deploy to SAP PI.
Perhaps anyone has an idea.
regards
Matthias
P.S.: A few month ago i had a similar problem with the conversion agent and it was just a "secret" checkbox

Problem in SEEBURGE BIC mapping adapter

Hi experts
I am using SEEBURGER MAPPING adapter for file to idoc scenario .I have to convert an input flat file into xml using BIC mapping adapter.The problem is that when i am giving input file to convert into xml ,the conversion is failing with a error that a special character(?) occurs in the begining of file.when we r opening the file then we r not able to see any special character.The file is in UTF16 Little endian encoding. we r unable to find that how the spechial character is coming in the input files and how to debugg it.Plz guide me how to proceed.Is there any function in SEEBURGER to remove special character from the source file?
Regards
Neha

Hi Neha,
Seeburger is providing Modules (Configurable in CC module chain) described in SAPXI_SeeXIModules_en.pdf with additional functionality like Replace String,Start Local Up, Charset Conversion, zip and dynamic Configuration.
So if you have those modules installed you can use Replace String functionality to replace this string.
Regards
Naycho

Seeburger BIC tool

Going to support EDI interface which uses Seeburger AS2 adapter either at sender or receiver side.I have few doubts on BIC module:
1.Do i need to install BIC tool on my laptop or it is a web based tool which i can access from seeburger workbench?
2.For all the edi conversion using Seeburger do we need BIC module to convert messages from EDI to XML or from XML to EDI?
3.why we need to do message mapping again if we had already done BIC mapping?
thanks in advance.

Hi,
1.Do i need to install BIC tool on my laptop or it is a web based tool which i can access from seeburger workbench?
Yes you need to install BIC mapping tool in your laptop to do the mappings.
2.For all the edi conversion using Seeburger do we need BIC module to convert messages from EDI to XML or from XML to EDI?
Yes for all EDI conversion using Seeburger you need BIC tool. But if you have some standard mapping already given by Seeburger than you dont need BIC tool, you can directly use those mappings. Remember standard mapping will start with name SEE*
3.why we need to do message mapping again if we had already done BIC mapping?
BIC mapping tool is used to convert EDI to XML and vice versa. Think about a scenario when you need to convert an IDOC to EDIFACT format.
Than first you have to do 1:1 mapping in PI where you will convert IDOC to EDIXML and than use BIC mapping tool to convert EDIXML to EDIFACT file.
I hope above answers will help you.
Regards,
Shradha

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

Seeburger EDI adapter Vs Seeburger BIC adapter

hi,
what is the difference between <b>Seeburger EDI adapter Vs Seeburger BIC adapter</b>.any docs please.
thank you,
babu

Hi,
<i>Seeburger EDI adapter Vs Seeburger BIC adapter.</i>
If your edi file converts with BIC mappers then you would have to use BIC adapter or BIC modules, i hope BIC modules, next EDI Adapters see the below links to get more details..
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards
Chilla

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

BIC Seeburger

Similar Messages

Maybe you are looking for