Production Issue: Drop ship order line workflow issue

orapeasant

于 2008-10-06 15:22:00 发布

阅读量1k

点赞数

分类专栏： Oracle Apps 文章标签： workflow archive table

本文链接：https://blog.csdn.net/orapeasant/article/details/3022362

版权

Oracle Apps 专栏收录该内容

39 篇文章

订阅专栏

本文讨论了一起废弃工作流导致的订单处理问题。在dropship订单中，由于标准的清理和归档程序错误地清除了保留订单，使得这些订单被不当处理并完成结账流程。文章深入探讨了工作流系统的缺陷，并揭示了故障诊断过程中的关键挑战。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Recently I closed a case of troubleshooting work flow issue in a drop ship order line. The order went through an obsolete workflow and get invoiced and closed while some holds exist, which is absolutely impossible.

In wf_activity_status WF_ITEM_ACTIVITY_STATUSES, the 'eligiblity' is in 'COMPLETE' status while it should return on_hold. after checking the hold table, the exact hold is there. Later, we found out it's the standard purge and archive program that purge the holds but restored holds 6 hours later. It's just in this 6 hours, these Drop ship orders got processed and workflow got pushed forward. The trap in the troubleshooting is the wf_item_activity_stauses table, the wf engine always update the last 'eligibility' activity and records the latest timestamp , thus it's difficult to know whether it's triggered hundreds of times in the past and completed at last.