SEEburger error in conversion from EDI to EDI-XML

Dear SAP experts,
Good day!
Can i seek your inputs regarding this error i'm getting when i've tried to convert the EDI (D93A_RECADV message) into EDI-XML?
I am using BIC for this one.
This is the error i am getting,
[Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[78167]: the found segment  is not in the message description.
Conversion error
Does this mean the source file is in wrong structure?
Kindly advise.
Thank you very much!
Fred

Hi,
Make sure that You used the Source structure in the IR from the External Def of the Seeburger SWCV only.
And deployed the necessary mappings on XI server by making the .sda file in BIC.
And the Incoming file should have the valid values while parsing the EDI file inorder to convert the EDI ti EDI_XML
Check this also
/people/nithiyanandam.au2/blog/2008/02/20/handling-edi-interfaces-using-seeburger-bic-modules
Regards
Seshagiri

Similar Messages

  • Error Message: Conversion of file content to XML failed at position 0: sun.

    Hi Experts,
    i strugle with a File 2 IDOC Scenario.
    In the sender communication channel monitoring I get the error message:
    Conversion of file content to XML failed at position 0: sun.io.MalformedInputException
    Unfortunately I am not getting any further information and I do not know where the file-adapters problem is.
    Tthe .fieldSeparator = # . Can this be the problem, that the file-adapter-engine can not handle # within file conversion? I also tried it with .fieldSeparator = '#' . But the error message is the same.
    I am glad for any hints.
    Thank you for your help in advance.
    Regards,
    Udo

    Hi Udo,
    The error is due to wrong intput.
    putting # might be a reson.
    You Can try (,) or a space as a field separater.
    Can you test this once.
    Have to defined the field separated?
    Regards,
    Sumit Gupta

  • Run time error message - Conversion from string "Mobile Telecommunications" to type 'Boolean' is not valid.

    I get a error message when I select an element in the combo box, please review my variables:
     Public Sector As String
        Public Index As Decimal
    ...and code
     Select Case ComboBox1.Text
                Case "Banks"
                    Sector = "Bank" And Index = -0.086
                Case "Mobile Telecommunications"
                    Sector = "Mobile Telecommunications" And Index = -0.024
                Case "Real Estate Investment Trusts"
                    Sector = "Real Estate Investment Trusts" And Index = 0.132
            End Select

    And is a boolean operator. Try it like this instead:
    Select Case ComboBox1.Text
    Case "Banks"
    Sector = "Bank"
    Index = -0.086
    Case "Mobile Telecommunications"
    Sector = "Mobile Telecommunications"
    Index = -0.024
    Case "Real Estate Investment Trusts"
    Sector = "Real Estate Investment Trusts"
    Index = 0.132
    End Select
    Still lost in code, just at a little higher level.

  • Error 3 in Update(The Conversion from 0CALDAY to 0FISCPER failed)

    Hi Guyz....
    Seriously struck with this issue while loading data into 0PP_C02 using the D.S- 2LIS_04_P_MATNR. I've been getting the error "Time Conversion from 0CALDAY to 0FISCPER (Fiscal Year) Failed... and at update rule I've been getting the error "Error 3 in Update"
    I've searched almost all the posts- alas, all are unanswered.
    Can anyone please provide me the right soultion...?
    Thanks,
    Regards,
    G!

    Hi Gautam,
    For converting calday to fiscal period, you need to have fiscal variant and also entries in Table T009B for this fiscal variant.
    1) Check whether you have company code populated for all records.
    2) Please check whether you have fiscal variant maintained in the company code master data.
    3) Check whether you have T009B table maintained.
    If not this can be transferred in source system -> Global settings.
    Hope this helps.
    Thanks,
    Krishnan

  • Conversion from u0091Stringu0092 to type u0091Dateu0092

    Hi,
    I am fetching a date from DeliveryDate TextBox from Sales Order. I enter as 10/03/2007. As I need to fetch this value and store it in Production Order DueDate records through SDK Code.When I fetch this value from code,I get as 20070310. When I try to update my Production Order DueDate it gives me an Error Msgbox “Conversion from string “20070310” to type ‘Date’ is not valid.” Here is my code to update production order.
    Dim DelDt As String
    DelDt = MyForm.Items.Item("12").Specific.value
    Here DelDt shows 20070310
    Now I have created an object of ProductionOrder and try to add Records,
    sboProdOrder.DueDate = DelDt
    On the above line it gives me that messagebox.
    Can any one help me as to how can I convert this code in a working one or how to convert the string to date in VB.Net
    Thanks a lot
    Murtaza

    Hi Murtuza,
    Retrieving the value from a date-field through the value always returns the date as a string in the format yyyymmdd.
    the field DueDate is a field of type DateTime.Date. to enter the date in this field, you must convert the string to a date.
    The following line converts the date-string to a date.
    new DateTime.Date(left(DelDt,4), mid(DelDt,5,2), right(DelDt,2))
    Regards
    Ad

  • Short dump: Conversion from type 'c' to 'v' not possible

    Hi,
    When do we get the following error? 'Conversion from type "c" to "v" not possible'.
    I am getting this dump when I try to assign a structure to a field symbol.
    This is happening only for a specific structure type. 
    Thanks in advance,
    Regards,
    Wenonah

    Hi,
    type - v is Structure with internal table , deep structure....
    u might have declared the field-symbol as a typed one.....
    Declaring it a generic one like type any as suggested in above post might solve the problem.....
    Cheers,
    Jose

  • Conv from IDoc to IDoc xml

    Hello All,
    When SAP is triggers an IDOC to SAP XI, the conversion from IDOC to IDOC XML takes place in SAP XI(correct me If Im wrong here).
    Can some body tell me what is the mechanism behind this conversion from IDoc to IDOC xml....and there is no adapter comes to into picture as the sender is SAP....which component does this conversion in XI
    Regards,
    Thai

    To Convert IDOC to IDOC XML and the other way around,IDOC Meta Data is required by the IDoc adapter(availabe at Integration Server).
    IDoc metadata is loaded in IDX2 Using  RFC connection maintained in IDX1(port maintenance in the IDoc adapter).
    For more details refer http://help.sap.com/saphelp_nw70/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm

  • Error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element

    Hi All,
    I am facing below mentioned error while using '*'in the NTE (EDI 850) Segment where '*' is also used as Data Element
    Error: 1 (Field level error)
      SegmentID: NTE
      Position in TS: 70
      Data Element ID: NTE02
      Position in Segment: 2
      Data Value:
      3: Too many data elements
    For Eg: NTE*GEN*My Text *goes here
    Here, NTE02 should be My Text *goes here. So, how can I use "*" here without changing anything in the EDI message?
    Can it be done?
    Thanks.

    Sorry, no.
    X12 does not support an escape character so whatever is used for delimiters become reserved characters.
    If you want to allow '*' in the data, you will have to chooser a different Element delimiter.  The receiver should read the from this from the ISA Segment so it's supposed to be dynamic but that's not always the case in practice.

  • Reg: IDoc is u0091pushedu0092 into SAP from the external EDI system

    Iam facing one issue in our system for message type DESADV (inbound). please read through .
    "When an IDoc is pushed in from the external EDI system & even though the inbound Partner Profile is set to immediate processing mode:
    The IDoc stays in status 64 - 'IDoc ready to be transferred to application'. This assumes that the IDoc has not been processed yet and still needs to be processed with program RBDAPP01 (or via the “process” button in BD87).
    We don't want to again run this program "RBDAPP01". What was the problem.
    I appreciate ur help.

    Hi Krishna,
    In some other scenarios if an IDocs remains in status 64, it means that the processing within the IDoc engines did not reach its end, where the new status could be set. There are two principal reasons:
    1. In the matching partner profile the processing is not set to "Trigger immediately"
    2. The application that processes the IDoc abnormally ends with a fatal error (crashes). If this happened you will see a trace in the system log (ST22). In this case have the satellite system write the file to disk but you trigger the EDI_DATA_INCOMING. Then start EDI_DATA_INCOMING from SE37 manually and debug yourself through the individual steps. A good start would be to set a break-point in the application handling function (in your case: IDOC_INPUT_DESADV ).
    If useful do reward.
    Regards,
    Adarsh Srivastava

  • Error while loading : Time conversion from 0CALDAY to 0FISCPER

    Hi ,
           I get the following error when loading to an ODs .
    My 0FISCPER is mapped to one of the date fields from the extractor (Document date) and also Have 0FISCVARNT as part of data fields  .
    " Time conversion from 0CALDAY to 0FISCPER (fiscal year ) failed with value 20060405 " .
    thanks .

    Hello CG
    Please refere this forum
    Time conversion problem
    Thanks
    Chandran

  • How to create an XML file from a given EDI file?

    Hi All,
    I am trying to write some BPEL processes that will be sending EDI Documents to Integration B2B using the AQs.
    BPEL works with XML data and finally enqueues it to the AQ IP_OUT_QUEUE. From there B2B will pick up and send to Trading partner. I have sample EDI documents but they are not xml. Can anyone tell me if i can convert these EDI docs to XML?
    Can the EDIFECS builder be of any use here?
    TIA,

    B2B adapter? I just want some test data. Finally the setup is going to be such that some xml is going to be posted to the B2B internal channel and then on it will translate and send to Trading Partner.

  • SEEBURGER Error (Outbound from XI): SSLHandshake Exception

    Dear SAP experts,
    Need your help regarding Seeburger error that i was encountering during our testing.
    SAP have successfully triggered an IDoc from their system and was successfully sent to SAP XI for message translation. SAP XI have successfully translated the message and will be sending the output message via AS2 of XI to AS2 of the third party.
    But, as looking the Seeburger (message monitor) of XI, there is an error logged:
    Status Description:  Could not deliver as2 message to partner: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found # null
    The AS2 of the third party is also their SSL certificate.
    Can somebody help me what is the root cause of the error?
    Thank you very much in advance.
    Have a great day!
    Godofredo

    Hi Soumya,
    Thank you for your information.
    The XI certificate we are using wa not yet expired. (will be expired by Sept 2008).
    The second link, i think, was not applicable, since, we are using AS2 adapter and not Soap adapter.
    Im still checking what could be the root cause of the issue.
    Hope you can help me with this one.
    Thanks!

  • Benefits Service - Error occurred during currency conversion from  to USD

    I am attempting to run the add beneficiaries service in employee self servie and receive the following error message "Error occurred during currency conversion from blank to USD
    Has anyone come across this error before?

    Both are set up properly.  This error only happens on some US teammate records.  It seems to occur after we do a refresh of our QA environment from our produciton environment

  • How can we identify idoc is generated from ale or edi

    hi friends,
    This is interview question asked in tcs,
    how can we identify idoc is generated from ALE or EDI.
    please give me reply if anybody knows
    thanks,
    hari priya

    Idoc created by ALE is a means of migrating DATA between SAP systems. You configure logical destinations, establish some migrating criteria and the system takes care of getting your data from point A to point B
    Where as Idoc created by EDI is described as the interchange of structured data according to agreed message standards between computer systems, by electronic means. Structured data equates to a simple and direct method of presenting the data content of a document. The method of ensuring the correct interpretation of the information by the computer system is defined by the EDI standard."
    EDI is a technique used to communicate business transactions between computer systems of different companies and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to other systems within the same organization."
    Also refer to these lonks:
    www.sapgenie.com/sapedi/edi_sap_training.htm
    www.sap-img.com/basis/ difference-between-edi-and-idoc.htm
    www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b592afab52b9e10000009b38f974/content.htm
    www.help.sap.com/saphelp_nw04/helpdata/ en/35/26b594afab52b9e10000009b38f974/content.htm
    http://www.onestopsap.com/interview-Question/edi/
    IDocs act as data containers in an ALE scenario. They are just a format of storing application data and then transferred using ALE. Take a look at http://www.sapgenie.com/ale/why_ale.htm and http://www.sapgenie.com/sapgenie/docs/ale_whitepaper.doc for further details on ALE.
    Check this link.
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.henrikfrank.dk/abapexamples/IDOC/IDOC.htm
    http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
    http://help.sap.com/saphelp_47x200/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
    Reward points if found helpful...
    Cheers,
    Chandra Sekhar.

  • Workflow tasks related to error processing when u201Cinvoices received via EDI"

    Hi all,
    Please tell me the process like how an workflow tasks related to error processing when u201Cinvoices received via EDI".
    Give me in details the inform.
    Thanks in advance
    Chakri

    Hi Sven,
    Please implement SAP Note: 1321676 in your backend system to solve the current issue.
    But later you will have to implement SAP Note: 1380788 also in your backend system to solve some other issues.
    Regards,
    Binson

Maybe you are looking for