Webcasts
Abstract
The IBM Sterling Order Management team delivered a webcast in preparation for the 2023 Holiday Peak season on the IBM Order Management platform on -
18 May 2023 @ 10:00 AM | 1 hour 30 minutes | Eastern Daylight Time (New York, GMT-04:00)
Content
- Our IBM OMS Support mission aims to proactively partner with you to identify and address potential risks, while quickly mitigating any issue that does arise.
- Establish a stable platform and share a 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 through our Event Readiness offering
- Plan and take necessary action to position y(our) solution for peak success, it is critical to TAKE ACTION NOW!
Presenters
Mike Callaghan Program Director – WW Supply Chain Support
Shoeb Bihari Technical Lead and SRE Advisor – Order Management Support
Vijay Gosavi Development Lead - Payments - Order Management Support
Q & A
Q: Is rounding logic like HALF_EVEN possible?
A: In OMS, we round to the nearest penny with up to 6th decimal precision. Refer to Price precision.
Q: Will Dynamic CTR distribution be audited under the payment audit and reasons feature?
A: Yes it is audited.
Q: When using the Dynamic CTR feature, if we add a line to an existing order, will it change the order payment status to AWAIT_AUTH?
A: If we have partial authorization - that is, for another release - the payment status remains in AUTH status (the auth amount will be less than the order total). We will need to ensure we create another authorization for the new line release.
A: We can set java.util.Arrays.useLegacyMergeSort=true property. Refer to paymentCollection agent fails with java.lang.IllegalArgumentException
A: In such cases, the system decides on which authorization to use, but we also have the user exit OMPModifyChargeTransactionRequestMappingUE, which will allow us to to modify the system defined ChargeTransactionRequest mappings as needed.
A: This is not required for DB2, as-is, it uses the index.
Q: What is the recommended approach to handle INVOKED user exit status in the Charge transaction record?
A: The best way to handle this is to implement YFSValidateInvokedCollectionUE. For detailed information about the user exit, see the Javadoc.
Q: Is there any recommendation on how frequently we should explicitly be using ProcessOrderPayments API without impacting performance?
A: We should avoid using processOrderPayments API, as this API is intended for In-person scenarios - e.g., carry lines.
Note: This API cannot be used with any of the order modification APIs or any APIs that modify orders - either through events, multiApi calls, or services.
The requestCollection() API is invoked in a new transaction boundary and with a special condition - each Charge and Authorization request created will have UserExitStatus set to “ONLINE”. When requestCollection() is complete, it returns to processOrderPayments() and execute a commit in the new transaction boundary then close it. Thus, even if an error is thrown after this point, the database will not rollback the changes made by requestCollection(). Refer to javadoc for more details.
Instead of using processOrderPayments. Use requestCollection, executeCollection APIs explicitly.
Reading Material
The authors shared the following links to continue learning about the topic:
Related Information
Was this topic helpful?
Document Information
Modified date:
23 May 2023
UID
ibm16995885