This section describes the changes to sequence numbering in views.
If a custom view has been placed between the system resources or after the system resources in the Resource Hierarchy tree, cross check the views and verify if the sequencing of views in the Resource Hierarchy tree is correct.
The following table displays the views that have been added to an existing entity in Release 9.0:
View Type | View ID | View Name | Sequencing Affected in the Entity in the Resource Hierarchy Tree |
---|---|---|---|
DETAIL_VIEW | YOMD353 | Container Return Tracking Number | container |
DETAIL_VIEW | YOMD147 | Modify Order Payment Information | order |
DETAIL_VIEW | YOMD3147 | Modify Order Payment Information | po |
DETAIL_VIEW | YOMD647 | Modify Order Payment Information | return |
DETAIL_VIEW | YOMD2647 | Modify Order Payment Information | templateorder |
The following SQL script identifies the list of custom views that may require a change in resource numbering because of the system views that have been added:
select parent_resource_id, resource_type,
resource_id, resource_desc, resource_seq from yfs_resource
where resource_create_type <> 'SYSTEM'
and resource_type in ('SEARCH VIEW,'LIST_VIEW', 'DETAIL_VIEW') and
parent_resource_id in (select distinct parent_resource_id from yfs_resource
where resource_id in ('YOMD353', 'YOMD147', 'YOMD3147', 'YOMD647',
'YOMD2647')) order by parent_resource_id, resource_type;