Refresh Idoc Metadata in PI 7.31 Java Only

Hello experts,
We are facing issue to refresh the Idoc metadata every time when we change Idoc structure in ECC for Idoc outbound scenario.
We have imported the latest Idoc structure in ESR and assigned that to MM,OM and IFolw. Still in message monitoring we can see the old Idoc structure.
Is there anywhere else to import Idoc metadata like it used to be in Dual Stack idx2 ??
Regards,
Suman

Hi Suman,
If you are new with Idoc in PI you try with the sap.help documentation: http://help.sap.com/saphelp_nw73ehp1/helpdata/en/50/980951964146f1a7f189b411796bae/content.htm
Regards

Similar Messages

Calling IDoc structure from IDOC metadata into Java mapping.

Hi All,
I have a requirement where we need to post an IDOC on target side, We are having to go for a Java Mapping ,so I need to create a Target XML with IDOC Structure, So i need to understand if we could import the structure from IDOC Meta Data in to the Java Mapping insted of creating the IDOC Structure, I am using DOM parser for my Java Mapping,
Really appreciate your response in this regard.
Best Regards
Jayaram

Hi Jayram,
In your requirement, get the xsd format of the idoc from idoc structure and using String xsdFormat ="xsd retrieved"; in the java mapping, you can create the xml structure using DOM parse APIs and then you can put values into the structure and pass it.
Thanks,
RK

Problem in importing idoc metadata

Hi all,
i have problem in loading metadata in idx2. idoc details are AFS/ORDERS05/ZADIORDCONF port: SAPAGS client 003 . i could see an idoc metadata with name ORDERS05 under the corresponding sap system (SAPAGS with client 003) but with out any extension.
now i tried to create another with idoc type : ORDERS05
Extension: ZADIORDCONF
and Source port:SAPAGS
it is giving error msg Extension ZADIORDCONF is not assigned to basic type OREDERS05.
wat could be the reason , please help to solve it
Thanks and Regards
Jhansi

Hi,
There is no need to add anything to idx2. You could delete the existing metadata from idx2 and reimport it.
In some cases even this would not work. In that case, you could refresh the entire metadata by running report IDX_RESET_METADATA. However, use this report only if the above option does not work, since this report will reset your entire metadata.
Thanks,
Bhavish
Reward points if comments helpful

Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

Hi specialists
I'm trying to send an IDoc to our new PI 7.4 Java Only.
Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.
Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:
The IDoc Destination <blabla> was changed. Refresh the destination instance with
Meldungsnr. SR053
Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.
Thanks a lot in advance for any hints.
Renaud

Hi Iñaki
Great document btw... didn't stumble uppon this before. Thanks.
I carefully went through it but nothing I tried helped.
The RFC destination (PI -> ERP) is working fine.
The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.
BUT still: sending an IDoc from ERP to PI fails with this message in SM58:
The IDoc Destination <destinationName> was changed. Refresh the destination instance with
Meldungsnr. SR053
This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".
So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...
Best regards
Renaud

"IDOC Metadata not Found" - Error with Business Connnector 4.7

I have been trying to get our 4.7 installation of Business Connector going after having all kinds of issues getting 3.5 to run as a service on Windows Server 2003.
I believe I am just about able to succesfully load the Idocs as I did in 3.5. However, when it gets to the inboundProcess step, I get an error saying "The IDOC Metadata for ORDERS05 is not available." I seem to be stuck at this point.
If anyone has any ideas on what I can do to get around this or fix this issue, I would really appreciate it. I am trying to load these IDOCS via ALE and I am getting this error just after the OutBoundProcess (ALE.java) step.
Thanks for any help you can give.
Damon Hicks

Hi,
Did you configure the Tc.IDX2.
See the below link
http://help.sap.com/saphelp_nw2004s/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/content.htm
Regards
Chilla

BCExeption: The IDOC metadata for null is not available in SID

<h3>Hello Guys,</h3>
we need some information about the error message:
com.wm.pkg.sap.BCExeption: The IDOC metadata for null is not available in <SID>
We use a Business Connector 4.8 and the backend is an ECC 6.0, we have an inbound xml scenario with FTP.
We pick up the ORDRSP from the vendors ftp-server and we would like to drop it to our backend system.
We can read the xml file into a string, but not send to the backend system, we use following steps:
- bytesToString
- stringToDocument
- documentToRecord
- recordToIDOC
- lockSession
- createTID
so far works perfekt
- sendIDoc
- releaseSession
On the step "sendIDoc" we see the described error message, but what is the message from the message?
Any Ideas?
Thank you and regards,
Michael

Hello Michal,
thank you for your quick answer!
In my opinion, i don't need any input for this service, because we pick up all data from the vendors ftp - server in a definied time interval.
All needed fields are available in the xml file. In the result tab is the IDocList filled correct, but no sending to the backend system because the error is displayed.
Is it a problem with my concept?
Regards,
Michael

Error reading IDoc Metadata from CRM 5.0 (Basis 7.0) through XI 3.0

We are not able to generate the IDoc metadata from XI 3.0 through IDX2 for port/RFC destination pointing to SAP CRM 5.0 which runs on the Basis 7.0 Web application server.
Has anyone run into this issue? We get the dialog box with information "I::000" Message no. 000. The metadata is not generated at all.
We have no problem generating IDoc metadata for other SAP systems including 6.40 and 4.6C basis layers. Is there something different with 7.0 Basis?
Thanks,
Jay Malla
SAP XI Consultant
Licensed To Code

Hi Renjith,
Thanks for the suggestion. We've already tried that out - the RFC call IDX_STRUCTURE_GET works from SE37 using the RFC destination that we have defined for the CRM system which is referenced in the port. We can debug from the XI system into the CRM system and the data is returned correctly. We can also generate the IDoc schema from the Integration Builder Repository.
However, we cannot generate the metadata from IDX2. If we point the port in IDX1 to another RFC destination for a non Basis 7.0 system, the metadata generation works. So it seems that something is strange regarding generating the IDoc metadata for Basis 7.0 systems.
Regards,
Jay

IDoc Metadata message

Hello while creating a new entry in IDoc metadata , in IDX2 , getting following message : "I::000" and nothing happens after hitting continue: please suggest
Best regards
Krishna

HI Krishna,
Just go thru this help-
http://help.sap.com/saphelp_nw2004s/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/3b/beb13b00ae793be10000000a11402f/frameset.htm
Regards,
Moorthy

Problem With Uploading IDOC Metadata using IDX2

Hi Experts,
While i am uploading IDoc metadata using IDX2 it is showing
"I::000" information.
Anybody please help me why i am getting this problem?

Hi Bhuvan,
Basicall this problem arises when user Id being used in the SM59 to trigger the IDoc's from the R3 system , i,e , the XI user id being used in SM59 of R3 does not have the authorizations to post the Idoc.
Note : 837595 describes the authorizations needed to post and Idoc. Make sure that the user id has the authorizations in this note.
Activate the authorization check in transaction ST01.
And also it may be due to insufficient roles for the user which ur using in RFC connection to SAP system.
Check with the port in IDX1 whether u have configured corectly.
Check this link
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
PAGE - 11
Regards,
Vinod.

How to get IDoc Metadata and Structure without connection to sender

Hello folks!
Is there any chance to receive and process an IDoc with PI without having loaded the IDoc
Metadata with a direct connection from the sending SAP System? Can't this be done by hand?
Or is it not possible to bypass the IDoc Adapter and send the Idoc via an RFC?
Thanks in advance
Gunnar

Hi!
The idea behind the question is the following:
Usually any NONE-SAP RFC-Server of an Integration Tool can receive IDocs just by
beein registered at the sending system. The way you get the metadata into the
receiving Integration tool is an complete different story an can be done by
manually or by doneload the metadata from the DDIC just one time by hand.
But with PI you need to connect to the sending SAP System directly
with idx1 and by importing the structure out of the Integration Builder, right?

Getting IDoc Number after posting it frm Java Program

Hi All:
I had written a Java Program to post an IDoc into the SAP System. I was successful in posting an IDoc. My next step is, to get the Idoc number generated by SAP system for the posted IDoc. Using this IDoc number i want to track its status.
Can anyone please let me know how to get the IDoc Number from SAP from a Java program? I have Transaction ID with me, can i get IDoc Number via Transaction ID?
Please let me know ur views on this.
Thanks & Best Regard,
- - Rajiv

Hi Rajiv,
Could you Please help to clear one thing .I am very new to SAP JCO Programming.To remove the dependency of Posting Data to SAP through RFC program which is written by SAP People ,I want to use IDoc,is it possible to use it ? if yes could u please help with Some Java code so i can post Data through Java Code to SAP with IDoc.
Wait for Your Kind Reply.
Thanks & Warm regards,
Kamal

Multiple destinations for idoc metadata necessary in AAE

Hello,
we are trying to setup the AAE IDOC adapter in netweaver PI 7.3 sp5.
I am still trying to find my way in the new system, but I get the impression that you can only implement one destination for idoc metadata in the NWA.
This is not suffcient of course since different connected systems can have different custom idoc types.
Is this true? If not how should I configure multiple destinations? the inboundRA resource adapter only points to one destination.
Can I define multiple inboundRA resource adapters or is it possible to have multiple destinations in it?
One parameter of the inboundRA is programID which would lead me to think that multiple destinations based on program id must be possible somehow
See also the saplinks on this:
overviwe
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
inboundRA
http://help.sap.com/saphelp_nw73ehp1/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
Thanks
Tom

Hi Tom,
It is possible to have multiple destinations and this can be achieved by maintaining the multiRepository parameter value in properties in inboundRA resource adapter. We can specify as many values depending upon the number of destinations. The convention to specify the destination is as follows:
<SID>=XI_IDOC_DEFAULT_DESTINATION_<SID>
Thanks,
Ramya

Idoc metadata

hi
why should we import idoc metadata while using idoc adapter and what do we mean by metadata.even in mapping idoc structure why we assign segment and begin to constant values and disable cntrol record field.
regards
raghu

Hi Raghu,
What is Metadata:
IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types .This metadata is just a description of available structures
and fields.Using an RFC connection, metadata of this type can be either called directly at runtime or loaded to the Integration Server beforehand.Thus it can be loaded in two ways:
1. During the runtime
2. Before the actual message flow.
To find out what metadata has already been loaded, call the transaction Metadata Overview for IDoc Adapter (IDX2).The system displays a screen with the directory of all systems connected with the IDoc adapter (including a description) for which metadata has already been loaded. Choose Port Maintenance in IDoc Adapter () to call the corresponding transaction and to create additional ports.
Why to Import:
To process an IDocs in the form of an IDOCXML
message, an IDocs metadata must be loaded into
the Integration Server so that SAP XIs IDoc adapter can
change the native IDoc format into the XML representation.
All IDocs are created according to specific rules: This is the general structure (the record types) of every IDoc. Special rules affect the different IDoc types.
Segment:
Segment is like a container which strores all administration information for technical processing, as well as the actual application data.of an IDOC.
Fields :
A segment comprises segment fields as the smallest unit of the Idoc which contains the actual values and information.
control record :
The control record is identical for all IDocs and contains the administration information, for example, sender, recipient and message. Note that the control record also contains the last processing status ( STATUS field).
If you disable the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the fields are filled from the system information not from the payload as:
1. From XI sender service, configuration in Integration Directory, System Landscape Directory
2. Constant LS
3 . From XI receiver service, configuration in Integration Directory, System Landscape Directory
If you enable the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the fields are filled from the IDoc-XML payload.
**Pls: Reward points if helpful **
Regards,
Jyoti

Canu0092t load IDoc Metadata!

Hi all,
I dont know why, but I cant see the IDoc metadata in IDX2 on my Integration Server.
I already have defined the RFCs connection between these two systems (the user used to connect has the authorities needed). The port and the partner profile are created (we20 and we21 on backend side)
When I try to create load meta data manually (XI Integration Server, transaction IDX2) with IDoc Types ZSX_P1100 and source port (the port of backend), I receive Basic type ZSX_P1100 does not exist message!?!? But this message type exists on backend side I already checked! Why I cant load it???
Anybody knows whats happening?
Thanks in advance,
Ricardo.

Hi Ricardo -
>>><i>I need to release the IDoc segmets before the tranfer of meta data to my integration server (XI -> IDX2)?</i>
It's definitely good practice when you set up a new port in IDX1 to see if you can manually load the metadata from IDX2, but it's not a requirement. At runtime, if the metadata isn't there, it will go and get it and load it into the cache.
Regards,
Jin

Loading IDoc Metadata fails

Hi,
I try to load IDoc Metadata within IDX2.
It works fine for several systems/ ports (4.6c) but when I try to load data from a certain system (E.C.C. 6.0) I get an information box that says: "I::000" no matter which IDoc I try to read. It's alway the same mesage even if I try to load data from an IDoc that does not exist in the backend ( like "TEST" for instance).
The rfc connection (SM59) works (connection test), I suspect the user to miss some authorization though. Is that reasonable? Or could it be a "release conflict"? The XI is XI 3.0, Release NW04_20_REL and the backend is E.C.C. 6.0 as mentioned above. The "good "systems are all 4.6c.
Or what else could it be??
Thanks in advance
Karsten

Hi,
> So a user in a SM59 connection can be "good enough" for a connection test but may lack some authorization to read IDoc metadata?
Exactly!
There is an additional Authorization Test.
In sm59 try: Utilities --> Test --> Authorization Test
This test must work.
It could happen that a password is changed in capial letters by the system. Maybe this is the reason.
Regards
Patrick

Refresh Idoc Metadata in PI 7.31 Java Only

Similar Messages

Maybe you are looking for