on 04-27-2016 6:58 AM
I am working in a project with multiple slds, there are three slds, one for dev, one for qas and one for prod
I have to do transport from DEV to QAS.
1) where should I create transport target? I have three SLDs, in DEV or QAS or PROD?
2) the swcv that I created are only in SLD DEV, should I import them to both QAS SLD and PROD SLD?
3) the business sytem of PI DEV is only in DEV SLD, business system of PI QAS is only in QAS SLD and finally the business system of PI PROD is only in PROD SLD. should all the sbuiness systems shoulf be available in all three slds
I have done the export of ESR objects
1) My SWCV had some RFCs in it. I transported them also PI QAL. Should RFCs be instead imported from ECC QAL?
How do I transport ID objects?
2)I have a business system and business component? Do I have to transport them one after the other?
3) I have fifteen integration scenarios and 26 com channels. Can I transport all of them in one shot?
Regrds
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1 - If it is a standard RFC no RFC transports required. For a z RFC this will be an ECC transport out of the purview of PI transports. PI ESR should have the RFC transported so you are right.
2- you can do a export import of all objects in one shot but in this case as this is a first time transport I would save : transport business systems and business components first so that you can confirm that the transport target mapping is working. Subsequently you can export import all remaining objects in a single shot or you can split it into multiple tpz files if you want to segregate by scenario.
Hi Midhun,
The approach is -
1. Create separate Product.SWCV,TS and BS in DEV , QA and PROD system.
2. Then export DEV components from DEV system and download the zip file.
Now import this to QA and PROD system.
3. In BS under transport tab assign target system as per your transport route.
Thanks,
Apu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1) In QAS and PROD
2) Yes
3) If your transport route is always DEV > QAS and DEV > PROD, then you only need PI DEV Business system in both QAS and PROD. This is required for you to be able to do item (1) above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Eng
Thanks for the reply. Yeah, my rpute is like that only, always De - Qal, and then qal -- prod
I have two more doubts
1) Right now I have to transport from DEV to QAS only, so I have to create transport target only in QAL SLD, right?
2) the business system that they created for ECQ in qal is not linked to the PO business system. can it be edited and added ?
And by PI Dev business system, you mean both the business systems of DEV ECC and DEV PI, right
Hi Midhun,
1) Create the transport targets in DEV SLD
For ex: In Dev you have business systems Test_D / Test_Q / Test_P.
For Test_D set the transport target group - QA and transport target as Test_Q
Test_Q set the transport target group - Prod and transport target as Test_P
2) I hope you have created technical and business systems for ECC system in PI SLD.
we don't need to link ECC business to PO business system both are unique.
ALE /IDOC configuration will be used to set-up connection between PO and ECC systems.
Refer the below blog for the detailed procedure to be followed for SLD transports
SAPTechnical.COM - Transporting objects in PI
Regards
Bhargava Krishna
Yes, this can be done.
Once this is done, you would need to create a group for Dev and assign this to the corresponding Development Group.
What is your long term SLD strategy btw?
What version of PI are you on?
I would suggest you enable SLD auto synchronization to enable this for the long term.,
Regards
Bhavesh
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.