| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
To reiterate, only composites with pending records within the date range are displayed in the summary menu. The summary menu shown in the following figure displays the Composite Name, Composite ID, Pending From Date, Pending To Date, and # Pending.
The Pending From Date corresponds to the earliest build date where a pending record exists for each composite. The Pending To Date corresponds to the latest build date where a pending record exists for each composite and where that is equal to or prior to the As Of date selected in the Define screen.
You can click Refresh to monitor the completion of builds directly from Composite Approval and/or update the # Pending for a given composite.
| Info |
|---|
Be sure to click Refresh to update the menu if the date parameters were changed on the Define dialog box. |
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
To view the details for a specific composite, click the composite summary record to display the Performance Composite Pending Approval Details window shown in the following two figures. The results can be sorted by Entity and Effective Date or Effective Date and Entity as shown.
The default setting Entity and Effective Date displays the records by entity, then by date. As a result, if there are multiple records for a given entity, they are grouped together in chronological order. Conversely, the Effective Date and Entity option automatically sorts the changes with the Effective Date as the priority in the sorting order. Regardless of sorting order, pending records must be updated in chronological order.
The window is designed to simplify the display of multiple entities with multiple pending records within a composite. This is done by showing only the most recent pending change record for an entity using in/in Flag indicators.
It is important to note that the build process automatically applies dependency logic, whereas the current date entity change is dependent on any previous change for that entity. This logic is then applied when populating Composite Approval with in/in records. For example, consider a monthly build scenario where month-end builds were executed from 10/31/1981 through 12/31/1981 for the composite shown in the following figure. The builds for the composite determined that JK Portfolio 37 (JKEnt37) met the criteria for the composite as of 10/31/1981 and failed the criteria as of 12/31/1981. As a result, only the Pending in
) record on 10/31/1981 and pending out
(
) on 12/31/1981 displays. The pending in records for 11/30/1981 are suppressed and do not display unless the 10/31/1981 record is rejected.
The Performance Composite Pending Approval Details window allows you to Approve or Reject each individual record for a given composite. It is important to wait until all of the builds have completed for a given composite before you begin to approve/reject records.
To commit the membership change into ENTITY_RANGE_DETAILS for the composite for the selected entity with the appropriate Start Date or End Date, check the check box next to the entity and click Approve at the top of the screen. If it is determined that the change is not valid, click Rejectto ensure that the record is not committed. Rejected records are still retained in the journal table for audit purposes.
When records are updated, they are automatically cleared, the Total Records count is updated, and only the remaining pending records are displayed. To update all of the records for the composite for a given Effective Date, click Select All at the top of the screen and click Approve or Reject. An additional maintenance option, shown in the following figure, allows you to right-click on a specific entity and not only perform the functions described above, but also for Approve All for this Entity and/or Reject All for this Entity. These options are enabled when Entity and Effective Date sorting mode is used. These options allow you to update all of the pending records for the selected entity at one time.
To illustrate its usage, consider the previous example. If Approve All for this Entity is selected for JKEnt37, the first pending record of each change is approved, in this case the 10/31/1981 and 12/31/1981 records.
| Anchor | ||||
|---|---|---|---|---|
|
The Composite Approval functionality also supports the ability to perform multiple Reject and Approve updates over a date range for a single entity (if necessary). Building on the example of JKEnt37, you can reject the 10/31/1981 record and then approve the 11/30/1981 record, followed by a subsequent approval of the 12/31/1981 record. As a result, in Default Mode a Start Date record for 11/30/1981 and an End Date record for 12/31/1981 for the entity (JKEnt37) is committed to ENTITY_RANGE_DETAILS for the composite (JKACOM3).
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
During the approval process, you can view all of the records in Pending status for a given entity, highlight an entity, and click Detailsat the top of the screen to view the Pending Approval Details of the Entity screen. In the following figure, all of the pending
) record for JK Portfolio 37 (JKEnt37), including the 11/30/1981 record display.
Note:
You cannot update records from this screen. It is for viewing purposes only.
Close the screen to return to the Performance Composite Pending Approval Details window and continue the approval process.
In Default Mode, the Start Date and End Date correspond to the Effective Date of the build based on the default inclusion/exclusion approval logic (see Use the Composite Approval Module for optional inclusion/exclusion logic).
By leveraging Reason Code functionality, the Start Comments and End Comments display with the inclusion rule as well as the results for each entity for each effective date. Click the ellipsis button (…) to view the entire rule as well as the results. Note that you can also edit the comments by clicking Edit Comments.
The Composite Approval shown in the following figure allows you to add, edit, and/or delete the comments. The edited comments are stored in ENTITY_RANGE_DETAILS for the composite for the entity as of the appropriate effective date.
| Info |
|---|
Pending records are not included in composite calculations. |