Webcasts
Abstract
Now is the time to get familiarized with some of the important best practices to follow while using IBM Sterling Order Management.
Join our panel of experts for a session on 'Best Practices' while using the IBM Sterling Order Management platform, to proactively prepare for a peak success.
Content
Date/Time:
Thursday, August 1, 2024, 10:00 AM - 11:30 AM Eastern Time (US & Canada)
Agenda:
As part of the ongoing Event Readiness 2024 series, IBM Support and Development subject matter experts are coming together to explain some of the best practices to follow while using the IBM Sterling Order Management platform.
In this session, we will be covering best practices around CDT, customization, common performance guidelines around large order performance, containers, and Sterling Intelligent Promising.
Presenters:
Chirs Burgess - Manager, IBM Software Support (Sustainability SW Critical & Strategic Account Mgmt)
Mike Callaghan - Program Director, WW Supply Chain Support, IBM Sustainability Software
Shoeb Bihari - Executive IT Specialist | SRE Architect | SWAT IBM Sterling Order Management Solutions
Vishal Arora - Technical lead, Development | IBM Sterling Order Management Solutions
Senthil Ponnusamy - Technical Lead | SRE Advisor | IBM Sterling Order Management Solutions
Jitendra Buge - Technical Lead | IBM Sterling Order Management Solutions
Mike Callaghan - Program Director, WW Supply Chain Support, IBM Sustainability Software
Shoeb Bihari - Executive IT Specialist | SRE Architect | SWAT IBM Sterling Order Management Solutions
Vishal Arora - Technical lead, Development | IBM Sterling Order Management Solutions
Senthil Ponnusamy - Technical Lead | SRE Advisor | IBM Sterling Order Management Solutions
Jitendra Buge - Technical Lead | IBM Sterling Order Management Solutions
Paresh Vinaykya - Executive Technical Account Manager, Expertise Connect, IBM Expert Labs
Mohamed Jawahar - Technical Lead | IBM Sterling Order Management Solutions
Madhavi Pilaka - Technical Support Engineer | IBM Sterling Order Management Solutions
Damini Tacouri - Technical Support Engineer | IBM Sterling Order Management Solutions
Mohamed Jawahar - Technical Lead | IBM Sterling Order Management Solutions
Madhavi Pilaka - Technical Support Engineer | IBM Sterling Order Management Solutions
Damini Tacouri - Technical Support Engineer | IBM Sterling Order Management Solutions
Session Material:
Q&A:
Q - What is the best way to compare CDTs from 2 different environments in OMoC?
A - CDT import process related logs in SST gives the comparison overview about number of records between source and target tables.
A - CDT import process related logs in SST gives the comparison overview about number of records between source and target tables.
Q - How is IBM addressing issues happening due to JMS maintenance on IBM end?
A - As part of weekly maintenance in nextgen environment, MQ server might get failed over and that might force off all active connections momentarily; but like any other high availability setup, systems connecting to MQ servers should have the re-connection/retry mechanism in place to make sure systems are reconnected fine.
A - As part of weekly maintenance in nextgen environment, MQ server might get failed over and that might force off all active connections momentarily; but like any other high availability setup, systems connecting to MQ servers should have the re-connection/retry mechanism in place to make sure systems are reconnected fine.
Q - Is it right to say that we should minimize the sourcing sequence for better performance?
A - It is not just the sourcing sequence that matters but the number of DGs and the number of nodes within the DG also matters. If you reject assignments then the number of solutions will be lesser, making the API quicker. So, one needs to find the breaking point based on the requirement. Failure to find optimal solution can also trigger next sequence to be evaluated, so the configuration is purely based on the setup and data.
A - It is not just the sourcing sequence that matters but the number of DGs and the number of nodes within the DG also matters. If you reject assignments then the number of solutions will be lesser, making the API quicker. So, one needs to find the breaking point based on the requirement. Failure to find optimal solution can also trigger next sequence to be evaluated, so the configuration is purely based on the setup and data.
Q - How does system makes an entry into YFS_TASK_Q table to separate the order/orderline if it is BackOrder or NewOrder, to have dedicated schedule agent to process only Backorder and NewOrder, like OrderFilter=N|B which was explained in one of the slides?
A – When backorder happens, product will internally apply the logic and stamp the TRANSACTION_KEY of schedule agent (having OrderFilter agent criteria set as B) into YFS_TASK_Q table.
On a side note, product also provides one additional feature i.e. workload separation feature, which works via YFS_TASK_Q.FILTER_CRITERIA column. OrderFilter and workload separation are two different features though. OrderFilter can be used regardless of size of the order and It's used to reprocess backorders; while workload separation provides flexibility to prioritize and run a specific type of workload with required capacity to scale up the agent processing for individual workload.
For more details refer to -
https://www.ibm.com/docs/pl/order-management?topic=transactions-schedule
https://www.ibm.com/docs/en/order-management?topic=reference-workload-segregation-task-queue-agents
A – When backorder happens, product will internally apply the logic and stamp the TRANSACTION_KEY of schedule agent (having OrderFilter agent criteria set as B) into YFS_TASK_Q table.
On a side note, product also provides one additional feature i.e. workload separation feature, which works via YFS_TASK_Q.FILTER_CRITERIA column. OrderFilter and workload separation are two different features though. OrderFilter can be used regardless of size of the order and It's used to reprocess backorders; while workload separation provides flexibility to prioritize and run a specific type of workload with required capacity to scale up the agent processing for individual workload.
For more details refer to -
https://www.ibm.com/docs/pl/order-management?topic=transactions-schedule
https://www.ibm.com/docs/en/order-management?topic=reference-workload-segregation-task-queue-agents
Q - With API Input Limit for Sku-Location, Can I query 100 kits (where 1 kit can have 10 components) ?
A - Inventory reservation, supply and demand update are for components.
If its OMS OOTB integration API call, it will split and aggregate availability for components, and kit item fulfillment should be done as it’s done now.
A - Inventory reservation, supply and demand update are for components.
If its OMS OOTB integration API call, it will split and aggregate availability for components, and kit item fulfillment should be done as it’s done now.
Additional Resources:
[{"Type":"MASTER","Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"a8m0z000000cy01AAA","label":"Performance"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Product Synonym
IBM Sterling Order Management; OMS; OMoC; Sterling Intelligent Promising; SIP;
Was this topic helpful?
Document Information
Modified date:
04 September 2024
UID
ibm17160308