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

Similar Messages

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 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.

Seeburger BIC Help!!

We have followed all the steps for deploying Seeburger BIC module. I am currently trying to use File adapter and configure BIC module in the file adapter. I am successfully able to post IDOCS from R/3 but cannot see any errors or messages at the. If I post IDOCS without configuring BIC everything works fine (in terms of message transfer not EDI mapping).
Does anyone have an idea on why this is happening? how to debug BIC? Where I can find logs ?
Any help is greatly appreciated.

Hi,
You can folow the following steps inorder to send the IDOC into EDI
1) Find out the Correct Mapping Name in BIC mapping Designer. In order to get the Standard Mappings into your BIC tool you need to import the prj_GeneratorMappings.zip.bicmd which is found under the path
\user\bicmd\Exchange after installing the BIC map designer. This will import the Standard
Mappings that are available with the Map designer by creating a new GeneratorMappings
project tab.
2) And also we need to import another file prj_SeeburgerFormatMapping_1.7.zip.bicmd which
comes with the Seeburger EDI adapter package. Once we import this we will have all the
standard Structure for the EDI messages and standard mappings to convert the EDI Message
structure to XML and vice versa.
3)Now we need to copy all the standard mappings which ever is required from the
SeeburgerFormatMapping_1.7 project to ActiveMappings project Tab, to generate the SDA
file which needs to be deployed in XI server through SDM.
Note: This SDA file generated will always have the lastest mapping that needs to be deployed in
the server or in other words, once we generate an SDA file with selected mappings and if we
need to include few more mappings in the later stage then we have to append all those mappings
in the Active mappings directory and regenerate the SDA file.
Regards
Seshagiri

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 configured as Module

Has any one sucessfully used the BIC as module and convereted the EDI document to XML-EDI format and viceversa. I have configured the BIC as a module and i am running in to all sort of Isssues. Tried to use the Classifier Module to Classify the Message and all it could return was
<classifier><type>AnsiX12</type>
<classifierMappingID>null</classifierMappingID>
<encoding>US-ASCII</encoding>
<additionalIdentifier></additionalIdentifier>
</classifier>
Because the Mapping Id was Null and with the Information that classifier passed to the Bic Module it resolved the mapping name to See_AnsiX12 and i got the Functional Acknowledment in XML-EDI format.
I got fed up and took out the classifier Module and Provided the mappingName as Parmeter for the BIC module and specified the MAP to be used as bic mappingName See_E2X_ANSIX12_850V4010. Now when i try to Process the the 850 EDI File i get an error: ISA Segment Filed I15 is empty even though it has the value "/"
trying to see if any one went through the headchae of Seeburger EDI Adapter and got it working.
Adapter Error:
Sender Adapter v1830 for Party 'Business_Partner_1', Service 'EDI':
Configured at 19:15:57 2005-08-01
Last message processing started 19:19:07 2005-08-01, Error: Module Exception 'com.sap.aii.af.mp.module.ModuleException: Adapter call failed. Reason: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=2088;LEVEL=3] FieldData checkInputSyntax(): Mandatory, incoming field is empty. Segment:'ISA', Field:'I15'
DESCRIPTION: FieldData Error in Segment [not specified] incoming mandatory Field [not specified] is empty. Check class files.
' found, cause: javax.resource.ResourceException: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=2088;LEVEL=3] FieldData checkInputSyntax(): Mandatory, incoming field is empty. Segment:'ISA', Field:'I15'
DESCRIPTION: FieldData Error in Segment [not specified] incoming mandatory Field [not specified] is empty. Check class files.
last retry interval started 19:19:21 2005-08-01
length 10,000 secs
Actual Input Document:
ISA00 00 ZZCA7045542000 14007944580RTE 0503240823U004000063519450P/
GSPOCA7045542000007944580RTE2005032408236351945X4010
ST8506351945
BEG00SA450013584120050324*AC
CURBYUSD*1.000
N1SO922431
REFZZ3000*PAORG-
REFZZ903*PAGRU-
PERCNMc JunkinTE5409215020
PERCNNAFTA Purchasing OrgFX5409215030
N1BTCONTACT THE PST AT 704-554-377892903
N2*NO BILL-TO ADDRESS AVAILABLE
REFZZ3000*PAORG-
REFZZ903*PAGRU-
PERCNMc JunkinTE5409215020
PERCNNAFTA Purchasing OrgFX5409215030
N1VN920001008751
REFZZE*SPRAS-
N1STNarrows, VA924022
N2*Celanese Acetate, LLC
N3*3520 Virginia Ave.
N4NarrowsVA24124US
REFZZE*SPRAS-
REFZZVA*REGIO-
PO10001025EA3.62PEPI0VN55159103IN*30300754
PIDF***Pins,RETAINER #66267536008 FOR 3/4 DRIVE
REFWO000050248591
MSG*PINS, RETAINER #66267536008 FOR 3/4 DRIVE SOCKETS-LARGE, ,
SCH25EA**06720050408
N1STNarrows, VA924022
N2*Celanese Acetate, LLC
N3*CC SHOP
N3*3520 Virginia Ave.
N4NarrowsVA24124US
REFZZE*SPRAS-
PERCNtmckinne4381
PO10002050EA3.62PEPI0VN55142194IN*30300755
PIDF***Pins,RETAINER F/3/4 IN DRIVE SOCKET SMAL
REFWO000050248591
MSG*PINS, RETAINER F/3/4 IN DRIVE SOCKET SMALL #66267936007, ,
SCH50EA**06720050408
N1STNarrows, VA924022
N2*Celanese Acetate, LLC
N3*CC SHOP
N3*3520 Virginia Ave.
N4NarrowsVA24124US
REFZZE*SPRAS-
PERCNtmckinne4381
CTT*2
SE486351945
GE16351945
IEA1006351945
Message was edited by: Sudheer Nagalla
Message was edited by: Sudheer Nagalla

Hello,
I have forwarded your problem, do you have an OSS note open for this problem, already?
At a first glance I think it is missing a deimiter at the end of the ISA segment, but thats just a rough guess. I can tell you tomorow.
Greetings
Bernd

BIC Module Error in Sender Communication channel for EDI to File scenario.

Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
Abhishek

Hi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish

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 Seeburger EDI adapter Vs Seeburger BIC adapter.any docs please.
thank you,
babu

Hi,
Seeburger EDI adapter Vs Seeburger BIC adapter.
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

Use of "Archive Source Files with Errors" for BIC module error

Hi All,
I have Edi file to Idoc scenario , where i am using SEEBURGER BICXIADAPTER.MODULE.
My question is if the input file caught in error with BIC Module e.g
"MP: exception caught with cause Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: SegmentDescription: checkAndResetChildrenCounter() not enough repetitions of the segment UNH found: 0 instead of 1 offset :80 DESCRIPTION: SegmentDescription Warning: Not enough repetitions of the segment UNH ([not specified]/[not specified])."
can we move these errornous files to another directory using Processing parameter "Archive Source Files with Errors" available with Sender File Adapter?
In File Adpater my Module tab looks like :
1 localejbs/CallBicXIRaBean Local Enterprise Bean bic
2 localejbs/CallSapAdapter Local Enterprise Bean 0
In my scenario , its not working.. do we have any other option to achive this?

Hi Jyoti,
I had a raised a similar case with SAP and came to know that archiving only works if the error raised by the module is so called "Permanent". However, bic doesn't raise permanent error due to which archiving of error files won't be possible. Seeburger haven't came up with a solution yet.
Regards,
Prateek

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

Conversion in Seeburger BIC and XI

Hi,
We receive e-mails with an EDIFACT messages (ORDERS or DELFOR) as an attachment. The e-mails are received in the same INBOX on an e-mail server.
I configured a sender mail adapter in XI and added the PAYLOADSWAPBEAN to put the e-mail attachment into a SOAP attachment (see also /people/michal.krawczyk2/blog/2005/12/18/xi-sender-mail-adapter--payloadswapbean--step-by-step)
Now I need to convert the EDIFACT message to XML EDIFACT using a standard 1:1 mapping of Seeburger. I have to determine dynamically what message has to be used (for ORDERS or DELFOR)
How can I establish this?
I tried to use the classifier and BIC modules of Seeburger but I did not succeed.
Ron

Hi all,
when receiving files and you have no idea what file it is, you usually use 3 Modules of the Adapter-Set:
1. SeeClassifier
- determines the file type (e.g. EDIFACT,ANSI...)
2. BIC
- can be set to "Auto"-Mode, which means depending on the information from the Classifier, it executes a "MainMapping" which takes a look at the Header-Fields of this type (for example if it is an Edifact-File it looks at the UNH-Information...and then dynamically creates the name of the real 1:1-Mapping that needs to be executed)
So this means, if you receive a Edifact-File with several UNH within a UNB, it can even be a combination of DELFOR; ORDERS, INNOIV or whatever... each UNH-Loop will be translated seperately with the correct Mapping.
3. Split-Module
This allows you to have a seperate attachment for each UNH-Part (for Edifact). A new SenderChannel can also be created depending on the UNB Sender-Information.
Hope this clarifies the Modules a little bit. If you receive for example lots of different files from different partners via a VAN like IBM or GXS, you probably have no other possibility than use these 3 Modules together to separate all these messages by type and partner and be able to process them correct in the XI.
Regards
Stefan

Building own schemas in Seeburger bic mapper

I'm consulting for Utilities industry and looks like Seeburger does not have custom schemas for this industry type. Using standalone software bic converter and mapping designer, is it possible to
1. build custom schemas from standard EDI X12.
2. and once I build custom schema, would this be saved as xsd?
3. can this xsd be used to convert / map to an IDoc (xsd) using bic mapping designer.
4. does this come with Seeburger adapter cd or a separate cd (free / with cost)?
5. Finally, its latest version number?
I know I have several questions. Please let me know...I will reward them handsomely
Please send me answers and not links to documents. I get totally confused and lost with these Seeburger documents!
Thanks,
Pam

Hi,
1. build custom schemas from standard EDI X12.
Yes you can build custome schamas as per EDI Industry standards. Also we can have the pre standard schemas after installing the seeburger on server.
Also you can get exact manuals from the server/vendor.
2. and once I build custom schema, would this be saved as xsd?
Yes you can use it.
3. can this xsd be used to convert / map to an IDoc (xsd) using bic mapping designer.
See in general ,BIC / some edi converter can be used to generate the xsd.And also you can map the BIC mapper , if you use then you have to configure the eeburger adapter with bic modules.
4. does this come with Seeburger adapter cd or a separate cd (free / with cost)?
I hope Yes. you can have , but some cost.
5. Finally, its latest version number?
Vendor specific.
I hope you can have all seeburger links in your previous forum question.
I have given lot of links.
Regards
Chilla..
Points rewarded if it is helpful..

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/

Seeburger BIC module

Similar Messages

Maybe you are looking for