IDOC Segment missing when reaching to ECC

Hi,
This is file-to-IDOC scenario. When file is loaded XI is picking and creating IDOC with all segments as expected in XI, but when reached to ECC sytem main header and item segments are missing.
Refreshed cache, reloaded metadata in XI, did full system cache refresh but no luck.
Checked in ECC thru IDOC_INBOUND_ASYNCHRONOUS function module to create IDOC and it did create successfully with all segments.
Segments are missing only when coming from XI. We are in SAP ECC 6.0 & PI 7.0. IDOC I am using is DELVRY03

Hi Sriram,
Can you please check this note which disucss about the same issue:
Note 1170918 - IDoc adapter: Missing fields and deleted metadata
Regards,
---Satish

Similar Messages

IDOC Segment missing

Hi ABAP Experts, I created one Inbound IDOC using some standard segments. When I see the Idoc using WE02 and double click on it it does not show me the same no of segments as I included in 'IdocType'. Can someone please suggest how to check and get the same no of segments in IDOC as used in Idoc Type.

Did you also try by varying the time a little and by giving the date range with more expansion.
Becoz the time on your system might differ with time on application server.
I don't see any reason for it not displaying.
Please check them with a wider range and let me know.
thanks.

IDOC Segment missing for MATMASS Message type

Through change pointer program for the message type YAUIHUBMATMAS IDOC is triggered.
1) Change pointers are defined in system for the message type T Code u2013 BD52.
2) If respective field is changed in material master , this data is stored in change pointers table BDCP.
3) Background jobs are scheduled every day, which searches for the changes pointer table and triggers the idoc.
In our case IDOC is getting generated but with one segment missing.
We have analysed the succesful and failed IDOC and found desrepency is field updation of BDCP table.
Succesful case contain material number in object value of ZZMDST field where as failed contain some other value.
Can anyone please help us to guide how the BDCP table is updated and the values are mapped in it or any other suggestion to find why the segment is missing in it.
Regards,
Roshni.

Jürgen L. wrote:
> I have never seen a YAUIHUBMATMAS IDOC, nor a ZZMDST field .
> This seems to be home made.
>
> You are expecting that standard SAP programs are generating change pointers for your z-fields?
> Do you see a change history in material master for your z-field?
>
>
> follow the slution from this thread:
>
Yes ,This is a Z -field.
Change pointer is triggering the idoc fo this Z-field but in some cases one segment is missing .
This is z-field in the basic data view of material master.
Yes , we have checked the change history in material master for this field it is getting updated there in BDCP table as well but in BDCP table if this field is flagged then object value is not contain material number instead it contain some other number .
But in case of succesful IDOC the object value is same as material number.
Regards,
Roshni

Should not come to AE when the IDOC segment missed

Hi,
I 've done the multimapping from IDOC to mul.files.
Here my sender IDOC line Item contains 2 segments.
Let us assume the first segment named Z1CONSGROUP and having some fields which has mapped to my receiver end files.
In production system we should not have the case where there is no Z1CONSGROUP segment.
Here if the IDOC doesn't contain this segment then it's a payload error and it reached to RWB status : system error.
But, i want to prevent this in production when this Z1CONSGROUP segment doesn't contain the idoc it should n't reach to AE.
How can i do that...is there any option to maintain such a scenario in XI.
Please help me out on this.
Kind regards,
Y.Raj

>
YeswanthRaj Kumar wrote:
> Hi,
> I 've done the multimapping from IDOC to mul.files.
> Here my sender IDOC line Item contains 2 segments.
> Let us assume the first segment named Z1CONSGROUP and having some fields which has mapped to my receiver end files.
> In production system we should not have the case where there is no Z1CONSGROUP segment.
> Here if the IDOC doesn't contain this segment then it's a payload error and it reached to RWB status : system error.
> But, i want to prevent this in production when this Z1CONSGROUP segment doesn't contain the idoc it should n't reach to AE.
> How can i do that...is there any option to maintain such a scenario in XI.
> Please help me out on this.
>
> Kind regards,
> Y.Raj
the easiest thing to do is,
1. Use a condition on Z1CONSGROUP and use the EX operator (ref: /people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination)
2. if the EX gives you a fail, then provide no receiver and use the option 'Options for Behavior at Runtime If a Receiver Is Not Found' -> End Message Processing Without Error (Restart not Possible)
3. Else provide the right receiver and let the flow continue.

Idoc segments missing in the final output

hi
Using a file - idoc mapping. have mapped all relevant fields, but in the output only segments show up. not getting all the mapped segments when i test this message mapping. Could anybody please guide me.
thxm
Pradip

Hi Pradip,
see the cardinality of the node which is having the line items......if it is 0..1 then only the first line item will be used in mapping...........if it is 0..unbounded then only all your line items will be shown........so in your mapping test, in source file can you see all the line items in the tree structure.......check the cardinality of your target node also............if it is 0..1 then only the first line item of source will be mapped.
Thanks,
Rajeev Gupta

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

Outbound Idoc Segment Creation via BD52 trigger

hi all,
i am new to Idocs so please forgive me if i am missing the obvious. i am using standard the material master Idoc type MATMAS05 to transmit any material master changes to an existing legacy system. i set up some fields in BD52 to trigger an Idoc when they are changed. the problem is when i change a field in the MARC segment (ie: MARC-PRCTR - Profic Center) 3 segments are generated (E1MARAM, E1MAKTM, EIMARCM), but when i change something in the MARA segment (ie: MARA-PRDHA - Product Hierarchy) only E1MARAM and E1MAKTM are sent.
the receiver is set up for all three Idoc segments so when only 2 are sent it errors out. how can i force all 3 segments to send every time?
many thanks.
James Hinkin

Hi, I think you must be running the program RBDMIDOC to send an IDoc based on the change pointers.
SAP has designed such a way that it will create IDocs only with changed data. In other words, E1MARAM is always populated as it is header data. Its obvious that you dont want to send the data that is not changed. Hence if you are changing Product hierarchy, only relevent segments are populated with values.
If you still want to send all the data irrespective of whether those fields are changed or not, either you may have to code in a user-exit to populate these fields(segments) or, change the program accordingly.
Hope this helps you and let me know if you need further help
Vamsi

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

EDI: Syntax error in IDoc (mandatory group/segment missing)

hi EDI/IDoc experts,
Need you help urgently. According to the requirement, i need populate a segement E1IDT01 of basic type PEXR2002 . I added the code , then run and generate an idoc , the new segment
E1IDT01 was populated, but Syntax error 26 happend. Error message as below.   It also strange that i can see E1IDKU5 populate out as usual, but some others segment disappeared , i am sure that in my code ,i didn't changed any variable related to other segement . how can i fix this problem?
EDI: Syntax error in IDoc (mandatory group missing)
Message no. E0079
Diagnosis
The segment group E1IDKU5 has the attribute 'Mandatory' in the syntax description of the basic type PEXR2002 (customer enhancement ). However, the segment group is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment group is missing.
Procedure
Please check the IDoc or the syntax description of the basic type PEXR2002 (customer enhancement ).

Hi all,
Thanks so much for your concern!
Finally ,this problem has been figured out .
Requirement is user want to use segment E1IDT01 in idoc to populate the long text they maintained in accounting document vendor item line (use FB01 to create accounting doc).
Why I made out " EDI: Syntax error in IDoc (mandatory group/segment missing)" this message out ,because I didn't fill data correctly. I missed to keep SY-TABIX in momory .
when we use Function module ,or do..enddo...or read table it_table. we should be careful that SY-TABIX is changed .So we can't just use MODIFY EDIDD_TABLE INDEX SY-TABIX in the last . we should define a local variable to keep SY-TABIX in memory and then use it to modify EDIDD_TABLE.
Follow is the final code.
IF SEGMENT_NAME = 'E1IDT01'.
TABLES :STXL.
* Define for long text getting
DATA: LIT_TLINE LIKE TLINE   OCCURS 0 WITH HEADER LINE.
DATA: LV_STRING(2000) TYPE C.
DATA: LV_TDNAME TYPE THEAD-TDNAME,
        LV_ID     TYPE THEAD-TDID     VALUE '0001',
        LV_LANG   TYPE THEAD-TDSPRAS VALUE 'E' ,
        LV_OBJ    TYPE THEAD-TDOBJECT VALUE 'DOC_ITEM'.
data:   LV_LINE   TYPE I,                " long Text lines
        LV_LEN    TYPE I,                " long Text length
        LV_TABIX LIKE SY-TABIX.
* Clear memory
CLEAR:LV_TDNAME,
        LV_STRING,
        LV_LINE,
        LIT_TLINE, LIT_TLINE[],
        LV_LEN,
        LV_TABIX.
* Keep sy-tabix memory using a variable--This is the key point
LV_TABIX = SY-TABIX.
* Combine TDNAME with company code + accounting doc + fiscal year + item number.
    CONCATENATE REGUP_DATA-BUKRS REGUP_DATA-BELNR
                 REGUP_DATA-GJAHR REGUP_DATA-BUZEI INTO LV_TDNAME.
* When vendor item has long text , read long text into lv_string
    SELECT SINGLE *
      FROM STXL
      WHERE TDOBJECT = LV_OBJ
        AND TDNAME   = LV_TDNAME
        AND TDID     = LV_ID
        AND TDSPRAS = 'E'.
    IF SY-SUBRC = 0.
      CALL FUNCTION 'READ_TEXT'
        EXPORTING
          CLIENT   = SY-MANDT
          ID       = LV_ID
          LANGUAGE = LV_LANG
          NAME     = LV_TDNAME
          OBJECT   = LV_OBJ
        TABLES
          LINES    = LIT_TLINE.
      IF NOT LIT_TLINE[] IS INITIAL.
        DESCRIBE TABLE LIT_TLINE LINES LV_LINE.
        DO LV_LINE TIMES.
          READ TABLE LIT_TLINE INDEX SY-INDEX.
          CONCATENATE LV_STRING LIT_TLINE-TDLINE INTO LV_STRING.
        ENDDO.
        LV_LEN = STRLEN( LV_STRING ).
* Make sure we only need less than 840 charicters
        IF LV_LEN > 840.
          LV_STRING = LV_STRING+0(840).
          LV_LEN    = 840.
        ENDIF.
* Populate Vendor item long text with segment E1IDT01 start from
* Fields TXT03 to TXT14.
         EDIDD_TABLE-SDATA+147(LV_LEN) = LV_STRING.
        MODIFY EDIDD_TABLE INDEX LV_TABIX.
      ENDIF.
    ENDIF.
ENDIF.

EDI: Syntax error in IDoc (mandatory segment missing)

HI all,
Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
Status ID - E0
Message No - 072
Status of the IDoc - 26
Please help me how to solve this issue?
Thanks,
Srini

Hi,
This error normally comes up when the sequence of segments has been disturbed.
For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
Thanks,
Manish

Issue:EDI: Syntax error in IDoc (mandatory segment missing):Idoc extention

Hi all,
I have extended the the standard IDOC MATMAS05 classification view with structure as below-
E1MARAM                        Master material general data (MARA)--->Mandatory segment
     Z1KLART                        KLART --->Extended chaild to E1MARAM
         Z1CLASS                        segment for class --->Extended chaild to Z1KLART
         Z1CHARACTERISTIC               CHARACTERISTIC --->Extended chaild to Z1KLART
     E1MARA1                        Additional Fields for E1MARAM
     E1MAKTM                        Master material short texts (MAKT) --->Mandatory segment(Child   to
E1MARAM )
I am getting an error in IDOC fro material master as:EDI: Syntax error in IDoc (mandatory segment missing ).
Diagnosys By system is :*The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ZMATMAS05). However, the segment is missing in the IDoc. The segment number logged in the status record identifies the item before which the segment is missing.
This error may have been triggered by an unidentifiable segment before the expected mandatory segment.*
Please help to resolve the issue.
Thank you.
Edited by: sanu debu on Apr 30, 2009 11:25 AM
Edited by: sanu debu on Apr 30, 2009 11:31 AM

Hi,
   You cannot add an segment in the middle of other segments.
YOu have to add any segment at the last.
If you want to add a segment as the child of another segment, it should be added after the last child of the parent segment.
In you case, you have to add your segment after the E1CUCFG segment.(NOt under that segement)
Regards,
Ravi Kanth Talagana

Error when declaring IDOC segments in program

I am getting error when declaring IDOC segments in my program.
Below is how I declared.
data: wa_e1vfkonk like e1vfkonk.
For the same syntax few segments are showing as properly declared and few are showing error that 'eqvfkonk' does not exist.
How ever this structure does exist when i check it.
Help appreciated.

Hi Prasad,
I think the segment that you are declaring in the program doesn't exist in SAP system as standard.
Maybe you mean E1VFKONX, finishing with "X" instead "K"?
Reward points if useful.
Roger

Collect causes segmentation fault when profiling L2 data cache misses on T1

I am attempting to profile L2 data cache misses on a SUN T1000 server, but collect causes a segmentation fault when I choose to profile L2 data cache misses.
Is it possible to profile L2 data misses on the T1 processor?
Thanks!
-John
A simple hello world application and the failed profiling:
%] collect -p +on -h ecdm hello
Segmentation fault
I compiled with
CC -xhwcprof -xdebugformat=dwarf -g -03 -o hello hello.c

No it is not possible to profile L2 cache misses -- the chip does not generate
interrupts on performance register 0 (only register 1, which is hard-wired
to instruction count).
That said, we should not generate a segmentation fault. Exactly
which version of collect are you using? We did patch Studio 11
to correctly handle the US-T1, and Studio 12 express also
correctly handles it.
Is the SEGV on the collect command, or on the target it launches?
Marty Itzkowitz,
Project Lead, Sun Studio Analyzer

IDoc segment not reaching XI

Hi,
I have a peculiar problem where the values populated in an IDoc segment are not coming to XI, though the values are visible in the sender SAP system, they are not present in the IDoc XML generated in XI.
Please help if someone faced a similar problem.
Thanks
Pushpinder

Hi,
Check if problems are raised on Cache of Design side of your IB.
Environment - Cache Status Overview
Then "Clear Data Cache".
And try again.
Regards,
Giuseppe

Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

Hi All,
have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax . Idocs are getting failed .
If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
The error message in we05 as below
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
This error can have several reasons:
The segment Z1LFA1M is assigned to a group whose header segment does not occur.
The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
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.
Procedure
Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
Thanks

Hi,
I don`t understand what do you mean release after adding segment.
Message type works i.e. Idoc get posted if I send with the vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
Regards

IDOC Segment missing when reaching to ECC

Similar Messages

Maybe you are looking for