問題: WIP Pending Resource Transactions中的資料停在Pending, resubmit無效
狀況:
1.Pending Resource Transactions中的資料停在Pending, 沒有error
2.只有在特定時間的兩個工單資料有此狀況
3.group_id有值, transaction_id是空的
4.後續進來的交易沒有問題
5.resubmit沒用
解法: 在table中把狀態改為error, 再resubmit, 好了. :O
目前看來, 可能是原先資料異常, 導致未被處理, 改成error後反而符合要處理的條件.
有篇文章沒派上用場, 但還是記一下:
Oracle WIP Jobs Pending Resource Transactions, Pending Transactions in WIP_COST_TXN_INTERFACE Table
https://oracleappsdna.com/2011/07/oracle-wip-jobs-pending-resource-transactions-pending-transactions-in-wip_cost_txn_interface-table/
2018年11月30日 星期五
2018年11月22日 星期四
Oracle EBS: 設定為incompatible的程式, 已submit後要改為可同時執行
先說解法:
在 Conflict Resolution Manager 上, 點擊 [Verify] 按鈕
Conflict Resolution Manager的Status欄會出現 Verifying 訊息, 待系統處理完後, 就會依現有設定檢查是否程式互斥, 已submit的程式也會變更為可同時執行.
這方法先前有試過, 不知為何無效, 再作一次就有成果, 是時間差還是業障太重.
再來說說走了哪些冤枉路:
1.直接修改fnd_concurrent_requests的queue_method_code和crm_tstmp欄位('I', null), 結果是concurrent不會被執行, 改回才正常
2.直接修改fnd_concurrent_requests的status_code和crm_release_date('I', sysdate), 沒用, 因為過沒多久又被系統改為原值
Ref:
Removed Incompatible To Itself But Still Runs Serial, Not Parallel : Must Use Conflict Resolution Manager > Verify Button (Doc ID 2448116.1)
在 Conflict Resolution Manager 上, 點擊 [Verify] 按鈕
Conflict Resolution Manager的Status欄會出現 Verifying 訊息, 待系統處理完後, 就會依現有設定檢查是否程式互斥, 已submit的程式也會變更為可同時執行.
這方法先前有試過, 不知為何無效, 再作一次就有成果, 是時間差還是業障太重.
再來說說走了哪些冤枉路:
1.直接修改fnd_concurrent_requests的queue_method_code和crm_tstmp欄位('I', null), 結果是concurrent不會被執行, 改回才正常
2.直接修改fnd_concurrent_requests的status_code和crm_release_date('I', sysdate), 沒用, 因為過沒多久又被系統改為原值
Ref:
Removed Incompatible To Itself But Still Runs Serial, Not Parallel : Must Use Conflict Resolution Manager > Verify Button (Doc ID 2448116.1)
2018年11月21日 星期三
2018年11月2日 星期五
Oracle EBS: AR關帳問題 (Credit Memo Incomplete)
狀況: user關帳執行Subledger Period Close Exception Report, 在Receivable有幾筆Credit Memo的Status是Incomplete.
嘗試單純的方式, 以Examine在Form上直接把complete_flag改為N, 存檔時出現APP_AR_11017 error , 失敗.
搜尋一些文章, 有個del_orphans_xla_120.sql可用, 但Oracle support上可能已把這檔案移掉, 找不到了.
最後處理方式:
1.以SQL找出orphan record, 比對與出問題的那幾筆相符
2.針對其中一筆以diagnostics功能查看資訊, XLA_EVENTS出現兩列資料, 其中一列的event_status_code和process_status_code都是P (10/4建立), 另一列則分別是I和U (10/15建立)
3.為避免刪資料會有問題, 直接把event_status_code和process_status_code都改為P
4.重跑Subledger Period Close Exception Report, 已無異常資料
不知是否會有其他影響, 後續再觀察.
SQL: Orphan records
from xla_events xe,
xla.xla_transaction_entities xte,
fnd_user users
where xe.created_by = users.user_id
and xte.entity_code = 'TRANSACTIONS'
AND xte.upg_batch_id is NULL
and xte.entity_id = xe.entity_id
and xte.application_id = 222
and xe.application_id = 222
and xe.event_status_code not in ('P','Z')
and not exists
(select 'x'
from ra_cust_trx_line_gl_dist_all dist
where dist.customer_trx_id = xte.source_id_int_1
and dist.posting_control_id = -3
and ((dist.event_id is null
and not exists (select 'x'
from ra_cust_trx_line_gl_dist_all dist2
where dist2.customer_trx_id = dist.customer_trx_id
and dist2.account_set_flag = 'N'
and dist2.latest_rec_flag = 'Y'
and dist2.account_class = 'REC'))
OR
dist.event_id = xe.event_id)
union
select 'x'
from ar_receivable_applications_all
where customer_trx_id = xte.source_id_int_1
and posting_control_id = -3
and event_id = xe.event_id
union
select 'x'
from ar_receivable_applications_all
where applied_customer_trx_id = xte.source_id_int_1
and posting_control_id = -3
and event_id = xe.event_id
)
Ref:
1.Orphan Records In XLA_TRANSACTION_ENTITIES table (Doc ID 1066982.1)
2.How to Find Orphan Records in Subledger Accounting Related to Oracle Receivables? (Doc ID 549020.1)
嘗試單純的方式, 以Examine在Form上直接把complete_flag改為N, 存檔時出現APP_AR_11017 error , 失敗.
搜尋一些文章, 有個del_orphans_xla_120.sql可用, 但Oracle support上可能已把這檔案移掉, 找不到了.
最後處理方式:
1.以SQL找出orphan record, 比對與出問題的那幾筆相符
2.針對其中一筆以diagnostics功能查看資訊, XLA_EVENTS出現兩列資料, 其中一列的event_status_code和process_status_code都是P (10/4建立), 另一列則分別是I和U (10/15建立)
3.為避免刪資料會有問題, 直接把event_status_code和process_status_code都改為P
4.重跑Subledger Period Close Exception Report, 已無異常資料
不知是否會有其他影響, 後續再觀察.
SQL: Orphan records
select xte.*, --xte.source_id_int_1 source_id,
users.user_name user_namefrom xla_events xe,
xla.xla_transaction_entities xte,
fnd_user users
where xe.created_by = users.user_id
and xte.entity_code = 'TRANSACTIONS'
AND xte.upg_batch_id is NULL
and xte.entity_id = xe.entity_id
and xte.application_id = 222
and xe.application_id = 222
and xe.event_status_code not in ('P','Z')
and not exists
(select 'x'
from ra_cust_trx_line_gl_dist_all dist
where dist.customer_trx_id = xte.source_id_int_1
and dist.posting_control_id = -3
and ((dist.event_id is null
and not exists (select 'x'
from ra_cust_trx_line_gl_dist_all dist2
where dist2.customer_trx_id = dist.customer_trx_id
and dist2.account_set_flag = 'N'
and dist2.latest_rec_flag = 'Y'
and dist2.account_class = 'REC'))
OR
dist.event_id = xe.event_id)
union
select 'x'
from ar_receivable_applications_all
where customer_trx_id = xte.source_id_int_1
and posting_control_id = -3
and event_id = xe.event_id
union
select 'x'
from ar_receivable_applications_all
where applied_customer_trx_id = xte.source_id_int_1
and posting_control_id = -3
and event_id = xe.event_id
)
Ref:
1.Orphan Records In XLA_TRANSACTION_ENTITIES table (Doc ID 1066982.1)
2.How to Find Orphan Records in Subledger Accounting Related to Oracle Receivables? (Doc ID 549020.1)
訂閱:
文章 (Atom)