Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Categories Usability
Created by Guest
Created on Mar 26, 2024

Expand PCM correlation to allow bigger datasets of key and value pairs

PEM Standard / Partner Community Manager Correlation requirements

Customer has a use case where they will be processing large files in B2B via PCM and using ITX for translation. Translation will be outputting correlation data. The high-water mark of file size for the last 90 days was ~7gb and contained 66 million values under one correlation key (Tracking Number). The average number of correlation keys per file with be ~4.

The current design of correlation data storage in PCM has it taking all correlation values and storing them as a comma separated string in a single column (CORRELATION_VALUE[X] CLOB(1MB)) in the database (PETPE_TRANSFERINFO).  

Taking a tracking number (15 characters) and using the current design we are limited to around ~60,000 correlation values per key per document.

The current design doesnt allow for proper indexing of the CORRELATION_VALUE columns and search likely is using LIKE %SEARCHVALUE% which is highly ineffective across data sets and document volumes Customer will require.

The request for enhancement is to build a true relational database design for correlation key/value pairs that will allow for the volumes Customer needs.