B2B scenario with IDocs, sender system not in SLD

Hello all
When sending a purchase order IDoc (ORDERS05) out of SAP ECC 6.0 I get the following error in SM58:
No service for system SAPPEE, client 200 in Integr ation Directory
Message no. SR053
Until now I did not register the SAP ECC 6.0 system in the SLD. Is this absolutely mandatory?
The RFC-Destinations work like a charm, the user (type C) and authorizations (for now SAP_ALL) should be ok (same settings in XI and SAP ECC system).
In the integration directory I defined a partner "IDOC_SENDER" with the following identifiers:
Agency = http://sap.com/xi/XI
Scheme = XIParty
Name = IDOC_SENDER
Agency = PEE_200 (SID with client from customers system)
Scheme = ALE#LI#LF
Name = 0000601140 (this is the vendor id from customers point of view)
Agency = AEE_200 (SID with client from vendors system)
Scheme = ALE#KU
Name = 0000001011 (this is the customer id from vendors point of view)
Within this partner "IDOC_SENDER" I defined a business service "Order" and assigned ORDERS.ORDERS05 as allowed outbound-interfaces.
Within this business service "Order" I defined a sender communication channel "Order_send_IDOC" with adapter type IDoc.
Based on this I created a receiver determination, interface determination, etc.
I also configured things in IDX1, IDX2. The metadata (structure info of idoc type ORDERS05) was successfully loaded.
Did I miss something? What to do to eliminate this error:
No service for system SAPPEE, client 200 in Integr ation Directory
Message no. SR053
Any help would be greatly appreciated!
Thanks in advance
Renaud

I think there are some mis-configurations:
defined a business service "Order" and assigned ORDERS.ORDERS05 as allowed outbound-interfaces.
You do not define a business service when IDOC/ RFC/ PROXY is sender/ receiver
It should be Business System and it has to be defined in SLD and then imported in ID. (search on SDN for How to create Business System )
defined a sender communication channel "Order_send_IDOC" with adapter type IDoc.
You do not create Sender channel when IDOC/ PROXY is sender.
I would suggest that you follow steps mentioned in this wiki: http://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
Regards,
Abhishek.

Similar Messages

IDOC sender system settings

Hi,
I am trying to do the settings for the idoc sender system the steps i have completed are..
1) sm59..maintain a rfc destination from idoc sender to the integration server.
2) we21..created a tRfc port with the rfc dest from step1.
step 3 is where i am stuck...
3) we20....to maintain the partner profile and partner number...there isint enough info in the xi config guide..
any pointers..would be appreciated.
Regards
Ravi

ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) 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 XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination 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
3) 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.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.

Idoc to idoc scenario with idoc tunneling

IN idoc to idoc scenario with idoc tunneling the XML_CONVERSION parameter to value 2 is set whish means An IDoc is converted to IDoc-XML if requested by the service
I want to know where we specify this and how we specify?

1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
ref these weblogs.
It is given under;
TCODE - SXMB_ADM
- Integration Engine configuration
- set the XML_CONVERSION parameter to value 2

IDOC send step not running with exception in BPM?

Hello,
hope this is a simple question, but we are running with a problem here which is not answered well in SAP help or sdn. Possibly I didn´t find the right blog.
Situation:
We created a BPM with a send step (IDOC receiver) in a block (after a receive step starting the BPM) (That´s simple so far!).
The send step (async IDOC) in the block is connected in its attributes in field "system error" to an exception branch defined in the same block.
In this except.branch the process should send back to sender system a message via RFC and the last step in this exception branch is to interrupt the proces.
But now we tried to do a test. In this test we modified the receiver address of the send step (IDOC reciver) so that the receiver could not be reached, which results in a system error in SXMB_MONI (Service unavailable).
But this doesn´t work. The BPM starts the send step to the unavailable receiver, SXMB_MONI shows a system error step, but then the BPM continues with the next step after the block without starting the exception branch.
Any idea why the exception branch is not called?
Best regards
Dirk

Hello again,
we are one step further now.
We did the same with an RFC instead of the IDOC send step.
Same result:
The service is not reachable. So the step results in an system error.
But as we could see in the monitoring SXMB_MONI the block with the exception and this send step (RFC) is passed before the step gives back this error!
So it looks like connection problems do not trigger an exception?
Any help is welcome!
Best regards
Dirk

Change client in scenarios with SAP business system

Did you ever wonder how you can change the client of a Business System and it's related communication channels in scenarios that make use of SAP systems?
One might think that changing the client in the communication channel (sender and/or receiver) is enough.
Unfortunately this is not the case. If you change only the client in the communication channel you'll get the following error: "lookup of alternativeServiceIdentifier via CPA-cache failed for channel XYZ"
It took me a while to figure this out, but finally I got it.
Two options:
a) Either you create a new business system in the SLD and you restart the configuration of all your scenarios, or
b) You change the client from the business system in the SLD
I definitely didn't want to go for option 1, as it meant that I had to redo a lot of scenarios (sender agreement, receiver determination etc.). I would have lost significant time and the configuration work is subject to errors as well which would have meant retesting all of the flows.
Therefore I explain in this thread option (b)
SLD:
1) In the SLD in the Technical Systems area, create a new client for the Web AS ABAP system.
2) In the SLD in the Business Systems area, click on the system that is to be associated with a new client.
3) Click on the Integration tab
4) Change the associated technical system and choose your new client
remark: the name of the business system might be somehow misleading if you specified the client as part of its name.
Integration Directory:
1) Delete the Business System
2) Activate Changes
3) Import the modified Business System
4) Assign the new client to the communication channels related to the business system. (as the name of the Business System is still the same as before, the communication channels are automatically assigned to it)
5) Activate Changes

Danny
I would like to add two more things here -->
1) For Web AS ABAP Technical Systems, I would rather ask BASIS to execute RZ70 in order to create the entry in TS of SLD. This will list down all the client of the SAP server.
2) If the Business System name you created is not client specific like
SCP400_Tst /// Client specific name
SCP_Tst /// Not client specific name
I mean if the Business System name is not client specific then no need to delete the Business System just go for
Service ( Edit Mode ) --> Adapter Specific Indentifiers --> (click button ) Compare with SLD & then Apply button
And activate the changes.
Rest of the steps will reamin same as you mentioned.
- Lalit -

Change Idoc Sender system

Which are the necessary steps to be perform in order to change the sender system of an Idoc, for instance:
the current scenario: R3 System1(IDOC) -> XI -> SRM
the to be scenario: R3 System2(the same IDOC) -> XI -> SRM
Thanks in advance

1. All the ALE settings would be changed. So the names of RFC destination, port, Logical system etc would change at sender side.
2. In SLD entries should be maintained for new R3 system
3. There should be an entry on idx1 for ur sender system.
4. At IR it would be better to reimport the IDoc.
5. Mapping would be required if there is a change in structure
6. ID would change completely bcoz the sender system name will change
Regards,
Prateek

Problems with CIF (Logical system not assign to BSG)

Hello,
We are sending all master data from ECC to APO. We set up the CIF in DEV and all worked fine. But when we try to send the data from ECC to APO in QA an error appears. It says that the logical system is not assign in the BSG. Apparently the configuration that we have in DEV is the same that we have in QA. The logical systems in all instances (DEV & QA) have the same name. Could this be the problem?
Thanks,
David

Hi David,
1) Check whether BSG is defined in customisation under the below
link
SAP - Implementation Guide > Integration with SAP Components
     > Integration via APO Core Interface (CIF)    >
    Basic Settings for Creating the System Landscape   > Maintain Business System Group
2) Check the BSG is assinged to the logical system under the
spro transaction
SAP - Implementation Guide > Integration with SAP Components
     > Integration via APO Core Interface (CIF)    >
    Basic Settings for Creating the System Landscape   >
Assign Logical System and Queue Type
3) Check BSG is showing in APO material master for a location
product under "Properties" tab.
Regards
R. Senthil Mareeswaran.

Sending metaData with netStream.send is not working

I'm trying to send metaData from client to FMS server when recording Webcam video and have implemented sending of metaData as stated on Adobe's help page at: http://help.adobe.com/en_US/FlashMediaServer/3.5_Deving/WS5b3ccc516d4fbf351e63e3d11a0773d5 6e-7ff6.html
However when I play the recorded video from FMS, my custom metaData properties trace "undefined". I can trace default metaData properties such as duration or videocodecid successfully, but not my custom properties such customProp, width or height. Here is part of my code that is related to the issue:
private function ncNetStatus(event:NetStatusEvent):void {
     if (event.info.code == "NetConnection.Connect.Success") {
          ns = new NetStream(nc);
         ns.client = this;
          ns.publish(webcam_test, "record");
private function netStatus(event:NetStatusEvent):void {
     if (event.info.code == "NetStream.Publish.Start") {
          sendMetadata();
private function sendMetadata():void {
      trace("sendMetaData() called...");
     myMetadata = new Object();
     myMetadata.customProp = "Welcome to the Live feed of YOUR LIFE";
     ns.send("@setDataFrame", "onMetaData", myMetadata);
public function onMetaData(info:Object):void {
     trace('videocodecid: ',info.videocodecid); //returns 2
     trace('customProp: ',info.customProp); // returns undefined
And here is my trace result:
NetConnection.Connect.Success
NetStream.Publish.Start
sendMetaData() called...
NetStream.Record.Start
Stopped webcam recording...
NetStream.Record.Stop
NetStream.Unpublish.Success
NetStream.Play.Reset
NetStream.Play.Start
videocodecid: 2
customProp: undefined

Here is the working code which I have tried at my end. You can see the highlighted line in which the second parameter is 0 which means it will play only recorded stream:
package {
    import flash.display.MovieClip;
    import flash.net.NetConnection;
    import flash.events.NetStatusEvent;
    import flash.events.MouseEvent;
    import flash.events.AsyncErrorEvent;
    import flash.net.NetStream;
    import flash.media.Video;
    import flash.media.Camera;
    import flash.media.Microphone;
    import fl.controls.Button;
    import fl.controls.Label;
    import fl.controls.TextArea;
    public class Metadata extends MovieClip {
        private var nc:NetConnection;
        private var ns:NetStream;
        private var nsPlayer:NetStream;
        private var vid:Video;
        private var vidPlayer:Video;
        private var cam:Camera;
        private var mic:Microphone;
        private var clearBtn:Button;
        private var startPlaybackBtn:Button;
        private var outgoingLbl:Label;
        private var incomingLbl:Label;
        private var myMetadata:Object;
        private var outputWindow:TextArea;
        public function Metadata(){
            setupUI();
            nc = new NetConnection();
            nc.addEventListener(NetStatusEvent.NET_STATUS, onNetStatus);
            nc.connect("rtmp://localhost/publishlive");
         * Clear the MetaData associated with the stream
        private function clearHandler(event:MouseEvent):void {
            if (ns){
                trace("Clearing MetaData");
                ns.send("@clearDataFrame", "onMetaData");
        private function startHandler(event:MouseEvent):void {
            displayPlaybackVideo();
        private function onNetStatus(event:NetStatusEvent):void {
            trace(event.target + ": " + event.info.code);
            switch (event.info.code)
                case "NetConnection.Connect.Success":
                    publishCamera();
                    displayPublishingVideo();
                    break;
                case "NetStream.Publish.Start":
                    sendMetadata();
                    break;
        private function asyncErrorHandler(event:AsyncErrorEvent):void {
            trace(event.text);
        private function sendMetadata():void {
            trace("sendMetaData() called")
            myMetadata = new Object();
            myMetadata.customProp = "Welcome to the Live feed of YOUR LIFE, already in progress.";
            ns.send("@setDataFrame", "onMetaData", myMetadata);
        private function publishCamera():void {
            cam = Camera.getCamera();
            mic = Microphone.getMicrophone();
            ns = new NetStream(nc);
            ns.client = this;
            ns.addEventListener(NetStatusEvent.NET_STATUS, onNetStatus);
            ns.addEventListener(AsyncErrorEvent.ASYNC_ERROR, asyncErrorHandler);
            ns.attachCamera(cam);
            ns.attachAudio(mic);
            ns.publish("myCamera", "record");
        private function displayPublishingVideo():void {
            vid = new Video(cam.width, cam.height);
            vid.x = 10;
            vid.y = 10;
            vid.attachCamera(cam);
            addChild(vid);
        private function displayPlaybackVideo():void {
            nsPlayer = new NetStream(nc);
            nsPlayer.client = this;
            nsPlayer.addEventListener(NetStatusEvent.NET_STATUS, onNetStatus);
            nsPlayer.addEventListener(AsyncErrorEvent.ASYNC_ERROR, asyncErrorHandler);
            nsPlayer.play("myCamera",0);
            vidPlayer = new Video(cam.width, cam.height);
            vidPlayer.x = cam.width + 100;
            vidPlayer.y = 10;
            vidPlayer.attachNetStream(nsPlayer);
            addChild(vidPlayer);
        private function setupUI():void {
            outputWindow = new TextArea();
            outputWindow.move(250, 175);
            outputWindow.width = 200;
            outputWindow.height = 50;
            outgoingLbl = new Label();
            incomingLbl = new Label();
            outgoingLbl.width = 150;
            incomingLbl.width = 150;
            outgoingLbl.text = "Publishing Stream";
            incomingLbl.text = "Playback Stream";
            outgoingLbl.move(30, 150);
            incomingLbl.move(300, 150);
            startPlaybackBtn = new Button();
            startPlaybackBtn.width = 150;
            startPlaybackBtn.move(250, 345)
            startPlaybackBtn.label = "View Live Event";
            startPlaybackBtn.addEventListener(MouseEvent.CLICK, startHandler);
            clearBtn = new Button();
            clearBtn.width = 100;
            clearBtn.move(135,345);
            clearBtn.label = "Clear Metadata";
            clearBtn.addEventListener(MouseEvent.CLICK, clearHandler);
            addChild(clearBtn);
            addChild(outgoingLbl);
            addChild(incomingLbl);
            addChild(startPlaybackBtn);
            addChild(outputWindow);
        public function onMetaData(info:Object):void {
            outputWindow.appendText("Custom Prop : " + info.customProp);
            trace("Custom Prop : " + info.customProp);
            trace("Videocodecid : " + info.videocodecid);
            trace("Creation Date : " + info.creationdate);
Hope this solves your query and if still you have the issue then please tell the version of FMS and Player you are using.
Regards,
Amit

Problems with sent/sending folder, not able to quit??

I am having issues with my Mail 3.6 application recently.
Basically, Mail works perfectly for a few minutes after being opened (it checks new mail, sends mail, etc). Then, after a few minutes, the "Sent" folder turns into "Sending" with that spinning icon that indicates it is sending an email, when I have not sent anything.
Once this begins, I cannot send or save emails, or get any new ones. Furthermore, I cannot even quit the Mail application, and have been having to use the "force quit" option. Today, however, I have not even been able to get it to force quit all of the time, and have been having to shut down the computer.
This is getting increasingly annoying because every time I want to check for or send mail, I have to force quit or restart my computer.
Furthermore, within the "Sent" folder (before it changes to "Sending" unexpectedly), two recent emails are mixed up-- while the "subject" and "to" fields of sent emails look okay, when I click on them, the actual contents of the emails aren't what I sent, they are emails from 1-2 years ago. These two problem emails have been marked as junk by Mail.
Sorry for the long post, but there are issues with my "sent" folder that are making email exasperating and I do not know what to do! Does anyone know what is wrong with my Mail?

I seem to be having a similar problem.
Mail wont quit, unless by forced quit, and
Mail keeps getting old mail and the spinning wheel keeps turning forever.
did you find an answer?
Don

JCo Scenario with multiple Backend Systems

Hello @ all,
Is it possible to use multiple Jco destinations to multiple Backendsystems in one WD application?
The scenario is as following: I want to call different function modules on different SAP Backend systems?

Hi Mehmet
Alternatively you could try switching the destination through URL parameters
http://<Host-Name>:<Port-Nummer>/webdynpro/dispatcher/local/Example_Project/Example?sap-wd-arfc-useSys= WD_MODELDATA_DEST:SyB&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:
SyB
Check this link (I havent tried it though)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/651741f163f023e10000000a155106/frameset.htm
Regards
Pran

Unsent message with Invalid Sender Address: NOT in OUTBOX!

I have an unsent email that is stuck "somewhere", the result of accidentally entering the incorrect email address when modifying a mobileMe account. When it tries to send, I used to get "Sender Address Invalid". But there are no messages left in the Outbox to delete.
So now at the bottom center of the MAIL screen it says "1 Unsent Message". And every so often it'll try sending it ("Sending 1 of 1). But then it'll just stop -- with no messages.
Restarting the iPhone doesn't clear it out.
Where is this message sitting? And how does one zap it?

One thing that might help out.
Go to settings > mail, contacts, calendars > your mail account.
Then tap on smtp to view all your servers.
Make sure your primary server is on.
Then go through and turn on all your secondary servers.
Go back into mail and see if you have an outbox with an unsent message.
Hope this helps.

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.

IDOC sender: Error in Logical system name?

Hi,
In my current project, the IDOC sender system logical name is P2PCLNT100 but the SLD system name is P2P.
Its an IDOC to proxy scenario. At the receiver system side, the schemeAgencyID is getting populated at P2P and not P2PCLNT100, due to which there is an error on the receiver's side.
Following is already checked:
1. SLD has maintained the proper logical system name for the P2P system
2. The IDOC xml on the XI system has the sender port properly populated as P2PCLNT100
3. I have also debugged the program on the receiver side and fails at a point where it checks the logical system name from the database BBP_BACKEND_DEST.
On the receiver system, the followed error is shown as follows:
- <STANDARD>
<CONTROLLER />
<FAULT_TEXT>An error occured within an XI interface: SLD system P2P is not known Programm: SAPLBBP_BD_MAPPING_SAPXML1; Include: LBBP_BD_MAPPING_SAPXML1F1Y; Line: 96</FAULT_TEXT>
<FAULT_URL />
<FAULT_DETAIL />
</STANDARD>
Thanks in advance for the useful answers.
Sowkhya

Hi,
1. R/3 system's logical system name and SLD business system's logical system name has the same.
Is there a need to have the business system name in SLD to have the same name as R/3 system logical name?? As far as my knowledge goes, business system and logical system need not have the same name. Correct me if in the case IDOC sender scenario is different..
2. SLDCHECK shows following message:
Summary: Connection to SLD does not work
The issue still persists. Will SLDCHECK correct solve the issue?
Regards,
Sowkhya

Problem with automatic sending of IDOC immediately

Hi guys,
We are having probme with IDOC that is not being sent immediately... it is configured to send immediately, however it is sitting in Status 30...
Is there anything wrong with it? Is there any workflow that was not activated?
Thanks a lot!
Rgds,
mark

I think the processing mode in partner profiles is still set to "Collect IDocs" then IDocs will be in status 30 on creation and have to be dispatched to the receiver via a scheduled program using i.e. RESOUT00. please check the RESOUT00 is scheduled in the background?
This program would change the status of the IDocs from 30 to 03.
a®

B2B Scenario : Party Identifiers

Hi all ,
I have B2B scenario. ( IDOC to Mail)
My question is : Can I have more then one identifier for same Agency and schema pair?
XI is not allowing me to configure two identifiers for same Agency and schema pair. Is their any work around for this ?
Regards,
Sheetal

Hi Sheetal,
> My question is : Can I have more then one identifier for same Agency and schema pair?
Only if you setup another party. This can makes sense if you map parties in the receiver agreement.
> They have three partner profiles created in same R3. They will send IDOC from either of three to XI and I need to process those IDOCs and send a mail
I think you dont need parties here. Just process the IDocs messages - may be depending on value of field EDIDC40/RCVPRN - to a normal third party email receiver system.
Regards,
Udo

B2B scenario with IDocs, sender system not in SLD

Similar Messages

Maybe you are looking for