Webcasts
Abstract
The IBM Sterling Order Management team delivered a webcast in preparation for the 2022 Holiday Peak season on the IBM Order Management SaaS platform on -
Thursday, May 19, 2022 @ 10:00AM | 1 hour | Eastern Daylight Time (New York, GMT-04:00)
We will follow this up with more sessions as we lead up to the holiday season
Content
IBM shared the latest lessons learned and best practices gathered across prior peak seasons along with an overview of issues seen over the prior year. It is imperative to understand your role in the partnership with IBM to proactively ensure performance, stability, scalability of your solution during your most critical business period of the year. Understand your role in this journey, and how IBM can partner with you to achieve success.
- Our IBM OMS Support mission aims to proactively partner with you to identify and address potential risk, while quickly mitigating any issue that does arise.
- Establish a stable platform and share robust collection of proven self-help best practices focused on peak performance and stability.
- Build a deeper understanding and engagement with clients needing direct proactive guidance via our Event Readiness offering
A recording of the session is available here.
A copy of the event readiness questionnaire is available here.
Presenters
Presenters
Q & A
Q: With regard to new reserveAvailableInventory API aggregation property (yfs.yfs.UseAggregatedReservationsForIV=Y), What are the scenarios where aggregation will not take place?
A: By design OMS-GIV reservation api support below listed cases and are the reasons for calling reservations separately for each line, for example:
- Different Reservation id at each line
- Expiration date is different at each line
- Segment/Segment Type info is provided at line
Q: The smart sourcing logic of IBM Sterling Inventory Visibility (phase 2) is disabled. Could you elaborate on smart sourcing being disabled please? Does this mean if there are 200 nodes with inventory, all of them will qualify for sourcing logic?
A: Smart sourcing depends on data from YFS_INVENTORY_ALERTS table populated by RTAM, but since IV does not leverage this table, the logic for smart sourcing is redundant, and as such it has been disabled to optimize performance. The sourcing is within OMS, without Smart sourcing, it will rely on the sourcing rules including the DG set , priorities et all. Refer to prior panel discussion to learn more about sourcing and optimization.
Q: When are we expecting new SST enhancements (Calendar, Banner message, Notification Inbox) to be rolled out?
A: The Calendar is available now. The banner messages and Inbox are coming later this year.
Q: Do we have any plan to add custom charts in Monitoring in Self service tool?
A: We are reviewing the Monitoring dashboards from a holistic standpoint for future enhancements. At this time, no plans for custom charts, though we can feed this back to our Product team.
Q: With regard to Safety Stock and Fulfillment Options (KC Link) API enhancement, how long will the current format of the PATCH APIs be supported before we can make the switch to the new API formats?
A: IBM will stop support for the older formats in January 2023.
Q: With regard to Safety Stock and Fulfillment Options (KC Link) API enhancement, how long will the current format of the PATCH APIs be supported before we can make the switch to the new API formats?
A: IBM will stop support for the older formats in January 2023.
Q: How can implementation team review the indexes in DB?
A: Following query can be executed via DB query client for a particular table to list all indexes:
SELECT * FROM SYSCAT.INDEXES WHERE TABNAME = 'YFS_ORDER_HEADER' WITH UR
Q: How can we quickly identify the most frequent errors across all servers and see where it's coming from in SST?
A: Agent and Integration Server Performance and Application Server Performance contains Error count by application and Error count by error type capturing this information. For more details refer to Dashboards and charts.
Q: With regard to log4j, how do we identify if third-party libraries have reference to log4j logic and how do we go about addressing it?
A: Detailed guidance has been provided here: Migrating to log4j2
Reading Material
The authors shared the following links to continue learning about the topic:
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"a8m50000000CbxrAAC","label":"Archive (DO NOT USE)->Sterling Order Management System->Performance"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Product Synonym
IBM Sterling Order Management On Cloud, OMoC
Was this topic helpful?
Document Information
Modified date:
24 May 2022
UID
ibm16588225