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

Similar Messages

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

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

Design approach help : BIC Mapping Tool Conversion

Hi All,
Design approach:
we know that BIC mapping tool can be used for EDI to XML conversion. also i know that its a Any to any converter.
But we prefer EDI to EDI XML conversion only via this tool and do the mapping in SAP PI as it would be easy to do mapping change if any in PI than redeploy the mapping in module location every time.
My question is:
we know that sender file adapter supports FCC for max of 3 hierarchy levels.
Can we make it a practice of accepting requirements in SAP PI which has complex Flat file structure (more than 3 levels). and use BIC mapping tool to convert the Complex flat file Structure (with more than 3 levels) into PI required format and proceed with the mapping and Configuration. (Note: hear the assumption is that the organisation has BIC Mapping tool procured for some EDI message scenario's ).
or is it best practice to ask the Source system to supply flat files strictly in Header,with 1 line item format?
Suggestions would be deeply appreciated.
Warm Regards,
Senthilprakash

>
> if you are thinking of using only BIC mapping tool for converting flat file to xml and want to proceed with normal configuration without using BIC modules then it is not feasible.
>
Dear Suresh,
I am very well aware of that. we have Seeburger SFTP adapter installed in our PI system. and for EDI conversion we use BIC for converting to XML and deploy the module in the adapter level.
Now my question is that: weather is it the rite way to start accepting requirement from source which has complex flat file structure (non edi messages) and using BIC module in adapter to convert it into XML and proceed with configuration or better to ask the source system to send the flat file in a format which is accepted by our file adater FCC.
what are the drawbacks/bottlenecks we see in using BIC module for converting non EDI complex flat files into XML format? in PI
Regards,
Senthilprakash.

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

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

Hi Everyone,
I have a Problem with Seeburger BIC Mapping Designer. The problem is All the Projects/Mappings that i have done are suddenly disappeared in the Project Explorer, but my projects are available in the C:\Program Files\SEEBURGER\MappingDesigner\user\bicmd folder. I think the file "Project.xml" is refreshed.
what could be the problem and please suggest me with the suitable solution.
I am currently using 6.3.2 Version of BICMD.
Regards,
Varun Reddy.K
Edited by: Varun Reddy K on May 7, 2008 4:58 PM

Hi Seshagiri,
Thanks for your reply, even i opened and closed it multiple times, but no use.
Regards,
Varun.

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

Need Seeburger BIC Mapping names for standard Msg types - EANCOM2002

Hi All,
I need Seeburger Bic Mapping names for standard Msg types.
Orders
ORDRSP
DESADV
Note that they are in EANCOM2002 format.
Kindly provide them asap.
Can anyone pls send the document to [email protected] if you have the Seeburger mapping names for EANCOM2002 and ANSIX12.
Thank You.
Regards
Seema.

Hi Marcos,
>> IF they have been deployed in your system the names will be:
>> See_E2X_ORDERS_UN_D96A
>> See_X2E_ORDERS_UN_D96A
>> See_E2X_DESADV_UN_D96A
>> See_X2E_DESADV_UN_D96A
R u sure of we can use these mappings for EANCOM2002 format.??
R u sure EANCOM2002 is equavalent to UN D96A???
-Seema.

Batching different messages using Seeburger BIC

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

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

Mapping Split using the Graphical Mapping Tool

Hello,
I am a little confused right now... so I turn to you for help!
I found this excellent blog:
/people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool
It details how to do a message split using the Graphical Mapping Tool. WHich is exactly what I want!
But then I found this on help.sap.com:
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
Which states that:
Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
-          RFC Adapter
-          SAP Business Connector Adapter
-          File/FTP Adapter
-          JDBC Adapter
-          JMS Adapter
-          SOAP adapter
-          Marketplace adapter
-          Mail Adapter
-          RNIF adapter
-          CIDX Adapter
I have a simple mappling split where I want to take a file containing multiple materials and send them one by one to a PROXY into SRM. To send to proxy I want to use the HTTP adapter which is not listed above. BUT if I read it correctly it will work, as long as I dont try to do the interface determination based on the mapping.
Is this correct, that it will work I mean? I think so but not sure about the wording in the sentence above, and wanted to check before I go destroy my mapping.
Thanks!
Nam

Hi,
If your scenario is simple and straight fwd like from one source to one target then you can split message without BPM. As Priyanka said in the message mapping go to Message Tab and set the target message occurance to unbounded. Then in the Interface Mapping in the target interface section you will find the occurance in the last column, change occurance to unbounded.
While doing configuration you have to go for Enhanced Interface Determination thats it.
Provided you are above sp14, incase of any lowere SP'a you will not even able to activate your mapping program as it will expect ABSTRACT interface to do multimapping.
Thanks,
Prakash
Thanks,
Prakash

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

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

IDoc to File[EDI] using seeburger BIC Mapping Tool

Similar Messages

Maybe you are looking for