Run an SQL statement, as shown in Example 3-2, to insert the required lookup value code, meaning, and description into the AIA_LOOKUPS_TL table.
![database workbench project example database workbench project example](https://i.pinimg.com/originals/68/42/c5/6842c59ee13b7a845473142752989450.png)
#Database workbench project example code
Replace the bold variable with the lookup value code that you want to add. Replace the bold variable with the type of lookup code that you want to use: INDUSTRY, PROJECT_STATUS, SERVICE_TYPE, TASK_SCOPE, or PRODUCT_CODE. ('USERENV', 'AUTHENTICATED_IDENTITY'), sysdate, 1 SYS_CONTEXT('USERENV', 'AUTHENTICATED_IDENTITY'), sysdate, SYS_CONTEXT INSERT INTO AIA_LOOKUPS_B (LOOKUP_TYPE, LOOKUP_CODE, PARENT_LOOKUP_CODE,ĬREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_ Run an SQL statement, as shown in Example 3-1, to insert the required lookup value into the AIA_LOOKUPS_B table.Įxample 3-1 SQL Statement Used to Insert Lookup Values into AIA_LOOKUPS_B Obtain confirmation from the Project Lifecycle Workbench user community that the lookup value to be added is necessary and valid. If a required lookup value is not available, use this procedure to add it.įor more information about working with projects, see Section 3.3, "Working with Project Lifecycle Workbench Projects."įor more information about working with service solution components, see Section 3.4, "Working with Project Lifecycle Workbench Service Solution Components." These lookup values are available for assignment to projects, business tasks, or service solution components. Service type, for use with service solution components Product code, for use with service solution components Project Lifecycle Workbench is delivered with the following sets of lookup values: A service solution component conveys the functionality that the AIA service artifact needs to fulfill.įor more information about the overall Oracle AIA Project Lifecycle, see Chapter 2, "Building AIA Integration Flows."
![database workbench project example database workbench project example](https://www.mysql.com/common/images/products/MySQL_Workbench_Documentation_Mac.png)
![database workbench project example database workbench project example](https://s3.amazonaws.com/nettuts/636_mysql/twoSchemas.png)
For example, a service solution component corresponds to an Application Business Connector Service (ABCS), Enterprise Business Service (EBS), or Enterprise Business Flow (EBF). These could be business processes, business activities, or business tasks and are loosely added to a project in the Project Lifecycle Workbench as business tasks.Ī service solution component is a chunk of functionality within the scope of a business task that is implemented as an AIA service artifact. The components of a project must be packaged and deployed on a middleware solution.Ī business task represents a reusable unit of work that is arrived at based on analysis of reference process models. The primary building blocks that enable functional decomposition in Project Lifecycle Workbench are:Ī project is a named effort to deliver a solution conforming to the AIA methodology and guidelines. The functional decomposition, the final output of the design and analysis process, is captured and persisted in Project Lifecycle Workbench. Project Lifecycle Workbench complements any existing design and analysis process with its various modeling and functional analysis mechanisms. Figure 3-1 Functional Decomposition of a Project into Actual Implemented Services