Parameter Profile
A parameter profile is a named set of field settings handed to a group of users. One profile gives the payroll officers their defaults, another gives the factory time keepers theirs, and when you change the profile every user holding it gets the change.
What it is for
Organizational Structure sets how a field behaves for a whole company. This screen does the same thing for a group of people inside it.
The case it answers is the one every client has. The time keeper at the Faisalabad plant only ever enters attendance for his own plant, so his screens should open with that plant already filled in, and he should not be able to change it. The time keeper at Lahore needs the same thing with a different answer. Two profiles, one line each, and neither of them has to remember.
A profile is a list of lines. Each line names a company, a screen, a field, and what that field should do for the people holding this profile: start with this value, be compulsory, or be greyed out.
When you save the profile, everybody who holds it has their personal field defaults rewritten from it at once. Their old lines from this profile are dropped and the new ones put in. That is the point of a profile - you change it in one place and it reaches everybody.
The profile is given to a user on their own user setup. Creating it here does not hand it to anybody.
Every field, in plain words
Header
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Parameter Profile | The short code. | TK-FSD | Required. |
| Name | Who or what the profile is for. | Time Keeper - Faisalabad Plant | Required. Name it after the group of people, not after the fields, or nobody will know which one to hand out. |
Basic Data
One line per field you want set. The grid cannot be left empty, the screen refuses a profile with no lines.
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Line # | The line number. | Fills itself | |
| Legal Entity | The company the line applies in. | 01 | Required. |
| Process Code | Which screen the field is on. | Employee Attendance | Required. Pick it from the list of screens. |
| Object No | Which field on that screen. | Business Unit | Required. Pick it from the list of fields on the screen you chose. |
| Field Value | What the field starts with for these users. | 02 | Leave blank if you only want to make the field compulsory or read-only. |
| Mandatory | These users cannot save the record with this field empty. | Leave clear | |
| Disable | The field is shown but these users cannot change it. | Ticked | Use it with a Field Value to pin an answer. |
The same company, screen and field may appear only once in a profile. A repeat is refused and the screen names both lines.
How to configure it
- Decide which groups of users genuinely work differently. One profile per group, not one per person.
- Open Parameter Profile and enter the code and name, for example
TK-FSDandTime Keeper - Faisalabad Plant. - Add a line for each field: Legal Entity
01, Process CodeEmployee Attendance, Object NoBusiness Unit, Field Value02, Disable ticked. - Add the other lines the group needs. Keep it to the fields that really are always the same for them.
- Save. Everybody already holding this profile gets the new settings immediately.
- Hand the profile to the users who need it on their own user setup. Until that is done it affects nobody.
Scenarios
Each plant's time keeper should only ever see his own plant
One profile per plant. Each has a line pinning the business unit field to that plant with Disable ticked. The screens open correct and cannot be changed.
The payroll team always works in one company
A profile with a line on each payroll screen pinning the legal entity. It saves a selection on every screen they open and removes a whole class of mistake.
We changed the profile and nothing happened for one user
They do not hold the profile. The profile is given to a user on their own setup, and creating or editing it here only reaches the people who already have it.
One person needs a different default from the rest of their group
Set it on that person's own field defaults rather than building a profile for one user. A profile exists to be shared.
What it is connected to
- Legal Entity must exist, and every line names one.
- Organizational Structure does the same job for a whole company rather than a group of users.
- Saving a profile rewrites the personal field defaults of every user holding it.
- The profile reaches people only through their own user setup.
If something looks wrong
- "It will not save, it says the basic data lines cannot be empty" - a profile needs at least one line.
- "It will not save, it says a line is duplicated with another line" - the same company, screen and field appear twice. The screen names both lines.
- "A user's screen is not picking up the default" - they do not hold the profile, or the line names a different company from the one they are working in.
- "A field is pinned and the user now cannot do their job" - Disable is ticked on that line. Clear it and leave the Field Value, so the answer is suggested but can be changed.