PI 7.0 settings to avoid IDOC conversion to XML

Hi Experts,
In order to have idoc tunneling in PI 7.0 I know I have to:
--set the parameter in IE: XML_CONVERSION = 2.
--add entry in the exception table IDXIDOCINB using the report IDX_SELECT_IDOCTYP_WITHOUT_IS
Actually performing the 2nd step I can only add idocs from a List.but unfortunately we need to enter idocs out of the list.
Can we extend the list ?
How?
Regards,
Giamma

hi,
>>--set the parameter in IE: XML_CONVERSION = 2.
>>--add entry in the exception table IDXIDOCINB using the report IDX_SELECT_IDOCTYP_WITHOUT_IS
these are completely different things
a) XML_CONVERSION - for tunneling
b) IDX_SELECT_IDOCTYP_WITHOUT_IS - for processing IDOC without XI
(so as normal IDOCs with WE20 etc.)
so first you need to decide that do you want - a) or b)
obviously those 2 parameters are described in my book:
www.sap-press.com/product.cfm?account=&product=H1935
Regards,
Michal Krawczyk

Similar Messages

Idoc conversion rule

Hi,
What is idoc conversion rule? Why we need this?
While upgrading from 4.7 to ECC 6.0 what all precautions need to be taken for the existing standard idocs and custom idocs in the system.
Thanks & Regards,
Soumya.

Hi,
ALE allows the user to perform an SAP transaction in the sending system, after-which the following steps occur:
1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent
These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer
This layer performs an RFC call, using the port definition and an RFC destination determined through the customer model
The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems
If the receiving system is an SAP system then:
In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs
In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. Eg. A PO is loaded on the sending side, yet a SO is created on the receiving system
Master data has another difference:
It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object
If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system
In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.
The Detail as described by SAP
In the output processing one of the function modules of the application creates an IDoc, the so-called master IDoc. This IDoc is sent to the ALE layer where the following processing steps are applied:
Outbound processing
Receiver determination
An IDoc is similar to a normal letter in that it has a sender and a receiver. If the receiver has not been explicitly identified by the application, then the ALE layer uses the customer distribution model to help determine the receivers for the message.
The ALE layer can find out from the model whether any distributed systems should receive the message and, if so, then how many. The result may be that one, several or no receivers at all are found.
For each of the distributed systems that have been ascertained to be receiver systems, the data that is specified by the filter objects in the customer distribution model is selected from the master IDoc. This data is then used to fill an IDoc, and the appropriate system is entered as receiver.
Data selection
Segment filtering
Individual segments can be deleted from the IDoc before dispatch by selecting Functions for the IDoc processing -> Settings for filtering in ALE Customizing. The appropriate setting depends on the sending and receiving logical R/3 System.
Field conversion
Receiver-specific field conversions are defined under Functions for the IDoc processing -> Conversions.
General rules can be specified for field conversions; these are important for converting data fields to exchange information between R/2 and R/3 Systems. For example, the field "plant" can be converted from a 2-character field to a 4-character field.
The conversion is done using general EIS conversion tools (Executive Information System).
Version change
SAP ensures that ALE functions between different R/3 System releases. By changing the IDoc format you can convert message types of different R/3 releases. SAP Development use the following rules when converting existing message types:
Fields may be appended to a segment type;
Segments can be added;
ALE Customizing keeps a record of which version of each message type is in use for each receiver. The correct version of the communication IDoc is created in the ALE output.
The resulting IDocs (it is possible that several IDocs could be created in the receiver determination) are referred to as communication IDocs and are stored in the database. The dispatch control then decides which of these IDocs should be sent immediately. These are passed to the communications layer and are sent either using the transactional Remote Function Call (RFC) or via file interfaces (e.g. for EDI).
If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created. The ALE administrator can use this workflow to process the error.
Inbound processing
After an IDoc has been successfully transmitted to another system, inbound processing is carried out in the receiver system, involving the following steps in the ALE layer:
Segment filtering
Segment filtering functions the same way in inbound processing as in outbound processing.
Field conversion
Specific field conversions are defined in ALE Customizing.
The conversion itself is performed using general conversion tools from the EIS area (Executive Information System).
Generalized rules can be defined. The ALE implementation guide describes how the conversion rules can be specified.
One set of rules is created for each IDoc segment and rules are defined for each segment field.
The rules for converting data fields from an R/2-specific format to an R/3 format can be defined in this way. An example of this R/2 - R/3 conversion is the conversion of the plant field from a 2 character field to a 4 character field.
Data transfer to the application
Input control
When the IDocs have been written to the database, they can be imported by the receiver application.
IDocs can be passed to the application either immediately on arrival or can follow in batch.
You can post an inbound IDoc in three ways:
by calling a function module directly: A function is called that imports the IDoc directly. An error workflow will be started only if an error occurs.
by starting a SAP Business Workflow. A workflow is the sequence of steps to post an IDoc.
by starting a work item A single step performs the IDoc posting.
The standard inbound processing setting is that ALE calls a function module directly. For information about SAP Business Workflow alternatives refer to the online help for ALE programming.

XML IDoc conversion: No known segments identified

Hi all,
am working on a File to IDoc scenario. In runtime, error occurs at Call Adapter phase.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
Can anyone help me in diagnosing.
Thanks,
Chilanka

Hi,
This issue wis not with Mapping.
The issue is that the utout of the mapping does not confirm to the Idoc metadata,
Exactly why I want to look at the output of the mapping.
Regards
Bhavesh

"Settings for material number conversion not found" occurs when ...

After I run an initial load data into the InfoCube 0PUR_C01, I want to check the InfoCube Content by the following path:
RSA1 -> pick up the InfoCube 0PUR_C01, right click it and select Manage -> Get to Content tab -> Click InfoCube Content button -> Deselect all selection, only tick the 1st column checkbox next to 0Material, then hit enter, get a small window titled as "Cancel" with a red STOP msg sysing "Settings for material number conversion not found" with an "Exit" button and a question mark button, click Exit button leads to SAP Easy Access screen, if clicking the question mark button, another window pops up with the msg showed above, click Technical Information button causes the original window short dump and the short dump msg shows below in between two dashed lines:
Runtime Errors         RPERF_ILLEGAL_STATEMENT
Date and Time          11/28/2005 14:43:13
ShrtText
    Statement "CALL SCREEN" is not allowed in this form.
What happened?
    Error in ABAP application program.
    The current ABAP program "SAPLSHL2" had to be terminated because on
    statements could not be executed.
    This is probably due to an error in the ABAP program.
Error analysis
    There is probably an error in the program
    "SAPLSHL2".
    The program was probably called in a conversion exit
    or in a field exit. These are implemented by
    function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or
    USER_EXIT_xxxxx_INPUT.
    Conversion exits are triggered during screen field transports or
    WRITE statements, field exits during field transports from the
    screen to the ABAP/4 program.
    In this connection, the following ABAP/4 statements are not allowed:
    - CALL SCREEN
    - CALL DIALOG
    - CALL TRANSACTION
    - SUBMIT
    - MESSAGE W... and MESSAGE I...
    - COMMIT WORK, ROLLBACK WORK
    - COMMUNICATION RECEIVE
    - STOP
    - REJECT
    - EXIT FROM STEP-LOOP
    Moreover, conversion exits for output conversion
    (implemented by function modules called
    CONVERSION_EXIT_xxxxx_OUTPUT) do not allow
    - MESSAGE E...
    to be used.
Trigger Location of Runtime Error
Program                                 SAPLSHL2
Include                                 LSHL2F19
Row                                     3
Module type                             (FORM)
Module Name                             TECHNISCHE_INFO5
rce Code Extract
e SourceCde
1 ***INCLUDE LSHL2F19 .
2 form technische_info5.
>>   call screen 1900 starting at 5 8.
4 endform.
5
6 &----
7 *&      Form SHRINK_VALUES
8 &----
9 *       text                                                           *
10 ----
11 * --> p1        text
12 * <-- p2        text
13 ----
14 form shrink_values.
15
16   loop at dynpselect.
17     clear checktable.
18     if dynpvaluetab-lowvalue ne space and dynpvaluetab-lowvalue na '*'.
19       move 'EQ' to checktable-op.
20       move dynpvaluetab-lowvalue to checktable-low_value.
21       append checktable.
22     endif.
What could cause the problem by selecting only 0Material when checking the InfoCube 0PUR_C01 content? What does that mean by this STOP msg "Settings for material number conversion not found"?
Thanks

Hi Kevin,
Set the length of 0MATERIAL and change conversion to alpha:
Re: Error Installing 0MATERIAL from Business Content
Best regards,
Eugene

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.

IDOCType PORDCR101 : XML IDoc conversion: No known segments identified

Hello all,
I'm strugling with the mapping to the IDOC create puchase order PORDCR1.PORDCR101.
The source structure for the moment is exactly the same as the target strcuture i.e. our IDOC.
So I would not expect to much problems with this one.
However, when sending the message we get the following error in SXI_MONITOR:
<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:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I also augmented the trace lvl to 3 and got the following in the Trace-part of TC SXI_MONITOR and
suspect it starts to get wrong already in the beginning
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
Trace level="1" type="T">Convert one IDoc</Trace> .
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore segment field: COMP_CODE</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADERX</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADERX</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOADDRVENDOR</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOADDRVENDOR
I already found the four or so other threads on the SDN website about this error and in the mean-time tried them (delete and reload the structure with IDX2, set the begin and segment-attribute to 1, make sure that the segments-names self are also mappend) but to no avail.
We just implemented two other IDOC's (DELVRY03 and WMMBID02) and they arrive at SAP without problmens.
Hope you have form ideas to get me out of this one.
Tnx and best regards.
Bart.

Hi Bart,
We had a similar problem.... It took us 2 days to find out what the problem was... Nothing on SDN was helpfull so far... First we incremented the trace level of XI to see the debug messages... Then we saw that certain segments could not be identified and are ignored, others not...
So further investigation in IDX2 to the specific IDoc with problems showed us a list with all used segments and their versions. Some segments had only 1, others had more versions....
So we could identify the problem as a segment version problem. It seemed that our IDoc Communication Channel took not the most recent version. So we changed the "Segment Version" to the most recent one and the problem was solved!
Please reward points if this was usefull to you...
cheers!
Pedro

XML IDoc conversion: No known segments identified PPCC2PRETTICKET01

Hello to everybody,
I'm working with JDBC adapter to IDOC scenario with standard message PPCC2PRETTICKET01 and I found this message:
IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME
XML IDoc conversion: No known segments identified
I've read previous thread and I've already try to Reimport the Idocs into Repository
and Delete the Idoc metadata from the in Transaction IDX2 and reimport the same.
I'm in SAP NetWeaver 2004s.
Do you have another ideas?
Many thanks

Hi,
I've filled up control record in message mapping, I tried with Apply C R but it doesn't work.
I don't know how to disable EDI_DC40 in message mapping because the fields are red.
I've filled up every segment field with a constant with the right segment name but nothing.
This is the payload after the error but since the JDBC adapter in:
<?xml version="1.0" encoding="UTF-8" ?>
- <PPCC2PRETTICKET01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="EDI_DC40">
<TABNAM>EDI_DC40</TABNAM>
<DIRECT>2</DIRECT>
<IDOCTYP>PPCC2PRETTICKET01</IDOCTYP>
<MESTYP>PPCC2PRETTICKET</MESTYP>
<SNDPOR>SAPXI0</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>XIDEV100</SNDPRN>
<RCVPOR>SAPDEV</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>SYSDEV300</RCVPRN>
</EDI_DC40>
</IDOC>
</PPCC2PRETTICKET01>
Thank for more ideas.
Fabrizio

Send custom error message using IDoc conversion rule?

Hello,
I am using an Idoc conversion rule in BD79 to load cost centers. In my conversion rule I use a conversion exit function module to concatenate 2 specific characters and sending cost center value together and then this output value placed in the receiving cost center field. This works fine, but now I want to send a custom error message to the idoc and fail the idoc if the sending cost center value is greater than 8 digits.
Does anyone know how to send an error message or update an idoc with an error message using a conversion rule (bd79)?
Thank you,
Rhonda

Hi Rhonda,
Any luck on the below.. i have a similar issue...
Sorry to hijack your thread...

XML IDoc conversion: No known segments identified ,only few times

Hi all,
Our scenario is in production and is working fine,few times i get the below error.
This is a Daily run scenario.This week it ran 5 time right and 2 , times it failed to create Idocs for the same sccenario.
Can any one help me.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error

check if these discussions help you:
XML IDoc conversion: No known segments identified
IDOCType PORDCR101 : XML IDoc conversion: No known segments identified
Regards,
Abhishek.

Idoc Conversion rule, Change pointers and Filters

Hi Experts,
Please any one can help me out, i need material or clear picture about Idoc Conversion rule, Change pointers and Filters where we can use these concepts what is the befit for these concepts.
Thanks in advance,
Ramesh.

Hi,
Check this link. It has got some of the tutorials you are looking for.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
Cheers
VJ

Idoc Conversion Rules

Hi all,
Good Morning Friends. I am looking for proper documentation which can help me to understand the concept of <b>Idoc conversion rules</b>. I search a lot in help.sap.com and also google resources, but couldn't figure out any. I am very much interested in comprehending this concept from quite a long time. Can anyone help me to find out good doc's on this concept. If you have any documents you can plz forward them to <b>[email protected]</b>.
Any kind of help will be appreciated and will be awarded points without failing.
Have a nice day !!
Thanks and Regards,
Varun.

HI Ferry LIanto,
Thanks for your immediate reply. I have gone through this. I also want to learn the theoritical aspects behind this concept. Is there any documentation available in help.sap.com regarding this or are there any other resources available to learn this very much in detail ? I have tried rigorously, but couldnt trace any. If possible can you please help me in this regard ?
Thanks and Regards,
Varun.
Message was edited by: varun sonu

Settings for material number conversion not found

"Settings for material number conversion not found"
This is the error that came out. I was everytime i try to access the activated business content 0material, the system comes up with this error. Please help me with this! Thank you!
-Peter

Hi Peter,
try oss note 555675, it tells you to use transaction OMSL.
regards
Siggi
Message was edited by: Siegfried Szameitat

How to get IDOC schema in XML

Please tell me how to get an Idoc schema into XML from SAP.
I want all the details of an Idoc, i.e Segments and fields in one file.
Quick response will be appriciated.
Thanks
Kiran

WE60 enter the IDoc type then menu path Documentation->XML Schema. This may depend on what version of SAP you are on.

HR - XI - External System: one IDOC to multiple XML Files

Hi,
I have a scenario where I need, out of one HRMD_A07 IDOC send multiple XML files:
The IDOC and the XML files can the Master data for many employee (IDOC has max of 200 as of SAP, external system, max of 1000).
The IDOC will be generated with change pointers with all the needed filters (I can add/remove if needed).
My goal is to generate 3 types of XML files:
- 1 for the persons (containing basic info like name, firstname, persnr,etc)
- 1 for the various unit (with basic info of unit like number, description & name)
- 1 for the links between persons and units (this person is linked with that unit)
The structures of the 3 XML files are know and can be imported via XSD definition.
Do I need to use BPM for doing so or is there a way to do that with simple mapping?
If BPM is needed, as I new to that, if you have a link to a begginer guide, fell free to send it
Cheers,
greg

hi,
For your scenario there is no need of BPM.
In message mapping select the message tag.
In the target add 3 message types.
Just map the fields.Go to Interface mapping add the 3 message in the target.
Get the mapping.
In ID sender agreement,Receiver Determination is same.
In Interface Determination select extended.Get the mapping.
Create 3 Receiver agreement for each Receiver.
Regards,
Prakasu

Merging multiple idocs into 1 XML output

Hi Gurus,
I've got a scenario whereby i will need to send payment documents via idocs to XI and XI will output them into an XML file.
At the moment, when i perform a payment run for multiple vendors and send the idocs out, i realised that multiple idocs are being sent out and XI will output multiple XML docs.
Is there any way i can merged these idocs into a single XML document? The idocs are all from the same system.
Thanks in advance.

HI,
I think this is possible using PACKAGING.
Check this note 814393 on Service Market Place.
You want to create or process an XI message with multiple instances of an IDoc (of the same IDoc or extension type) in the mapping.
Please refer below link to follow the steps to Merge IDOCs under single XML,
SAP Network Blog: Collecting IDocs without using BPM
Collecting IDocs without using BPM
IDoc packaging
Reason and Prerequisites
The relevant IDoc is imported into the Integration Repository.
Solution
1) Log on to the Integration Repository.
2) Open the relevant IDoc in the object editor.
3) Select the "Export XSD" menu option in the "Tools" menu.
4) In the subsequent dialog box, assign a file name and save the data to the hard disk of your local PC.
5) Open the file that you have saved in step 4 in an adequate editor (for example, Notepad) for editing.
6) Locate the first entry: <xsd:element name="IDOC" type="<
Idocname>"> and add the following expression, maxOccurs="unbounded", between the value of the type attribute and the closing angular bracket.
Example:
<xsd:element name="IDOC" type="ADR2MAS.ADR2MAS02"
maxOccurs="unbounded">
7) Save the modified file to the hard disk of your local PC.
8) In the message mapping, use the file saved in step 7 instead of the imported IDoc by using the "Import XML or XSD" function in the mapping tool to select the source or target messages.
Thnaks
swarup

PI 7.0 settings to avoid IDOC conversion to XML

Similar Messages

Maybe you are looking for