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

Similar Messages

Multiple destinations for one file?

I'd like to have two destinations for one file - ie, local and on an FTP server. I ask because I've had the FTP fail, and can't find where Compressor stashed the render locally. Failing that, can I at least test the FTP connection (like in AfterEffects) before I commit to an hours-long encoding job?

Too Bad compressor doesn't have more than 1 destination, but if you want to find the temp file, the files are normally kept in /var/spool/qmaster , you can reveal this from the finder using the GO > GO TO FOLDER command, then typing in the above path. Of course you can change this temp space in the qmaster preferences in the System Preferences pane to any other folder you like.

Multiple destinations for form submittals

When a form is submitted can it be sent to multiple email addresses,

We support multiple email notification of form submittal if that is what you are looking for. See http://forums.adobe.com/docs/DOC-1424

Exception on creation of service metadata for WS metadata destination

Hi,
I have imported a webservice from the backend to the model in webdynpro and i have also configured the destination for the metadata in the CE server but when i execute it its giving me error as
Exceptioncom.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination FLIGHT_GETLIST and WS interface ZBapi_Flight_Getlist. One possible reason is that the metadata destination FLIGHT_GETLIST has not been properly configured; check configuration.
and during deployment i am getting the following warning
local/SampleFlightList : References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tcwdapi, sap.com/tcwdwslib~api] (described in the META-INF/application-j2ee-engine.xml)., file: SampleFlightList.ear, column 0, line 0, severity: warning
can any one please help me to solve this issue.
Thanks&Regards,
Hamsa Shree

Hi Hamsa,
Did you also create and configure an "Execution Destination"?
You can test the Metadata destination configuration on Web Service Navigator.
On the web service navigator (http://hostname:portnumber/wsnavigator) search in the metatda destination you have created for the service you imported in web dynpro as a model. If you can find it there test it on the ws navigator.
Best regards,
Yasar

SA PI 7.1 EHP1 - Support for IDOC Adapter using AAE

Hi,
Can anyone confirm if the SAP PI 7.1 EHP1 supports the IDOC adapter in the AAE ?
Cheers
Colin.

Hi Colin,
I am workinngt on EHP1 PI7.1,but no support for IDoc Adapter in the AAE.
The new features added for IDoc adapter is IDoc packging and new conversion module added .
we have to wait till next release,but not sure...
Regards,
raj

Urgent: Error during Import Metadata for IDoc

Hi
We successfully imported the metadata for IDoc from R/3 in Development and Test box and everything worked fine.
Now, when we try to import the metadata for IDoc in Production box it gives me an error" Basic type 'IDoc name' does not exist". I went back to the development box and I try to import some other Idoc metadata and it gives me the above error message.
I checked RFC destination, IDX1 and everything seems to works fine. Any suggestions will be helpful.
Thanks
Mohan

Hi Mohan,
Did you execute IDX2? And if so, please delete existing meta data for port and reimport, if you still receive an error check your R/3 connections (SM59) and port definitions in the receiver IDOC channel (directory)!
Cheers,
Paul

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

How to generate multiple files for each segment in the IDOC

Hi,
I have a IDOC with multiple segments, for each segment, a file needs to be generated,
There is only one target structure. Please let me know as to how do we handle this requirement in XI.
Regards,
Younus

Use multimapping in message mapping. Then map the Idoc node to the Message Type of File.
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure
Regards,
Prateek

RFC Destination type for IDOC to FILE

Hi,
wat is the RFC Destination type for IDOC to FILE ?
jeff

hi,
u shud create rfc dest tye: R/3 connections...that is type 3.
refer this:
R/3 side settings
1. SM 59 (RFC destinations)
Create a RFC destination pointing to the XI server. The connection type : R/3 connection. The target host: the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Give the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
XI side settings.
1. SM59 (RFC destination)
Configure the RFC destination pointing to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
[reward if helpful]
regards,
latika.

Load metadata for idoc

hi,
how to load metadata for idoc..
I hope IDX2 is for to check whether metadata is loaded or not..
thanks
guna

Hi,
use :
IDoc (Intermediate Document) metadata comprises structures for the corresponding IDoc types that are required by the IDoc adapter to convert these IDocs to IDoc XML format and the other way around.
Using an RFC connection, metadata of this type can be either called directly at runtime or loaded to the Integration Server beforehand.
The system containing the metadata is either the sender or receiver SAP system or, if the sender or receiver system is a subsystem, the SAP reference system where the metadata is saved.
You can display metadata that has already been loaded, or if you are upgrading the application system then you can delete the metadata and reload it.
Prerequisites
To access the metadata in the sender system, you must establish an RFC connection to this system using the port maintenance in the IDoc adapter.
Procedure
       1.      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.
       2.      Expand the individual systems to display the IDoc types and clients including a description for each system. The system displays the metadata for each connected system for which metadata has already been loaded.
       3.      To apply the metadata structure loaded from a particular system to another system (for example, to an SAP reference system), select the link to the corresponding IDoc type and choose Copy ().
The system displays a dialog box in which you can copy the IDoc type description to another system (Target Port).
       4.      To delete metadata that has already been loaded, select the link to the corresponding IDoc type and choose Delete ().
The system asks you if you really want to delete the selected structure.
       5.      To delete the metadata structure, choose Yes.
       6.      To load additional metadata, choose Create ().
The system displays a dialog box where you can enter the IDoc Type including Extension and the system (Source Port).
       7.      Make the required entries and choose Continue.
The new structure is inserted in the tree structure as follows:
¡        If the structure originates from a system from which metadata has already been loaded, it is inserted below the structures already loaded from this system.
¡        If the structure originates from a system from which no metadata has already been loaded, it is inserted together with the system below the already listed systems.
       8.      To display details about a metadata structure that has already been loaded, choose the link to the corresponding IDoc type. To display this structure in detail, choose Display (). The system displays the structure in a hierarchy tree.
       9.      To display the corresponding system (port) and the basic type from the detailed display, choose Header Information ().
   10.      To display the segment versions of all segment types in the structure, choose All Segment Versions ().
   11.      Select a segment to display all its fields.
and also refer these article
http://help.sap.com/saphelp_erp2004/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/content.htm
http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp?topic=/com.ibm.websphere.dtx.packsapxi.doc/tasks/t_pack_sapxi_Set_up_the_SAP_XI_System.htm
Regards,
Suryanarayana

Can we give multiple destination files for a crystal report.

Hi all,
Can i give multiple destination files for crystal check process when the out put type is file.
What i want is the text file, which will be created at the destination given by the user, must be created at other location also.
Please help me.
Thank you,
Bye.

Multiple default values for a presentation variable is only possible in 11g as Srini Said.
Check mark : Enable user to select multiple values. (under variable datatypes)
http://obieetraining11.blogspot.com/2012/08/obiee-11g-using-presentation-variable.html
If it is 10g, then it is not possible.

Multiple (mail) destinations for one report using distribution list

I would like to email a report to multiple destinations using a distribution list.
Environment:
Oracle reports: 10.1.2.3
OS: Windows 7
Database:Oracle 11g(11.2.0.2)
This is the content of the distribution file:
<destinations>
<foreach>
    <mail id="a1" from="[email protected]" to="&<mail_to>" subject="Invoice">
      <body srcType="text" format="ascii">Invoice attached
      </body>
      <attach srcType="report" name="invoice.pdf" format="pdf" instance="this">
         <include src="report"/>
      </attach>
    </mail>
    <mail id="a2" from="[email protected]" to="[email protected]" subject="Invoice sent to &<mail_to> ">
      <body srcType="text" format="ascii">Attached invoice was sent to the customer
      </body>
      <attach srcType="report" name="invoice.pdf" format="pdf" instance="this">
         <include src="report"/>
      </attach>
    </mail>
</foreach>
</destinations>
When I run this using the following URL:
http://testserver.our_servers.local:7778/reports/rwservlet?server=rep_dev&report=VKR0030.rdf&userid=myuser/test123@ORCL&distribute=yes&destination=VKR0030.xml&onfailure=rollback&onsuccess=commit
I get the following error: REP-34304: Distribution failed to complete, please review the distribution lists
When I remove one mail element, it works fine.
One mail tag with multiple email addresses in the "to" parameter isn't possible because I have to use 2 different mail templates(subject and body differ).
According to the documentation(https://docs.oracle.com/html/B14048_02/pbr_dist.htm#i1005830), it should be possible to use multiple mail elements.
Required/Optional
Optional. You can have as many mail elements as you require.
What am I doing wrong?

Found the solution.
When putting each mail element in a foreach, it works.

Same Destination for Multiple Clips

Hey Kids...
It should be simple but I seem to be drawing a blank.
I have, for example, 6 clips that I want to convert to Pro Res. Once I have applied the setting, how do I set the same destination, a file on an external drive for example, for all the clips all at once - as opposed to having to set the destination for each clip manually.
I know it can be done...but I appear to be vapor locking on how to do it.
Thanks in advance.
MS

Highlight all the individual encodes, (not the container the encode settings templates are a part of) once highlighted, Right click your mouse, select "Destination" in the popup menu and select the new destination from those listed, or go up to the Target menu and select the "Destination" menu and select other to create a new destination.

Sender Port Error in SAP ECC for IDoc

Hi,
I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
But in SM58, the IDoc ends in error saying
Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
Business Systems:
Sender : SAP ECC
Receiver: SAPPID
Kindly provide your inputs.
Thanks
Rahul

Hi Rahul,
thanks for the information that your scenario is working fine.
But i want to clarify some points:
   - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
     i.e. if your system id is "ABC", the senderport is "SAPABC"
      => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
     manually in the idoc test utility WE19
   - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
     the senderport in WE21, this is not necessary and did not solve your problem
- the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system
    without application idoc metadata
   The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
   but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
   In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
   With this rfc-destination the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
   If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
   I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
I hope this clarification helps you to understand the error and the solution.
Kind regards,
Andreas Dahl

Why is a sender communication channel not required for IDOC and PROXY ?

Hello,
In case of IDOCs, metadata will be available in PI for the IDOCs used both at inbound and outbound.
Why is a sender communication channel is not required in case of IDOC and PROXY outbound scenarios (i.e. IDOC to File or PROXY to file ..) when a receiver channel is required for scenarios like file to IDOC or file to PROXY.
Though this might be a regular question, I am not able to find a proper reason.
Please let me know the reason for the above request.
Thanks & Regards.

You will create RFC destination in ECC , it will have details about PI system details, when ever you send IDoc, ECC will use Port and RFC destination to connect PI Integratiion engine to deliver data to PI.
But when receiver side you will create RFC destination in PI with ECC details, but to call RFC destination and Port we need medium that was the reason we create IDoc communication channel.
Even the same case for Proxy also, but HTTP deastination establish the conection between ECC and PI, but receiver side you have to create XI channel with PI integratioin engine adress to post data.
Regards,
Raj

Multiple destinations for idoc metadata necessary in AAE

Similar Messages

Maybe you are looking for