Unified Reference ID- EDMCS for import and subscription request, instead of separate request IDs
Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):
CITI Corp
Description (Required): Currently, Oracle EDMCS provides two separate reference IDs: one for the import process and another for its corresponding subscription. This architectural design creates a disjoint in tracking related operations.
Use Case and Business Need (Required): The generation of separate reference IDs for import and subscription processes introduces additional complexities and checks for validation to accurately determine if an import and its lineage subscription have completed successfully, or to diagnose any related issues, users must correlate two distinct IDs. This process is prone to errors and lacks efficiency.