Missing IDOC Segment from RWB

Hi all,
I am experiencing an issue where <MESCOD> segment from ORDERS IDOC is not passed to target when sent from RWB.  When sent from source system, everything processes correctly, but our test messages from RWB lose <MESCOD>IC</MESCOD> when they reach the target system.
Our interface mapping for this scenario involves both a message mapping and an ABAP mapping before it is processed to target.
Any ideas to why this issue is isolated to RWB?  Any suggestions would be greatly appreciated.
Thanks,
Kevin

Hi Swarup,
I meant to say that we are taking a message from sxmb_moni from the source and resending in RWB to test new changes.  Therefore, it's an IDOC within XML tags as XML is declared.  Every field processes correctly when doing this method except MESCOD.  Why would every XML node process successfully except one?
Again, when passing this IDOC from source system, everything processes correctly.
Thanks,
Kevin

Similar Messages

  • Missing IDOC segment during invoice for specific user

    Hi Experts,
    While doing a post goods issue and generating an invoice, the idoc generated from this has missing segments, this only happens when using a spcecific RFC user name (with all authorizations enabled), however, when using an ordinary sap account, the idoc is created successully with no missing segments. Do you have any advide on what seems to be causing the issue? Any help is very much appreciated.
    Thanks in advance.

    yeah
    u go to TCODE WE30 and give ur object name and enter.
    then u will see all the segments related to ur object.
    u can double click on each segment and see whethet it is mandatory or not.
    regards
    jai
    please reward if helpful.

  • Node function to use for relating two idoc segments from source in mesmapp

    Hi Sap All.
    here i have got a requirement to do a graphical mapping between Souce Idoc Structure to target file structure .
    here i have got  aspecific requirement from the Functional saying that they want
    for a segment from source idoc with name E1EDL24-NTGEW should be mapped with shipment_detail-nett_weight
    and the conditon here is There should be a corresponding entry in E1EDL24 for each E1EDL44?(other) segment type.
    can nay body help me in guiding  how and what node functions do i need to use here to ge the solution.
    regards.
    Varma

    Varma,
    If you could give a sample that would be great!
    raj.

  • Multiple idoc segments from single flat file

    hi,
    I want to upload data throught LSMW,   in a single row i have many item. can anyone give me idea, how to proceed.
    2.  i have to show a custom error report linked to lsmw.. how to do it..
    waiting for your reply
    Thanks & Regards
    Dinesh

    What object do you need to load?
    What exactly is in the file (what kind of data) ?
    If it is a simple file with few fields, then i think a recording is the fastest methods. It does give you a detailed error log.
    But all this depends on the file you have

  • IDOC Segment Definition received instead of Segment type

    Hello Folks,
    When i send a Z Idoc Segment from A to B System, It is successfull from A System, but in B System sometimes its erroringout because in the inbound idoc Segment Definition is coming instead of Segment type.
    For Example
    From A System I have sent Z1P0002 segment
            B System I have received Z2P0002000(Which is the segment definition for Segment type Z1P0002)
    Any inputs to above problem?

    Hi,
    The problem may be due to system B using a older release version of the IDoc. In those scenarios, even though your IDoc type is recognized, it may not be possible for the reciever to determine the right segment version of the reciever.
    There are options in the WE20 partner profile configuration, Field Segment release in IDoc type and Segment Appl. rel. which enable the partner system preventing from erroring out.
    BR/Yogesh
    Edited by: Yogesh Surender on Jun 1, 2009 12:34 PM

  • Some Data Missing in the inbound Idoc received from Gentran

    Hi,
    We are receing one custom message type with the basic type ORDER05 in SAP from Gentran. When we checked the destination file generated in Gentran, its showing data for all the segments. However in SAP when we checked the corresponding idoc we find the segment E1EDP05 is missing. The Gentran team says they are placing the destination file in the unix server of SAP. However we dont find these files in the SAP Unix server. Could anybody advise what could be the problem and where we need to check further ?

    Gentran will never be able to create an IDOC within SAP. Here is what happens:
    > Gentran creates a flatfile/XML which is in the IDOC format (the one which you can see in WE60).
    > Gentran then places this flat file/XML in a folder on Application server. This can be UNIX, Windows NT, etc..
    > Gentran then triggers the Startrfc.exe which will trigger EDI_DATA_INCOMING function module.
    > This FM will parse the data, check it for consistency of the defined standards, then write the control record into EDIDC and corresponding data records into EDID4 and updates the relevant statuses (i.e. 01 - added, etc). It'll then look into the partner profile setup, look for process code and moves the status to 64 and calls the inbound FM which will post the application document.
    In you case, you need to find out what file is coming in and where E1EDP05 has missed. The data will only be sent by Gentran. The inbound function modules will never update IDOC data records (unless there is a customization). The status records are updated.
    If E1EDP05 is not mapped and sent by Gentran and you still used to see it, then there should have been a customization in place to add values to IDOC segment fields. Try to get the final file that is mapped from either X12/EDIFACT and then see if E1EDP05 segment is present in there. If it is present then upload the same file into AL11 using CG3Z and call EDI_DATA_INCOMING or WE19 to process it. Once processed, you'll can observe if E1EDP05 is being created or not.

  • TAX ASSESSMENT BASIS MISSING IN SEGMENT E1EDK04 FOR IDOC INVOIC

    Hello,
    Tax assesment basis is missing in segment E1EDK04 for IDOC INVOIC. In EDI messages,Tax assesment basis has to be sent in TAX segment together with VAT rate. When there is only one VAT rate this is not a problem as tax assessment basis is the total net amount (And we have it in the IDOC). On the other hand when there is more than one VAT rate in the invoice, we don't have in the IDOC the Tax assesment basis of each VAT rate.
    Did someone experience this issue ? How did you handle it ?
    Regards.
    Eric.

    Dear Eric
    The latest pack available now for these components are (for PI 7.1)
    SAP BASIS 7.11 support package 6
    SAP HR 6.04 with Support Package 44
    If you are in PI 7.0 then I suggest you download the latest patch from marketplace.
    Sourabh

  • Missing IDOCS from SAP to BODI

    I have an issue of missing idocs from sap going to BODI.
    Idocs are received by BODI trough adapter, but there are idocs that are missing but are successfully sent by SAP. When trying to resend the idocs it was successfully received by BODI.
    We thought that it is an intermittent connection issue, so we try to send idoc from SAP while the adapter was down. The idoc was successfully sent from SAP. Then we try to start again the adapter and it was loaded after sometime.
    Iu2019m now out of idea on why does the idocs went missing. Can someone help me?
    Thanks in advance.

    Hi Parida,
    IDoc Status 03...Green Status... wills not guarantee you that IDoc reached EDI subsystem...
    Run the Program RBDMOIND in SE38...
    Changed on                               :<Date>
    IDocs/Commit Work                   :100
    Display IDoc not sent- Check the Check Box.
    Now you will get list of un posted IDocs
    Ramesh

  • IDoc segment version issue in ECC upgrade from 5.0 to 6.0

    Hi experts,
    we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
    In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
    We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
    has any one faces such situation in the past? if yes, please throw some light.
    Thanks in advance.

    Please let me know if your issue was resolved. I have similar issue now.
    Thanks,
    Sailaja

  • Incoming IDOC-Segment missing

    Hi, Friends,
    I have a strange problem.
    The incoming IDOC in idx5 list miss a segment although the meta data is renewed.
    Could sb. help?
    Thanks and Reguards
    Zhiping

    Hi Krishna, Hi Jakub,
    I tried both. But it remains.
    Still strange is, the ALEAUD idoc with Z-Segment containd in E1PRTOB-Segment produced by the sending system contains some E1STATE segments. But the number of ALEAUD idocs recieved in IDX5 list is the number of the E1STATE segments in sending system. And every recieved ALEAUD idoc contains only one E1STATE-Segment
    Why is it splitted? and where?
    Thanks
    Zhiping

  • How we remove duplicate segments from an idoc

    how we remove duplicate segments from an idoc.

    Hi Manju.
    Go to T-code WE19------->Give your Existing Idoc Number or Basic Type --->Get in Select your (Nodes) segment and Click on "Delete Indicator"
    Regards,
    Seegal

  • ME59 Purchase order outbound idoc header text missing in segment

    Hi All,
    When Purchase Order created via ME59 for third party vendor Outbound Idoc is created but Header Text of PO not copied into IDOC Segment.This Problem occurs when PO has sales order assignment.
    Please Advice..
    Thanks,
    Vinod.

    Hi Ankur,
    I am not an expert in this area but I'm looking on an ORDERS05 iDoc where I have the following data for E1EDK14:
    <u>E1EDK14 014:</u>
    QUALF: 014
    ORGID: [Purchasing organization ID]
    <u>E1EDK14 009:</u>
    QUALF: 009
    ORGID: [Purchasing Group ID]
    <u>E1EDK14 013:</u>
    QUALF: 013
    ORGID: [Purchase Order type, e.g. EC]
    <u>E1EDK14 011:</u>
    QUALF: 011
    ORGID: [Company Code]
    Hope this helps!
    Regards,
    Kristoffer

  • Concatenating texts from multiple IDoc segments

    Hi everybody!
    I have to concatenate log texts supplied via IDoc segments into one string. There can be zero or more segments, each with one line of the long text. The result should be one single string field filled with all the lines concatenated.
    What's the easiest way to achieve this result? Do I need a user-defined function or can I code this using standard built-in funtions (this solution would be preferred)?
    Regards,
    Joerg

    Use the UDF with the following logic.
    Take the input type as Queue of the Segments
    Concatenate the temp = temp + a<i> in the loop
    return the temp.
    <b>UDF as follows:</b>
    String temp = " ";
    for(int i=0; i< a.lenght; i++)
    temp = temp + a<i>
    return temp;
    Your probelm will solve with the above UDF.
    Warm Regards,
    Vijay

  • Syntax error in IDoc segment

    Hi,
    when I make a syntax check on my Idoc segment '/FIT/E1FISFIINV'  I get the error message:
    Entries for segment '/FIT/E1FISFIINV' missing in the 'Segment structures' table.
    I can't delete the segment type as I get the error message Segment /FIT/E1FISFIINV does not exist yet when I try it.
    But I also can't create the segment type as I get the error message Structure /FIT/E1FISFIINV already exists
    I already looke in the tables EDISDEF and EDISEGMENT to check that the entries for the segement /FIT/E1FISFIINV do exist in these tables.
    Does anybody have an idea how to solve this problem?
    Thank you.
    Martin

    I want to create a new idoc type '/FIT/xxxxx' and therefore I want to create new segment types  '/FIT/xxx' for this.
    I copied the segment types from another system (older release) to that system but there seems to be a data inconsistency. which I am trying to fix.

  • Regarding EDI: Syntax error in IDoc (segment cannot be identified)

    Hi,
    My requirement is that I was adding two diffrent field values under two diffrent segments as "E1EDKA1" and "E1EDK02" in outbound invoice IDOCS, INVOIC02 (process code: SD09 - IDOC_OUTPUT_INVOIC).
    I am getting the IDOC number through Tcode "VF02". Can any body give me idea how to check that syntax error in debug mode.
    Please find the following error details using TCODE "WE02".
    *EDI: Syntax error in IDoc (segment cannot be identified)*
    *Message no. E0 078*
    *Diagnosis*
    *The segment E1EDKA1 does not occur at the current level of the basic type INVOIC02 (extension ).*
    *This error can have several reasons:*
    *The segment E1EDKA1 is assigned to a group whose header segment does not occur.*
    *The segment E1EDKA1 does not exist in the syntax description of the basic type INVOIC02 (extension ).*
    *The sequence of segments in the group in which the segment appears is incorrect.*
    *Previous errors ('mandatory' segment or group missing) may be due to this error.*
    Please help me to resolve this problem. <REMOVED BY MODERATOR>
    Regards,
    Skumar.
    Edited by: Alvaro Tejada Galindo on Apr 28, 2008 1:09 PM

    It seems that you added segment E1EDKA1 at a place where it is not supposed to be. That's where this error is coming from. The structure of every IDOC is definded by SAP standard and you cannot change the sequence or the level of standard segments. If you require a certain field at a certain level you have to add that field to a Z-segment and then add that Z-segment where appropriate in your extension.
    Hope that helps,
    Michael

Maybe you are looking for

  • Vendor ageing

    Hi Team, The requirment called vendor ageing report. when we using the T.code F.46 for company code level in standard sap 0-30   31-60   61-90   >90. So our requirement is 0-30  30-45 45-60 60-90  >90. So this is can able to change the days. Regards,

  • Connect Macbook PRO house sound system via IPOD adaptor

    I want to connect my Macbook PRO via USB to IPod dock adaptor on whole house sound system w/IPOD adaptor. Any suggestions for adaptors with USB to IPOD-like port?  In other words one end of the cable needs USB (for Mac) and the other needs to look th

  • Data into class to JSP (using dataTable)

    Hi, I have one class called pessoaHandler I have one JSP file called index.jsp with a dataTable <h:dataTable value="#{pessoaHandler.pessoas}" var="p">How I can acces the java.util.List that stay into pessoaHandler ? In the class has private List pess

  • How to do "DDL rollback"

    I have script, that contains several DDL-statements. For example script removes FK-constraint from a column, then it renames the column, then it puts new data to the column, then it puts new FK-constraint to the column, also some other ALTER-statemen

  • Any performance impact on satellite systems?

    Hello, Our productive solution manager are setup to connect to all the ECC, XI & R/3 systems, as central monitoring system. So far we only use Solman for monitoring & EWA, not even BPM is configured yet. in SMSY, it's configured to use our XI SLD, to