Use Case
In many enterprise integrations, multiple projects need to reference the same configuration data such as:
- SFTP locations
- Integration IDs
- File paths
- Environment-specific values
Maintaining separate lookup files for each project leads to:
- Data inconsistency
- High maintenance effort
- Deployment overhead across environments
To avoid this, we use a Shared Lookup (DVM) that can be accessed across different OIC projects using the built-in function:
dvm:sharedLookupValue()
This ensures centralized configuration management and reusability.
Solution Approach
We store common configuration values in a Shared Lookup (DVM) under one project and access it from another project using the sharedLookupValue function inside an Assign action.
✅ Step 1: Create a Shared Lookup
In the source project:
- Create a lookup (DVM) named:
Common_CCS_Interface_SFTP_Lookup - Example structure:
| IntegrationId | SourceFileLocation |
|---|---|
| INT105 | /ftp/inbound/path |
✅ Step 2: Call Shared Lookup from Another Project
In the target project, use an Assign Action with this expression:
dvm:sharedLookupValue(
'CUSTOMER_BO2_01',
'Common_CCS_Interface_SFTP_Lookup',
'IntegrationId',
'INT105',
'SourceFileLocation',
'NA'
)
Parameter Explanation
| Parameter | Description |
|---|---|
CUSTOMER_BO2_01 |
Source project code |
Common_CCS_Interface_SFTP_Lookup |
Shared lookup name |
IntegrationId |
Source column |
INT105 |
Source value |
SourceFileLocation |
Target column |
NA |
Default value if no match found |
- ✅ Single source of truth
- ✅ Reduced deployment effort
- ✅ Easy maintenance
- ✅ Cross-project reusability
- ✅ Environment-specific control
Conclusion
Using dvm:sharedLookupValue in Oracle Integration Cloud enables seamless sharing of lookup values across projects, improves governance, and significantly reduces operational overhead. This approach is highly recommended for managing common SFTP paths, integration identifiers, and environment configurations in large OIC programs.
No comments:
Post a Comment