Error in IDOC Inbox

Hi Abapers,
I'm getting one error in IDOC (inbox),I did't understand that error,
outbox is sucessfully created green light is displayed but inbox is faild,i tried so many times but i did't understand.
it's urgent ........
can anyone plz slove this error .
Regards,
siri.

hi ,
   In idoc status , it was showing that message have been issued,but it was not picked by the external system.
   Actually our requirement is to send a MATMAS to external system (WPS)i.e, webspheres . Actually problem is RFC connection is not establishing , it was showing 'Error in connection'. can u help me how to do RFC to external system.
What I did in RFC connection is, I gave RFC name, Connection type is 'T', In technical system , what we have give , to establish connection.
Actually I send Idoc from R/3 system to External System. I want vice-versa , how to do this connection.
    please help me .....

Similar Messages

Error in Idoc with status 26

Hi,
IDOC showing an error messge when syntex check.
EDI: Syntax error in IDoc (segment cannot be identified)
Diagnosis:
The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
This error can have several reasons:
The segment E1EDP19 is assigned to a group whose header segment does not occur.
The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (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....
Regards,
Sudha

Hi,
I have pasted a portion of my code:
DATA: BEGIN OF GT_EDIDC OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC.
DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
        INCLUDE STRUCTURE EDIDC.
DATA :END OF GT_EDIDC1.
DATA: BEGIN OF GT_EDIDD OCCURS 0.
        INCLUDE STRUCTURE EDIDD.
DATA :END OF GT_EDIDD.
DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
        INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
DATA : END OF GT_Z1ZPSOBJLOC.
* Control Record
FORM BUILD_CONTROL_RECORD .
GT_EDIDC-MESTYP = C_MESTYP.
GT_EDIDC-IDOCTP = C_IDOCTP.
GT_EDIDC-DIRECT = C_1.
APPEND GT_EDIDC.
ENDFORM.                    " built_control_record
*&      Form built_data_record
* Data record
FORM BUILD_DATA_RECORD .
LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
    GT_EDIDD-MANDT = SY-MANDT.
    GT_EDIDD-SEGNAM = C_SEG.
    GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
    APPEND GT_EDIDD .
PERFORM DISTRIBUTE_DATA.
ENDLOOP.
ENDFORM.                    " built_data_record
*&      Form distribute_data
* Distribute Data
FORM DISTRIBUTE_DATA .
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = GT_EDIDC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
      MASTER_IDOC_DATA               = GT_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
CASE SY-SUBRC.
      WHEN 1.
      MESSAGE E004.
    WHEN 2.
      MESSAGE E005.
    WHEN 3.
      MESSAGE E006.
    WHEN 4.
      MESSAGE E007.
    WHEN 5.
      MESSAGE E008.
    WHEN OTHERS.
* Do Nothing
ENDCASE.
COMMIT WORK.
* Clear IDOC data internal table after use
CLEAR GT_EDIDD.
REFRESH GT_EDIDD.
ENDFORM.                    " distribute_data
Hope it proves useful.
Regards,
Gayathri

Error sending Idoc's to SAP

Hi,
I'm getting error in file-XI-SAP scenario. File is read and transformed to Idoc ok, but then I get this kind of error message in SXMB_MONI:
<SAP:Stack>Error: Basic type 'HRMD_A01' is unknown</SAP:Stack>
What I'm I missing in the scenario?

Hi Tapio,
Take a look at this link:
http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
Error: No IDocs could be sent to the SAP BW using RFC.
Hope it helps you.
Cheers,
Chandra

Getting Error in Idoc.

Hi all,
I m getting this error in idoc..
Entry in outbound table not found.
I doc number is generated..
also giving Program code ..check and tell me whr can i do change..
Following is program for idoc...
REPORT ZNA_IDOC .
*TABLES: CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
TABLES : ZNA_ID.
DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control
*Record
KUNNR TYPE ZNA_ID-KUNNR, " SEGMENT ORDER DATA
VBELN TYPE ZNA_ID-VBELN.
*QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
DATA : ZORDER LIKE ZNA_ID OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE. "Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated
"Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZNA_I'.
PARAMETERS : ZID LIKE EDIDC-MESTYP DEFAULT 'ZID', "Message Type
C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS', "Partner type of receiver
C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'D11CLNT100',
C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000009',
C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'A000000008',
C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'D11CLNT210',
C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZNA_IT',
C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'. "Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*& Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = ZID. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
APPEND S_CTRL_REC.
ENDFORM. " generate_control_record
*& Form send_idoc
FORM SEND_IDOC.
*SELECT * FROM ZNA_ID INTO TABLE ZORDER.
ZORDER-KUNNR = '1'.
ZORDER-VBELN = '101'.
**ZORDER-QUANTITY = QUANTITY.
APPEND ZORDER.
T_EDIDD-SEGNAM = C_ZRZSEG1.
T_EDIDD-SDATA = ZORDER.
APPEND T_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
MASTER_IDOC_CONTROL = S_CTRL_REC
TABLES
COMMUNICATION_IDOC_CONTROL = T_COMM_IDOC
MASTER_IDOC_DATA = T_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
IF SY-SUBRC = 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
COMMIT WORK.
LOOP AT T_COMM_IDOC.
WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
ENDLOOP.
ENDIF.
ENDFORM. " send_idoc
thx...

The program is probably correct, however, it seems that you haven't completed the 'customizing' just yet. The parameters entered in S_CTRL_REC contains entries which have not yet been maintained in the settings.
Have a look at the settings. I have no SAP system available right now, so I can't tell you what transaction is needed, but first have look at WE20 (use transaction menu WEDI).

Regarding Getting Error in Idoc .... Outbound table not found

Hello everyone
I am working on ALE/Idoc, at the last i am getting error that idoc has created but cannot be send, I am using XML port (not file) so giving Physical Dictionary, please solve my problem where i have to change. please reply its urgent.
Thanks & Regards
Vimarsh B.

Dear,
The addon is a third party addon which was developed by CitiXSys. so the support is provided by the partner who developed the addon.
Go to the vendor Citixys for further support will give you a quick reply.
Regards
Apple

Error in IDOC generation

Hi Gurus,
I have got an Error in IDOC Processing from other interface.
The IDOC status is 51 and we are using it to create Promotion Deal in
SAP ERP through IDOC from other interface.
The Error i am getting in Status Record is that "Promotion is Duplicated
along with Promotion Deal Number"
I have also checked the Promotion Deal No in VB 33 but it is not existing.
Please could you suggest where is the possible error.
I have also checked the Control Record it is correct.
Awaiting for response.
Thanks,
Sam.
+

Hi,
Reprocess the IDOC by using the T.Code "BD87".
Even if the same error persists,try to change the data manually by using the T.Code "WE19".
Check with the ABAPer for debugging the code.
Regards,
Krishna.

Syntax error in IDoc (too many repetitions of a segment)

Hi,
I tried to load master data from R/3 into BW system. The load is not ending and the IDoc error message is displaying,
The error message is " EDI: Syntax error in IDoc (too many repetitions of a segment) with status 26" .
I tried to analise the issue and checked in the Idoc List Outbox of BW system. I found Red status message with number 26 stating " Error during Syntax check of IDoc (Outbound) and the message type is RSRQST.
Could any one help me out in solving this problem. Reply to the message if any more information needed.
Thanks in Advance.
Regards
Koushik

I'm getting the same error. I think it is because I have a InfoPackage selection routine, that selects more than 1000 select conditions. I guess it is a parameter that needs to be changed somewhere. Any help on this one?
BR
Øyvind

Getting error in idoc FD 008

Hello ,
i am getting an error in idoc which is related with Tax code & Tax rate conversion in EDI . The Message number is FD 008 and message is "Assigning a new tax key for and VAT .000 not possible .
Can anyone please help me what could be possible cause of this error and how can i correct it.

hello,
see if your tax code has a correct value and it is not blank.
best regards,
swanand

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 Status 26: EDI: Syntax error in IDoc (segment cannot be identified).

Hi All,
I have created IDOC extension for IDOC Basic type "PROACT01" and have followed all required necessary steps but getting IDOC
Status 26. EDI: Syntax error in IDoc (segment cannot be identified). The exact error is:
Please check Error Details and the details of the steps I followed for Setting up IDOC Extension:
Error Detail :
EDI: Syntax error in IDoc (segment cannot be identified)
Message no. E0078
Diagnosis
The segment ZPROSEG does not occur at the current level of the basic type PROACT01 (extension PROACTEX).
This error can have several reasons:
The segment ZPROSEG is assigned to a group whose header segment does not occur.
The segment ZPROSEG does not exist in the syntax description of the basic type PROACT01 (extension PROACTEX).
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 PROACT01 (extension PROACTEX).
Can you please look at this problem and suggest what is wrong with IDOC Extension/Custome Segment?
Below is the Details of the Steps which I have followed:
1. Tcode WE31 - Created new custom Segment ZPROSEG with 4 fields. Released segment.
2. TCode WE30 - Created IDOC Extension PROACTEX for Basic Type PROACT01. Released IDOC extension.
Here when I run syntax check warning appears "No predecessors exist". I am not sure if its okay!!
3. TCode WE82 - Added Extension PROACTEX in the Message Type PROACT with BASIC Type PROACT01.
4. TCode WE20 - Added IDOC Extension PROACTEX in the predefined partner profile in WE20 transaction.
5. Added the following code in the Customer Exit EXIT_SAPLWVMI_001 include ZXWVMIU01 .
DATA segnam(27).
READ TABLE dedidd WITH KEY segnam = 'ZPROSEG'.
IF sy-subrc NE 0.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
APPEND dedidd.
ENDLOOP.
ENDIF.
Finally ran transaction WVM2 (Transfer of Stock & Sales Data) to generate IDOC, its creating IDOC but when checked IDOC in WE05 its getting Status Error "26".
Looking forward for your reply.
Many thanks in advance.

Hello,
Actually you are appending the Z segment instead of inserting into the correct position. So the segment is added at the last, so hierarchy of segments is collapsed.
So get the index of the previous segment E1EDP31 and increase the index by 1 and INSERT the Z segment with that new index as below.
LOOP AT dedidd WHERE segnam = 'E1EDP31'.
lv_index = sy-tabix. " <<--
ADD 1 TO lv_index. " <<--
CLEAR dedidd.
dedidd-segnam = 'ZPROSEG'.
zproseg-matnr = 'Mat1'.
zproseg-lgort = '001'.
zproseg-gernr = 'SNo1'.
zproseg-labst = 2.
dedidd-sdata = zproseg.
*APPEND dedidd.
INSERT dedidd INDEX lv_index. " <<---
ENDLOOP.
Here actually we are insering the record inside the LOOP and it regenerates the index again. It is not actually a good practice.
So the best practice is get the index and generate the segment inside the loop, store them into another internal table, come out the loop and insert the Z segments into DEDIDD by looping the new internal table.

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

Getting error saying 'IDoc included in IDoc packet containing an error'.

hi experts
When I am processing idoc in LSMW, getting error saying 'IDoc included in IDoc packet containing an error'.I changed the packet size also but it was not resolved.
Can any one tell me how to resolve this.

Hi,
Check below link......
Getting error 51 saying 'IDoc included in IDoc packet containing an error'
even this link is not solving problem then check the aplication log to get exact error text.
Thanks,
Asit Purbey.

Error in IDOC: XML IDoc conversion: No known segments identified

Hi Team
i am facing error in my scenario. When we are testing my interface, another Interface is picking up the Messages and resulting into an error.
There is no mapping involved in my scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me out
thanx in advance

Hi,
Do The following:
1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
2) Have a look into this SAP Note- 742093
3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
4) If any field which is mandatory in the idoc must not be disabled...take care about it.
Hope this will help you...
Regds,
Pinangshuk.

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

Hi All,
Im facing the below error EDI: Syntax error in IDoc (segment cannot be identified).
And this error is coming only for few idocs rest are getting processed successfully.
Message no. E0078
Diagnosis
The segment E1EDP03 does not occur at the current level of the basic type ORDERS05 (extension ).
This error can have several reasons:
The segment E1EDP03 is assigned to a group whose header segment does not occur.
The segment E1EDP03 does not exist in the syntax description of the basic type ORDERS05 (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.
Procedure
Please check the IDoc or the syntax description of the basic type ORDERS05 (extension ).
Please suugest.
Thanks,
Spandana

Hi,
Is this standard program or custom program?
you might be appending the Z segment instead of inserting it. Always best practice is get the index of the segment and instert it.
If all the data is not populated then segment position will change incase of appending. Please check your code and revert back.
Refer the below link for detailed information.
IDOC Status 26: EDI: Syntax error in IDoc (segment cannot be identified).
Thank you

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.

Error in IDOC Inbox

Similar Messages

Maybe you are looking for