針對此需求, 要修改:
MTL_INTERCOMPANY_INVOICES.get_transfer_price
Ref:
1.How to Customize Intercompany Transfer Price and Derive Based on Average Cost
http://raghu-oracleapps.blogspot.com/2010/04/how-to-customize-intercompany-transfer.html
2.Transfer Price
http://www.oracleug.com/user-guide/general-ledger/transfer-price
2019年2月27日 星期三
2019年2月13日 星期三
Oracle EBS: Concurrent program returned no reason for failure
狀況:
1.concurrent program的status為Error
2.View Log中只有列出start的日期時間, 資訊不完整
3.View Details中, Completion Text的訊息為Concurrent program returned no reason for failure
檢查方式:
Concurrent
->Manager
-> Administer
-> Standard Manager
-> Processes
-> Internal Manager Log
依request id搜尋, 找到相符的資料為:
Found running request xxxxxx attached to dead manager process.
Setting request status to completed.
Found dead process: spid=(2734), cpid=(4737129), ORA pid=(114), manager=(0/11312)
原因: 進行控制的manager沒有在所有處理都完成後才停止(shut down)
避免此問題的方法:
1.要到所有處理都完成後, 再停止 internal manager
2.若有manager在還有處理動作進行時被停止, 而且internal manager已啟動, 可在OAM中執行Concurrent Manager Recovery
Ref:
1.Concurrent program returned no reason for failure
http://oracleexpertsolutions.blogspot.com/2013/01/concurrent-program-returned-no-reason.html
2.Concurrent program returned no reason for failure
https://oralinx.wordpress.com/2011/09/29/concurrent-program/
3.Why Are Dead Process Found In The Standard Manager Log File? [ID 246584.1]
1.concurrent program的status為Error
2.View Log中只有列出start的日期時間, 資訊不完整
3.View Details中, Completion Text的訊息為Concurrent program returned no reason for failure
檢查方式:
Concurrent
->Manager
-> Administer
-> Standard Manager
-> Processes
-> Internal Manager Log
依request id搜尋, 找到相符的資料為:
Found running request xxxxxx attached to dead manager process.
Setting request status to completed.
Found dead process: spid=(2734), cpid=(4737129), ORA pid=(114), manager=(0/11312)
原因: 進行控制的manager沒有在所有處理都完成後才停止(shut down)
避免此問題的方法:
1.要到所有處理都完成後, 再停止 internal manager
2.若有manager在還有處理動作進行時被停止, 而且internal manager已啟動, 可在OAM中執行Concurrent Manager Recovery
Ref:
1.Concurrent program returned no reason for failure
http://oracleexpertsolutions.blogspot.com/2013/01/concurrent-program-returned-no-reason.html
2.Concurrent program returned no reason for failure
https://oralinx.wordpress.com/2011/09/29/concurrent-program/
3.Why Are Dead Process Found In The Standard Manager Log File? [ID 246584.1]
2019年2月12日 星期二
Oracle EBS: fnd_lobs的檔案來源
select fad.seq_num, fad.entity_name, fad.pk1_value, fad.pk2_value
from fnd_attached_documents fad,
fnd_documents fd
fnd_lobs fl
where fad.document_id = fd.document_id
and fd.media_id = fl.file_id
Ref:
1.Oracle Apps: Helpful Queries on FND Attachments tables and sample code to extract attachments
http://johnytips.blogspot.com/2016/01/oracle-apps-helpful-queries-on-fnd.html
2.EBS Attachements表结构
https://blog.csdn.net/cunxiyuan108/article/details/6446698
2019年1月29日 星期二
Oracle EBS: 提早關期間的警告訊息
為因應長假, 提早關期間結帳, 出現警告訊息:
Caution: There are 57 hours remaining in the period. Do you still wish to continue?
user看到就緊張了, 從來沒出現過這種訊息, 但也查不到什麼相關資料, 照字面看就是要小心, 現行期間還有57個小時.
後來還是把期間關閉, 作業本身沒什麼問題, 但影響:
1.ASN不能cancel
2.工單不能release
user看到就緊張了, 從來沒出現過這種訊息, 但也查不到什麼相關資料, 照字面看就是要小心, 現行期間還有57個小時.
後來還是把期間關閉, 作業本身沒什麼問題, 但影響:
1.ASN不能cancel
2.工單不能release
2019年1月23日 星期三
Oracle EBS: PO拆shipment後, 新的shipment沒有產生supply資料
問題: PO拆shipment後, 新的shipment沒有產生supply資料
user作業:
1.PO拆shipment
2.改另一個PO line單價
3.送出approve, PO狀態為 IN PROCESS
以實測來看, 拆shipment時, PO狀態變為Require Reapproval, 此時新shipment的supply尚未寫入, user送approve, 造成這段時間沒有supply.
user作業:
1.PO拆shipment
2.改另一個PO line單價
3.送出approve, PO狀態為 IN PROCESS
以實測來看, 拆shipment時, PO狀態變為Require Reapproval, 此時新shipment的supply尚未寫入, user送approve, 造成這段時間沒有supply.
訂閱:
文章 (Atom)