IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

OMoC platform cap of 1MB for the YFS_EXPORT.MESSAGE needs to be increased

To troubleshoot/debug issues we need to log outgoing/incoming messages to yfs_export table and few messages are more than 1 MB. Service fails if YFS_EXPORT.MESSAGE is more than 1 MB.This imitation needs to be increased as DB2 supports 2GB of CLOB data to be stored in YFS_EXPORT.MESSAGE.

  • Guest
  • Oct 29 2020
  • Submitted
How will this idea be used?

As part of the design TB is capturing Email XMLs in YFS_EXPORT table.

An email is sent to customer ON_SUCCESS of CREATE_CONFIRM_SHIPMENT transaction and email XML is stored in YFS_EXPORT.

For a specific order (790007814) the email XML posting to YFS_EXPORT is failing with error "The data bound to the column is invalid in this context." SQLState Value=22001.

Below is the query

INSERT INTO YFS_EXPORT(EXPORT_KEY,SYSTEM_NAME,API_NAME,FLOW_NAME,SUB_FLOW_NAME,USER_REFERENCE,STATUS,MESSAGE,REPLY_TO_ID,FROM_ORG_CODE,TO_ORG_CODE,ENTERPRISE_KEY,SHIP_NODE,PRIORITY,CREATEUSERID,MODIFYUSERID,CREATEPROGID,MODIFYPROGID,CREATETS,MODIFYTS,LOCKID) values ( '202010141853251216394464',' ',' ','TBEmailMsgToDB','YIFTBEmailMsgToDB',' ','00','A-Clob-Value','10.171.245.20816027016051110000000052301',' ',' ',' ',' ',0.0,'TBProcessDCMessageIntegServer','TBProcessDCMessageIntegServer','TBProcessDCMessageIntegServer','TBProcessDCMessageIntegServer','2020-10-14T18:53:25','2020-10-14T18:53:25',0 )

The length of the XML to be inserted in CLOB column is 1359320 in Unicode. The length allowed for CLOB in DB2 is 2 GB.

What is your industry? Retail
What is the idea priority? High
  • Attach files