Go to the bottom.
!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! SDDL Name: PROPOSALS_PROCESSING.SDDL
!
! Purpose: This SDDL file declares the ASSIST proposals_processing
! relation.
!
! Modification History:
!
! Date PR Who Reason
! -------- ------- --- -------------------------------------------------
! 04/16/98 31837 MRB Created for access purposes
! 08/31/98 31837.1 MRB Added descriptions
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
LANGUAGE C, SQL
INCLUDE ZSPSS_USER_TYPES.SDDL
RECORD PPRC_TYPE
!------------------------------------------------------------------------------
!
! RECORD INFORMATION
!
!------------------------------------------------------------------------------
DESCRIPTION "This is the master relation for 'front end' processing
of a proposal. As such it has tracking information
for each element of a proposal. Here a proposal
consists of one or more visits and targets.
To support the partial-Transformation project
(see OPR 27789), this ASSIST relation was needed
to track the flow of assignment files through the
system. The relation will have an entry for
each proposal entity for which a separate AF can be
generated. It is populated by the Change Manager
and the AF_GENERATION and TRANSFER tools.
There are four processing steps to track: proposal
modification, assignment file generation, transfer to
SOGS, and loading into the PMDB. Since it is not
easy to set up a replicated relation in which different
fields are populated from different sides of the rep
server, information about the load step will
be stored separately using existing PMDB relations.
At each step, it is useful to store the date when the
step was performed, the proposal version involved,
the software version used to generate the assignment
file, and the version of the assignment file. "
!------------------------------------------------------------------------------
!
! FIELD INFORMATION
!
!------------------------------------------------------------------------------
FIELD prop_id
TYPE INT_PROPOSAL_ID_TYPE
DESCRIPTION "prop_id is the proposal number. It is set by
the Change Manager when a new record is created."
END_FIELD
FIELD entity_type
TYPE C1
DESCRIPTION "entity_type identifies the type of entity.
Its possible values are V (a visit), T (a target),
L (the entire collection of links in a proposal), and
P (all proposal-level data). It is set by the Change
Manager when it identifies a new entity in a proposal
which does not yet have a record in the database. "
END_FIELD
FIELD visit_id
TYPE VISIT_ID_TYPE
DESCRIPTION "It is set by the Change Manager when it identifies a
new visit entity. For non-visit entities, this
should be set to an empty string. "
END_FIELD
FIELD target_number
TYPE I2
DESCRIPTION "target_number is the target number, as an integer.
It is set by the Change Manager when it identifies a
new target entity. For non-target entities, this
should be 0. The prop_id, entity_type, su_id, and
target_number form a primary key for this relation. "
END_FIELD
FIELD entity_deleted
TYPE C1
DESCRIPTION "entity_deleted is N if the entity is still part of
the proposal, Y if it has been deleted. It is
initialized to N by the Change Manager when a new
entity is identified. If the entity is later deleted
from the proposal, the Change Manager sets its
entity_deleted to Y, but the record should never be
deleted from this relation. Later, if a new entity
with the same key fields is re-created, the
entity_deleted may be set back to N. The LOAD_TRANS
tool will use the entity_deleted to determine when an
entity has to be deleted. "
END_FIELD
FIELD prop_date_modified
TYPE SYBASE_DATETIME
DESCRIPTION "prop_date_modified is the date when the version of
the proposal in which the entity was last modified
was checked into PLIB. It is set by the Change
Manager when it determines that an entity has been
modified. All dates will be in the standard Sybase
format (datetime_type). "
END_FIELD
FIELD af_date_generated
TYPE SYBASE_DATETIME
DESCRIPTION "af_date_generated is the date when the assignment
file for the entity was last generated by running
the GENERATE_AF tool. It is set by GENERATE_AF after
the assignment file is generated. "
END_FIELD
FIELD prop_rev_modified
TYPE I2
DESCRIPTION "prop_rev_modified is the revision number of the
version of the proposal in which the entity was
last modified. It is set by the Change Manager when
it determines that an entity has been modified. It
is used by GENERATE_AF to determine whether an
assignment file needs to be regenerated. "
END_FIELD
FIELD prop_rev_af_generated
TYPE I2
DESCRIPTION "prop_rev_af_generated is the revision number of the
version of the proposal with which an assignment file
was last generated for the entity. It is used by
GENERATE_AF to determine whether an assignment file
needs to be regenerated. It is set by GENERATE_AF
after an assignment file is generated. "
END_FIELD
FIELD sw_ver_af_generated
TYPE C6
DESCRIPTION "sw_ver_af_generated is the version of the Trans or
SPIKE software used to generate the most recent
assignment file for the entity via GENERATE_AF.
It is set by GENERATE_AF after the assignment file
is generated. "
END_FIELD
FIELD af_rev_generated
TYPE I2
DESCRIPTION "af_rev_generated is the revision number of the
assignment files last generated via GENERATE_AF.
It is initialized to 0 by the Change Manager when the
entry for the entity is created, and incremented by
GENERATE_AF each time it is run to generate an
assignment file. It is used by TRANSFER to determine
whether an assignment file needs to be transferred. "
END_FIELD
FIELD prop_af_errors
TYPE C1
DESCRIPTION "prop_af_errors is Y if the Trans or SPIKE software
used to generate the most recent assignment file for
the entity via GENERATE_AF reported any errors, N
otherwise. It is used by TRANSFER to warn against
the transfer of bad assignment files. "
END_FIELD
FIELD sw_af_errors
TYPE C1
DESCRIPTION "sw_af_errors is Y if GENERATE_AF failed to generate
an assignment file (due to some fatal error or crash)
for the entity the last time it was run, N otherwise.
It is used by TRANSFER to warn against the transfer
of obsolete assignment files. "
END_FIELD
FIELD trans_mode
TYPE C50
DESCRIPTION "Mode trans was run in, i.e. full, manual merge. "
END_FIELD
END_RECORD
!------------------------------------------------------------------------------
!
! RELATION DECLARATION
!
!------------------------------------------------------------------------------
RELATION proposals_processing
TYPE PPRC_TYPE
DESCRIPTION "Proposals Processing Relation"
SUBSYSTEM_USING "SPSS", "TRANS", "SPIKE", "PEPSI"
INDEX proposals_processing_index1
TYPE unique, clustered
FIELDS prop_id, entity_type, visit_id, target_number
END_INDEX
END_RELATION
Go to the top.