ECC Receiver system config change: Which way is good?

[Former Member]

Hi,

I have 120 plus interfaces as IDoc receivers/sender running in production.

The existing ECC system [SAPabc] will be down for patch updates and we need to point different ECC system [SAPxyz].

Please let me know which way is better to handle this situation.

a) Change each and every receiver channel details with SAPxyz and receiver agreement in the ID component and once revert back to SAPabc once it is up and running.

b) Change the logic system name in the SLD and point the existing SAPabc system details to SAPxyz and rever back once the SAPabc system is back and running.

Much appreciated if I get the steps to change the system details in SLD. [not much worked in SLD ]

Thanks

Ray..

[former_member184681 · Accepted solution]

Hi Ray,

For receiver IDoc scenarios, you can perform this change really easily in a single place. Your receiver IDoc Communication Channels point to some particular RFC Destination, that is defined in sm59 transaction of your PI ABAP stack. Simply go there and change connection details from SAPabc to SAPxyz (just the details, do not change the connection name in CC configuraiton). Thanks to that, you centrally change all the settings.

For receiver Proxy scenarios, this might be a little bit more complicated, but still same can be done (changes only in sm59), assuming that you use the Addressing Type = HTTP Destination in your receiver CCs.

Hope this helps,

Greg

[Former Member · Accepted solution]

Hi Greg,

Thanks for the quick response.

So you mean to say if I change the SM59 details in PI ABAP stack with the new SAPxyz details, interfaces will flow to the new SAP system.

Do you see any cautions points to be noted before changing the details in SM59?

Thanks

Ray..

[former_member181962 · Accepted solution]

Hi Ray,

There may be other places also to be changed in your case.

Check the below wiki.

http://wiki.sdn.sap.com/wiki/display/XI/ConnectionSettingsbetweenECCandPIsystem

However, i have few questions.

1) How long is this stop gap arrangement?

2) What happens when the main system is live again? how does the system get updated with the postings that happened in its absense?

Best Regards,

Ravikanth Talagana

[Former Member · Accepted solution]

Hi Ravi,

Thanks for the link.

We are expecting the stop gap arrangement for 10 days. Later the old system will be back and running.

The server change is there only for the quality environment. Testing will be restricted to business critical interfaces only.

I hope using TDMS, data migration will be done.

As per the link which you have shared, we may have to create a new Business system in the SLD and assign the same in communication channels and may have to recreate all the receiver agreement.

I would appreciate if you any quick fix for this temporary arrangement.

Thanks

Ray..

[former_member181962 · Accepted solution]

Hi Ray,

I do not thikn you need to create a new business system.

You just need to change the technical system that is aatched to the current the business system in SLD.

And then change the settings in 1)RFC destinations 2) IDOC receiver adapters 3) Partner profiles etc.

Best Regards,

Ravikanth Talagana

[baskar_gopalakrishnan2]

Try to do the option b. refer this link for configuring business systems in the SLD.

http://help.sap.com/saphelp_nwpi71/helpdata/en/ae/e3bd4f6b61e146ad1384954ecabb41/content.htm

[Former Member]

Hi Baskar,

Thanks for the link.

Once the Business system is added in SLD, i have to import in ID component.

In this case, I may have to recreate the receiver agreement for each scenario right?

I have more than 120 plus interfaces with different channel name and receiver agreement even though SAP details are same.

Please let me know a quick method to point all my interfaces to the new SAPxyz system and this need to revert back to older system details once the SAPabc system is ready for use.

Thanks

Ray.