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

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.

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.

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

Sender System Info

Hi,
We have changed the Sender system details for existing Interface. But not reflecting in the Receiver System where the Message is passed thru PI
regards,
John

Hi Jhon,
1) Clead the Cache - tcode- Sxi_Cache - go to Run time ther go for Complete Cache refresh
2) Select the Business System in ID ( Object Tab ) Activate it....
3) Tcode- Idx2 clear the Meta data or Update the respective IDOC Meta data
Regards
Agasthuri Doss

HOW TO LOOK AT SENDER SYSTEM IDOCS

hi friends,
Scinario :recieving the idocs(inbound)
we know that the idoc nos. which is send from the sap system to the reciever sap system will change.
suppose the sender system is having idoc nos as 10002
the same idoc in the reciever system will have, let us say 20001
we can view the idoc nos.which we have in our system ie recieving system.
now, my problem is how to check the corresponding idoc's in the sender system.
ie in our example 10002.
please help.
Regards,
Murali G.S.A

hi DJ,
thanks for responding.
in my program there is requirement to display all the corresponding idoc's of the recieving system.
can we do this ??????????
since , in a report we can display things which are there in system (in the form of tables..)
but in this case as u said there are generated by system.......
but is there any way to track these numbers..... will they be stored in recieving system ( the idoc nos. of the sender system).....
Regards,
Murali G.S.A

JDBC to Idoc scenario - change of logical system name

Hi,
I have a JDBC to idoc scenario that worked. Now i had to change the logical system name from my sender system from ABC_123 into ABC123 in the SLD (Business System - Integration - Logical System name). I did so and also refreshed my Cache.
Afterwards I started the process, but it failed in the Receiver system. The idoc is correct expect of the partner name. My receiver system expect ABC123 - as I changed in the SLD - but PI send ABC_123.
If io look in SXI_CACHE - Services my Business System still got the "old" name (ABC_123).
Did i miss something resp. how can i load the current configuration from SLD?
Thanks in advance
Michael

Hi Michael,
Again Import the changed logical system in the Integration directory of you PI system.
And check the scenario (Sender Agreement, Receiver agreement ) what system they are reflecting.
If they are showing old system then you have to replace the business system in all the scenario.
Edited by: Rajhans Abhay on Jan 7, 2010 3:14 PM

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

IDOC: Status (Error/Success/information)report to Sender system

How would one send a message(error/success/information) to the sending(external) system to inform them of the statuses of the messages they've sent to our SAP system?

Hi Baumann,
you have an option called Audit reporting in which you can have the status of idoc at sender side.read the following.
Setting Up Audit Reporting
In the default behavior, after an IDoc is dispatched to a destination system, the sender does not know the state of the process on the destination system. You can configure the system, however, for cross-system reporting. You must model the ALEAUD message between the systems.
Two programs enable cross-system reporting.
1)RBDSTATE. This program is scheduled to run periodically on the destination system. It reports the status of incoming IDocs to the sending system, using the ALEAUD message and ALEAUD01 IDoc. This status information is recorded separately from IDoc status information in the audit logs.
2)RBDAUD01. This program is executed on the sending system. It analyzes the audit log and displays the output as a report.
The RBDSTATE program returns the following statuses, from the receiving to the sending system.
RBDSTATE Is Run on the Receiving System
Status of IDoc in receiving system     Status reported to sending system via ALEAUD
53 (Application document posted.)     41 (Application document created in receiving system.)
51 (Error: Application document not posted.)     Status 39 (IDoc is in the receiving system.) This status is repeated each time RBDSTATE is run, as long as the IDoc remains in status 51.
68 (Error: No further processing.)     40 (Application document not created in receiving system.)
reward points if helpful,

IDOC send message to third party system

Hi,
I got the below scenario,
1) Data came from 3rd party system through EDI
2) Because the material is not there in SAP system it didn't create sales order
3) IDOC is errored out
4) How to inform the 3rd party system through an IDOC or message that IDOC got errored out?
Thanks
anikaushi

so you mean to say that we can trigger workflow sothat those people or email.
Yes, for error handling and resolution
Can we send the eror message to 3rd party in the form of IDOC immediately afer error IDOC is created in SAP?
You could, but I don't see the point and you'd have to map it. Your EDI system should provide an FA back to the sender upon receipt so that it knows the message was received. The error should go to the person or group that would handle the issue if it's an SAP-related issue such as a master data or config error. I don't know your system/setup, but it doesn't make sense to send a material error back to the sender system if someone is going to fix that in SAP and then re-process the IDOC (and trigger an order confirmation).

Configuration needed for non-SAP system as Idoc sender

Hi,
We have a need to connect a non-SAP system which is sending an Idoc to XI. I understand that on the sender side, we need to create a tRFC port from the sender system with the server address of the Integration as the target host?
My question is on the PI side, are the configurations the same as a SAP system, i.e. maintaining the port in IDX1 and getting the metadata in IDX2 or will it be different?

In PI, you will need to create a port in IDX1 with the same port name as the Idoc control record when the Idoc comes from the non SAP system.
As you cannot load the Idoc metdata from your actual source, you will need to copy the Idoc metadata from a actual SAP system or from the port of another SAP system in IDX2
Also, in the Business Service / System, make sure that the logical system name is maintained as per the Idoc control record of the source.
Regards
Bhavesh

Can IDoc sender and receive system be the same client?

thanks.
I think one client can't assign to two logical system.so?

Can IDoc sender and receive system be the same client?
yes
Regards,
Prateek

IDOC in sending system

hi friends,
When SAP r//3 in sending system for transforming the IDOC...
How the IDOCs are posted ?
whether mannual or automated?
if automated what is the process.

How the IDOCs are posted ?
check this link for ALE setup http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
whether mannual or automated?
Depends on the setting in partner profile. If transfer immedialtly is enabled then it is automatic elase if collect idocs is selected then it is mannual

Idoc Sender Configurations

Hi,
Our requirement is to do Idoc to File scenario in which what are all the configurations that are to be done in R/3 and as well as in XI server.
regards,
Kishore

Hi Kishore,
Please go through /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
also i give a quick checklist, chk it out.
1)Create an RFC destination to XI in the sender SAP system using SM59
2)Create a transactional port to XI using the RFC destination created in the above step
3)Create a Partner agreement usign transaction we20 and port using we21 in the sender SAP system
4)Create a logical system using transaction bd54 for the partner agreement created in the above step
5)Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name
6)Create an RFC destination to the Sender SAP system using SM59
7)Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
8)Create SLD entries(technical and business system) for the sender SAP system.
In IR , import IDOC metadata, create ur target XSD , create ur Message Mapping , Interface Mapping, thats it.
In ID, import ur sender R/3 system & receiver systems, U dont need a IDOC sender CC , so only File receiver CC is reqd. Now create a receiver determination, interface determination & receiver agreement ,activate & ur done.
Use WE19 , select an IDOC and do an outbound processing and u shud see the IDOC in XI.
Rgds
joel
Edited by: joel trinidade on Feb 23, 2009 2:44 PM

IDOC Sender Adapter acknoledgements

Hi,
we have a scenario IDOC -> PI => HTTP Plain (ASync) .
I have configured the Message Type ALEAUD and AUD1 in sender system.
I also have the ACK_SYSTEM_FAILURE = 1
Now , when I get a permanent error from the HTTP receiver adapter. The acknolegement message falls in error .
The message says that the Receiver component (HTTP system) canot be converted into an ALE logical system.
What is missing... I thought we didn't have to define the external system anywhere except as a Business Component in Integration Builder ... ?
Thanks.

Hi,
thanks... it worked, now the ALEAUD IDOC is sent back to ERP but the status of the outbound IDOC is not changed.
In fact in WE02 on ERP , the message is that the EDI interchange accord is not created for the thirds party's logical system (that's the one that had the http error) ...
Now , since I'm planning to have possible 50 third party systems, I'm hoping we don't have to define a accord for each third party.
Can't it just be set to some generic value ??? or done more elegantly ... I thought this should be a lot simpler to maintain.
Thanks.

Change Idoc Sender system

Similar Messages

Maybe you are looking for