WILLIAMS BUSINESS PROCESS MANAGER 5/22/95
DSP01 EVENT MAINTENANCE EVENT DETAIL
Type PO1 Desc OVERDUE PURCHASE ORDERS
Extract Name CF900CLP Extr Type PGM RPG PROGRAM
Replace Y Extr Freq Cd M/D MULTI DAILY
Extr Day Nbr Extr Freq Mn 1
Last Extract 5/22/95 10:58:53 Next Extract 5/22/95 10:59:00
Action Code 1 007 PO INQUIRY Action Code 2 006 PO MAINTENANCE
Action Code 3 011 VENDOR MASTER INQ Action Code 4 012 ITEM/VENDOR ANALYSIS
Action Code 5 008 PO RECEIPT ADMIN Action Code 6 009 PO RECEIPT QTY CTL
Action Code 7 015 MULT-LNE QTY CONTROL Action Code 8
Action Code 9 Action Code 10
Auto Action Immed Delete
Sort Sequence ASC ASCENDING
Control Value Description Balance Due Qty
Route Based on Description Receiving Co/Wh
Headings PO # Ln B Item # Dock Dt
F3=Exit F4=Prompt F10=Function Select F12=Comments
F15=Rekey Data
The Event Maintenance Detail screen allows you to define information about events and how they should be monitored by the Business Process Manager (BPM).
Much of the information specified on this screen will be useful in creating the extract or query program for the event type. For example, the Control Value Description and Headings fields tell the person creating the extract program or query some of the information that will need to be extracted.
Further information about the extract or about the event type in general can be specified in the Comments window.
TYPE
Display only. This is the event type code specified on the Function Select screen.
DESCRIPTION
Required. Enter a description of the event type.
EXTRACT NAME
Required. Name of the extract program or query. This program or query will be called by the BPM Asynchronous Monitor to check for occurrences of the event.
EXTRACT TYPE
Required. Indicates if the event extract is a program, a query that outputs to a file, or a query that outputs to a report. Extract type codes are user-defined on Reference File category N05.
If the extract type is a program or query file, the extracted information will be routed to the appropriate BPM mailbox, as specified on the Event Dispatch screen. If the extract type is a query report, the extracted event information will be printed, but there will be no online routing or notification of the event.
EXTRACT TYPE DESCRIPTION
Display only. The description of the extract type is retrieved from Reference File category N07.
REPLACE FLAG
Required. Used to specify if new extracted information should replace information extracted previously.
However, if this field is set to Y (yes), each time the extract program or query is run the resulting information replaces all the existing information for the event type in the new events queue. If the In-Process flag is set for an existing event extract record on the Event Manager Detail screen, that extract record will not be deleted when information for the same type of event is extracted.
If this field is set to N (no), all the existing information remains in the new events queue and the newly extracted information is added to the queue.
EXTRACT FREQUENCY CODE
Required. This code indicates how often the BPM Asynchronous Monitor should run the extract program or query. Extracts can be performed monthly, weekly, daily, or multiple times per day. Frequency codes are defined on Reference File category N05.
Daily, weekly, and monthly extracts are performed at the end of the specified day when the BPM Asynchronous Monitor shuts down.
EXTRACT FREQUENCY DESCRIPTION
Display only. The extract frequency description is retrieved from Reference File category N01.
EXTRACT DAY NUMBER
Required if the extract frequency is monthly. This code indicates the date on which extract processing is to occur each month. The value entered must be between 1 and 31. If 31 is entered, extract processing will occur on the last day of the month in months with fewer than 31 days.
If the extract frequency is not monthly, this field must be blank.
EXTRACT FREQUENCY (MINUTES)
Required if the extract frequency is multiple times per day. The frequency with which extract processing is to occur, expressed in minutes.
If the extract frequency is not multiple times per day, this field must be blank.
LAST EXTRACT DATE
Display only. This field displays the date of the last extract performed for the event.
LAST EXTRACT TIME
Display only. This field displays the time of the last extract performed for the event.
NEXT EXTRACT DATE
Required. Enter the date the next extract is to be performed. If you are adding a new event type, this will be the date the first extract is to be performed.
After the event is initially defined, the next extract date is automatically calculated and updated based on the extract frequency.
NEXT EXTRACT TIME
Required. Enter the time the next extract is to be performed. If you are adding a new event type, this will be the time the first extract is to be performed.
After the event is initially defined, the next extract time is automatically calculated and updated based on the extract frequency.
ACTION CODE
Optional. Codes indicating possible actions to be taken if an event of this type occurs. Each action code corresponds to a standard MAC-PAC conversation to which the user can navigate from the Event Detail screen in the Event Manager conversation. Action codes are defined in Reference File category N04.
Up to ten action codes can be defined for an event type. The action codes specified here determine the ten options that appear in the BPM Action Codes window in the Event Manager conversation for events of this type.
If specific information should be passed to the selected conversation, the description of the information can be specified in the comments for the event type. Press the Comments key (F12) to enter event type comments. When accessing a conversation using the action codes, the standard program authorization for the conversation will apply.
ACTION CODE DESCRIPTION
Display only. The description of the action code is retrieved from Reference File category N04.
AUTO ACTION CODE
Optional. Indicates an action code that can be used to automatically process events from the Event Manager Recap screen. The code entered in the Auto Action Code field must be one of the action codes defined for the event type in the Action Code fields.
IMMEDIATE DELETE FLAG
Required if an automatic action code is specified. Indicates if events should be deleted immediately if they are processed using the Auto Action option.
If this field is set to Y and you process a new event of this type using the auto action code, the event will be immediately deleted from your BPM mailbox. If this field is set to N, the event information will remain in your mailbox when you process it and must be deleted manually.
SORT SEQUENCE CODE
Required. Code indicating if event information on the Event Manager Detail screen should be displayed in ascending, absolute ascending, descending, or absolute descending order of the control value.
Sort Sequence codes are user-defined in Reference File category N05.
SORT SEQUENCE DESCRIPTION
Display only. The description of the sort sequence is retrieved from Reference File category N06.
CONTROL VALUE DESCRIPTION
Optional. The description of the control value for the event type, as defined in the extract program or query. For example, the control value for overdue purchase order lines might be the balance due quantity. The description entered here is used by the creator of the extract program or query to determine the information that must be extracted for the event type.
When new events are extracted, the Accumulate and Route Event Data program (CF202E) uses the amount of the control value in determining whether to route event information to a specific BPM mailbox. Maximum and minimum amounts for each mailbox ID are specified on the Event Dispatch screen.
When events are displayed on the Event Manager Detail screen, the text entered in this field is used as the heading literal for the control value field.
ROUTE BASED ON DESCRIPTION
Required. The description of the information that will be used to determine the routing of the extracted event information. For example, overdue purchase order lines might be routed based on the buyer code associated with the purchase order, while information about manufacturing orders due today might be routed based on the order’s company/warehouse.
The description entered here is used by the creator of the extract program or query to determine the information that must be extracted for the routing of the event information.
The Event Dispatch screen allows you to enter specific route-to information for the event type.
HEADINGS
Required. Specifies the literals that will be displayed on the Event Manager Detail screen when events of this type occur. Up to 40 characters can be displayed as the headings for the detailed information.
The literals entered in this field can be used by the creator of the extract program or query to determine the information that should be extracted and displayed on the Event Manager Detail screen for events of this type.
COMMAND KEYS
Enter - Process the information on the Event Maintenance Detail screen and display the Event Dispatch screen.
F3 - Exit program without processing the entered data and return to the BPM Menu screen.
F4 - Display a list of values for the field on which the cursor is positioned. If you select one of the items from the list, it will be returned to the application screen.
F10 - Return to the Function Select screen without processing the entered data.
F12 - Display the Comments screen for this event type.
F15 - Undo changes you have made to the screen since it was last saved.
|