Failure in retrieving business system with Idocs

We implemented a B2B scenario (SAP R/3 4.7 ->XI->XI->SAP R/3 4.7 ) in which each SAP R/3 + XI act as a Business Party with a business service assigned to internal business system.
Trying to send IDoc from one Business Party to the other
The IDoc got through from the source system to the target system OK, The target R/3 sent the ALEAUD ack back but the ALEAUD sent from the target R/3 contains the internal business systems names and the XI did
not convert it back to address the services that sent it from the source system.
The message gets to the source system with the internal names of the target system so it falls due to unrecognized systems.
the error at the source target for the returning ALEAUD is OUTBOUND_BINDING_NOT_FOUND
SAP dev support claim that the source is the header mapping from XI1 to XI2.
Any work around for this?
Thanks,
Udi

I have an idea.
call me : 0526116713
Nimrod

Similar Messages

SAP PI Modeling: Two Business systems with party

I am triing to create SAP BPVT Interaction model that describe connection of 2 process components. Each of that components must be business systems with party. As I understand process component must be Process component at business partner for assigning business system with party.
If I create SAP BPVT Interaction model with two Process component at business partner, I get they connection in type of "Other Interaction". When I try create new assigment, I get error "Unable to assign the model to this connection type due to the method or profile in use".
How can I create correct connection?

Hi Eugenia,
Please see note 1084315 which descriibes the the multiple backend scenario.
This should be relevant here.
Best regards
Christophe

Connect one Business system with two Integration Server

Hello,
Can we able to connect one Business System with two Integration Server?
I have one Business system (ECC 6.0 with the client 900) and it is already connected with PI 7.0 system.Can I able to connect the same sytem (with same client) with PI7.1?
I want to do the HTTP Connection for ABAP Proxy for this two XI system with one business Sytem ?
Is this possible ?Is there any work around solution there?
Thanks.

Hello ,
This document describes about connecting with Two PI7.1 system using Application Server 7.1 and Application Server 7.0 SP14 .
I want to connect same ECC system via abap proxy with two different PI system .One is PI7.0 and another one is PI7.1 system.
Is this possible if i use Application Server 7.1 or Application Server 7.0 SP14 ?
Thanks.
Lakshmi
Edited by: Muthulakshmi Pandi on Apr 16, 2009 11:48 PM
Edited by: Muthulakshmi Pandi on Apr 17, 2009 12:21 AM

Business System with or without Party

Hello,
I've a interface RFC to JDBC syncrhonous
I've two CC sender (RFC) for the same interface, one for each client. The test for one client is ok however the test in other client result with the follow error:
'aternativeServiceIdentifier: party/servce from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier..', I have seen the 730870 note (Q26) but i don't see how solved my problem.
1.- Somebody can explain me the difference betwen using business system with party or business system without party in the integration directory?
Thanks very much.

>
silvia diego wrote:
> Hello,
>
>
> I've a interface RFC to JDBC syncrhonous
> I've two CC sender (RFC) for the same interface, one for each client. The test for one client is ok however the test in other client result with the follow error:
>
> 'aternativeServiceIdentifier: party/servce from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier..', I have seen the 730870 note (Q26) but i don't see how solved my problem.
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
>
> 1.- Somebody can explain me the difference betwen using business system with party or business system without party in the integration directory?
>
> Thanks very much.
in you case you dont ahve to use a part. You have different Business services.
Configure you RFC adapters, one for each client.
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

Business system for idoc reciver communication channel.

hi gurus,
iam doing one file to idoc scenerio.
for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
pls guide me .
warm regards.

Hi
You can use th Buiness system as a receiver for IDOC.
Making sure
1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
2. Use the same LS name for the BS pointng to FIle in the SLD.
Complete the IDOC configuration from XI
1. Create the RFC dest from XI to ECC
2. Create the Trfc port and call this RFC dest created..
3. Use this Trfc port in the IDOC receiver
On ECC:
Make sure the Partner Profiles is created properly.
it is suggested to use always the business systems when you deal with IDOC and Proxies.
Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

Transport of Business System in IDoc scenarios.

HI All,
I am doing IDoc scenarios so I am using Business System say PIS_800 . Now i have moved these scenarios to quality system and my Business System name is supposed to be PIQ_800.
I am using simply file import-export for transport. After transport my Business System name is coming as PIS_800 only.
Can anybosy plz suggest me how to change it to PIQ_800? This part is quite new to me so detailed explaination will be helpful.
Thanks,
Atul.

Hi Atul,
In DEV
1) Export the TS & BS of SAP R/3
2) Export the TS & BS of DEV XI Server
In QTY
1)Import the TS & BS of SAP R/3
2) Import the TS & BS of DEV XI Server
3) Create the TS for Quality SAP R/3 & Corresponding BS also which is pointing the QTY Server Details
Now create the Transport Groups and Targets
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
With this Configuration, the DEV BS will be replaced by the QTY BS.
Thats all
Regards
Seshagiri

SLD Business System with or with out Logical System If so, which Log system

Hi
I'm in confuse with the Logical System when creating a Business System in SLD.
Our requirement is LEGACY -- PI/XI -- ECC.
When I create Business sytem in SLD, I need to give a Logical System. Which system (Is it xi/pi or ECC ) Logical System to be provided?
Thanks.

>
Pothana Yadav wrote:
> Hi
>
> I'm in confuse with the Logical System when creating a Business System in SLD.
> Our requirement is LEGACY -- PI/XI -- ECC.
>
> When I create Business sytem in SLD, I need to give a Logical System. Which system (Is it xi/pi or ECC ) Logical System to be provided?
>
> Thanks.
if you are using File to IDoc scenario then need to define logical systems for both business systems you are going to create for
i.e they will be used as sender and receiver partners in case of logical systems
if need more details check the below blog
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
check the same for how logical system are used in this case...
note above will be helpful in case of only idoc scenario..else no need of creating logical systems even though target sysstem is ECC
HTH
Rajesh

Integrating MDMP and Unicode systems with IDoc interfaces

Hi,
We are working on integrating SAP R/3 6.20 (MDMP) with SAP PI 7.0 SP10 (Unicode) system. The source will send MATMAS or CLFMAS IDocs with Thai / Japanese characters and PI should transform and post it to SAP ECC 5.0 Target system [IDoc to IDoc scenario].
( SAP R/3 Legacy 620 - Non-Unicode / MDMP ) |----> ( XI - Unicode) -> (ECC - Unicode)
Had a look at few SAP notes (745030 ,656350 and 613389) and it looks like there is no standard way/best practice to handle this scenario.
References:
1.PDF of TECHED Session ID: IM101 Dealing with Multi-Language Garbage?Data Lessons Learned
2.SAP Note 745030 - MDMP - Unicode Interface_Solution Overview.pdf
3.MDMP_Unicode_Transfer_final.doc from SAP Note 745030
4.SAP Note 656350 - Master Data Transfer UNICODE to MDMP Systems with ALE.pdf
5.SAP Note 613389 - ALE SAP system group with Unicode systems (Solution-2)
My understanding per SAP Notes: (Please correct me if I'm wrong)
a. For MDMP integraton we can't use Standard ALE Config instead we have to use Custom Configuration (IDoc collection setting in Partner profile &Scheduling RSEOUT002/RSEOUT00_MDMP and use Function module :IDOC_INBOUND_ASYNCHRONOUS_2 ).
b. The RFC Destinations should use proper logon langauage for correct MDMP IDoc transfer (For sending IDocs with Japanese character, the logon language should be JP).
c. If we want to transfer IDocs in more than one language we need to create multiple Partner profiles/RFC destinations each with specific logon language.
Please guide us in integrating these systems if you have done a similar integrations, following are my questions:
1] Is there any configuration change required at PI layer?
2] Do we need to install codepages in PI Unicode system for all languages used or Unicode system is capable of handling all the languages?
3] Is it necessary to install any SAP Add-on package in R/3 MDMP system inorder to support MDMP to Unicode data transfer?
3] If we want to send MATMAS/CLFMAS IDoc with Thai/Japanese characters from same system, what are the changes required at the Source system?
(Source may send MATMAS/CLFMAS IDoc with either Thai/Japanese characters but not both of them in a single IDoc)
4] Can we use regualr ALE & Partner profile settings for handling multi-byte characters or we need to use IDoc collection and RSEOUT002/RSEOUT00_MDMP report for transfer?
5] Is there any restrictions on the IDoc types (MATMAS,CLFMAS etc) supported in MDMP-Unicode integration solution.
5] Is there any best practice document available for this scenario?
6] Do we need to involve SAP AG for MDMP to Unicode system integrations(As per SAP Note: 656350) ?
Thanks and Regards,
Ananth

Hi Ananth,
as you have already mentioned, you need differents RFC destinations for each language. So you have to make sure, that the IDocs use the right destination according to there content.
If you have messages from PI to MDMP it is the same, you need different channels with different logon languages as well. You need an identifier in the message, that can be used for selecting the correct channel.
It should not be a restricting to any IDoc type, but it is not possible to post a message with different languages (which require different codepages) in one IDoc.
For correct conversion from a non unicode system to unicode, the codepages have to be installed in th OS of the PI server.
Regards
Stefan

Unable to create Business System with role Integration Server

hi Experts,
we are unable to create a BS with role of integration server, its throwing error with internal server 500.
please advise. we do not have any issues while creating TS with role of WEBASABAP.
thanks and regards,
Kesava
Edited by: Prateek Raj Srivastava on Jan 23, 2012 12:13 AM

Hi Kesava,
what is the purpose of creating a business system of type IS? This is automatically done in the post installation by CTC templates. So if the post installation is successfully executed, this should already be there. And if not you should check if the post installation was properly executed and if there where problems analyse why they occured.
The creation of the BS is just one part of the game, so I would highly recommend to execute the hole post configuration via template or follow the help.sap.com and execute it step by step manually in the described order. Otherwise i guess this will not work.
If there where just problems with SLD - please also have a look at SA Note 1117249 - Incomplete Registration of PI components in SLD
best regards,
Markus

Finding message in SAP Business Connector with IDoc number

Hi Experts,
Since there is no separate forum for Business Connector, posing my question here.
Does anyone have idea how we can find a message in SAP Business Connector if we know the source IDoc number, the same way we use IDX5 in PI.
Thanks,
Dhawal

AFAIK there is no simple way. What I usually do is compare timestamps. The Idoc is usually processed on the B.C. within the same minute.
We only have up to 10 Idocs within one minute and I do not have to search every day. So it works for me.

Configurations required in SLD,IR,ID,SM59,BD64 to Start with IDOCS

Hello all,
Can You Post me the Above details.
thanks,
Srinivasa

Hi Srinivas,
Let us explore the need for each steps and detail it now...
Step-1 : You need RFC destinations for placing the metadata of the IDoc.
Use transaction SM59 to maintain an RFC destination for the IDoc sender/receiver system.
This RFC destination is used to retrieve the IDoc metadata from the sender system.
The IDoc adapter needs these metadata to create the corresponding IDoc-XML message from the RFC stream.
Step-2 : Next You need IDx1 for getting IDoc metadata from the Sender system.
Use transaction IDX1 to assign a port (RFC destination) to the system that contains the metadata of the IDoc types.
Note:
There is a mechanism on the Integration Server that uses this RFC destination to retrieve and cache the metadata at runtime if it is not yet available on the Integration Server.
Nut-Shell:
Since IDoc metadata is cross-client, you should only assign one port for each system.
If several ports are assigned, ensure that they are all working.
This is Done in Partner Profile.
If you are not able to load the metadata from this system (because of administrative or security-related restrictions, for example),
you can also load it from a reference system (for example, a test system) and use transaction IDX2 to assign it to your production system afterwards.
For non-SAP systems, either the ports in transaction IDX1 have to point to a reference SAP system, or you copy the metadata with transaction IDX2.
I come to mean that if you double click the OutBound Parameter in the Partner Profile you will be allowed to choose the Idoc type like Matmas,Debmas blabla..
There after providing the receiver destination in that partner profile which is nothing but your Maintaining Metadata through a port,
which on double click leads to RFC destination alloted with a port to transfer its data from sender to receiver Server.
Step-3 : Goto SLD and do the following.
Access the System Landscape Directory (SLD) to maintain the technical systems for the sender and receiver business systems of your system landscape.
You have to define a technical system (and a client in the case of SAP systems) to which your business system belongs.
When you define a client number, you also have to specify the corresponding logical system name in the Technical System Browser.
Note:
The technical system configuration is not required if your business system is configured as a data supplier for the SLD.
Step-4 : Goto Integration Directory and do the folllowing.
Access the Integration Directory to define your business systems as services without party.
a) Either you can choose from the Objects Business Service where your client is defined for it.
With this Selected Business Service you just rightclick and choose ASSIGN TO BUSINESS SCENARIO.
b) Second choice is to choose the business system which was done in SLD.
Do the receiver determination and interface determination but since the adapter is not required to choose for Idoc dont do sender determination.
Note:
The IDoc adapter only uses the service definition (business system) together with the corresponding adapter-specific identifiers in the Integration Directory.
The maintenance of your IDoc sender system in the SLD is therefore not sufficient.
It is recommended that you assign your business system definition retrieved from the SLD to a service in the Integration Directory.
Nut-Shell:
Using this information about the system ID, client, and logical system name for a specific business system, the IDoc adapter is able to specify the corresponding service in the XML header. Routing is then based on service names.
You need the
 logical system, SAP system ID, and client for an IDoc receiver SAP system
 SAP system ID and client for an SAP system
 logical system for a non-SAP system.
This means that the business systems used for the routing definitions in the IDoc-XML message header are retrieved from the adapter-specific identifiers of the service definitions in the Integration Directory,
where for each business system client, the corresponding system ID, client, and logical system name is defined.
Caution:
Use the import function to retrieve the adapter-specific identifiers for a service (business system) to avoid double maintenance in the SLD and Integration Directory.
Step-5 : Steps in Integration Repository.
Export the IDoc in Imported Objects.
Double click the Idoc to view the structure.
This Idoc type is decided in the partner Profile.
See step-3 for further details.
Create the Interface Objects like
1.Data Type for Receiver File.
2.Message type which wrapps this Data type.
3.Interface Type.
a) For Sender Idoc just drag the Idoc name which you have loaDED IT IN YOUR imported objects.
b) For Receiver File It just wrapps the Message type of the file.
4.Message Mapping:
The Fields selected in the data type for the file should be the mandatory fields in the Idoc.
Since the Idoc is in the sender side,it just performs similar operation like selecting things from a database.
Begin and Other Attributes are neednt be worried to map.
The Mandatory fields which was chosen will need to be mapped with the target file.
5.Interface Map:
Just Wrapps the Message mapping.
Step-6 : BD64 is to Distribute the Idoc to Various Acceptors.
1.Create Model View.
2.Add Message Type to it.
3.So that it displays your model view with your Message type like MATMAS.
4.Goto Environment and click Generate Partner Profiles.
5.Executing it,you will get a log indicating the Partner,port and Outbound Parameters.
6.After Doing this goto Edit Menu available in the tool Bar and give Distribute.
7.After distributing it ,it shows your logical system name along with the technical name.
8.Now to fill the IDOCs with Data we have to go to Transaction bd10.
9.We can give our own selection criterias and select the list of materials accordingly.
10.Now to check whether the IDOCs has been correctly created and sent to the receiving system (in this case it is the SAP XI Server)
11.we have to check it out in Transaction WE05.
12.Now we can go to the Location we specified in the Configuration where the file will be created.

Logical System for RFC-Business system?

Hi,
I want use RFC adapter for my scenario like File to RFC.
The query is like, is there any importance to use Logical system for my Business System which is using for my RFC Adapter in my communication channel.
Regards
Gopi

logical system name is relevant only for Idocs, but it is always a good idea to maintain the technical and business systems with all the information you can provide.
you can check the logical system names of ABAP application servers at bd54 tx code.
Regards,
Henrique.

XI 2.0: HowTo connect Bus.-Systems with different Releases to XI (RFC-Ad.)

Hi,
can anybody help me solving this problem:
I have Business-Systems connected to XI by RFC-Adapter. Everything works fine. Now I want to upgrade some of these Business-Systems to a newer Release --> RFCs are changing! (For both Releases I have separate Developing-Systems)
Does the following work?
- Creating a new Product-Version
- Creating new Software-Component-Versions for the new Product-Version
- Creating Namespaces with the same names (as in the older Software-Component-Versions)
- Tools/Release-Takeover for every Software-Component
- Connecting Develop-System of the new Release to the new Software-Components (Interface-Import of RFCs)--> in the new Software-Components only new RFCs can be uploaded.
- Business-Systems with old Release keep connected with old Product-Version. Business-Systems with new Release are connected with new Product-Version.
Does it work? Is this the best approach or are there other possibilities?
Thanks in advance,
Max.

Hey
are u suppose to do an IDOC(R/3 system A)-Xi-IDOC(R/3 system B) scenario,of u have to collect IDOC's from both the R/3 systems and send it to a single file?
in any case u have to maintain separate Business system and logical system name for both R/3 systems
thanx
ahmad
Message was edited by:
Ahmad

Integration server already has a business system

Dear All,
I got problem while creating sender business system for FILE-IDOC Scenario.I have created r3_800 business system for IDOC receiver with logical system name APOCLNT800.After that I tried to create business system for FILE Sender with logical system name XI7CLNT001.But i am getting the error "The selected integration server already has a business system with logical name XI7CLNT001. Select a different integration server or change the logical name."
Do I need to create another logical system?
Any help would be appreciated.Thanks in advance.
Regards
Vinay

In addition to my previous post, refer the following blogs. This will help you understand how ABAP based systems in the landscape already get registered in SLD while post installation. Just check once the BS you are trying to create in SLD is already there.
/people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
/people/praveen.kurni3/blog/2010/10/15/creating-a-technical-system-of-type-was-abap-in-sld133-are-we-sure-about-the-objects-that-get-created

Technical System vs Business system jms

Technical System vs Business system jms

Hi,
So i should create third party business system or use business service from your reply.
--Create Business System with ABAP-WebAS system for R/3 system.
How does this idoc know to flow through my integration scenario during runtime?
You need to create a RFC destination in R/3 system which will point towards the XI port. When you will configure your partner profile ( Outbound ) from R/3 to XI, in the receiver port details you need to provide a RFC destination details which will point to XI.
Let me know if you need more details.
Nilesh

Failure in retrieving business system with Idocs

Similar Messages

Maybe you are looking for