Transport SWC to Prod sld

Hi,
This is a simple requirement but not sure why its getting so complicated, i have done lot of search on SDN and got the solution, but unable to execute it.
Basis has created a swc in Dev SLD and i imported it into my ESR, created my objects and exported the TPZ file. (Transport mechanism is FILE transport)
In production SLD, we need to import the created software component to maintain the same version, else if we create directly in Prod SLD, and import my .TPz file, it will throw a version error.
The software component is exported from the Dev SLD, but when basis is trying to import it under "Software Components", the option "import" is not present. All the roles are assigned and checked, but still, the import option is not present.
Thanks
Saiyog
PS: There are 2 SLD, one for Dev and Q, and one for Prod and they are not on the Pi Server.

Hi
May I know what do you mean by version no..?
Thanks

Similar Messages

How to get DEV Integration Server into Prod SLD?

Hello,
in a two-tier landscape I need to define transport targets in SLD. Both PI syetems have their own SLD. In each SLD there is just the Integration server of the corresponding PI system. How to get the DEV Integration Server into PROD sld? Manually?
Thanks,
CHRISTOPH

Hello Seshagiri,
that is what I wanted to know. So there seem to be two possibilities:
- Creating the DEV Integration Server in productive SLD manually
- Exporting the DEV Integration Server from DEV SLD and import it into productive SLD.
I tried importing / exporting SLD content some time ago. AFAIK there is no exporting single technical / business systems, you can just export all the content together from a SLD?
Thanks,
Christoph

Transport package to Prod

I have found an issue with transporting package to Production system.It is necessary to transport the package itself to QA before you transport any thing assign to this package to QA. But I observe the transport went to production system without transport package to Prod first.
Could some one explain this?
And also, could I transport every thing which assigned to this package together with transport the package?
Thnaks a lot!
Jason

Did you check with SE80 if the package exists in Prod? It seems quite abnormal that the transport has gone without importing the package first ...
Best regards
GFV

Transport targets for single SLD for (Dev & QA), another SLD for (prod)

Hi All,
My landscape is
systems: DEV ( Dev & QA )----->PRD ( prod ).
i.e, Development and Quality in one sys DEV , Production in the other PRD.
i have two business systems in DEV :
1) BS_Dev1
2) BS_Dev2
i created a group for these , say DEV_GROUP
As Dev and QA are under one SLD, there is no need of quality group right?
so i have created business sys in DEV:
which points the target business systems for BS_Dev1 & BS_Dev2
1) BS_Pro1
2) BS_Pro2
and created a target group for these, say PRO_GROUP
So my question is , as there is no QA in landscape
this would be the procedure to create the Groups and target systems for the objects of DEV (Dev & QA ) to PRD.
And then transport the objects from DEV (SLD -> Administration -> Content -> Export)
to PRD (SLD -> Administration -> Content -> Import).
Correct me if i am wrong.
Thanks
Sai

Hi SAI,
Check the [LINK|http://www.****************/Tutorials/Basis/Transport/Index.htm]
came across few blog on PI transport process..hope it helps:
/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
Regards,
Naveen.

Transport object from Prod to Dev

Hi Folks,
Developer wants to restore a version of SAP "Smart Form" from production to Dev system as the one in dev system lost some modifications. In Dev system, it was always showing the current active version and there are no traces of old versions or i am not looking in the correct place.
In this particular landscape, there is no transport path between Dev and Prod. We manually FTP transports (Cofile and data files). Could you please, guide how to create a transport with a "Smart Form" from production to dev. After searching the forum, i could find only one posting talking about opening the production system and create a transport. I can open the production system for a brief period and create a transport but i am seeking for help if any one has done this before.
I am not sure if i have to crearte temporatry transport path.
Thanks a lot in advance.

Hello again rk_007
on this case, you can create a 'temporary' transport route from Production to Development (temporary on the sense that you can delete it afterwards. By all means, this route is just another normal one). By doing so, you will be able to create a transport request in the Productive system, release it and import it on the other system.
You just have to go to u201CSTMS --> Overview --> Transport Routesu201D, create the route you want and distribute the new configuration. Once that the transport is done you can delete that transport request.
Do you know who to manage transport routes? It's not difficult, you need to go to STMS transaction, click on the routes button (or Shift + F7), go on 'Edit' menu, then 'Transport Route' option then 'Add Transport Route'.
You can find everything explained here:
http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a1df7acc11d1899e0000e829fbbd/frameset.htm
Further and valuable information can be found here:
http://help.sap.com/saphelp_nw04/helpdata/en/57/38de0c4eb711d182bf0000e829fbfe/content.htm
http://www.sap-img.com/basis/transport-request-within-same-server-different-clients.htm
http://wiki.sdn.sap.com/wiki/display/EmTech/TMSassigningclassorpackagetoroute
But there is another option where the creation of a transport route is not needed, which might fit your need (and which I believe it's the FTP option you're already using):: you can create the transport request in Productive system (from SE01) and instead of creating a Workbench transport request, create a Transport of Copies. Once that the request is created, you can add the objects you need manually and release the transport request. The datafile and cofile will be created in the data and cofile directories of the transport directory of the Productive system; now you will have to copy manually (at operating system level) the datafile and cofile of the transport request to the transport directory of the Development system, and go to u201CSTMS --> Overview --> Imports --> double click in DEV --> Extras --> Other Requests --> Addu201D to add this transport request to the import queue of DEV system. Now you will be able to import it into DEV, avoiding the creation of the transport route from PRD to DEV.
Best regards,
Tomas Black

SWC removed from SLD by mistake

Hi,
I have removed my SWC from SLD. How can i retrieve it in the SLD??? It is now not available in the Product also. But that SWC is still available in the IR and all the scenarios based on that SWC is still working fine. I cleared the Cache also and it is still working. Just that it is not listed in SLD.
Regards,
kanan

Kanan,
You will have to recreate the SWCV in your SLD. When creating the Software Component you will have to make the change in the Software GUID so that the SWCV in the SLD and the IR are in synch with each other.
Go to SLD --> Administration --> Content Maintenance -->
Subset: Component Information --> Class: Software Components Versions , select your SWCV whioch you have newly created and then chantge the GUID to the same GUID as in the IR.
Also take a look at this guide,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/adb8f911-0d01-0010-82b9-a8134d7d89d5
Regards
Bhavesh

Unable to create multiple transport target groups in SLD

We have multiple R/3 QA systems but just 1 XI QA system and we need to test interfaces with all R/3 QA client at the same time. My XI development team has asked to explore whether its possible to create multiple target systems.
Currenlty R3_dev has R3_QA1 as target business system, we would like to add R3_QA2 as target system for R3_dev.
There is a "add/change" option in Transport tab and there is a grid which seems to imply that multilple entries are possible.
I have added R3_QA2 to the Group "Qa_Bus_Group" and was able to replace
R3_QA1 with R3_QA2 however I was unable to create multiple target systems.
I was wondering if anyone ran into this issue and any suggestions are welcome. Thanks in advance.

Hi Syed,
           You can create multiple target systems only for different business system groups.If all the business systems like R3_QA1,R3_QA2, R3_QA3 belong to the same business group "QA_BUS_GROUP" , then you can have only one among the three system as target.
           So R3_DEV can have only one system as target either R3_QA1 Or R3_QA2 or R3_QA3 since they belong to the same business group "QA_BUS_GROUP".
            If there are three different business system groups then you can have 3 target systems that correspond to their respective business system groups ,in this case source business system can be assigned to the 3 target systems that belong to different business system groups .
           Since that is not the case with your scenario, you cannot create multiple target systems.
Regards,
Laawanya

Regd. Detailed steps for creating BS,TechSys, SWC etc in SLD

Hi Experts !
Can some one share a good detailed document on the steps performed in SLD like creation of product, software componet and how to create and link the Technical system and business systems. What are the various dependencies to be maintained and what autorisations to be given to the users to access business system created in SLD.
Regards,
Srinivas

Hi Srinivas,
You can follow below links.
You can search on SDN can get more information if needed.
http://help.sap.com/saphelp_nw04s/helpdata/EN/31/f0ff69551e4f259fdad799a229363e/frameset.htm
http://www.sapag.co.in/HOWTOLOGINTOXI.html

Development and Production SLDs

We have completed Development and testing of XI objects and are at a stage to transport the objects to Production. We have two SLDs for XI, one for Non-productive systems and another for the Prod system. As regards to SLD entries for transport to Production, I though the following is the process
1. Create Production Business systems in DEV-SLD putting them in the right Business group
2. Export DEV-SLD entries
3. Import the file into PROD-SLD
4. After go-live only delta SLD entries would be exported and imported into PROD-SLD
In the following Weblog, /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation, Yuvaraj talked about SLD data supplier bridge from Dev SLD to Production SLD. Is this absolutely necessary? With the bridge operating, what happens if somebody deletes a business system by mistake in Dev SLD?
Any inputs would be appreciated and rewarded

Bhavesh,
My reason for not having prod entries on Dev SLD is that if Prod Entries are going to be on dev SLD, then why have a separate SLD for Prod itself?
My logic for this would be during development, create all the Production Business Systems in DEV-SLD and transport them to PROD-SLD. At runtime system uses Prodcution-SLD. I guess the differernce is design time vs Runtime.
But once again, SAP recommends a single SLD and so when the landscape contains multiple SLD's there are no rules on how to go about this and so either way things will work fine :-)
SAP's recommendations seem to have changed off late. Though in online help they have again and again mentioned that one SLD is recommended, I do know that some internal SAP Consultants recommending separate SLDs for non-productive and productive purposes. There are also documents on Service market place providing information on how to set-up two SLDs for productive and non-productive purposes.

Error while importing ID component

Hi Experts,
I am getting following error while importing one of my configuration scenarios in PROD.
"Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.wxip, string], target element type: SAP_BusinessSystem)"
Regards,
Miten.

Hi,
In my landscape we r not having QUALITY environment for XI. So th current scenario is between QUAL(BS: WSQCLNT201) of R/3 and DEV(BS: XIDDEV) of XI.
Now I have created two BS in PROD SLD viz. WIPPROD(R/3) and XIPPROD(XI).
Can u tell me how to create transport groups and transport targets in PROD SLD?
regards,
Miten.

Transport issue with SLD

Hi,
On PI 7.1 EHP 1.
Trying to transport an interface to Production, Prod has its own SLD. When the Basis team import the change on the Integration Builder it is failing and giving error:
Communication Component | SEDCLNT316: Obligatory transport target for business system SEDCLNT316 not found in System Landscape Directory
I have checked the SLD for the Business System SEDCLNT316 and it is there, also the transport groups for Quality and Production are set up on it. I can't see anything wrong with the SLD.
Can someone help me out?
Thanks
Gareth

Hi,
I have seen this behaviour before. We fixed it by making sure the transport target is complete for the business system both in the source-SLD and the Prod-SLD (that it contains both Dev, Tst and Prod business system name in both the SLDs). Then export your objects again, and it should be able to import correcly to target system.
I usually find it easiest to have all systems available in all SLDs, not just the systems relevant for the spesific SLD environment (i.e. Dev or Tst or Prd).
-Kenneth

Two SLDs with separate XI-systems behind - transport content

Hello,
we have two SLDs, one for dev. Xi and one for prod XI.
So per SLD only one XI is known.
On SLD dev we implemented all required R/3 systems and included the transport groups to the systems and the transport connection (dev. syst to prod. syst).
So here the prod R/3 has as connected XI the dev XI!
Now we want to move the content of the dev SLD to the prod SLD.
What will happen to the related XI system in the business systems.
Do we have only have to change them in the destination prod. SLD?
Best regards
Dirk

Hi Shankar,
thanks for the detailed work on my question.
Unfortunately it wasn´t me who had to organize the environment.
Customer made the installation and then was asking for external consultancy.
So the situation was fixed a little bid away from simple logic.
For a go live at end of the year we will use this construction.
Next year customer plans to implement a new central SLD (including portals issues).
Then we will do another move with our SLD content.
Until then customers Xi guys can train a little bit on moving SLD content
to ensure that both SLDs have the same systems implemented.
Only to complete that:
To use transport groups you need prod XI and dev XI both on one SLD else you cannot link the R/3 systems to dev and prod area because transport groups have to be linked to the XI systems on the SLD.
So, my question was a little bit useless!
We had no prod XI available on the dev SLD.
From this issue my question was coming up.
We will add the dev XI to the prod SLD too.
Then moving content won´t cause any problems, I think!
Regards
Dirk
Message was edited by:
Dirk Meinhard

How to remove Variable-Values prior to transporting to prod-system?

Hi specialists,
I've got the following problem:
We've got a mixed BEx-client-environment with user using BEx 3.5 as well as BEx 7.x.
So I create workbooks with BEx-Analyzer 3.5 and transport them from the developement-system to the production-system.
The problem: Obviously the variable-selection that I used at last in the developement-system is saved in the workbook. So let's say I tested the query in the dev-system with "DE01" as value for the company_code on the variable screen, then this value is saved in the workbook and transported to the prod-system.
In the production-system the value is not replaced anymore by the users permitted company-code values (the variable is based on the users permissions), but the user has to remove this "DE01" manually and has to enter all his personal company-codes manually - which makes the permission-bases-variable senseless.
Even if I clear all variable-values in the developement system (which is not possible for mandatory variables) prior to saving the workbook, the issue is the same: This time empty fields are presented in the prod-system, but the permission-based-variable isn't set correctly - the field stays empty (=exactly as it was when I saved the workbook in the dev-system).
So, how can I clear the variable-screen-values before I save and transport the workbook to the prod-system? The only way (and it is certainly not the recommended one) i found: If I cancel the query at once after having confirmed the variable-screen and save/transport that query, then the variables seem to be really empty and the permission-based variables in the prod-system work.

So, when user run the report in production, they will have to remove # for mandatory variables and put thier value.
Mh - most of our reports have variables for "company_code","sales_org" (for example).
Normaly this fields are not mandatory but optional.
But: Normaly if the user opens such a variable-screen (for the first time) the company_code and sales_org are preset according to the users permissions for this chars.
If I follow your description, then the variable-screen would open with "#" or "" - but wouldn't be replaced by the user's permitted values anymore :/ - hence the phone rings because the users didn't manage to restrict the variables to their permitted values.
Maybe this is a case for an oss-message for the area BW-BEX-ET-USAB Userability Frontend....

Missed get delta once option in dtp and transported to prod

hi all
we have transported DTP for our infocube 0wbs_c11 into production.
This infocube 0wbs_c11 is loaded from 4 datasources of which one datasource supports delta and rest donot.
so in process chains we are using the option for delete overlapping requests. for all the 3 datasources which doesnot support delta.
But for one of these 3 datasources we have transported DTP without ticking GET DELTA ONCE OPTION AND loaded to infocube.
now we should tick the get delta once option and transport it to production, where we already ran this dtp once.
Since we cannot enable the get delta once option enabled in dtp after the first dtp run
my question is should i delete the request from infocube and transport the dtp transport request (to prod )with getdelta once option ticked and run the dtp again will it work.
or do i need to delete the request as well as dtp from prod and then transport the new request with delta once option ticked.
regards
krishna

based on the above link which says after activating transformations using the program rsdg_trfn_activate if we run process chain the dtp's get activated by itself
i have done a trial based on the above point
i went to dtp execute tab and press execute ,and when it asks me for furthur process
YES NO CANCEL
I have cancelled the execution of dtp.
and now when i refresh the tree the dtp is seen active .
i followe the same for all.
regards
Edited by: krishnav3.5 on Sep 16, 2011 4:17 PM

Sld objects transportation

Hi
Here I have some doubts in mind.
In case of file transportation system how the SLD objects are imported from DEV and exported to QA ?? Suppose if we are going to use another application system in QA how to tackle this situation ?? Here another application system means we have technical system and on top of that we have business system. So here probably here we are going to change only technical system name right ?? plz correct me if I am wrong. Then only new application system is going to point to our scenario.
In case of transporation using CMS how we do that ?? Becaue here everything is automated how we are going to tackle the situation if we are goint to use another application system in QA ??
thanks
kumar

hi,
>>>>In case of file transportation system how the SLD objects are imported from DEV and exported to QA ??
first of all SAP recommeds to use only one SLD (production)
so you create all objects there
>>>>have technical system and on top of that we have business system
you're right business systems change per landscape
(for example DEVCLNT100 can be QATCLNT500 on test system)
but it's only the case with integration directory objects
so all you need to do is to define transport targets in SLD
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
and if you export and import system names will change automatically
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Transport SWC to Prod sld

Similar Messages

Maybe you are looking for