Transport Objects In Sap PI

[Former Member]

Hello experts,

I have the query while importing the TR in PRD .

I have created one TR in DEV for integration directory objects .

and also defined the path for business system.

I have successfully imported the TR in quality now same TR when iam importing in production

then it throwing the error regarding business system path

so what m i doing is correct...?

thanks,

Priya Sharma

[anand_shankar10 · Accepted solution]

Create another transport from Q and set the transport path from Q to P.

It should solve your problem.

Thanks

Anand

[Former Member · Accepted solution]

thanks for the reply

My question is,  what TR has created is in DEV that only will  import in to PRD .

In this TR Business system data is DEV BS so how this will convert into production BS ..??

There is no mapping between dev and prd for BS. the mapping is DEV to QAS and QAS to PRD.

thanks,

priya.

[anand_shankar10 · Accepted solution]

If you are talking about business systems then it should be of same name in all the environments.

Moreover before you start moving your transports from Dev to Qa to Prod, before that SLD transports should be done so that BS are already available and this is BASIS activity.

You can ask your basis team to do the assosiation of QA and PRD systems so that when you import the objects from Quality into prod they get changes to respective BS.

Regards

Anand

[Former Member · Accepted solution]

Hi Priya

Your solution is very simple and do not get confused by other replies.

In SLD , open the dev business system and add the prod business system as the target.

So DEV business system will have  two target business system

1. QA BS

2. Prod BS

Once you have done the target mapping in SLD, re-import the transport from transport queue.

This will work.

[Former Member · Accepted solution]

Hi Priya,

What Indrajit saying is right. Also consider below point.

If you have two SLDs (One for Dev and QA and the other for Prod), Create Dev business system in Prod SLD aswell and map it to Prod Business system.

Thanks

Jayaram

[Former Member · Accepted solution]

Hi Indrajit ,

Yes I agreed with your points , and that is helpful too.

But this is not standard one right ...?

thanks,

Priya

[Former Member · Accepted solution]

Hi Priya

Yes that is the standard way of doing this. Whatever object we released it should be released from DEV.

Then we need to import it QA first , once we do that it will go to PROD import queue and we import that in prod.

This way all the three system will be in Sync.

We should not release any object from QA because in that case the DEV and QA will not have the same version of the objects.

[Former Member · Accepted solution]

Hello Indrajit,

So u mean to say is Business System mapping is

BS_DEV-->.BS_QAS

BS_DEV-->BS_PRD

Is the standard way ....?

thanks,

Priya

[Former Member · Accepted solution]

Hi Priya

Yes that is the mapping. We need to create 3 groups in SLD also for each environment.

[anand_shankar10 · Accepted solution]

No Its not this way as far as I have observed with various clients. (But yes such configuration is possible.)

it should be DEV-- to QA and from QA to Prod.

Just to keep the objects in Quality in synch with production because either its SIT or UAT, its done in Quality and DEV environment is most unstable.

Thanks

Anand

[Former Member · Accepted solution]

I agree, this is NOT a standard. It is definitely possible to do so and there is nothing wrong with it, but it is no standard. By default, objects cannot be modified in QAS, anyway, so export from there does not change anything. Furthermore, you can set up your transport tracks such that the system imports to Q and exports from there automatically, just as in ABAP systems.

You problem has two solutions:

1) Change SLD and enter P as transport target from D or

2) Create a new export from Q and import to P in order to match SLD transport config.

The choice is yours, both are possible and depend on strategy and personal preference.

Regards,

Jörg

[Former Member · Accepted solution]

Hi Anand

Yes QA is used for UAT or SIT and is most stable rather than DEV. But in many of the projects you can not edit ESR objects in QA.

So if you found any mapping defect during testing in QA, you need to change the map in DEV

and then transport it to QA and continue testing.

If we can change and transport from QA, then what is the point of having development environment.

[anand_shankar10 · Accepted solution]

Thats what my point was. Once testing is confirmed and approved in QA then we move it to production and so no chances of any edit on the tested object. hence Q to P. If we make any movements directly from D to P there may be chances that we have two different version in Q and P.

This is my understnding from my working experience. I am not raising my fingers on anyone.

Thanks

Anand

[former_member184720 · Accepted solution]

Agree with Indrajit.

If we make any movements directly from D to P there may be chances that we have two different version in Q and P.

>>>Just to make it clear.. you'll be importing the same transport in QA and Prd.

So even if you make changes in your development system it will have zero impact on production unless you export them again which'll be a new TR..

[Former Member · Accepted solution]

Hello Everyone,

Discussion is going on different Way .

Earlier I  have the query that .

Is it Standard Concern that for Business System Grouping Mapping

BS_DEV-->.BS_QAS

BS_DEV-->BS_PRD

If not then what...?

[Harish · Accepted solution]

Hi Priya,

If you are using CTS+ transport then objects are attached from Dev and transported till Production. In this case the transport paths in SLD is

DEV -->> QA

DEV -->> Prod

But if you are using file transport and transporting the ID object from QA (which is not common) then you need to define the transport path as

DEV -->> QA

QA -->> Prod

But i would suggest to go with below approach (works in all cases)

DEV -->> QA and prod

QA-->> Prod

So for Dev target is QA and Prod. for QA source is Dev and target is Prod.

regards,

Harish

[former_member184720 · Accepted solution]

Hi Priya - I don't think there such standard.. It's up to the organization to decide such process

All you need to care - is the consistency among different environments.

If you would like to avoid exporting the objects multiple times then simply follow

Dev -> QA and prod

[Former Member · Accepted solution]

Ok thanks all ,

Closing the thread here with knowledge that

DEV->QAS

DEV->PRD is fine

thanks,

Priya

[Harish · Accepted solution]

Hi Priya,

Please also close the discussion by choosing the appropriate option.

Regards,

Harish

[Former Member]

Hello Priya,

what transport targets have you configured? Do you transport from Q to P or from D to P? Have you configured that transport target in production SLD? The path is evaluated in the target system.

Regards,

Jörg

[Former Member]

Hello Jorg,

Transport path is configured as

DEV-QAS-PRD

When I imported the TR in QAS  that TR is visible in PRD .

But when I am importing in PRD getting the error that

Business system (DEV) is not found in SLD .

I have mapped  Business systems

DEV ::

Target QAS business system

QAS:::

Source DEV BS

Target PRD BS

PRD:::

Source : QAS

what should be the solution .

thanks,

Priya

[Former Member]

Hello Priya,

probably you configured the transport path such that transports will be put from DEV directly into PRD import queue. In that case you have two options:

1: Configure transport path such that transport is put into PRD import queue only after export from QAS.

2: Configure your SLD such that transport path is DEV-->QAS and DEV-->PRD.

Option 2 you can also execute now, so configure your SLD and re-execute the import. For option 1 you'd have to repeat the transport. It looks like your DEV system is not available in your PRD SLD, so you'd probably have to transport (or synchronize) your SLD first. It should always be complete and contain all systems in your landscape. Then update the transport paths in SLD.

Regards,

Jörg

[engswee]

Hi Priya

In the SLD for your PRD system, in the Business system for DEV, you should have Target as PRD.

Rgds

Eng Swee