Smartforms client-independent?

Hi every body,
Please help in,
1)Why smartforms are client-independent?
2)What are SAP memory and ABAP memory?
3)How to use the option "Outline" in scripts while creating a paragraph fomat?
4)What are the control commands RESET and SUMMING in scripts and their syntaxes to use them (sample codes)?
5)What is exactly HIDE?
Thanks in advance,
SUMAN.

hi,
1Q The reason why SmartForms are client independent is because when you activate a SMartForm, SAP actually generates a Function Module (which as you know is client independent). The Print Program (or as SAP likes to refer to them these days - Application Program) calls your generated FM.
2Q SAP Memory
SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens
The SAP memory, otherwise known as the global memory, is available to a user during the entire duration of a terminal session. Its contents are retained across transaction boundaries as well as external and internal sessions. The SET PARAMETER and GET PARAMETER statements allow you to write to, or read from, the SAP memory.
ABAP/4 Memory
ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data
to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.
The contents of the ABAP/4 memory are retained only during the lifetime of an external session (see also Organization of Modularization Units). You can retain or pass data across internal sessions. The EXPORT TO MEMORY and IMPORT FROM MEMORY statements allow you to write data to, or read data from, the ABAP memory.
https://forums.sdn.sap.com/click.jspa?searchID=2274783&messageID=2489768
ABAP/4 Memory
ABAP memory is a memory area that all ABAP programs within the same internal session can access
using the EXPORT and IMPORT statements.
Data within this area remains intact during a whole sequence of program calls. To pass data
to a program which you are calling,
the data needs to be placed in ABAP memory before the call is made.
The internal session of the called program then replaces that of the calling program.
The program called can then read from the ABAP memory.
If control is then returned to the program which made the initial call, the same process operates in reverse.
3Q Name of the highest-level paragraph in an outline hierarchy. The outline hierarchy of various paragraphs is formed by assigning a common highest-level outline paragraph to all outline paragraphs.
Example: Three outline paragraphs, AA, BB, and CC, are to be defined, where AA is the highest and CC the lowest paragraph in the hierarchy. AA is to be used, for example, for chapter headings, BB for section headings, and CC for headings within the sections.
Paragraph AA must be specified as the highest-level outline paragraph for all three paragraphs. Make sure that AA, this paragraph itself, is entered as the highest-level outline paragraph for AA.
4.SUMMING: Adding program symbols
Program symbols can be added with the SUMMING command. The command only needs to be defined once. Each time that the specified symbol is edited, its current value is added to the sum field. Several program symbols can also be added in a sum field.
Sntax:
/:SUMMING program symbol INTO sum symbol
As SAP script cannot define sum fields dynamically, the sum symbol must be in a structure of the calling program, which was declared with TABLES.
5. Hide is a keyword used in Interactive reporting.it is used to hold the value till the next screen

Similar Messages

Smartform text modules client independent...

Hi Guys,
Are smartform text modules also client independent ?
If I do some change in text modules in one client its not getting reflected in other. Can someone tell me why ?
Thanks.
Tushar.

Hi Tushar,
As Phani and Rich mentioned Text module are client dependent similar to smartforms. You have to transport from one client to another.
Lanka

Why SAP Script client-dependent but Smartform is client independent

Hi All,
What are the fundamental reasons for justifying that SAP Script is client-dependent but Smartform is client independent ???
Regards
jaman

hi,
why script is client dependent?
the reason is:
in script, to display some table data, we use text elements, where the text elements access the dictionary tables data. there the table from which we are fetching data, that may be a client dependent table, so first the text elements became client dependent. as script use text elements, script also became client dependent.
hope u got the point. to b simple, the text elements r client dependent, there fore scripts also became client dependent.
smartforms are client independent. bcoz it doesnt use any text elements. it will be executed through a function module, as you know function modules are client independent, the smartform also became client independent.
hope ur clear, if any doubts, plz post them back.
reward if helpful.

Why SAP Script are Client Dependent, Smartforms are client-independent.

why SAP Script are Client Dependent,Smartforms are client-independent.
Edited by: Srinivasa Reddy Ariga on Oct 27, 2008 12:28 PM
Edited by: Srinivasa Reddy Ariga on Oct 27, 2008 12:49 PM

Before you do anything else, read this: Welcome and Rules of Engagement
Google is your friend. Try keywords smartforms client dependent Next time - search first and ask second.
oh, and it helps to get the correct forum...

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.

Client dependent & client independent objects

Hi All,
What is meant by client independent & client dependent ?
I know that sapscripts are client dependent while smartfiorms are client independent. Also reports & FMs are client independent.
Want to have a better idea on this concept....
Thanks in advance..
Sweta

If you create a table in 010 client in DEV server with CLNT as its first fields type, then you will find that table structure in all clients in DEV server. (i.e client independent)
example: function module, abap program, smart form.
If you create a record in that table in 010 client, you will not find that record in other clients. (i.e client dependent)
Example: script.
Sap script was developed a long back.
smartform is developed to avoid these type of some restrictions
Also:
Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
Like SAP SCRIPTS and STD texts data
where as Client Independent means the data if you create in one client that is available in that as well as in other clients
Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s.SAPscript 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.
MANDT is the field which differenciates the table from Client Dependent and Client Independent Tables.
All the Scripts are Client Dependent Objects
Smart Forms, Function Modules are Client Independent Objects.

Client Independent

What is the client concept in SAP? What is the meaning of client independent?

HI
http://www.sap-img.com/sap-introduction.htm
http://www.sap-img.com/general/what-is-sap--landscape.htm
Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
Like SAP SCRIPTS and STD texts data
where as Client Independent means the data if you create in one client that is available in that as well as in other clients
Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s.SAPscript 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.
In commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables.
There are different meanings.
Functionality point of View CLIENT is the highest hierarchial Orgn entity in any module
Clients again are different from each box/system like DEV,Quality and PRD.
Generally we create more clients in DEV system one for technical and other for sandbox and other for Customization etc.
This is a Mandatory field in all tables.
Each client has its own set of Application,master,data. Hence we need to populate data for each clinet separatly.(I think you cant say "implementing the SAP for the client")
Client Independant: These objects are not specific to any client. And it is universal which can be viewed,changed across the clients.
Client Dependant: These are the objects can be viewed, changed for the client for which it has been assigned. Other clients do not have access on these objects.
In SAP, all objects are finally stored as tables. "Mandt" is key field which determines whether the object is client dependant or not.
Client Independant transport requests will make the transported objects available across the clients. and Client dependent transport request make the objects available only for the client mentioned by field "Mandt"
look here:
http://help.sap.com/saphelp_nw04/helpdata/en/b7/8a9a3aaf894871e10000000a114084/frameset.htm
Client Independent(cross client) objects can be accessed from any client without transporting. For example, Reports and smartforms are client independent that means if you create a report or smartform in one client, this report and smartform can be viewed in another client without transporting.
Where as client dependent objects can be viewed or accessed only in the client in which you create them.
All scripts are client dependent and some tables are client dependent.
There are two types of objects in SAP, client dependent and client independent. Objects used in several clients are called client independent while objects used in a specific client is called client dependent. To identify if a table is client dependent, one can use tcodes SE11 or SE12. In the table field attributes, if the MANDT field is present that table is client dependent.
Almost all the programs and database objects are client independent.
Only the data in Database tables are client dependent.
Go through the below PDF file, it is having 4 pages which explains why SAP has Client independent and Client dependant..
http://www.sappoint.com/basis/clntadm.pdf#search=%22ABAP%20%2B%20client%20independent%20and%20client%20dependant%20%22
Create client????
Goto Tcode su01,
Client 810
Give user name sap*
password:06071992.
presss continue.
In the next screen :
User: Sapuser
Press creat buttom in the application tool bar ,
In address tabstrip : give ur name last name and first name ,
click on logon data: here u give the initial password, suppose password is = nihar
click on profile give : SAP_ALL
SAP_NEW
Press save buttom .
Now ur client 810 created
Goto the SAP EASY Access Screen
Give client : 810
User: sapuser
password: nihar
press enter
Again system will ask for final password.
Give here exiting password: nihar
new password: india.
check this
needed very urgently: ABAP real time questions and answers
check the below link u will find lot of info..
https://forums.sdn.sap.com/click.jspa?searchID=1815764&messageID=1967306

Client dependent vs client independent

Hi,
CASE-1 :
there are two clients using one Application
Server .
q1) Are scripts and smartforms client-dependent/independent.
CASE-2 :
There are two clients using different Application Servers
q1) Are scripts and smartforms client-dependent/independent.
if smartforms are client independent so why am not able to see it
from dev to qat without trasporting smartform.
as we know smart forms are client independent so under what condition i can see my smartforms in another client without transporting to other client.
please help me out.

Scripts are always client dependant and Smart forms are
client independant.
You will be able to see your smartforms in all the clients in the same application server.
For examples in DEV system there might be three clients
100, 300, 500. So you will be able to see ur smartforms in
all the three clients.
But in order to see SapScripts you will have to transport the form from each client to another.
To see the smartform in you QA server which is a different appplication serer you will have to transport objects.
Regards,
Sudhir Atluru
Reward points for helpfull answers

Client dependent n client independent?????????/

hi this is vinod,
please explain the concept behind of script client dependent and smartforms r client independent pleaseee its urgent????????????

Hi,
Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
Like SAP SCRIPTS and STD texts data
where as Client Independent means the data if you create in one client that is available in that as well as in other clients
Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s.SAPscript 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.
rewards if useful,
regards,
nazeer

Smart Forms are Client Independent..

Hi ,
I Have one doubt.. about the Smart Forms are Client Independent.
Client Independent Means Smart Forms are generated function modules.
For example I am generated function module in client 100, can i use this same function module in client 200??
and also can i move the Samrtform from client 100 to client 200??
OR Independent means it is depending Sytem LAND SACPE??
I am confuse. Please any one clarify what EXACTLY MEAN by Smart Forms are Client Independent..
Thanks and Regards,
Vijay.

HI Vijay,
Your Reports are client independent, this means, if you create a report in one client 100 of a dev system, then you can see this report in client 200 of the same dev system.
But SAPscripts are client dependent , this means if you create a script in client 100 you cannot see it in 200 unless you import it using SCC1.
Similarly Smartforms are client independent means you dont have to import it into different clients, it will be available to all the clients once you create in one client 100, like the reports.

Difference between client dependent table and client independent table

hi all,
i m new in sap pls tell me the difference between client dependent table and client independent table.
tell me in detail.
thanks and regards
vikas saini

HI
Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
Like SAP SCRIPTS and STD texts data
where as Client Independent means the data if you create in one client that is available in that as well as in other clients
Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
As for SAP -- Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.
Few more reasons why....? Please read below:
SAPscript technology is based on a mainframe product from the 1980s.SAPscript 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.
What is client dependent and Client Independent
https://www.sdn.sap.com/irj/sdn/forums

Why sapscripts are client dependent & smart forms are client independent?

why sapscripts are client dependent & smart forms are client independent?

You developed the script in development client , you can't find the same in testing client even though the server is same.
Where are You developed the smartform in development client , you can find the same in testing client even though the server is same.
Few more reasons why....? Please read below:
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.
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).
Check the beloe links for more information
script and smart forms
http://www.sap-img.com/smartforms/smartform-sapscripts.htm

What exactly is the diff between client dependant and client independant te

Hi gurus,
What is the diff between client independant and client dependant term.. I initially had a confusion related to client independant and client dependant Transport requests, where else are these words applicable, do they apply to data as well, if so how? any links to help me understand the difference..
regards,
kishore

Hi Kishore,
Client Independant: These objects are not specific to any client. And it is universal which can be viewed,changed across the clients.
Client Dependant: These are the objects can be viewed, changed for the client for which it has been assigned. Other clients do not have access on these objects.
In SAP, all objects are finally stored as tables. "Mandt" is key field which determines whether the object is client dependant or not.
Client Independant transport requests will make the transported objects available across the clients. and Client dependent transport request make the objects available only for the client mentioned by field "Mandt"
Regards,
Dinesh D

Which are client independent and dependent objects in SAP ABAP

which are client independent and dependent objects in SAP ABAP

Hello Jagrut
A special kind of objects are client-<u>dependent </u>repository objects. These objects have to be treated specially in the way that they have to be imported into their specific target client. In contrast, client-independent repository objects can be imported into any client.
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
Regards
Uwe

Client Independent Authorizations

Hi,
I would like to know, whether there are any ways in performing authorizations checks, irrespective of clients.
I have a scenario where only 1 user, say USER01 in client 100 should be authorized to view, execute, change certain programs and other data dictionary objects in the client 100. All other users in this client 100, should be authorized only to execute the program and not to view any of the programs and dictionary objects.
This should not be the case with any other user of the other clients of the server.They should not have any rights over these specified objects.
Kindly help me out with a solution for the same.
Venkat

Hi,
The authorizations are client independent. Whatever auth objects that you create and assign to the users in a client will NOT reflect in other clients. In fact the users are also client dependent. Having access to one client, does not guarantee access to other clients.
This is the defaul functionality.
regards,
Ravi
Note : Please mark the helpful answers.

Smartforms client-independent?

Similar Messages

Maybe you are looking for