Differences between attribute and user defined attributes

1.what is commit block

When uncommitted access is enabled (by default)
Commit Block - number of blocks modified before a sycornization point occurs
Relates to how calc scripts are processed and written to the database during a transaction.
If this setting is too low, Essbase will automatically adjust it.
Default setting is 3000.
Brian Chow

Similar Messages

Difference Between BADI and User Exits

Hi..
generally BADIs & User Exis are used exensively in SAP SD...
Can anybody throw some light waht is difference between them ...
Kindly please reply......
Regards
Nisha

Hi
ifference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Differences between BADIS and User-exits

Hi everybody,
I am new to ABAP and wonder what are the differences between BADIS and User-Exits. I read paper but did not find a SAP documentation yet.
Does anybody know where to find a sap document which explains both technologies?
Greetings, AD

Hi,
User-Exit is a specific place in a transaction-process where SAP offers
third parties to include there own business functionality. Actually
User-Exit is the namespace used for Exits programmed by SAP specifically
for SD. For the other modules it's called Customer-Exit.=20
>Business Add-Ins (BADI) =20
The use of object orientated code within SAP has lead to new method of
enhancing standard SAP code called Business Add-Ins or BADI's for short.
Although the implementation concept is based on classes, methods and
inheritance you do not really have to understand this fully to implement
a BADI.
For better understanding visit.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/779183#
Hope it was useful.
Thansk,
Sandeep.

Difference between administrators and users

Hi,
I just created a new site for my client on Business Catalyst, using Adobe Muse, and would like to give my client acces to the sites tools. The site has settings for creating User Roles. What is the difference between an Administrator role and a User role. Are there limits on how many Administrators and/or Users there can be? Thanks.
Edit: I think I'm getting a few ideas on how it works from this link http://helpx.adobe.com/business-catalyst/using/site-users.html#id_37324 but still not sure. I gather from the thread that there is a limit of 3 administrators. Does this include administrators plus users to total 3? Thanks.
Barbara

"Administrators" and "Users" are two different (and default) User Roles <http://helpx.adobe.com/business-catalyst/using/user-roles.html> on a BC site that distinguishes between a site admin/user's role or access permissions. Every BC site irrespective of it's plan has 3 admin/site users <http://www.businesscatalyst.com/pricing/monthly> that can be later upgraded to a higher number from the Partner portal for non-trial sites that are under BC standalone subscription <http://helpx.adobe.com/business-catalyst/kb/detailed-plan-breakdown.html#id_32561>.
Thanks,
Vinayak

Difference between EO and VO Transient Attributes

Guys,
We do have Transient attributes at EO and VO Level. Are there any difference in that?
Can you give me use cases where we need to prefer EO Transient attribute instead of VO Tranisent attribute or Vice versa...
Any help appreciated....

EO transient Attribute - behave like a column in the db table.. either it can be mapped tothe db column or not..
VO transient attribte - behaves like a query attribute.. its just used to mape the attribute with the underlying EO attributes.. or for any calculations to be made based on other attributes..

Diff between BADI and USER EXITs

Hi,
What is the difference between the BADI and USER EXITs?
Thanks,
Satish

HI
GOOD
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......
THANKS
MRUTYUN

What is the main difference between Enhancements and BADI.?

What is the main difference between Enhancements and BADI.?plzz tell
Edited by: Alvaro Tejada Galindo on Feb 13, 2008 3:48 PM

CMOD is the Project Management of SAP Enhancements (i.e., SMOD Enhancements). SMOD contains the actual enhancements and CMOD is the grouping of those SMOD enhancements.
Difference Between BADI and User Exits
BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
BADI's are oops based.
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.

Difference between Userexit and BADI

can any one explains about the difference between Userexit and BADI and BAPI & BADI..
how to process Error Codes in ALE?

BADI is just an object-oriented version of user-exit. Instead of entering program code into some function module (as in customer-exit), you define some class which has to implement predefined methods and those methods are fired at predefined points just like an old user-exit. Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently.
<b>BADI is technology of user exit? and BAPI is technology of aplication interface.
U can use BAPIs for create a material, for example.</b>
<b>Difference Between BADI and User Exits</b>
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
Regards,
Pavan

Difference between Userexits and BADI

Pls give me the Difference between Userexits and BADI.

Hi,
hope this is helpful
Difference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Difference between collect and move stmts

hi
anyone plz explain...
1. Difference between collect and move stmts
2. Badi and user exit.
gowri

Hi,
1.COLLECT:COLLECT is used to create unique or compressed datsets. The key fields are the default key fields of the internal table itab .
If you use only COLLECT to fill an internal table, COLLECT makes sure that the internal table does not contain two entries with the same default key fields.
If, besides its default key fields, the internal table contains number fields,the contents of these number fields are added together if the internal table already contains an entry with the same key fields.
If the default key of an internal table processed with COLLECT is blank, all the values are added up in the first table line.
If you specify wa INTO , the entry to be processed is taken from the explicitly specified work area wa . If not, it comes from the header line of the internal table itab .
After COLLECT , the system field SY-TABIX contains the index of the - existing or new - table entry with default key fields which match those of the entry to be processed.
COLLECT can create unique or compressed datasets and should be used precisely for this purpose. If uniqueness or compression are unimportant, or two values with identical default key field values could not possibly occur in your particular task, you should use APPEND instead. However, for a unique or compressed dataset which is also efficient, COLLECT is the statement to use.
If you process a table with COLLECT , you should also use COLLECT to fill it. Only by doing this can you guarantee that the internal table will actually be unique or compressed, as described above and COLLECT will run very efficiently.
If you use COLLECT with an explicitly specified work area, it must be compatible with the line type of the internal table.
In 'move' the actually data copies into another data field
2.
Difference between BADI and USER-EXIT.
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.
A. BAdI Definition
1. SE18
2. Enter the name for the BAdI to be created in customer namespace and press "Create".
3. Enter a definition for your BAdI and on the interface tab enter a name for the BAdI interface. SAP proposes a name and it is pretty good. Meanwhile a BAdI class is also created which is not in our concern.
e.g for "ZTEST", SAP proposes "ZIF_EX_TEST" for the interface and "ZCL_EX_TEST" for the class.
4. Save your BAdI.
5. Double-click on the interface name. It will pass to a Class Builder session to make you implement your interface. If you are not familiar to the Class Builder; it's a bit like Function Builder and it will be easy to discover its procedure.
6. Save and activate your interface.
B. Calling your BAdI from an application program
1. Declare a reference variable with reference to the Business Add-In interface.
e.g. DATA exit_ref TYPE REF TO zif_ex_test.
2. Call the static method GET_INSTANCE of the service class CL_EXITHANDLER. This returns an instance of the required object.
e.g.
CALL METHOD CL_EXITHANDLER=>GET_INSTANCE
CHANGING instance = exit_ref .
3. After those two steps, you can now call all of the methods of the BAdI where it is required in your program. Make sure you specify the method interfaces correctly.
C. BAdI Implementations
1. SE19
2. Enter the name for the BAdI implementation to be created in customer namespace and press "Create".
3. It will request the BAdI definition name to which this implementation will be tied.
4. Enter a definition for your implementation and on the interface tab enter a name for the implementing class. Again SAP proposes a name and it is pretty good.
e.g for "ZIMPTEST", SAP proposes "ZCL_IM_IMPTEST".
5. Save your implementation.
6. To implement a method, just double-click on the method name and you will be taken to the Class Builder to write the code for it. Here you redefine the BAdI interface methods.
7. You must activate your implementation to make it executable. You can only activate or deactivate an implementation in its original system without modification. The activation or deactivation must be transported into subsequent systems
Regards

Difference between automatic and non-automatic page attributes

Hi,
Can anyone tell me difference between automatic page attributes and non-automatic page attributes?
and also difference between stateful and stateless mode with examples?
Thanks
Narendra

Hi Mullapudi,
If you mark a page attribute as u2018automaticu2019 (auto in the system), the attribute automatically gets its values via the calling URL or
via the navigation process from other pages.
This kind of attribute only has to be declared for one page.
It is identified by its name equivalence.
If another page uses a parameter with the same name,
at runtime that parameter automatically
gets the same values as the attribute.
Non-automatic page attributes
If you flag a page attribute as non-automatic, the attribute gets its values from the class attribute.
The visibility of page attributes when parameters are transferred between BSP pages depends on whether the navigation is explicit or implicit.
Explicit navigation
For example, if navigation->goto_page(page.htm)
Implicit navigation
With implicit navigation, the page attributes are transferred automatically from OnInputProcessing to OnInitialization, both in stateful and stateless mode.
The auto page attributes are refilled by the request, both in stateful and stateless mode.
Reward if Useful...
Regards,
Anita. B

BP User Defined Attributes -- Error

Hi experts!!
The customer i am working on needed some extra fields on the Accounts screen page, so i defined all User Defiened Attributes from 1 to 10 and added them from the Node MARKETING of the component BP_HEAD.
When i try to save the Account (after filling one of the attributes) I get the following error msg: Classification data is already maintained for business partner.
The Account can be saved and replicated to the ERP if the attributes remain empty.
What am i missing here???
Is there a connection between the attributes and account classification ??
Thank you in advance

The error was fixed with Note 1271004.
BUT .. now when i Save the Account with User Defined Attributes filled the replication to ERP does not happen..
If the attributes are empty it gets replicated.
Any ideas???
Please help!!

Limitations of User Defined attributes in USR.

11.1.1.3
I added a notes field to the user defined fields of a user, customer wanted a textarea to makes notes in reagarding the user in question.
Can someone tell me where the limitations of these fields are listed?
I added a large textfield and the system happily accepted the size and made a clob in the db.
I have added the permissions in the policy to make it visible in create as well as in view and modify, all that works fine.
However, when I modify the field by simply writing a small note in it....
I save the change, no exceptions, no error whatsoever
the correct data gets into the clob field in the USR table
but the text area in the user view show the entity object name and reference/instance instead...
i.e.
i add the text "test" into the text area, press save
the fields then shows me...
weblogic.jdbc.wrapper.Clob_oracle_sql_CLOB@65e1
So, I am looking for where this limitation is mentioned in the manuals or trying to find out if its a bug.
Reason I am wondering is because there is a field (USR.USR_NOTE) in the DB which is a CLOB but I cant
find any reference to that in the User Configuration, i.e. what does the system use it for?
So, if there is a limitation on the size of fields in the User Configuration, where can I see them?
I looked in the System and developer manuals and I see nothing on that there.
What is the maximum and where can I see that defined?

Hello Antilles.
The user defined attributes that you refer to it´s used to specify additional attributes.
You can find more useful information about this topic in this link: http://download.oracle.com/docs/cd/E14373_01/appdev.32/e11838/nav.htm
Regards Pedro

Help needed in creating user defined attribute

Hi all,
I want to create user defined attributes and make it available for all users in sun LDAP5.2,I have followed the below mentioned steps,
1.Under configuration-schema i have created attribute named "ldapproducts"
2.I have created new object class "userproducts" and made the parent to be "inetorgperson" and added my "ldapproducts" attribute in required attribute.
Now,in directory tab,Iam trying to add the "ldapproduct" attribute for each user but my defined attribute i.e,"ldapproducts"is not available in the "Add Attribute"list
please let me know do i need to do some steps or do i need to do any changes in DS files..
waiting for ur replies...
thanks in advance.

Hi,
I dont know the solution for this, but heres a work arround
//create new label some where else in the excel sheet as shown below
Label lblcmbdata;
for(int i=0; i<1000; i++)
             lblcmbdata = new Label(75, i, (i+1)+" satish", format);
             sheet1.addCell(lblcmbdata);
}//set the validation range as shown below
writableCellFeature.setDataValidationRange(75,0,75,1000);
Label cmb = null;
cmb = new Label(0, 1, "Select",format);
cmb.setCellFeatures(writableCellFeature);
sheet.addCell(cmb);this will create a combo list with 1000 values
also you can keep the data to be populated in the different sheet in same workbook by creating a named range as below
workbook.addNameArea("cmbdata", sheet1, 0, 0, 0, 1000);
// then fill the data in sheet1
Label lblcmbdata;
for(int i=0; i<1000; i++)
                lblcmbdata = new Label(0, i, (i+1)+" satish", format);
                sheet1.addCell(lblcmbdata);
//set the validation named range as below
writableCellFeature.setDataValidationRange("cmbdata");
Label cmb = null;
cmb = new Label(0, 1, "Select",format);
cmb.setCellFeatures(writableCellFeature);
sheet.addCell(cmb);Thanks and Regards
Satish

Differences between Roles, Schemas, Users and Logins.

I need differences between Roles, Schemas, Users and Logins. Can anyone help me. Thanks in advance

Roles:
I think of creating roles in the database to group users of like
function. Roles are granted certain permissions in the database. You
should become familiar with the fixed database roles since these will be
utilized once you start creating users within the database. Also, once
you see the type of permissions that are granted to each role, is makes
more sense.
Schema: there can be several schemas in a database,
which will house different types of objects such as tables, indexes,
stored procedures, functions, etc. Users own schemas. Looking into
the AdventureWorks database illustrates this concept, with several
schemas like HR, Production, etc.
Login: Think about login as
gaining access to the SQL Server instance. If a user account is not
granted any permissions within the instance, you basically just were
able to unlock the door and enter the room, by creating a user you then
grant access to the database objects or principals, and can begin to
work with them.
Users: Users own schemas, and as such will be
able to manipulate the objects they own. Some of the manunipulations
are very permissive, such as creating tables, indexes, stored
procedures, functions, etc. These are developers and administrators.
Users
are created and granted permissions for application use, which will
have select, update, insert, and delete and execute permissions to a
finite set of objects in the schema, for which the application will need
to function properly.
In a client server database, as an
example, of the structure. Roles were defined which provides the
permissions to the database objects in the database, which only has one
schema 'dbo'. One SQL server login was created with the same username,
and dbo is the assigned default schema, and the roles assigned to that
username.
In the application, each specific user is given there own
"application" login which is mapped to the one defined sql server
login.
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/

Differences between attribute and user defined attributes

Similar Messages

Maybe you are looking for