on 09-15-2011 10:26 AM
Hi Experts,
Is there any way to Restrict the End user from Creating StandAlone A/P Invoice,GRPO.
Thanks
Kamal
Hi Kamal.....
Yes it is possible. But through SP Transaction Notification....
For Standalone GRN:
If @object_type='20' and @transaction_type='A'
BEGIN
If Exists (Select * from [dbo].[OPDN] T0 Inner Join PDN1 T1 On T0.DocEntry=T1.DocEntry
Where T0.DocEntry = @list_of_cols_val_tab_del and T1.BaseEntry is null)
BEGIN
Select @error = -1,
@error_message = 'Please Raise PO First'
End
End
For Standalone AP Invoice:
If @object_type='18' and @transaction_type='A'
BEGIN
If Exists (Select * from [dbo].[OPCH] T0 Inner Join PCH1 T1 On T0.DocEntry=T1.DocEntry
Where T0.DocEntry = @list_of_cols_val_tab_del and T1.BaseEntry is null)
BEGIN
Select @error = -1,
@error_message = 'Please Raise GRN First'
End
End
Regards,
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Kamal. . .
Yes, you can do it through SP Transaction Notification... As Rahul Suggested. .
But if you like to do it in simple way means. Follow the below steps. . .
1) In Form Settings mention Item No and Item Description as "Visible" and un check the active for both Item No and Item Desc. ...
Do it for both GRPO and for A/P Invoice etc., based on your requirements. .
2) Restrict the user as NO authorization in Form Settings... .
Even you can do it by User wise and when even the client dont need the above functionality you can just check the Item no and Item Desc as Active. . .
Hope it helps you
Regards,
Anish A
Edited by: Anishsamvel A on Sep 16, 2011 8:20 AM
Hi Deepak,
Anish's suggestion could be applicable and quite a good workaround.
If you disable / set read-only status for item code column in row level of document, therefore you couldn't add a GR-PO / A/P Invoice without copying the items in row levels from PO document, because that's the only way to add the document, by copy from base document, you couldn't add new item since the column is read-only. But you have to make sure the form setting authorization is not granted, otherwise this workaround is completely futile since user him/herself can alter the column setting.
Best Regards,
Hendry Wijaya
User | Count |
---|---|
91 | |
7 | |
7 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.