IBM Data and AI Ideas Portal for Customers


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

Post 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 product management 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 notification 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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Created by Guest
Created on Apr 8, 2019

Detail exact trigger for missing or late files

HNB requests IBM to find a better solution for more exact triggering for Missing or Late files; FTM can't provide the detail we expect and creates too many false positives when used for this. We want to be able to specify the Incoming ACH verses the Incoming ACH Return file is missing; we want to be able to

Look at a specific time and know if all the debit card reconcilement files have arrived.

Here you go, hope this helps.

1) FTM Email Notification: “Possible Missing HOPS file-Check FTM Console to review inbound transmissions: TRH00010W” is for “TRH00010W Warning Message - HOPS is looking for an overdue inbound file it was expecting.” My understanding it was supposed to look for Inbound ACH & ACH Return files that are pasted the Expected Transmission time. Instead of only looking for these files, it was triggering the email on every payment file that came into HOPS after the Expected Transmissions times. It started to send at least 1000 email notifications a day so the notification was shut off. It’s defect QC 7075/TFS 7452 & PMR TS001912920.

(2) Currently there is no good notification being sent separately in regards to when an ACH or an ACH Return file has been sent in by an expected time. We have to manually monitor the inbound ACH & ACH return files to ensure they’ve been received & accepted. Need a more robust notification setup to notify when separate incoming files are late or missing and provide information on what file type is missing (Inbound ACH, ACH Returns, etc), not just a general statement that an “overdue inbound file is missing” (Warning TRH00010W).

(3) For the Debit Card Settlement & Reconciliation files - There is no notification or alert as to when these files are late or haven’t been received. We have to manually monitor the email notifications each day on whether they have arrived by a specific time. If the email notifications are missing, it means that the files are missing and action is needed like contacting Visa or Mastercard or EWS to question the delay. This requires constant monitoring on a daily basis and without an alert, it’s possible to miss an expected file especially on the weekends.

  • Guest
    Sep 22, 2021

    Restbet the use of transmission types as a way to solve at least some of this with configuration. Betpas

  • Admin
    Craig Rector
    Oct 8, 2020

    We are looking at this item, but wanted to let you know that you can differentiate NACHA returns from NACHA forward files by using a different file name extension and transmission type in the interim.

  • Guest
    Sep 27, 2019

    Here you go, hope this helps.

     

    1) FTM Email Notification:   “Possible Missing HOPS file-Check FTM Console to review inbound transmissions: TRH00010W”  is for “TRH00010W Warning Message - HOPS is looking for an overdue inbound file it was expecting.”    My understanding it was supposed to look for Inbound ACH & ACH Return files that are pasted the Expected Transmission time.  Instead of only looking for these files, it was triggering the email on every payment file that came into HOPS after the Expected Transmissions times.  It started to send at least 1000 email notifications a day so the notification was shut off.  It’s defect QC 7075/TFS 7452 & PMR  TS001912920.

     

    (2) Currently there is no good notification being sent separately in regards to when an ACH or an ACH Return file has been sent in by an expected time.  We have to manually monitor the inbound ACH & ACH return files to ensure they’ve been received & accepted.   Need a more robust notification setup to notify when separate incoming files are late or missing and provide information on what file type is missing (Inbound ACH, ACH Returns, etc), not just a general statement that an “overdue inbound file is missing” (Warning TRH00010W). 

     

    (3) For the Debit Card Settlement & Reconciliation files -  There is no notification or alert as to when these files are late or haven’t been received.  We have to manually monitor the email notifications each day on whether they have arrived by a specific time.  If the email notifications are missing, it means that the files are missing and action is needed like contacting Visa or Mastercard or EWS to question the delay.  This requires constant monitoring on a daily basis and without an alert, it’s possible to miss an expected file especially on the weekends.

  • Admin
    Craig Rector
    May 9, 2019

    We need more specifcs around use cases here,  and we need to explore the use of transmission types as a way to solve at least some of this with configuration.