Error in BIC mapping

Hello Pals,
                             Am using BIC mapping for converting a flat file to xml, am able to convert all formats of flat file but BIC mapper is throwing error if my input file has characters like ä , Ü and § . Upon  removing the special characters from my input file, BIC mapper is giving the desired xml output file, If special characters are kept in input file, it throws error.
I tried to change the BIC data type for the field from A to AN, but nothing seems to be working...
Kindly help
Regards
Vijay

Hi,
      Your characters looks like umlaut characters ..if yes then there is an option for handling them by  specifiying the function mode  setSourceUmlautMode  to ON at child level mapping or at source mapping similarly at target too..
if not then you need to look for encoding which can be set with the option setXMLEncoding/SrcEncoding...options..
HTH
Rajesh

Similar Messages

  • 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

  • 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 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 deployment issue in PI 7.1

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

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

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

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

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

  • Problem in SEEBURGE BIC mapping adapter

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

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

  • Seeburger Splitter:Fatal error in user mapping . java.lang.StackOverflowErr

    Hello,
    I have created a mapping E2X_SLSRPT_UN_D96A as we didnt have the standard mapping(See_)  from Seeburger
    In my scenario when I give hardcoded mapping name ,it works fine,so I assume mapping is correctly created and deployed.
    But I need to use it with splitter,and in doing so,I am getting this error:
    Message initiation failed: Adapter call failed. Reason: --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=not set;LEVEL=1] Fatal error in user mapping ... java.lang.StackOverflowError at com.seeburger.jucon.dochandler.SegmentDescription.semanticCheck(SegmentDescription.java:444) at com.seeburger.jucon.dochandler.SegmentDescription.semanticCheck(SegmentDescription.java:460) at com.seeburger.jucon.dochandler.SegmentDescription.semanticCheck(SegmentDescription.java:460) at com.seeburger.jucon.dochandler.InhouseDocReader.doSyntaxCheck(InhouseDocReader.java:1555) at com.seeburger.jucon.dochandler.InhouseDocReader.moveNext(InhouseDocReader.java:1852) at com.seeburger.jucon.dochandler.EdifactDocReader.moveNext(EdifactDocReader.java:457) at com.seeburger.jucon.dochandler.InhouseDocReader.moveNext(InhouseDocReader.java:1859) at com.seeburger.jucon.dochandler.EdifactDocReader.moveNext
    My splitter configuration is :
    classifier     classifierMappingID     Abc
    classifier     destSourceMsg     MainDocument
    classifier     showInAuditLog     true
    bic     destSourceMsg     MainDocument
    bic     destTargetMsg     MainDocument
    bic     logAttID                          ConverterLog
    bic     mappingName     AUTO
    bic     saveSourceMsg     ORIGINAL_EDI
    bic     split     true
    splitter     mode     ASYNC
    splitter     transaction     MESSAGE
    The same configuration works fine with ORDERS message.
    Also,I have configured same mapping name in Splitter section in Seeburger Workbench.
    Has anyone encountered this error before?
    Kindly let me know
    Thanks.
    Regards,
    Shweta

    Hi,
        I understand that you need to use Custom mapping for your EDIFACT Message...
    Then did you created the generic mapping with Clasasifier ID...i.e ABC_edifact... (By default it will be See_Edifact)
    so you need to create the generic mapping by Name provided in classifier ID of settings then....
    need to create the child mapping in such a way that it calls the same (developed one...)
    in default cases See_Edifact frames the child mapping name to be called based on the messages received ...
    similarly your generic mapping need to call your child mapping....
    Hope this clears you
    Rajesh

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

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

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

  • 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

  • Import Manager 'Error 5611520 - Error Saving Key Mapping'

    I am using CREDITOR_EXTRACT in R/3 to send Vendor IDoc to XI and use CREMDM04 type.  XI generates an XML file that I load into MDM using a client that is set up for Inbound/Outbound.  The key mappings have been turned on for the Vendor repository.
    In IM, I use the standard map CREMDM04 and the system maps the incoming XML file to the vendor main table.  There are few values that I have to map manually - fine.  Next, when I click Import, I get a error pop-up message 'Error Saving Key Mapping - Errno 5611520'.
    Has anybody experienced this when using all standard content (schemas and maps) for Vendor?
    Thanks in advance.

    Subbu,
    Found another system that has the same versions as you do.  This particular error did not appear, but we got some internal IM error.  Also, the SAP training demos are on the same versions as mine.
    I am using MDC R/3 as the client and the CREMDM04 schema map.  Not using MDM inbound ports for now.  Just loading XML file generated by XI based on CREMDM04. Do you think that I need to define a Qualified Range for this client in the Console or can it be left blank?
    Thanks.

  • Data source cannot be created : MAPVIEWER-00011: Error creating a map data

    Hi everyone,
    i am getting an error meaasge while creating datasource
    " Data source cannot be created : MAPVIEWER-00011: Error creating a map data source."
    pls help

    You should assign only one value to jdbc_sid. Try with this
    <map_data_source name="mvdemo"
    jdbc_host="localhost"
    jdbc_sid="orcl"
    jdbc_port="1521"
    jdbc_user="mvdemo"
    jdbc_password="!mvdemo"
    jdbc_mode="thin"
    number_of_mappers="3"
    allow_jdbc_theme_based_foi="false"
    />
    Make sure that oracle sid is 'ORCL'
    Sujnan

  • The error is " The Mapping to Node has not been completed

    Hi All,
    I am getting a strange type of error and need help immediately.
    The error is " The Mapping to Node COMPONENTCONTROLLER.1.PLANNING_ENTITY Has Not Been Completed" for the node that exists in the Parent component and is being used in all the child nodes thru reverse mapping.
    I have done mapping in all the child nodes but still the message is coming.
    Could anybody tell me the reason .
    Regards,
    Arti.

    Basically somewhere you have defined a context node 'PLANNING_ENTITY'  to be an Input-Element. At the same time you did not define (through a component usage at design time) where the input to that node is coming from. This means the mapping path to the node is not complete, and the node does not know where it is mapped to.
    Either:
    - You untick the checkbox 'Input-Element (ext.)' inside the controller context, or
    - You find the component that uses the component with the node 'PLANNING_ENTITY' and select Component_Usage->'Name of Usage'->'Add controller usage'. Inside the controller menu you see then, you can now provide a mapping to the context node.
    I realise this now sounds a little confusing, but I'm happy to provide more details should you need them.
    Cheers,
    Robin

  • Getting Error in java mapping: Parsing empty source. Root element expected!

    Hi Experts,
       I am using java mapping for schema validation of input message. I have followed all the standard procedures and implemented the java class in the interface mapping.
    My interface mapping is like this:
    OrderData --->Java Class ---SchemaValidate
                         Mesg Map ---OrderData_to_BAP --->BAPI Msg
    So first I want to validate the schema of the input message. If the input message is invalid then XI should throw an exception. Then I use the actual message mapping to map the input order data to the BAPI input parameters.
    In the java code I am using xerces parser.
    The java code works fine when I run it as a standalone application.
    The interface mapping also works fine if I don't include the java mapping. Ofcourse schema validation does not happen.
    But when I test the interface mapping by including the java mapping then I am getting the error:
    Call method execute of the application Java mapping SchemaValidate
    Java mapping SchemaValidate completed. (execute() of SchemaValidate
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: Parsing an empty source. Root element expected!
    What am I doing wrong? Why it is not getting the root element?
    My Java code is as follows:
    import com.sap.aii.mapping.api.StreamTransformation;
    import com.sap.aii.mapping.api.StreamTransformationConstants;
    import com.sap.aii.mapping.api.StreamTransformationException;
    import java.io.*;
    import java.util.Map;
    import javax.xml.parsers.*;
    import org.xml.sax.helpers.*;
    import org.xml.sax.*;
    import org.apache.xerces.jaxp.*;
    Sample mapper for SAP-XI
    @author Gopal
    public class SchemaValidate implements StreamTransformation {
        //Constants when using XML Schema for SAX parsing.
         static final String JAXP_SCHEMA_LANGUAGE =
         "http://java.sun.com/xml/jaxp/properties/schemaLanguage";
         static final String W3C_XML_SCHEMA =
         "http://www.w3.org/2001/XMLSchema";
         static final String JAXP_SCHEMA_SOURCE =
         "http://java.sun.com/xml/jaxp/properties/schemaSource";
    Injection of mapping parameters
    from integration engine
    @param map Map with configuration data
        public void setParameter(Map map) {
    Mapping implementation
    @param inputStream Input data from integration engine
    @param outputStream Output data to integration engine
        public void execute(InputStream inputStream,
                            OutputStream outputStream)
          throws StreamTransformationException {
            try {
                  // obtain an object of class javax.xml.parsers.SAXParser,
                  SAXParserFactory spf = SAXParserFactoryImpl.newInstance();
                  spf.setNamespaceAware(true);
                  spf.setValidating(true);
                  SAXParser sp = spf.newSAXParser();
                  // setup the schema file
                  sp.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
                  sp.setProperty(JAXP_SCHEMA_SOURCE, new File("IOReqMsgSchema.xsd"));
                  //parse the input xml using the given schema
                  sp.parse(inputStream, new ParseErrorHandler());
            catch(SAXException se) {
              se.printStackTrace();
            catch ( Exception e ) {
              throw new StreamTransformationException( e.getMessage() );
    My input message is :
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:OrderCreate_request xmlns:ns0="mynamespace">
       <ORDER>HTEST1234567</ORDER>
       <ORDER_TYPE>z001</ORDER_TYPE>
       <ORDER_NAME>Test Order</ORDER_NAME>
       <CO_AREA>INTC</CO_AREA>
       <CCTR_POSTED>1234567890888888888</CCTR_POSTED>
       <CURRENCY>USD</CURRENCY>
       <PERSON_RESP>12345679</PERSON_RESP>
    </ns0:OrderCreate_request>
    Kindly help! please this is urgent!!!!!!
    Thanks
    Gopal
    Edited by: gopalkrishna baliga on Feb 28, 2008 9:34 AM

    Hi Stefan,
       I did the code changes to return output stream and the java code works perfectly in standalone mode in my PC.
       But when I use the same in the Java mapping with XI then It throws an error "Getting Error in java mapping: Parsing empty source. Root element expected!".
    My XI J2EE server has JDK1.4.3.11.
    Is there any limitation of using SAX parser in XI? If Yes, then which parser should be used for schema validation in XI?
    I have included the XSD file for schema validation along with class files in the .jar file. This jar file is then imported in XI repository. Is the XI engine not able to read the XSD file?
    Do I have to handle reading XSD file differently? Any suggession how?
    Is this parser error due to some security access?
    Kindly help me! I have been struggling with this problem since 2 weeks. I will be greatfull to you if you can help me.
    Thanks
    Gopal

  • About BIC mapping designer

    Hi Guys,
    Can anybody pls give me overview on BIC mapping designer?
      Is that mandatory in seeburger related scenarios? Do i need to have the access to accomplish my business requirements
    Because Seeburger has already some default mapppings if i need to prepare any mapping that should be accessible to me right.?
    pls clarify on this.
    brief me about BIC modules that would be used in Adapter configuration ? How can we do those modules?
    Pls clarify
    Regards

    Hi,
    Can anybody pls give me overview on BIC mapping designer?
    --> THE BIC Mapping Designer responsible for managing the transformation of messages is an easy-to-use graphic tool, which gives the possibility of providing software for complicated transformations as well as quick performance for those which are less demanding.
    This is a graphic tool for the purpose of defining data formats and the information flow diagram. The relation between the source and the destination can be defined easily by means of the drag & drop technology. It may also be extended by a big set of manuals, a code in the JAVA language may be used as well. This enables the implementation of the business logic for any application.
    used for transforming and compressing data.
    File adapters: EDIFACT, ANSI X.12, TRADACOM, VDA, ODETTE, SWIFT, Biz Talk, XML.
    Servicing the data bases via JDBC , ODBC controllers.
    Message compression (GZIP,.. ).
    Dividing and joining files.
    Data format and business logic converter.
    List printing generator, data-entry-mask generator.
    Blog- Handling EDI interfaces using Seeburger BIC modules
    Handling EDI interfaces using Seeburger BIC modules
    Forum postings - Seeburger BIC Help!!
    Re: Seeburger BIC Help!!
    Is that mandatory in seeburger related scenarios? Do i need to have the access to accomplish my business requirements
    --> BIC Mapping is required in case of EDI Messages, as Amir had already mention inprevious post if the messages are coming in XML format, then I don't think its mandatory to use.
    Because Seeburger has already some default mapppings if i need to prepare any mapping that should be accessible to me right.?
    --> Refer -- Building own schemas in Seeburger bic mapper  
    Building own schemas in Seeburger bic mapper
    Plesae refer below links to get more details of BIC Mapping designer
    check the link related to bic mapping
    1.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
    Thanks
    Swarup

Maybe you are looking for