Import entity views are views of entities that are input to a process, procedure, or action block during execution. These views consist of the information input through a screen or window.
The name of an entity view should always modify the entity type name. The combination of entity view name and entity type name must be unique within a process.
In Analysis, if one occurrence of an entity is in the import view subset, you can distinguish import view names from export view names by using a name such as INPUT for entity views. For example, if you add import views for the entities EMPLOYEE, DIVISION, and COST CENTER, the entity views may be named INPUT EMPLOYEE, INPUT DIVISION, and INPUT COST CENTER. This naming convention is useful when you work with long lists of views and want to see the information you are importing quickly.
Based on the needs of information imported to the process, you can add more than one occurrence of an entity to an import view subset. For example, consider the situation where information is required from two separate CUSTOMERS in the same execution of a process. In this case, the process requires two import views of the same entity type, thus making the combination of the entity type (CUSTOMER) name and the view name (input) insufficient to distinguish between the two views. Each entity view must have a unique name.
Procedure Synthesis generates new view names when you specify processes to be implemented by a procedure.
The Consistency Check facility checks entity views for conformance with the following rules:
|
Copyright © 2014 CA.
All rights reserved.
|
|