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

Similar Messages

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

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

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

Seeburger BIC problem

Hello experts,
I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.
The error is:
- SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.
Adapter Framework caught exception: BICMODULE:Adapter call failed. Reason:
- Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error in BICMODULE-module:Adapter call failed. Reason: .
As you can see, the reason is not mentioned.
When I look into the message monitoring, I see the message does not have a payload. On the SOAP ducument is provided with this content:
authorization:Basic UElJU1VTRVI6SUQzaW5zdGFsbA== accept-encoding:gzip
sap-xi-messageid:4BA11A89186666D8E1000000C0A8A310 content-
length:2916349 host:id3-ma-dwh1.mrco.be:51300 user-agent:SAP NetWeaver Application Server (1.0;711) content-
type:multipart/related;boundary=SAP_001E0BFD21001DEF8CBF15AFFC885B07_END;type="text/xml";start="" soapaction:"http://sap.com/xi/XI/Message/30"ApplicationMessageasynchronous4ba11a89-1866-66d8-e100-0000c0a8a3102010-
03-17T19:07:56ZID2CLNT001SteriaVANBC_UTILMDToSteriaVANMDSnapShot_In_AExactlyOnceInformationOffID2CLNT001XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0is.13.id3-ma-dwh1XI4ba11a89-1866-66d8-e100-0000c0a8a3103.0af.id3.id3-ma-dwh1XIRA4ba11a89-1866-66d8-e100-0000c0a8a310MainDocumentApplication
The Seeburger modules used in my receiver adapter:
1. localejbs/CallBicXIRaBean -- BIC
2. localejbs/Seeburger/Zip -- ZIP
The Module Configuration:
BIC - destEncoding - ISO8859_1
BIC - destSourceMsg - MainDocument
BIC - destTargetMsg - MainDocument
BIC - mappingName - X2E_....
BIC - srcEncoding - ISO8859_1
ZIP - mode - zip
ZIP - sourceDest - MainDocument
ZIP - targetDest - MainDocument
ZIP - zipFormat - gzip
Messages fail at random. ABAP mapping and data are ok.
I think there is a problem with capacity or memory or something.
Anyone any idea?
Thanks a lot!
Dimitri

>
Dimitri Sannen wrote:
> Hello experts,
>
> I'm facing a nasty Seeburger BIC problem in my receiver adapter when converting from XML to EDI.
>
> The error is:
>
> - SEEBURGER BICXIADAPTER.MODULE Message could not be forwarded from the Module (CallBicXIRa) to the JCA adapter.
>
> The Seeburger modules used in my receiver adapter:
>
> 1. localejbs/CallBicXIRaBean -- BIC
> 2. localejbs/Seeburger/Zip -- ZIP
>
Dimitri,
The reason that you are getting this error is because you are missing the exit module bean. add this module after the zip module
Processing sequence
3. localejbs/ModuleProcessorExitBean Local Enterprise Bean Exit
Module configuration
exit JNDIName deployedAdapters/SeeXIAS2/Shareable/SeeXIAS2
There is an exit entry missing which actually is used to pass the bic data to PI box.
Regards,
Pavan

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 Interface configuration problem

I am facing some problems in configuring the interfaces in seeburger.
As the standards which i want to translate are not configured as default for AS2 adapter so i want to configure it through BIC but as i am new to this don't know the basics as how to load the XSD, provided by client, and how to develope it in XML using BIC.
Please throw some light on it as i am a new bee in seeburger, i also tried doing it but was not successful.

>
Rohit Kaushal wrote:
> I am facing some problems in configuring the interfaces in seeburger.
> As the standards which i want to translate are not configured as default for AS2 adapter so i want to configure it through BIC but as i am new to this don't know the basics as how to load the XSD, provided by client, and how to develope it in XML using BIC.
> Please throw some light on it as i am a new bee in seeburger, i also tried doing it but was not successful.
Can you provide more details like what you are expecting..
If my understanding is correct you want to implement a mappings in seeburger bic mapping tool for your sceanrio which can take care of conversions right?
if yes provide more details about your scenario
Rajesh

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

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

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 import the IDOC into Seeburger BIC mapping designer

Hi All,
Can u please tell me how to import the IDOC into Seeburger BIC mapping desginer.
I have scenario My scenario is SAP GTS 7.0.....>Seeburger BIS.....>Atlas customs system for Germany
Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send
to Atlas systeam.
Regards,
Ramesh.

Hi Ramesh
BIC is a tool from Seeburger to transmit the XML data to EDI and EDI to XML.
Seeburger mapping programs for transferring the XML data to EDI data and EDI data to XML data, but not for the structure changing, in the IR your mapping program is same.
Receiver side you need AS2 Adapter for converting data to EDI target structure. we have many EDI versions are available, for converting the EDI to XML or vice versa AS2 gives some default mapping programs, xml to EDI or EDI to XML convertion done through this mapping programs.
Seeburger AS adapter provider provides some mapping programs(for example EDI4010 version or other), if you are using the same EDI version(4010) then you can use that mapping programs, if the version is different then we can manually generate the Seeburger X2E and E2X mappings for the corresponding version and signal(850 or 810 or ..), for this seeburger provides the mapping designer tool (BIC), there we can develope the X2E and E2X mapping programs and configure this in the Seeburger work bench.
Regards
Ramesh

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

Seeburger BIC mapping error(on changing mandatory fields)

Hi Experts,
I am working on IDOC to EDIFACT file scenario with seeburger.
Earlier my end to end scenario was working fine. I got a requirement to change all the mandatory fields of segment NAD into non mandatory field. To acheive this i changed my Seeburger BIC mapping and target XSD in PI. After this process i create .sca file and ask basis to upload it.
But after deployment i am getting error in communication channel where i am using BIC mapping. The error is message is quite big, still i am attaching a part of it. Please help
Message processing failed. Cause: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: BICMapping: runMapping() FATAL ERROR: java.lang.OutOfMemoryError: Java heap space (failed to allocate 16777240 bytes) Stacktrace: java.lang.OutOfMemoryError: Java heap space (failed to allocate 16777240 bytes) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:191) at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:111) at java.io.BufferedWriter.write(BufferedWriter.java:212) at java.io.Writer.write(Writer.java:126) at com.seeburger.jucon.dochandler.util.GrammarFileWriter.write(GrammarFileWriter.java:262) at com.seeburger.jucon.dochandler.EdiSegmentData.write(EdiSegmentData.java:234) at com.seeburger.jucon.dochandler.Segment.write(Segment.java:645) at com.seeburger.jucon.dochandler.EdiSegmentData.write(EdiSegmentData.java:390) at com.seeburger.jucon.dochandler.Segment.write(Segment.java:645) at com.seeburger.jucon.dochandler.EdiDocWriter.write(EdiDocWriter.java:367) at com.seeburger.jucon.dochandler.InhouseDocWriter.flush(InhouseDocWriter.java:884) at com.seeburger.jucon.mapping.Mapping.run(Mapping.java:2429) at com.seeburger.jucon.seebicapi.BICMapping.runMapping(BICMapping.java:1724) at com.seeburger.jucon.seebicapi.BICMapping.run(BICMapping.java:2518) at com.seeburger.jucon.seebicapi.BICMapping.startSyncMapping(BICMapping.java:1415) at com.seeburger.bicxiadapter.CCIInteraction.convert(CCIInteraction.java:1201) at com.seeburger.bicxiadapter.CCIInteraction.convertCalledFromModule(CCIInteraction.java:911) at com.seeburger.bicxiadapter.CCIInteraction.execute(CCIInteraction.java:313) at com.seeburger.xi.api.cci.impl.nw71.SeeXIInteractionProxy71.execute(SeeXIInteractionProxy71.java:86) at com.seeburger.bicxiadapter.module.CallBicXIRaBean.process(CallBicXIRaBean.java:384) at com.seeburger.xi.api.module.impl.nw71.SeeModuleAdapter71.process(SeeModuleAdapter71.java:78) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal
java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:266) DESCRIPTION: BICMapping: FATAL ERROR: Internal Fault. Class could not be load or instatiated. Check Installation, access rights. Last error: java.lang.OutOfMemoryError: Java heap space (failed to allocate 16777240 bytes)
Regards,
Shradha

Hi,
Even I faced a Similar problem...
1) make sure that the size of the data that is coming to BIC map is not larger than the size defined in the Source field (Check In BIC and SAP XI/PI map.
2) Make sure id any other seeburger mapping are working fine , This is because you have to deploy the file in form of Active mapping.sca in SAP XI/PI after the changes are made on BIC side.
3) Check the Adapter Engine Cache ...
Hope this helps..
Regards,
Sainath Chutke

Seeburger BIC mapping designer : querry

Hi,
 We have installed the SeeBurger BIC adapter. I have a querry regarding the mapping that we specify as a parameter to the BIC module in the modules tab of the communication channel.
 Are there standard mappings provided with the installation for EDI -> XML and vice versa , and we simply need to provide the name of the mapping that needs to be used or do we need to develop the mappings from scratch using the BIC mapping designer.
 If the first case is true then how to get the names of all the mappings that are provided so that we can make out which one do we need to use. If it is not so please help me with the BIC mapping designer manual path on the installation as we are not able to figure out the path to the manual.
Thanks in advance,
Pravesh Puria.

Hi Babu,
1."you can use these mappings in "Modules" of your seeburger communication channel."
>> can we use these developed mappings with BIC MD in any communication channel of Seeburger like OFTP,FTP ,AS2 ,BIC or we need to use those mapping with only BIC communication channel?
>>> Yes Babu,You can use this in all communication channel modules .
one thing, "BIC" is not a seeburger adapter type.
You need to deploy BIC Mappings in your XI server.
You have to refer Seeburger manuals for this.
2.lets say if we have developed mappping with BIC MD ,then do we need to develop mapping with XI mapper too or its not needed?but if we do mapping with Xi then data format will be of xml but it needs to be converted to/from EDI ,so how it can be possible just with XI maping and no BIC MD mapping?
>>> No, You Cannot do it in only with XI Mapper.
First you need to use BIC Mapping in modules which will convert your EDIFACT format to EDI-XML.
After this you need to Apply XI Mapping Which will Convert EDI-XML to your IDOC-XML.i.e. your mapping program.
Thanks & Regards,
Akshay Jamgaonkar.
Reward Points For Good Answer .

Seeburger - BIC configured as Module

Similar Messages

Maybe you are looking for