What are the Transportable and Non-Transportable Objects IN pi 7.1

[Former Member]

Hello Experts,

What are the transportable and non - Transportable ABAP and non-Abap objects in PI 7.1:

In SLD

Integration Repository

Integration Directory

Abap objects(Code)

Thanks in Advance

Rajeev

[Former Member · Accepted solution]

Hi!

When you configure CTS+ for use with PI 7.1 at least SPS06 (and applying some patches, best is to apply the latest patches available) every kind of object can be transported using CTS+:

SLD (every object type where you can find an "Export" button)

ABAP Repository, DDIC and customizing (as known)

ESR (all kinds of objects)

ID (all kinds of objects)

And the best is: If you like you can pack alle these different things into one transport request and transport/deploy it through you landscape form dev to qa and prod.

By the way: There is a howto guide for configuring CTS+ for PI 7.1

Regards,

Volker

Uuups. Forgot to say:

The only exception is that deletions of SLD objects currently cannot be transported using CTS+

Edited by: Volker Kolberg on Jul 1, 2009 2:45 PM

[former_member192295]

Hi,

In R3 or SAP we can transport any type of object from one system to another system. But this object should not be saved in local object (ABAP point of like program, function module etc), Locally saved object we can't make transport request.. In XI/PI we can transport all objects (SLD, IR & ID).

[Former Member]

Hi Guys,

So we can transport all Integration Directory Objects? such as Communication channels with parameters, receiver Determination, Interface Determinations, sender aggrements and reciever aggrements even ??

All objects what ever developed and configured in Development system are transportable and ready to test with out any manual work/configuration in any other enviornment?

Thanks

Rajeev

[Former Member]

Hi!

In general YES.

But for security reasons some attributes of communication channels and receiver agreements are not transported (controlled by the respective templates). For example for RFC Receiver Channel you have to maintain the Server Attributes and User Credentials manually after import in target system.

Additionally: For Integration Directory transports a change list is automatically created in the target system that has to be activated in the target system before the objects become active and usable.

We have configured CTS+ for a PI 7.1 and it works very well (for SLD, ESR, ID and ABAP part).

Regards,

Volker

By the way: All the constraints mentioned above also come true if you use export/import for transportation instead of CTS+