Transport of unwanted config.

Hi gurus,
In our ECC 6.0 development system, we have 100 as the customising client and 200 as the unit test client.
There is some SAP standard configuration around company codes in structure V_T001 that has found its way to client 200. This is anything that falls outside of the company range 1101 to 1119 (e.g. 0001, AR01 etc). I am not sure whether these entries have been transported from 100 or if they were in client 200 in the first instance prior to transports? Can you please look into this for me and advise how we can reverse these entries from 200?
Any suggestions will surely be rewarded.
Thanks in advance,
Abdul

Hi Abdul,
You can use SE03 to search for the transport that did the changes...
Anyhow, there no way to reverse a transport you'll need to reverse the changes manually or restore from backup.
Regards
Juan

Similar Messages

Need to create a transport of SD config data from DEV 120 to DEV 110

During our conversion some config modifications were mad in DEV 120 instead of DEV 110.
I need to get the config:
SPRO> Sales Distribution> Billing> Billing Documents> copy sales documents to Billing documents
From 120 to 110.
I have tried to force a transport creation in 120, and used SCC1 to import into 110, but no data comes over.
How can I force all the data from these config tables to load into a transport so can send from 120 to 110.
Thanks,
Bev Barbush

Hi Beverly,
I would try bringing this transport in via STMS and then reviewing the import log to see why the data is not going across. What I've normally seen in this situation is the data was not correctly added to the transport before it was imported.
I would NOT copy config tables back from the QAS system. Copying select portions of config data from one system to another is likely to break all sorts of logical relationships between tables.
Have you guys tried running a config comparison between 110 and 120 to see what the actual differences are?
Hope that helps.
J. Haynes

Transport abt ALE Config

Hi,
We have done all IDOC to File scenarios
We have configured the ALE settings on SAP R/3's DEv server.
Can i transport these Config to SAP R/3's QTY Server or Should i create them as it is appear in the SAP R/3's DEV server???
Regards
Suman

Hi Suman..
This was the ALE settings...
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.\
idoc to idoc
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
regards,
Kishore

Transport of config objects...business system prblem...

Hi Gurus,
We want to transport dev and config objects from XI qua to a XI test server... we hav successfully transported all design objects...but we are facing problem while transporting the config objects because of business and technical system issue....the business system in quality points the ECC quality....how can i tranposrt the config objects with same business system name....is there any way??
Thnx in advance...

Hi,
This will be Maintained in SLD .You know what will be Business system name in Quality or Production.
While Creating Business system you need specify in the Transport Tab which is your Target Business System and also the Group like Production or Quality ,
When you do transport from Development and for the Dev_Bs (Bussiness system ) if you assign the Qaulity System Bussiness system ,it automatically move the object under Quality Business System.
if this setup is done in SLD when you do transport the Configuration Object It Automatically assigns the Quality and production Business System if you are doing Transport from Dev Respectively.
hope this helps.
Thanks,
Madhu
Edited by: Madhusudhan Honnappa on Sep 3, 2009 8:11 PM

Transport of Config

Hi,
I found out that while transporting a ABAP code a file is created at the server for that transport.But it is not the same for the Config transport.Is there some place from where transport logs for config can be extracted.
thnx in advance
Regards,
Chirantan

i need to create a report that will display the status for a TR..i.e. to which all systems it has been moved to.I have been able to do that successfully to some extend.
What sap does in this case is that it creates a file at the server that contains the log for that particular TR,this file can be used to determine the status of the TR at a particular server.
But in case of a "config TR" no such log file is created.Now, I need to check(without these logs-since they are not available) that they have moved to other systems.
I hope the situtation is clear now.
null

Is it safe to transport more than 100 of configs?

Hi BASIS gurus,
We are about to go live and there are about more 100 configs per module that needs to be transported in prod. is it safe to transport those selected configs at the same time via import request button? or it is still best to transport it one by one? which is the best practice?
Thanks and regards,
Joel

One by one is not the most efficient way of doing imports always. If you are sure about the sequence which you must normally be before moving transports to production ( i mean changes would have been tested out in quality) then use import all. Import all in way creates a single piece list of objects in transport keeping the version in mind and does the import. You may not save anry y time on actual import but definitely on generation of objects. Suppose there is an include in two separate transports used across several reports then SAP will try to generate all those reports for the first import and then again for the second one. Imagine if the same objects are in multiple transports then we are talking about a fair degree of redundancy. Import all avoids that by doing generation in the end. In my personal experince import all is much much quicker than import single provided you are sure about the sequence. It can save you a lot of time.
With Regards.
Ruchit

Order of BW objetcs for transporting

HAI
i need to transport the infoobjects , transfer rules , trasnfer structure , communication structure , update rules for ODS , ODS , Update Rules for InfoCube , InfoCube from DEVLOPMENT Phase to QA system .
1) so what is the order of objects for transaporting
2) pls telll me how to transport .
i ll assing the points
bye
rizwan

I love this question ?
The transport connection tool if used properly can be of
great help! if used improperly can cause many issue's.
Transports should follow the same sequence as development.
1. Trans datasource's in source systems.
2. replicate source system datasources in subsequent
BW system (verify in overview).
3. Check Logical source system mappings.
4. Info objects are the building blocks, Place them
in catalogs and transport only ness.
5. structure definitions IS's, ODS's IC's etc..
Only ness.
6. select data targets in flow before. to collect
update rules , transfer rules etc.. (Dataflow Connections)Caution- Check all objects selected when collecting auto. To ensure no unwanted config is included in transport.
also make sure the appropriate source system is selected
prior to selection.
7. select data targets after flow.
for Roles Web config etc.
8. Reporting and reporting elements if relevant last.
again expand all collected objects in the above process for review to ensure additional unwanted dependencies are not included in your transport.
Hope this Helps
George

'transport' applications from QA to Production - isolation group error

Hi,
I have a QA isolation group connected to my QA ECC system in which I created job definitions and chains and assigned all of it to my Custom application group. I exported this by right clicking on Custom and 'Export tree..' to a *.CAR file.
I now try and import the same *.CAR file into my Prod isolation group connected to my Prod ECC system. I get the error:
Import failed, no objects have been imported: JCS-102242: Object cannot be persisted to an isolation group other than the active one.
Why is this? How can I 'transport' my QA config to my Prod config?
Thanks,
Adriaan

For anyone interested: you have to run a merge isolation groups CPS system job to get rid of the isolation groups after you installed a full license

Transporting webservices from dev to qa

I transported our webservices from dev to qa. I generated all of the nodes necessary in SICF in QA and I activated the web services in qa, but all of the web services still have a WSDL with dev address. If I try to create the web service in QA, then it wants a transport.
I'm also having an issue with soamanager. When I put in tcode soamanager , I get the logon on screen dev. I can't seem to get anything to point to QA.
How do I get the webservices(WSDL) generated to have the qa address?

Hi Linda,
Only the definition is transported & not the config, this is default behaviour. You will need to complete the config again in Prod.
One reason for this is that the Config is client-dependant so SAP can't make the assumption to which client (in Prod) the config should be relevant to while transporting.
Regards, Trevor

Transport does not map business systems

Hello,
we have a problem when transporting XI configuration objects (via normal file export/import, not CMS). In the SLD, we have configured business systems
T01CLNT010, belongs to group dev and has transport target PROCLNT010
T01CLNT020, belongs to group dev and has transport target PROCLNT020
the strange thing is the first business system is not converted correctly to the prod business system after transporting the XI config from XI dev to XI Prod. For the second business system, that works fine. I compared the entries in the SLD, both look fine. But one does not work, the other does.
For the one that does not work, the transport goes fine, does not show any error, but just does not convert the name. (which of course will lead to an error when trying to activate the objects, because T01CLNT010 does not exist in XI prod). So it seems it cannot find the SLD transport target for that object.
Does anyone know how XI exactly finds out how to convert the business system while transporting it to production ? How does it find the connection between the XI business system object and the corresponding SLD entry ? Just by name ? Or is some kind of internal GUID used which may have been broken ? Can I see that anywhere ?
Is it safe to re-associate the SLD business system to the XI business system in the XI integration builder ? Or are dependent objects (e.g. receiver det.) then lost ?
CSY

Does anyone know how XI exactly finds out how to convert the business system while transporting it to production ?
The only thing that matters here is properly defining the Transport Targets.
How does it find the connection between the XI business system object and the corresponding SLD entry?
Not sure about this but I think the name in the transport target would suffice for this requirement. Also, make sure that the groups are properly defined and target SLD has all business systems properly maintained.
Is it safe to re-associate the SLD business system to the XI business system in the XI integration builder ?
How will you be doing this re-association? If you are thinking of changing the Business system name in ID manually, then it would mean almost complete development in ID.
Regards,
Prateek

Exchange 2010 - Error setting a new transport rule for email disclaimer

Hi
Trying to setup some additional email disclaimer rules on Hub transport under Org Config on exchange 2010. We allready have a few and they work ok, however we are trying to replace this woth some alternate ones and are getting the error
The length of the property is too long. the maximum length is 8192 and the length of the value provided is 8522.
Most of this length comes from the html code we are inserting into the disclaimer. I've reduced it by about as much as i can but it's still too large. Does anybody have any suggestions or know if it;s possible to increase the 8192 sixze limit ?
Regards
Roger

Hi Roger,
For AD replication packet the ideal size is 8K. Or the above error may occur due to build/design issues.
You can eliminate this size related issue by splitting the large rule into multiple rules. This size limit is Per Rule and does not add up for all rules.

Bw general

whats the meaning of involved in Multi dimentional modeling.
whats the meaning of validated data consistency in reporting with data targets aganist psa after loading them to data targets.
how we can do performence for unit testing and integrity testing in real time.
what type of bussiness content we can install for financial project.
how the steps goes for transporting the bw objects from development server to quality server for regression test and unit test.
how to escalate priority tickets regarding extractions, performance issues and load failures in real time.
what is reconciliation. where we use this concept.
what is deadlock. how we get dead lock.

Hai narasimha,
Transportation ( How to transport objects from one server to another)
Follow the steps.
1. RSA1 > Transport connection
2. In the right window there is a catagory "all object according to type"
3. Select required object you want to transport.
4. Expand that object , there is select object, double click on this you will get the number of objects, select yours one.
5. Continue.
6. Go with the selection, select all your required objects you want to transport.
7. There is icon Transport Object (Truck Symbol).
8. Click that, it will creat one request, note it down this request.
9. Go to Transport Organiser (T.code SE01).
10. in the display tab, enter the Request, then go with display.
11. Check your transport request whether contains the required objects or not, if not go with edit, if yes "Release" that request.
Thats it, your cordinator will move this request to Quality or Production.
PROCEDURE 2:
Ideally you should transport the datasource first and get it replicated. then transport the objects coming in the dataflow after the datasource.
try steps
1) replicate datasource in bw QAS from r/3 QAS
2) transport ODS/Infocube with 'only necessary objects' grouping
this will bring ods/Infocube and infoobjects needed
-3)transport ODS with 'in dataflow before'
will collect update rules infosource-ods, infosource,
transfer rules, datasource, infopackage.
4)transport process chain.
5). select data targets in flow before. to collect
update rules , transfer rules etc.. (Dataflow Connections)Caution- Check all objects selected when collecting auto. To ensure no unwanted config is included in transport.
also make sure the appropriate source system is selected
prior to selection.
7). select data targets after flow.
for Roles Web config etc.
8). Reporting and reporting elements if relevant last.
For transports steps above:in transaction RSA1->goto the transport conncection screen by clicking transport conncetion in the left pane.
In the end,in the se10 transactoin , release the request and ask the basis person to transport
for complete clarification go through this link
check this link & revert on doubts
http://help.sap.com/saphelp_nw2004s/helpdata/en/38/5ee7377a98c17fe10000009b38f842/frameset.htm
Transport !
Best Regards,
Sateesh

Workflow Upgrade 4.6C to ECC6 - manual settings during Cutover

Hello Guys,
We are upgrading to ECC 6 from 4.6C and we are on release 701 & support pack SAPKB70106.
I would like to know which are the "Manual activities" that needs to done during cutover and WHEN should these should be done (eg. before ECC6 upgade, or after ECC6 upgrade but before config/dev transports, or after config/dev transports).
I have looked on few SDN threads and found the following info. Please correct me or add extra info if i have missed something:
1. Configure RFC destination & WF user info in Transaction SWU3.
2. Run Transaction SWU_OBUF to clear the runtime buffers before users start Testing.
I assume rest of changes would be imported with transports, but i have read through lot of SDN threads that all custom Workflow definitions needs to be ACTIVATED in each system (DEV - QAS- PRD) and custom BOR objects needs be REGENERATED in each system (DEV - QAS- PRD). Also, do I have manually set the agent assignement for Customer Task as GENERAL TASK in each system? Are above stated 3 steps needs to be manually done in each system or transports take care of them ? I am bit confused. Could anybody please advise me regarding the Manual Task/activities that needs to done in each system during cutover during WF upgrade from 4.6 C to ECC6.
Thanks for posting excellent stuff regarding the Workflow Upgrades on SDN. It really helped me in resolving most of my issues.
Thanks in advance
Kind Regards
Sam

Helli Viji,
Thanks for the information. I still have some doubts.
Yes , as you have mentioned there are many other mandatory settings in Transaction SWU3 that needs to be maintained in each system. I hope these settings are imported with the Customizing tranport request created in DEV or Do we have to maintain these manually just in case of Upgrade.
For transporting the Agent assignment from one system to another, can we use Transaction RE_RHMOVE30 ? Or this functionality do not works when upgrading to ECC 6 from 4.6 C.
Is there any other activity I am missing that needs to done during Cutover when upgrading from 4.6C to ECC 6 with regard to Workflows.
Thanks
Regards
Sam.

Increasing Email Size Limits for some users

Hi All,
For some users (management) i needed to arrange that they are able to send bigger files then the default 10MB limit to each other.
I used this procedure to do so,
https://www.simple-talk.com/sysadmin/exchange/increasing-email-size-limits-for-your-high-profile-users-in-exchange-2010/
In a nutshell:
Set Global Transport Org. Config to 200MB
Set Transport Send and Receive connector to 200MB
Created a Distribution group adding the MT members and me (for testing)
Created a transport Rule for the 10MB limit for all users and exception for the distribution group
(Believe me, i am not happy with the 200MB size limit)
All seems to work but i have one issue that i cannot tackel or maybe it is by design.
-Managemant can also send big files to all
users who do not have this privelige, this is not someting i want, sending 100MB+ attachments to over 150 users.
Is this by design or do i mis something?
Thanks,
Ron

Hi RonGielgens,
Attachment size in exchange has to be set on
Global settings
Connectors (send and receive connectors)
Mailbox
The global settings will affect all the others. of course connectors will affect specific servers and mailbox one user. You have to set the global to the absolute max size you want to allow in your organization.
after you do this you will need either to set the 10MB on each mailbox
Get-Mailbox | Set-Mailbox -MaxSendSize 10MB -MaxReceiveSize 10MB
Then change the limit on specific mailbox
or another way is to create a transport rule that will reject the email if the attachment size it > 10MB unless the sender/recipient is the required user or group.
so basically create 2 transport rules
1. reject messages sent to anyone with attachment > 10mb unless the recipient is userX
2. reject messages sent from anyone with attachment > 10mb unless the sender is userX
Normal case it should not allow.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

REAL TIME QUESTIONS- LANDSCAPE

hi Friends,
my doubt's are
1. sandbox is a client in DEV server or seprate server??
2.after golive how many clients are there in production serever?
3. In real time can we transport objects from sand box to DEV or can we re do in DEV???
4.what is the use of pre production server???
5.In real time we copy clients from 000 or 001??
if anybody answer these, very useful for us
thanks

Hi Manu,
1. sandbox is a client in DEV server or seprate server??
Sandbox is a seperate server . It may or maynot include in DEV Server.
2.after golive how many clients are there in production serever?
Most Probably only 1 client-for the live transactions of Business.
3. In real time can we transport objects from sand box to DEV or can we re do in DEV???
we wont do any config in Sandbox.So there is no Q'n of transportation. All Config will be done in DEV-Config Client & will be transported to Test client in DEV server,then moved to Qlty for further testing like UNIT & INTEGRATION, after that will be moved to Prdocution server.
even its vary from project to project.
some project Config directly moved from DEV to PRD.
4.what is the use of pre production server???
Generally its maintained to minimize/avoid the mistakes.
5.In real time we copy clients from 000 or 001??
Depends on client strategy client from production will be copied in quality client. So that while testing- real time data will be available.
*hope it adds info

Transport of unwanted config.

Similar Messages

Maybe you are looking for