What objects need maintaining when transported between systems?

[Former Member]

I have posted an earlier thread and now have information as to how Business Systems can be configured when transporting objects between e.g Development and Test environments.

What about other objects that have information specific to the environment that they are in. For example:

File adapters: What happens to the directory name? Does it remain the same or is it removed in transport?

IDoc adapters: what happens to the RFC destination?

Receiver agreements: what happens to the header mappings e.g. if the Receiver Service has been configured to point to one development system, will it still point to the same system in Test, or will it have been cleared?

Is there a check list of things that need to be manually adjusted when a objects are transported between systems?

[Former Member · Accepted solution]

> I have posted an earlier thread and now have

> information as to how Business Systems can be

> configured when transporting objects between e.g

> Development and Test environments.

>

> What about other objects that have information

> specific to the environment that they are in. For

> example:

>

> File adapters: What happens to the directory name?

> Does it remain the same or is it removed in

> transport?

>

Generally in my experience what i have seen is that some times the file path and the filename are blank after the transport but the rest of the parameters are always consistent. So you will have to check only for these parameters.

> IDoc adapters: what happens to the RFC destination?

you will have to manually change this in the channel.

> Receiver agreements: what happens to the header

> mappings e.g. if the Receiver Service has been

> configured to point to one development system, will

> it still point to the same system in Test, or will it

> have been cleared?

Not sure what you mean by this ? but what ever values you enter in the dev env. the same values will be present in quality env. You might have to change it manually based on your system landscape.

>

> Is there a check list of things that need to be

> manually adjusted when a objects are transported

> between systems?

Some things to take care of during transportation:

There are no empty or inactive change lists against any user id in IR/ID. If there are then please activate them by assigning it to your name befor transporting.

Import one scenario at a time, as you will be able to activate only one scenario at a time in ID.

Verify all the communication channels, though most of them are always correct its prudent to recheck them.

The value mapping tables should also be transported from one env. to another.

The communication channels start polling by default once you activate the scenario. You might have to stop them in RWB, if you don't want them to process msgs immediately.

Check that all the partner profiles/RFC destination are created in the test/acceptance/production environment.

Cheer's

[Former Member]

Hi,

refer to the blogs

Transporting objects in XI

/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi

/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation

/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview

/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms

You need to traansport the objects in SLD if you are using multiple SLDs.

Have a look at this doc on handling SLD. Very useful.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d64...

Also, the blog

/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi

Regards,

Kumar.

**reward points if helpful!!!

[Former Member]

Also, Ref this blog regarding SLD preparation before transport.

/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation

Regards,

Sreenivas

[Former Member]

Hi,

In SLD need to create group to maintain the systems like DEV>Quality>Prod. While transporting the objects from DEV to Quality the business sytems replaced as per pointed in your Group which is existing in SLD same for QA to PROD.

File Adapters : You need to modify manually the directory name.

IDoc Adapters : You need to modify manually the RFC destinations as per your sceanrios. In DEV,Quality & Prod need to create separately in between the systems

Receiver Agreements : Header Mappings would be present same and the Receiver service will point to Quality system ( Based on Group Creation in SLD).

Regards

Veera

"Reward Points Found as Needfull"

[Former Member]

Hi Anthony,

When you transport ID objects from Dev to Test, the information in the communication channels like the directory, url, userId, pass etc which are specific to the environment will be cleared automatically in Test evironment. You need to specify all these details and then activate the changes.

RFC destination should be created manually in Test or prod envn.

Receiver agreements need not be changed. It will point to the same system in Test.

Regards,

Sreenivas