Generating Dynamic Asset Tags in Oracle Fusion Using Oracle Integration Cloud (OIC)
Introduction
Recently, I worked on an asset integration project where asset records were created in an external Asset Tracking System (ATS) and then synchronized with Oracle Fusion Assets through Oracle Integration Cloud (OIC).
One of the business requirements appeared simple at first glance: generate a unique asset tag number automatically during asset creation.
However, as with most enterprise requirements, there were several complexities behind the scenes.
The business wanted asset tags to follow a predefined format based on asset category while ensuring uniqueness across the organization.
This article shares the approach we used, challenges encountered, and lessons learned during implementation.
Business Requirement
The client wanted asset tags generated automatically using the following format:
LAP0000001
LAP0000002
LAP0000003
For laptops,
FUR0000001
FUR0000002
for furniture, and so on.
The prefix depended on the asset category, while the numeric portion had to be sequential and unique.
Users should not manually enter the tag number.
Initial Approach
Our first thought was to generate the tag number directly within Oracle Fusion.
However, after discussions with the business team, we realized that asset creation requests originated from an external application before reaching Fusion.
Because of this, generating tags during integration made more sense.
This would ensure consistency regardless of how the asset was created.
Solution Architecture
The integration flow involved:
Asset Tracking System (ATS)
Oracle Integration Cloud (OIC)
Oracle Fusion Assets
When a new asset was submitted:
ATS sent the asset details to OIC.
OIC determined the asset category.
OIC generated the next available tag number.
OIC populated the tag number in the Fusion Asset payload.
Fusion created the asset with the generated tag.
This approach centralized tag generation logic within a single integration layer.
Determining the Prefix
The business maintained a mapping between asset categories and tag prefixes.
Examples:
| Asset Category | Prefix |
|---|---|
| Laptop | LAP |
| Furniture | FUR |
| Printer | PRT |
| Network Equipment | NET |
Instead of hardcoding values inside integrations, we maintained the mappings in OIC Lookup Tables.
This provided flexibility for future changes without requiring code modifications.
Generating the Sequence Number
The next challenge was generating the numeric portion.
For example:
LAP0000045
requires extracting the highest existing sequence for LAP and incrementing it.
The integration queried existing asset records and identified the latest sequence number associated with the prefix.
Once identified, the next value was generated.
Example logic:
Current Highest Tag:
LAP0000045
Generated Tag:
LAP0000046
The value was then padded with leading zeros to maintain a consistent format.
OIC Mapping Logic
The tag generation process involved:
Read asset category.
Retrieve prefix from lookup.
Fetch latest sequence.
Increment sequence.
Pad sequence with leading zeros.
Concatenate prefix and sequence.
Result:
LAP0000046
The generated value was mapped directly into the Fusion Assets payload.
Challenges Faced
Concurrent Asset Creation
One challenge appeared during testing.
Multiple users were creating assets simultaneously.
Without proper controls, two transactions could potentially generate the same sequence number.
To avoid duplicates, sequence generation was moved to a controlled database process that guaranteed uniqueness.
This eliminated race conditions and ensured reliable tag generation.
Legacy Asset Records
Another challenge involved historical assets.
Many older records contained inconsistent tag formats.
Before implementing the solution, we performed a data assessment exercise to identify existing numbering patterns and determine the correct starting sequence.
This prevented collisions with historical asset tags.
Error Handling
Tag generation failures should never create incomplete assets.
We implemented validations to ensure:
Prefix exists.
Sequence generation succeeds.
Generated tag does not already exist.
Asset category is valid.
Any failures were logged into the integration error framework and routed to support teams for investigation.
Benefits Achieved
After deployment, the organization experienced several benefits:
Elimination of manual tag entry.
Consistent tag formatting.
Reduced data entry errors.
Improved asset traceability.
Simplified reporting and auditing.
Support teams also appreciated having a single location where tag generation logic was maintained.
Lessons Learned
Looking back, the biggest lesson was that seemingly simple requirements often contain hidden complexity.
Generating an asset tag is not just about concatenating a prefix and a number. Considerations such as concurrency, historical data, maintainability, and future scalability are equally important.
Another key takeaway was the value of using OIC lookup tables instead of hardcoded mappings. This significantly reduced maintenance effort when business requirements changed.
Conclusion
Dynamic asset tag generation is a common requirement in enterprise asset management projects. By leveraging Oracle Integration Cloud and a centralized numbering strategy, organizations can ensure consistency, accuracy, and scalability.
While every implementation will have unique business rules, the principles of centralized logic, controlled sequence generation, and robust error handling remain critical for success.
The solution described here helped streamline asset creation processes and provided a reliable foundation for future growth within the asset management ecosystem.
Comments
Post a Comment