If you select the EXECUTE option on the Inquiry Processing screen, the Business Element File Data Entry screen shown in Figure 3-128 appears.
/--------------------- Business Element File Data Entry ------------------------\ |Option ===> | | | |Composing CAP DB File def.: BEF - Business Element File | | | | | | 1 - Initialize Business Element File | | Prime business element file with null entries in preparation | | for online data entry. | | 2 - Online Data Entry | | Update the business element file using SAS/FSP. The file must | | have been previously initialized. | | 3 - Batch Data Entry | | Update the business element file using external card images. | | The card image update can be executed in foreground or batch. | | | | Starting date ===> _______ (ddmonyy) Number of months ===> ___ (1-9999)| | Card image DSN ===> _______________________________________________________| | | | | | | | | | | \------------------------------------------------------------------------------/ Figure 3-128. Business Element File Data Entry Screen
The Business Element File Data Entry screen provides you with
the options for initializing (only required if you intend to
use the SAS/FSP method of data entry), and for loading
business element data into your business element file.
Choosing Option 1, Initialize Business Element File, causes
any previous data that you entered in your business element
file to be discarded. A new file is created with initialized
entries based on the following parameters:
Starting The execution-time override for the Starting
date: date parameter on the Business Element File
Definition screen shown in Figure 3-125.
Specify this parameter to define the starting
date for file initialization.
Number of The execution-time override for the Number of
months: months parameter on the Business Element File
Definition screen shown in Figure 3-125.
Specify this parameter to initialize the number
of days, weeks, or months in your business
element file.
Choosing Option 2, Online Data Entry, provides direct,
interactive access to your business element file for data
entry. You can use the SAS Full Screen Product (SAS/FSP),
which is a prerequisite, to implement this option. When you
select this option, SAS/FSP is invoked in the foreground
through MICF. To use this method, you must first initialize
the file by selecting Option 1. If you use all of the
previously initialized entries, DO NOT reinitialize the file
unless you want to discard all of your previously entered
data. Instead, use the SAS/FSP commands for adding
observations to a SAS data set.
Choosing Option 3, Batch Data Entry, invokes a batch job that
reads your business element observations from the data set
that you identified in the following parameter:
Card image The data set name of the card image. This
DSN: parameter points either to a sequential data set
or a member of a partitioned data set that
contains business element data that you create
external to the CA MICS Capacity Planner.
Code this parameter as you would any other data
set name. If the data is a member of a
partitioned data set, include the member name as
part of this parameter. If the data set name is
cataloged under your userid, then do not enter
your userid as part of the data set name. If
you code a fully qualified data set name (that
is, including a user ID), then enclose this data
set name in single quotes.
Figure 3-129 shows a typical example of a SAS/FSP data entry
screen for a business element file.
1...5...10...15...20...25...30...35...40...45...50...55...60...65...70...75...80 /--------------------------------------------------------------------------------\ 1| Edit SAS data set: CAPACITY.CAPBEF01 | Screen 1 | 2| Command ===> ---------- | 3| | Obs 1 | 4| _____________________________________________________________________________ | 5| | 6| YEAR: 98 | 7| | 8| MONTH: 1 | 9| | 0| DATE: 31JAN98 | 1| | 2| INVOICES: __________ | 3| | 4| UPDATES: __________ | 5| | 6| OPN_ITEM: __________ | 7| | 8| | 9| | 0| | 1| | 2| | 3| | \
Figure 3-129. Business Element File Data Entry Screen
|
Copyright © 2014 CA.
All rights reserved.
|
|