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

Similar Messages

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

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

Can SeeBurger BIC Mapping tool automatically remove Delimiters?

Hi all,
When we map IDOC's to EDI X12 messages using the SeeBurger BIC Mapping tool, we sometimes have delimiters occur in fields such as name or address. We are using the setDestinationDelimiter and have changed our delimiters so this occurance is rare. However the problem may still occur. This causes an invalid message to be passed to our partner.
One option is to use XI mapping and the replace function on each field however this is cumbersome and not the ideal solution.
Is there a way to automatically remove Delimiter characters from fields as part of the BIC Mapping.
Cheers,
John

Hi Satish,
Thanks for re-iterating the problem. You are absolutely right that this does cause an invalid message.
Also thanks for your suggestion regarding asking business not to enter the data, this has been done and as stated the occurences of these delimiters in the fields will be low, usually due to user error.
We still however want to cater for these occurrences and prevent an invalid message being sent to the partner.
I'm not sure if you've ever used the BIC Mapping tool and what I'm really looking for is someone with experience in this area to give a solution that works. Anyone out there who can help?
Cheers,
John

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

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

Outbound IDOC( Error passing data to port)

Hi,
We have an interface running daily configured such that the idocs are converted to files and placed on a directory path.
All the idocs are processed successfully but for one hour the idocs failed and the error message says:
Status: Error passing data to port
Error at OPEN (Directory path) with operating system error msg.:No such file or directory.
The missed data from the error idocs have been sent via PFAL.
But again after this one hour the idocs were successfully posted for the same directory path.
Please let me know what the issue can be here or how can we avoid this.
Thanks.

Hi
*Some times it may happen that IDOC doesnt reach to the port , in case if you are using Transactional RFC port so*
*you can use the report RSEOUT00 for sending the IDOC to port .*
*Hope it may help you .*

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

BIC mapping error with Text as trasnfer mode & File type

Hi guys,
I am using ftp adapter in my sender channel and also using BIC mapping in the sender side.
When i specify "Binary" as my transfer mode as well as File type, It is working fine.
When i specify "Text" as my transfer mode as well as File type, i am getting the below BIC mapping error. According to client requirement i am supposed to use Binary. Can anyone help me on this.
SEEBURGER BICXIADAPTER --- CONVERSION ERROR ---Error: [Error:ID=2023;LEVEL=1] InhouseDocReader readNextSegment(): offset[12(read Segment : BILLINGHEADER)]: caught ReadingException: only whitespaces as fill characters allowed!, Trace: [com.seeburger.jucon.dochandler.util.WrongFormatException: only whitespaces as fill characters allowed! at com.seeburger.jucon.dochandler.inhousereader.InhouseSegmentReader.readNextSegment(InhouseSegmentReader.java:384) at com.seeburger.jucon.dochandler.inhousereader.InhouseSegmentReader.readNextSegment(InhouseSegmentReader.java:193) at com.seeburger.jucon.dochandler.InhouseDocReader.readNextSegment(InhouseDocReader.java:2399) at com.seeburger.jucon.dochandler.InhouseDocReader.moveNext(InhouseDocReader.java:1818) at com.seeburger.jucon.mapping.E2X_DT_BILLINGDATA_2.main(E2X_DT_BILLINGDATA_2.java:991) at com.seeburger.jucon.mapping.Mapping.run(Mapping.java:2313) at com.seeburger.jucon.seebicapi.BICMapping.runMapping(BICMapping.java:1636) at com.seeburger.jucon.seebicapi.BICMapping.run(BICMapping.java:2386) at com.seeburger.jucon.seebicapi.BICMapping.startSyncMapping(BICMapping.java:1343) at com.seeburger.bicxiadapter.CCIInteraction.convert(CCIInteraction.java:1167) at com.seeburger.bicxiadapter.CCIInteraction.convertCalledFromModule(CCIInteraction.java:873) at com.seeburger.bicxiadapter.CCIInteraction.execute(CCIInteraction.java:294) at com.seeburger.bicxiadapter.module.CallBicXIRaBean.process(CallBicXIRaBean.java:363) at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:102) at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292) at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103) at com.sap.aii.adapter.file.File2XI.send(File2XI.java:3672) at com.sap.aii.adapter.file.File2XI.processFtpList(File2XI.java:2408) at com.sap.aii.adapter.file.File2XI.invoke(File2XI.java:630) at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:513) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) ] DESCRIPTION: InhouseDocReader causes an ReadingException while trying to read the next segment of current file, abort

Hi Pratichi,
in my point of view having text as the file type,the file will be having characters that are used for Segment separators or Element separators ( like space ) in the standard EDI format message. Hence it is throwing exception in X2E mapping. It is just my point of view but not sure.
Thanks,
Shabbir.

Seeburger AS2 Adapter Error :AUTHENTICATION_ERROR

i am doing the scenario for Purchase Order -> XI ->File
custumer is posting the purchase order
and XI Receives the PO using AS2 Adapter (Seeburger) and sends the output as File
i have done all the AS2 Adapter configurations as mentioned below but still i am getting the error in Seeburger Monitoring, the Error is Authentication_Error
1. Communication chennel
Adapter Type : AS2
Direction : Sender
Transport protocol : HTTP
Message Protocol : AS2
AS2 : Authentication Required is Enabled
Message Subject : Filled which is in Seeburger Monitor
2. Sender Agreement
Sender Communicational chennel which is created above
Security Setting
AS2 Sender Config :
Authentication Certificate : Customer public key
AS2 Receiver Config :
Decryption Key : Private key
3. in Party Identifiers
Party Name
AS2 ID
is there any settings missing to rectify the error "AUTHENTICATION_ERROR"

Hi
Check with PIAPPLUSER authentication
With this Check the following content on AS2 may be you get more clue.
http://www.customware.net/repository/display/WMFAQ/AS2-authenticationfailureinreceivingEDIINT+MDN
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/bpxproj/edi%2bwith%2bpi
Handling EDI interfaces using Seeburger BIC modules
Thanks
Gaurav

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 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,
<i>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?</i>
>>> 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.
<i>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?</i>
>>> 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 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

Seeburger BIC let errors pass

Similar Messages

Maybe you are looking for