Skip Headers
Oracle® Fusion Applications Developer's Guide
11g Release 6 (11.1.6)

Part Number E15524-11
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

Part II

Defining Business Services

This part of the Developer's Guide discusses business services and service-oriented development, defaulting and derivation logic, creating validation rules, and using messages in Oracle Fusion Applications. It provides information about the Oracle Fusion Middleware Extensions for Applications base classes and describes how to share reference data across organizations by using set IDs to partition the data into different sets of values. Also included is how to implement lookups and simple lookups.

The Getting Started with Business Services chapter provides overviews of ADF Business Components, services, validators, list of values (LOVs), and data types. It also discusses migrating PL/SQL to Java, batch processing, and extensibility and reusability.

Service-oriented development is based on the concept of services. It is the realization of business functionality via software that customers can use to compose new business applications by using existing services in the context of new or modified business processes. The Developing Services chapter describes how to design the service interface, how to develop and invoke services. It also provides information about service versioning.

Defaulting logic means assigning attribute values when a row or entity object is first created or refreshed and is achieved either declaratively in the attribute's default field or programmatically by adding code to the EOImpl file. Derivation logic means assigning attribute values when some other attributes have changed. Derivation is achieved either declaratively in the transient attribute's default field or by using a validator, or programmatically by adding code to the EOImpl file. This chapter provides the information you need to determine whether to implement defaulting or derivation logic.

The Message Dictionary and Messages Resource Bundles are used to store messages for display from your application without hard-coding them into your forms and programs. By using the Message Dictionary and resource bundles you can define standard messages that you can use in all your applications, provide a consistent look and feel for messages within and across all your applications, define flexible messages that can include context-sensitive variable text, and change or translate the text of your messages without regenerating or recompiling your application code. The Defining and Using Message Dictionary Messages chapter provides an overview of Message Dictionary messages and discusses how to use them in Oracle Fusion Applications.

Using Fusion Middleware Extensions for Oracle Applications Base Classes provide additional features that are not part of the standard ADF Business Components core entity objects, view objects, and application modules. The Middleware extensions support Oracle Applications features such as TL (translatable) table, WHO column, PL/SQL entity, FND services, Unique ID, and document sequencing. In JDeveloper, selecting the Oracle Fusion Applications Developer role automatically sets the Middleware extensions for Oracle Applications base classes as the default classes for ADF Business Components objects. The base classes become available when you add the Applications Core library. This chapter describes the Oracle Fusion Middleware extensions for Oracle Applications base classes that extend the features of standard ADF Business Components classes.

Unique ID generation provides a mechanism to manage the key-generation process and to ensure that it runs without interruption. The process efficiently generates distinct sets of IDs in different databases for the same table, ensuring that the same key is never used for two different records created in different systems.

SetIDs enable different organizations within a single company to use different sets of reference data to serve the same purpose. For example, the job codes for one country might be different from the job codes for another country. Each organization can maintain its job code data in the same table, using a set of values that is specific to that organization. You use set IDs to partition the table into different sets of values so that each organization can identify and access its own data. In addition to tables, other sources of reference data such as lookup types and views can also be partitioned and shared using set IDs. These are all generically referred to as reference entities. This chapter describes how to share reference data across organizations by using set IDs to partition the data, implement shared reference entities, extract and expose set ID metadata, and implement shared lookups.

Lookups in applications are used to represent a set of codes and their translated meanings. For example, a product team might store the values 'Y' and 'N' in a column in a table, but when displaying those values they would want to display "Yes" or "No" (or their translated equivalents) instead. Each set of related codes is identified as a lookup type. There are many different examples of these across Oracle applications.

A document sequence uniquely numbers documents generated by an Oracle Applications product. Using Oracle Applications, you initiate a transaction by entering data through a form and generating a document, for example, an invoice. A document sequence generates an audit trail that identifies the application that created the transaction, for example, Oracle Receivables, and the original document that was generated, for example, invoice number 1234.

This part contains the following chapters: