Adding import group views is the first part of creating import group views. A group view is a collection of one or more associated entity views. Group views have cardinality, that is, each of their component views may occur more than once.
A group view with cardinality greater than one is a repeating group view, and can be thought of as an array of data items.
Group views with cardinality of one are non–repeating group views. Non-repeating group views are often used to collect many other entity views and group views together so that view matching can be simplified when calling subordinate action blocks.
Repeating group views can be illustrated by an order form. A typical order form for one customer relates to attributes from the CUSTOMER, ORDER, PRODUCT, and ORDER LINE entity types in the Data Model. An order relates to only one customer; therefore, an entity view for CUSTOMER exists. The details on the order form concern only one order; therefore, an entity view of ORDER exists.
The views for PRODUCT and ORDER LINE exist because each line on the order represents a different product. However, the correct product for each order line must always be referenced. Therefore, it is convenient to establish a group view that assembles the entity view of PRODUCT and the entity view of ORDER LINE.
The order form can be represented by an import group view named IN_GROUP_PRODUCT_INFORMATION. It contains the entity views Input Product (view of PRODUCT) and Input Order Line (view of ORDER LINE). The group view is defined as repeating because both entity views are imported for each line on the order.
group(r) IN_GROUP PRODUCT INFORMATION view of INPUT entity PRODUCT attr NUMBER view of INPUT entity ORDER_LINE attr QUANTITY
A group view can contain one or more work views. In the next example, the group view In_Group_Order_Line contains the work view that includes attributes from the work set IEF_SUPPLIED. The group view also contains the input entity view Input Customer_Order_Line.
The name of the group view should accurately reflect its contents. Unlike entity view names, group view names always stand alone in the process logic or the procedure logic. They should therefore carry the full weight of the meaning of their components. For example, if you are adding an import group view, you may want to use the naming system shown in the example, which is IN_GROUP followed by the name of the entity type.
Procedure Synthesis generates new view names when you specify processes to be implemented by a procedure.
The Consistency Check facility checks group views and subordinate entity views for conformance with the following rules:
Views for CREATE_ORDER Import Views group (r) IN_GROUP_ORDER_LINE view of CUSTOMER_WORK_AREA wrk set IEF_SUPPLIED attr COUNT attr FLAG view of INPUT entity CUSTOMER_ORDER_LINE attr QUANTITY attr NUMBER attr REQUESTING_UNIT
|
Copyright © 2014 CA.
All rights reserved.
|
|