IDOC Scenario Error: External segment cannot be interpreted.

Hello Experts,
We have developed a scenario wherin ECC6 s/m sends a customized IDOC ZRESREVIDOC to PI 7.0 client 100.
On processing the IDOC in ECC6 the IDOC status is 03 (Idoc has been sent successfully) whereas in PI 7.0 WE05 transaction shows an error on this record that "56 - External segment ZRESREV000 cannot be interpreted". There are no records in SXMB_MONI however.
We have checked our ALE settings for RFC destination, port with client 100 etc on both ends. Also we have aleady imported the IDOC metadata in IDX2 of PI7.0. The configuration objects are also done in ID & IR.
Pls advice.
Thanks in advance,
Elizabeth.

Hi
-->Check the Port which you had created in your PI system it should follow the naming convention like SAP+System id of ECC,and also check the RFC destination and client and logical system name which you had maintained in IDX1 t-code.
-->Once Re import your Idoc meta data in IDX2 and also check RFC destination in PI system.
Thanks

Similar Messages

File to IDOC scenario error...

Hi all,
we hhave created an File to Idoc scenario .
we are getting the following error in SXMB_MONI t-code.
<?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_INV_SND_SERV</SAP:Code>
<SAP:P1>BUS_SENDER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service BUS_SENDER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
can any one plz say wat this error might be..
TIA
Regards,
Raj

Hi,
The problem occurs when sender and receiver business system or business service does not have a logical system name.
ID - Integration Directory
Posting the IDOC'S into SAP R/3 System, sender and receiver business system or business service requires the logical system name. If the business system (Web As ABAP) does not have the logical system name, then add the logical system for business system.
If business system type = Web AS ABAP, then add the Logical system in Technical System level and Save.
If business system type = Third-Party, then add the logical system in business system level and Save.
If the business service does not have the logical system name in ID, it needs to be configured as follows.
Go to ID and click the Business service -> Services -> Adapter Specific Identifiers. Enter the logical system name and Save.
Apply and activate.
hope this will help you.
regards
Aashish Sinha
PS : reward points if helpful

File to IDOC scenario : Error with mapping due to Context handling

Hi Experts.
I have a file to IDOC scenario which need your advice.
Source File structure as follows:
Control_Header <1:1>
Invoice_Header <1:unbounded)
Invoice_Line <1:unbounded)
Trailer <1:1>
Payload as follows capture from SXMB_MONI
- <Control_Header>
 <Key>999</Key>
 <TransactionID>RCTV</TransactionID>
</Control_Header>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB05</BusinessUnit>
 <InvoiceNo>64471</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>7.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.49</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>8.00000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>0.56</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Invoice_Header>
 <Key>000</Key>
 <BusinessUnit>HDB21</BusinessUnit>
 <InvoiceNo>6Y0575</InvoiceNo>
</Invoice_Header>
- <Invoice_Line>
 <Key>001</Key>
 <UnitPrice>49.50000</UnitPrice>
 <Quantity>1.0000</Quantity>
 <GSTAmount>3.47</GSTAmount>
 <GSTRate>0.07</GSTRate>
</Invoice_Line>
- <Trailer>
 <Key>TRL</Key>
 <TransactionID>RCTV</TransactionID>
 <TotalFeedLine>96</TotalFeedLine>
 <HashTotalValue>212.00</HashTotalValue>
</Trailer>
</ns:MT_EINVOICE>
Mapping as follow:
 IDOC
<Control_Header> -> <Control_Header>
<Invoice_Header> --> <Header_Invoice>
<Invoice_Line> ---> removeContext --> <Line_Invoice> this is the child node of <Header_Invoice>
<Trailer> -
> <Trailer>
The result of the using the above Payload get the following result which not wht I seek
<Control_Header>
<Header_Invoice>
 <Line_Invoice>
 <Line_Invoice>
 <Line_Invoice> *** This belong to the Invoice_Line of the second <Header_Invoice> at the payload
<Header_Invoice>
 <Line_Invoice> *** THis segment is empty
<Trailer>
I required the Line_Invoice to belong to the child of the second <Header_Invoice>, I have tried using
removecontext with splitVaue and collaspeContext but to no avail.
May I know what is my mistake on the mapping of the Invoice_Line to Line_Invoice>
Rgds
FNG

Hello,
There should be something that could correlate the Invoice_Header/Key and Invoice_Line/Key. In your example, both are the same for the first and data set. If the sample looks like the one below, it is possible to sort things by correlating the Invoice_Header key and Invoice_Line key
<Invoice_Header>
<Key>000<Key>
</Invoice_Header>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Line>
<Key>000<Key>
</Invoice_Line>
<Invoice_Header>
<Key>001<Key>
</Invoice_Header>
<Invoice_Line>
<Key>001<Key>
</Invoice_Line>
An example mapping could look like this
For Header
Invoice_Header --> Header_Invoice
For Line
/InvoiceLine/Key --> removeContext --> splitByValue:valueChanged --> Invoice_Line
The subfields of the invoice line would also follow a similar logic, you just need to use formatByExample --> splitByValue:eachValue so that the context levels are the same.
Hope this helps,
Mark

Error : External ID cannot be used; it has already been used .

Hi ,
Sometime the following senario happend the user delete and want to recreate with the same Marketing Element ID
If we create a Marketing Element with a ID, and Delete it , and after recreate it with the same ID .
SAP issue the following message : Details External ID cannot be used; it has already been used .
Did somebody find an solution ?

Hi Christophe,
we face the same problem. Do you have a solution?
Best regards,
John

File to idoc scenario error - not working yet :(

Hello! I'm trying to make changes in business partner record in CRM using idoc CRMXIF_PARTNER_SAVE_M01
I have an error 56 EDI: Partner profile not available.
In Control record in we02 transaction, I have right Partner number for Recipient information - logical system name like CRM has in SLD. But there is no Port.
In Sender information I have right Partner number, like my filesystem business system has in SLD and have a port SAPP1D - but I have nowhere entered it!
And one more little question. In we20 transaction am entering inbound parameters for partner:
CRMXIF_PARTNER_SAVE
CRMXIF_PARTNER_SAVE_M
1) Is this right inbound parameters for my idoc?
2) What Process code should I use ?

Hi,
in XI in IDX1 transaction, maintain a port for CRM system specifying the CRM port and the client and the RFC destination from XI to CRM system.......moreover if you are using apply control record values from payload option in reciver IDOC comm channel, then in the IDOC control record in msg mapping map the sender port to CRM port, partner number as logical system of CRM ie C2DCLNT100 and partner type as LS..........then when you will re-run your scenario, your IDOC will have CRM port also in the control record..........
in CRM system your WE20 for LS for XI should have as an inbound parameter your IDOC - which i think you have already done.........
One more thing - put everything in uppercase letters everywhere in msg mapping in control record data, in we20 setting etc.
Regards,
Rajeev Gupta

External segment name E2LFA1M002 cannot be interpreted

Dear All,
I am sending IDoc from SAP R/3 to XI.In SAP R/3 (WE02) it shows IDoc with status 03 but when i check it in XI(WE02) it shows Status 56 and 60 with Error
56-External segment name E2LFA1M002 cannot be interpreted
60-Basic type CREMDM04 does not exist
I am sending CREMDM04 IDoc type with CREMDM Message type.
Thanks,
RP

Yes
we have loaded Meta data in IDx2
Port in IDx1
it says IDoc with Error Added
and gives above error
-RP

File to IDoc scenario( Bypass)-- Error ( Segment is missing) -- urgent pls.

Hi All,
I am doing File to IDoc scenario( Bypass) for Orders05.
File is picking succesfully and not posting the idoc in the SAP..
My source file(idoc-xml) consists of all the required data to post the idoc including the segment 'E1EDK01'.
but the error it is showing is " Obligatory node 'E1EDK01' missing in the structure ORDERS05 "
Please suggest me ASAP what is going wrong .
Thanks in Advance.
Regards
Seema.

The source File is not the idoc XML. It is invalid. You might need to ask the source to change the XML or use a Mapping to do this.
This is how it should look, ( check the parts in bold),
<?xml version="1.0"?>
<ORDERS05>
<IDOC BEGIN ="1">
<EDI_DC40 SEGMENT="EDI_DC40">
<DOCNUM>1</DOCNUM>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<CIMTYP></CIMTYP>
<MESTYP>ORDERS</MESTYP>
<SNDPOR>XXXXXXXXX</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC></SNDPFC>
<SNDPRN>XXXXXXXX</SNDPRN>
<RCVPOR>XXXXXX</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPFC></RCVPFC>
<RCVPRN>XXXXXXXX</RCVPRN>
<CREDAT>20070511</CREDAT>
<CRETIM>152803</CRETIM>
</EDI_DC40>
<E1EDK01 SEGMENT = "1"><BELNR>AAAAAAAAA123</BELNR>
</E1EDK01SEGMENT = "1">
<E1EDKA1 ><PARVW>EK</PARVW> <ILNNR>231654845121</ILNNR>
</E1EDKA1>
<E1EDKA1 SEGMENT = "1"><PARVW>LF</PARVW>
<NAME1>international</NAME1>
<NAME2>Delhi</NAME2>
<ILNNR>2121211545</ILNNR>
</E1EDKA1><E1EDK02 SEGMENT = "1"><QUALF>001</QUALF>
<BELNR>AAAAAAAAA123</BELNR>
</E1EDK02><E1EDK02 SEGMENT = "1"><QUALF>002</QUALF>
<BELNR>AAAAAAAAA123</BELNR>
</E1EDK02><E1EDP01><POSEX>45</POSEX>
<E1EDP19 SEGMENT = "1"><QUALF>001</QUALF>
<IDTNR>00000000002150059</IDTNR>
<KTEXT>Reddy</KTEXT>
</E1EDP19><E1EDP19>
<QUALF>003</QUALF>
<IDTNR>5484218521214</IDTNR>
</E1EDP19></E1EDP01>
</IDOC></ORDERS05>
Regards
Bhavesh
PS : You need to add SEGMENT = "1" for every segment. Please do add it if I have missed in the XML above.

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.

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

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

Error status 26:Syntax error in IDoc (segment cannot be identified)

Hi Experts,
i extended one idoc which has the following structure
                           A(this is the parent segment)
                                z1
                                    zz1.1
                                    zz1.2
                                    zz1.3
                                    zz1.4
                                e1
                                e2
                                    z2
                                       zz2.1
                                       zz2.2
                                       zz2.3
                                       zz2.4
I am using an user exit for populating the custom segment. values are getting poppulated.
My problem is all segments are coming in the same level. like below
A
z1
zz1.1
zz1.2
zz1.3
zz1.4
e1
e2
z2
zz2.1
zz2.2
zz2.3
zz2.4
Diagonsis of error.:
The segment Z1BPAD1VL does not occur at the current level of the basic type CREMAS05 (extension ZCREMAS05).
This error can have several reasons:
The segment Z1BPAD1VL is assigned to a group whose header segment does not occur.
The segment Z1BPAD1VL does not exist in the syntax description of the basic type CREMAS05 (extension ZCREMAS05).
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.
i have maintained we81 and we82. partner configuration in we20 is also maintained..
What might be the problem??pointers on this will be very helpful.
Regards
Sridevi S

Hi,
>check whether all the parent segments are filled before child segments .
>check the heirarchy level you r passing for each segment.
Regards,
Lokeswari.

Issues in IDoc Sender Scenario:IDoc with errors added

Hi all
Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
status 56 : External segment name E2KOMG003 cannot be interpreted
status 60 : Basic IDoc type COND_A03 could not be found.
And the segments displayed in data record are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
Would any one help in resolving the issue.
Thanks,
Chilanka

Hi,
>>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
no you cannot create any partner profiles in XI
for more about IDOC configuration in XI check :
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

IDoc to File Scenario Error ( IS - Retail )

Hi all ,
I was trying scenario IDoc (SAP ECC 6.0) (IS-Retail) to File scenario .
When i trigerred IDoc from ECC system , it's showing sent successfully to external system or program.
But the problem is it's not coming inside XI sxmb_moni .
I have checked the ALE Configuration and SLD configuration .
Everything is fine.
When i run the TCODE WE05 for IDocs List in XI , it's getting stucked there and the Error showing is
"IDoc: 0000000000000028 Status: IDoc with errors added
External segment name E2WBB01003 cannot be interpreted "
Even i tried with other IDoc WPDWGR it is showing the same error
"IDoc: 0000000000000029 Status: IDoc with errors added
External segment name E2WPW01 cannot be interpreted"

Hi Ashwin,
Please check :
1.The SAP system from which you want to import the IDocs contains function modules for calling metadata.
2.You can import IDocs from SAP Release 4.0 and higher.Support Packages Required for IDoc Imports:
Release    Minimum Support Package Requirement
40B                   SAPKH40B48
45B                   SAPKH45B26
46A                   SAPKB46A20
46B                   SAPKB46B12
46C                   SAPKB46C05
3.check for the authorizations required to import.
Also see SAP Notes 677732 (authorizations), 672745 (missing function modules), 212011 (access to IDoc metadata), and 718320.
check http://help.sap.com/saphelp_nw04/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htm
*Pls: Reward points if helpful*
Regards,
Jyoti

IDOC scenario: MATMAS02 (Application document not posted ALE/EDI errors)

Hi!
I am almost ready with with my first File to Idoc scenario and having the following error.
(Idoc of type MATMAS.MATMAS02)
The IDOC will be received on business system B.
Unfortunately the following errors come in tcode BD87 or MM90
Enter a material type
Message no. M3098
No material number transferred
Message no. M3752
Can some one help me to trace and solve this problem?
Thank you very much!
regards
Holger

Hi!
I corrected the error!
Now the Idoc has the status "yellow" which mean "IDOC ready to be transformed to application".
Is that still an error/warning or is everything is ok?
I mean does some background job started and create a material from this IDoc?
I loooked into tcode MM03 and cannot unfortunately detect any new materials....
kein Filtern , kein Umsetzen , kein Versionswandel .
Message no. B1005
In Log I could find:
IDoc successfully processed in the ALE layer
The IDoc has passed through the ALE layer successfully and can now be passed to the application. This transfer is either done online or as a background job, depending on the settings in the partner profile.
If there are no further status records, the IDoc waits for the next run of the transfer report to the application.
Success or failure when passing the IDoc to the application is documented in the subsequent status records.
Actions in the ALE layer
The parameter 'kein Filtern' indicates whether the processing in the ALE layer led to segments of the inbound IDoc being omitted. The important criteria here are the settings in the segment filter and in the distribution model for this sender.
The parameter 'kein Umsetzen' indicates whether field values were converted in the ALE layer. This is the case if the IDoc contains organizational units to be converted, or if the ALE conversion tool for this sender is activated.
The parameter 'kein Versionswandel' indicates whether the IDoc was converted into an earlier version of the IDoc type. This happens if the IDoc type of the sender is different from its own IDoc type.
Holger

IDOC Scenario Error: External segment cannot be interpreted.

Similar Messages

Maybe you are looking for