|
|
|
|
|
|
This screen is used to maintain company definitions. All entities and mappings defined for a particular company depend on the QED-specific control information entered here. The company must have been previously set up in e5, using the screen Company - Edit, MAAF. Entities, mappings, fields presentations and so on, can not be set up for a company until this screen has been used to enter the necessary QED control information.
This screen is available with three different actions: Amend, Insert, and Copy. The Copy and Amend actions both display the current Company Controls field contents, ready for editing; the Insert action displays a screen with all fields empty.
When Inserting, you enter completely new information into all the fields. The Update action then creates a new set of QED Company Controls under the Company ID you specify. (You cannot Insert a new set of Company Controls with the same Company ID as an existing set of Company Controls.)
When Copying or Amending, then the existing information for the chosen Company is displayed. When Amending, all fields except the Company ID are available for editing; when Copying, then the Company ID is also unprotected so that you can specify a new Company to which the displayed Controls are to be copied.
When Copying or Inserting, the specified new Company ID must already exist - that is, it must have already been defined as an e5 Company on the screen Company - Amend, MAAF.
The screen has two formats; the second format displays the Created date, Updated information (time and date of last Update, with user ID), and the Disabled flag.
Mapping authorisation can be used for a selected company. This allows amendments to mappings to be controlled. Authorisation is selected for a company by setting the flag field Authorisation Required. Any amendments made to a mapping attached to the company must now be authorised before the mapping can be executed by the background.
A mapping is authorised on the screen Mapping - Amend, MQMX. If a mapping has its Authorised flag set, then it is executed by the background. Amending the mapping definition, or a mapping component, blanks (unsets) the Authorised flag field on the mapping, making the mapping unauthorised.
An unauthorised mapping may still be requested (submitted to the background for processing). If, however, the mapping remains unauthorised when it is about to be run, then execution of the mapping is aborted.
Mappings can be authorised by users with the appropriate functional security. The ability to authorise is a facility which can be denied on a security group. The security group can then be attached to a user definition.
A facility is defined on the screen MQMX, to allow entry to the field Authorised on that screen. If this facility is denied on a security group, then users with that group may not authorise mappings. Facilities are denied on the screen Facility Denials - Amend, MADD.
The fields Default Report Prefix, and Default Report Prefix No, are used to attach a default report name to report components defined on mappings for the current company.
The combination of the values entered in these fields, must be prefixed to a report definition , on the screen Report Definition - Amend, MANB. So, if the field Default Report Prefix contains QED, and the field Default Report Prefix No contains 132, then a report definition with the identifier QED132 is used. When a mapping report component is created, the default report name is QED132.
A number of report definitions with the selected prefix should be defined. The system then attaches the next available report name, defined with the required report prefix, to a report component.
Three report definitions may be defined with these identifiers:
If a report component is created, the default report name is QED132. If a second report is created, the system recognises that a component using the identifier QED132 exists for the current mapping. The next default report name is therefore QED132A. If a third component is created, the default report name is QED132B; and so on.
If a report definition has not been defined with the default report prefix, then there is no default report name.
This is a key field which contains a company identifier. The QED control information on this screen is for the company identified in this field. The associated description from MAAF is displayed alongside the company identifier.
This is a flag field which may be set, or it may be blank. If the flag is set, then mapping authorisation is in use for the current company. Any amendments to a mapping defined on the current company, must be authorised before the mapping can be executed by the background.
If the field is blank, then this denotes that the mapping can be amended and executed without prior authorisation.
A mapping is authorised using Mapping - Amend, MQMX.
This is a mandatory field for MVS but is not required for Unix or Windows NT. It must contain the identifier of a device. It is to this device that mapping compilations for a company are stored. The mapping compilation is the COBOL program which is generated by the system when a mapping is compiled.
The device nominates a file on a disk or tape, somewhere on the system.
The device must be defined on Device - Edit, MANT. The associated description is displayed alongside the device identifier.
This field is for future enhancements. It will be used to allow updates to database tables for mappings defined on the current company.
This is a mandatory field which contains the identifier of a currently defined user. This user should be notified when difficulties arise during the processing of a mapping for this company.
The user must have been previously defined on User - Edit, MAFD.
These are system-specific fields which may not be in use at your site. These should be set up at installation for you.
This is a mandatory field which must contain a three character code. The field is used in conjunction with the field Default Report Prefix No. The combination of the values entered in these fields is used as a default report name when a report component is created for a mapping. The report name must also be defined on the screen Report Definition - Amend, MANB.
This is a mandatory field which must contain a three digit, numeric value. This field is used in conjunction with the field Default Report Prefix. The combination of values entered in these fields, can be defined as a report definition, on the screen Report Definition - Amend, MANB. This report definition is used as the default report for report components defined on mappings for the current company.
Action |
Description |
List Entities |
This action can be used on a selected company. It transfers you to the screen Entity - List, MQEA. This screen builds a list of the entities which have been defined for the selected company. From MQEA you can reach the screen Related Entities - List, MQEG, to display the relationships between entities diagrammatically. Entities are defined on the screen Entity - Edit, MQEB. |
List Functions |
This action can be used on a selected company. It transfers you to the screen Function - List, MQFA. This screen builds a list of the functions which have been defined for the selected company. Functions are defined on the screen Function - Edit, MQFB. |
List Mappings |
This action can be used on a selected company. It transfers you to the screen Mapping - List, MQMA. This screen builds a list of the mapping which have been defined for the selected company. Mappings are defined on the screen Mapping - Edit, MQMX. |
List Presentations |
This action can be used on a selected company. It transfers you to the screen Field Presentation - List, MQPA. This screen builds a list of the field presentations which have been defined for the selected company. Field presentations are defined on the screen Field Presentation - Edit, MQPB. |
If not described in this topic, click on a field and press F1 to view help. See Common Fields for more information.
Fast prompt allows you to quickly view a list of options for certain fields.
See Using the Command Line on opening the screen without going through the menu.
See also
|
© Advanced, Jan 2021 |
|
