Ellipse Administration Guide

—
Ellipse Administration
Ellipse EAM 9.0

© Copyright 2018 ABB
All Rights Reserved
Confidential and Proprietary
Published: Tuesday, 2 October 2018
Legal Disclaimer
The product described in this documentation may be connected to, and/or communicate
information and data via, a network interface, which should be connected to a secure network. It is
your sole responsibility to ensure a secure connection to the network and to establish and maintain
appropriate measures (such as but not limited to the installation of firewalls, application of
authentication measures, encryption of data, installation of antivirus programs, etc.) to protect the
product, the network, your systems, and the interface against any kind of security breach,
unauthorised access, interference, intrusion, leakage, damage, or corruption or theft of data. We
are not liable for damages or losses related to any such security breach, unauthorised access,
interference, intrusion, leakage, damage, or corruption or theft of data.
Contents
Contents
Administration .........................................................................................................8
Batch Administration ............................................................................................. 9
Start or Stop the Batch Subsystem ..................................................................... 10
Add User Queues ........................................................................................... 11
Review Default Queues ................................................................................... 12
Override Scheduled Cyclic Request Time ............................................................. 13
View Batch Log File ....................................................................................... 14
View Batch File............................................................................................. 15
Create Custom Batch File ................................................................................ 16
Upload Custom Batch File ................................................................................ 17
Delete Custom Batch File ................................................................................ 18
Reporting Administration (E9.0) ............................................................................. 19
Group Report Requests ................................................................................... 21
Create Program or Report Configuration .............................................................. 24
Modify Program or Report Configuration .............................................................. 25
Delete Program or Report Configuration .............................................................. 26
Upload Report .............................................................................................. 27
Delete Report Upload File................................................................................ 28
Request Cyclic Reports ................................................................................... 29
Request Ad Hoc Reports .................................................................................. 31
Initiate Program or Report Requests using the Search and Detail Screen ....................... 33
Defer Report Request using the Search Screen ....................................................... 34
Modify Report Requests................................................................................... 35
Delete Program or Report Requests .................................................................... 36
View Program or Report Request Log .................................................................. 37
Review Cyclical Request .................................................................................. 38
Modify Cyclical Details .................................................................................... 39
Delete Cyclical Request .................................................................................. 40
Review Reports Online .................................................................................... 41
Send Report to an Employee ............................................................................. 42
Delete an Online Report Record ........................................................................ 43
Display Reports with Logs Files .......................................................................... 44
Reporting - Reports ........................................................................................ 45
Month-End Procedures ......................................................................................... 48
External Systems Interface to Ellipse ....................................................................... 49
General Housekeeping ......................................................................................... 54
Convert Request Banners - MSH080A ................................................................... 55
Convert Standard Text (Compression) - MSH096A ................................................... 56
Convert Standard Text (Relational) - MSH095A ...................................................... 57
Rebuild MSFX99 records for Work Orders - MSHX9AA ................................................ 58
Update MSFX99 record with Project No. - MSHX99A................................................. 59
Audit Rules, Restrictions and Overrides .................................................................... 60
Create Audit Rule .......................................................................................... 62
Review Audit Rule ......................................................................................... 63
Update Audit Rule ......................................................................................... 64
Delete Audit Rule .......................................................................................... 65
Review Audit Data ......................................................................................... 66
Update Audit Rule Reason Code or Comment ........................................................ 67
Create Audit Restriction Override ...................................................................... 68
Review Audit Restriction Override ...................................................................... 69
Update Audit Restriction Override ..................................................................... 70
Delete Audit Restriction Override ...................................................................... 71
5
Contents
Bulk Request Creation - MSH083A ........................................................................... 72

Work File Procedures .......................................................................................... 73
Administration - Reports ...................................................................................... 74
MSB042 - Notification & Diary Deletion ................................................................ 77
MSB043 - Notification & Diary Reminder .............................................................. 78
MSB044 - Notification & Diary Escalation .............................................................. 79
MSB04A - Diary and Notification Report ............................................................... 80
MSB070 - Bulk Changes.................................................................................... 81
MSB07A - Transfer Selection ............................................................................. 84
MSB07B - Process Transfer ............................................................................... 85
MSB07C - Reduce Dues-In District/Warehouse ........................................................ 87
MSB07D - Close a District ................................................................................. 88
MSB07E - Check for Closure .............................................................................. 89
MSB07F - Bulk Requisition Cancel ....................................................................... 92
MSB07G - Delete a Transfer List ........................................................................ 93
MSB07H - Close Warehouse .............................................................................. 94
MSR07Z - Transfer Errors ................................................................................. 95
MSB17V - Valuation Accounting Report ................................................................ 96
MSB19H - Delete Bin Locations .......................................................................... 97
MSBTNE - Maximum Transfer Number Exceeded ..................................................... 98
MSB877 - Archive Authorisations ........................................................................ 99
MSB907 - Archive/Roll Back Transactions ............................................................ 100
MSR038 - Errored/Junked Incoming Messages Report .............................................. 101
MSR040 - Diary Report ................................................................................... 102
MSR041 - Diary Follow-Up Report ...................................................................... 104
MSR042 - Employee Diary Report ...................................................................... 105
MSR079 - Check for District/Warehouse Closure, Goods Holding ................................ 106
MSR07A - Check for District/Warehouse Closure - Orders Report ................................ 107
MSR07B - Check for District/Warehouse Closure - Warehouse Requisitions Report ........... 108
MSR07C - Check for District Closure - Holdings Report ............................................ 109
MSR07D - Check for District Closure - Accounts Payable Invoices Report ...................... 110
MSR07E - Check for District Closure - Accounts Receivable Invoices Report ................... 111
MSR07F - Check for District Closure - Work Orders Report ........................................ 112
MSR07G - Check for District Closure - Equipment Report ......................................... 113
MSR07H - Check District/Warehouse Closure - Waybills Report .................................. 114
MSR07I - Check for District Closure - Batch Requests Report ..................................... 115
MSR07J - Check for District Closure - Scheduled Tasks Report ................................... 116
MSR07K - Check for District Closure - Goods in Transit Report ................................... 117
MSR07L - Check for District/Warehouse Closure - Purchase Requisitions Report ............. 118
MSR07M - Check for District Closure - Open Incidents Report .................................... 119
MSR07N - Check for District Closure - Logsheets .................................................... 120
MSR07O - Check for District Closure - Projects Report ............................................ 121
MSR07P - Check for District Closure - Accounts Report ............................................ 122
MSR07Q - Check for District Closure - Employees Report ......................................... 123
MSR07R - Check for District Closure - Labour Costing Report..................................... 124
MSR07S - Check for District Closure - Unposted Transactions Report ........................... 125
MSR07T - Check for Supply Customer Closure - Holdings Report ................................. 126
MSR07U - Check for Supply Customer Closure Requisitions Report .............................. 127
MSR07V - Check for Supply Customer Closure - In Transit ......................................... 128
MSR07W - Check for District Closure - Cyclic Requests Report ................................... 129
MSR07X - Check for District Closure - Repair Requests Report ................................... 130
MSR07Y - Check for Warehouse Closure - Holdings Report ........................................ 131
MSR081 - Batch Request Parameters Report ......................................................... 132
MSR083 - Cyclical Request Report ..................................................................... 133
MSR09A - Work File Listing .............................................................................. 134
MSBXPO - Purchase Order Print XML ................................................................... 135
6
Contents
MSBXRQ - Request for Quotation ....................................................................... 148

MSRXDRA - Discrepancy Report Letter ................................................................ 154
MSIXPO - Build PO and PS Interface ................................................................... 160
MSIXRQ - TTT .............................................................................................. 171
MSIXRA - TTT .............................................................................................. 179
MSIXSS - TTT ............................................................................................... 184
Ellipse Administration - Screens ............................................................................... 190
MSE016 - Search Device ....................................................................................... 191
MSE016 - Device detail ........................................................................................ 192
MSE081 - Search Program/Report Configuration ......................................................... 194
MSE081 - Program/Report Configuration detail ......................................................... 195
MSEAUR - Search Audit Restriction Override .............................................................. 199
MSEAUR - Update Audit Restriction Override ........................................................ 200
MSEBAT - Batch Admin ........................................................................................ 201
MSM005A - Close Accounting Period ........................................................................ 205
7
Administration
There are a number of activities that are essential to the effective administration of the Ellipse EAM
system. These activities are normally managed by a system administrator and included in their daily
routine administrative tasks.
Some of the activities include:
 Batch Administration - Contains information on the batch subsystem. This includes activities on
adding user queues, starting/stopping the batch subsystem, creating custom batch files and so
on.
 Month-end Procedures - Modules within Ellipse EAM that generate financial transactions for an
accounting period are subject to the month-end process. Information relating to month end
procedures can be found in this process.
 Audit Procedures - Auditing provides the functionality to track file modifications within Ellipse
EAM. Audit reports are provided so that copies of these changes can be made and stored for
future reference.
 General Housekeeping - Contains information relating to housekeeping programs.
8
Batch Administration
The Batch Administration process is used only by the system administrator or a high level user.
MSEBAT - Batch Admin is used to administer the Batch Subsystem. The batch subsystem is the key
function to run batch programs, which are Ellipse EAM applications that run in the background.
The batch subsystem queues batch requests and the batch programs process the requests on the
batch application servers (the batch subsystem runs on one or more application servers, providing
the opportunity to increase the volume of requests processed in a given time).
There are three applications that support administration:
MSEBAT - Batch Admin
This application can do the following:
 Define batch queues as an addition to the default queues provided.
 Provide a cyclic request schedule time that overrides the time in Batch.xml.
 View the batch job structure defined in batch.xml.
Tasks are part of the job structure (task = batchjob and job = list of tasks)
Streams are a collection of jobs.
 Open a custom_batch.xml template.
 Upload a custom_batch.xml file.
 Create streams, tasklists, and batchjobs through custom_batch.xml that extend the batch
structure.
MSE081 - Program/Report Configuration
 Create a program/report.
 Define or update the parameters that are used for execution of a batch job.
MSE016 - Devices
 Configure printers by defining where a printer is found in the network and where it can be used.
 Store printer configuration information (MSFPRT and MSFPRD).
The System Administrator supports the user by defining, configuring or managing the batch
subsystem.
The System Administrator can:
 Set up customer queues and override the cyclic request schedule time.
 Add batch structure defining the jobs, tasks, and streams.
 Configure printers and assign districts to which they will be accessible, see Maintaining Devices
for more information.
Refer to the Batch Processing Configuration and Administration Guide for more detailed
information on Batch Administration.
9
Start or Stop the Batch Subsystem

Use this activity when there is a requirement to stop and start the batch subsystem. For example,
to reload the batch.xml and/or custom_batch.xml.
Activity Steps
1. Access MSEBAT - Batch Admin.
The MSEBAT - Update Batch Admin screen displays.
2. Click Stop.
3. Select Refresh.
4. Select the Files tab.
5. Click the batch.log file.
The File Download dialog box displays.
6. Select Open.
The batch.log file displays.
Check that the batch subsystem has stopped, for example, BatchController - BEC stopped.
7. Click Start to restart the Batch Controller.
8. Select Refresh.
To check that the Batch Controller has restarted:
3. Select Open.
Check that the batch subsystem has restarted, for example, BatchController - BEC started.
10
Add User Queues

Use this activity when there is a requirement to add queues that support effective batch job
processing in the customer environment.
Activity Steps
2. Select the Queues tab.
3. Click the Add icon to add a new row to the queue grid.
4. Enter data in the following fields:
Queue Name
Pattern
Maximum Concurrent Jobs
Do Not Retail
Trim Trailing Spaces
5. Repeat steps 3 and 4 to add additional queue entries.
6. Select Submit.
The queue entries are saved.
11
Review Default Queues

Use this activity to review default queues.
Note: The queues in the Default Queues (Internal) tab are Mincom defined and provided as part of
the installation. These queues cannot be modified.
Activity Steps
2. Select the Default Queues (Internal) tab.
3. Review data as required.
12
Override Scheduled Cyclic Request Time

Use this activity when there is a requirement to change the start of the overnight process.
The overnight process consists of MSB082 processing valid cyclic requests, then overnight running
the streams that process the batch jobs held in MSF080.
Activity Steps
2. Modify data in the following field:
Cyclic Request Schedule Time
3. Select Submit.
The default time for scheduling cyclic requests is overwritten by the time entered.
13
View Batch Log File

Use this activity to view the batch log file.
Activity Steps
2. The MSEBAT - Update Batch Admin screen displays.
5. Select Open.
6. Review the batch log file as required.
14
View Batch File

Use this activity to view the batch.xml file.
Activity Steps
3. Click the batch.xml file.
4. Select Open.
The batch.xml file opens in your browser.
5. Review the batch.xml file as required.
15
Create Custom Batch File

Use this activity to create a custom batch file. A batch file can be created if there is a requirement
to add or replace the job structure contained in a batch.xml.
If you create an entry with a batch name that is the same name as that contained in batch.xml, it
will override the entry when loaded into the batch subsystem.
A custom batch file can be created from a template and must be saved and uploaded before it is
used. The newly created batch file is stored in the MSFTFS file.
Activity Steps
3. Click the Custom Batch.xml template icon below the Custom Batch File field.
4. Save the custom batch file.
5. Open the saved custom batch file.
Use an editor to add job structure details.
6. Save the custom_batch.xml into designated directory used for custom_batch.xml.
7. Access MSEBAT again
9. Click the folder icon next to the Custom Batch File field to browse for the created custom
batch.xml file.
10. Select Submit.
The created custom batch file is uploaded.
16
Upload Custom Batch File

Use this activity to upload an existing custom batch file.
Activity Steps
3. Click the folder icon next to the Custom Batch File field to browse for an existing file to
upload.
Once a file has been selected, the Custom Batch File field is populated and a file type icon
displays below the field.
4. Select Submit.
The uploaded batch file is loaded into the batch subsystem.
17
Delete Custom Batch File

Use this activity to delete/remove an uploaded custom batch file.
Activity Steps
3. Click the Delete icon next to the Custom Batch File field.
The file and icon are removed.
4. Click Submit to save the changes.
18
Reporting Administration (E9.0)

The majority of Ellipse EAM modules include a standard set of reports, most of which can be
requested on an ad hoc basis. Reports are written using either Jasper Reports (MSJs), or ABB Report
Definition Language (MSRs).
Reports and Batch Processes

A report (MSR) is a request to the database for a listing of current database values. A batch update
process (MSB), on the other hand, will write information to the database and provide a report
summarising the updates made.
Because of their complexity, some reports are also executed using batch programs. These batch
programs are identified by the letters MSB.
Note: The majority of MSB programs are batch update processes.
Initiating Reports and Batch Processes

Some reports and batch processes are initiated by system events. All other batch and report
requests are submitted using MSO080. Your level of access to MSO080 determines whether you can:
 Submit requests for immediate execution
 Nominate the printer to which the report output is sent
 Increase the number of copies printed
 Nominate the time and date of execution
 Submit requests for periodic (or cyclical) generation
Notable Features
Some of the notable features of Ellipse EAM reports are:
 Report requests can be started online, or deferred for overnight processing.
 Requests can be registered in advance of the actual processing date.
 You can nominate the date and time when the reports are processed.
 Cyclical requests can be created to automatically produce reports on a recurring basis.
 Both ad hoc and cyclical requests can be maintained online.
Output Formats
You can nominate the device to which the report will output. Options for the report output medium
are:
 Printed (hardcopy, email or fax, where available)
 Online (for reviewing with the option to print)
 Sequential file format (used for interfacing to other systems)
 Emailed (direct to external email system)
To email reports, the Electronic Mail module must be installed. To define an email device to be
used instead of a printer device, refer to Configure Email Device.
Report Requests
The request mechanisms can be tailored to vary the database commits during the running of a job
by changing the number of maximum reads and/or updates of the database for the request. Default
values can be set up on MU - Timeslot Details for Batch Programs Table File, specifying start and
end times and optionally specifying a day of the week to which they apply.
Overall default values can be set on the Systems Control file. These are used if neither report
request maximum values nor table type MU maximum values are set up.
19
If the maximum values are entered against the report request then the Table File MU values and
Systems Control file values are overridden for the duration of the run. These values are rechecked
every time the program commits.
If a customer version of a report cannot be selected by the user because the request is embedded in
Ellipse EAM software, the customer-specific report should be entered in the SR -Substitute Request
table file as an associated value of the delivered program.
Business Rules
The following business rules govern this process:
 Users with low level of access to MSE083 - Program/Report Request and MSE086 -
Program/Report Review will only be able to modify their own requests and review their own
online report output.
 Programs will not perform database commits if the maximum values (identified earlier) are set
to zero.
 Programs can be submitted to execute on a cyclic basis, as follows: Daily, Weekly, Fortnightly,
Monthly, Quarterly, Half-Yearly, Yearly, and Periodically (every xx days).
 Customers define the length of time that reports that produce online output will be retained,
before being deleted.
When you request a report, Ellipse EAM uses your default printer. You can change this when
submitting the request, and if the printer you nominate is not found, Ellipse EAM will use the
default printer for the district you are using at the time of request submission. If no district default
exists, Ellipse EAM will send the output to the default global printer.
20
Group Report Requests

You can group reports and submit them as one request with common parameters. It is used ideally
to group logical sets of reports. Once built, a group can be submitted on whatever frequency is
appropriate. YOu can also use cyclic requests with group report requests.
Overview Diagram
Limitations
Grouping report requests is not a scheduling tool.
Additional information
The following procedures need to be considered when you use the Group Report Request facility:
 Group labels are set up using Table File LABL. Using a standard set of abbreviations within an
organisation ensures consistency in the table file.
 You can create group names using MSE081 - Program/Report Configuration, in the same manner
as program names.
 Request parameters for the group require a group label to be entered for each field
(Mandatory). Request parameters for individual programs can have a group label entered
against any field (Optional). The group label allows a relationship to be created between the
group request parameter and the individual program request parameter. The net effect of this
relationship is that, at request time, the values entered for the group are overlaid into the
program where the group labels match.
 Reports are added to a group using the MSO088 - Group Report Requests program. You can
also maintain and review available groups with this program.
 Groups are submitted for execution using the MSO080 - Report Request program. The process is
similar to that of submitting a request for a program. The request method can be either
Immediate, Deferred, or Cyclical.
 If existing defaults are not already available, Report Request Selection details for the group are
overlaid into each program within the group.
 Where the group labels match, the request parameters supplied through the MSM080C - Report
Parameters screen for the group will overlay the request parameters for the individual
programs.
Example - setting up and requesting a Group Request
Using MSE081, create a group called EQUIPQ. This group has two request parameters.
 Enter Equipment Number From : 'GROUP LABEL = EQUIPFR'
 Enter Equipment Number To : 'GROUP LABEL = EQUIPTO'
Set up the group labels using MSE081.
Two programs (MSR600 - Master Register of Equipment and MSR615 - Actual/Effective Statistics
Equipment Profile) are identified to be added as members to the group EQUIPQ. These programs
both use Equipment From/To values as input parameters. Their parameter definitions are adjusted
using MSE081 to also contain reference to the group labels EQUIPFR and EQUIPTO.
21
Note: It is important to create the group label relationship before the programs are physically
added to the group using MSO088.
The programs are then added to EQUIPQ using MSO088. Request parameters are required for fields
other than the ones with a group label relationship. These are entered when the programs are
added to the group.
Program MSR600 requires a mandatory (D/S) entry for the Report Type field. The Equipment No or
Plant No range From and To fields are protected. You can enter the other fields for MSR600, as no
relationship exists with the group on these.
Program MSR615 requires a mandatory (A/E) for the Profile field. The Equipment Reference
range: From and To fields are protected.
You request the group EQUIPQ using MSO080 and the Equipment No.: From and To fields are
mandatory.
A request is created on file MSF080 for MSB084. A review of request parameters will show which
group the request is for and the parameters entered.
When MSB084 is executed, requests are written for both MSR600 and MSR615 on MSF080. The
Equipment From and To values supplied EQUIPQ have now been overlaid into the parameter
definitions for both of the programs.
22
Group Reports
Use this activity to group a number of reports so that only one request is required to run all the
reports in the group.
Activity Steps
1. Add a name for the group of reports to table file LABL.
For information on maintaining Table Files, refer to Create a Table Code in Maintaining Table
Files.
2. Access MSO088 - Maintain Group Report Requests.
The MSM088A - Maintain Group Requests screen displays.
3. Select A - Add from the Actions list.
4. Select Submit.
The MSM088B - Add Requests To A Group screen displays.
5. Enter data in the following fields for each report request to be added to the group:
Program - This field should contain the Report or Batch ID.
Report Id
Request By
Distribution Code
Notify When Complete
Medium
Printer
Copies
6. Select Submit.
The requests are saved to the group and the MSM088A - Maintain Group Requests screen
displays.
The group of reports can be requested by entering the group name rather than a Report ID when
requesting an ad-hoc report, or requesting a cyclic report.
23
Create Program or Report Configuration

Use this activity to create a program/report.
Activity Steps
1. Access MSE081 - Program/Report Configuration.
The MSE081 - Search Program/Report Configuration screen displays.
2. Select New.
The MSE081 - Program/Report Configuration detail screen displays.
Program Name
Request Type
Program ID
Request number
Title
4. Enter data in fields in the Details tab as required:
5. Select the Parameters tab.
6. Click Add to add a new row for parameter value entry.
Display Row
Description
Mandatory
8. Enter data in the remaining fields on this tab as required
9. Repeat step 6 to 8 for each additional parameter required.
10. To upload an existing file, refer to Upload Report.
11. Select Submit.
The new program/report is saved.
24
Modify Program or Report Configuration

Use this activity to modify parameters used for individual reports. This activity is usually used when
newly developed reports are being included in Ellipse EAM. Only System Administrators have write
access to this program.
Activity Steps
2. Enter data in the following field:
Program Name
3. Select Search.
The program/report matching the criteria entered displays in the results grid.
4. Select the program/report entry.
The MSE081 - Program/Report Configuration detail screen displays.
5. Modify data as required.
6. Select Submit.
The modified details are saved.
25
Delete Program or Report Configuration

Use this activity to delete an existing program/report.
Activity Steps
Program Name
3. Select Search.
The MSE081 - Program/Report Configuration detail screen displays with the program/report
details.
4. Select Delete.
A message displays prompting you to confirm the deletion.
5. Select Confirm.
The program/report is deleted.
6. Click New to create a new program/report or click New Search to return to the MSE081 -
Program/Report Configuration Search screen.
26
Upload Report
Use this activity to upload an existing file, such as an .rdl, .grvy or .jasper file.
Activity Steps
Program Name
3. Select Search.
details.
4. Select the Upload File tab.
5. Select the folder icon next to the File field to browse for an existing file.
Once a file is selected, the File field is populated and a file type icon displays below the field.
6. Select the icon to view the file.
7. Select Submit.
The file upload is saved to the program/report.
27
Delete Report Upload File

Use this activity to delete an uploaded file attached to a program/report.
Activity Steps
Program Name
3. Select Search.
details.
4. Select the Upload File tab.
The name of the file displays in the File field.
5. Click Delete next to the File field.
The file and icon are removed from the program/report.
6. Click Submit to save the changes.
28
Request Cyclic Reports

Use this activity to request a cyclical report. The output types available depend on the offerings
that are installed.
Some reports run without the need to enter parameters. When this occurs, the Parameters screen is
bypassed.
To create a cyclic report, enter a value in either theCycle Type or the Cycle Days field.
Activity Steps
1. Access MSO080 - Request Reports.
The MSM080A - Available Reports screen displays.
2. Select the check box next to the required item.
OR
Search ID
4. Enter data in the following fields to restrict the reports which display:
Search Program Type
Search Name
Method
5. Select Submit.
The MSM080B - Report Request Selection screen displays.
Request by (defaults to current user)
Distribution Code
Medium
Enter Printer
and Number of Copies
Enter Y for Additional Printers
Note: If Y is entered, the printers will be selected on the subsequent screen.
Notify when complete
Enter Defer Date
and Defer Time
Batch Submission: Enter Y to Submit Program for Batch Processing
Cyclical Request: Enter Cycle Days
Cycle Type
7. Select Submit.
If you entered Y in the Additional Printers field, the MSM084A - Select Printers screen displays.
Otherwise:
 If report parameters are required for this report, the MSM080C - Report Parameters screen
displays.
 If report parameters are not required, the MSM080B - Report Request Selection screen
displays.
8. Perform one of the following steps:
a. If you entered Y in the Additional Printers field:
1. Enter data in the Copies field next to each printer on which the report is to be printed.
29
2. Select Submit.
Depending on whether report parameters are required for this report:
Note: If you entered Y in the Notify when complete field in MSM080B, advice is displayed when
the report has been successfully executed.
Or
The MSM080C - Report Parameters screen displays.
Note: Some reports run without the need to enter parameters. When this occurs, the Report
Parameters screen is bypassed.
3. Go to step 7.
30
Request Ad Hoc Reports

Use this activity to request the ad hoc execution of a report or batch process.
Some programs do not require runtime parameters, in which case the parameter entry screen is
bypassed.
Note: You can review a list of printers using MSO085 - Review Printers for Report Requests.
Activity Steps
1. Access MSO080 - Request Reports.
The MSM080A - Available Reports screen displays.
All the reports and batch processes that you can request display. This list is security checked
before it displays.
Search ID
You can enter a program, report ID, partial program or partial report ID.
Reports/programs matching the characters entered in the Search ID field display.
3. Double-click the required item.
Request by
Distribution Code
Medium
Enter Printer
and Number of Copies
Enter Y for Additional Printers - If you enter Y in this field, you will select the printers on the
subsequent screen.
Notify when complete
Enter Defer Date
and Defer Time
Batch Submission: Enter Y to Submit Program for Batch Processing
5. Select Submit.
If:
 You entered Y in the Additional Printers field, the MSM084A - Select Printers screen
displays. Go to step 7a.
Otherwise:
 If report parameters are required for this report, the MSM080C - Report Parameters screen
displays.
 The MSM080B - Report Request Selection screen displays. If report parameters are not
required for this report the message Request was successfully written displays. This is the
end of the activity.
a. If you entered Y in the Additional Printers field:
1. Enter data in the Copies field beside each printer on which the report is to be printed.
2. Select Submit.
Depending on whether report parameters are required for this report:
31

Or
The MSM080C - Report Parameters screen displays.
b. If you left the Additional Printers field blank:
1. Go to step 8.
a. If report parameters are required for this report:
1. Enter parameters for the individual report.
2. Select Submit.
The MSM080B - Report Request Selection screen displays. The message Request was
successfully written displays.
b. If report parameters are not required for this report:
1. The MSM080B - Report Request Selection screen displays. The message Request was
successfully written displays. This is the end of the activity.
Some reports run without the need to enter parameters. When this occurs, the Report
Parameters screen is bypassed.
The fields on the MSM080C - Report Parameters screen are individual to each report. For
more information on each report and its individual parameters, refer to the Online
Help.
If you entered Y in the Notify when complete field on MSM080B, then advice is
displayed when the report has been successfully executed.
32
Initiate Program or Report Requests using the Search

and Detail Screen
Use this activity to initiate program/report requests using the search or detail screen. The search
screen allows you to initiate single or multiple program/report requests. The detail screen allows
only the initiation of a single (specified) program/report request.
Note: Only program/report requests with a process status of Deferred, Stopped or Failed or can be
initiated.
Activity Steps
1. Access MSE083 - Program/Report Requests.
The MSE083 - Search Program/Report Requests screen displays.
a. To initiate program/report requests using the search screen:
1. Enter the relevant search criteria and select Search.
Program/Report entries matching the search criteria entered display in the results grid.
2. Select the required check boxes next to the program/report.
b. To initiate program/report requests using the detail screen:
1. Select the required entry.
The MSE083 - Program/Report Request detail screen displays.
3. Select Initiate.
Processing of the program/report begins immediately.
4. Select Cancel to stop the initiation process.
Note: Only program/report requests with a process status of Initiating, Executing and Queued
can be cancelled.
33
Defer Report Request using the Search Screen

Use this activity to defer a report request for processing to another date and time using the MSE083
- Search Program/Report Requests screen.
Note: Only program/reports with a status of Initiating, Deferred, Stopped or Failed can be deferred.
Activity Steps
3. Select the required check boxes next to the program/report.
4. Click Defer.
The Dialog Box - Defer displays.
Defer Date
Defer Time
6. Select OK.
The selected program/reports are deferred to the date and time entered.
34
Modify Report Requests

Use this activity to maintain report requests after they have been submitted.
A report request only remains in the request queue until it has been executed. A report request can
not be maintained after it has been executed. The request parameters can however be reviewed
when the report is in the queue.
Activity Steps
3. Select the required Program/Report entry.
4. Modify data in the following fields:
Medium
Notify when Completed - This field identifies whether or not the originator wants to be notified
on completion of task execution.
To add a printer (if the medium type is Print):
1. Select the Printers tab.
2. Select Add.
A new row is added to the grid.
Printer
No.Copies
4. Select Submit.
To add an email address (if the medium type is Email):
1. Select the Email Destination tab.
2. Select plus.
A new row is added to the grid.
Report Destination Type
Report Destination Code
Email Address (if not the default address)
4. Select Submit.
35
Delete Program or Report Requests

Use this activity to delete program/report requests. A request can be deleted in both the search
and detail screens.
Note: Only programs/reports with a status of Initiating, Deferred, Stopped and Failed, can be
deleted.
Activity Steps
3. Select the required check boxes beside the program/report.
4. Select Delete.
A confirm deletion message displays.
5. Select Yes.
The selected program/reports are deleted.
36
View Program or Report Request Log

Use this activity to view program/report request logs. Logs are created when the request is run. Use
the MSE086 - Program/Report Review screen to view completed program/report request output
details.
Note: The Logs column only displays if the Show Logs check box is selected.
If a log is available, a document icon displays in the Logs column beside the request.
Activity Steps
3. Select the Show Logs check box.
4. Click the document icon beside the program/report request.
The File Download dialog box displays where you can Open or Save the log file.
37
Review Cyclical Request

Use this activity to review cyclic report request details which have been created using MSO080 -
Report Request.
Activity Steps
1. Access MSE082 - Report Cyclical Request.
The MSE082 - Search Report Cyclical Request screen displays.
Report entries matching the search criteria entered display in the results grid.
3. Select the required cyclical report request.
The MSE082 - Report Cyclical Request detail screen displays.
38
Modify Cyclical Details

Use this activity to modify an existing scheduled cyclical request.
Activity Steps
3. Select the required cyclical report request.
The MSE083 - Program/Report Request detail screen displays.
4. Modify data in one of the following fields:
Cycle Days
Cycle Type
Note: Only one of Cycle Days or Cycle Type can be used to indicate the length of the cycle.
5. Modify data in the following fields, if required:
Requested By
District Code
Medium
The Banner to be Displayed on Reports
Notify when Complete
Depending on the medium type modify details in either the Printers tab or Email Destinations
tab.
6. Select Submit to save details.
39
Delete Cyclical Request

Use this activity to delete a scheduled cyclical request.
Multiple cyclical requests can be deleted using the search screen. Single requests can be deleted
using the search and detail screen.
Activity Steps
a. To delete single or multiple cyclical requests using the search screen:
Cyclical entries matching the search criteria entered display in the results grid.
2. Select the required check box or boxes next to the program/report.
b. To delete a specific cyclical request using the detail screen:
1. Select the required entry in the results grid.
The MSE082 - Report Cyclical Request detail screen displays.
3. Select Delete.
A confirm delete message displays.
4. Select Confirm.
The cyclical request is deleted.
40
Review Reports Online

Use this activity to review reports online.
Note: A report must have executed fully for it to be available for online review. Any report which
has not executed successfully remains in MSE083. A report will be available for review in MSE086
until the retention date and time is reached.
Activity Steps
1. Access MSE086 - Program/Report Review.
The MSE086 - Search Program/Report Review screen displays.
3. Select the icon in the File column to download the report. If there are multiple files, select the
Folder icon to display the files, and then select the required file for download.
Note: If the File column beside the request is blank, no report is available.
41
Send Report to an Employee

Use this activity to send a report to a specified employee email inbox.
Note: The Send To button enables when a check box is selected.
Activity Steps
3. Select the relevant check boxes.
4. Click Send To.
The Dialog Box - Send To displays.
User ID
6. Select OK.
The selected report is sent to the specified employee email inbox.
42
Delete an Online Report Record

Use this activity to delete an online report record when it is no longer required.
Activity Steps
3. Select the check box next to the required report.
4. Select Delete.
A confirm deletion message displays.
5. Select OK.
The report is removed from the results grid.
43
Display Reports with Logs Files

Use this activity to view log files attached to a report.
Note: If a folder displays in the File column, the log file is contained within this folder.
Activity Steps
To view a log for a specific program name, user ID or district:
1. Enter data in one or more of the following fields:
Program Name
User ID
District Code
3. Select Search.
Report entries matching search criteria entered display in the results grid.
4. Click the icon in the File column to open the log file.
To view logs for all reports:
2. Select Search.
All reports containing log files display in the results grid.
3. Click the icon in the File column to open the log file.
44
Reporting - Reports
Reports
MSB081 - Batch Request Housekeeping Program .................................................. 46
MSB085 - Batch Report Monitoring Housekeeping ................................................. 47
45
MSB081 - Batch Request Housekeeping Program

Report MSB081A deletes requests from the batch request file.
This program cannot delete any batch request records where restart values exist.
All records on the batch request file that satisfy the program request parameter (that does not have
a restart value) are deleted, regardless of status.
The summary/details report displays:
 The request parameters
 Number of batch request file records read
 Number of batch request file records deleted
 Number of batch request file records not deleted due to restart values
 Detail listing of all batch request file records not deleted due to restart values
Additional Information
Parameters Enter the following information in the Report Request Selection screen for
this report:
Report (Y-Detailed, N- Enter Y for a detailed report or N for a summary. A summary is the
Summary) default.
This field is mandatory.
Retention Day/s Enter the retention days that determines the calculated retention date.
For example, the number of retention days is added to the date the
program is executed, to provide the calculated retention date.
Program Name Enter the program name. When the program name is entered requests
with the same name are processed, otherwise if left blank the records are
deleted.
If the batch request file does not have a restart values the defer date is
older than the calculated retention date, it is deleted.
District Code Enter the district code to process the batch request records for that
district. If left blank all requests for all districts that the user has a
profile are processed.
46
MSB085 - Batch Report Monitoring Housekeeping

Report MSB085A deletes records from the batch reporting monitoring file. A summary report is also
generated.
This program must be generated after running MSR085.
The summary report displays the following:
 total number of records read
 total number of records deleted
this report:
Retention Days Enter the number of retention days. This date calculates the retention
date as today's date.
47
Month-End Procedures
Modules within Ellipse EAM that generate financial transactions for an accounting period are subject
to the month-end process. This is either an online process using MSM005A - Close Accounting Period
or batch process using MSB005A - Month End Roll, and no month-end report is produced in general.
This process closes off an accounting period for a subsystem and opens up the next accounting
period so that financial transactions are created with this new accounting period.
Note: When month end is closed using MSM005A - Close Accounting Period, you must reset your log
on session for the new period to take effect.
It is possible to reopen a period in a financially closed year. Entry of transactions from the journal
entry screens can then be posted to these non current periods, subject to user security. Adjustment
of opening balances is automatic.
It is not necessary to close an accounting period for all subsystems at the same time. For example,
the Supply subsystem may be closed for 04/2020 and open for 05/2010 while the Fluid Management
module may still be open for 04/2020. A subsystem can be any number of periods ahead of another
subsystem.
However, if these modules are installed, the Journals and General Ledger modules must be closed
last. This means that the Journals module cannot be closed if another subsystem is still open for an
accounting period. Similarly, the General Ledger module cannot be closed if the Journals module is
still open for a period.
The month-end close will not be successful if any financial transactions are generated while the
MSB005 - Month End Roll-Over batch program is run.
Fixed Asset Month End is processed by running batch job MSB685 – Fixed Asset Month End. MSB685
calculates the depreciation and generates the related transactions (if depreciation has been
enabled) and rolls the period over to the next period.
48
External Systems Interface to Ellipse

This system is designed to allow Ellipse EAM to interact with any external system.
Overview diagram
Documents
Messages from Ellipse EAM are sent to the out packet queue using the subroutine MSS035, and are
made available for any external system using the subroutine MSS036.
Messages to Ellipse EAM are placed on the in packet queue using the subroutine MSS038, and are
processed by Ellipse EAM when ready, using the subroutine MSS037.
Limitations
There can be some limitations on the speed of the external system. While Ellipse EAM may place the
information on the out packet queue, the external system may not request the information for some
time.
Additional information
Ellipse EAM places a message on the out packet queue using the subroutine MSS035. The external
system retrieves the message from the queue using the subroutine MSS036. All messages are
periodically inspected by the batch program MSB035. Those that have been completely processed
(deleted) are removed from the system. Batch program MSB035 also checks the integrity of the
message files. It can also be used to mark as deleted, messages that are received and are known to
49
have been processed, but were not marked as deleted. Until the message is deleted from the out
packet queue by the batch program MSB035, any message or group of messages can be reported
upon.
The message data is transferred at a fixed number of characters per line. There may be up to 9.4
megabytes (95,700,000 characters) of information per message.
The external system places inbound messages on the in packet queue using the subroutine MSS037.
Ellipse EAM extracts these messages using the subroutine MSS038.
All inbound messages are periodically inspected by the batch program MSB037. Processed or
completed inbound messages (by Ellipse EAM) can be flagged for deletion from the message files. All
messages can be reported on until they are deleted.
The message undergoes status changes after each access. While it is being created, its status is
Incomplete. After the message has been created, its status changes to Complete and can be read
by any external system. When the external system starts reading the message, its status changes to
Accessing. When the external system has completed reading the message, its status changes to
Received. The external system can then set the status of the message to Deleted after the message
has been processed. If a message is created and left in an illegal status, its status is set to Errored
and subsequently to Deleted and it is removed from the out packet queue.
The External System Interface
The external system obtains messages from the out packet queue by calls to subroutine MSS036. It
is the responsibility of the external system to request the messages in a timely manner.
Ellipse EAM receives messages from the in packet queue by calls to subroutine MSS038.
There are two interfaces: MSS036 and MSS038. They are described below.
The MSS036 interface
Parameter Type Length Values/ Meaning
Character 1
OPTION 1 - RESERVED
2 - find a transmission, if available
3 - read a transmission
4 - complete receipt of a transmission
5 - abort the current read
Character 8
FACILITY-CODE free format
Character 2
FACILITY-ID free format
The meaning of the values of the parameter OPTION are:

 2 - used to determine if any messages are on the out packet queue. If a message is found, the
RETURN-STATUS is set to S (Successful) and the first line of the message is returned in MESSAGE.
If no messages are found, the RETURN-STATUS is set to U (Unsuccessful).
 3 - used to obtain successive lines of the message. At completion of the message, the RETURN-
STATUS is set to S (Successful).
 4 - used to terminate receipt of the current message and delete it from the out packet queue.
 5 - can be used at any time before option 4 and after option 2. It abandons the current message
retrieval and allows the message to be re-read from the beginning at a later date (by using
option 2 to find a transmission).
FACILITY-CODE and FACILITY-ID are used to specify which external system the messages are for.
These parameters should be set to the code for whichever external system is attempting to obtain a
message. If FACILITY-ID is left as spaces, all Facility IDs are returned for the supplied Facility Code.
50
FACILITY-ID is used to specify a particular sub-facility within the general facility specified by the
FACILITY-CODE. For example, an external system may be 'ACCNTNG', but there may be many actions
performed by this external system. In this case, FACILITY-ID is used to specify what action to
perform. This field is defined on a facility by facility basis.
A typical message for 'External' would be obtained using the following calls.
1. OPTION = 2, FACILITY-CODE = 'EXTERNAL', FACILITY-ID = spaces, gives a RETURN-STATUS of S
(assuming that a message was found) and MESSAGE with the first line of the message.
2. OPTION = 3 and all other linkage fields left as they are, gives a RETURN-STATUS of S (assuming
that there were more messages) and MESSAGE with the next line of the message.
Continue calling with this option until RETURN-STATUS is = U.
3. OPTION = 4 and all other linkage fields left as they are, stops the reading of the message and
removes it from the output packet queue.
To obtain another message, start again at OPTION = 2.
Note: It is very important that after OPTION = 2 is used successfully, only the OPTION parameter is
changed as the linkage area stores extra information between calls.
After a call to subroutine MSS036, the following parameters are available for interrogation:
Parameter Type Length Values/ Meaning Definition

Character 28
XMITTER-ID free format Unique identifier specifying which
Ellipse EAM system program sent
this message.
Character 1
REQUEST-TYPE R - if reply Flag that shows whether Ellipse EAM
expected expects a reply to this message.
Numeric 5
MESSAGE- 00000 - 99999 A packed signed numeric field (3-
LENGTH characters long) that provides the
length of the individual lines in the
message.
Character 1200
MESSAGE free format Contains a line (of the length
specified MESSAGE-LENGTH) of the
message.
If MESSAGE is returned from OPTION
= 2, it has a fixed length of 61
characters.
Character 1
RETURN-STATUS S or M - Used to signal the status of the
SUCCESSFUL performed operations.
STATUS M - MORE LINES

U - UNSUCCESSFUL
P - PARTIAL
When the RETURN-STATUS is S or M the operation was successful. When it is M there are more
message lines available. When the RETURN-STATUS is U the operation was unsuccessful. When the
RETURN-STATUS is P the operation has returned only part of a message in MESSAGE, where the total
length of the message (MESSAGE-LENGTH) is greater than can be passed in MESSAGE in one go. The
rest (or further instalments) of the message will be returned in successive calls.
The MSS038 interface
The following parameters are available:
51

Character 1
OPTION 1 - used to allocate a packet in the in packet queue.
2 - used to add lines to the message.
3 - used to finish the transmission and send the
message.
4 - used to stop the current transmission.
Character 8
FACILITY-CODE Free format
Used to specify the Ellipse EAM system to which the
message refers.
Character 2
FACILITY-ID Free format
Used to specify the Ellipse EAM system to which the
message refers.
Character 1
PRIORITY A through Z
Used to specify the importance of this message, relative
to other messages.
A is the most important and Z is the least important.
Character 8
REV-DEF-DATE Reverse Defer Date
Used to specify a defer date for the delivery of the
message.
Character 6
REV-DEF-TIME Reverse Defer Time
Used to specify a defer time for the delivery of the
message.
Character 12
XMITTER-ID free format
Used to specify which system, subsystem, or program is
sending the message.
Character 1
REQUEST-TYPE R, if a reply is expected
Used to specify whether or not a reply is expected from
Ellipse EAM.
Numeric -+5
MESSAGE- 00000 - 99999
LENGTH
Used to specify the length of each line in the message.
All lines are of equal and fixed length.
Character 1200
MESSAGE Free format
Used to pass a line of the required message.
Character
HEADER-TYPE Y, if this is a single line message
Used to specify whether or not this message is a single
line short message of 61 characters.
The following parameters should be set up:

 FACILITY-CODE
52
 FACILITY-ID
 PRIORITY
 XMITTER-ID
 MESSAGE-LENGTH
The following parameters can optionally be set up:
 REV-DEF-DATE
 REV-DEF-TIME
 REQUEST-TYPE
 MESSAGE
 HEADER-TYPE
With OPTION 2, only the OPTION and MESSAGE fields should be changed. If a line is successfully
added, the RETURN-STATUS is set to S (SUCCESSFUL), otherwise the RETURN-STATUS is set to U
(UNSUCCESSFUL).
With OPTION 3, the MESSAGE field is added as a line to the message. Only OPTION and MESSAGE
should be changed.
With OPTION 4, only the OPTION should be changed. The current message is discarded and is not
sent.
PRIORITY only assures an order for messages, not that messages will be expedited in any manner.
REV-DEF-DATE is calculated as 99999999 - CCYYMMDD (where CC is century, YY is year, MM is
month and DD is date of day). If this field is set, the message is not delivered before this date.
REV-DEF-TIME is calculated as 999999 - HHMMSS (where HH is hour, MM is minutes, SS is seconds). If
this field is set, the message is not delivered before this time.
The following parameters are available for interrogation after a call to subroutine MSS038:

Character 1
RETURN-STATUS S - SUCCESSFUL
U - UNSUCCESSFUL
RETURN-STATUS is used to signal the status of the performed operations.

When the RETURN-STATUS is S, the operation was successful. When the RETURN-STATUS is U, the
operation was unsuccessful.
53
General Housekeeping
This section describes the housekeeping programs. These are:
 Update MSFX99 record with Project No. - MSHX99A
 Rebuild MSFX99 records for Work Orders - MSHX9AA
 Convert Request Banners - MSH080A
 Bulk Request Creation - MSH083A
 Convert Help Text - MSH091A
 Convert Standard Text (Relational) - MSH095A
 Convert Standard Text (Compression) - MSH096A
54
Convert Request Banners - MSH080A

MSH080A is a program that runs only once. It converts the Banner field on both the Report Request
(file MSF080) and the Cyclical Report Request (file MSF082) from binary format to numeric format
when the Medium is either M (eMail) or U (Publish). This conversion is required primarily for SQL
Server platforms.
File Dependency
Main File
MSF080
MSF082
Sort Sequence and Report Breaks
None.
Frequency
Once.
Selecting the Printer
The printer is nominated during the request process.
Report Information
This program produces a log indicating the number of Request records and the number of Cyclical
Request records that were read and updated.
Selecting Report Contents
There are no request parameters for this report.
55
Convert Standard Text (Compression) - MSH096A

Program MSH096A is a housekeeping program. It converts the Standard Text file (MSF096) from a
non-relational format to a relational format.
File Dependency
Main File Lookup File
MSF096 MSU09604
None.
Frequency
When converting from a non-relational environment to a relational environment.
Report Information
This program produces a log indicating the number of help text records that were read and
rewritten.
56
Convert Standard Text (Relational) - MSH095A

Program MSH095A is a housekeeping program. It converts the Standard Text file (MSF096) from a
relational format to a non-relational format.
File Dependency
MSF096 MSU09604
None.
Frequency
When converting from a relational environment to a non-relational environment.
Report Information
This program produces a log indicating the number of help text records that were read and
rewritten.
57
Rebuild MSFX99 records for Work Orders - MSHX9AA

This housekeeping program is designed to rebuild MSFX99 (WO/Account Code/GL transaction Cross
Reference) records from MSF900, MSF901, and MSF902 transaction files where necessary, for
selected Work Orders.
File Dependency
MSF900 MSF260
MSF901 MSFX99
MSF902
None.
Frequency
As required.
Report Information
This program produces a single report, whether run in Report Mode or Update Mode. The report
includes details of each MSFX99 record rebuilt, plus a summary of Work Orders read and MSFX99
records written. It should be noted that the Cost Category applied to newly created MSFX99 records
is based upon current rulings, rather than historical rulings.
The following information can be entered on the report selection screen for this report:
 Work Order No. From - enter a Work Order number from which to commence processing. Entry
is optional. If entered, the Work Order No. To field must also be completed.
 Work Order No. To - enter a Work Order number up to which processing will continue. Entry is
optional. If entered, the Work Order No. From field must also be completed.
 Work Order Numbers - enter up to ten Work Order numbers. Entry is optional.
 Report Mode Only (Y/N) - enter 'Y' to run the program in Report Mode only, or 'N' to run in
Update Mode. Entry is mandatory.
58
Update MSFX99 record with Project No. - MSHX99A

This housekeeping program is designed to browse all MSFX99 (WO/Account Code/GL Trans) records
and for each posted transaction record found, read the associated Work Order (MSF620) file to
obtain the current Project number.
File Dependency
MSFX99 MSF620
None.
Frequency
As required.
None.
Report Information
None.
59
Audit Rules, Restrictions and Overrides

Many organisations have a focus on safety to ensure that the workplace is safe for employees, and
that procedures and guidelines are followed to minimise safety incidents. For some organisations,
there is the extra consideration of public safety and environmental impacts arising from accidents.
Failure to follow procedures for these organisations can have severe consequences, including
affecting public perception and trust in the organisation, environmental impact, loss of market
credibility and loss of profitability.
Where the impact of not following procedures is significant, an organisation may choose to carry out
compliance reviews of updates to the Ellipse EAM system, to ensure people are following correct
processes. In such circumstances, auditors will need to identify information, review the information
and record details about the audit process and compliance with procedures.
Should a safety incident occur, organisations will need to investigate the root cause and plan
actions to prevent the safety incident recurring. An accident investigator will need to be able to
review the history of significant data around the maintenance of assets involved in the incident, for
example, checking that work was not rescheduled, reprioritised or closed incorrectly.
Organisations may also have other significant data that needs to be monitored to confirm correct
business process has been followed around the data modification. For example, if the account code
on certain types of work orders or projects are changed, the finance department might have to be
notified before making the change.
The Field Level Audit and Safety Compliance functionality assists organisations in reviewing and
validating that procedures are followed and allows auditors to apply reasons and comments for
changes against the audit data being reviewed.
 Audit rule application (MSEADR) allows organisations to determine, which data is important for
audit requirements and to define rules to capture that data.
 Audit application (MSEAUD) allows searching and review of audit data. The application also
enables users with sufficient security access to update audit data with reasons and comments.
 Audit file restriction application (MSEAUR) provides a mechanism to restrict access to audit data
that may be sensitive (for example, HR or Payroll details). By default, users will not have access
to review HR and Payroll data. This application can be used to see the list of files that can’t be
reviewed and will allow an organisation to set security levels to control who can see the
sensitive data.
Defining Audit Rules

Audit rules can be defined using MSEADR. This allows the organisation to create rules matching
their requirements for data to be captured for audit. Once an audit rule is created in MSEADR, the
rule takes immediate effect and any matching updates to files with rules will generate audit data
which can be reviewed in MSEAUD.
Audit File Restrictions

The normal service level security around Ellipse EAM applications data does not apply to the audit
generated data. As some organisations may choose to audit files that have sensitive personal
information, there needs to be a mechanism to restrict access to this data. There also needs to be a
mechanism for an organisation to choose other files which contain business sensitive information
and to be able to restrict access to audit data from these files.
MSEAUR - Audit Restriction Override allows customers to see which files have restricted audit
access, and to set up override access. By default, the Ellipse EAM configuration restricts access to
all the HR/Payroll files that may contain sensitive personal information. Overrides will need to be
configured before any audit data from HR/Payroll files can be accessed in MSEAUD.
MSEAUR also allows restriction overrides to be set up for any other Ellipse EAM files to restrict
access to audit data from these files. Access levels defined in MSEAUR are matched against the
security access of the MSEAUD search method to determine if a user is restricted from seeing
certain audit data.
60
Note: Audit restrictions can be removed from files that customers have added to the system, by
opening the audit restriction application and selecting Delete. Deleting an audit restriction for non
HR/Payroll files allows all users to access audit data for that file. If an audit restriction override is
deleted for a HR/Payroll file (for example MSF810), the override that was set will be deleted, but
the system defined No Access rule will not be deleted.
61
Create Audit Rule

Use this activity to create an audit rule.
Activity Steps
1. Access MSEADR - Audit Rules.
The MSEADR - Search Audit Rules screen displays.
2. Select New.
The MSEADR - Audit Rules detail screen displays.
3. Enter data in the following fields
Table Name
Description
 If no column conditions are specified in the Column Conditions tab, all operations are
audited.
 If no columns are specified in the Column Inclusions tab, all operations are audited.
4. Select Submit.
The audit rule is saved.
62
Review Audit Rule

Use this activity to review an audit rule.
Activity Steps
2. Enter the relevant search criteria.
Select Search.
4. Review data as required
63
Update Audit Rule

Use this activity to update an audit rule.
Activity Steps
Select Search.
4. Modify data as required
 If no column conditions are specified in the Column Conditions tab, all operations are
audited.
 If no columns are specified in the Column Inclusions tab, all operations are audited.
5. Select Submit.
64
Delete Audit Rule

Use this activity to delete an audit rule.
Activity Steps
Select Search.
4. Select Delete.
The Confirm Delete dialog box displays.
5. Select OK.
The audit rule is deleted.
65
Review Audit Data

Use this activity to review audit data.
Audit data matching the audit rules can be reviewed online. Auditors, compliance officers, accident
investigators and safety officers can use MSEAUD to review audit details generated by the audit
rules.
Activity Steps
1. Access MSEAUD - Audit.
The MSEAUD Search Audit screen displays.
3. Select Search.
The results of the search display in the grid.
66
Update Audit Rule Reason Code or Comment

Use this activity to update an audit rule reason code or comment. You can update a single,
multiple, or all audit records at the same time.
 To update a single rule, select the row in the grid to be updated.
 To update multiple audit records, select multiple rows in the grid.
 To update all audit records, select the very top row in the grid.
Clicking Update Reason/Comments allows the same reason/comment to be applied to all selected
rows.
Note: For a single row, clicking the Update Reason action from the front of the grid row always
shows the history of updates. For bulk updates, clicking the Update Reason/Comments button at the
bottom of the grid applies updates to the records without reviewing the history.
Activity Steps
1. Access MSEAUD - Audit.
The MSEAUD Search Audit screen displays.
3. Select Search.
The results of the search display in the grid.
4. Select the rows to be updated.
5. Click Update Reason/Comments.
The Update Reason / Comments Dialog box displays.
6. Enter a reason code and / or comments.
7. Select OK.
The information displays in the results grid.
67
Create Audit Restriction Override

Use this activity to create an audit restriction override.
Activity Steps
1. Access MSEAUR - Audit Restriction Override.
2. The MSEAUR - Search Audit Restriction Override screen displays.
3. Select New.
4. The MSEAUR - Create Audit Restriction Override screen displays.
5. Enter data in the following fields
Table Name
Override Level
6. Select Submit.
The audit restriction override is created.
68
Review Audit Restriction Override

Use this activity to review an audit restriction override.
Activity Steps
The MSEAUR - Search Audit Restriction Override screen displays.
3. Select Search.
Results matching the search criteria display in the grid.
69
Update Audit Restriction Override

Use this activity to update an audit restriction override.
Activity Steps
3. Select Search.
6. Modify data as required
7. Select Submit.
The updated details are saved.
70
Delete Audit Restriction Override

Use this activity to delete an audit restriction override.
Note: Audit restrictions can be removed from files that customers have added to the system, by
opening the audit restriction application and selecting Delete. Deleting an audit restriction for non
HR/Payroll files allows all users to access audit data for that file. If an audit restriction override is
deleted for a HR/Payroll file (for example MSF810), the override that was set will be deleted, but
the system defined No Access rule will not be deleted.
Activity Steps
3. Select Search.
6. Select Delete.
The Confirm Delete dialog box displays.
7. Select OK.
The audit restriction override is deleted.
71
Bulk Request Creation - MSH083A

Program MSH083A is a housekeeping program. It creates and modifies last run records for the
following batch programs:
 MSR146
 MSR14A
 MSR151
 MSR153
 MSR224
 MSR287
This program uses the last transaction run (MSB900 - Transactions Posting Update Control) key when
writing the requests.
File Dependency
Main File
MSF083
Frequency
When requested by Ventyx.
Report Information
This program produces a log indicating the number of request records written.
72
Work File Procedures

Various Ellipse EAM programs use the work file for extra data storage. The life span of data written
to the work file is transaction dependent.
The work file contains three basic forms of data:
 Screen scrolling data
 Screen navigation data
 Temporary storage data
Overview diagram
The content of data stored on the work file is transaction dependent.
Data records are created and re-used according to transaction logic.
73
Administration - Reports
74
Reports
MSB042 - Notification & Diary Deletion ............................................................. 77
MSB043 - Notification & Diary Reminder ............................................................ 78
MSB044 - Notification & Diary Escalation ........................................................... 79
MSB04A - Diary and Notification Report ............................................................ 80
MSB070 - Bulk Changes ................................................................................. 81
MSB07A - Transfer Selection .......................................................................... 84
MSB07B - Process Transfer ............................................................................ 85
MSB07C - Reduce Dues-In District/Warehouse ..................................................... 87
MSB07D - Close a District .............................................................................. 88
MSB07E - Check for Closure ........................................................................... 89
MSB07F - Bulk Requisition Cancel .................................................................... 92
MSB07G - Delete a Transfer List ...................................................................... 93
MSB07H - Close Warehouse ............................................................................ 94
MSR07Z - Transfer Errors .............................................................................. 95
MSB17V - Valuation Accounting Report ............................................................. 96
MSB19H - Delete Bin Locations ....................................................................... 97
MSBTNE - Maximum Transfer Number Exceeded .................................................. 98
MSB877 - Archive Authorisations ..................................................................... 99
MSB907 - Archive/Roll Back Transactions .......................................................... 100
MSR038 - Errored/Junked Incoming Messages Report ............................................ 101
MSR040 - Diary Report ................................................................................. 102
MSR041 - Diary Follow-Up Report .................................................................... 104
MSR042 - Employee Diary Report..................................................................... 105
MSR079 - Check for District/Warehouse Closure, Goods Holding .............................. 106
MSR07A - Check for District/Warehouse Closure - Orders Report .............................. 107
MSR07B - Check for District/Warehouse Closure - Warehouse Requisitions Report ......... 108
MSR07C - Check for District Closure - Holdings Report ........................................... 109
MSR07D - Check for District Closure - Accounts Payable Invoices Report..................... 110
MSR07E - Check for District Closure - Accounts Receivable Invoices Report ................. 111
MSR07F - Check for District Closure - Work Orders Report ...................................... 112
MSR07G - Check for District Closure - Equipment Report ....................................... 113
MSR07H - Check District/Warehouse Closure - Waybills Report ................................ 114
MSR07I - Check for District Closure - Batch Requests Report ................................... 115
MSR07J - Check for District Closure - Scheduled Tasks Report ................................. 116
MSR07K - Check for District Closure - Goods in Transit Report ................................. 117
MSR07L - Check for District/Warehouse Closure - Purchase Requisitions Report ........... 118
MSR07M - Check for District Closure - Open Incidents Report .................................. 119
MSR07N - Check for District Closure - Logsheets .................................................. 120
MSR07O - Check for District Closure - Projects Report ........................................... 121
MSR07P - Check for District Closure - Accounts Report .......................................... 122
MSR07Q - Check for District Closure - Employees Report ........................................ 123
MSR07R - Check for District Closure - Labour Costing Report ................................... 124
MSR07S - Check for District Closure - Unposted Transactions Report ......................... 125
MSR07T - Check for Supply Customer Closure - Holdings Report ............................... 126
MSR07U - Check for Supply Customer Closure Requisitions Report ............................ 127
MSR07V - Check for Supply Customer Closure - In Transit ....................................... 128
MSR07W - Check for District Closure - Cyclic Requests Report ................................. 129
MSR07X - Check for District Closure - Repair Requests Report ................................. 130
MSR07Y - Check for Warehouse Closure - Holdings Report ...................................... 131
MSR081 - Batch Request Parameters Report ....................................................... 132
MSR083 - Cyclical Request Report ................................................................... 133
MSR09A - Work File Listing ............................................................................ 134
MSBXPO - Purchase Order Print XML ................................................................. 135
MSBXRQ - Request for Quotation ..................................................................... 148
MSRXDRA - Discrepancy Report Letter .............................................................. 154
MSIXPO - Build PO and PS Interface ................................................................. 160
MSIXRQ - TTT ............................................................................................ 171
MSIXRA - TTT ............................................................................................. 179
75
MSIXSS - TTT ............................................................................................. 184
76
MSB042 - Notification & Diary Deletion

Batch program MSB042 deletes notification messages older than a specified number of days. The
message age is based on the creation date. Both notification messages and diary entries will be
processed.
This program will typically be used on a cyclical basis. Multiple requests can be scheduled with
different parameters and cycles if different notification types are required to be retained for
different periods.
The following summary details are produced by this report:
 The number of messages processed
 The number of messages deleted
this report:
Status Enter the status code of the notifications to be deleted.
Include Emailed Select Yes to include emailed notifications in the processing.

Notifications
If not entered, No defaults.
Delete After No of Enter the number of days since creation after which notification messages
Days or diary entries will be deleted.
Exclude Event Names Select one or more types of notification event to be excluded from
processing. Up to 10 event names may be nominated.
Exclude Diary Types Select one or more types of diary message to be excluded from
processing. Up to 10 diary types may be nominated.
77
MSB043 - Notification & Diary Reminder

Batch program MSB043 will send an email to the original notification recipients when a nominated
event or diary type has not been processed for a specified number of days since the notification
creation date. Both notification messages and diary entries will be processed, but unassigned diary
entries will be excluded.
The email will be sent depending on the original recipients' preferences. The new message will be
for Event Name or Diary Type Reminder, and will contain the subject line Reminder for diary
type/event XXX. The message will contain the diary or event type and key details including the
creation date. The original message will be unchanged.
This program will typically be used on a cyclical basis.
 The number of messages for which a reminder was sent
this report:

Notifications
Remind After No of Enter the number of days since creation of the original notification
Days message or diary entry after which a reminder will be sent.
New Priority Enter the priority for the reminder notification.
Include Event Names Select one or more types of notification event to be included in
processing. Up to 10 event names may be nominated.
Include Diary Types Select one or more types of diary message to be included in processing.
Up to 10 diary types may be nominated.
78
MSB044 - Notification & Diary Escalation

Batch program MSB044 will send an email to nominated recipients when a nominated event or diary
type has not been processed for a specified number of days since the creation date. Both
notification messages and diary entries will be processed. Only Open items will be included in
processing.
The email will be sent depending on the nominated recipients' preferences. The new message will
be for Event Name or Diary Type Escalation, and will contain the subject line Escalation for diary
type/event XXX. The message will contain the diary or event type and key details including the
creation date. The original message will be unchanged.
This program will typically be used on a cyclical basis.
 The number of messages for which an escalation was sent
this report:
Diary Type Select a diary type to be processed. If a diary type is selected, an event
name cannot be specified.
Event Name Select an event name to be processed. If an event name is selected, a

diary type cannot be specified.

Notifications
New Priority Enter the priority for the escalation notification.
Recipient Type Enter the recipient type for the escalation message. This must be
consistent with the type of message, for example, a diary message cannot
be escalated to a team.
Recipient Enter the recipient id for the escalation message. This can be an
employee number, position id or team identifier. It must be consistent
with the selected Recipient Type.
Escalate After No of Enter the number of days since creation of the original diary entry or
Days notification message after which an escalation message will be sent.
79
MSB04A - Diary and Notification Report

MSB04A report lists diary messages associated with the request parameters selected from Diary file
(MSF040). The request parameters consist of a maximum of ten specified diary types (all types if
blank); this is optionally restricted by the responsibility code, action date range, and status.
this report:
Diary Type The diary entry type associated with the message. Entry is validated
against the Table File XD - Diary Entry Control Record.
Event name The event that triggered the notification. Entry is validated against the
Table File EVNT - Ellipse EAM Event.
Diary/Message Status The diary entry status (All, Open or Complete).
Assign Status The assignment status for the diary entry (Assigned or Unassigned).
Team The team that the notification was directed to.
Position Id The position ID to report notification/diary messages for a position.
Employee Id The ID of the employee.
From Date The first diary message/notification creation date in the range.
To Date The end diary message/notification creation date in the range.
Include Text (Y/N) Enter Y to include the text associated with the notification message.
80
MSB070 - Bulk Changes

MSB070 is the batch program used to make bulk changes to one of the following entities:
 Supply Catalogue - (MSM104A)
 Inventory - (MSM177A)
 Purchasing - (MSM215A)
 Global Requirements Determination - (MSM16AA)
On bulk change of the home warehouse, if the warehouse does not exist in the district a warehouse
record is created.
After entering normal report parameters, a selection screen displays. You can enter a maximum of
three selection and change parameters. The change parameters consist of specifying a From value
and a To value.
this report:
81
The screen MSM104A - Supply Catalogue Bulk Change - Select is used to

enter the parameters for the Supply/Catalogue option of Bulk Changes and
is called from MSB070. The changes are made to the Catalogue by the
batch program MSB070.
The following list of predetermined data dictionary items shows the
selection options available to you:
1. Category Id
2. Stock Class
3. Stock Type
4. UN Transport Type
5. Haz. Material Code
6. Template Id
7. Concession Category
8. Mnemonic
9. Colloquial
10. APL Number
11. Catalogue Section 1
21. Catalogue Reference Code
22. Repairable Item
23. Policy
24. Stock Item Owner
25. Batch Lot Management
26. Shelf Life Period
27. Quality Inspection Type
28. Inspection Frequency
Text for options 10-19 is obtained from Table File C0 - C9 which is set up
using Table File XX.
Selection Your selections should not conflict with each other or present an
ambiguous choice for the batch process to interpret.
You can enter either an = or a number representing one of the data items
displayed. Enter = to select all records on the Supply Catalogue file.
82
Value of The value must be valid for the choice made as determined by the
items to validation rules for original entry. Enter = to select all records on the
select Supply Catalogue file MSF100.
The following validation applies to the selection parameters:
 Product Services Category
This entry field must exist on the Product Services Category file
(MSF1EI).
 Stock Class
This entry field must exist on Table File CL.
 Stock Type
This entry field must exist on Table File ST.
 UN Transport Code
This entry field must exist on Table File TN.
 Hazardous Material Code
This entry field must exist on Table File HZ.
 Template ID
This entry field must exist on the Template ID file.
 Mnemonic
This entry field must exist on the Part Number/ Stock Code Cross
reference file (MSF110C).
 Colloquial
This entry field must exist on the Colloquial Name Reference file
(MSF120).
 APL Number
This entry field must exist on the APL Header file (MSF130). You can
enter a partial APL Number.
 Table File C0 - C9
This entry field must exist on the relevant table file (C0 - C9).
 Cat. Reference Codes
This entry field is validated against the special edit field type defined
for the Reference Code Number. This field can contain spaces for the
second and third selections.
 Repairable Item
Valid values for this entry field are Y and N. This field is only available
if the Repairable Item Management module is installed.
Reference Enter the reference code number to be used in conjunction with the Cat.
No. Reference Codes selection. This field is mandatory for the Select by
Reference Codes option. You must enter a valid reference code number
for the CAT entity. Entry is not required for other selection options.
If you enter a ?, control passes to the Review Reference Code Parameters
screen. You can then select the appropriate reference code number.
83
MSB07A - Transfer Selection

Report MSB07A identifies orders, requisitions and holdings for a nominated district, warehouse or
supply customer account. It also adds any item that prevents the district or supply customer
account from being closed to a transfer list.
Where a supply customer account is closed the order is not transferred.
The following summary details display on this report:
 Transfer run number for the list created
 Entity nominated for closure (that is, district or district and warehouse or supply customer
account)
 Number of orders selected
 Number of requisitions selected
 Number of stock holdings selected
 Number of supply customer holdings selected
 Number of supply customer transfers selected
 Total number of records selected
this report:
Type Enter the transfer selection type.
District Enter the district code. Entry is mandatory if closing a district and in
either an active or suspended state.
Transfer District Enter the transfer district.

This field is optional. If you enter a transfer district, it will be used by the
transfer process to record a district against each item selected and
written to the Transfer List, providing the item can be transferred.
84
MSB07B - Process Transfer

Batch program MSB07B activates the transfer list, shifting the items to the nominated districts or
supply customer accounts.
It scans through purchase orders, requisitions and stock holdings previously identified as needing to
be transferred to another location so the account specified (district or warehouse or supply
customer account) can be closed. These items with the details of the new transfer location are
written to the transfer list item file by the MSB07A - Transfer Selection program.
All items that fail the transfer process are written to the report and their status set to E (error). An
error code is recorded on the transfer list. All items successfully transferred have the status
updated to I (inactive) on the transfer list.
Transfer location details previously reported against each transfer item are used to transfer the
item to the new location.
The transfer item can be a purchase order, requisition, or stock holding from a district/warehouse,
or a customer holding from a supply customer account.
The transfer destination for the item can be a district or district/warehouse or another supply
customer account depending on the list entity type.
Purchase orders, requisitions and customer transfers for a supply customer account cannot be
transferred.
Transfers are not processed:
 for transfer items, where the district/warehouse is the same as the destination
district/warehouse
 if no transfer details are found against the transfer item and not specified on MSF07A for the
run
Items will be selected for transfer based on the following criteria:
PURCHASE ORDERS (Type 0)
Purchase order items for a supply customer account or items referring to a purchase requisition, or
items being selected for a district/warehouse closure, partially receipted, cannot be transferred to
a new district.
Transfer of purchase orders to a nominated district/warehouse changes the delivery
district/warehouse on the purchase order item, decrements the dues-in in the items
district/warehouse, and increments the dues-in in the destination district/warehouse.
REQUISITIONS (Type R)
Requisitions for district transfers, warehouse transfers, referred demands or for a supply customer
account cannot be transferred to a new district.
If a requisition is being moved to another warehouse the item on the requisition is completed and a
new item created on the requisition for the new warehouse.
Requisitions transferred to a new district are set to 9 - complete in the current district/warehouse
and a new requisition created in the destination district/warehouse.
Note: There is no link between the old requisition and the new generated requisition.
Transfer of requisitions to a nominated district/warehouse will:
 reduce the dues out in the items district/warehouse
 increase the dues out in the destination district/warehouse
The requisitions are transferred with a status of not printed.
STOCK HOLDINGS (Type S)
Stock holdings with a different district to the destination district will have an inter-district transfer
generated to produce the following:
85
 A purchase order in the transfer district

 An issue requisition in the item district
If the district on the stock holding is the same as the destination district but the warehouse is
different to the destination warehouse, a warehouse transfer is generated.
If no records exist for the stock code in the transfer district an error is produced and the transfer
not proceeded.
The current district for the stock holding has to be a valid supplier with business information
present in the transfer district for the inter-district transfer to proceed.
SUPPLY CUSTOMER HOLDINGS (Type C)
If the transfer location type for the supply customer holding is D the stock is being moved back to a
district/warehouse and a credit return requisition for the nominated district/warehouse is
generated.
If the transfer location type for the supply customer holding is S the stock holding being transferred
to another supply customer account and a supply customer transfer is generated.
The customer stock holdings for the supply customer account is updated on the supply customer
inventory details file.
ALL TRANSFER LIST TYPES
All transfer list items failing the transfer process are written to the report and an error code is
recorded against them on the transfer list.
All transfer list items that are successfully transferred have their status updated to I (in-active) on
the transfer list.
At the end of the run the following summary details are produced on this report:
 Transfer run number for the list processed
account)
 Number of purchase order items processed
 Number of purchase orders rejected
 Number of requisitions transferred
 Number of requisitions rejected
 Number of stock holdings transferred
 Number of stock holdings rejected
 Number of supply customer holdings transferred
 Number of supply customer holdings rejected
 Total Processed Items
 The number of items of all types on the nominated transfer list that passed the tests for
eligibility and were successfully transferred to the new location, as specified for the
transfer list item.
 Total Failed Items
 The number of items of all types on the nominated transfer list that failed the transfer
process.
86
MSB07C - Reduce Dues-In District/Warehouse

Batch program MSB07C is requested when a district/warehouse is to be suspended. It reduces the
level of unactioned recommended orders and transfer orders not picked in the issuing district to
match the level of dues-out.
The process is submitted when a request is made to delete all the unactioned recommended orders
and transfer orders when a district or warehouse is being closed.
The following summary totals are produced in this report:
 District or Warehouse used to select the items
 The number of recommended orders processed
 The number of transfer orders deleted
 The number of transfer orders completed
 The total number of orders successfully processed
this report:
Type Enter the transfer type to match the level of dues out for the district
being suspended.
District Code Enter the district code. This is validated against the VALIDATE macro with
the DSTRCT-CODE, ACTIVE, and AuthoriseD options to ensure the district
is active. The user must be authorised to access the district information.
Process Transfer Enter Y to include the transfer orders in the processing.

Orders
If not entered, N defaults.
87
MSB07D - Close a District

Program MSB07D closes the requested district when all closing conditions are met.
This report is run in either report or update mode. It produces a summary report indicating closure
conditions not met. The MSB07E - Check for Closure reports is run to provide full details of the
outstanding transactions not meeting the closure conditions.
Report check for closure is run to extract details for each condition type. When run in update mode
and no conditions are detected that would prevent the district being closed, the batch program
updates the district status.
Errors are written to the report leaving the district suspended. The closure report is re-checked to
ensure all outstanding conditions are actioned.
Closure of a district is prevented if any of the following conditions are met:
 outstanding dues-in
 outstanding dues-out (all requisition types including loans and recalls)
 stock holdings
 goods in transit
 open purchase requisitions
 open waybills
 open work orders
 open incidents (not included in the CFSSU solution)
 unprocessed log sheets (not included in the CFSSU solution)
 open projects
 scheduled tasks
 goods holding
 active equipment
 outstanding accounts receivable invoices
 outstanding accounts payable invoices
 cyclic requests (for example, automatic replenishment)
 batch requests
 certain accounts must have a zero balance at closure
 no employees may be linked to pay groups that are in the district to be closed
 no employees should be currently costed against the district to be closed
 all labour costing transactions for the district should be posted
 all financial transactions should be posted
 inter-company accounts should be zero
 no outstanding discrepancy reports
An associated value on the table file - MC indicates that a particular control account must have a
zero balance before a district can be closed.
Parameters Enter the following information in the Report Request Selection screen for this
report:
District Enter the district code. Entry is mandatory if closing a district and in either an
active or suspended state.
88
MSB07E - Check for Closure

Batch program MSB07E records details of the entity selected for closure and the reports that have
been requested to be checked for various transaction types.
There are three types of closure reports:
 Closure Report for District
 Closure Report for Warehouse
 Closure Report for Supply Customer Account (SCA)
The following summary details are produced in this report:
account)
 Closure reports requested
Additional Information - Closure Report for District
Additional Information - Closure Report for Warehouse
Additional Information - Closure report for Supply Customer Account
this report:
Type Enter the type indicator for the district closure report.
District Enter the district code. This field is mandatory if closing a district in an
active or suspended state.
Note: The reports selected are only those relevant to the type of closure
being processed. The following reports are generated:
Orders - (MSR07A) Enter Y to request this closure report. MSR07A report is generated.
Warehouse Enter Y to request this closure report. MSR07B report is generated.

Requisitions -
(MSR07B)
Stock Holdings - Enter Y to request this closure report. MSR07C report is generated.
(MSR07C)
Accounts Pay, Enter Y to request this closure report. MSR07D report is generated.
Invoices - (MSR07D)
Accounts Recv, Enter Y to request this closure report. MSR07E report is generated.
Invoices - (MSR07E)
Work Orders - Enter Y to request this closure report. MSR07F report is generated.
(MSR07F)
Equipment - (MSR07G) Enter Y to request this closure report. MSR07G report is generated.
Waybills - (MSR07H) Enter Y to request this closure report. MSR07H report is generated.
Batch Requests - Enter Y to request this closure report. MSR07I report is generated.
(MSR07I)
Scheduled Tasks - Enter Y to request this closure report. MSR07J report is generated.
(MSR07J)
89
Goods in Transit - Enter Y to request this closure report. MSR07K report is generated.
(MSR07K)
Purchase Requisitions Enter Y to request this closure report. MSR07L report is generated.
- (MSR07L)
Open Incidents - Enter Y to request this closure report. MSR07M report is generated.
(MSR07M)
Logsheets - (MSR07N) Enter Y to request this closure report. MSR07N report is generated.
Projects - (MSR07O) Enter Y to request this closure report. MSR07O report is generated.
Control Accounts - Enter Y to request this closure report. MSR07P report is generated.
(MSR07P)
Employees - (MSR07Q) Enter Y to request this closure report. MSR07Q report is generated.
Labour Costing - Enter Y to request this closure report. MSR07R report is generated.
(MSR07R)
Unposted Transactions Enter Y to request this closure report. MSR07S report is generated.
- (MSR07S)
Cyclic Requests - Enter Y to request this closure report. MSR07W report is generated.
(MSR07W)
Repair Requests - Enter Y to request this closure report. MSR07X report is generated.
(MSR07X)
Good Holdings - Enter Y to request this closure report. MSR079 report is generated.
(MSR079)
this report:
Type Enter the type indicator for the warehouse closure report.
District Enter the district code. This field is mandatory if closing a district and in
either an active or suspended state.
Warehouse Id Enter the warehouse ID for the requested closure report.
Note: The reports selected are only those relevant to the type of closure
being processed. The following reports are generated:
Orders - (MSR07A) Enter Y to request this closure report. MSR07A report is generated.
Warehouse Enter Y to request this closure report. MSR07B report is generated.

Requisitions -
(MSR07B)
Waybills - (MSR07H) Enter Y to request this closure report. MSR07H report is generated.
Goods in Transit - Enter Y to request this closure report. MSR07K report is generated.
(MSR07K)
90
Purchase Requisitions Enter Y to request this closure report. MSR07L report is generated.
- (MSR07L)
Stock Holdings - Enter Y to request this closure report. MSR07Y report is generated.
(MSR07Y)
Goods Holdings - Enter Y to request this closure report. MSR079 report is generated.
(MSR079)
this report:
Type Enter the type indicator for the supply customer account closure report.
Supply Customer Id Enter the supply customer ID for the requested closure report.
Note: The reports that can be selected are only those relevant to the
type of closure being processed. The following reports are generated:
Stock Holdings - Enter Y to request this closure report. MSR07I report is generated.
(MSR07I)
Requisitions - Enter Y to request this closure report. MSR07U report is generated.

(MSR07U)
Stock in Transit - Enter Y to request this closure report. MSR07V report is generated.
(MSR07V)
91
MSB07F - Bulk Requisition Cancel

Batch program MSB07F deletes or cancels warehouse and purchase requisitions.
Any loan returns or recalls have the required by date modified to the current date.
The following summary totals are produced in this report:
 The number of warehouse requisitions that have been processed
 The number of purchase requisitions that been processed
 The total number of requisitions successfully processed
92
MSB07G - Delete a Transfer List

Batch program MSB07G deletes all transfer records from a transfer list for a nominated transfer
selection number.
When all items on the list have been deleted successfully, the header record is also deleted.
 Transfer list number processed
 The number of transfer list items deleted
report:
Transfer Run Enter the transfer run number.

Number
This field is mandatory. The entry must exist on the transfer list header file.
93
MSB07H - Close Warehouse

Batch program MSB07H scans the warehouse to ensure that all closure conditions are met and if so,
closes the warehouse. If any errors are detected the warehouse is suspended. This report is checked
to ensure all outstanding conditions are actioned.
Closure of a warehouse is prevented if any of the following conditions are met:
 outstanding dues-in
 outstanding dues-out (all requisition types, including loans and recalls)
 stock holdings
 home warehouse for any stock items
 included in a DOS list
 nominated as a preference warehouse
 goods in transit
 recommended orders
 no outstanding discrepancy reports
 no cyclic requests for automatic replenishment (MSB180)
 goods holding
The following summary information is produced by this report:
 Warehouse nominated for closure
 Error messages identifying the type of any closure conditions not met
 Message to indicate the status of the warehouse at the end of processing
94
MSR07Z - Transfer Errors

The MSR07Z - Transfer Errors report displays records transferred to the MSF07B file that have been
flagged as errors. Refer to the MSR07B - Check for District Warehouse Closure report.
Parameters Enter the following information in the Report Request Selection screen
for this report:
Run Number Enter a valid Run Number. This field is mandatory
95
MSB17V - Valuation Accounting Report

The MSB17V program lists the summed value of stock items from Inventory Control file (MSF170) or
Category Costed file (MSF194) when the stock code is category costed.
For each stock code within the district, the following details display:
 Stock Code and Description
 Category
 Inventory or Asset
 Unit of Issue
 Stock on Hand
 Item Cost Price
 Currency Type
 Value At
 Inventory Value
At the end of the report, the following details display:
 Total Value at Net-Realisable Value (N)
 Total Value at Cost Replacement Value (C)
 Total Value at Inventory Cost Price (I)
 Total for all District
Parameters Enter the following information in the Report Request Selection

screen for this report:
Report Mode Enter the mode type. The report is generated in the selected
(D - Detailed, mode.
S - Summary)
All Districts Enter either Y or N. If Y is entered all districts are reported.
96
MSB19H - Delete Bin Locations

Batch program MSB19H is run from MSM19SA and deletes all records for the selected bin locations
where the stock on hand in the bin equals zero. This program verifies that a bin location has no
stock on hand before deleting.
97
MSBTNE - Maximum Transfer Number Exceeded

This batch program MSBTNE reports when the transfer order number has exceeded a pre-
determined value entered as a request value. The last system generated transfer number is read
from the system file and if any transfer order numbers exceed the pre-determined value a list
display on this report.
If the non-numeric prefix of the request parameter differs a warning message displays on the report
and further comparison is not possible.
this report:
Transfer Number to Enter a pre-determined transfer number.

Exceed
98
MSB877 - Archive Authorisations

Program MSB877A archives all authorisations prior to a specified date to a sequential file. A
summary report of archived records is produced.
This report can be generated at any time.
this report:
Archive Records Enter the cut-off date for archiving authorisations. All authorisations
Authorised before before the nominated date are archived.
99
MSB907 - Archive/Roll Back Transactions

This batch archives or rolls back transaction records. These include any associated journal
transaction extended text details.
Transaction records are re-distributed on transaction files MSF900,MSF901, MSF902, and MSF90F.
The transaction archive file (MSF078) is also used in this process.
This report can be generated at any time.
report:
Maximum You can limit the duration of the run duration by specifying the number of
duration of run in minutes of elapsed time for which the batch run is allowed to run. If the
minutes request is not complete by then, it remains active and continues when it is
next allowed to run.
Earliest Period Specify the earliest Accounting Period for which transaction records should be
for Transx on located on file MSF900. The program either adds records or moves them to
MSF900 other files to achieve this aim. The period specified must be before the
Current Period in the district.
If the period is not specified it is assumed that all transactions should be
relocated on file MSF900.
MSF901 other files to achieve this aim. Any period specified must be before the period
entered for file MSF900.
If a period is not specified, it is assumed that all transactions not included
above should be relocated on file MSF901. This period is not applicable if no
period was entered for file MSF900.
MSF902 other files to achieve this aim. Any period specified must be before the
earliest periods entered for files MSF900 and MSF901.
If a period is not specified, it is assumed that all transactions not included
above should be relocated on file MSF902. This period is not applicable if no
periods were entered for files MSF900 and MSF901.
Any transactions not covered above are relocated on file MSF078.
Do Consistency Enter Y to check consistency on all fields, to reset all necessary control
Test (Y/N) information required to run this process. This essentially requires a pass
through all the Transaction Master files and is generally only required when a
previous run of this process has not produced the expected redistribution
results.
100
MSR038 - Errored/Junked Incoming Messages Report

The MSR038 - Errored/Junked Incoming Messages report displays the MSM080B screen.
report:
Facility Code Enter the facility for the messages.
101
MSR040 - Diary Report

The MSR040 - Diary Report details information pertaining to diary entries presented by diary type,
responsibility code or action date.
The report can be sorted in the following orders:
A page break occurs on change of Diary Type if the report is ordered by Diary Type. Page break
occurs on change of Responsibility Code if the report is ordered by Responsibility Code.
The details listed are:
 Diary Type Description
 Diary Key presented according to the key structure
 Action Date
 Action Time
 Responsibility Person
 Created Date
 Created Time
 From
 Status
 Two Message Lines
 Extended Text Indicator
 Follow-up Entry Indicator
 Extended Text
At run time, security checks are made against the user who requested the report and the
responsibility code of the diary notes before data is included in the report.
this report:
Diary Type Enter up to 10 specific diary types to include in the report. Alternatively,
leave this field blank to include all diary types.
Entry is validated against the Table File XD - Diary Type.
Responsibility Code Enter a valid responsibility code. Entry is validated against the Employee
(Optional) Core Record file (MSF810). If this field is left blank, all responsibility
codes are included.
Age in Days (Optional) Age in days can be used to limit report to diary notes that are over this
many days old. Enter a valid number.
Action Date From Enter the date defining the start of the period to be reported. If this field
is left blank the report shows all diary entries earlier than the To date.
Action Date To Enter the date defining the end of the period. If this field is left blank all
diary entries with an action date after than the From date are included in
the report.
Diary Status Enter O for outstanding diary entries. Enter C for completed diary entries.
If this field is completed, only diary entries with a status matching that
entered are reported on. If this field is left blank, all diary entries within
the specified parameters are included on the report.
102
Order Enter T to sort and page break by Diary Type. Enter R to sort and page
break by Responsibility Code. Enter D to sort by Action Date/Time. If this
field is left blank the report is sorted by Diary Type.
Include Extended Text Enter Y to include extended text recorded for the diary entry in the
in Report report. If this field is left blank N is entered, no extended text is
included.
103
MSR041 - Diary Follow-Up Report

The MSR041 - Diary Follow-Up Report lists diary entries in a follow-up chain in the sequence in
which they were created.
The following details are reported:
 Diary Type
 Expanded Diary Key
 Customer Name
 Date Entered
 Time Entered
 Date Due
 Time Due
 Date Completed
 Time Completed
 Diary Status
 Diary Message
 Extended Text
 Responsible Person
 Responsibility Code
This report can only be selected from diary review and maintenance screens. The following
information is supplied by these programs:
 Diary Type
 Diary Key
 Due Date
 Due Time
 Sequence Number
104
MSR042 - Employee Diary Report

The MSR042 - Employee Diary Report provides a monthly picture of outstanding diary notes that
exist for a specified Employee Code.
This report is in the format of a calendar page. It details the number of outstanding diary entries
that exist for each day.
this report:
Responsible Code Enter a valid responsibility code. Entry is validated against the Employee
(Mandatory) Core Record file (MSF810).
Date From Enter the date defining the start of the period to be reported on.
(Mandatory)
Date To (Mandatory) Enter the month defining the end of the period to be reported on.
Status Enter O for outstanding diary entries. Enter C for completed diary entries.
If this field is completed, only diary entries with a status matching that
entered are reported on the details report (MSR042B). If this field is left
blank, all diary entries within the specified parameters are included on
the details report (MSR042B).
Print Report Enter A to print the summary report (MSR042A) only. Enter B to print the
detail report (MSR042B) only. Leave this field blank to print both reports.
105
MSR079 - Check for District/Warehouse Closure,

Goods Holding
Report MSR079 displays all goods currently held at the requested district or warehouse.
These report parameters are requested from MSB07E:
 Create Closure Report for Districts
 Create Closure Reports for Warehouse
 Create Closure Reports for SCA
106
MSR07A - Check for District/Warehouse Closure -

Orders Report
Report MSR07A displays all order items that preventing the nominated district or warehouse from
being closed. This includes all items that are not cancelled or complete.
The following details are printed for each order:
 Current district code and name
 Current warehouse code and name
 Order number
 Order item
 Order type
 Order status
 Order authorised status
 Supplier
 Stock code/purchase requisition
 Repair order indicator
District Closure
All items on the purchase order item file that are not cancelled or complete for the nominated
district are listed.
Warehouse Closure
All owned stock and consigned stock items on the purchase order item file that are not cancelled or
complete for the nominated district and warehouse are listed.
107
MSR07B - Check for District/Warehouse Closure -

Warehouse Requisitions Report
Report MSR07B displays all requisition items preventing the nominated district or warehouse from
being closed. This includes all items that are not cancelled or complete.
The following details are printed for each stock code:
 Current warehouse
 Requisition number
 Requisition item
 Requisition type (short description)
 Requisition status (short description)
 Requisition authorised status
 Stock code
 Quantity requested
 Total quantity issued
District Closure
All items on the item file that are not either cancelled or complete for the nominated district are
listed.
Warehouse Closure
All issue requisition items on the issue requisition item file that are not cancelled or complete for
the nominated district and warehouse are listed.
108
MSR07C - Check for District Closure - Holdings Report

Report MSR07C displays details on all stock currently held in the district.
 District code and name
 Stock code and description
 Stock classification
 Stock type
 SOH (stock on hand)
 Consign SOH
 Stock in transit
 Consign in transit
 Stock dues in
 Stock dues out
All stock items on the district inventory file that are not cancelled or complete for the nominated
district are listed.
109
MSR07D - Check for District Closure - Accounts

Payable Invoices Report
Report MSR07D displays all invoices that are not paid or cancelled.
 Supplier number invoice number
 Invoice type
 Payment status and description
 Amount paid
 Full period date
 Invoice receipt date
 Due date
 Approved date
 Approval status
All invoice items on the invoice master file for the nominated district are listed.
110
MSR07E - Check for District Closure - Accounts

Receivable Invoices Report
Report MSR07E displays invoices that have not been fully paid.
 Invoice Number
 Invoice Type
 Invoice Status and description
 Payment Status
 Creation Date
 Due Date
 Invoice Date
All invoice items on the accounts receivable invoice master file for the nominated district are
listed.
111
MSR07F - Check for District Closure - Work Orders

Report
Report MSR07F displays all open work orders for the district that are preventing the nominated
district from closing.
The following details are printed for each work order:
 Work order
 Work order type and description
 Originator ID
 Authorised date
 Parent work order
 Work group
 Percentage complete
 Number of tasks
 Number of tasks complete
All work orders on the work order file for the nominated district are listed.
112
MSR07G - Check for District Closure - Equipment

Report
Report MSR07G displays all active equipment still owned by the district.
The following details are printed for each work order:
 Equipment number
 Equipment group ID
 Equipment class
 Equipment status
 Equipment location
 Equipment description
 Plant number
All equipment on the equipment register file for the nominated district is listed.
113
MSR07H - Check District/Warehouse Closure -

Waybills Report
Report MSR07H displays all active waybills where the receiving or forwarding district/warehouse is
the same as the suspended/closed district/warehouse. Any associated manifests also display.
The following details are printed for each waybill:
 Waybill number
 Waybill type
 Waybill status
 Receiving district/warehouse
 Forwarding district/warehouse
 Depot bin location
 Manifest number
 Manifest status
 Required by date
 Items received
 Total number of items
 Waybill description
All waybills on the waybill header file for the nominated district/warehouse are listed.
114
MSR07I - Check for District Closure - Batch Requests

Report
Report MSR07I displays any batch requests that are preventing the nominated district from closing.
The following details are printed for each batch request:
 Program name
 Program report ID
 Request record number
 Defer date
 Request date
 User ID
 Request by
 Distribution code
 Retention days
 Process status
 Start date
 Restart status description
115
MSR07J - Check for District Closure - Scheduled Tasks

Report
Report MSR07J displays any active scheduled tasks for the district.
The following details are printed for each scheduled task:
 Work group and description
 Equipment number/equipment group ID and equipment description
 Work order
 Work order task
 Maintenance type
 Equipment component code
 Component modification code
 Task number
 Sequence number
 Job priority code
 Scheduling indicator and description
 Statistic type
 Scheduled frequency
 Last scheduled statistic
 Last performed statistic
 Last scheduled date
 Last performed date
116
MSR07K - Check for District Closure - Goods in Transit

Report
Report MSR07K displays any goods currently in transit for the district.
117
MSR07L - Check for District/Warehouse Closure -

Purchase Requisitions Report
Report MSR07L displays details of all incomplete purchase requisitions for the district or warehouse.
118
MSR07M - Check for District Closure - Open Incidents

Report
Report MSR07M displays details of all open incidents for a district.
119
MSR07N - Check for District Closure - Logsheets

Report MSR07N displays details of all unprocessed logsheets for a district.
120
MSR07O - Check for District Closure - Projects Report

Report MSR07O displays details all open projects in a district.
121
MSR07P - Check for District Closure - Accounts

Report
Report MSR07P displays details of all general ledger control accounts that have non-zero balances.
122
MSR07Q - Check for District Closure - Employees

Report
Report MSR07Q displays details of all employees that are linked to pay-groups that are in the
district to be closed or are costed against the district to be closed.
123
MSR07R - Check for District Closure - Labour Costing

Report
Report MSR07R displays details of all un-posted labour costing transactions in the district to be
closed.
124
MSR07S - Check for District Closure - Unposted

Transactions Report
Report MSR07S displays details of all un-posted financial transactions in the district to be closed.
125
MSR07T - Check for Supply Customer Closure -

Holdings Report
Report MSR07T displays details of all holdings for the supply customer account to be closed.
126
MSR07U - Check for Supply Customer Closure

Requisitions Report
Report MSR07U displays details of all requisitions due in, loans and recalls for the supply customer
account to be closed.
127
MSR07V - Check for Supply Customer Closure - In

Transit
Report MSR07V displays details of all in transit stock for the supply customer account to be closed.
128
MSR07W - Check for District Closure - Cyclic Requests

Report
Report MSR07W displays any cyclic requests that are created in the suspended district.
129
MSR07X - Check for District Closure - Repair Requests

Report
Report MSR07X displays details of all un-actioned repair requests in the district to be closed.
130
MSR07Y - Check for Warehouse Closure - Holdings

Report
Report MSR07Y reports on all stock currently held in the warehouse.
131
MSR081 - Batch Request Parameters Report

The MSR081 - Batch Request Parameters report displays request parameters for the specified
program/report.
report:
Program Name Enter a range of program names to restrict the selection of program/reports
Range: From/To returned. Leave From blank to report from the first program. Leave To range
blank to report to the last program.
132
MSR083 - Cyclical Request Report

The MSR083 - Cyclical Request Report lists records on the Cyclical Request file (MSF082). This
report lists details for selected cyclical requests.
A program or range of programs can be selected. The range can be filtered by a range of defer
dates.
this report:
Program Name Range: Enter a range of program names to restrict the selection. Leave 'From'
From/To blank to report from the first program. Leave 'To' range blank to report to
the last program.
Defer Date Range: Enter a range of defer dates to restrict the selection. Leave the 'From'
From/To blank to report from the first request. Leave the 'To' blank to report to
the last request.
133
MSR09A - Work File Listing

Report MSR09A displays details of records stored on the work file. This report is for use by the
Software Administration only. Each user number displays.
This report can be generated at any time. The key of each record on file is shown.
The data contents of each record on file are also optionally shown.
this report:
Detail Required Enter Y to select the Detail mode. The data contents of each record on
file are printed.
Report COMMAREA Enter the COMMAREA level threshold. This number represents the level
Usage Threshold above which statistics will be gathered for COMMAREA shuffling.
134
MSBXPO - Purchase Order Print XML

Purpose
Report MSBXPO is an XML-encoded listing of the Purchase Orders Print report (MSRPOP), and/or
the Purchase Orders Fax report (MSRPOF), for a given run number. It builds business-to-business
purchase orders and picking slips.
For each purchasing officer, the purchase orders 'print' in purchase order number within the
supplier, at the Purchasing Officer's printer.
The data relating to each purchase order is prefixed and suffixed by XML tags. The output from
MSBXPO is used in conjunction with a Microsoft® Word template (msrxpo.dot) to produce a
formatted document.
If the Repairable Item Management module (3390) is installed, a Repair Order may also be printed,
along with Repairs Required.
File Dependency
Main File Lookup File Auxiliary File
MSF061 MSF010 MSF221
MSF096 MSF39K
MSF100 MSF39L
MSF200 MSFX05
MSF220 MSS110
MSF231
MSFX05

This report is sorted by Purchase Order Number, within supplier, within purchasing officer.
Frequency
As required.

If a printer was nominated during the request process, purchase orders are printed on that printer.
Otherwise, they are printed on the Purchasing Officer's default LAN printer (setup on the Printers
tab on the MSE81S - Update Personnel Workbench screen), or on the Default Printer for the report
(setup by the Maintain Parameters for Forms Management Module program MSO01D).
Selecting the Fax Device

If the Purchase Orders are to be faxed, the output is directed to the Fax Server queue name, as
defined for the MSBXPO report, through MSO01D - Maintain Output Designer Parameters.
Note: Purchase orders are printed when the Order Medium is P. Otherwise, if the P/O Order Medium
is F, the output will be faxed.
Report Information
Each purchase order starts on a new page.
135
XML Tags
The following XML tags and related data are available to the Word template, and fields with an '*'
are currently used by the Word template.
XML Tag Description
<FAX_INFO> * Faxing Information. When the report is to be

FAXed, this tag will consist of several lines of
Faxing Commands, containing commands as
configured in the Maintain Output Designer
Parameters program MSO01D.
NOTE: If the expediting letter is NOT being
faxed, the '<FAX_INFO>' Tag will be empty.
<MSF220_PO_NO> * Purchase Order Number
<MSF220_PO_TYPE>
<MSF220_SUPPLIER_NO>
<MSF220_PURCH_OFFICER>
<MSF220_STATUS_220>
<MSF220_SUPPLY_CUST_ID>
<MSF220_REVSD_ORDER_DATE>
<MSF220_REVSD_CRT_DATE>
<MSF220_PO_XMIT_VERSION>
<MSF220_FREIGHT_CODE>
<MSF220_DELIV_LOCATION>
<MSF220_LIVE_CONF_IND>
<MSF220_PO_MEDIUM_IND>
<MSF220_LAST_PRT_RUNNO>
<MSF220_CURRENCY_TYPE>
<MSF220_ORDER_DATE> Purchase Order Date
<MSF220_PO_VERSION> * Purchase Order Version
<MSF220_CHANGE_COUNT>
<MSF220_NO_OF_ITEMS>
<MSF220_COMPLETE_ITEMS>
<MSF220_OWNED_STK_IND>
136
<MSF220_CON_STOCK_IND>
<MSF220_SERV_ITEM_IND>
<MSF220_PREQ_ITEM_IND>
<MSF220_FREL_ITEM_IND>
<MSF220_EDI_ACK_RCVD>
<MSF220_EDI_ACK_DATE>
<MSF220_AUTHSD_BY>
<MSF220_AUTHSD_POSITION>
<MSF220_AUTHSD_DATE>
<MSF220_AUTHSD_TIME>
<MSF220_AUTHSD_STATUS>
<MSF220_RESTRICT_POS>
<MSF220_RESTRICT_RULE>
<MSF220_CREATION_DATE>
<MSF220_CREATION_TIME>
<MSF220_CREATION_USER>
<MSF220_LAST_RCPT_NO>
<MSF220_ORIGIN_CODE>
<MSF220_COMPLETED_DATE>
<MSF220_AUTHSD_TOT_AMT>
<MSF220_AUTHSD_ITM_AMT>
<MSF220_FMS_REQ_IND>
<MSF220_NPV_INDEX_CODE>
<MSF220_NPV_PAY_DATE>
<MSF220_NPV_PAY_DAYS>
<MSF220_ORDER_ORIG>
<MSF220_GLOBAL_PO_IND>
<MSF220_MULTI_DST_RCPT_FLG>
<MSF200_SUP_STATUS>
137
<MSF200_SUPPLIER_NAME> * Vendor Name
<MSF200_ORDER_ADDR_1> *
<MSF200_ORDER_ZIP>
<MSF200_ORDER_PCODE> *
<MSF200_ORDER_PHONE>
<MSF200_ORDER_CONTACT>
<MSF200_ORDER_STATE> *
<MSF200_ORDER_FAX_NO>
<MSF200_ORDER_TLX_NAME>
<MSF200_ORDER_TLX_NO>
<MSF200_FORMATTED_ORDER_ADDRESS> * Consists of the Supplier's order address, state

and post code.
<MSF200_PAYMENT_NAME>
<MSF200_PAYMENT_ADDR_1>
<MSF200_PAYMENT_ZIP>
<MSF200_PAYMENT_PCODE>
<MSF200_PAYMENT_PHONE>
<MSF200_PAYMENT_CTACT>
<MSF200_PAYMENT_STATE>
<MSF200_PAY_FAX_NO>
<MSF200_PAY_TLX_NAME>
<MSF200_PAY_TLX_NO>
<MSF200_PAYMENT_LINK>
<MSF200_RETURNS_NAME>
<MSF200_RETURNS_ADDR_1>
138
<MSF200_RETURNS_ZIP>
<MSF200_RETURNS_PCODE>
<MSF200_RETURNS_PHONE>
<MSF200_RETURNS_CTACT>
<MSF200_RETURNS_STATE>
<MSF200_RETURNS_FAX_NO>
<MSF200_RETS_TLX_NAME>
<MSF200_RETS_TLX_NO>
<MSF200_CLOSE_XMAS>
<MSF200_NO_ITEM_ORDER>
<MSF200_FRT_IN_DISC>
<MSF200_SEP_CHEQUE>
<MSF200_LINKED_SUPP_NO>
<MSF200_LINKED_CUST_NO>
<MSF200_COUNTRY_CODE>
<MSF200_SUP_TYPE1>
<MSF200_SUP_TYPE2>
<MSF200_SUP_TYPE3>
<MSF200_SUP_TYPE4>
<MSF200_SUP_TYPE5>
<MSF200_SUP_TYPE6>
<MSF200_PAY_CONTRA>
<MSF200_CURRENCY_TYPE>
<MSF200_LAST_MOD_DATE>
<MSF200_LAST_MOD_TIME>
<MSF200_LAST_MOD_USER>
<MSF200_CREATION_DATE>
139
<MSF200_COMMODITY_TY1>
<MSF200_EMAIL_ADDRESS>
<RES_ORDER_CONTACT> * Attention at Vendor, either PO Header

Attention Narrative (if not blank) or
MSF200_ORDER_CONTACT.
<MSF000_DSTRCT_ADDR_1>
<MSF000_DSTRCT_ZIP_CODE>
<MSF000_DSTRCT_PCODE>
<MSF000_DSTRCT_PHONE> *
<MSF000_DSTRCT_STATE>
<MSF000_DSTRCT_FAX_NO> *
<MSF000_DSTRCT_TLX_NAME>
<MSF000_DSTRCT_TLX_NO>
<MSF000_DSTRCT_ACN_NO> *
<MSF002_DISTRICT_NAME> *
<MSF000_FORMATTED_DISTRICT_ADDRESS> Consists of the District name, address, and

phone number.
<MSF010_DELIV_LOCATION> * Delivery Location description
<MSF010_FRGHT_CODE> * Freight Code description
<EMP_FORMATTED_NAME> * Purchasing Officer
<MSF810_SURNAME>
<MSF810_BARCODE>
<MSF810_FIRST_NAME>
140
<MSF810_FIRST_INITIAL>
<MSF810_PREF_NAME>
<MSF810_NAME_TITLE>
<MSF810_SECOND_NAME>
<MSF810_SECOND_INITIAL>
<MSF810_RES_ADDRESS_1>
<MSF810_RES_STATE>
<MSF810_RES_ZIPCODE>
<MSF810_RES_POSTCODE>
<MSF810_POST_ADDRESS_1>
<MSF810_POST_STATE>
<MSF810_POST_ZIPCODE>
<MSF810_POST_POSTCODE>
<MSF810_WORK_PHONE_NO> * Purchasing Officer's telephone no.
<MSF810_WORK_EXT>
<MSF810_FAX_NO>
<MSF810_MOBILE_NO>
<MSF810_EMAIL_ADDRESS>
<MSF810_PRINTER_ID_5>
<group type="po_change_txt"> * This group is only available if the order has

been changed.
<TXT_CHANGE_ORDER> * Text to indicate change order: 'This is a Change

Order and only items changed from the original
are printed'
<group type= "po_header_narrative"> * Group data for PO Header Narrative if it exists.
<PO_HEADER_NARRATIVE> * Purchase Order Header Narrative
141
<group type= "global_supp_comments_1"> * Group data for first Global Supplier Comments
if it exists.
<GLOBAL_SUPPLIER_COMMENTS_1> * Global Supplier Comments.
"global_supp_comments_2"> * Group data for second Global Supplier

Comments if it exists.
"global_supp_comments_3"> * Group data for third Global Supplier Comments

if it exists.
"global_supp_comments_4"> * Group data for forth Global Supplier Comments

if it exists.
"global_supp_comments_5"> * Group data for fifth Global Supplier Comments

if it exists.
"district_supp_comments_1"> * Group data for first District Supplier Comments

if it exists.
<DISTRICT_SUPPLIER_COMMENTS_1> * District Supplier Comments.
"district_supp_comments_2"> * Group data for second District Supplier

"district_supp_comments_3"> * Group data for third District Supplier

"district_supp_comments_4"> * Group data for forth District Supplier

"district_supp_comments_5"> * Group data for fifth District Supplier Comments

if it exists.
<po_items> * Repeating Data for PO Items
<group type="po_cancel_txt"> * This group is only available if the current item

is cancelled.
<TXT_CANCELLED_ITEM> * Text to indicate cancelled item: '* CANCELLED

ITEM - DO NOT INVOICE *'
142
<group type="po_item"> * Group of data for each item in the Purchase

Order Item table.
<MSF221_PO_ITEM_NO> * Purchase Order Item Number
<MSF221_CURR_QTY_P> * Quantity
<MSF221_STOCK_CODE>
<ITEM_NAME>
<ITEM_DESC_LINE_1>
<ITEM_DESC_LINE_2>
<ITEM_DESC_LINE_3>
<ITEM_DESC_LINE_4>
<ITEM_EXTENDED_DESC>
<FORMATTED_ITEM_DESC> * Consists of PO Item description lines 1 thru 4

and item extended description.
<MSF221_DISCOUNT_A> * Discount or Surcharge taken
<MSF221_DISCOUNT_B> * Additional Discount/Surcharge
<MSF221_SETTLE_PC_A> * Settlement Discount-1 percent
<MSF221_SETTLE_DAYS_A> * Days Discount-1 available
<MSF221_SETTLE_PC_B> * Settlement Discount-2 percent
<MSF221_SETTLE_DAYS_B> * Days Discount-2 available
<MSF221_CURR_NET_PR_P> * Unit Price
<MSF221_UNIT_OF_PURCH> * UOM
<MSF221_DUE_DATE> * Due Date
<MSF221_CALC_ITEM_TOTAL> * Purchase Order Item Total
<SUPPLIER_1> * First Manufacturer/Supplier
<PART_NO_1> * First Part Number
<group type= "po_item_extra_part_no"> * Group of data for extra Supplier and Part
Numbers.
<SUPPLIER_2> * Second Manufacturer/Supplier
<PART_NO_2> * Second Part Number
<SUPPLIER_3> * Third Manufacturer/Supplier
143
<PART_NO_3> * Third Part Number
<group type="po_item_hazardous"> * Group of data for hazardous goods.
<HAZARDOUS_LITERAL> * '*** WARNING HAZARDOUS GOODS ***'
<HAZARDOUS_MATERIAL_CODE> * Stock Code Hazardous Material Code
<HAZARDOUS_DESC> * Hazardous Material Code Description
<group type= "po_item_un_transport"> * Group of data for UN transport.
<UN_TRANSPORT_LITERAL> * 'UN Transport Code :'
<UN_TRANSPORT_CODE> * Stock Code UN Transport Code
<group type="po_item_fpa"> * Group of data for an FPA.
<FPA_LITERAL> * 'Forward Purchase Agreement :'
<FPA_ID> *
<group type= "po_item_additional_disc"> * Group of data for an additional discount or

surcharge.
<ADDITIONAL_DISCOUNT> * 'Additional Discount :' or 'Additional Surcharge

:'
<group type= "po_item_settle_disc_a"> * Group of data for settlement discount A.
<SETTLEMENT_DISC_A> * 'Discount' '%' 'within' 'days'
<group type= "po_item_settle_disc_b"> * Group of data for settlement discount B.
<SETTLEMENT_DISC_B> * 'Discount' '%' 'within' 'days'
<group type= "po_item_repair_data"> * Group of data for all the Repairs required by a
PO Item. Consists of Repair Task
Description/Quantity/Amount and Repair Sub-
Task Description/Quantity/Amount.
<group type= "po_item_narrative"> * Group data for PO Item Narrative if it exists.
<PO_ITEM_NARRATIVE> * Purchase Order Item Narrative.
<group type= "global_sc_comments_1"> * Group data for first Global Stock Code
<GLOBAL_STOCK_CODE_COMMENTS_1> * Global Stock Code Comments
<group type= "global_sc_comments_2"> * Group data for second Global Stock Code
<GLOBAL_STOCK_CODE_COMMENTS_2> * Global Stock Code Comments.
<group type= "global_sc_comments_3"> * Group data for third Global Stock Code
144
<group type= "global_sc_comments_4"> * Group data for fourth Global Stock Code
<group type= "global_sc_comments_5"> * Group data for fifth Global Stock Code
<group type= "district_sc_comments_1"> * Group data for first District Stock Code
<DISTRICT_STOCK_CODE_COMMENTS_1> * District Stock Code Comments.
<group type= "district_sc_comments_2"> * Group data for second District Stock Code
<group type= "district_sc_comments_3"> * Group data for third District Stock Code
<group type= "district_sc_comments_4"> * Group data for forth District Stock Code
<group type= "district_sc_comments_5"> * Group data for fifth District Stock Code
<group type= "global_sc_supp_comments_1"> * Group data for first Global Stock Code Supplier
<GLOBAL_SC_SUPP_COMMENTS_1> * Global Stock Code Supplier Comments.
<group type= "global_sc_supp_comments_2"> * Group data for second Global Stock Code
Supplier Comments if it exists.
<group type= "global_sc_supp_comments_3"> * Group data for third Global Stock Code
<group type= "global_sc_supp_comments_4"> * Group data for forth Global Stock Code
145
<group type= "global_sc_supp_comments_5"> * Group data for fifth Global Stock Code Supplier
<group type= "district_sc_supp_comments_1"> * Group data for first District Stock Code
<DISTRICT_SC_SUPP_COMMENTS_1> * District Stock Code Supplier Comments
<group type= "district_sc_supp_comments_2"> * Group data for second District Stock Code
<group type= "district_sc_supp_comments_3"> * Group data for third District Stock Code
<group type= "district_sc_supp_comments_4"> * Group data for forth District Stock Code
<group type= "district_sc_supp_comments_5"> * Group data for fifth District Stock Code
<DISTRICT_SC_SUPP_COMMENTS_5> * District Stock Code Supplier Comments. Up to

20 occurrences of PO Item Standard Clause
numbers.
<PO_ITEM_CLAUSE_1> PO Item Standard Clause Number.
<PO_ITEM_CLAUSE_2>
<PO_ITEM_CLAUSE_3>
<PO_ITEM_CLAUSE_4>
<PO_ITEM_CLAUSE_5>
<PO_ITEM_CLAUSE_6>
<PO_ITEM_CLAUSE_7>
<PO_ITEM_CLAUSE_8>
<PO_ITEM_CLAUSE_9>
<PO_ITEM_CLAUSE_10>
<PO_ITEM_CLAUSE_11>
<PO_ITEM_CLAUSE_12>
<PO_ITEM_CLAUSE_13>
146
<PO_ITEM_CLAUSE_14>
<PO_ITEM_CLAUSE_15>
<PO_ITEM_CLAUSE_16>
<PO_ITEM_CLAUSE_17>
<PO_ITEM_CLAUSE_18>
<PO_ITEM_CLAUSE_19>
<PO_ITEM_CLAUSE_20>
<group type= "po_item_clause_text"> * Group of data for up to 20 PO Item Standard

Clauses.
<PO_ITEM_CLAUSE_TEXT> * PO Item Standard Clause Text, may contain up

to 20 clauses.
<group type="po_confirm_txt"> * This group is only available if the current order

is a confirmation.
<TXT_CONFIRMATION_ORDER> * Text to indicate confirmation: '*

CONFIRMATION ORDER *' '* DO NOT SUPPLY
AGAINST THIS DOCUMENT *'
<group type="po_consign_txt"> * This group is only available if the current item

is a consignment.
<TXT_CONSIGNMENT_ORDER> * Text to indicate consignment: '* CONSIGNMENT

STOCK - DO NOT INVOICE *'
<group type= "po_footer_narrative"> * Group data for PO Footer Narrative if it exists.
<PO_FOOTER_NARRATIVE> * Purchase Order Footer Narrative.
<group type= "po_attach_narrative"> * Group data for PO Attachment Narrative if it

exists.
<PO_ATTACH_NARRATIVE> * Purchase Order Attachment Narrative.
<ORDER_TOTAL> Purchase Order Total

To print this report, a substitute request must be set up on the SR table file (to redirect MSRPOP to
MSBXPO). This may be specific to an employee, or available at district or global level. The original
request for the Purchase Order Print report (MSRPOPA), is generated through MSB222.
To automatically fax this report, a substitute request must be set up on the SR table file (to
redirect MSRPOF to MSBXPO). This may be specific to an employee, or available at district or global
level. The original request for the Purchase Order Fax report (MSRPOFA) is generated through
MSB222.
147
MSBXRQ - Request for Quotation

Report MSBXRQ is an XML encoded listing of the MSR253A - Request for Quotation - FPA report or
MSR25HA - Request for Quotation - Quote report.
The program is run in two separate modes:
1. Build the business to business (B2B) FPAs and RFQs - When run in this mode, it will generate the
B2B FPAs and RFQs for those suppliers that are B2B enabled. This program will process RFQs and
FPAs for suppliers that are flagged for B2B processing by an associated value of 'Y' on the 'SXML'
table file, and output the details to the Batch Interface Messaging File (MSF012).
2. Housekeeping - When run in this mode, the batch program manages the clean up of successfully
transmitted FPAs and RFQs from the Batch Interface File (MSF012). It can also be used to change
the processing status of individual or multiple FPAs and RFQs.
The data relating to the Request for Quotation reports are prefixed and suffixed by XML tags. The
output from MSBXRQ is used in conjunction with a Microsoft Word template (msrxrq.dot) to produce
a formatted document.
File Dependency
MSF250 MSF253
MSF251 MSF231
MSF096 MSF096
MSF010 MSF110
MSF100 MSF39A
MSFX05 MSF39B

The report is produced in FPA item sequence. The RFQ for each supplier is started on a new page.
Frequency
As required.

If a Printer was nominated during the request process, RFQ's are printed on that printer. Otherwise,
they are printed on the default printer for the report (setup by the Maintain Ellipse/Output Designer
- Word Reporting Parameters program MSO01D).
Selecting the Fax Device

If the FAX Quotation reports have been selected, the output will be 'directed' to the 'Fax Server'
queue name, as defined for the MSBXRQ report, via 'Maintain Output Designer Parameters' program -
MSO01D.
XML Tags
The following XML tags and related data are available to the Word template, and fields with a '*' are
currently used by the Word template:
148
XML Tag Description
<FAX_INFO> * Faxing Information. When the report is to be FAXed,

this tag will consist of several lines of Faxing
Commands, containing commands as configured in
the Maintain Output Designer Parameters program
MSO01D. NOTE: If the expediting letter is NOT being
faxed, the '<FAX_INFO>' Tag will be empty.
<FPA_TYPE> * 'FPA' or 'Repair' or 'Quote'
<FPA_NUMBER> * Forward Purchasing Agreement Group Number or

Repair Agreement Group Number or Quote Number.
<FPA_DESC> * Description of FPA/Repair/Quote
<MSF250_QUOTE_CLS_DATE> * Closing date for quotes
<FORMATTED_SUPP_ADDR> * Consists of Supplier Name and Address
<MSF253_SUPPLIER_NO> Supplier Number
<group type="fpa_header_text"> * Group of data for FPA/Repair/Quote Header Text if

it exists.
<FPA_HEADING_LIT> * 'Quotation Instructions/Terms and Conditions:'
<FPA_HEADING> * FPA/Repair/Quotation Header Text
<group type="fpa_supplier_text"> * Group of data for FPA/Repair/Quote Supplier Text if

it exists.
<FPA_SUPPLIER> * FPA/Repair/Quotation Supplier RFQ Text
<PURCH_OFF_NAME> * Formatted Purchasing Officer name
<MSF810_WORK_PHONE_NO> * Purchasing Officer Telephone Number
<MSF810_WORK_FAX_NO> * Facsimile Number
<MSF810_EMAIL_ADDRESS> * Email Address
<header_clauses> * Repeating Data for FPA Header Clauses
<group type="header_clause_lit"> * Group of data for Header Clause literal
<HEADER_CLAUSE_LIT> * 'Clauses Applying:'
<group type="header_clause"> * Group of data for each FPA Header clause found, up
to 20 occurrences.
<CLAUSE_NUMBER> Standard Clause Number
<CLAUSE_TEXT> * Standard Clause text
<fpa_items> * Repeating Data for FPA Items
149
<group type="fpa_item"> * Group of data for each item in the

FPA/Repair/Quote Item table.
<MSF100_ITEM_NAME> * Item Name
<MSF100_DESC_LINE_1> First line of item description
<MSF100_DESC_LINE_2> Second line of item description
<MSF100_DESC_LINE_3> Third line of item description
<MSF100_DESC_LINE_4> Fourth line of item description
<FORMATTED_ITEM_DESC> * Consists of Item Description lines.
<STOCK_DESC> * Stock Code extended description
<MSF251_FPA_ITEM_NO> * FPA/Repair/Quotation Item Number
<MSF251_STOCK_CODE> * Stock Code
<group type="hazardous_warning"> * Group of data for hazardous goods.
<MSF100_HAZARD_MAT> * Hazardous Material Code
<HAZARD_MAT_DESC> * Hazardous Material Code description
<group type="un_transport"> * Group of data for UN transport.
<MSF100_UN_TRANSP_CODE> * United Nations Transportation code
<group type="fpa_item_data"> * Group of data for RFQ Item.
<MSF251_DSTRCT_CODE> * District Code
<MNEMONIC_1> * Manufacturer's Mnemonic
<PART_NO_1> * Manufacturer's Part Number
<PREF_PART_IND_1> * Part Number Preference Indicator
<MSF100_UNIT_OF_ISSUE> * Standard Unit of Issue
<QTY_TEND_UOI> * Quantity Tendered (UOI)
<MSF251_FREIGHT_CODE> * Freight Code
<MSF251_DELIV_LOCATION> * Delivery Location
<NORM_ORD_QTY> * Normal Order Quantity (UOI)
<group type="mnemonic_2"> * Group of data for second Manufacturers Part

Number if it exists.
150
<group type="mnemonic_3"> * Group of data for third Manufacturers Part Number

if it exists.
<group type="mnemonic_4"> * Group of data for forth Manufacturers Part Number

if it exists.
<group type="mnemonic_5"> * Group of data for fifth Manufacturers Part Number

if it exists.
<group type="mnemonic_6"> * Group of data for sixth Manufacturers Part Number

if it exists.
<group type="mnemonic_7"> * Group of data for seventh Manufacturers Part

Number if it exists.
<group type="mnemonic_8"> * Group of data for eighth Manufacturers Part Number

if it exists.
151
<group type="mnemonic_9"> * Group of data for ninth Manufacturers Part Number

if it exists.
<group type="mnemonic_10"> * Group of data for tenth Manufacturers Part Number

if it exists.
<group type="fpa_item_text"> * Group of data for FPA/Repair/Quote Item Text if it

exists.
<FPA_ITEM_TEXT> * FPA/Repair/Quotation Item Text Up to 5 Required

District Codes if they exist.
<group type="required_dstrct_1"> * Group of data Required District 1
<REQD_DSTRCT_LIT> * 'Required for Districts'
<REQD_DSTRCT_1> *
<REQD_DSTRCT_2> *
<REQD_DSTRCT_3> *
<REQD_DSTRCT_4> *
<REQD_DSTRCT_5> *
<group type="repair_data"> * Group of data for all the Repairs required by a

Repair Agreement Item. Consists of Repair Task
Description/Quantity/Amount and Repair Sub-Task
Description/Quantity/Amount. Up to 20 occurrences
of Item Clause
<ITEM_CLAUSE_NO_1> Standard Clause Number
<ITEM_CLAUSE_NO_2>
<ITEM_CLAUSE_NO_3>
152
<ITEM_CLAUSE_NO_4>
<ITEM_CLAUSE_NO_5>
<ITEM_CLAUSE_NO_6>
<ITEM_CLAUSE_NO_7>
<ITEM_CLAUSE_NO_8>
<ITEM_CLAUSE_NO_9>
<ITEM_CLAUSE_NO_10>
<ITEM_CLAUSE_NO_11>
<ITEM_CLAUSE_NO_12>
<ITEM_CLAUSE_NO_13>
<ITEM_CLAUSE_NO_14>
<ITEM_CLAUSE_NO_15>
<ITEM_CLAUSE_NO_16>
<ITEM_CLAUSE_NO_17>
<ITEM_CLAUSE_NO_18>
<ITEM_CLAUSE_NO_19>
<ITEM_CLAUSE_NO_20>
<group type="item_clause"> Group of data to indicate that FPA Item clauses

exist.
<ITEM_CLAUSE_LIT> 'Clauses Applying:'
<ITEM_CLAUSE_TEXT> Display up to 20 FPA Item Clauses Standard text.
<TOTAL_ITEMS> * Total number of items

This report is a substitute for the PRINTed version of the MSR253A report and/or the MSR25HA
report. To select MSBXRQ, substitute request(s) must be set up on the SR table file; that is, create
substitute requests to redirect 'MSR253' to 'MSBXRQ', and 'MSR25H' to 'MSBXRQ', as required.
Similarly, to use MSBXRQ to generate the MS Word formatted listings of the FAX versions of the
Quotation reports, create substitute requests on the SR table file to redirect MSRQFF to MSBXRQ,
and MSRQQF to MSBXRQ, as required.
When the Update FPA for RFQ program (MSB25R) is requested, the report(s) are automatically
initiated.
153
MSRXDRA - Discrepancy Report Letter

Purpose
Report MSRXDRA is an XML encoded listing of all discrepancy reports for the specified Print Run
Number. The discrepancy report data is prefixed and suffixed by XML tags. The output of this report
is used in conjunction with a Microsoft Word template to produce a formatted discrepancy letter.
File Dependency
MSF010
MSF096
MSF110
MSF150
MSF151
MSF200
MSF221
MSF231
MSF245
MSFX05

Discrepancy reports are sorted in report order within Supplier/Waybill Forwarding District and
Raised By Person.
Frequency
As Required.

If a printer was nominated during the request process, discrepancy reports are printed on that
printer. Otherwise, they are printed on the Raised By Person's default LAN printer (setup on the
Printers tab on the MSE81S - Update Personnel Workbench screen), or on the default printer for the
report (setup by the Maintain Ellipse/Output Designer - Word Reporting Parameters program
MSO01D).
Report Information
Each discrepancy report is printed on a new page.
The following XML tags and related data are available to the Word template, and fields with a '*' are
currently used by the Word template:
XML Tag Description
<MSF000_DSTRCT_NAME> * Forwarding District
154
<MSF061_DSTRCT_CODE_3P>
<MSF061_PRINT_RUN_NO_3P>
<MSF061_MEDIUM_3P> The medium for the report. Valid values are 'P'
(Printer).
<MSF061_DR_NO_DR> * Discrepancy report number
<MSF200_SUPPLIER_NAME> * Supplier company name
<MSF200_ORDER_ADDR_1> 1st line of address for orders
<MSF200_ORDER_ADDR_2> 2nd line of address for orders
<MSF200_ORDER_ADDR_3> 3rd line of address for orders
<MSF200_ORDER_ZIP> Order Zip code
<MSF200_ORDER_PHONE> Telephone number for orders
<MSF200_ORDER_STATE> Order state code for supplier
<MSF200_RETURNS_NAME> Name for returns
<MSF200_RETURNS_ADDR_1> 1st line of address for returns
<MSF200_RETURNS_ADDR_2> 2nd line of address for returns
<MSF200_RETURNS_ADDR_3> 3rd line of address for returns
<MSF200_RETURNS_ZIP> Returns Zip code
<MSF200_RETURNS_PHONE> Telephone number for returns
<MSF200_RETURNS_STATE> Returns state code for supplier
<FORMATTED_RETURN_NAME> * Depending on the type of discrepancy report this will

consist of either the Forwarding District name and
Warehouse name or the Supplier's name, return
address and phone number.
<MSF100_ITEM_NAME> * Stock Code Item Name
<MSF150_WAYBILL_DESC> * Waybill Description
<MSF150_RECEIPT_IND>
<MSF245_SUPP_TYPE> The type of discrepancy report. Valid values are 'S'

(Supplier) or 'W' (Waybill)
<MSF245_DSTRCT_WH> The district warehouse
<MSF245_FORWARD_DSTRCT>
<MSF245_FORWARD_WH>
155
<MSF245_SUPPLIER_NO>
<MSF245_RAISED_BY>
<MSF245_RAISED_DATE>
<MSF245_SHIP_CARRIER> * The method used for returning the item
<MSF245_SHIP_REF> * A reference for the item's return
<MSF245_SHIP_DATE> * The date on which the item was returned
<MSF245_SUPP_CTACT> * The supplier's contact for goods returned
<MSF246_DR_ITEM_NO> * Item number on the discrepancy report
<MSF246_STOCK_CODE> * Stock Code
<MSF246_PO_NO> * Purchase Order number
<MSF246_PO_ITEM_NO> * Purchase Order Item number
<MSF246_WAYBILL_NO> * Waybill number
<MSF246_WAYBILL_ITEM_NO> * Waybill Item number
<MSF246_DISCREP_TYPE_1>
<MSF246_DISCREP_QTY> * Discrepancy Quantity
<MSF246_HOLD_PAYMENTS_IND> * Indicates payments are to be withheld
<MSF246_DR_DESC> * Discrepancy description
Headings for Purchase Order Discrepancy:
<ITEM_HEADING_1> * 'Item'
<ITEM_HEADING_2> * 'Purch Order'
<ITEM_HEADING_4> * 'Item Description'
<ITEM_HEADING_5> * 'Quantity'
<ITEM_HEADING_6> * ''
156
<ITEM_HEADING_7> * ''
<ITEM_HEADING_8> * 'Mnemonic'
<ITEM_HEADING_9> * 'Part Number'
Headings for Waybill Discrepancy:
<ITEM_HEADING_2> * 'Waybill'
<ITEM_HEADING_4> * 'Description'
<ITEM_HEADING_5> * 'Quantity'
<ITEM_HEADING_6> * 'Type'
<ITEM_HEADING_7> * 'Document'
<ITEM_HEADING_8> * 'Stock Code'
<ITEM_HEADING_9> * 'Item Name'
<discr_items> * Repeating Data for Discrepancy Items.
<group type="discr_item"> * Group of data for each item in the Discrepancy Item
table.
Item values for Purchase Order Discrepancy:
<ITEM_DETAIL_1> * First item for discrepancy table Discrepancy Report

Item Number
<ITEM_DETAIL_2> * Second item for discrepancy table Purchase Order

Number
<ITEM_DETAIL_3> * Third item for discrepancy table Purchase Order Item

Number
<ITEM_DETAIL_4> * Fourth item for discrepancy table Either Stock Code

Item Name or Purchase Requisition Item Description 1
<ITEM_DETAIL_5> * Fifth item for discrepancy table Discrepancy Quantity
<ITEM_DETAIL_6> Sixth item for discrepancy table
<ITEM_DETAIL_7> Seventh item for discrepancy table
<ITEM_DETAIL_8> * Eighth item for discrepancy table Manufacturers

Mnemonic
<ITEM_DETAIL_9> * Ninth (and final) item for discrepancy table

Manufacturers Part Number
157
Item values for Waybill Discrepancy:
<ITEM_DETAIL_1> * First item for discrepancy table Discrepancy Report

Item Number
<ITEM_DETAIL_2> * Second item for discrepancy table Waybill Number
<ITEM_DETAIL_3> * Third item for discrepancy table Waybill Item Number
<ITEM_DETAIL_4> * Fourth item for discrepancy table Waybill Description
<ITEM_DETAIL_5> * Fifth item for discrepancy table Discrepancy Quantity
<ITEM_DETAIL_6> * Sixth item for discrepancy table Waybill Item Type
<ITEM_DETAIL_7> * Seventh item for discrepancy table Waybill Document

Number
<ITEM_DETAIL_8> * Eighth item for discrepancy table Stock Code
<ITEM_DETAIL_9> * Ninth (and final) item for discrepancy table Stock Code
Item Name
<ITEM_STARRED> * Items on which payment is being held pending

completion of the discrepancy will contain an asterix in
this field
<DR_TYPE_1> * Discrepancy type 1 description
<group type="discr_type_3_4"> * Group data to indicate that third and forth discrepancy
types exist.
<group type="discr_type_5_6"> * Group data to indicate that fifth and sixth discrepancy
types exist.
<group type="discr_comment"> * Group data to indicate that discrepancy item

comments exist.
<COMMENT_TEXT> * Text of comments attached to the discrepancy item.
<CLAUSE-IDS> Display up to 20 Clause Numbers for the current

discrepancy item.
<group type="discr_clause"> * Group data to indicate that discrepancy item clauses

exist.
158
<CLAUSE-DATA> * Display up to 20 Clauses Standard Text for the current

discrepancy item.

This report is a substitute for the printed version of the Discrepancy Advices report (MSRDRPA). To
print it, a substitute request must be set up on the SR table file. The report is then requested from
MSO246 or MSB245.
159
MSIXPO - Build PO and PS Interface

Field name Field Length/Type
MSIXPO-KEY-012
MSIXPO-DATA-TYPE PIC X(1).
STD-INTERFACE VALUE 'S'.
CLIENT-INTERFACE VALUE 'C'.
MINCOM-INTERFACE VALUE 'M'.
MSIXPO-KEY-VALUE PIC X(63)
KEY-STRUCTURE REDEFINES MSIXPO-KEY-012.
MSIXPO-DATA-TYPE-2 PIC X(1).
MSIXPO-INTERFACE-ID PIC X(8).
MSIXPO-RECORD-STATUS PIC X(1).
RECORD-READY VALUE 'R'.
IN-PROGRESS VALUE 'I'.
RECORD-COMPLETED VALUE 'C'.
RECORD-ERROR VALUE 'E'.
RECORD-DELETED VALUE 'D'.
DATA-RECORD VALUE ' '.
MSIXPO-DOC-TYPE PIC X(1).
PURCHASE-ORDER-DOC VALUE 'O'.
PICKING-SLIP-DOC VALUE 'V'.
MSIXPO-DOCUMENT-NO PIC X(10).
MSIXPO-SUPPLIER-NO-1 PIC X(6).
MSIXPO-PROC-DATE PIC X(14).
MSIXPO-SEQUENCE-NO-9 PIC 9(6).
MSIXPO-SUB-SEQUENCE-NO-9 PIC 9(2).
160
MSIXPO-PRINT-RUN-NO PIC X(4).
MSIXPO-REST-OF-KEY PIC X(11).
MSIXPO-DATA-AREA.
MSIXPO-REC-TYPE PIC X(6).
MSIXPO-HEADER-RECORD.
MSIXPO-MESSAGE-TYPE PIC X(3).
MSIXPO-PO-NO PIC X(6).
MSIXPO-TRAN-PURPOSE PIC X(2).
MSIXPO-ORDER-TYPE PIC X(1).
MSIXPO-PO-VERSION PIC 9(4).
MSIXPO-NO-OF-ITEMS PIC 9(4).
MSIXPO-ORDER-DATE PIC X(8).
MSIXPO-BUYER-CURR-TYPE PIC X(4).
MSIXPO-ISO-BUYER-CURR PIC X(4).
MSIXPO-ORDER-CURR-TYPE PIC X(4).
MSIXPO-ISO-ORDER-CURR PIC X(4).
MSIXPO-BUYING-RATE PIC +9(8)V9(7).
MSIXPO-AUS-COY-NUM PIC X(14).
MSIXPO-AUS-BUS-NUM PIC X(20).
MSIXPO-DSTRCT-NAME PIC X(40).
MSIXPO-DSTRCT-ADDR-1 PIC X(32).
MSIXPO-DSTRCT-ZIP-CODE PIC X(10).
MSIXPO-DSTRCT-STATE PIC X(20).
MSIXPO-COUNTRY-CODE PIC X(3).
MSIXPO-COUNTRY-DESC PIC X(40).
MSIXPO-DELIV-LOCATION-1 PIC X(4).
MSIXPO-DELIVERY-DESC-1 PIC X(40).
161
MSIXPO-FREIGHT-CODE PIC X(2).
MSIXPO-FREIGHT-CODE-DESC PIC X(40).
MSIXPO-PO-ATTN-DESC PIC X(80).
MSIXPO-PO-CONTACT PIC X(35).
MSIXPO-PO-CONTACT-ID PIC X(10).
MSIXPO-PO-CONTACT-PHONE PIC X(16).
MSIXPO-PO-CONTACT-EMAIL PIC X(40).
MSIXPO-PO-CONTACT-FAX PIC X(16).
MSIXPO-ORIGIN-CODE PIC X(2).
MSIXPO-ORIGIN-DESC PIC X(50).
MSIXPO-LIVE-CONF PIC X(1).
MSIXPO-DELIV-INSTR PIC X(60).
MSIXPO-ANSWER-1 PIC X(4).
MSIXPO-ANSWER-1-DESC PIC X(30).
MSIXPO-MAT-GROUP-CODE PIC X(6).
MSIXPO-DSTRCT-CODE-1 PIC X(4).
MSIXPO-PO-CONTACT-WK-EXT PIC X(6).
MSIXPO-PO-CONTACT-MOBILE PIC X(16).
MSIXPO-PROGRAM-VERSION PIC X(4).
MSIXPO-PROGRAM-REVISION PIC X(4).
MSIXPO-WORKSHOP-IND PIC X(1).
MSIXPO-REST-OF-DATA-1 PIC X(52).
MSIXPO-HEADER-2-RECORD REDEFINES
162
MSIXPO-PO-WHOUSE-ID PIC X(4).
MSIXPO-PO-WHOUSE-DESC PIC X(50).
MSIXPO-PO-PRIORITY-CODE PIC X(4).
MSIXPO-PO-PRIORITY-DESC PIC X(50).
MSIXPO-ADDRESS-2. PIC X(20).
MSIXPO-ADDR-2-TYPE PIC X(40).
MSIXPO-ADDR-2-LINE-1 PIC X(40).
MSIXPO-ADDR-2-ZIP-CODE PIC X(2).
MSIXPO-ADDR-2-STATE-CODE
MSIXPO-ADDR-2-STATE-DESC PIC X(20).
MSIXPO-ADDR-2-COUNTRY-CODE PIC X(3).
MSIXPO-ADDR-2-CONTACT-NAME PIC X(40).
MSIXPO-ADDR-2-CONTACT-ID PIC X(10).
MSIXPO-ADDR-2-CONTACT-PHONE PIC X(16).
MSIXPO-ADDR-2-CONTACT-EMAIL PIC X(40).
MSIXPO-ADDR-2-CONTACT-FAX PIC X(16).
MSIXPO-ADDR-2-CONTACT-WK-EXT PIC X(6).
MSIXPO-ADDRESS-3.
MSIXPO-ADDR-3-TYPE PIC X(20).
MSIXPO-ADDR-3-ZIP-CODE PIC X(10).
MSIXPO-ADDR-3-STATE-CODE PIC X(2).
MSIXPO-ADDR-3-STATE-DESC PIC X(20).
MSIXPO-ADDR-3-COUNTRY-CODE PIC X(3).
MSIXPO-ADDR-3-CONTACT-NAME PIC X(40).
163
MSIXPO-ADDR-3-CONTACT-ID PIC X(10).
MSIXPO-ADDR-3-CONTACT-PHONE PIC X(16).
MSIXPO-ADDR-3-CONTACT-EMAIL PIC X(40).
MSIXPO-ADDR-3-CONTACT-FAX PIC X(16).
MSIXPO-ADDR-3-CONTACT-WK-EXT PIC X(6).
MSIXPO-AUTHBY-CONTACT-NAME PIC X(46).
MSIXPO-AUTHBY-CONTACT-ID PIC X(10).
MSIXPO-AUTHBY-CONTACT-PHONE PIC X(16).
MSIXPO-AUTHBY-CONTACT-EMAIL PIC X(40).
MSIXPO-AUTHBY-CONTACT-FAX PIC X(16).
MSIXPO-AUTHBY-CONTACT-WK-EXT PIC X(6).
MSIXPO-AUTHBY-CONTACT-MOBILE PIC X(16).
MSIXPO-ITEM-1-RECORD REDEFINES
MSIXPO-PO-ITEM-NO PIC 9(4).
MSIXPO-DSTRCT-CODE PIC X(4).
MSIXPO-CURR-QTY-P PIC +9(9)V9(2).
MSIXPO-UNIT-OF-PURCH PIC X(4).
MSIXPO-UOP-DESC PIC X(50).
MSIXPO-ISO-UOP PIC X(4).
MSIXPO-GROSS-PRICE PIC +9(11)V9(4).
MSIXPO-STD-PACK PIC +9(5)
MSIXPO-STOCK-CODE PIC X(9).
MSIXPO-MNEMONIC-1 PIC X(8).
MSIXPO-MANUFACTURER-1 PIC X(40).
MSIXPO-PART-NO-1 PIC X(30).
164
MSIXPO-ITEM-NAME PIC X(40).
MSIXPO-DESC-LINE-1 PIC X(40).
MSIXPO-GROUP-CLASS PIC X(4).
MSIXPO-OTHER-CLASS-CODE PIC X(12).
MSIXPO-OTHER-CLASS-DESC PIC X(24).
MSIXPO-FPA-REC-TYPE PIC X(1).
MSIXPO-FPA-ID PIC X(8).
MSIXPO-FPA-ITEM-NO PIC 9(4).
MSIXPO-DISCOUNT-A PIC +9(3)V9(2).
MSIXPO-DISCOUNT-B PIC +9(3)V9(2).
MSIXPO-SETTLE-PC-A PIC +9(3)V9(2).
MSIXPO-SETTLE-DAYS-A PIC +9(3).
MSIXPO-SETTLE-PC-B PIC +9(3)V9(2).
MSIXPO-SETTLE-DAYS-B PIC +9(3).
MSIXPO-TAX-CODE PIC X(1).
MSIXPO-TAX-CODE-DESC PIC X(15).
MSIXPO-TAX-PERCENT PIC +9(3)V9(2).
MSIXPO-WHEN-TO-APPLY PIC 9(1).
MSIXPO-INCLUDE-TC-IN-PO PIC X(1).
MSIXPO-TAX-TYPE PIC 9(1).
MSIXPO-CURR-DUE-DATE PIC X(8).
MSIXPO-PRICE-EFF-DATE PIC X(8).
MSIXPO-PRICE-EXP-DATE PIC X(8).
165
MSIXPO-PREQ-NO PIC X(6).
MSIXPO-PREQ-ITEM PIC X(4).
MSIXPO-DRAWING-NO PIC X(20).
MSIXPO-ITM-ACTION-REQ PIC X(2).
MSIXPO-CTAX-CODE PIC X(2).
MSIXPO-CTAX-CODE-DESC PIC X(50).
MSIXPO-CTAX-PERCENT PIC +9(3)V9(2).
MSIXPO-INCLUDE-CM-IN-PO PIC X(1).
MSIXPO-PO-WITH-STAX PIC X(1).
MSIXPO-CTAX-TYPE PIC 9(1).
MSIXPO-CTAX-RECOVERY PIC X(1).
MSIXPO-CC-CHECK PIC X(1).
MSIXPO-CTAX-ISS-RCPT PIC 9(1).
MSIXPO-ITEM-TYPE PIC X(1).
MSIXPO-DELIV-LOCATION-2 PIC X(4).
MSIXPO-DELIVERY-DESC-2 PIC X(40).
MSIXPO-ITEM-STATUS PIC X(1).
MSIXPO-REQNR-NAME PIC X(30).
MSIXPO-REQNR-CONTACT-ID PIC X(10).
MSIXPO-REQNR-CONTACT-PHONE PIC X(16).
MSIXPO-REQNR-CONTACT-EMAIL PIC X(40).
MSIXPO-TRACKING-IND PIC X(1).
MSIXPO-REPAIR-IND PIC X(1).
MSIXPO-ITEM-2-RECORD REDEFINES
MSIXPO-REQNR-CONTACT-FAX PIC X(16).
MSIXPO-UN-TRANS-CODE PIC X(4).
MSIXPO-WORK-ORDER PIC X(8).
MSIXPO-PLANT-NO PIC X(30).
166
MSIXPO-COST-CENTRE PIC X(24).
MSIXPO-PROJECT-NO PIC X(8).
MSIXPO-WHOUSE-ID PIC X(4).
MSIXPO-WHOUSE-DESC PIC X(50).
MSIXPO-PRICE-CODE PIC X(2).
MSIXPO-PRICE-CODE-DESC PIC X(40).
MSIXPO-PRICE-ADJUSTMENT PIC X(1).
MSIXPO-PRICE-TBA PIC X(1).
MSIXPO-AUTO-INVOICE PIC X(1).
MSIXPO-PRE-PAYMENT PIC X(1).
MSIXPO-DSTRCT-NAME-3 PIC X(40).
MSIXPO-UN-TRANS-CODE-DESC PIC X(50).
MSIXPO-HAZ-MAT-CODE PIC X(4).
MSIXPO-HAZ-MAT-CODE-DESC PIC X(40).
MSIXPO-TARIFF-CODE PIC X(18).
MSIXPO-TARIFF-CODE-DESC PIC X(40).
MSIXPO-CONC-CAT-CODE PIC X(10).
MSIXPO-CONC-CAT-CODE-DESC PIC X(40).
MSIXPO-PURCH-OFFICER PIC X(46).
MSIXPO-PURCH-OFFICER-ID PIC X(10).
MSIXPO-PURCH-OFFICER-PHONE PIC X(16).
MSIXPO-PURCH-OFFICER-EMAIL PIC X(40).
MSIXPO-PURCH-OFFICER-FAX PIC X(16).
MSIXPO-PURCH-OFFICER-WK-EXT PIC X(6).
MSIXPO-PURCH-OFFICER-MOBILE PIC X(16).
MSIXPO-PRIORITY-CODE PIC X(4).
MSIXPO-PRIORITY-DESC PIC X(50).
MSIXPO-EQUIP-NO-2 PIC X(12).
MSIXPO-SERIAL-NO PIC X(30).
167
MSIXPO-EQUIP-GRP-ID PIC X(12).
MSIXPO-INSPECT-CODE PIC X(2).
MSIXPO-INSPECT-CODE-DESC PIC X(50).
MSIXPO-EXPEDITE-CODE PIC X(2).
MSIXPO-EXPEDITE-CODE-DESC PIC X(50).
MSIXPO-QUOTE PIC X(12).
MSIXPO-CATEG-ID PIC X(30).
MSIXPO-PURCH-TEAM PIC X(10).
MSIXPO-GPA-GROUP-CODE PIC X(12).
MSIXPO-SUPPLIER-RECORD REDEFINES
MSIXPO-SUPPLIER-NO-2 PIC X(6).
MSIXPO-SUPPLIER-NAME PIC X(32).
MSIXPO-ORDER-CONTACT PIC X(35).
MSIXPO-ORDER-PHONE PIC X(16).
MSIXPO-ORDER-ADDR-1 PIC X(32).
MSIXPO-ORDER-ZIP-CODE PIC X(10).
MSIXPO-ORDER-EMAIL PIC X(40).
MSIXPO-ORDER-FAX PIC X(16).
MSIXPO-PAYMENT-CONTACT PIC X(35).
MSIXPO-PAYMENT-PHONE PIC X(16).
MSIXPO-PAYMENT-ADDR-1 PIC X(32).
MSIXPO-PAYMENT-ZIP-CODE PIC X(10).
MSIXPO-PAYMENT-EMAIL PIC X(40).
MSIXPO-PAYMENT-FAX PIC X(16).
168
MSIXPO-SUPP-CNTY-CODE PIC X(3).
MSIXPO-SUPP-CNTY-DESC PIC X(40).
MSIXPO-ACCOUNT-NUMBER PIC X(10).
MSIXPO-GOVT-ID-NO PIC X(14).
MSIXPO-ACK-REQD-SW PIC X(1).
MSIXPO-NO-OF-DAYS-PAY PIC 9(2).
MSIXPO-INV-STMT-IND PIC X(1).
MSIXPO-PAYMENT-METH-IND PIC X(1).
MSIXPO-ORDER-STATE PIC X(2).
MSIXPO-PAYMENT-STATE PIC X(2).
MSIXPO-ITEM-REPAIR-RECORD REDEFINES
MSIXPO-REPR-TASK-NO PIC 9(3).
MSIXPO-REPR-JDESC-CDE PIC X(2).
MSIXPO-REPR-JOB-DESC PIC X(50).
MSIXPO-REPR-TASK-QTY PIC +9(9).
MSIXPO-REPR-TOT-AMT PIC +9(13)V9(2).
MSIXPO-ITEM-SUB-REPAIR-RECORD REDEFINES
MSIXPO-REPR-TASK-NO-S PIC 9(3).
MSIXPO-REPR-JDESC-CDE-S PIC X(2).
MSIXPO-REPR-JOB-DESC-S PIC X(50).
MSIXPO-REPR-TASK-QTY-S PIC +9(9).
MSIXPO-REPR-TOT-AMT-S PIC +9(13)V9(2).
MSIXPO-TEXT-RECORD REDEFINES
MSIXPO-TEXT-LINE-1 PIC X(600).
MSIXPO-STD-CLAUSE-RECORD REDEFINES
MSIXPO-CLAUSE-ID PIC X(20).
MSIXPO-CLAUSE-VER-NO PIC 9(4).
MSIXPO-TEXT-LINE-2 PIC X(600).
169
MSIXPO-PO-ITEM-TRACKING-RECORD REDEFINES
MSIXPO-TRACKING-NO PIC X(30).
170
MSIXRQ - TTT
Field Name Field Length/Type
MSIXRQ-KEY-012.
MSIXRQ-DATA-TYPE PIC X(1).
MSIXRQ-KEY-VALUE PIC X(63).
KEY-STRUCTURE REDEFINES MSIXRQ-KEY-012
MSIXRQ-DATA-TYPE-2 PIC X(1).
MSIXRQ-INTERFACE-ID PIC X(8).
MSIXRQ-RECORD-STATUS PIC X(1).
MSIXRQ-DOC-TYPE PIC X(1).
REQUEST-QUOTE-DOC VALUE 'Q'.
FPA-DOC VALUE 'F'.
MSIXRQ-DOCUMENT-NO PIC X(5).
MSIXRQ-SUPPLIER-NO-1 PIC X(6).
MSIXRQ-PROC-DATE PIC X(14).
MSIXRQ-SEQUENCE-NO-9 PIC 9(6).
MSIXRQ-SUB-SEQUENCE-NO-9 PIC 9(2).
171
MSIXRQ-REST-OF-KEY PIC X(20).
MSIXRQ-DATA-AREA.
MSIXRQ-REC-TYPE PIC X(6)
MSIXRQ-HEADER-RECORD
MSIXRQ-FPA-REC-TYPE PIC X(1).
MSIXRQ-FPA-ID PIC X(5).
MSIXRQ-FPA-DESC PIC X(40).
MSIXRQ-FPA-REF-NO PIC X(20).
MSIXRQ-BUYER-CURR-TYPE PIC X(4).
MSIXRQ-ISO-BUYER-CURR PIC X(4).
MSIXRQ-DSTRCT-ACN-NO-H PIC X(14).
MSIXRQ-DSTRCT-NAME-H PIC X(40).
MSIXRQ-DSTRCT-ADDR-H-1 PIC X(32).
MSIXRQ-DSTRCT-ZIP-CODE-H PIC X(10).
MSIXRQ-DSTRCT-STATE-CODE-H PIC X(2).
MSIXRQ-DSTRCT-STATE-DESC-H PIC X(20).
MSIXRQ-DSTRCT-PHONE PIC X(16).
MSIXRQ-DSTRCT-FAX PIC X(16).
MSIXRQ-COUNTRY-CODE-H PIC X(3).
MSIXRQ-COUNTRY-DESC-H PIC X(40).
MSIXRQ-MSG-ACK-REQD PIC X(1).
MSIXRQ-CONTACT-NAME PIC X(40).
MSIXRQ-CONTACT-ID PIC X(10).
MSIXRQ-CONTACT-PHONE PIC X(16).
MSIXRQ-CONTACT-EMAIL PIC X(40).
MSIXRQ-CONTACT-FAX PIC X(16).
MSIXRQ-CONTACT-WK-EXT PIC X(6).
172
MSIXRQ-CONTACT-MOBILE PIC X(16).
MSIXRQ-QUOTE-CLS-DATE PIC X(8).
MSIXRQ-EFFECTIVE-DATE PIC X(8).
MSIXRQ-EXPIRY-DATE PIC X(8).
MSIXRQ-ISSUE-DATE-TIME PIC X(14).
MSIXRQ-PROGRAM-VERSION PIC X(4).
MSIXRQ-PROGRAM-REVISION PIC X(4).
MSIXRQ-COMPANY-NAME PIC X(40).
MSIXRQ-DSTRCT-CODE-H PIC X(4).
MSIXRQ-MULTI-SUPPLIER PIC X(1).
MSIXRQ-REST-OF-DATA-1 PIC X(361).
MSIXRQ-HEADER-2-RECORD REDEFINES
MSIXRQ-ADDRESS-2.
MSIXRQ-ADDR-2-TYPE PIC X(20).
MSIXRQ-ADDR-2-LINE-1 PIC X(40).
MSIXRQ-ADDR-2-ZIP-CODE PIC X(10).
MSIXRQ-ADDR-2-STATE-CODE PIC X(2).
MSIXRQ-ADDR-2-STATE-DESC PIC X(20).
MSIXRQ-ADDR-2-COUNTRY-CODE PIC X(3)
MSIXRQ-ADDR-2-COUNTRY-DESC PIC X(40).
MSIXRQ-ADDR-2-CONTACT-NAME PIC X(40).
MSIXRQ-ADDR-2-CONTACT-ID PIC X(10).
MSIXRQ-ADDR-2-CONTACT-PHONE PIC X(16).
MSIXRQ-ADDR-2-CONTACT-EMAIL PIC X(40).
MSIXRQ-ADDR-2-CONTACT-FAX PIC X(16).
MSIXRQ-ADDR-2-CONTACT-WK-EXT PIC X(6).
MSIXRQ-ADDRESS-3.
173
MSIXRQ-ADDR-3-TYPE PIC X(20).
MSIXRQ-ADDR-3-ZIP-CODE PIC X(10).
MSIXRQ-ADDR-3-STATE-CODE PIC X(2).
MSIXRQ-ADDR-3-STATE-DESC PIC X(20).
MSIXRQ-ADDR-3-COUNTRY-CODE PIC X(3).
MSIXRQ-ADDR-3-COUNTRY-DESC PIC X(40).
MSIXRQ-ADDR-3-CONTACT-NAME PIC X(40).
MSIXRQ-ADDR-3-CONTACT-ID PIC X(10).
MSIXRQ-ADDR-3-CONTACT-PHONE PIC X(16).
MSIXRQ-ADDR-3-CONTACT-EMAIL PIC X(40).
MSIXRQ-ADDR-3-CONTACT-FAX PIC X(16).
MSIXRQ-ADDR-3-CONTACT-WK-EXT PIC X(6).
MSIXRQ-ITEM-1-RECORD REDEFINES
MSIXRQ-FPA-ITEM-NO PIC 9(4).
MSIXRQ-DSTRCT-CODE PIC X(4).
MSIXRQ-ITEM-TYPE PIC X(1).
MSIXRQ-STOCK-CODE PIC X(9).
MSIXRQ-DSTRCT-NAME-I PIC X(40).
MSIXRQ-DSTRCT-ADDR-I-1 PIC X(32).
MSIXRQ-DSTRCT-ZIP-CODE-I PIC X(10).
MSIXRQ-DSTRCT-STATE-CODE-I PIC X(2).
MSIXRQ-DSTRCT-STATE-DESC-I PIC X(20).
MSIXRQ-DSTRCT-ACN-NO-I PIC X(14).
174
MSIXRQ-COUNTRY-CODE-I PIC X(3).
MSIXRQ-COUNTRY-DESC-I PIC X(40).
MSIXRQ-MNEMONIC-1 PIC X(8).
MSIXRQ-MANUFACTURER-1 PIC X(40).
MSIXRQ-PART-NO-1 PIC X(30).
MSIXRQ-ITEM-NAME PIC X(40).
MSIXRQ-ITEM-DESC-1 PIC X(40).
MSIXRQ-UN-TRANS-CODE PIC X(4).
MSIXRQ-HAZARD-MAT PIC X(4).
MSIXRQ-HAZARD-DESC PIC X(40).
MSIXRQ-UOI PIC X(4).
MSIXRQ-ISO-UOI PIC X(4).
MSIXRQ-UOI-DESC PIC X(40).
MSIXRQ-QTY-TEND-UOI PIC +9(11)V9(2).
MSIXRQ-FREIGHT-CODE PIC X(2).
MSIXRQ-FREIGHT-CODE-DESC PIC X(40).
MSIXRQ-DELIV-LOCATION PIC X(4).
MSIXRQ-DELIV-LOCATION-DESC PIC X(40).
MSIXRQ-NORM-ORD-QTY PIC +9(9).
MSIXRQ-GROUP-CLASS PIC X(4).
175
MSIXRQ-GRP-CLASS-DESC PIC X(25).
MSIXRQ-TARIFF-CODE PIC X(18).
MSIXRQ-TARIFF-CODE-DESC PIC X(40).
MSIXRQ-CONC-CAT-CODE PIC X(10).
MSIXRQ-CONC-CAT-CODE-DESC PIC X(40).
MSIXRQ-TAX-CODE PIC X(1).
MSIXRQ-TAX-CODE-DESC PIC X(15).
MSIXRQ-TAX-PERCENT PIC +9(3)V9(2).
MSIXRQ-WHEN-TO-APPLY PIC 9(1).
MSIXRQ-INCLUDE-TC-IN-PO PIC X(1).
MSIXRQ-TAX-TYPE PIC 9(1).
MSIXRQ-CTAX-CODE PIC X(2).
MSIXRQ-CTAX-CODE-DESC PIC X(50).
MSIXRQ-CTAX-PERCENT PIC +9(3)V9(2).
MSIXRQ-INCLUDE-CM-IN-PO PIC X(1).
MSIXRQ-PO-WITH-STAX PIC X(1).
MSIXRQ-CTAX-TYPE PIC 9(1).
MSIXRQ-CTAX-RECOVERY PIC X(1).
MSIXRQ-CTAX-ISS-RCPT PIC 9(1).
MSIXRQ-PREQ-NO PIC X(6).
MSIXRQ-PREQ-ITEM PIC X(4).
MSIXRQ-ACTIVITY-CTR PIC X(3).
MSIXRQ-PRIORITY-CODE PIC X(4).
MSIXRQ-PRIORITY-DESC PIC X(50).
MSIXRQ-DSTRCT-CURR-TYPE PIC X(4).
MSIXRQ-ISO-DSTRCT-CURR PIC X(4).
MSIXRQ-ITEM-PRICE PIC +9(11)V9(4).
176
MSIXRQ-LEAD-TIME.
MSIXRQ-LEAD-TIME-9 PIC 9(4).
MSIXRQ-CATEG-ID PIC X(30).
MSIXRQ-CATEG-NAME PIC X(100).
MSIXRQ-PART-NO-TABLE OCCURS 11.
MSIXRQ-SUPPLIER-RECORD REDEFINES
MSIXRQ-SUPPLIER-NO-2 PIC X(6).
MSIXRQ-SUPPLIER-NAME PIC X(40).
MSIXRQ-ORDER-CONTACT PIC X(35).
MSIXRQ-ORDER-PHONE PIC X(16).
MSIXRQ-ORDER-EMAIL PIC X(40).
MSIXRQ-ORDER-ADDR-1 PIC X(32).
MSIXRQ-ORDER-ZIP-CODE PIC X(10).
MSIXRQ-ORDER-STATE-CODE PIC X(2).
MSIXRQ-ORDER-STATE-DESC PIC X(20).
MSIXRQ-SUPP-CNTY-CODE PIC X(4).
MSIXRQ-SUPP-CNTY-DESC PIC X(40).
MSIXRQ-ACCOUNT-NUMBER PIC X(10).
MSIXRQ-GOVT-ID-NO PIC X(14).
MSIXRQ-ORDER-FAX PIC X(16).
MSIXRQ-REST-OF-DATA-4 PIC X(579)
177
MSIXRQ-TEXT-RECORD REDEFINES
MSIXRQ-TEXT-LINE-1 PIC X(600).
MSIXRQ-STD-CLAUSE-RECORD REDEFINES
MSIXRQ-CLAUSE-ID PIC X(20).
MSIXRQ-CLAUSE-VER-NO PIC X(4).
MSIXRQ-TEXT-LINE-2 PIC X(600).
178
MSIXRA - TTT
Field Name Field Length/Type
MSIXOS-KEY-012.
MSIXOS-DATA-TYPE PIC X(1).
MSIXOS-KEY-VALUE PIC X(63).
KEY-STRUCTURE REDEFINES MSIXOS-KEY-012.
MSIXOS-DATA-TYPE-2 PIC X(1).
MSIXOS-INTERFACE-ID PIC X(8).
MSIXOS-RECORD-STATUS PIC X(1).
MSIXOS-DOC-TYPE PIC X(1).
ORDER-STAT-REQ-DOC VALUE 'S'.
MSIXOS-XPED-RUN PIC X(3).
MSIXOS-PO-NO-1 PIC X(6).
MSIXOS-SUPPLIER-NO-1 PIC X(6).
MSIXOS-PROC-DATE PIC X(14).
MSIXOS-SEQUENCE-NO-9 PIC 9(6).
MSIXOS-SUB-SEQUENCE-NO-9 PIC 9(2).
179
MSIXOS-PROGRAM-VERSION PIC X(4).
MSIXOS-PROGRAM-REVISION PIC X(4).
MSIXOS-REST-OF-KEY PIC X(8).
MSIXOS-DATA-AREA.
MSIXOS-REC-TYPE PIC X(6).
MSIXOS-HEADER-RECORD.
MSIXOS-XPED-RUN-NO PIC X(3).
MSIXOS-PO-NO PIC X(6).
MSIXOS-TRAN-PURPOSE PIC X(2).
MSIXOS-ORDER-TYPE PIC X(1).
MSIXOS-ORDER-DATE PIC X(8).
MSIXOS-BUYER-CURR-TYPE PIC X(4).
MSIXOS-ISO-BUYER-CURR PIC X(4).
MSIXOS-ORDER-CURR-TYPE PIC X(4).
MSIXOS-ISO-ORDER-CURR PIC X(4).
MSIXOS-BUYING-RATE PIC +9(8)V9(7).
MSIXOS-AUS-COY-NUM PIC X(14).
MSIXOS-AUS-BUS-NUM PIC X(20).
MSIXOS-DSTRCT-CODE PIC X(4).
MSIXOS-DSTRCT-NAME PIC X(40).
MSIXOS-DSTRCT-ADDR-1 PIC X(32).
MSIXOS-DSTRCT-ZIP-CODE PIC X(10).
MSIXOS-DSTRCT-STATE PIC X(2).
MSIXOS-DSTRCT-STATE-DESC PIC X(20).
MSIXOS-COUNTRY-CODE PIC X(3).
MSIXOS-COUNTRY-DESC PIC X(40).
MSIXOS-PO-CONTACT PIC X(35).
180
MSIXOS-PO-CONTACT-ID PIC X(10).
MSIXOS-PO-CONTACT-PHONE PIC X(16).
MSIXOS-PO-CONTACT-EMAIL PIC X(40).
MSIXOS-PO-CONTACT-FAX PIC X(16).
MSIXOS-REST-OF-DATA-1 PIC X(530).
MSIXOS-SUPPLIER-RECORD REDEFINES
MSIXOS-SUPPLIER-NO-2 PIC X(6).
MSIXOS-SUPPLIER-NAME PIC X(32).
MSIXOS-ORDER-CONTACT PIC X(35).
MSIXOS-ORDER-PHONE PIC X(16).
MSIXOS-ORDER-ADDR-1 PIC X(32).
MSIXOS-ORDER-ZIP-CODE PIC X(10).
MSIXOS-ORDER-STATE-CODE PIC X(02).
MSIXOS-ORDER-STATE-DESC PIC X(20).
MSIXOS-ORDER-EMAIL PIC X(40).
MSIXOS-ORDER-FAX PIC X(16).
MSIXOS-SUPP-CNTY-CODE PIC X(3).
MSIXOS-SUPP-CNTY-DESC PIC X(40).
MSIXOS-ACCOUNT-NUMBER PIC X(10).
MSIXOS-GOVT-ID-NO PIC X(14).
MSIXOS-TEXT-RECORD REDEFINES MSIXOS-HEADER-RECORD
MSIXOS-TEXT-LINE-1 PIC X(840).
MSIXOS-ITEM-1-RECORD REDEFINES
MSIXOS-PO-ITEM-NO PIC 9(4).
MSIXOS-CURR-QTY-P PIC +9(9)V9(2).
181
MSIXOS-UNIT-OF-PURCH PIC X(4).
MSIXOS-UOP-DESC PIC X(50).
MSIXOS-ISO-UOP PIC X(4).
MSIXOS-RECV-QTY PIC +9(9)V9(2).
MSIXOS-OVERDUE-QTY PIC +9(9)V9(2).
MSIXOS-GROSS-PRICE PIC +9(11)V9(4).
MSIXOS-STOCK-CODE PIC X(9).
MSIXOS-MNEMONIC-1 PIC X(8).
MSIXOS-MANUFACTURER-1 PIC X(40).
MSIXOS-PART-NO-1 PIC X(30).
MSIXOS-ITEM-NAME PIC X(40).
MSIXOS-DESC-LINE-1 PIC X(40).
MSIXOS-FPA-REC-TYPE PIC X(1).
MSIXOS-FPA-ID PIC X(8).
MSIXOS-FPA-ITEM-NO PIC 9(4).
MSIXOS-CURR-DUE-DATE PIC X(8).
MSIXOS-DAYS-OVERDUE PIC +9(3).
MSIXOS-PREQ-NO PIC X(6).
MSIXOS-PREQ-ITEM PIC X(4).
MSIXOS-ITEM-TYPE PIC X(1).
182
MSIXOS-ITEM-STATUS PIC X(1).
183
MSIXSS - TTT
Field Name Field Type/Length
MSIXSS-KEY-012.
MSIXSS-DATA-TYPE PIC X(1).
MSIXSS-KEY-VALUE PIC X(63).
KEY-STRUCTURE REDEFINES MSIXSS-KEY-012.
MSIXSS-DATA-TYPE-2 PIC X(1).
MSIXSS-INTERFACE-ID PIC X(8).
MSIXSS-RECORD-STATUS PIC X(1).
MSIXSS-DOC-TYPE PIC X(1).
SUPPLIER-STATEMENT VALUE 'S'.
MSIXSS-DSTRCT-CODE-1 PIC X(4).
MSIXSS-SUPPLIER-NO-1 PIC X(6).
MSIXSS-START-DATE PIC X(8).
MSIXSS-END-DATE PIC X(8).
MSIXSS-NO-OF-DAYS PIC X(2).
MSIXSS-PROC-DATE PIC X(14).
184
MSIXSS-SEQUENCE-NO-9 PIC 9(6).
MSIXSS-SUB-SEQUENCE-NO-9 PIC 9(2).
MSIXSS-REST-OF-KEY PIC X(3).
MSIXSS-DATA-AREA.
MSIXSS-REC-TYPE PIC X(6).
MSIXSS-HEADER-RECORD.
MSIXSS-SUPPLIER-NO PIC X(6).
MSIXSS-CURRENT-DATE PIC X(8).
MSIXSS-DSTRCT-CODE PIC X(4).
MSIXSS-DSTRCT-NAME PIC X(40).
MSIXSS-DSTRCT-ADDR-1 PIC X(32).
MSIXSS-DSTRCT-ZIP-CODE PIC X(10).
MSIXSS-DSTRCT-STATE-CODE PIC X(2).
MSIXSS-DSTRCT-STATE-DESC PIC X(20).
MSIXSS-DSTRCT-PHONE PIC X(16).
MSIXSS-DSTRCT-FAX PIC X(16).
MSIXSS-COMPANY-NAME PIC X(40).
MSIXSS-COUNTRY-CODE PIC X(3).
MSIXSS-COUNTRY-DESC PIC X(40).
MSIXSS-DSTRCT-ACN-NO PIC X(14).
MSIXSS-AUS-BUS-NO PIC X(20).
MSIXSS-PAYEE-NAME PIC X(32).
MSIXSS-PAYEE-BRANCH-CODE PIC X(15).
MSIXSS-PAYEE-BRANCH-NAME PIC X(40).
MSIXSS-PAYEE-BNK-ACCT-NO PIC X(20).
MSIXSS-PAYEE-BNK-ACCT-NAME PIC X(40).
MSIXSS-PAYEE-BNK-ACCT-TY PIC X(1).
185
MSIXSS-REST-OF-DATA-1 PIC X(445)
MSIXSS-ORDER-SUPPLIER-RECORD REDEFINES
MSIXSS-SUPPLIER-NO-O PIC X(6).
MSIXSS-SUPPLIER-NAME PIC X(32).
MSIXSS-ORDER-CONTACT PIC X(35).
MSIXSS-ORDER-PHONE PIC X(16).
MSIXSS-ORDER-FAX-NO PIC X(16).
MSIXSS-ORDER-EMAIL-ADDR PIC X(40).
MSIXSS-ORDER-ADDR-1 PIC X(32).
MSIXSS-ORDER-ZIP-CODE PIC X(10).
MSIXSS-ORDER-STATE-CODE PIC X(2).
MSIXSS-ORDER-STATE-DESC PIC X(20).
MSIXSS-ORDER-COUNTRY-CODE PIC X(3).
MSIXSS-ORDER-COUNTRY-DESC PIC X(40).
MSIXSS-ORDER-ACCOUNT-NO PIC X(10).
MSIXSS-ORDER-GOVT-ID-NO PIC X(14).
MSIXSS-ORDER-CURR-TYPE PIC X(4).
MSIXSS-ORDER-CURR-ISO PIC X(4).
MSIXSS-REST-OF-DATA-2-ORDER PIC X(580).
MSIXSS-PAY-SUPPLIER-RECORD REDEFINES
MSIXSS-SUPPLIER-NO-P PIC X(6).
MSIXSS-PAYMENT-NAME PIC X(32).
MSIXSS-PAYMENT-CTACT PIC X(35).
MSIXSS-PAYMENT-PHONE PIC X(16).
MSIXSS-PAY-FAX-NO PIC X(16).
MSIXSS-PAY-EMAIL-ADDR PIC X(40).
MSIXSS-PAYMENT-ADDR-1 PIC X(32).
186
MSIXSS-PAYMENT-ZIP PIC X(10).
MSIXSS-PAYMENT-STATE-CODE PIC X(2).
MSIXSS-PAYMENT-STATE-DESC PIC X(20).
MSIXSS-PAYMENT-COUNTRY-CODE PIC X(3).
MSIXSS-PAYMENT-COUNTRY-DESC PIC X(40).
MSIXSS-REST-OF-DATA-2-PAY PIC X(612).
MSIXSS-INVOICE-HEADER-RECORD REDEFINES
MSIXSS-INVOICE-NUMBER PIC X(10).
MSIXSS-SUPPLIER-NO-3 PIC X(6).
MSIXSS-EXT-INV-NO PIC X(20).
MSIXSS-PO-NO PIC X(6).
MSIXSS-INVOICE-DSTRCT PIC X(4).
MSIXSS-INVOICE-DSTRCT-NAME PIC X(40).
MSIXSS-INVOICE-TYPE PIC X(1).
MSIXSS-NO-OF-INV-ITEMS PIC X(3).
MSIXSS-INVOICE-DATE PIC X(8).
MSIXSS-INVOICE-PAID-DATE PIC X(8).
MSIXSS-INVOICE-DUE-DATE PIC X(8).
MSIXSS-PAYMENT-ID PIC X(18).
MSIXSS-CHQ-WRITTEN-DATE PIC X(8).
MSIXSS-CHQ-PRESENTED-DATE PIC X(8).
MSIXSS-CHEQUE-RUN-NO PIC X(18).
MSIXSS-INVOICE-AMT-PAY PIC +9(13)V9(2).
MSIXSS-SETT-DISC-AMT-PAY PIC +9(13)V9(2).
MSIXSS-PRESC-PAY-AMT-PAY PIC +9(13)V9(2).
MSIXSS-CTAX-AMT-PAY PIC +9(13)V9(2).
MSIXSS-DEDUCT-TAX-PAY PIC +9(13)V9(2).
187
MSIXSS-ADD-SUPP-TAX-PAY PIC +9(13)V9(2).
MSIXSS-PAYMENT-AMT-PAY PIC +9(13)V9(2).
MSIXSS-INVOICE-AMT-INV PIC +9(13)V9(2).
MSIXSS-SETT-DISC-AMT-INV PIC +9(13)V9(2).
MSIXSS-PRESC-PAY-AMT-INV PIC +9(13)V9(2).
MSIXSS-CTAX-AMT-INV PIC +9(13)V9(2).
MSIXSS-DEDUCT-TAX-INV PIC +9(13)V9(2).
MSIXSS-ADD-SUPP-TAX-INV PIC +9(13)V9(2).
MSIXSS-PAYMENT-AMT-INV PIC +9(13)V9(2).
MSIXSS-INVOICE-CURR PIC X(4).
MSIXSS-INVOICE-CURR-ISO PIC X(4).
MSIXSS-INVOICE-AMT-OS PIC +9(13)V9(2).
MSIXSS-PAYMENT-AMT-OS PIC +9(13)V9(2).
MSIXSS-BUYING-RATE PIC +9(8)V9(7).
MSIXSS-HDR-PAYMENT-STATUS PIC X(2).
MSIXSS-HDR-PAY-STATUS-DESC PIC X(20).
MSIXSS-HDR-APPROVAL-STATUS PIC X(2).
MSIXSS-HDR-APPR-STATUS-DESC PIC X(20).
MSIXSS-COMMENT PIC X(80).
MSIXSS-REST-OF-DATA-4 PIC X(386).
MSIXSS-INVOICE-ITEM-RECORD REDEFINES
MSIXSS-INV-NO-4 PIC X(10).
MSIXSS-INV-ITEM-NO PIC 9(3).
MSIXSS-PO-NO-1 PIC X(6).
MSIXSS-PO-ITEM-NO PIC 9(3).
MSIXSS-ONST-RCPT-REF PIC X(10).
MSIXSS-WORK-ORDER PIC X(8).
MSIXSS-PROJECT-NO PIC X(8).
MSIXSS-EQUIP-NO PIC X(12).
188
MSIXSS-ACCOUNT-CODE PIC X(8).
MSIXSS-ITM-PAYMENT-STATUS PIC X(2).
MSIXSS-ITM-PAY-STATUS-DESC PIC X(20).
MSIXSS-ITM-APPROVAL-STATUS PIC X(2).
MSIXSS-ITM-APPR-STATUS-DESC PIC X(20).
MSIXSS-REST-OF-DATA-5 PIC X(816).
MSIXSS-TEXT-RECORD REDEFINES
MSIXSS-INV-NO-5 PIC X(10).
MSIXSS-TEXT-LINE-1 PIC X(918).
189
Ellipse Administration - Screens

Screens
MSE016 - Search Device ................................................................................ 191
MSE016 - Device detail ................................................................................. 192
MSE081 - Search Program/Report Configuration .................................................. 194
MSE081 - Program/Report Configuration detail .................................................. 195
MSEAUR - Search Audit Restriction Override ....................................................... 199
MSEBAT - Batch Admin ................................................................................. 201
MSM005A - Close Accounting Period ................................................................. 205
190
MSE016 - Search Device

Use this screen to search for existing printer devices in your logged in district.
You can also search for devices in all districts and create a new association to a device which exists
on the network.
Note: Only System Administrators have write access to this program.
Device Name
The name of the device as defined on your printer network. This name identifies the device.
All Districts
Select this check box to search and display devices for all districts.
191
MSE016 - Device detail

Use this screen to create an association to a device which exists on your network.
This screen can also be used to modify existing device details and delete devices which are no
longer required.
Note: Only System Administrators have write access to this program.
The following devices can be set up:
 IPP enabled printers enabling direct printing
 Printers that have an IPP URL and are accessed using servers with IPP functionality, such as
Windows Server 2003 or 2008 (this is best practice for a multi-printer environment).
More than one device can be created to point to the same device URL.
Note: Each device is given a unique two-character device code by the Ellipse EAM system. Within
Ellipse EAM this two-character code is linked to the device name to which users can direct reports.
Device Type
The device type. Options are:
 Printer
 Fax
 Email
This field is mandatory in create mode.
Device Name
The name of the device as defined on your printer network. This name identifies the device.
Description
A full description of the device. This can be information such as where the device is located and the
type of device, for example if the device is a printer, a description of Duplex can be entered.
This can be taken from the location as defined on your printer network.
Device URL
The URL of the device.
For Example:
ipp://ServerGrpA.Company.com:631/printers/PRTABC1S.
Use port 631 to print remotely to any IPP enabled printer through the internet.
Note: For printers that are IPP enabled the printer URL can be set up for direct printing rather than
the requirement to go through the server.
This field is mandatory when in create mode.
System Wide Default
Indicates the specified printer is the system wide default printer.
A printer can be the system wide default when it is not available to any district.
A printer that has a district selected as a default is used as the default printer. Priority is district
default before system wide default.
In the case of a printer being selected as the system-wide default, Ellipse EAM will clear the current
system wide default printer.
192
All Scopes
If selected, indicates all scopes are accessible.
District
The district code. When creating a new device association, by entering a district code in this field,
the device will be valid for the district entered only.
If All Districts is selected, the results grid displays a list of all the districts at the time the printer
was configured.
District Desc
The district code description.
Default
Indicates that the district uses the printer as its default.
Functions and Actions
Function and Actions allow you to perform a command or task in an application. For more
information, refer to Ellipse EAM Application Toolbar.
 Print Test Page - Prints a test page to the specified printer.
Note: This button does not display when in create mode.
193
MSE081 - Search Program/Report Configuration

Use this screen to search for existing program/reports request parameters.
Using this screen you can also:
 Upload reports (RDL definitions)
 Delete files for existing program/reports
Program Name
The program/report name, for example, MSRxxx, MSBxxx, MSHxxx and so on.
This name uniquely identifies the program/report.
Note: Partial entry of a program name restricts the search. For example by entering MSR61, Ellipse
only returns programs that start with MSR61.

 Delete File - Deletes the program configuration.
Grid Actions
Grid actions allow you to perform an action relating to the item in the grid. For more information,
refer to Grids.
The following grid actions are available:
 Upload Report - Opens the Dialog Box - Upload Report.
194
MSE081 - Program/Report Configuration detail

Use this screen to create, update, delete and review a program/report template and its
parameters. For each new program/report created, program/report parameters can be defined.
This template is used by MSO080 to create a request, MSM080C - Report Parameters displays the
parameters which require entry to produce the batch request.
When report parameters are created for a program/report, the parameters display in MSM080C -
Report Parameters and are available for entry.
Program Name
The program name which uniquely identifies the program/report and complies with the following
conventions:
 MSRxxx - Ellipse Reports
 MSBxxx - Batch Programs
 MSHxxx - House Keeping Programs
 MSUxxxx - Utility Programs
Request Type
The request type. Options are:
 Group - Create a program/report that calls multiple program/reports
 Program - Define single stand alone programs.
 Stream - Create a stream configuration that can be used in Queues to manage customer
streams developed in custom_batch.xml
 No Request - Run programs on an ad hoc basıs.
Program ID
The alphabetical character used to differentiate reports with the same name and different
parameters.
For example, the report/program may produce more than one report, in this case an alphabetical
character is used to differentiate the reports, for example A, B or C.
Request number
The request number, this is used as a way to separate programs with the same code/name and
different parameters. For example, 01, 02, 03...99.
Title
The title of the program/report. Two lines are available.
If a number of programs/reports are going to be defined with similar functionality and changed
parameters, then the second line can be used to provide a descriptive difference.
Tabs
 Detail
 Parameters
 Upload File
Detail tab
Start option for batch
Select one of the following:
195
 Initiation of Batch Jobs allowed from online - Allows the request to be submitted from
MSO080 as well as cyclic requests being created.
 Run Batch Job overnight only - Stops batch requests from running outside of the overnight
cycle.
Note: For users with System Administrator privileges, the system overrides the Run Batch Job
Overnight Only selection.
No. of Requests
The number of requests required for the report.
Options are:
Option Description
Does Not Require a Request Does not allow a request to be submitted

Report
Only One Request is Valid For Only one request containing this program is allowed in
This Report MSF080. If a second request is submitted through MSO080 -
Request Reports or MSB082 - Cyclic Request Submission,
this will result in an error (while the request exists in
MSF080).
Multiple Requests are Allows unlimited requests containing this program.

Allowed per District
Single Request Allowed per Only one request containing this program is allowed in
District MSF080 (per district). If a second request is submitted
through MSO080 - Request Reports or MSB082 - Cyclic
Request Submission, this will result in an error (while the
request exists in MSF080).
Note: If it is for a different district that has no request, it is
successfully written to MSF080.
District Code
If selected, this check box indicates that the program/report can be run at global level.
If clear, district code is mandatory and cannot be changed from the user's login district.
Reverse Option
If selected, this check box indicates that the requests are processed 'last in first out'.
If clear, requests are processed 'first in first out'.
For example if selected, if users enter multiple requests for the same program the last request is
processed first.
Parameter Program
The parameter program. This is the name of the online program that will accept and validate the
request parameters for this report.
This program writes its own request records to the Batch Request file (MSF080). This facility is only
used if the standard request parameter validation is insufficient.
Inhibit Medium/Printer
If selected, removes the the medium/printer related options from the MSM080B - Maintain Report
Request screen.
196
Request Record
If selected, request records are written.
If clear, an error displays when a request (cyclic or non-cyclic) is submitted.
Request Allowed
The type of request allowed. This identifies how the program/report can be run.
Valid options are:
 Batch only - This report can only be submitted as a cyclic request.
 Always - If there are no restrictions on the submission of the report, the report can be
requested using MSO080 - Request Reports from the reports menu of applications, or within
another Ellipse application.
 Never - This report cannot be submitted from within an Ellipse application.
No Process SPL
The number of requests to be processed each time the report is initiated. Entry must be in the
range 1 to 999. The default is 1. This field is only for RDL type reports. For example, if this field is
set to 5, on a single execution of a report for example, MSB141 Picking Slips, the report internally
iterates and processes 5 requests before terminating.
No of Requests to Proc in an Execution
(Number of Requests to Process in an Execution)
Enter the required number of requests. This field together with the No Process SPL field are
applicable to installations that can process multiple requests and hold them for spooling. For
example, spool off after every five requests are processed.
Parameters tab
Display Row
The number of the row to display the parameter. The row is relative to the first parameter row, for
example, row 1 is line 9 on the screen.
Description
The description of the parameter. This parameter description displays in MSM080C - Report
Parameters once the request is submitted from MSM080B - Maintain Report Request.
Mandatory
Indicates the report parameter is mandatory.
Repeat Counter
The number of times the parameter is to be repeated on the screen.
Offset
The offset is the character position within that record relative to the start of the parameters field.
Length
The length of the parameter.
Field Type
The code to identify the type of parameter. Entry is validated against the Table File FT - Field
Type.
Field Type Description
The field type code description. For example if Field Type AN has been selected, the description is
Alpha Numeric.
197
Parameter Type
The parameter type. Valid options are:
 Constant - The value of this parameter is not shown on the screen, but is moved onto the
request record.
 Default - The value is displayed on the screen as a default value.
Note: You must enter a value in the Parameter Value field, if this field is populated.
Parameter Value
The parameter type value where applicable.
Range Test
The range test for numeric parameters. This test is inclusive of the low values.
Range High
The range test for numeric parameters. This test is inclusive of the high values.
Special Editing
The code to specify additional validation requirements.
Entry is validated against the Table File SE - Special Edit.
Special Editing Desc
The special editing code description.
Group Label
A group label to form a relationship between a group and a program. Entry is validated against the
Table File LABL - Group Label Variables.
Table Test
This indicates whether the parameter is to be validated against a Table File.
Table Type
If the Table Test check box has been selected, enter the table type the field is to be validated
against.
Table Type Desc
The title of the table type.
Error
The error number to be used if the validation fails.
Error Desc
The error number description.
Upload File tab
File
Enter or browse and select the file to upload.
198
MSEAUR - Search Audit Restriction Override

Use this screen to search for audit restriction overrides. The following files can be accessed using
MSEAUR:
Audit Restrictions ABB Defined
Audit Restriction Override Client-defined
Related Processes and Activities

Audit Rules, Restrictions and
Overrides
60
Create Audit Restriction
Override
68
Review Audit Restriction
Override
69
Update Audit Restriction
Override
70
Delete Audit Restriction
Override
71
Search Audit Restriction Override Search Method

The method used to search for audit restrictions based on a specific search method and criteria.
Records found matching the search criteria display in the search results grid.
Select the required search method:
All Searches for all audit restrictions.
Exact Match Displays the exact audit restrictions based on the entry made in the
Table Name field.
Starts With Displays audit restrictions that start with the specified characters
entered in the Table Name field.
Starts From Displays all audit restrictions starting from the specified characters
that match the entered search criteria.
Table Name
Enter a table name on which to search.
199
MSEAUR - Update Audit Restriction Override

Use this screen to update audit restriction overrides.
Related Processes and Activities

Audit Rules, Restrictions and
Overrides
60
Create Audit Restriction
Override
68
Review Audit Restriction
Override
69
Update Audit Restriction
Override
70
Delete Audit Restriction
Override
71
Table Name
The name of the table.
Override Level
Select the required override level from No Access to Full Access.
Note: The default for tor the ABB defined Audit_Restriction file is no access. Users can update the
setting and it will override the ABB defined level of no access. If the user subsequently deletes the
user defined setting, the ABB default of no access will be reapplied.

 Submit - Validates and saves the data entered.
 Refresh - Reloads the original data. Any changes made since the last submit are lost.
 New - Opens the MSEAUR - Create Audit Restriction Override screen.
 Save As - Creates a new item based on the information provided by an existing item.
 Delete - Displays a confirm deletion dialog box to confirm deletion of the current item.
 Open - Displays a dialog box to enter an existing item to display its detail.
 New Search - Returns to the Search screen and clears the search results and the search criteria.
200
MSEBAT - Batch Admin

Note: Only Systems Administrators have access to this screen and its functionality.
Use this screen to update and review administrative details for the batch subsystem.
This screen can also be used to:
 Load the custom_batch.xml file
 Set up a cyclic request schedule time that overrides the default time held in batch.xml
 View a batch.xml file
 Add user queues to ensure that jobs are efficiently processed
 View batch log files
 Create additional queues and delete queues
The batch subsystem loads batch.xml and custom_batch.xml each time it is started.
MSEBAT holds queue and schedule information as well as start/stop requests.
Each time information is saved in MSEBAT, the batch subsystem is updated.
Refer to the Batch Processing Configuration and Administration Guide for more detailed
information on Batch Administration.
Batch Status
Indicates the status of the batch subsystem as started or stopped.
 If the batch status is Started, the Stop and Force Stop button is available to those authorised.
 If the batch status is Stopped, a Start button is available for those authorised.
Note: Stop performs a controlled shutdown of the batch process, where jobs are allowed to finish.
Force Stop cancels all running jobs.
Cyclic Request Schedule Time

The overriding schedule time. This replaces the default time used for scheduling cyclic requests. If
provided, it is used by the batch subsystem in place of the default schedule time.
The default time is found in batch.xml as the value of 00:05 (Time="0005") within the Weekly
Schedule definition for overnight. If you want the overnight process to start at another time it must
be entered here.
For example, to start at 3:15 am, enter 03:15:00.
Tabs
 Queues
 Default Queues (Internal)
 Files
Queues tab
This tab is used to maintain queues in addition to those provided in the Default Queues (Internal)
tab.
Additional queues can be created so that:
 The user can ensure important requests have a queue specifically allocated to the type of
request, for example the need to having picking slips printed without delay
 Requests with high volumes are not slowed down by being part of a general queue.
These queues are used by the batch subsystem along with the default queues.
Note: If a request is submitted for immediate processing, without a user queue, it would run
through the default queue which has only one thread.
201
Sequence No
The order in which batch subsystem checks the user queues against the request. This is to assess a
match with the queue pattern.
 The default queues with First in the Applied field (Default Queues Internal tab) are always
checked before any of the user queues
 The default queues with Last in the Applied field are always checked last.
The batch subsystem may find a match with the first user queue it compares or with default queues
with an Applied of first, therefore the batch subsystem stops when a match is found.
Notes:
• When a row is added to the grid, it is allocated a sequence number. To change the sequence of a
queue, select the row and move it up or down.
• Sequence numbers are maintained by Ellipse EAM.
• The relative value of the sequence number ensures the rows are maintained in the correct order.
• Add a new queue at the end and the number continues the series, for example 100, 200, 300 and
so on.
• Add a new queue between the rows and the number continues in sequence, for example 100, 200,
250, 300 and so on.
• Move a row up or down in the queue and the number assigned to the moved row adjusts to
continue the sequence, for example 100,200, 225, 250 and so on.
Queue Name
The name given to the queue. This field is mandatory.
Pattern
The pattern that defines the queue.
The maximum number of jobs. This is used to allocate resources and ensure that they are only
available to the specified queue.
When a queue does not have any requests to process it will not consume any resources. When it
does have requests, it continues to add threads until it reaches its maximum or until it does not
have any more resources available.
For example:
If seven is entered for the Picking Slips queue, up to seven picking slip requests would be processed
at any one time.
Note: A number of one or greater must be entered. The higher the number the greater the volume
of job requests can be handled for that queue.
Do Not Retain
Indicates the batch requests belonging to that queue are not retained.
This means, that the request is not moved from MSF080 to MSF085 and is deleted upon completion.
The review information is not written to MSF086, therefore the details cannot be viewed in MSE086
- Program/Report Review.
Indicates the trailing spaces are removed from the output created using this queue.
Default Queues (Internal) Tab
Applied
The order in which the batch subsystem checks the default queues against the request to assess if
there is a match with the queue pattern.
202
 First indicates that the default queues are checked before any user queues.
 Last indicates that the default queues are checked after the default first and any user queues.
Queue Name
The name given to the queue.
Note: These are the default queues defined by Mincom. These queues cannot be modified.
Pattern
The pattern that defines the queue.
The maximum number of jobs. This is used to allocate resources and ensure that they are only
available to that queue.
The default queues are able to have the maximum concurrent jobs field blank. For example, the
queue default has been configured so that one thread is always available and only one job request
can run at a time.
Do Not Retain
Indicates the batch requests belonging to that queue are not retained.
This means, that the request is not moved from MSF080 to MSF085 and is deleted upon completion.
The review information is not written to MSF086, therefore the details cannot be viewed in MSE086
- Program/Report Review.
Note: This field is review only and cannot be modified.

Indicates the trailing spaces are removed from the output created using this queue.
Files tab
Contains access to the files used to configure and monitor the batch subsystem.
Using this tab you can:
 View a batch.log
 View a batch.xml
 Create, import modify and delete a custom_batch.xml
LOGS
Batch Log File
Ellipse EAM generates a batch.log file every day. To separate the current date from past days, the
system provides a date extension in the format of YYYY-MM-DD, for example batch.log.2012-06-22.
The number of past days is dependent on the housekeeping that is in place.
The batch.log file contains entries on the batch subsystem. Each entry starts with the date and
time, and then contains a description of how the batch subsystem has been impacted.
Note: This file contains the errors associated with batch subsystem NOT the batch requests. Batch
request log information can be viewed in MSE086 - Program/Report Review.
CONFIGURATION FILES
This section contains access to the .xml files used by the batch subsystem at start up, which
includes any time MSEBAT makes changes.
Note: Each time the MSFPRF or MSFTFS files are updated through MSEBAT, the batch subsystem
does a stop then start, which ensures it is up-to-date.
203
Batch File
The batch.xml file provides a structure that contains the streams, task lists and batch jobs that are
loaded into the batch subsystem at start up from the MSFTFS file.
Batch.xml is not editable. Entries in custom_batch.xml are used to provide the same functionality.
Custom Batch File
Create or browse and upload a custom batch file.
The custom batch file allows you to create your own batch structure containing batch jobs, task list,
and stream.
If you create an entry with a batch name that is the same name as that contained in batch.xml, it
will override the entry when loaded into the batch subsystem.
A custom batch file can be created from a template and must be saved and uploaded before it is
used. The newly created batch file is stored in the MSFTFS file.
 Start - Starts the batch subsystem process.
If the batch status is Stopped, the Start button displays.
 Stop - Performs a controlled shutdown of the batch jobs where jobs are allowed to finish.
If the batch status is Started, the Stop button displays.
 Force Stop - Cancels all running batch jobs.
 Release All SyncKeys - Releases all memory synchronized keys. This is useful if a batch freezes
on a specific sync key.
 Flip Batch Trace Flag - Turns batch server tracing on or off.
204
MSM005A - Close Accounting Period

This screen is used to close off a sub-system (module) so that subsequent financial transactions
generated within that sub-system are automatically posted to the next accounting period for the
processing district.
Access to this screen is restricted to users with the appropriate security access. A screen is
displayed for each sub-system where financial transactions apply.
You can choose to close the Accounting Period for only some of the sub-systems, however, the
Financial and General Ledger modules must be the last sub-systems closed for any given accounting
period.
Note: This screen only displays the Fixed Asset processing period if the selected district owns a
Fixed Asset register.
Close
(Close Period Indicator)
Enter Y to close the current period and move to the next sub-system. Accounting period records
must exist in the System Control file for the closing period and the new current accounting period.
Journal Holding Sub-system closure. For example, Y is only permitted if the new current accounting
period will not be later than that of any of the other sub-systems displayed excluding the General
Ledger.
General Ledger Sub-system closure. For example, Y is only permitted if the new current accounting
period will not be later than that of any of the other sub-systems displayed excluding the General
Ledger.
Confirmation is required for any entry if its corresponding new current accounting period will be
two periods or more later, than that of any of the modules displayed.
205

Ellipse Administration Guide

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Ellipse Administration Guide

Încărcat de

Drepturi de autor:

Formate disponibile

—

Ellipse EAM 9.0

Bulk Request Creation - MSH083A ........................................................................... 72

MSBXRQ - Request for Quotation ....................................................................... 148

Start or Stop the Batch Subsystem

Add User Queues

Review Default Queues

Override Scheduled Cyclic Request Time

View Batch Log File

View Batch File

Create Custom Batch File

Upload Custom Batch File

Delete Custom Batch File

Reporting Administration (E9.0)

Reports and Batch Processes

Initiating Reports and Batch Processes

Group Report Requests

Create Program or Report Configuration

Modify Program or Report Configuration

Delete Program or Report Configuration

Delete Report Upload File

Request Cyclic Reports

Request Ad Hoc Reports

The MSM080B - Report Request Selection screen displays.

Initiate Program or Report Requests using the Search

Defer Report Request using the Search Screen

Modify Report Requests

Delete Program or Report Requests

View Program or Report Request Log

Review Cyclical Request

Modify Cyclical Details

Delete Cyclical Request

Review Reports Online

Send Report to an Employee

Delete an Online Report Record

Display Reports with Logs Files

MSB081 - Batch Request Housekeeping Program

MSB085 - Batch Report Monitoring Housekeeping

External Systems Interface to Ellipse

The meaning of the values of the parameter OPTION are:

Parameter Type Length Values/ Meaning Definition

STATUS M - MORE LINES

Parameter Type Length Values/ Meaning

The following parameters should be set up:

Parameter Type Length Values/ Meaning

RETURN-STATUS is used to signal the status of the performed operations.

Convert Request Banners - MSH080A

Convert Standard Text (Compression) - MSH096A

Convert Standard Text (Relational) - MSH095A

Rebuild MSFX99 records for Work Orders - MSHX9AA

Update MSFX99 record with Project No. - MSHX99A

Audit Rules, Restrictions and Overrides

Defining Audit Rules

Audit File Restrictions

Create Audit Rule

Review Audit Rule

Update Audit Rule

Delete Audit Rule

Review Audit Data

Update Audit Rule Reason Code or Comment

Create Audit Restriction Override

Review Audit Restriction Override

Update Audit Restriction Override

Delete Audit Restriction Override