IDX2 and EDI_DC40

Hi all,
There is one IDoc imported in "imported objects" of one software component in IR. The IDoc metadata also has been imported in IDX2. However the nodes "IDOC" (with the attribute 'BEGIN') and "EDI_DC40" seen in IR are not visible when I check the metadata details in IDX2. The remaining IDoc nodes and their children are present at both places.
Is this expected or something is missing ?
--Shankar

>>Is this expected or something is missing ?
It is normal behavior.. You can only view the basic structure/segment of the IDoc in IDX2.
The EDI_DC40 segment is a generic segment that is attached to every IDoc type created and hence it is not added as a part of the metadata(as in known implicitly).
However it may be required to change/map any values to the EDI_DC40 segment fields and so it is made visible in the IR to be used by the mapping program.
Hope this clarifys why this segement is included in IR and excluded in IDX2.
Thanks
SaNv...

Similar Messages

EDIDC and EDI_DC40

Hi Experts
what is the gap between EDIDC and EDI_DC40. All outbound idocs from my sap system contains the control records in EDIDC rather i want to have it in the format EDI_DC40 because based on EDI_DC40 mapping is performed. How to find the gap between EDIDC and EDI_DC40 and fix it up by populating appropriate data in EDI_DC40 from the outbound side (r3) ?
thkx
Edited by: Prabhu S on Mar 11, 2008 2:58 PM

Hi,
All the idoc header information is stored in the dictionary table EDIDC that is controle information for idoc it contains all the information like
1>who is sender.
2>who is receiver
3>which is the message type
4>between which logcal system
5>in which port idoc to be send to receiving ligical system
6>what is idocid
all information are stored in this table
that port what you created by the transaction WE21 that port you have to assign here
Probably this kind of mapping will help you
WA_EDIDC-MANDT = SY-MANDT.
WA_EDIDC-MESTYP = 'ZMSG_TYP'.
WA_EDIDC-IDOCTP = 'ZIDOC_TYP'.
wa_edidc-cimtyp = c_temp.
WA_EDIDC-RCVPRN = '<Port>'.
WA_EDIDC-RCVPRT = 'LS'.
WA_EDIDC-CREDAT = SY-DATUM.
WA_EDIDC-CRETIM = SY-UZEIT.
append wa_edidc to it_edidc.
This information you could compare with teh structure of EDI_DC40
Following links may help you-
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
/people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
Thanks
Swarup

Regarding IDX1,IDX2 and WE20

Hi Masters,
while doing file to idoc scenerio i have little bit of confusion ..
1) In idx1 we have to create a idoc port.. in case of port tab wht we have to give .. either we have to give logical system name of xi server or any other .. name ..
2) In idx2 we have to load the metadata .. here also we have to give source port .. so here also we have to give logical system name of xi server or any other name ..
3) In case of maintaining partner profile .. we have to give partner number.. so here also we have to give logical system name of xi server or other name ... this we have to do in r3 system ..
please help for doing this process ... if possible can u provide a step by step process for maintaining idx1,idx2 and we20...
Thanks in Advance,
jagannath.

Hi,
Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Regards
Santhosh
Remember to set the thread to solved when you have received a solution

IDX2 and it gives me I::000 error

Hi All,
I am trying to import metadata using the IDX2 and it gives me I::000 error. I have checked the authorizations for the user RFCUSER on R/3 and it has
SAP_ALL
SAP_NEW
I am not sure where can I check the log which can show me where could be the problem...
Kind Regards,
Praveen.

Hi Praveen,
Check if these threads give you some inputs:
I::000 error in IDOC to IDOC scenario
::000 message no. SR053
Regards,
ravi

IDX2 and table IDXEDSAPPL

Hello,
I loaded an Idoc into IDX2 from SAP system. This is a Z Idoc. Subsequently, I did some changes to the segments fields in the Idoc. Initially segment had 28 fileds but I deleted 5. I re-loaded the metadata into IDX2 (delete and created). But table IDXEDSAPPL is not reflecting the correct fields in the swgment. I shows 28, the first 23 are correct and last 5 are from the earlier version of Idoc.
It looks cache issue to me.. any idea that where the problem lies.
Thanks, Dehra

Hi Dehra.
i think that you can use this report: IDX_RESET_METADATA.
This document may be helpful:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290">How to handle caches in SAP XI 3.0</a>
Hope this help
Francesco

IDX2 and Idoc metadata in production system

As explained my Michal & SAP note - 767091, I ran program IDX_GET_CONFIG in production, pointed rfc dest to source where the config is located. It loaded the data but the metadata in the tables are pointing to the XI development (DEV) target system port and not production (PRD)landscape....meaning
XI0 sending data to SAPDEV port
XC0 sending data to SAPTST port
XP0 sending Idoc data to SAPPRD port
Now all my entries in xp0 is pointing to SAPDEV port
How do I fix this. I don't want to create a SAPPRD port in XI0 and load metadata from SAPPRD into Xi0...its would not be SOX complaint.
IDoc Adapter: Configuration Data Transfer
 17 Entries for table IDXSLOAD
 0 Entries for table IDXIDOCINB
 1 Entries for table IDXNOALE
 0 Entries for table IDXQUEUE
 9 Entries for table IDXPORSM59
 492 Entries for table IDXIDOCSYN
Please Help!
 4470 Entries for table IDXEDSAPPL
 636 Entries for table IDXEDISDEF

hi,
just like I said you need to do it manually
I gave you note 767091 just to consider
(the note is for system copy not for DEV-PRD)
also Naveen told you the same
you only need to be careful and read what we write
now just delete IDX1 entries in PRD and create new
manually - just like we said
Regards,
michal

PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario

Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards

>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

XI 3.0 and ECC 5.0 IDoc definitions

We use XI 3.0 fo extensive integration with SAP. We recently upgraded from 4.7 ES 2.00 to ECC 5.0. The problem is that all IDoc developments we do now, is recorded as version 640, but XI still thinks the system runs on WAS 620. XI still uses the "old" 620 IDoc definitions missing all the new developments. There is no installed product entry for the new ECC 5.0 in XI. I assume one has to import new application components into XI so that XI is now also aware of ECC 5.0? Is this true and if so, where would we get those new components?
Thanks for the help.

Hi Johan,
- if then new IDOCs have new signatures (some new fields) you can import them again in Repository and use the new ones in all mappings/message interfaces etc.
- also try removing old definitions (idoc metadata) in TCODE IDX2 - and upload new
(you don't have to do it because it should upload when you first you the new IDOC type but...
you can try doing it to see if you got the new IDOC definition)
IDX2:
- click Create
- specify idoc type and RFC port to your ecc 5.0
- and check if this is the idoc type taht you want
BTW you specify RFC port for loading idoc metadata in IDX1
- you can also set SAP release parameter in IDOC communication channels
Regards,
michal
Message was edited by: Michal Krawczyk

IDoc and Message Mapping

Hi,
I have a question.
In a idoc to file scenario,idoc as a sender,.If the idoc is updated in r/3 system due to some change request after we finish the mesage mapping,what steps need to be followed to ensure the correct mapping.
Do we need to change the mapping.
Regards,
Haritha

Hello,
if just the values of your IDoc changed you don't have to change
your message mapping.
If the structure has changed you have to reload the metadata (idx2)
and the IDoc in your Repository and then update your message mapping with reloading your IDoc.
Regards
Patrick

IDX2 IDoc Metadata issue

Hello,
We have created an IDoc and imported it in our XI system,it worked fine.
Then we changed the length of a field and reimported this IDoc,deleted the metadata in IDX2 and it is fine in development system.
The metadata is exactly same as the latest version of IDoc.
However,when we imported the same in our test system,in IDX2, for metadata,we can see this changed field appears two times,one with the old length and other with the changed length.
What could be the reason for this?
Has anybody encountered this problem?Kindly let us know.
Thanks.
Regards,
Shweta

Hi Rajesh,
We tried to delete the metadata using transaction IDX2 a number of times but every time it gets created with twice occurence of this field.
Also,this is fine in dev system and test R/3 system.
Problem only exists in test XI system.
We tried transporting again as well,but no luck.
Here,new changes are being picked up but older changes are not removed ,so we can see both versions for this field.
Any other areas to check?
Thanks.
Regards,
Shweta

Idoc from XI to R3 losing fields and segments

The idocs I have posted from XI to R3 seem to lose some of the fields and segments.
The idoc is sent correctly from XI but the idoc posted in R3 have less fields and segments.
Any idea?
Thanks

Hi,
Check in transaction IDX2. You may need to delete the Idoc Type Metadata from IDX2 and then resend your XML file to XI. It will then generate the new metadata.
Also, there was once when we encountered this case but simply deleting it from IDX2 did not fix the problem. We then deleted the entry directly from the table IDXEDSAPPL and that fixed the problem.
You may also want to refresh your XI cache via tcode SXI_CACHE.
Thank you.
Best regards.

IDX2 doens't refresh IDoc structure

Hello everybody,
I have a problem with the IDX2. There is a Z IDoc which has changed. So I deleted the old entry in the IDX2 and load it again from the system. But the structure is not refreshed. I tryed to load it from another XI System (the development XI and not the quality XI) but from the same R/3 backend. And there the structure is refreshed. So it seems to be a problem of the XI and not the R/3 backend.
We are on NW04s SPS 13.
Did anybody know this problem and can help me.
Thanks

Hi,
Following two should solve your problem:
Goto IDX1 edit port and then save it again it will refresh connection b/w R/3 and XI.
Goto IDX2 delete metadata and import Idoc again.
You can also refer to note: 907957 (not sure as you are already on higher patch)
Regards,
Gourav
Reward points if it helps you

What are the steps XI development? What is IDX1, IDX2, IDX5 used for?

What are the steps XI development? What is IDX1, IDX2, IDX5 used for?

Hey
there are mainly two categories of steps
in Integration Repository
data Types
message Types
message interface
Message mapping
Interface mappin
in Integration directory
sender and receiver communication channel
sender/receiver agreement
recever determination
interface determination
IDX1,IDX2 and IDX5 etc are transaction codes used in IDOC scenarios for port,partner profile and IDOC metadata
thanx
ahmad
Message was edited by:
Ahmad

Can't delete Metadata in IDX2

Hi well i want to reload the metadate of an IDoc because Structure has changed.
But when i delete it, it is gone and when i want to re-import it i am told that the metadata is already imported.
Well, i jumped out of IDX2, reselect IDX2 and the metadata are back even though i have deleted them.
I already did a complete cache-refresh.....
Any ideas what to do?!
br

Hi -
Based on what you described, it sounds like you're doing what's necessary.
Other options:
1. Delete all the idoc types within the relevant IDoc port. Then delete and recreate the idoc port and reimport the metadata (or let it populate itself at runtime). But it's always good practice to reimport the metadata to validate the connection.
2. Use report IDX_RESET_METADATA to delete the metadata (more info Note 934430).
Regards,
Jin

IDoc to multiple receivers...

Hi All,
(This is an IDoc to IDoc scenario)
I am working on a scenario where I need to send a mapped IDoc to four local folders. (The local folders are for archived copies of the IDoc and for pick up by third party systems. We are not concerned with the IDocs after deposit in the folders) The key is to have 4 identical copies of the IDoc in 4 different folders after mapping through PI. This is not for xml versions of the IDoc, this is for the flat text version of the IDoc.
I have already mapped the IDoc and have also taken care of the 1:N issue on the outbound IDoc. What is the best way to get 4 copies of the mapped IDoc to four different folders? Couldn't seem to find a definitive answer anywhere!
Thanks!
Don

Hi Ravi,
I am sending PAYEXT.PEXR2002.PEXR2002 and the payload confirms this as below:
<IDOCTYP>PEXR2002</IDOCTYP>
<CIMTYP>PEXR2002</CIMTYP>
<MESTYP>PAYEXT</MESTYP>
<STDMES>PAYEXT</STDMES>
<SNDPOR>SAPDEV</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>DEVCLNT400</SNDPRN>
<RCVPOR>PIDDEV100</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>SAPXI</RCVPRN>
<CREDAT>20110707</CREDAT>
<CRETIM>150248</CRETIM>
<SERIAL>20110420145801</SERIAL>
</EDI_DC40>
- <E1IDKU1 SEGMENT="1">
<BGMTYP>PEX</BGMTYP>
<BGMNAME>EXTENDED PAYMENT ORDER</BGMNAME>
I will delete the metadata again in IDX2 and re-load. Is there anything else you can think of or may need from me in order to diagnose/resolve the issue? Thanks in advance for your help thus far!
Donald

IDX2 and EDI_DC40

Similar Messages

Maybe you are looking for