|
|
Description
The user enters key information regarding the problem, namely the company code and the individual
reporting the problem. After routine validation of the company and person for validity, the
program presents a screen permitting input of the problem data.
| Screen |
Screen_2 |
Contact Criteria |
All PIRs must be associated with a company and contact. Both company and contact must be currently registared with PROS. |
| Screen |
Screen_3 |
PIR Entry |
All PIRs must have a valid Product Code, Feature, Version, and Component. All other fields can be filled in now or updated later. |
| Database |
RG1 |
Company |
Main Company data report. |
| Database |
RG2 |
People |
The People data reports contains contact information. |
| Database |
RG4 |
Product |
Maintains FCI Product Versions. |
| Reports |
|
None |
|
| Interfaces |
|
None |
|
Summary of Major Outputs
| Screen |
Screen_4 |
PIR In-Progress Screen |
An In-Progress line is displayed at the bottom of the screen to let the user know something is happening. |
| Screen |
Screen_5 |
PIR Acknowledgement |
PIR entry is acknowledgement with a reference number displayed at the bottom of the screen. |
| Database |
RG10 |
PIR |
Problem Incident Report |
| Reports |
|
None |
|
| Interfaces |
|
None |
|
Summary of External Interfaces
None
Screen Analysis
 Contact Criteria - Screen_2
PIR Entry - Screen_3
PIR In-Progress Screen - Screen_4
PIR Acknowledgement - Screen_5
System Notification - Screen_6
Decision Logic
| 4
|
Adhoc
|
@ldv,w V20I3=erid
|
Setup Return Parameters
|
| 9
|
Label
|
1:
|
Main RUN Loop
|
| 78
|
Screen
|
@out,-0,2,24,1,V2
|
Solicit Company and Contact Information
|
| 119
|
Branch
|
@gto 3
|
Re-Display Criteria Screen
|
| 194
|
Screen
|
@out,-0,2,24,1,V2
|
Main Input Screen
|
| 326
|
Label
|
26:
|
Write PIR Record
|
| 352
|
Label
|
29:
|
Write Note to PIR report.
|
| 377
|
Screen
|
@out,-0,2,1,23,-1
|
Acknowledgement Screen with PIR Reference Number.
|
| 389
|
Screen
|
@out,0,1,-0,2,10,
|
PIR data report full - Call Admin
|
Call Analysis
| 415
|
Call
|
@gto rpx 90
|
Use Help method
|
|
| 439
|
Call
|
@gto rpx 90
|
Call Help Method
|
| 501
|
Call
|
@gto rpx V27
|
Use GTO RPX to pass variables to user selected menu item
|
Data Access Methods
| 121 |
@bfn,V4,B,2,,8 '' . . 2-6 ,V248 V33I4,V34I6 |
| 122 |
@rdl,V4,B,V33,V34,8 2-6,9-35,45-30,76-4 V221A |
| 123 |
@rln 9-35,45-35 V225S35,V226S35 |
| 124 |
@rln 2-75 V227S75 |
| |
Find and Retrieve Company Information |
|
| 135 |
@bfn,V4,C,,,11 i 2-6,9-20 ,V248,V249 V33I4,V3 |
| 136 |
@rdl,V4,C,V33,V34,11 2-6,9-20,30-31,62-3,66-8, |
| 137 |
@rln 9-20,30-31,66-8 V238S20,V239S31,V240A8 |
| 138 |
@rln 2-75 V241S75 |
| |
Find and Retrieve People Information |
|
| 328 |
@wrl,V5,B,V33,V34 2-5,8-6,15-4,20-5,26-12,39-1 |
| |
Write PIR Main Record |
Database Analysis
| 316
|
Database
|
@ln+,V5,B,V3,V70,
|
Expand data report space for new PIR entry. |
Operational Factors
| Frequency of execution |
As needed |
User enters P.I.R. data in response to a reported problem. |
| Special time of day / week / month / qtr / year? |
Not applicable |
|
| Sequence / Dependency |
See comments above |
|
| Other |
Not applicable |
|
Field Definitions:
None
LinkedRun:
None
|