Idoc conversion

Hi All,
I have an idoc which when passed through a port of file type changes the segment name from E1* to E2*.
When the idoc is passed through another RFC port however the conversion does not take place. There is no conversion rule defined based on the message type. also the message type for both the cases are different.
Could you please tell me what is the difference that when the idoc is passed through file type port it does change the segment name.
The conversion is maintained in the table "EDISDEF".
If this is a configuration issue then please specify the configuration steps
Regards
Bidyut

Made the code changes ..it works

Similar Messages

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

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 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.

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

XML IDOC to Native IDOC Conversion

Hi,
We have a scenario, where we need to convert XML idoc into native idoc and write to a file. I am doing this based on
How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0.
When I first executed the scenario, I was getting the following error
Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.
After including the try-catch block, now i am just getting a blank file without any conversion.
Can anyone help me on this?
Regards,
Ravi

Hi,
It looks to be error in ABAP mapping
To test ABAP mapping in XI use the transaction SXI_MAPPING_TEST after creating a little scenario in the directory.
Or even you could do this with below sample code
Lets create one ABAP mapping class with the method IF_MAPPING~EXECUTE
data: obj type ref to zcl_abap_mapping_test.
data: source type xstring,
result type xstring.
data: param type ref to IF_MAPPING_PARAM,
trace type ref to IF_MAPPING_trace.
create object obj.
try.
CALL METHOD obj->IF_MAPPING~EXECUTE
EXPORTING
SOURCE = source
PARAM = param
TRACE = trace
IMPORTING
RESULT = result.
CATCH CX_MAPPING_FAULT .
ENDTRY.
This is a link very useful for ABAP Mapping :
http://help.sap.com/saphelp_nw04/helpdata/en/86/8280ba12d511d5991b00508b6b8b11/frameset.htm
Or may be think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Thanks
swarup

ALE IDoc Conversion Rule or BADI

Hi,
I'm new to ALE IDoc. I have a requirement to hide some sensitive data field for the HR information when outbound the Idoc.
Example, I need to outbound the IT8 Basic Pay with payscale area etc but not with the basic pay amount. I can convert the basic pay amount to zero when the idoc is being created.
I've searched through some information and found out that there are several ways to achieve it. However, I'm not sure which one is a better way.
Is it using the Conversion Rule (BD62) or using Badi or Idoc Reduction method is better?
Kindly give me some hints as I'm very confuse of which one is the better solution.
Many thanks in advance.

No user exit is needed for conversion rule.
However, you should remember that conversion rules are applied segment fields for a particular message type. So wherever the IDoc message type is used the rule will be applied. If you want to associate the rule for any other condition in addition to message type better to go with a BADI
These are steps to create and apply a conversion rule to a message type:
1. Transaction BD62 - Create conversion rule and assign it to a IDoc segment
2. Transaction BD79 - Define the conversion rule by selecting your field and clicking display button. Once inside you can use various options like set constant to map 0 to the basic pay
3. Finally assign the conversion rule to your message type using BD55
As for BADIs, IDOC_DATA_MAPPER is also suited for your requirement, the method PROCESS, allows you to manipulate your IDoc fields whichever way you want. You get the control record, data records, using which you can restrict your manipulation to specific message type or other conditions
To above post, BADI IDOC_CREATION_CHECK should not be used for mappings/conversions as its specific purpose is to stop creation of an IDoc under required conditions

BD79 Idoc Conversion Rule

Hi,
I have a requirement where I have a Inbound Idoc which has two segments say E1EDP03 and E1EDP20. Both are date fields.
now I want to map date from E1EDP03 if Qualif is Z01 to E1EDP20 using conversion rule.
E1EDP03 (Qualif. Z01) - DATUM -
>>> E1EDP20-EDATU
Is it possible to do this using conversion rule?
Thanks,

Hi Shital ,
Thank U very much for replying to my question.
But when I m trying to create the same , by clicking Use general rule & specifying special conversion routine ZBLNK , it is throwing the following error "Conversion exit ZBLNK does not exist".
Please can u help me out.
Thanks,
Gyanaraj

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

EDI TO IDOC Conversion

Hi,
I need to convert EDI 850 data into IDOC PO data at the same time, it has to be generate 997 automatically using seeburger.
Can anyone help me on this issue. with the steps.
I found some scenarios in Forums but those are not giving clear idea.
Plzz help me on this task.
Thanks,
Singh.

Do you have access to Seeburger documents available with the Seeburger installation CD? There you have a document called FunctionAcknowledgement explaining this scenario very clearly.
Regards,
Prateek

Idoc conversion

Similar Messages

Maybe you are looking for