Validation to restrict the user at parking level

Hi,
I have created a validation to restrict the user to use particular G/L codes only using GGB0. It is working fine and it gives the error message in T-code FB50 & FB60 immediately after entering the un-authorized g/L codes. But still the user is allowed to park the document. and the same validation works in Z tcodes. But in Z tcodes the error message comes only at the time of Simulate/Save as complete or Post.
But i want the error to display immediately after entering the G/L Codes in Z transaction also. Can you please help me to complete the validation by restricting the user to park also

HI,
Yes. Thanks for your valid answer. It will not work in parking T codes. It will work only in Posting T-codes. The Z-tcode what we are using all the parking transaction. Then I should try using the Badi. I will try.
Divya S
Edited by: S Divya on Dec 8, 2011 5:12 AM

Similar Messages

How to restrict the Users at Page level

Hi Gurus,
I want to restrict the users page to page.I am having 3 pages and 3 set of users.If any user having access to page1 then he will not see Page2 & Page3 .For Page2 & Page3 it is same case i.e page2 will displayed to user2 and not to user1 & user3.Same for page3 which will be displayed to user3 only.
Waiting for reply..
Thanks & Regards
Ganesh

Hi,
There is PCDFilter, which can be used to filter role and workset content depending on the context.
I think this can solve your usecase.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3367e690-0201-0010-d285-c69bd884c9f3
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/17968de1-0a01-0010-1f9f-c090fbc7001a
Greetings,
Praveen Gudapati
[Points are always welcome for helpful answers]

How to restrict the user from making any changes in Sales order- item level

Hi to all
How to restrict the users from making any changes in sales order at item level if the same sales order is released by senior user through status profile.
Regards
Anish Parikh
Edited by: anish parikh on Jan 24, 2008 5:16 AM

Hi Anish,
This can be achieved through the roles and authorization.
This can be done through the basis team. they can create user profiles and roles.
For the roles they assign some transaction codes so that they can view the only assigned tr. codes.
Like that ur requirement can be done.
Also u can prevent the user to change any fields in the sales order screen (VA02). for that please modify the authorisations.
Hope i answers.
Reward points if useful.
Edited by: kaleeswaran bhoopathy on Jan 24, 2008 9:57 AM

Is it possible to restrict the user from creating a sibling and allow him to ONLY create child nodes in DRM?

When in a hierarchy, a user right clicks on a node to crate a new node, he has two options
-Child
-Sibling
Is it possible to restrict the user from creating a sibling and allow him to ONLY create child nodes?
Business cases:
1. different level nodes need to have different prefixes.
- Thus, the default prefix property definition uses the level number to assign a prefix
- Also, a validation, to ensure the correct prefix, uses the level number
But if the user can create a child and a sibling then the default prefix will only be right for a single case and not both.
Thanks

If the images are exactly the same size then make sure the layer with the mask
is the active layer and in the other documents go to Select>Load Selection and choose
your document with the layer mask under Source document and under channel choose the layer mask.
After the selection loads press the layer mask icon at the bottom of the layers panel.
MTSTUNER

How to restrict the user to enter only numeric values in a input field

How to restrict the user to enter only numeric values in a input field.
For example,
i have an input field in that i would like to enter
only numeric values. no special characters,alphabets .
reply ASAP

Hi Venuthurupalli,
As valery has said once you select the value to be of type integer,once you perform an action it will be validated and error message that non numeric characters are there will be shown. If you want to set additional constraints like max value, min value etc you can use simple types for it.
On the project structure on left hand side under local dictionary ->datatypes->simple types create a simple type of type integer
The attribute which you are binding to value property ;make its type as simple type which you made
Hope this helps you
Regards
Rohit

How will I block/restrict the user to change the payment term in FBL5N?

Hi All,
How will I block/restrict the user to change the payment term in FBL5N????
I have tried on following objects:
F_BKPF_BLA
F_BKPF_BUK
F_BKPF_GSB
F_BKPF_KOA
F_IT_ALV
F_KNA1_BED
F_KNA1_BUK
F_LFA1_BUK
S_ALV_LAYO
But, not succeeded.
=>Actually user runs FBL5N, double click on a record then click on Change icon.
=>Change Payment Term.
Please reply ASAP. Point will be awarded.
With Best Regards
Dharmendra

Hi Dharmendra,
Please set an authorization trace in ST01 and then ask the user to execute the transaction and the steps on the same application server as the o ne on which the trace has been set (valid in case we are talking about mutiple application servers for same <SID>). After this is done switch off the trace,list it and fill all the authorization objects. That might give you the perfect idea.
Regards.
Ruchit.

Restrict the user to edit Activity

Hi guys
What will be the validation for the below scenarion
1) To restrict the user to edit any activity a " 5 Days after the close of the month". for eg is a activity is created on 13/02/2011 , it can be edited till 05/03/2011
Waiting for the solutions

Another approach will be to use a pair of dynamic pages. Dynamic Pages for Task are base on "Type".
So if you have Types like ToDo, CallBack, Research create 3 more as ToDo-RO, CallBack-RO, Research-RO
Make copies of the Task Pages that you use for ToDo, CallBack, Research and make all the field as Read Only.
So "Cust ToDo Task Page" is copies as "Cust ToDo Task Page - RO" and so on
All fields in the - RO pages are Read Only.
Create a Dynamic Page and assign the correct pages to the Type Values
Type "ToDo" has the "Cust ToDo Task Page"
Type "ToDo-RO" has the "Cust ToDo Task Page - RO"
and so on
Create an field "RecordRO" with Field Type "Checkbox" called Default Value as "N". Have a workflow set this field as "Y" on appropriate event or time tigger.
In your case one workflow will be Time triggered to set this to Y on 5th of Month post the creation. So simply export on 4th or 5th night all Records that have the filed as N and reimport the Field as Y. Else use a WebService.
Have one more workflow (Workflow Expression could be like FieldValue('<bRecordRO_ITAG>') = "Y") to set Type as PreValue of Type +"-RO"; Update Expression will be PRE('<Type>') + "-RO" with Overwrite Existing Values as TRUE
Let me know if this works for you.
How much we miss the On Premise State Models :-(.

TMG related logic - restricting the user entry fields

I have created table and table maintenance generator using below fields
MANDT                     MANDT
WERKS                     WERKS_D
MTART                     MTART
MATKL                     MATKL
CREATED_BY     SYUNAME
CHANGED_BY     SYUNAME
I have to restrict the user with out entering wild card (*) in the mtart and matkl fields.
In TMG, in screens how to build the logic ?
THANKS.

Hi ,
I am not sure if I understand your requirements fully.
Anyway , you can add a validation in TMG events and output a message accordingly when the user enters *.
Regards,
Deepthi

How to Restrict the users from changing the Default variant of report.

Hello everybody,
The requirement is to restrict the users to save and overwrite the default layout variant (Layout for higher managenet)set for the report, but at the same time they should be able to change and save the other layouts for which they are having access.
I have written the logic in the program which is working fine for all the scenario when we execute the report. But the logic doesnt work if the user is selecting the layout on the output screen of the report.
for e.g if the user runs the report using the layout varaint for which he is having the authorization then he gets the all 4 options so he then he can select the layout for which he is not authorized and he can overwrite.
i have debugged and check as i have found that after the report output is shown all the layout paramater is controllled by the statndard SAP objects.
Can anyone help me out in this issue.
Thankyou in advance.
*to get the default layout variant.
w_save = 'A'.
if p_vari is initial.
    clear disvariant.
    disvariant-report = sy-repid.
    w_variant = disvariant.
    call function 'REUSE_ALV_VARIANT_DEFAULT_GET'
      exporting
        i_save     = w_save
      changing
        cs_variant = w_variant
      exceptions
        not_found = 2.
    if sy-subrc = 0.
      p_vari = w_variant-variant.
    endif.
endif.
*logic to check user authorization to change the layout setting.
if p_vari = c_layout.
    if not sy-uname is initial.
      select single * from agr_users
              where agr_name = c_role
              and   uname    = sy-uname.
      if sy-subrc = 0.
        w_save = 'A'.
      else.
        w_save = ' '.
      endif.
    endif.
endif.
Regards,
Satish.

Hi Maine,
Thanks for your reply.
As you mentioned for your own program, you can control the parameter "I_SAVE", when calling "REUSE_ALV_GRID_DISPLAY".
so already i have use the same logic and control the parameter through I_SAVE and here i am calling method ALV_GRID->SET_TABLE_FOR_FIRST_DISPLAY instead of "REUSE_ALV_GRID_DISPLAY".
and it works fine when we execute the report but the logic doesnt work when the user tries to change and save the layout variant on the output screen of the report.
Regards,
Satish

How do i Restrict the users up to the self service pag only in IDM 11g

Hi all,
can any one please help me out to restrict the users to self service page only in 11g.
thanks for your time and support
Regards
Siva

Your user will have the Administration page if they have an Authorization Policy configured to allow the user any of the User Management or Role Management Functions. Also, if you login as a user that has those tabs, and logout while on the Administration tab, sometimes i've noticed the new user logging in with the same browser session will be in the Administration tab but with no items available.
-Kevin

How to Restrict the users in oracle applications

Hi,
I want to Restrict the users in oracle applications without using database
can any one please expalin me how to resttrict the users using middletier
Thanks
Gita

HI srini ,
my application version 12.0.4 and database is 10.2.0.4
and i want to restrict the No of users
exp i have have 500 users and i want restrict to 100 only
how can i do that please explain
Thanks,
Sudheer

How to restrict the users not to change receiving batch no. in 305 mov.type

Dear MM Guru,
We are using mov.type 303 & 305 for transferring the materials from one plant to another plant. t.code is MB1B (Non split valued item)
While receive the goods through 305 mov.type the user having the chance to change the receiving batch number. To control this changes, is there a way where we can restrict the users not to do the changes in receiving batch no. or can we do the GR with reference to the material document 303 mov.type.
Regards,
Sivanandan

Hi,
Generally there is a possibility to change the batch no. If you want to restrict it means go for enhancement. Use BADI to acheive this.In MB_MIGO_BADI you can set not to change the batch no. Hope it works. Thanking you.

How to restrict the user in MIRO for not modifying price

Hi All
My requirement is How to restrict the users in MIRO screen for not modifying Material Prices of only the for specific ROH types .
For example :
Valuation class             RM description
3021                             RM - A
3022                             RM - B
3024                             RM - C
when ever we procure the above Raw materials A,B and C and
the Quantity of each Raw material @ 10 units and value @ 1 INR for each unit
RM - A procured qty 10 @1 total price is INR 10
RM - B procured qty 10 @1 total price is INR 10
RM - C procured qty 10 @1 total price is INR 10
total price of PO is INR 30
when we received invoice material prices are assume it INR 1 is excess for each material.Now the invoice price for each RM has become INR 11.
in MIRO we want restrict the user to change the price from INR 10 to 11.
suggest the best possible ways to restrict in MIRO screen
Thanks & Regards
Mala

Dear:
                  Take help of ABABPER fo implement exit using INVOICE_UPDATE or MRMH0003 Logistics Invoice Verification: Revaluation/RAP exit. If this does not help then seek help of MM functional who will help you to find exit for the required task.
rEGARDS

Restrict the user   based on document type on migo transaction-prepare GRN

Hi,
We are running ECC6.0 R/3 system.We had a requirement as follows
In MIGO transaction , we want to restrict the user on document type i.e. we want that a particular user can prepare GRN for document type STO only. He cannot prepare GRN for other document type.
We checked SU24->maintain check indicators for transaction codes->enter migo->execute->check indicator.This returned us the authorisation objects present in Migo transaction.We checked the help of all these objects,but none of them we found suitable for above mentioned requirement.We were planning to find out the proper authorisation object to add to Profile generater.
The following is the objects which we have checked for.
A_B_ANLKL-->     Asset Postings: Company Code/Asset Class
A_B_BWART-->     Asset Postings: Asset Class/Transaction Type
B_USERSTAT-->     Status Management: Set/Delete User Status
B_USERST_T-->     Status Management: Set/Delete User Status using Process
C_AFKO_AWK-->     CIM: Plant for order type of order
C_CACL_DSG-->     Interface Design
C_DRAW_BGR-->     Authorization for authorization groups
C_DRAW_DOK-->     Authorization for document access
C_DRAW_TCD-->     Authorization for document activities
C_DRAW_TCS-->     Status-Dependent Authorizations for Documents
C_KLAH_BKP-->     Authorization for Class Maintenance
C_STUE_BER-->     CS BOM Authorizations
C_STUE_WRK-->     CS BOM Plant (Plant Assignments)
C_TCLA_BKA-->     Authorization for Class Types
C_TCLS_BER-->     Authorization for Org. Areas in Classification System
C_TCLS_MNT-->     Authorization for Characteristics of Org. Area
F_BKPF_BUK-->     Accounting Document: Authorization for Company Codes
F_BKPF_BUP-->     Accounting Document: Authorization for Posting Periods
F_BKPF_KOA-->     Accounting Document: Authorization for Account Types
F_FICA_FOG-->     Funds Management: authorization group of fund
F_FICA_FSG-->     Funds Management: authorization group for the funds center
F_FICB_FKR-->     Cash Budget Management/Funds Management FM Area
F_KNA1_APP-->     Customer: Application Authorization
F_LFA1_APP-->     Vendor: Application Authorization
F_SKA1_BUK-->     G/L Account: Authorization for Company Codes
G_GLTP -->       Spec. Purpose Ledger Database (Ledger, Record Type,
                               Version)
J_1IDEP_SL-->     Authorization object for depot sale transaction
J_1IEXC_OT-->     Authorization object for Other Excise Invoice Create
J_1IEX_PST-->     Autorization object for posting Other Excise invoice
J_1IGRPT1-->     Auth. for PART1 at GR
J_1IINEX -->            Incoming Excise Invoice
J_1IRG23D-->     Authorisation object for Depo Transactions
K_CCA-->                     CO-CCA: Gen. Authorization Object for Cost Center
                                Accounting
K_CSKS     -->                CO-CCA: Cost Center Master
K_CSKS_SET-->     CO-CCA: Cost Center Groups
K_PCA-->                    EC-PCA: Responsibility Area, Profit Center
L_TCODE-->                    Transaction Codes in the Warehouse Management System
M_ANFR_BSA-->     Document Type in RFQ
M_ANFR_EKG-->     Purchasing Group in RFQ
M_ANFR_EKO-->     Purchasing Organization in RFQ
M_ANFR_WRK-->     Plant in RFQ
M_BEST_BSA-->     Document Type in Purchase Order
M_BEST_EKG-->     Purchasing Group in Purchase Order
M_BEST_EKO-->     Purchasing Organization in Purchase Order
M_BEST_WRK-->     Plant in Purchase Order
M_MATE_CHG-->     Material Master: Batches/Trading Units
M_MATE_STA-->     Material Master: Maintenance Statuses
M_MATE_WRK-->     Material Master: Plants
M_MRES_BWA-->     Reservations: Movement Type
M_MRES_WWA-->     Reservations: Plant
M_MSEG_BMB     -->Material Documents: Movement Type
M_MSEG_BWA-->     Goods Movements: Movement Type
M_MSEG_BWE-->     Goods Receipt for Purchase Order: Movement Type
M_MSEG_BWF-->     Goods Receipt for Production Order: Movement Type
M_MSEG_LGO-->     Goods Movements: Storage Location
M_MSEG_WMB-->     Material Documents: Plant
M_MSEG_WWA-->     Goods Movements: Plant
M_MSEG_WWE-->     Goods Receipt for Purchase Order: Plant
M_MSEG_WWF-->     Goods Receipt for Production Order: Plant
M_RAHM_BSA-->     Document Type in Outline Agreement
M_RAHM_EKG-->     Purchasing Group in Outline Agreement
M_RAHM_EKO-->     Purchasing Organization in Outline Agreement
M_RAHM_WRK-->     Plant in Outline Agreement
Q_TCODE     QM -->         Transaction Authorization
S_ADMI_FCD-->     System Authorizations
S_ALV_LAYO-->     ALV Standard Layout
S_BDS_DS-->     BC-SRV-KPR-BDS: Authorizations for Document Set
S_BTCH_ADM-->     Background Processing: Background Administrator
S_BTCH_JOB-->     Background Processing: Operations on Background Jobs
S_CTS_ADMI-->     Administration Functions in Change and Transport System
S_DATASET-->     Authorization for file access
S_DEVELOP-->     ABAP Workbench
S_DOKU_AUT-->     SE61 Documentation Maintenance Authorization
S_GUI-->                     Authorization for GUI activities
S_OC_DOC-->     SAPoffice: Authorization for an Activity with Documents
S_OC_ROLE-->     SAPoffice: Office User Attribute
S_OC_SEND-->     Authorization Object for Sending
S_PACKSTRU-->     Internal SAP Use: Package Structure
S_PRO_AUTH-->     IMG: New authorizations for projects
S_RFC-->                     Authorization Check for RFC Access
S_SCD0     -->                Change documents
S_SPO_DEV-->     Spool: Device authorizations
S_TABU_DIS-->     Table Maintenance (via standard tools such as SM30)
S_TCODE     -->                Transaction Code Check at Transaction Start
S_TRANSLAT-->     Translation environment authorization object
S_TRANSPRT-->     Transport Organizer
S_WFAR_OBJ-->     ArchiveLink: Authorizations for access to documents
V_LIKP_VST-->Delivery: Authorization for Shipping Points
V_VBAK_AAT-->Sales Document: Authorization for Sales Document Types
V_VBAK_VKO-->Sales Document: Authorization for Sales Areas

Have you executed a trace while a functional user executes the transaction code for the specific parameters? (i.e. document type). The trace will then show which objects are being checked; then look at the object documentation in txn Su21 to determine if there are any ways to restrict on the particular value; in some cases, if the authorization group field is being checked, additional configuration is needed in order to implement the security (Su21 will explain in detail for the particular object).

How to restrict the user to change the project structure but not the documents?

Hi,
I have created one project assigning different users in Solution manger. I want to risitrict some of the users to change the project structure but simultaneously allwoing the project documents to be created, edited or deleted using solar01 under Project documentation tab. For that I have followed the steps provided in the follwoing link.
http://wiki.scn.sap.com/wiki/display/SM/Howto+Restrict+Changes+to+Project+Nodes+to+Assigned+Team+Members
I am able to restrict the users to change the project structure, but I am not able to allow access to the project documents. It gives me the message "You are not authorised to change the project". This fulfills my one of the requirements. But, Is there any way to restrict the user to change the project structure but not the documents?. Any help will be apperitiated.
Thanks,
Rutvik Uapdhyay.

Hi Rutvik,
Basically there are 2 different authorization role ...you should look for and customize as per requirement in Z* namespace.
role - SAP_SOLAR01_ALL
this take care of objects in Solar01 like tab access etc
role -SAP_SOL_KW_ALL
this takes care of entire documentation within solman
hope this helps
Regards
Prakhar

Validation to restrict the user at parking level

Similar Messages

Maybe you are looking for