Datacontrol with MFL
The data control functionality in GCON4 MFL has changed:
To maintain the data control configuration, whether it comes from a Modeler structure or a traditional data control setup,
it is requiered to set a system setup value indicating the MenuID where data control is applied.*
Parameter definition
Parameter Name: MFL_DC_MENUID
Location: System Setup Values window, filtering by System Code = 'EN'.
Storage Table: aagsysvalues (filtering by sys_setup_code = 'EN').
Structure:
Text 1: Internal name of the Master File (name of the XML file associated with the MF in MFL).
Text 2: Valid MenuID value
Parameter validation
- MenuID Validation:
The value of Text 2 must be a valid MenuID, verified using the following query:
SELECT * FROM asysmenu WHERE menu_id = '$menuid' AND tree_type = 2;
If the MenuID is not valid, the process will display an error message and stop.
Log information: Example MenuID AT119 does not exist:
- Parameter Behavior:
Default Behavior: If data control is active in ERP for a Masterfile and it does not have a value configured in System Setup Values, MFL will not perform the expected data control validations according to the data control setup in ERP.
Behavior with Defined Values: If a Master File has a value configured in System Setup Values, Data Control will be applied using the MenuID specified in Text 2.
Data control applied via Modeler
Example:
Structure setup
Data control Management
Since the validation is applied over the Work Order masterfile, the following parameter must be entered in the System Setup values window:
Users with the correspondant access will see the following message in the MFL report:
Users without the correspondant access will see the following message in the MFL report:
Note the parameter is shown indicating the menu id where it was applied.
Important
If data control comes from a structure setup configuration, you must create the MFL_DC_MENUID parameter for all menu entries where the attributes subject to data control are used. Following the same example, the work orders are used in the GL analysis of Assets. In order to prevent incorrect data control validation against the Assets masterfile, it is required to set the system setup value for both Workorders and Assets, as shown below:
The same case will apply if we work with projects, since some of them my contain work orders, then the system setup value must affect the Projects masterfile as well.
Traditional data control setup based on roles:
For this kind of setup is is only required to set the system parameter for the specific masterfile where data control is applied.
Example: We have the following alternatives of data control configuration applied on Projects.
For these examples, the system setup value must be set to projects.
| name | position | text | Number | Text 2 | Number 2 | Text 3 | Number 3 | Description |
|---|---|---|---|---|---|---|---|---|
| MFL_DC_MENUID | 0 | Project | TS291 |
Below you will find the list of masterfiles with their corresponding MenuID. Please ensure that the masterfile name is entered correctly.
| Masterfile | MenuID |
|---|---|
| Account | GL376 |
| Applicant | HS372 |
| Asset | AT111 |
| Attribute | CR403 |
| Balance | HS397 |
| BalanceValueReference | PS477 |
| Course | TA379 |
| CourseEvent | TA381 |
| Customer | AR531 |
| CustomerGroup | AR542 |
| CustomerFactor | AR553 |
| ExchangeRate | AG727 |
| PayScale | PR663 |
| PaymentAndDeduction | PR676 |
| PaymentDispatch | PR542 |
| Personnel | PS356 |
| PersonnelCostDistribution | PR550 |
| PersonnelEmployment | PS356 |
| PersonnelRate | HS412 |
| Position | PS350 |
| PositionCode | PS455 |
| Product | ST201 |
| Project | TS291 |
| PurchaseOrderAmendment | PO285 |
| Rate | PS378 |
| RateValueReference | PS477 |
| Requisition | PO282 |
| Role | AG784 |
| Supplier | AP484 |
| SupplierGroup | AP492 |
| SupplierFactor | AP496 |
| TrainingNeed | TA366 |
| User | AG746 |
| WorkOrder | TS498 |
| WorkSchedule | PS403 |
Important Note: The skip_dc parameter is no longer in use and it was removed from the Settings. This paramenter is not available as a MFL04 variant parameter either.