Difference between Professional User and Limited Professional User?

SAP Members.
Hi \ Salam,
I want to know the difference between a Professional User and a Limited Professional User. Why do we create them and what are the advantages of having them?
Your input will be highly appreciated.
Regards,
Mohammed Ali Khan.

Yup. It means, in Limited Professional, you can display posted documents, view reports etc. & can create/change through single transaction, e.g. FB60. It is generally provided to management/heads.
Professional license is a fully functional license. You can use any transaction no matter if its create, change or display
BR
PS: The thread is not related to ERP Financials/

Similar Messages

  • Difference between Professional application and self-service application

    hi frntz,
    May I know the difference between professional application and self-service application in oracle E-biz. Why we cant able to use both at same time ?

    Hi;
    Please check below which could be helpful for your issue:
    http://download.oracle.com/tech/blaf/specs/blafusers.html
    Regard
    Helios

  • Difference Between Database Schema and Database User Account ??

    First i would like to know what an Oracle Database schema exactly is ?
    And what is it for and also What is it's use ?
    Later the exact "Difference Between Database Schema and Database User Account".
    I googled about it but i'm unable to find out it's The difference,
    Please try to explain in a simple manner........
    Thank you very Much in Advance..........

    user13655582 wrote:
    Greate example. but i would like add one more point..
    a user is a schema and schema is a user. but when this applies to the user that he become a schema, only if he has got some objects. so we can say while creating the user which dosent contain any objects called simple user account but afterwords when he has got an objects then we can say its a schema as the above user has shown you through the exampleIt is just word-play. There is nothing in like a 'status' indicator to say "USER_A is just a user but USER_B has become a schema". Many people use the terms "user" and "schema" interchangeably, and some very good DBAs will insist this is correct. I don't disagree with them even though I usually try to make the distinction.
    In a typical application, all of the objects (tables, procedures, etc) that implement the app will be owned by a "application schema owner" - a user which exists for the sole purpose of owning the schema. Said user will have no privileges at all .. especially not CREATE SESSION. Except for possible maintenance activity no one ever actually connects as this user. User accounts are then given to actual humans who connect with their own accounts. The accounts have the necessary system and object privileges granted to them - via a role. One could also create a special account (let's call it APP_ADMIN) that is used for maintenance and batch operations within the application.

  • Difference between WEP, WPA, and WPA2 and better suggestion to use for shared family users

    What is the difference between WEP, WPA, and WPA2? My router is set up on my family PC and connected to a modem so I access Wi-fi through my laptop and my sister has a laptop too and uses our family network to get internet. I just set up a WPA today, so will we all be able to get internet (along with my family using the pc, and my sis on her laptop, even at the same time) protected? (like nobody else using our network)

    Wired Equivalent Privacy, commonly called WEP is 802.11's first hardware form of security where both the WAP and the user are configured with an encryption key of either 64 bits or 128 bits in HEX. So when the user attempts to authenticate, the AP issues a random challenge. The user then returns the challenge, encrypted with the key. The AP decrypts this challenge and if it matches the original the client is authenticated. The problem with WEP is that the key is static, which means with a little time and the right tool a hacker could use reverse-engineering to derive the encryption key. It is important to note that this process does affect the transmission speed.
    WPA builds upon WEP, making it more secure by adding extra security algorithms and mechanisms to fight intrusion.
    WiFi Protected Access (WPA) is the new security standard adopted by the WiFi Alliance consortium. WiFi compliance ensures interoperability between different manufacturer’s equipment.WPA delivers a level of security way beyond anything that WEP can offer, bridges the gap between WEP and 802.11i networks, and has the advantage that the firmware in older equipment may be upgradeable.
    WPA2 is based upon the Institute for Electrical and Electronics Engineers’ (IEEE) 802.11i amendment to the 802.11 standard, which was ratified on July 29, 2004. The primary difference between WPA and WPA2 is that WPA2 uses a more advanced encryption technique called AES (Advanced Encryption Standard), allowing for compliance with FIPS140-2 government security requirements. 

  • Difference between target schema and target user

    hi,
    Can anyone explain to me what is the difference between target schema and target user? examples will be more welcome then theoratical explanation.
    thanks so much

    In Oracle database schema and user is the same things (if you use general authentication by database).
    When used external authentication (for example with Windows domains/active directory) schema is a owner of database objects group and you should specify mapping between external usernames and schema to which this user has access when connects to database.
    For example:
    - windows domain user CORPDOMAIN\USER1 can connect to oracle database schema SCOTT;
    - windows domain user CORPDOMAIN\USER2 can connect to oracle database schema SCOTT;
    - windows domain user CORPDOMAIN\ADMIN can connect to oracle database schema SYSTEM;
    Oleg
    Message was edited by:
    tsiboleg

  • Difference between dynamic actions and user exit

    Hi,
    Please help me in when to use table T588z and user exit to write code for dynamic actions.
    Thanks,
    Venkat

    Hi Prasad,
    Find the difference between Dynamic action and user exits.
    Dynamic Action                                              User Exits
    1. Here only initialization of an infotype                    1. Along with initialization of an infotype,                  depending upon other infotype                                    validation also can be done like in
        can be done.                                                        IT 16 the contract end date can not be
                                                                                    entered more than 6 months.
    2. Less time consuming to write.                             2. Require programming approch so more
                                                                                    time consuming.
    3. Table T588Z                                                       3. PBAS0001
    Br/Manas

  • Difference between Real User Experience Insight and Webalizer?

    Dear All,
    Can u tell me that is there any difference between Real User Experience Insight and Webalizer?
    If both are functioning almost same then why RUEI is expensive
    Please must reply

    Webalizer uses Web Server logs however RUEI does not use web server logs it monitors Network Traffic without interfering in application which does not affect application performance...
    For using Webalizer Application code is modified but not in the case of RUEI
    The most important one is that Webalizer does not provide Sufficient and Efficient information as does the RUEI because it can replay the whole session called FULL SESSION REPLAY, Which helps finding errrors on specific pages. Also helps finding delays in transactions.
    RUEI is deployed either by copy port or Tapping which create duplicate copy of each request to web server and pass it to RUEI for Analysis
    Regards
    Ali Asadullah

  • Difference between BADI's and User Exits.

    Hi Experts,
        I want to know the difference between BADI's and User Exits....
    What i know is BADI's are Object oriented But User exits are normal Programs.....i think in User exits also we can write Object oriented program.....
    AND one more is BADI's are multiple use but user exits are not,,,,
    IF BADI's are multiple use like all BADI's are multiple use or some....is there any performance issues,,,i need to know gurus .......and please provide to me more than this.........
    Thanks
    Venkat

    User exits are some provisional space in the standard program for you to write your own business functionality.
    BADI's are soem of the business add-in's that comes along with the standard SAP product but are disabled as most of the customers do not need it. So for those customers who need this will have to activate it and that functionality will be avilable in the transaction.
    - guru
    Reward points for helpful answers

  • Difference between Adhoc package and user created package

    what is the difference between Adhoc package and user created package.
    Thanks,

    Hello Asha,
    Here are some links which would be helpful for you to get started with BPS
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/s-u/sap bw business planning and simulation - how to guides list.htm
    https://media.sdn.sap.com/public/eclasses/teched04/BW253_files/Default.htm#nopreload=1
    https://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/3040dd5d-0501-0010-baa8-fc0aafa88c40 [original link is broken]
    http://help.sap.com/bp_biv235/BI_EN/html/BW/CostCtrPlan.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/d-f/enhancements bw-bps formerly sem-bps in sapnetweaver 04.ppt
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d90209f-0501-0010-59a2-9243ac94a4d7
    http://help.sap.com/saphelp_nw04/helpdata/en/05/242537cedf2056e10000009b38f936/frameset.htm
    Also sent you some useful documents. Please check your mail.
    Regards,
    Praveen

  • Difference between PDF user's password and PDF owner's password?

    What is the difference between PDF user's and owner's passwords? When creating a document, which one to use?

    The user password, if set, is what you need to provide in order to open a PDF. Acrobat/Reader will prompt a user to enter the user password. If it's not correct, the document will not open.
    The owner password, if set, controls permissions, such as printing, editing, extracting, commenting, etc. Acrobat/Reader will disallow these things based on the permission settings. Acrobat will require this password if you want to set/change permissions.

  • Difference between customer exit and user exit?

    hi experts
    difference between customer exit and user exit?

    These r the main differences between user exits and customer exits
    1) user exits r subroutines where as customer exits r function modules
    2) user exits r not upgraded where as customer exits r will upgrade
    3) customer exits r used for creating and additional fields or menu items to stadard tcode where as user exits r used for enabling or disabling the fields on the standrd screen or concatenating the key fields,it is not used adding an additional componenats to stadard tcode
    4) customer exits r reusable where as user exits r not reusable.
    Also:
    1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.
    2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.
    BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)
    Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.
    Please go through the following link which will help you understand the exits in a much better way:
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm
    http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
    http://sap.niraj.tripod.com/id21.html
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.sap-img.com/ab038.htm
    User Exits.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    customer exits
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662562d
    Menu Exit.
    http://www.sappoint.com/abap/spmp.pdf
    http://www.sappoint.com/abap/userexit.pdf
    http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm
    http://www.sapdevelopment.co.uk/enhance/enhancehome.htm
    1. Previously there were only user-exits.
    2. Then came the concept of customer-exits.
    3. user exits were nothing but subroutines
    FORM/PERFORM
    called from standard programs.
    4. The FORM defintion was placed inside
    an empty include file.
    5. So It was called EVERYTIME.
    and we need to MODIFY/REPAIR the
    standard include .
    6. Then it came with concept of customer-exit
    7. It consists of calling a FUNCTION MODULE,
    which is called only if
    the user-exit is ACTIVATED (other wise not called)
    In this case, the code in put inside
    a pre-defined Z include.
    8. Functionality of both is same, howerver
    we can note the following important differences
    a) Customer exit is called only if activated.
    (hence, it does not waste resources)
    b) in customer exit, REPAIR does not happen
    to the standard include.
    Exits are basically the hooks whcih SAP has provided to add your own code.
    User Exits: These are provided only SD module .
    They are Empty subroutines with naming like USEREXIT_.
    We need to have Access key to implement them.
    Customer Exits: These are enhancement techniques.
    There are defined in SMOD and implemented in CMOD.
    Types of Customer exits: Function exit, Screen Exit, Menu exit.
    User Exit and Customer Exit are same ,but SAP Exit and Customer exit are different...
    Customer Exit,
    Enables you to determine values for variables by means of Functional Module exit.The function module used is EXIT_SAPLRRSO_001.
    Create a project in CMOD by selecting the SAP Enhancement RSR00001 and assign this to the enhanced proj and activate it.
    Customer Exit
    SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
    • They do not affect standard SAP source code
    When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.
    • They do not affect software updates
    When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.
    Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    SAP EXIT:this processing type contained in variables that are delivered with SAP BW business content.
    http://help.sap.com/saphelp_nw04/helpdata/en/1d/ca10d858c2e949ba4a152c44f8128a/frameset.htm
    User Exits: allow you to add additional functions to the SAP standard.
    Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
    Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
    Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors
    reward points if found useful
    regards
    palak

  • Difference Between Service Account and User Account

    What is the Difference Between Service Account and User Account

    Hello Mohit,
    Basically there are two types of approches which you should understand.
    In many environments, administrators prefer to simply create a domain user account and assign appropriate privileges to it. Then this user account is used in order to start a specific service on a computer.
    In that case there is really no difference between a user account and the so called service accounts. Since this service account is simply a domain user, all the task related to managing the domain users apply to it. For example you
    should keep the password up to date manually. Some environment move step forward and assign
    Deny Logon Locally of this type of service account in order to enhance the security.
    The second concept is Managed Service Accounts. There are plenty of differences between a Managed Service Account and a User Account.
    The Display Icon is different from a view perspective.
    The type of object is different. 
    Managed service accounts password management is automatic.
    You can not create Managed Service Accounts using GUI. They are only created using Powershell.
    You can refer to link below for more inormation:
    Service Accounts Step-by-Step Guide
    Regards.
    Mahdi Tehrani   |  
      |  
    www.mahditehrani.ir
    Please click on Propose As Answer or to mark this post as
    and helpful for other people.
    This posting is provided AS-IS with no warranties, and confers no rights.
    How to query members of 'Local Administrators' group in all computers?

  • Difference between system status and user status.

    Can someone explain to me the difference between system status and user status in details

    Hi,
    As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
    In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
    System statuses will be updated automatically based on business transactions which will be done on SAP.
    For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
    If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
    These user status as per the name, should be updated by the user manually.
    Regards,
    Maheswaran.

  • Exact difference between System status and the user status

    Hi,
    Please tell me the exact difference between System status and the user status .
    how we customize the both in the system
    Thanks & Regards
    Prajith P
    Moderation: Locked. Please, try to find an answer first. See rules of engagement
    Edited by: Joaquin Fornas on Feb 23, 2012 11:14 AM

    Hi,
    As you mentioned there are 2 status can be maintained for documents like Equipment Master, Notification, Maintenance Order & other important business documents.
    In case, client feels that system status is not enough to capture the details of the object, then user status can be used.
    System statuses will be updated automatically based on business transactions which will be done on SAP.
    For example, once the equipment is created, System status would CRTD (Created). If you install the same to some superior equipment or FL, then status would be INST (Installed).
    If you keeping that equipment in Spare, then for that, you have to maintain separate User Status like AVLB (Available in Stock / Spare) so that through IH08, by using User status, you can the report which is available as spare.
    These user status as per the name, should be updated by the user manually.
    Regards,
    Maheswaran.

  • Any difference between Master data and User master data ?

    Any difference between Master data and User master data ?

    hi
    A user master record defines the authorizations assigned to a user. Based on these authorizations one can access the master data.
    Master data - it is the data which is used long term in SAP r/3 system such as vendor master , material master, customer master,
    there is no such thing like user master data to the best of my knowledge
    hope this helps
    regds
    Manan

  • What is the difference between customer exits and user exits?

    hello friends,
    what is the difference between customer exits and user exits?

    Hi
    User exit - A user exit is a three character code that instructs the system to access a program during system processing.
    SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
    UXX: U is for user exits that are defined by the user.  XX represents the 2-digit exit number
    Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.     *-- Mani
    The following document is about exits in SAP :-
    The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. 
    SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
    Types of Exits 
    There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
    Menu Exits
    Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
    SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.
    Screen Exits
    Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.
    Function Module Exits 
    Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. 
    When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. 
    Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs. 
    These calls have the following syntax: 
    CALL CUSTOMER-FUNCTION ‘001’.
    Field Exits
    Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field.  Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100. 
    The field exit concept lets you create a special function module that contains this logic. 
    You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number. 
    In 4.6c, you can use "RSMODPRF" program to create field exits.
    An example of a user exits :-
    MODULE user_exit_0001 INPUT 
        CASE okcode.
            WHEN 'BACK OR EXIT'.
                CASE sy-dynnr.
                        WHEN '100'.
                             SET SCREEN 0.
                             LEAVE SCREEN.
                        WHEN '200'.
                             SET SCREEN 100.
                             LEAVE SCREEN.
                 ENDCASE.
          ENDCASE.

Maybe you are looking for