Introducing Domain-Value Maps (DVM)
Domain-Value Maps enable mapping of vocabulary in one domain to another, which is useful
when different domains represent the same data in different ways. Applications that you want to
integrate often use different vocabulary to represent the same information. For example, one
domain might represent a city with a long name (Boston), whereas another domain may
represent a city with a short name (BO). In such cases, you can use a Domain-Value Map to
directly map values between multiple domains. A direct mapping of values between two or more
domains is also known as Point-to-Point mapping.
Each Domain-Value Map typically holds a specific category of mappings among multiple
applications. For example, one Domain-Value Map might hold mappings for city codes and
another might hold mappings for state codes
Features of Domain-Value Maps include:
• Qualifier Support: Allows you to validate a mapping using additional information
• Qualifier Order Support: Is used to find the best match during lookup at run time
• One-to-Many Mapping Support: Allows you to map one value to multiple values in a
Domain-Value Map
Steps to create & use DVM :
1) Create a DVM file with domains and there values
Like :
Domain(column)- short, long , combined
Value (Rows)- CA, California, California(CA)
Qualifier : Can be used to narrow down the match in case multiple values match . eg : CA for California, Cambridge etc. So Qualifier can be state.
2) Drop DVM lookup in XSL Mapper:
1. Select dvm
2. Select source column name , the source Domain
3. Source Value , from where the value is coming for mapping
4. Select Target column name , Target Domain
XREF
Using cross references, you can dynamically populate, maintain, and map values for equivalent
entities created by different applications. When creating, updating, and deleting objects in one
application, there may be a need to propagate the changes to other applications. For example,
when a new customer is created in a SAP application, you may need to create a new entry for the
same customer in your Oracle E-Business Suite application (EBS). However, since the
applications being integrated are using different entities and IDs to represent the same
information you need to cross reference these entities
Cross references are stored in table structures defined by an .xref file that you can create by
using JDeveloper. To use the cross reference table defined by an .xref file you need XSD
structures that defined the data to be cross referenced, the data itself, and a composite
application with either a Mediator or BPEL component containing an XSL transformation that
executes the appropriate XREF functions to populate, update, or look up cross references.
When you execute a function to populate a cross reference table, the data is stored in the
XREF_DATA table in a database referenced by the jdbc/xref JNDI name. By default, the
XREF_DATA table is created in the SOAINFRA schema created by the Repository Creation
Utility (RCU), which is used to create the Oracle SOA Suite 11g database schemas required
before installing Oracle SOA Suite 11g. Because the cross reference data is persisted in a
database it remains available for applications until explicitly deleted, preferably by using the
appropriate XREF functions
How to use :
1) Create Xref
The initial two End System entries, which appear as a of XML elements in a
XREF source file. Each End System represents a collection of unique reference values for
a given system. The actual cross reference values are created dynamically at run-time
2) Can add , delete new End systems
3) Populating Cross Reference Tables
Drag the populateXRefRow (or populateXRefRow1M) function into the middle column of the XSLT :
- The xrefLocation, specifies the directory and name of the .xref file defining the cross reference structure. Click the Browse (magnifying glass) icon to locate the file.
- The referenceColumnName, which is the primary End System name
- The referenceValue, which is the unique ID value in the primary End System
- The columnName, which is the End System name being cross referenced
- The value, which is the unique ID value in the End System being cross referenced
- The mode, which can be the value ADD, UPDATE, or LINK (in uppercase). ADD creates a new row, UPDATE modifies an existing row
4) Lookup xref using lookup xref
Delete using markforDelete
Example of Xref Table in DB :
Ref : http://oraclefusion1011.blogspot.com/2010/12/dvm-xref.html
Domain-Value Maps enable mapping of vocabulary in one domain to another, which is useful
when different domains represent the same data in different ways. Applications that you want to
integrate often use different vocabulary to represent the same information. For example, one
domain might represent a city with a long name (Boston), whereas another domain may
represent a city with a short name (BO). In such cases, you can use a Domain-Value Map to
directly map values between multiple domains. A direct mapping of values between two or more
domains is also known as Point-to-Point mapping.
Each Domain-Value Map typically holds a specific category of mappings among multiple
applications. For example, one Domain-Value Map might hold mappings for city codes and
another might hold mappings for state codes
Features of Domain-Value Maps include:
• Qualifier Support: Allows you to validate a mapping using additional information
• Qualifier Order Support: Is used to find the best match during lookup at run time
• One-to-Many Mapping Support: Allows you to map one value to multiple values in a
Domain-Value Map
Steps to create & use DVM :
1) Create a DVM file with domains and there values
Like :
Domain(column)- short, long , combined
Value (Rows)- CA, California, California(CA)
Qualifier : Can be used to narrow down the match in case multiple values match . eg : CA for California, Cambridge etc. So Qualifier can be state.
2) Drop DVM lookup in XSL Mapper:
1. Select dvm
2. Select source column name , the source Domain
3. Source Value , from where the value is coming for mapping
4. Select Target column name , Target Domain
XREF
Using cross references, you can dynamically populate, maintain, and map values for equivalent
entities created by different applications. When creating, updating, and deleting objects in one
application, there may be a need to propagate the changes to other applications. For example,
when a new customer is created in a SAP application, you may need to create a new entry for the
same customer in your Oracle E-Business Suite application (EBS). However, since the
applications being integrated are using different entities and IDs to represent the same
information you need to cross reference these entities
Cross references are stored in table structures defined by an .xref file that you can create by
using JDeveloper. To use the cross reference table defined by an .xref file you need XSD
structures that defined the data to be cross referenced, the data itself, and a composite
application with either a Mediator or BPEL component containing an XSL transformation that
executes the appropriate XREF functions to populate, update, or look up cross references.
When you execute a function to populate a cross reference table, the data is stored in the
XREF_DATA table in a database referenced by the jdbc/xref JNDI name. By default, the
XREF_DATA table is created in the SOAINFRA schema created by the Repository Creation
Utility (RCU), which is used to create the Oracle SOA Suite 11g database schemas required
before installing Oracle SOA Suite 11g. Because the cross reference data is persisted in a
database it remains available for applications until explicitly deleted, preferably by using the
appropriate XREF functions
How to use :
1) Create Xref
The initial two End System entries, which appear as a of XML elements in a
XREF source file. Each End System represents a collection of unique reference values for
a given system. The actual cross reference values are created dynamically at run-time
2) Can add , delete new End systems
3) Populating Cross Reference Tables
Drag the populateXRefRow (or populateXRefRow1M) function into the middle column of the XSLT :
- The xrefLocation, specifies the directory and name of the .xref file defining the cross reference structure. Click the Browse (magnifying glass) icon to locate the file.
- The referenceColumnName, which is the primary End System name
- The referenceValue, which is the unique ID value in the primary End System
- The columnName, which is the End System name being cross referenced
- The value, which is the unique ID value in the End System being cross referenced
- The mode, which can be the value ADD, UPDATE, or LINK (in uppercase). ADD creates a new row, UPDATE modifies an existing row
4) Lookup xref using lookup xref
Delete using markforDelete
Example of Xref Table in DB :
Ref : http://oraclefusion1011.blogspot.com/2010/12/dvm-xref.html
No comments:
Post a Comment