Troubleshooting
Problem
Diagnosing The Problem
- Gathering information to open a support ticket
- How to submit diagnostic data to IBM Support
- General IBM Support hints and tips
- Must Gather Index Page for IBM Sterling Order Management System
Gathering information to open a support ticket
A valid IBM customer number, contact name, email address, and phone number are important to validate the entitlement and contact information.
Refer to the section "Accessing Software Support" in the IBM Software Support Handbook to have the full list of information necessary to open a support ticket.
To determinate the correct Severity of your concern for your business, refer the IBM Software Support Handbook.
|
A. Provide answers to all of the following before you gather problem-specific information requested in part B.
|
-
Describe the Business Impact (current/future) due to this problem
-
Indicate any project timelines impacted.
-
What is the current impact on users? How many users are affected?
-
How frequently is the issue seen - once/multiple times a day/week, intermittently/consistently?
- Tenant Details
- Production/Non-Production
- Tenant Id
- Carrier
- Carrier Management - Legacy or CAS
- When did the issue start? Were there any recent changes to the system such as a new deployment, functionality roll-out etc.?
- Provide detailed replication steps for Support to test the issue along with any relevant screenshots.
- Is this a new flow being tested or was it working before?
- Capture a .HAR file by following the steps outlined here.
- Capture developer console logs by following the steps outline here.
- If you have SIP deployed on Containers, see the corresponding IBM Sterling Intelligent Promising Containers MustGather.
|
B. Find the problem that best describes your situation. This lists the diagnostics that IBM Support team requires to review your problem.
|
For issues pertaining to any of the Promising Calculation APIs, capture and share the following diagnostics:
- Is the issue observed from the REST Client or Order Hub?
- If the issue is observed on Order Hub, verify the behavior by directly calling the API with the same API input, and share the observations.
- What is the API request and body used?
- What is the response received?
- For issues with Promising Calculations, follow the steps in the Troubleshooting Promising Calculations documentation to capture diagnostics.
- Unable to view EDD Simulator in the Promise and Fulfill Menu
- Screen prints of:
- Order Hub UI.
- User Configuration in OMoC, Applications Manager -> Application Platform(Enterprise) -> Security -> Users -> <User Name>
- Resource Permissions set in User Group associated with the impacted user or users, Applications Manager -> Application Platform(Enterprise) -> Security -> Groups
- Screen prints of:
-
EDD screen is rendered blank
- Screen print of the Order Hub UI.
- Inconsistency in the output of EDD Simulator
- Provide multiple example inputs and outputs that show the inconsistent behavior.
- Invoke EDD API directly through a rest client by using same data passed in the EDD Simulator and share the API input and output.
- Unable to view Sourcing Tester in the Promise and Fulfill Menu
- Screen Print of:
- Order Hub UI.
- User Configuration in OMoC, Applications Manager -> Application Platform(Enterprise) -> Security -> Users -> <User Name>.
- Resource Permissions set in User Group associated with the impacted User/Users, Applications Manager -> Application Platform(Enterprise) -> Security -> Groups.
- Screen Print of:
- Sourcing Tester screen is rendered blank
- Screen Print of Order Hub UI.
- Inconsistency in the output of Sourcing Tester
- Provide multiple example inputs and outputs that show the inconsistent behavior.
- Invoke getSourcingConfig REST API directly using same input passed to the Sourcing Tester. Share the API input and output.
- Name of file processed
- What time was the process initiated?
- What is the concern?
- Did you receive an email - success/failure notification?
- If you are sending data via an API - Provide the API input and output
- Provide COS bucket name
- Provide client side logs
- Share a screenshot of the optimization settings page
- Share the error for derived capacity if it is set
- Issue description with the expected behavior vs actual observation
- Share the order number
- Issue description
- Screenshot of UI from the Order Hub application
For issues with Inventory Visibility, please refer to the Inventory Visibility Must Gather to capture diagnostics.
- After you collect the preceding information and a support ticket is opened, follow the instructions in: exchanging information with IBM Technical Support for problem determination
- For more information, see submit diagnostic data to IBM (ECuRep) and Enhanced Customer Data Repository (ECuRep)secure upload.
- If you are using IBM Community Portal, update the case to indicate that data is sent.
Here you can find a list of useful links for IBM Order Hub and the Support processes:
- IBM Sterling Intelligent Promising Documentation
- IBM Sterling Intelligent Promising What's New Section
- IBM Sterling Order Management System Support 101 page
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
18 July 2025
UID
ibm17171658