Credit Term

[gtmsb]

I have maintained my credit term in my supplier/ customer maintenance. Any idea how should i restrict them from letting user from entering the credit limit?

 

[Max Viskov]

Hi!
In most versions Credit Limit field (cm_mstr.cm_cr_limit) is password protected. You can use mgflpwmt.p (Field Security Maintenance) to restrict access for certain users.
Regards.
Max Viskov
Senior Consultant, Implementation Services
MFG/PRO Toronto User Group Board Member
32Soft Inc., an Official QAD Subcontractor
We Help Making the Most of your MFG/PRO Implementation!
To find more, please call 416-605-1830

 

[gtmsb]

I am using eb version, is it work? I have tried it. An error message pop out: Field security is not available. Please reenter.

 

[gtmsb]

I am not saying on the credit limit, what i want is credit term

 

[sharkdim]

I am not saying on the credit limit, what i want is credit term

i think it can be done for your needing , and you can get Dictionary Field Security Report in QAD mfg/pro36.3.6
Maybe, it can give you help.

 

[Max Viskov]

According to my knowledge, eB has this field enabled for security. But if not, there is solution in QAD knowledgebase - No. 11.0.888845.1334213. You can follow the instructions and hopefully it will help. Good luck!
Best regards

____________________________________
Max Viskov
Senior Consultant, Implementation Services
MFG/PRO Toronto User Group Board Member
32Soft Inc., an Official QAD Subcontractor
We Help Making the Most of your MFG/PRO Implementation!
To find more, please call 416-605-1830[FONT=&quot][/FONT]

 

[gtmsb]

I am not able to access QAD knowledgebase. Perhaps you can tell me which field i can block the user from changing the credit term. Thankx.

 

[W.Wulmsen]

When you want to add field security you add in the data dictionary two additional lines:

In the FIELD VALIDATION:
{gppswd.v &field = "cm_cr_terms"}

In the FIELD VALIDATION MESSAGE:
ERROR: USER DOES NOT HAVE ACCESS TO THIS FIELD. Please re-enter.


You have now another challange. The customer credit terms already contains another validation:
can-find(ct_mstr where ct_code = cm_cr_terms) or cm_cr_te = ""

cm_cr_te is no TYPING ERROR. It is the shortest unique name for this field!!


You have to add the the password validation as the FIRST validation.

Example.
{gppswd.v &field = "cm_cr_terms"} AND (can-find(ct_mstr where ct_code = cm_cr_terms) or cm_cr_te = "")

For the FIELD VALIDATION MESSAGE:
ERROR: CREDIT TERMS CODE MUST EXIST OR BE BLANK. Please re-enter.
Write some new poetry to help you users.

NEXT STEP:
compile adcsmtb.p. Only then will the field security be activated.

LAST STEP:
Fill the field security in the security menu.

______________________
Request
Lookup the value "gppswd.v" in mfgempty.df and check other existing field checks
______________________

Alternative
For each other field in the future use program mgfldcmt.p. This program first step is to check if the field validation is emtpy or if gpcodsec.v (Generalised Code check) is available. If not it follows the next steps:
- unFreezes the table
- Add the validation and error message
- Freezes the table


William W.

 

[gtmsb]

Thank you William