Activating switch in switch framework is client dependent?

Hi Experts,
We have an interesting scenario where a system is running in 2 clients in the same server. Now the requriement is to activate few of the switches in only one client. Is this possible?
I am not really really sure on which forum to post this thread. Now that I am an ABAPer finally ended up here.
Regards,
Arun.

Hi Arun,
There is a method. But I'm not sure if this is should be done or if this is right.
@moderators, Experts Please correct me if i'm wrong.
Go to T.code SFW1
Go to your corresponding switch.
Click on Global status.
It shows a description for each client.
Regards
ncvajja

Similar Messages

Maintenance Optimizer - Activate Switch Framework

When I calculate in mopz the packages the system writes, that I must activate the switch framework in the satellite system.
Whitch framework does it means?

In order to make a correct auto-calculation when customer has SAP ERP 6.0 -ECC server instance installed. MOPZ try to get the active switch framework information.
So, it's not mandatory to maintain the RFC for all product systems in SMSY that you run MOpz trasaction for. It's only mandatory for product system with PV SAP ERP 6.0 and instance ECC server.
If you have active switch frame work for this ERP system while MOPZ can't get this information by valid RFC. The calculation is not correct then.
That's why MOPZ import this new error RFC destination is not available to get switch framework information! Message no. MOPZ_CHECKS237
To deactivate the RFC check for ERP, is not recommended by SAP!
In order to bypass the RFC destination check, you can set the user profile parameter "VALIDATION_MODE" with value "X"
You can reactivate the RFC check easily when you find you need it. Delete the user profile parameter "VALIDATION_MODE" with value "X"

Switching between old/enhanced dependency editor in PDN/PPE

Hi,
Current I have the enhanced dependency editor enabled and a customer syntax defined in config. When I try to modify the dependencies of a variant in PPE or PDN I get the enhanced dependency editor as expected, and i can define my dependencies using the customer syntax - awesome. Without modifying the config, I now want to be able to swtich to being able to edit the dependency using SAP syntax on a case by case basis. Reading online it appears to be possible to accomplish this by switching to the old dependency editor using some user specific settings. I've gone searching, but I can't seem to figure out where this can be maintained on a user by user basis.
Any help woudl be greatly appreciated.
Thanks,
Jacob

I am not sure this is the "right" place to publish this, because the "problems" I have with the new editor is not exactly bugs, more lack of functions compared to the old one.
But i thought it would be better to put this in one place, instead of spreading it all over the forum? If it is not the case, i apologize
1. Will there be a "paste plain text" in the new editor, I use this feature often so I don't need to remove the formatting from text before pasting it into BC.
I also recommend it to a lot of clients who try to paste in text with all sorts of formatting.
2. The new "inser image" dialog is really nice. I like the previews and i know that our clients will like it as well, but will there be a option to switch to a "file overview" instead.
Some times it will be a lot easier to find a picture from the filename, instead of browsing through the pictures.
3. Is "Image properties" removed in the new editor? I found it useful for floating pictures left/right, resizing to a specific width etc. I can do this in the html fairly easily,
but i found the other way quicker.
4. Much the same with the "Insert link" tool. I can't find "target". Is this gone also? Yes i can do this directly in the HTML, but in some situations i think this is a lot easier.
In general I think the new editor is great, and I think it will be even better, but i think some of the tools has been simplified a bit to much.
I am aware that this is a whole new editor, and I think it is great with all these new features, but i am a bit sad to see some of the old ones go.
Maybe a lot of my problems i've put here can be solved in other ways, if that is the case I would love to know

Switching default mail clients?

Is it possible to switch default mail clients from Mail to Entourage? I would like for Entoutage to open when I I hit the Apple key + I .
Thanks

Thanks for this great tip, Matt, though I wish Mitch had marked this question as "answered" since I can't do it for him!
FP iMac G4 700 768 RAM Mac OS X (10.3.9)

SAP Management of Global Employee- activation switch disabled

Hi all,
In order to activate SAP GE, I find the node "Activate GE" is all grayed out. Then I tried to access and activate it from T77S0 but it's also grayed out in the table.
This is the situation while holding SAP_ALL profile.
Any clues anyone how to enable the activate field in IMG or in Table T77S0?
Regards.

Thanks Wrens and Sreenu,
It works and changes the status of MGE to activate... but this still does not release the infotypes (700 series for GE ie 702, 703, 706, 715 etc with others). This is the situation after activating switches CCURE MAINS and CCURE GLEMP.
The message displayed is:
"You attempted to access infotype &1. According to the system settings, however, it is not permitted to use this infotype."
Any clues on this restriction.
Regards.

Overview of Switch framework

Hello,
I would like to know more about the Switch framework to activate the technical uses after the ERP system is upgraded to EHP4.
Are there any docs or slides available talking about this, maybe an overview on switch framework? Any help would be highly appreciated.
Thanks,
Ajay

You find an overview on some features of the Switch Framework in these weblogs:
The Three Use Cases of the Enhancement- and Switch-Framework - Part 5: The Basics about Switching
Second Try: The Three Use Cases of the Enhancement- and Switch-Framework - Part 6: The Re-Integration of the SAP Industry Solutions into the ERP Core
The Three Use Cases of the Enhancement and Switch Framework: Part 7 - The Enhancement Package Strategy of SAP ERP 6.0
How to Get the Most From the Enhancement and Switch Framework as a Customer or Partner - Tips from the Experts
Regards
Thomas

Move a switch from VTP client mode to VTP transparent mode

Hi,
Does anybody have an experience / knowledge if I move a switch from VTP client mode to VTP transparent mode, should I re-create all the VLANs on this switch?
Thank you!

Hi there,
The VTP and the VLANs are seperate beasts.
The switch has a vlan database which is held in a seperate file to the config. If you type "sh flash" you'll see it in there.
VTP passes around the VLAN information and the switch stores it in the vlan database. If you remove the switch from the VTP domain, then VTP will not be able to update this file and it will remain exactly as it was.
In short - if you've got 20 vlans, when you go to VTP transparent, you'll still have 20 vlans
Regards,
LH
Please rate all posts

Client Dependent or Client Indipendent

Hi All,
Could you plz tell me, XI Scenarios are Client Dependent or Client Independent ?
Is there any T.Code Creation for every scenario like ABAP ?
Who run these scenarios in Production system ? And how they are know this scenario for this purpose ?
( Based on Namespace or any thing )
Thanks & Regards
Murali
Edited by: Murali Dusi on Jun 26, 2008 9:49 AM
Edited by: Murali Dusi on Jun 26, 2008 9:53 AM

Xi s not same as R3..
Its a middle ware .. even XI system has a R3 (ABAP stack) other than JAVA(Integration Builder)
common Tcoded used in XI are:
SXMB_IFR
Start Integration Builder
SXMB_MONI
Integration Engine Monitoring
SXMB_ADM
Integration Engine Administration
SXMB_MONI_BPE
Business Process Engine Monitoring
SXI_CACHE
XI Directory Cache
SPROXY
ABAP Proxy Generation
IDX1
Port Maintenance in IDOC
IDX2
Metadata display in IDOC
IDX5
IDOC Adapter Monitoring
SLDCHECK
Test SLD Connection
RZ70
SLD Administration
SLDAPICUST
Maintain SLD Access Data
SM59
RFC Destination
ALRTCATDEF
Define Alert Category
ALRTDISP
Display Alerts
SU01
User Maintenance
SXI_SUPPORT
Test all the Repository and Directory Objects
SMICM
ICM administration and monitoring
SMQ1
Outbound Queue monitoring
SMQ2
Inbound Queue monitoring
SWELS
Switch event trace On/Off

Client dependant objects in ABAP or SAP

5.What are client dependant objects in ABAP or SAP?

Hi Venu,
Sap Scripts are Client dependent
How do we debug sapscript?
First we need to put Break point in Print program where ever you want to stop the execution.
After in SE71 give your form name and go to Utilities-->Active De-bugger.
Then go to your transcation like VF03(for Invoice or Credit memo) etc to see the print preview or print the form execute it.
When you execute it the the form Debugging will get activated and you can see your Form execution step by step.
Thanks,
Satya
Edited by: SATYA KUMAR AKKARABOYANA on May 30, 2008 12:45 PM

List of client dependant and independent

Hi All,
Can any one let me knw the list of objects which are client dependent and which are not.
Thanks,
Vibha

Hello Vibha
The following list shows the client-dependent repository objects:
LIMU     FSEL     Field Selection
LIMU     VARI     Report Program System Variant
R3TR     COC1     CO: Cost Centers
R3TR     COC2     CO: Activity Types
R3TR     FORM     SAPscript form
R3TR     LODS     HRDSYS: Logical information object client-dep. table E SYST
R3TR     PCYS     HR: Transport standard personnel calculation rules
R3TR     PHDS     HRDSYS: physical information object client-dep. table E SYST
R3TR     SBNL     Logical Information Object for BDS
R3TR     SBNP     Logical Information Object for BDS
R3TR     SBNR     BDS: Relationship Between Information Objects
R3TR     SBPL     Logical Information Object for BDS: Bid Invitation
R3TR     SBPP     Physical Information Object for BDS
R3TR     SBPR     BDS: Relationship Between Information Objects
R3TR     SBRL     Logical Information Object for BDS
R3TR     SBRP     Physical Information Object
R3TR     SBRR     BDS: Relationship Between Information Objects
R3TR     SBSL     Logical Information Object for BDS
R3TR     SBSP     Physical Information Object
R3TR     SBSR     BDS: Relationship Between Information Objects
R3TR     SBTL     Logical Information Object for BDS
R3TR     SBTP     Physical Information Object
R3TR     SBTR     BDS: Relationship Between Information Objects
R3TR     SBWL     Logical information object for BDS
R3TR     SBWP     Logical information object for BDS
R3TR     SBWR     BDS: Relationship between information objects
R3TR     SRHL     SRM: Hierarchical Lists
R3TR     SRLD     Language-Dependent Client-Specific Retrieval Index Objekt
R3TR     STYL     SAPscript Style
In contrast to client-independent repository objects which can be imported into any client these objects must be transported into their specific target client.
Regards
Uwe

Urgent:Why Script is cliend dependant and smartform is not client dependant

Hi all,
Can any one pls tell me why script is client dependent and smartform is not client dependant.
Please give some real time examples in brief
regards
tapu

Hi
DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:
1. script is client dependent one while smartform is client independent.
2. In scripts we have to write print program while in smart forms it is not necessary.
3. In scripts we can print background logo while in smartforms we cant print background logo
4. In scripts we have 99 main windows while in smartforms we have only 1 main window.
5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .
6. In scripts we can print the text in only two character formats.
while in smartforms we can do with more.
7. In scripts we dont have line types while in smartforms we have linetypes.
8.Multiple page formats are possible in smartforms which is not the case in SAPScripts
9.It is possible to have a smartform without a main window .
10.Labels cannot be created in smartforms.
11.Routines can be written in smartforms tool.
12.Smartforms generates a function module when activated.
SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...
also refer
difference between smartforms and scripts
Diff betwen Scripts & smartforms
advantages of smartforms over scripts
Whenever a smartform is created, a funciton module gets generated. So, we can access the smartform in different clients. But in case of scripts, it is not so.. So, scripts are client dependent.
Smart Forms are implemented using the Function Module SSF*, and all the logic lies in the FM. Function Modules are client independent objects, so Smart forms are also client independent
SAP Scripts are the Layout Forms that you design and there are aviable in the client in which you have created them, for making them available you have to copy across the clients.
Because, Sapscripts are saved in ITF format as text in client dependant tables STXH and STXL. smartforms are not saved in client dependant tables and visible across clients.
SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. As you have noted correctly, client dependence is a fundamental one.
Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports; if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean. Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.
Conversely, a Smart Form is significantly more robust and complex. For instance, it can contain program nodes and nested tables with patterns. When a Smart Form is compiled, it generates an ABAP function module and these are always client-independent. This is appropriate, given that this form has more in common with an ABAP program than its predecessor. For instance, when a print program calls a Smart Form, the form itself takes over to produce output, without any further direction from the print program. In fact, the join is so seamless that I often find myself using a Smart Form's Initialization section for logic to handle any data gathering not handled by the print program. I would never even think to attempt this with SAPscript.
I suspect several factors figured into SAP's decision to make Smart Forms client-independent, including customer feedback. There are significant advantages to client-independence. For instance, a change made in one development client happens immediately across all development clients. Among other things, this means we don't have to waste time figuring which client contains the most recent version -- they all do! In addition, transporting Smart Forms is easier, since we can safely bundle them together in the same transport as their client-independent print programs (no worry about mixing client-dependent and independent objects).
Reward points for useful Answers
Regards
Anji

Are SAP programs client dependent?

hi,
send me replay

Hello
The following repository objects (basis = 6.40) are defined as client-dependent (-> function module TR_CHECK_TYPE):
LIMU FSEL Field Selection SYST X
LIMU VARI Report Program System Variant SYST X
R3TR COC1 CO: Cost Centers SYST X
R3TR COC2 CO: Activity Types SYST X
R3TR FORM SAPscript form SYST X
R3TR LODS HRDSYS: Logical information object client-dep. table E SYST SYST X
R3TR PCYS HR: Transport standard personnel calculation rules SYST X
R3TR PHDS HRDSYS: physical information object client-dep. table E SYST SYST X
R3TR SBNL Logical Information Object for BDS SYST X
R3TR SBNP Logical Information Object for BDS SYST X
R3TR SBNR BDS: Relationship Between Information Objects SYST X
R3TR SBPL Logical Information Object for BDS: Bid Invitation SYST X
R3TR SBPP Physical Information Object for BDS SYST X
R3TR SBPR BDS: Relationship Between Information Objects SYST X
R3TR SBRL Logical Information Object for BDS SYST X
R3TR SBRP Physical Information Object SYST X
R3TR SBRR BDS: Relationship Between Information Objects SYST X
R3TR SBSL Logical Information Object for BDS SYST X
R3TR SBSP Physical Information Object SYST X
R3TR SBSR BDS: Relationship Between Information Objects SYST X
R3TR SBTL Logical Information Object for BDS SYST X
R3TR SBTP Physical Information Object SYST X
R3TR SBTR BDS: Relationship Between Information Objects SYST X
R3TR SBWL Logical information object for BDS SYST X
R3TR SBWP Logical information object for BDS SYST X
R3TR SBWR BDS: Relationship between information objects SYST X
R3TR SRHL SRM: Hierarchical Lists SYST X
R3TR SRLD Language-Dependent Client-Specific Retrieval Index Objekt SYST X
R3TR STYL SAPscript Style SYST X
Regards
Uwe

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

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.

Are risks client dependent or independent in GRC 10.0?

Hi Experts!
My bosses has a question:
Are risks client dependent or independent in GRC 10.0?
Logically I would say client dependent, but they need a much official answer.
Could you please someone give this info, who has an installed system.
Thanks for your help!
Peter!

Hi if you're referring to risks generated after analysis 'YES' it's client dependent, basically you analyse risk against the user/role assignment. If you're talking about the risk for initial load I've no system to check but since they're considered as database table entries from technical standpoint, they're client dependent objects only.
Regards,
Asok Christian

Activating switch in switch framework is client dependent?

Similar Messages

Maybe you are looking for