TMS Configuration client depending

Hello Community,
i need information on how to configure TMS with the following scenario:
Two Systems:
DEV and PRD
Two Clients:
DEV with clients 100 (Customizing GTS) and 200 (Customizing ERP)
PRD with clients 100 (GTS prod) and 200 (ERP prod)
can you explain me how i can get client based transportation from DEV100 to PRD100 and DEV200 to PRD200?
regards

Hi
At first it is not recommended to have many clients in a production system, I've never worked with GTS maybe there is a specific requirement but I do not feel confident with this.
I do not feel confident either having two different SAP solutions within on system... at least this might generate extra regression testing work for instance when you apply OSS note or SP for one of the two solutions (you will need also to validate impact on the other solution)
=> check that post on that subject Installation of GTS on same server with SAP ECC
For workbench object this can be easily done by creating 2 packages (aka dev class) linked to two different transport layers that will follow specific transport routes... but as your two target clients within the same system this is useless because workbench objects are cross client...
For customizing object the only way would be to activate Client Transport Control (setting TMS parameter CTC=1 for both PRD and DEV systems) and for each order you are creating you can select the client you wish to target.
Regards

Similar Messages

TMS configuration for multi-clients in one system

Hi All,
we have got some problem defining transport routes in stms in transport domain...
We have to add to target group for one system 6 clients:3 clients with the dev/test roles for country X and 3 clients with dev/test roles for country Y.
Transport requests have to route only between clients for defined country (only for country X or only for country Y, must not mix).
How i can get status when transport requests will route in one system only between clients of country X (or only for country Y)?
Should i define two target groups and add to one group 3 clients for X and to the second 3 clinets for Y? I am not sure that it is enough. May be exists a lot of other options/ actions?
Where is garanthy that requets from country X will not mixed with requests from Y?
Thanks a lot.

> The SSO is working fine for only the client which we used to import the certificate (verify.der).
> 1>Is it that the certificate import should be done from all the clients exclusively ?
Logon ticket certificate is instance wide, not client dependent. And you need to call STRUSTSSO2 in client 000 to export/import.
> And the SSO is not working for other clients in the same system .
> 2>If yes can you tell the procedure, why b'coz transaction STRUSTSSO2 is same for all clients and if we try to import the certificate again how about the existing one over there ?
Could you provide more details about this issue you're facing? What is the Portal UME source? What application is it based on, BI or ESS/MSS?

Client Specific TMS configuration

Hi,
How can configure client specific STMS
For eg;
Development Request from client 100 goes to Client 100 in quality, client 200 from Development200 goes to Qulaity Client 300.
Dev(100) --- Quality(100) -- Production
Dev(200) --- Quality(300) -- Production
Thanku

Hai,
You can use Extended Transport control to achieve this.
http://help.sap.com/saphelp_nw04/helpdata/en/1b/9dc2d6e59911d184810000e8a57770/content.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci916309,00.html
Regards,
Yoganand.V

Client dependent and client independent in ALE

I am going through pdf learning of an ALE scenario,i couldnot get wat is meant by client Independent and client dependent.
How can i conclude
Create message type (WE81){color:green} Client independent {color}
To create a new message type, follow these next few steps:
u2022 Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
u2022 Choose Create logical message type by double clicking on it
u2022 Click on change icon to enter change mode
u2022 Click on New entries to add a new type
u2022 Enter the required message type, in our case it is ZINVRV and an appropriate description
u2022 Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) {color:green} Client independent {color}
To link the message type to the IDoc type follow these next few steps:
u2022 Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
u2022 Click on change icon to enter change mode
u2022 Click on New entries to create the link
u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
u2022 Save and exit
u2022 Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
u2022 Click on change icon to enter change mode
u2022 Click on New entries to create the link
u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
u2022 Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
u2022 Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
DOC NAME: ALE_SCENARIO_DEVELOPMENT_PROCEDURE
Version 1 Page 6 of 16
ALE Scenario Development Guide
u2022 Type in your message type ZINVRV and press enter
u2022 Click on New entries
u2022 Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
u2022 Save and exit.
You have now created an object that weu2019ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) {color:green} Client dependent {color}
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
u2022 Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
u2022 Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
u2022 Choose the receiving systems to which the sending system must forward message type ZINVRV to.
u2022 For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
u2022 Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
u2022 Save the entries.
Refer my query within color:green
Edited by: aditya sharma on Jul 14, 2010 12:57 PM
Edited by: aditya sharma on Jul 14, 2010 1:01 PM

A client is an independent business unit within an R/3 System, Data in the R/3 are classified as cleint-Dependent and client-independent.
Client-independent data such as ABAP Programs, R/3 repository objects throught the entire system. Other data is client-dependent. meaning, it can be viewed from one client. Cleint-dependent data includes customizing application and user data.
Eg.
Scripts are client dependent, means the changes done to SAP scripts in particular client will not be reflected in other client.
Smartforms are client independent, means changes done in one client will be reflected in all the clients.
Server : ECC6
Client : 100 , 200 , 300 , 400
Now suppose you have developed report in DV server client 100.
Then you will be able to see that in all clients.
Hence this is called as client independent. You can change anywhere and changes will be reflected to all ...
Now suppose you have developed a script in DV client 100.
You will not be able to see that in client 200 or 300 or 400 unless ytou copy that from client since it is client dependent.

CHARM TMS configuration

Hello,
We are implementing CHARM in our project.. The landscape in our project is as below:
D-100 - Dev client
D-200 - Unit test client (Dev sys)
Q-100- Quality system (Integration Testing)
P-100- Production System
We have configured (client specific roots) TMS as D-100 --» Q-100 --» P-100. Is it possible to include D-200 as Unit test client in TMS?
As per SAP docs, once the Change Manager approves the reqeust, further tasks (creating transports and unit test...) will be handled by Developer. The developer will perform configuration in D-100 and accordingly create the transport request. Now IT operator will need to move the reqeust to testing client (D-200).
How the transport will be moved from D-100 to D-200 (Unit test client)??
Appreciate your reply.
Thanks,
SM

There are different ways to do this.
One option is:
1) Goto transaction STMS
2) Select 'Overview --> Imports'
3) Double click on the system you wish to schedule the job for
4) Click on the truck icon to schedule an import all job (only import
   all jobs may be scheduled as periodic)
5) Fill in target client, if necessary
6) Select 'At start time' and fill in the date and time
7) Next to 'Period' there is a box with a gray background. If you
   click in the box a drop-down arrow will appear. Click on this.
8) Select your period from the menu options and click on the green
   check.
9) Click on the green check again and your job will be scheduled.
or
Scheduling the Automatic Import of U_gent Corrections via /TMWFLOW/SCMA_BTCH_SYNC_UC
http://help.sap.com/saphelp_sm40/helpdata/en/96/0737423df2b26be10000000a155106/content.htm
or
give your IT Operator proper Roles to do the import manually
or
give your IT Developer proper Roles to do the import manually
Nesimi

Error in STMS - The TMS configuration is inconsistent

Hi gurus,
Yesterday I installed the SAP Solution Manager 7.0 SP14 with S.O. Win 2003 server and D.B. Oracle 10.2.0.4 version.
When I tried to configure the STMS I´m facing with a problem... the system send me a error "The TMS configuration is inconsistent" and when I open the error details it show me a information "tp configuration note completely distributed"... I search a lot to find a valid solution for this and I don´t have sucess, I don´t achieve a answer / suggest that solve this error...
Please give your suggestion to resolve this issue as snow as possible.
Thanks in advance
Best regards,
João Dimas - Portugal

Hi,
Please check the Note 1144208 - TMS Tendering: Inconsistent tendering template
Settings under the Transport Management System do follow the steps.
All the below settings has to be done in satellite system not solution manager
1.     Define Transport Routes for System Landscape
Go to Transaction STMS
Choose Overview -> Systems.
Double-click each system.
The Display TMS Configuration: System <system ID> screen appears.
Select the Transport Tool tab page.
If the entry CTC does not appear in the Parameters column, enter it there, and then in the Value column, enter 1.
Save your entries.
Configure Transport Strategy
Go to Stms Transaction
Go to Menu Overview  Transport Route
Doule click on Each System
In the Transport strategy group box, select Single transports
(since only Import Single and Import Project All are used).
In the Quality assurance group box, deselect Delivery after confirmation
1.     Choose Continue.
Activate TMS Trusted Services
Go to Stms Transaction
Choose Overview -> Systems.
Choose Goto -> Transport domain.
In Management Tab
In Security Options group box
Click on Trusted Services Active
Go to QA Approval Procedure
You should not assign any QA approval system there
Save your Entries
Call Transaction STMS.
Choose Overview  Systems. The system overview appears.
Choose SAP System  Create  Domain link.
The dialog box Request for Linking 2 Domains appears.
Enter the system name, host name and system number of the domain controller you want to link to, and then confirm your entries.
Your SAP System performs the following actions automatically:
o     Generates the required RFC destinations.
o     Sends the address data of the controller to the controller in the other domain.
You can now see that you have requested the domain link to the other domain in the system overview.
Click the Distribute and Activate TMS Configuration ICON on the Application Toolbar
After that Go to SAP System  Check  Connection Test, transport directory and transport tool
Check all once whether it is having inconsistency.
4.Check Configuration of Transport Domain
Log on to every domain controller that is connected to your transport landscape.
Call transaction STMS
Apart from the information "You are logged onto the domain controller", you should not be able to see other messages or warnings.
Generate RFC Destinations to Client 000
Call Transaction SMSY.
Go To Landscape Components
Go to your Satellite System
Click on the Domain Controller System
In the Right side Tab strip, Click on the Clients, Select 000 client Click on RFC generate Button
Give the User name for Read Access and Change Manager
Click the OK Button to Continue
Add Import Authorization to Operator/Administrator
Make sure that the operator and administrator users in client 000 of the target systems have the same name as their user in the Solution Manager   system.
Assign import authorization to the operator and administrator users in client 000 of the target systems (SAP_CHANGEMAN_OPERATOR and SAP_CHANGEMAN_ADMIN roles).
Regards
Sreedhar Reddy

TMS Configuration problem - SET_CODEPAGE_FAILED

I have just installed a new system "CRM 7.0/NW 7.01". The first thing I am doing is configuring TMS in client 000. When I try to distribute the configuration I get an error:    TMS Configuration could not start transport control program TP. SET_CODEPAGE_FAILED.
I looked at all the previous posts and have done all the prework: ENV variable dbms_type = ora and I upgraded the kernel to current.
In TMS I don't get an error when I check the connection or when I check the transport directory. It only happens when I check the transport tool. Here is the error message from the dev logs:
Trace file opened at 20110210 131154 Eastern Standard Time, SAP-REL 701,0,125 RFC-VER U 3 1215400 MT-SL
======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
ABAP Programm: SAPLSTPA (Transaction: SPAM)
Called function module: RFC_TP_INTERFACE_VERSION
User: PREED (Client: 000)
Destination: CALLTP_WindowsNT (handle: 3, 64588453, {254135E0-9A35-F1B2-8C05-0013724E7C66})
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3348
CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1829
Thu Feb 10 13:11:14 2011
ERROR => GwISearchPartner: timeout, partner LU: >SITASERV44<, TP: >C:\usr\sap\CR3\DVEBMGS00\exe\tp.EXE< [gwr3cpic.c   6349]
ERROR => GwISearchPartner: HOST: SITASERV44, conv ID: 64555875 [gwr3cpic.c   6362]
Thank you for your assistance.
Peggy

I copied the wrong dev_rfc log:
Trace file opened at 20110210 130049 Eastern Standard Time, SAP-REL 701,0,125 RFC-VER U 3 1215400 MT-SL
======> CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
ABAP Programm: SAPLSTPA (Transaction: )
Called function module: RFC_TP_INTERFACE_VERSION
User: TMSADM (Client: 000)
Destination: CALLTP_WindowsNT (handle: 3, 63913828, {953F35E0-66FD-F1C8-8C05-0013724E7C66})
SERVER> RFC Server Session (handle: 1, 63911750, {983F35E0-5E6B-F160-8C05-0013724E7C66})
SERVER> Caller host:
SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
SERVER> Called function module: TMS_CI_START_SERVICE
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 3348
CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 thRc=456
Timeout during connection setup (check that partner exists)
Error RFCIO_ERROR_MESSAGE in abrfcio.c : 1829

Client dependant/independant

Hello All,
Can anybody please tell me, Configuration and Desing in Integration Builder is client dependant or independant?
Thanks.

Hi Kinnari,
I complety mistook ur question. IR and ID are based on Java Stack.
lets say you are doing Xi development on XI Client 10. Add you want to access interface definitions in Client 20 on the same machine. then you can. all the clients on the same machine will have access to every thing. say if you go to tcode: sproxy in client 20 , you can see all the interfaces defined in client 10.
so for testing you dont have to transport anything between clients.
Naveen

TMS configuration problem

Hello everybody,
I had install the IDES ECC 6.0, Now i want to configure the TMS then I have planned the client like
800->customizing
500->backup (means only copy the change request)
550-->Quality (Same as backup but here i will test all the configuration)
600-->PRD( like final producion)
Then, How to configure TMS?
which transport route is set and hows?
when i am trying to configure then i get message like
Delivery with source system IDS & source client 800 not allowed
Will anybody please send the step by step proceudure to configure the right TMS configuration
Thanks
Ganesh

Hi,
I am bit cofused about the client, are these clients in same system or different systems, if the clients are in same system, then
Any way you will save the customizing changes you have done under a change request number, then login into the client which was present in same system and execute the t-code SCC1, here you have to select the change request number that you wanted to import from other cleint and the source client number and execute, the changes will be transferred into this cleint(note: this was case when both clients in same system).
If you wanted the change request to be transported into client which was in other system(you need TMS configured by now), the you have to release the change request in the source system client and using STMS you can trasnsport the change requests to the target system into tghose clients, you need to trasnport this way to all cleints in target system.(Note: once change request is released you cannot add any modification in that Change request, need to create new request again)
for backup of your customizing cleint, make a new client in source system and using local client copy process you can have backup of your customizing client(decide local cleint copy frequency yourself for this), if you wanted to take backup into some other system you can do it by remote client copy.
apart form your SAP level backup, you should always backup your entire system onto tape or some other system ikn co-ordination with your IT team.
Regards.....

TMS Configuration Database installation

Dear Gurus,
I have few requirements from client which is
(1). TMS configuration between two systems which are DEV(Bangalore) PRD(Hyderbad) is it possible or not if is possible howit is?
(2). is it possible to install database is in one server and SAP application(CI) is in one server if it is possible how it is?
Please give me the some sugestion.
with Regards,
kk

Hi,
> (1). TMS configuration between two systems which are DEV(Bangalore) PRD(Hyderbad) is it possible or not if is possible >howit is?
Yes this is possible.
Check below links to configure TMS:
[link1|http://bbs.cenet.org.cn/UploadImages/200581112435749207.pdf]
[link2|http://www.academictutorials.com/sap-basis/sap-basis-tms-configuration.asp]
[link3|http://help.sap.com/saphelp_nw04/helpdata/en/44/b4a15d7acc11d1899e0000e829fbbd/content.htm]
> (2). is it possible to install database is in one server and SAP application(CI) is in one server if it is possible how it is?
>
Yes, this is also possible.
[link1|http://help.sap.com/saphelp_40b/helpdata/pt/e5/06a411802111d1889a0000e83539c3/content.htm]
[link2|Re: Advantages of Distributed Installation;
Thanks
Sunny

Is SAP HR client dependent

Hi all,
Is SAP HR client independent or dependent?
what ever changes we make in IMG screen by logging into 1 client (eg:800) can they be seen when i login by another client (eg.000)?

Hi,
Almost all are client dependent...You need to transport to other client.All Configurations has to be transported to diff, server (Like QAS,PRD) from DEV .
Regards,
Manoj.

Local TMS configuration inconsistent in sid

hi,
i am facing this problem while using tms
"Local TMS configuration inconsistent in sid"
can u pls help me

at first, the TMS domain is running good.
I delete the TMS configuation in DEV client 000 before delete QAS system in this domain, and then i try to reconfig TMS domain in DEV, when i try to join QAS to the domain, I got the error message "Local TMS configuration inconsistent in QAS", details information:
=============================================================
System   QAS              Command TMS_MGR_CONFIGURE_CLIENT
Client   000              Service Communication Interface
User     TMSADM           Start    Online
Date     2011-05-23       Function TMS_CI_START_SERVICE
Time     11:12:40         Message INVALID_LOCAL_CONF
    Local TMS configuration inconsistent in QAS
    tms_not configured
=============================================================
and i try to update and distrubut the domain configuation in Domain controller(DEV) according the online help, and I try to post installation both in DEV and QAS, but still no effected of all.

Distinguish client dependent & client independent

Hi
what is the difference between client dependent and client independent;
can any one explain on it.
thanks in advance
sameer

Hi,
Whatever the configuration we do in IMG- will be store in certain tabels .
if u observe tables in
Tcode:SE11- enter table name
if first field is CLNT- MANDT means
its client dependant .
this config is specific to the client.
the rest will be client independent like number ranges.
eg: Factory Calender-
once maintained will be available in all clients in the same server.
Table:TFACD
( check in SE11)
whichsnt client specific (no CLNT - MANDT field)
Edited by: RMD on Apr 11, 2008 6:42 PM

What is client specific,client dependent,client in-dependent please explain

Hi,
Could anyone explain below terminologies
client specific,
client dependent,
client in-dependent
Delta -
Thanks.
RAAM

Hi,
when you log on to SAP you log on to a client.
That client may be sitting on server with other client.
Typically in a development system you will have several clients.
- One for you configuration
- one for your unit testing
- one for your playpen testing
- some even have one just for ABAP developments
There are some configuration setting you do that are client specific (client dependent). I.e it means that your configuration will only be seen in client.
There are some configuration settings and all ABAP developments that are client independent. I.e do the change in one client and that change is automatically, immediatly visible in all other clients.
Hope it clears things up.

Use of client dependent tables

Hi Gurus,
I have read many threads on difference between client dependent and independent data/objects etc.
But, someone tell me please, wheat exactly the 'Use or Advantage' of client dependent tables/data.
Thanks in advance.
V

HI,
The use of client dependent tables is that if data in one table of a particular client is updated then that data wont be seen in any other clent it provides a security to the data we retrict users with their authorizations in differen clients
When you log on to an SAP System, you log on to a particular client of this system. Any activities you carry out in the system are always carried out in one client. When you plan your SAP system landscape, you must consider which clients you need for which activities.
By assigning activities to be performed in a client, you give each client a particular role. This section describes the most important client roles.
Since you need to adapt the SAP software for your own business needs, each SAP system landscape requires a client where Customizing settings, and possibly ABAP Workbench developments, can be made. This client is known as the Customizing and development client, or Customizing client for short. The abbreviation CUST is used for this client.
Before you can use the Customizing settings and Workbench developments productively, you need to test them extensively for errors. Any faulty settings can seriously disrupt productive operations, and at worst, lead to the loss of productive data. The integrated nature of the various SAP applications means that there are many dependencies between the different Customizing settings. Even an experienced Customizing developer may not discover these dependencies immediately. The correctness of the settings can only be guaranteed with extensive testing. The client where these tests are made is the Quality Assurance Client, QTST for short.
A separate client is required for productive use of the SAP System. So that this client can be used without disruption, it is essential that no Customizing settings or Workbench developments are made here, and also that no tests are carried out. This client is known as the Production Client, PROD for short.
These three clients, CUST, QTST and PROD, are the central clients that exist in every system landscape. Standard system landscapes have precisely one client for each of these client roles.
We recommend that you make all your Customizing settings in a single Customizing client, and then use the CTS to transport them to the other clients.
We also recommend that you do not make any Customizing settings or Workbench developments in the quality assurance or production clients. You can make sure of this by making appropriate client settings.
In addition to the central clients, you can also set up other clients for other tasks. However, you must remember that each extra client takes up additional system resources (main memory and database space). They also need to be administrated. For example, you need to set up and administrate access authorization for the users, and also distribute any changes to other clients with the CTS. You must weigh up the advantages and disadvantages of setting up other clients.
Examples of other client roles are:
Development test client (TEST): Developers can use this client to test their Customizing settings and Workbench developments, before they release their change requests. In this client the developers can create test application data for realistic tests. If they discover errors, they can remove them in the Customizing client. A development test client is always set up in the same SAP System as the Customizing client. This means that any changes that are made to cross-client data in the Customizing client are also immediately visible in the development test client. Changes to client-specific data are copied from the Customizing client to the development test client using a special client copy function. The client copy function uses the unreleased change requests from the Customizing client to do this. The development test client is set so that you cannot make changes to Customizing data and Repository objects.
Prototype or sandbox client (SAND): You can use this client to test any client-specific Customizing settings if you are not sure whether you want to use them in this form. Any settings that you want to keep are then entered in the Customizing client. To prevent conflicts between the prototype client settings and real settings in the Customizing client, you cannot make changes to cross-client Customizing data and Repository objects in the prototype client. The CTS does not record changes made to client-specific Customizing data, and does not transport them from the prototype client. You can make sure of this by making appropriate client settings.
Training client (TRNG): To prepare end users for new functions that are to be transported into the production client, you can set up a training client. The users can use the new functions in this client with specially created application data. This client is set so that you cannot make changes to Customizing data and Repository objects.'''
plzz reward if this information is usefull to u plaa dont forget to reward

TMS Configuration client depending

Similar Messages

Maybe you are looking for