作者: jianping.ni 時間: 2009-2-13 12:52 标題: Oracle EBS R12經驗談（二）
OAF頁面:銀行帳戶開戶人LOV值清單無值
在輸入 應付超級使用者職責/Setup : Payment/銀行帳戶/建立銀行帳戶：帳戶開戶人和用途
中的銀行帳戶開戶人字段時,不要選擇邊上的LOV值清單(選了也白選,因為沒有值可選,是bug),
直接在該字段輸入法人實體
作者: jianping.ni 時間: 2009-2-13 12:52
付款儲存時，報如下錯誤:
Document Payer Bank Branch Type is required.
Document Delivery Channel is required.
Document Payee Bank Branch Type is required.
Document Payee Bank Instruction Code 2 is required.
措施:
定義
AP Super User/Setup/Payment/Bank Accounts/Manage Payment Documents/Update/
Document Information/Format Standard Check Format
作者: jianping.ni 時間: 2009-2-13 12:52
一/子帳定義驗證失敗
經過對驗證的并發請求進行TRACE，沒找到關鍵問題
然後啟用PROFILE :FND:DEBUG LOG,檢查FND_LOG_MESSAGES表獲得詳細的程式執行資訊，發現原來是沒有考慮UTF8的問題，導緻xla_cmp_string_pkg程式執行失敗.
解決方法：
将xla_cmp_string_pkg裡的
xla_cmp_string_pkg.g_Max_line CONSTANT NUMBER ：＝255 修改為80
從255改為80，這樣就肯定不會錯了。理由：255/3=86，是以，80個字元長不會報錯。
二/workflow的圖不能打開，報Cannot View Workflow Status Monitor. Start: Applet Not Initialized
解決方法：
1. Run Adadmin and regenerate all the jar files with FORCE option.
2. Clear Jinitiator cache on client PC.
3. Clear Apache cache and bounce Apache.
4. Retest the problem by logging out and logging back in.
參考文檔：Note:304662.1
三/OPM費用配置設定代碼的彈性域不能儲存（儲存後再查就沒有了），能打開
解決方法：檢視FORM的原代碼，發現根本沒有ATTRIBUTE字段，手工添加這幾個字段到FORM中(别看這是低級問題，但很不好查，開始把我給搞蒙了）
四/打開http://erpdb.cnnice.com:8001登陸位址時，沒有任何錯誤，但是什麼也不做，蒙吧，根本沒任何資訊
解決方法，根據登陸頁面的JSP頁面到METALINK去找相關類似的資訊，果然找到個文檔：Note:435550.1：R12 Login issue on target after cloning
過程步驟：
1. cd $FND_TOP/patch/115/bin
2. ./ojspCompile.pl --compile --flush -p 2
3. Bring up the services and test login
問題原因： $COMMON_TOP/_pages 下的檔案被人删除了，是以，12版本很不同的地方是，_pages在我們看來，肯定是屬于緩存檔案，應該是可以删除的，但是就是不能删除，删除就有問題了。需要重新編譯。
作者: jianping.ni 時間: 2009-2-13 12:53
io wait特别大，而基本上無人使用ebs，也沒有運作的request，發現資料庫程序特别多
一看，原來是oracle10g資料庫自動在收集統計資料。。。
這個自動收集的時間點也太不正常了吧，在工作時間運作，占用大量系統資源，
将它disable掉先
[轉自metalink]How to Disable Automatic Statistics Collection in 10G
Solution
1)To Disable the automatic statistics collection in 10G , you can execute the following procedure :
EXEC DBMS_SCHEDULER.DISABLE('GATHER_STATS_JOB')';
2) To check whether the job is disabled, run the following QUERY:
SQL> SELECT STATE FROM DBA_SCHEDULER_JOBS WHERE JOB_NAME = 'GATHER_STATS_JOB';
STATE
---------------
DISABLED
還是用ebs的gather schema statics請求來定期讓它周末或者深夜執行吧~
作者: jianping.ni 時間: 2009-2-16 08:57
Q:報表：信用暫挂報表 送出報錯。路徑：AR超級使用者-報表-收款
A:請參考metalink Doc ID: 744501.1
Subject: Problems Submitting Several Reports In None US Session Language: APP-FND-806: "The default value xyz is invalid for segment Reporting Level".
Doc ID: 744501.1 Type: HOWTO
Modified Date : 02-DEC-2008 Status: PUBLISHED
In this Document
Goal
Solution
References
-------------------------------------------------------------------------------
Applies to:
Oracle Receivables - Version: 12.0.4
Information in this document applies to any platform.
NLS MLS
ARRGTA - Journal Entries Report
ARRXACRC - Publish Actual Receipt
ARRXARRG - Applied Receipts Register
ARRXBRBS - Bills Receivable by Status Report
ARRXBRSS - Bills Receivable Summary Report
ARRXINVR - Transaction Register
ARRXMTRG - Miscellaneous Receipts Register
ARXAGE - Aging - 4 Buckets Report
ARXAWall - Aging - 7 Buckets - By Account Report
ARXAGLW - Aging - 7 Buckets - By Collector Report
ARXAGRW - Aging - 7 Buckets - By Salesperson/Agent Report
ARXAGSW - Aging - 7 Buckets Report
ARXCCS - Customer Credit Snapshot
ARXCHR - Credit Hold Report
ARXRECON - AR Reconciliation Report
RAXGLA - Sales Journal By Customer
RAXGLR - Sales Journal by GL Account Report
RAXINX - Invoice Exception Report
RXARADJR - RX-only: Adjustment Register
RXARARRG - RX-only: Applied Receipts Register
RXARBRBS - RX-only: Bills Receivable by Status Report
RXARBRSS - RX-only: Bills Receivable Summary Report
RXARMTRG - RX-only: Miscellaneous Receipts Register
RXARRCRG - RX-only: Receipt Register
Goal
In Release 12 several reports fail to submit, if you do this in any other session language than English with
"APP-FND-806: The default value xyz is invalid for segment Reporting Level".
Example if you try to run the reports in French, Spanish or German environment you are not able to submit them due to above error message.
If you switch to American English Session language the report can be submitted without any problem.
Solution
Prio 3 Bug 7499513 has been logged for this to get the seed data changed.
Workaround:
Logon to System Administrator
Navigate to Concurrent > Program > Define
Query for Short Name <any of the reports that fail at your instance)
Click Button Parameters
Put your cursor on parameter 'Reporting Level'
Use Edit > Field on field 'Default Value'
Change the current default sql statement from
SELECT MEANING FROM FND_LOOKUPS WHERE LOOKUP_TYPE = 'FND_MO_REPORTING_LEVEL'
AND rownum=1
to
SELECT MEANING FROM FND_LOOKUPS WHERE LOOKUP_TYPE = 'FND_MO_REPORTING_LEVEL'
AND lookup_code = 1000
Save
After this has been done you should be able to submit the report in any session language.
作者: jianping.ni 時間: 2009-2-16 08:58
公司知識庫中的檔案存放在資料庫表中，
通過以下sql語句可以找到檔案和目錄結構:
--1.檔案存放目錄
SELECT folder.name folder_name,--檔案夾
op.name, --檔案名
omc.globalindexedblob, --檔案内容
omc.bfilecontent
FROM content.odm_contentobject oc,
content.odm_document od,
content.odm_publicobject op,
content.odmm_contentstore omc,
content.odm_publicobject folder
WHERE od.contentobject = 2333911--具體ID
AND od.contentobject = oc.id
AND od.contentquota > 0
AND op.id = od.id
AND oc.content = omc.id
AND folder.id = op.primaryparentfolder
--2.在知識庫中使用者建立的目錄樹狀結構:
SELECT b.level_no ,
c.name parent_path,--父目錄
b.name path, --目錄
b.*
FROM (SELECT LEVEL level_no ,a.*
FROM content.odm_publicobject a
WHERE EXISTS(SELECT 'x' FROM content.odm_folder b--表示為目錄
WHERE b.id = a.id)
AND securingpublicobject != 0 --排除系統自帶的目錄(在知識庫中界面中看不到的目錄)
AND securingpublicobject != 59181--排除系統自帶的目錄(在知識庫中界面中看不到的目錄)
AND acl ! = 59391 --排除系統自帶的目錄(在知識庫中界面中看不到的目錄)
START WITH a.id=607--根節點
CONNECT BY a.primaryparentfolder = PRIOR a.id) b,
content.odm_publicobject c
WHERE c.id = b.primaryparentfolder
ORDER BY b.level_no,c.name
作者: jianping.ni 時間: 2009-2-16 08:58
Q:在資産工作台做資産目前成本調整時，系統報錯“APP-OFA-48392:您不能更改進行擴充折舊的資産的成本”，英文環境下也是這個錯誤（Unable To Change Depreciation Method Of An Asset Which Is Not In Extended Depreciation）
A:參考metalink文章 Doc ID：756668.1，打更新檔7612039
作者: jianping.ni 時間: 2009-2-16 08:59
metalink文檔:
R12 Accounting Errors Encountered FAQs
Doc ID: 601306.1 Type: FAQ
Modified Date : 10-NOV-2008 Status: PUBLISHED
Subject: R12 EBTax FAQs
Doc ID: 602006.1 Type: FAQ
Modified Date : 13-DEC-2008 Status: PUBLISHED
作者: jianping.ni 時間: 2009-2-16 09:00
Q:有同學非常認真，在春節期間說<<呵, 這兩天我上了最新的測試環境, 想關庫存會計期, 但是有很多未核算成本的事務哦;有空幫忙看下>>
A:
CREATE TABLE cux_mmt_0131
AS SELECT * FROM mtl_material_transactions mmt
WHERE mmt.costed_flag = 'E'
AND mmt.error_code = 'CST_INVALID_JOB_DATE'--事務處理日期早于任務或計劃的發放日期。
AND mmt.transaction_source_type_id=5;
SELECT * FROM cux_mmt_0131
DECLARE
CURSOR cur_mmt IS
SELECT wdj.date_released,mmt.transaction_date,mmt.transaction_source_id,mmt.transaction_id,mmt.error_code,mmt.error_explanation
FROM mtl_material_transactions mmt,wip_discrete_jobs wdj
WHERE mmt.costed_flag = 'E'
AND mmt.error_code = 'CST_INVALID_JOB_DATE'
AND mmt.transaction_source_type_id=5
AND wdj.wip_entity_id = mmt.transaction_source_id;
BEGIN
FOR rec_mmt IN cur_mmt LOOP
UPDATE mtl_material_transactions
SET transaction_date = rec_mmt.date_released,
costed_flag = 'N',
error_code = NULL,
error_explanation = NULL,
transaction_group_id = NULL
WHERE transaction_id = rec_mmt.transaction_id;
END LOOP;
COMMIT;
END;
SELECT * FROM mtl_material_transactions mmt
WHERE mmt.costed_flag = 'N'
(特别聲明，本data fix僅作為在測試環境碰到類似問題時，提供一種思路。)
作者: jianping.ni 時間: 2009-2-16 09:00
EBS中安全性規則限制sql(Oracle官方寫法):
SELECT fnd_flex_values_vl.flex_value,
fnd_flex_values_vl.flex_value VALUE,
fnd_flex_values_vl.description DESCRIPTION,
nvl(fnd_flex_values_vl.summary_flag, 'N'),
nvl(to_number(fnd_flex_values_vl.structured_hierarchy_level), -1),
fnd_flex_values_vl.compiled_value_attributes,
nvl(fnd_flex_values_vl.enabled_flag, 'Y'),
nvl(to_char(fnd_flex_values_vl.start_date_active, 'J'), 0),
nvl(to_char(fnd_flex_values_vl.end_date_active, 'J'), 0)
FROM fnd_flex_values_vl fnd_flex_values_vl
WHERE (fnd_flex_values_vl.flex_value_set_id = 1013707)--p_flex_value_set_id
AND (((1 = 1) AND
(gl_aff_awc_api_pkg.gl_valid_flex_values(SYSDATE,--p_date
fnd_flex_values_vl.flex_value) = 'Y')))
AND NOT EXISTS (SELECT NULL FROM fnd_flex_value_rule_lines l, fnd_flex_value_rule_usages u
WHERE u.application_id = 101--p_application_id
AND u.responsibility_id = 50726--p_responsibility_id
AND u.flex_value_set_id = 1013707--p_flex_value_set_id
AND l.flex_value_rule_id = u.flex_value_rule_id
AND l.include_exclude_indicator = 'E'
AND fnd_flex_values_vl.flex_value BETWEEN
nvl(decode(u.flex_value_set_id,
1013707,--p_flex_value_set_id
l.flex_value_low,
NULL),
fnd_flex_values_vl.flex_value) AND
nvl(decode(u.flex_value_set_id,
1013707,--p_flex_value_set_id
l.flex_value_high,
NULL),
fnd_flex_values_vl.flex_value))
AND NOT EXISTS (SELECT NULL FROM fnd_flex_value_rule_usages u
WHERE u.application_id = 101--p_application_id
AND u.responsibility_id = 50726--p_responsibility_id
AND u.flex_value_set_id = 1013707--p_flex_value_set_id
AND NOT EXISTS (SELECT NULL FROM fnd_flex_value_rule_lines l
WHERE l.flex_value_rule_id = u.flex_value_rule_id
AND l.include_exclude_indicator = 'I'
AND fnd_flex_values_vl.flex_value BETWEEN
nvl(decode(u.flex_value_set_id,
1013707,--p_flex_value_set_id
l.flex_value_low,
NULL),
fnd_flex_values_vl.flex_value) AND
nvl(decode(u.flex_value_set_id,
1013707,--p_flex_value_set_id
l.flex_value_high,
NULL),
fnd_flex_values_vl.flex_value)))
ORDER BY fnd_flex_values_vl.flex_value
作者: jianping.ni 時間: 2009-2-16 09:00
Q:根據科目彙總模版、彙總科目 取 明細科目
A:直接從gl_account_hierarchies中取
（減掉了自己根據科目彙總模版得出明細科目的煩惱）
作者: jianping.ni 時間: 2009-2-16 09:00
Q：做銷售發運确認時，提示發運确認成功，但是再次檢視行狀态為“已發運”，下一步為“運作接口”，手工運作“連接配接行程停靠站”也會提示警告，在物料事務進行中也無法查詢到這些銷售出庫事務。
在庫存開放接口可以查到相應的錯誤記錄,報釋放保留錯誤。
A:
CREATE TABLE mtl_reservations090118 AS
SELECT * FROM mtl_reservations a
WHERE demand_source_header_id IS NULL
AND subinventory_code = 'STAGE'
AND demand_source_type_id = 2;
DECLARE
CURSOR cur_data IS
SELECT * FROM mtl_reservations a
WHERE demand_source_header_id IS NULL
AND subinventory_code = 'STAGE'
AND demand_source_type_id = 2;
l_sales_order_id NUMBER;
BEGIN
FOR rec_data IN cur_data LOOP
SELECT msok.sales_order_id INTO l_sales_order_id
FROM oe_order_lines_all oola,
oe_order_headers_all ooha,
mtl_sales_orders_kfv msok
WHERE oola.line_id = rec_data.demand_source_line_id
AND ooha.header_id = oola.header_id
AND msok.segment1 = ooha.order_number;
UPDATE mtl_reservations
SET demand_source_header_id = l_sales_order_id
WHERE reservation_id = rec_data.reservation_id;
END LOOP;
END;
UPDATE mtl_transactions_interface
SET process_flag = 1,
lock_flag = 2,
transaction_mode = 3,
validation_required = 1,
error_code = NULL,
error_explanation = NULL
WHERE process_flag = 3
((特别聲明，本data fix僅作為在測試環境碰到類似問題時，提供一種思路。)
作者: jianping.ni 時間: 2009-2-16 09:01
Missing Reference Link In GL Approval Workflow
Doc ID: 363547.1
To implement the solution, please execute the following steps:
There are some notes that address this issue, but the following can be done also to achieve the requirement.
1. Define new custom menu (similar to Workflow User Web (New)).
2. Add 'Enter Journals' function to this new custom menu. (You can still add it to an available menu)
3. Create new custom responsibility 'i.e Workflow Notifications'
4. Add the custom menu to this new custom responsibility. (Or any available responsibility)
5. Assign the new custom responsibility to user.
..
6. Create Journal and submit it for approval.
7. Reference link should appear in the notification. (using this custom responsibility)
8.需要重新開機adapcctl.sh(11i)或者 adoacorectl.sh(R12)
作者: jianping.ni 時間: 2009-2-16 09:01
Q:應收做事務處理
1.輸入頭資訊,儲存
2.輸入行項目,儲存
3.回到頭資訊界面,按完成按鈕
報APP-AR-294094:出現意外錯誤,狀态已經恢複為未完成
A:找到arp_etax_util.synchronize_for_doc_seq(AREBTUTB.pls 120.39.12000000.29 2008/09/09)中，
SELECT
DECODE(TT.type, 'INV', 'INVOICE',
'DM', 'DEBIT_MEMO',
'CM', 'CREDIT_MEMO') event_class,
TT.type || '_UPDATE' event_type,
T.customer_trx_id customer_trx_id,
T.trx_number trx_number,
SUBSTRB(T.comments,1,240) description,
T.doc_sequence_id doc_sequence_id,
-- bug 6806843
--TT.name trx_type_name,
SEQ.name doc_seq_name,
T.doc_sequence_value doc_sequence_value,
T.batch_source_id batch_source_id,
TB.name batch_source_name,
TT.description trx_type_description,
T.printing_original_date printing_original_date,
T.term_due_date term_due_date
FROM RA_CUSTOMER_TRX T,
RA_CUST_TRX_TYPES TT,
RA_BATCH_SOURCES TB,
FND_DOCUMENT_SEQUENCES SEQ
WHERE T.customer_trx_id = trx_id
AND T.cust_trx_type_id = TT.cust_trx_type_id
AND T.doc_sequence_id = SEQ.doc_sequence_id (+)
AND T.batch_source_id = TB.batch_source_id
AND (T.doc_sequence_id IS NOT NULL OR
T.doc_sequence_value IS NOT NULL OR
NVL(T.old_trx_number, T.trx_number) <> T.trx_number OR
sync_line_data = 'Y')
因為T.doc_sequence_id和T.doc_sequence_value都為空導緻
該sql沒有傳回資料。于是，嘗試由顧問将單據編号改為在儲存時自動産生。
此錯誤不再産生。
但以前的版本都是可以設定單據編号為手工或者部分産生,都是不報錯的。
找到了ARP_PROCESS_HEADER_UPDTE_COVER.update_header_cover(ARTEHECB.pls 120.9.12000000.4 2008/07/08)
調用了arp_etax_util.synchronize_for_doc_seq。
從ARP_PROCESS_HEADER_UPDTE_COVER.update_header_cover中看出,p_sync_line_data的值并不是來源于預置檔案
或者其它什麼設定表。當付款條件和總帳日期沒有改變時，就會傳入p_sync_line_data='N'的值。
這就會導緻不自動産生單據編号時，報APP-AR-294094:出現意外錯誤。
推斷這是oracle的一個bug,需要提tar,請oracle給出更新檔.
作者: jianping.ni 時間: 2009-2-16 09:01
本帖最後由 jianping.ni 于 2009-2-23 13:34 編輯
Q:定期實際成本處理程式 在某些職責中 巨慢，狀态一直處于運作中，不能運作完成。
A:oracle剛出更新檔8208324.
--------------------------------------------------------------
原來臨時措施:
CREATE OR REPLACE PACKAGE BODY CSTPPACQ AS
.....
procedure acq_cost_processor
.....
the first "CURSOR c_invoices IS"
........
把
AND
( ( l_res_flag =1 ) AND ( ad2.accounting_date between i_start_date and i_end_date) )
OR (l_res_flag = 2)
AND ad2.line_type_lookup_code <> 'REC_TAX'
........
改為
........
AND
( --Added ( at 2008.12.28
( ( l_res_flag =1 ) AND ( ad2.accounting_date between i_start_date and i_end_date) )
OR (l_res_flag = 2)
) --Added ( at 2008.12.28
AND ad2.line_type_lookup_code <> 'REC_TAX'
長久措施:等待oracle給出更新檔。
-------------------------------------------------------------------------------
oracle承認是個bug，正出更新檔呢
Oracle metalink answer:
There was a problem with fix done through bug6748898 because of wrong
brackets there was cartesain join when fetching the invoice.
Fix the bracketing through bug8208324. CSTPACQB.pls 120.16.12000000.13
Bug 8208324 - PERIODIC ACQUISITION COST PROCESSOR DID NOT FINISH AFTER PATCH 6751847/69
42050
Tested the patch successfully in internal instance. After UT and QA
certified, supersede patch will be released.
Thanks,
Jayashree
STATUS
=======
@DEV -- Development Work In Progress
17-FEB-09 22:38:22 GMT
Associated bug 8208324 has been updated and is still at status: 11.
作者: jianping.ni 時間: 2009-2-16 09:02
銷售退貨庫存事務在庫存事務表中報錯:
mtl_material_transactions.error_code = 'No Error'
mtl_material_transactions.error_explanation = 'CSTPACIN.COST_INV_TXN:Failure in procedure CST_RevenueCogsMatch_PVT.Process_RmaReceipt()'
其原因是銷售退貨庫存事務的日期(mtl_material_transactions.transaction_date)早于了對應的銷售訂單的cst_cogs_events.event_date日期
通過以下SQL查找錯誤資料:
SELECT DISTINCT mmt.transaction_id,
mmt.transaction_date,
mmt.acct_period_id,
mmt.organization_id,
cce.event_id,
cce.event_date
FROM mtl_material_transactions mmt,
oe_order_lines_all oola,
cst_cogs_events cce
WHERE mmt.costed_flag IN('E','N')
--AND mmt.error_code = 'No Error'
--AND mmt.error_explanation = 'CSTPACIN.COST_INV_TXN:Failure in procedure CST_RevenueCogsMatch_PVT.Process_RmaReceipt()'
AND mmt.transaction_source_type_id = 12
AND mmt.transaction_type_id = 15
AND oola.line_id = mmt.trx_source_line_id
AND oola.reference_line_id = cce.cogs_om_line_id
AND cce.event_date > mmt.transaction_date;
措施:根據實際庫存事務情況修正mmt.transaction_date,
使得mmt.transaction_date >= cce.event_date,
并保持mmt.transaction_date和mmt.acct_period_id在同一會計期間
作者: jianping.ni 時間: 2009-2-16 09:02
Q:現發現财務報表： CUX:應計負債 中，**号需要做“轉義”處理，否則當**号中包含“&”之類的符号時無法正常顯示，在導出、查詢、對照的過程中易于出錯。請解決。
A:
方法之一：提供給如下函數進行處理,這種方法可以處理HTML類型報表,XML PUBLISER的相關報表；
FUNCTION get_parsing_str(p_string IN VARCHAR2)
RETURN VARCHAR2 IS
v_parsing_str VARCHAR2(250);
BEGIN
--轉義：&
v_parsing_str := REPLACE(p_string, '&', '&');
--轉義：<
v_parsing_str := REPLACE(v_parsing_str, '<', '<');
--轉義：>
v_parsing_str := REPLACE(v_parsing_str, '>', '>');
--轉義：/
v_parsing_str := REPLACE(v_parsing_str, '/', '"');
--還有其他的好多轉義字元：具體碰到的時候具體添加
--......
RETURN v_parsing_str;
EXCEPTION
WHEN OTHERS THEN
RETURN NULL;
END;
方法之二：如果是XML PUBLISHER報表，一種方法是使用如上“方法之一”進行解決，還有一種方法是使用XML的格式字元，就是在列印每個
XML标簽的時候，多列印一個标簽，便可解決該問題。如下：<![CDATA[。。。。。。]]>
比如說：
<customer_name>上海&惠普</customer_name>
修改為：
<customer_name><![CDATA[上海&惠普]]></customer_name>
作者: jianping.ni 時間: 2009-2-16 09:03
有同學碰到如下問題
1.
Q:給某資料庫使用者授權(比如grant dba to cux)後，發現沒有生效。
A:要重新登陸pl/sql developer才生效
2.
Q:修改了regedit系統資料庫NLS_LANG的值(比如改成AMERICAN_AMERICA.ZHS16CGB231280)，FORM界面還是亂碼。
A:要關閉FORM BUILDER,重新打開
作者: jianping.ni 時間: 2009-2-16 09:10
本帖最後由 jianping.ni 于 2009-2-19 21:36 編輯
運作MRP很慢或者報錯
1.增加表空間大小
2.增加标準管理器個數(原來是3個)
3.MRP 管理器(原來是0個)
4.以系統管理者運作請求:Gather Schema Statistics
參數選擇ALL或者分别選擇MRP、INV、WIP
重新運作MRP
作者: jianping.ni 時間: 2009-2-16 09:11
本帖最後由 jianping.ni 于 2009-2-19 21:36 編輯
Q:建立銷售訂單時，在行資訊中輸入ITEM，數量和機關，不能自動帶出價目表，提示物料和機關不在價目表中，并且手工輸入價格不能繼續，導緻訂單不能建立
A:參考metalink 605330.1,将profile:QP:custom sourced的值設定為No
該問題由顧問韓宇雷提tar解決，tar部分内容如下:
ISSUE CLARIFICATION
====================
On R12.HC_PF.A.DELTA.1 in Production:
When attempting to enter the item and UOM in sales order line.the error will appear,
the following error occurs.
ERROR
-----------------------
1255-3 and W not on test00.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Order management super user resp> Orders,Returns>Sales Orders>line item>enter the item and uom
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot filfull the sale order.
-------------------------------------------------------------------------------------------------------
UPDATE
======
Please take the following actions
1. Run Build Attribute Mapping Rules
Responsibility = Oracle Pricing Manager
Navigate: Reports
Select 'single request' then 'OK'
Name: Build Attribute Mapping Rules
Click OK then Submit Request
2. Once step #1 completes, Run QP: Maintains the denormalized data in QP
Qualifiers
Responsibility = Oracle Pricing Manager
Navigate: Reports
Select 'single request' then 'OK'
Name: QP: Maintains the denormalized data in QP Qualifiers
Parameters:
Enter the list header id (low) by selecting the lowest value from
the LOV (list of values). This is the first value listed.
Enter the list header id (high) by selecting the highest value
from the LOV (list of values). This is the last value listed.
Click OK then Submit Request
3. Please retest issue.
--------------------------------------------------------------------------------------------------------------
Build Attribute Mapping Rules
QP: Maintains the denormalized data in QP Qualifiers
i have run the requests according to your advice,and both are sucessfull.But the question is still existing.
--------------------------------------------------------------------------------------------------------------
Could you kindly review 605330.1 published on Metalink?
--------------------------------------------------------------------------------------------------------------
Closed by customer
the question is resolved.
set up profile:QP:custom sourced=NO
thanks a lot!
--------------------------------------------------------------------------------------------------------------
(Update for record id(s): 256082469,256082476,256082481,256082483)
CAUSE DETERMINATION
===================
QP: custom Sourced is set to 'Yes' when it was not supposed to be.
CAUSE JUSTIFICATION
===================
Reference Note 393665.1
PROPOSED SOLUTION(S)
====================
QP: custom Sourced is set to 'Yes' when it was not supposed to be.
PROPOSED SOLUTION JUSTIFICATION(S)
==================================
QP: custom Sourced is set to 'Yes' when it was not supposed to be.
SOLUTION / ACTION PLAN
======================
-- To implement the solution, please execute the following steps::
QP: custom Sourced is set to 'Yes' when it was not supposed to be.
KNOWLEDGE CONTENT
=================
Knowledge content not created because the following note already addresses this issue: SURE 3
93665.1 : Item Is Not Found On Price List - for a Simple Price List Setup
SURE 605330.1 : Common Reasons To Receive "Item and UOM Not on Price List" Error
作者: jianping.ni 時間: 2009-2-16 09:11
<<AP 和 PO 應計調節報表>>和<<未開票接收報表>>在運作時，如果不限定參數條件，會報錯：ORA-06502: PL/SQL: numeric or value error: character string buffer too small 。
原因:<<未開票接收報表>>對應代碼CST_UninvoicedReceipts_PVT.Print_ClobOutput中:
l_amount := 32700; 中的32700稍大了點，
臨時措施:将其l_amount := 31000
長久措施:在oracle metalink上提tar，尋求相應更新檔幫助。
同樣，<<AP 和 PO 應計調節報表>>也是CST_ApPoAccrualReport_PVT.Generate_APPOReportXml中:
l_amount := 32000;中的32000稍大了點
---------------------------------------------------------------------
另外，技術同僚如果用PL/SQL來産生xml檔案，可以參考這兩個程式包寫法。
作者: jianping.ni 時間: 2009-2-16 09:12
Q:在“檢視淨額結算報表”的WEB頁面中，不能運作、檢視淨額結算報表.
A:<<最終的淨額結算報表>>PL/SQL程式包FUN_XML_REPORT_PKG對應PL/SQL代碼中，沒有指定 <?xml version="1.0" encoding="....">，
參考其它EBS系統通過PL/SQL産生XML檔案寫法，臨時措施為:
l_encoding VARCHAR2(100);
l_xml_header VARCHAR2(100);
BEGIN
.............
l_encoding := fnd_profile.value('ICX_CLIENT_IANA_ENCODING');
l_xml_header := '<?xml version="1.0" encoding="'|| l_encoding ||'"?>';
fnd_file.put_line(fnd_file.output,l_xml_header);
.............
長久措施:在oracle metalink上尋找更新檔或者提tar尋求相應更新檔幫助。
PS:如果我們用PL/SQL産生XML檔案，不妨和ORACALE EBS标準做法一緻，
根據fnd_profile.value('ICX_CLIENT_IANA_ENCODING')來指定xml檔案的encoding值。
作者: jianping.ni 時間: 2009-2-16 09:12
Q:如果碰到以下類似錯誤(XML檔案不能正常顯示、中文顯示亂碼等)
無法顯示 XML 頁。
使用 XSL 樣式表無法檢視 XML 輸入。請更正錯誤然後單擊 重新整理按鈕，或以後重試。
--------------------------------------------------------------------------------
結束标記 'BATCH_DETAILS' 與開始标記 'NETTING_CURRENCY_RULE' 不比對。處理資源 'http://rx6600.jasolar.com:8003/OA_CGI/FNDWRR.exe?temp_id=3364...
</BATCH_DETAILS>
---^
+------------- 1) PUBLISH -------------+
節點 RX6600 上的請求 391441 于 20-12-2008 21:08:01 開始進行後期處理。
請求 391441 的後期處理于 20-12-2008 21:08:01 失敗，并顯示錯誤消息：
One or more post-processing actions failed. Consult the OPP service log for details.
+--------------------------------------+
+------------- 2) PRINT -------------+
由于後期處理失敗，是以沒有列印此請求的輸出。
+--------------------------------------+
A:可能可以通過修改以下設定(可能需要重新開機unix adoacorectl.sh 或重登入EBS):
預置檔案:ICX：客戶機 IANA 編碼 和 FND: NATIVE CLIENT ENCODING
首選項: 地區設定 和 客戶機字元編碼
來解決這一類問題
作者: jianping.ni 時間: 2009-2-16 09:13
Q:重新開機并發管理器失敗
A:重新開機并發管理器失敗之後，試圖執行stopAPP.sh停止整個應用，
報如下錯誤
Database connection could not be established. Either the database is down or the APPS credentials supplied are wrong.
此錯誤的原因是unix伺服器磁盤空間不足了。
删除了unix伺服器上無用的檔案後，重新開機成功。
unix伺服器上無用的檔案包括如下:
/tmp
請求結果:$INST_TOP/logs/appl/conc/out
日志:$INST_TOP/logs/appl/conc/log
已經打過patch的patch目錄
$ORACLE_HOME/admin/....../udump (啟動資料庫使用者的$ORACLE_HOME)
$ORACLE_HOME/forms/doc(啟動EBS應用使用者的$ORACLE_HOME)
......
還有其它無用的目錄請大家補充
并建議調試或者跟蹤完後，及時将調試或者跟蹤flag關閉。
并以系統管理者職責計劃運作那些清除過時資料的請求
作者: jianping.ni 時間: 2009-2-16 09:13
Q:運作請求時，報如下錯誤:
Enter Password:
Xlib: connection to "erpwork:0.0" refused by server
Xlib: Client is not authorized to connect to Server
Xlib: connection to "erpwork:0.0" refused by server
Xlib: Client is not authorized to connect to Server
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-3000: Internal error starting Oracle Toolkit.
A:
以root身份執行
DISPLAY=EBS應用伺服器IP位址:0.0 (比如DISPLAY=192.168.100.13:0.0)
export DISPLAY
xhost +
以啟動EBS應用的UNIX使用者(比如apptest1)身份執行
DISPLAY=EBS應用伺服器IP位址:0.0 (比如DISPLAY=192.168.100.13:0.0)
export DISPLAY
xhost + EBS應用伺服器IP位址(比如xhost + 192.168.100.13)
作者: jianping.ni 時間: 2009-2-16 09:14
問題:客戶化FORM添加了glcore.pll,在本地編譯能夠通過,
但到伺服器上編譯時報錯，且沒有顯示具體錯誤資訊。
原因:該pll在unix伺服器上的檔案名是GLCORE.pll,
unix是區分大小寫的。
措施:在本地電腦上将glcore.pll改名為GLCORE.pll,
将客戶化FORM重新attach一邊GLCORE.pll。
問題:Autoinvoice Master Program的子請求報錯
原因:1.沒有設定預置檔案AR: Use Invoice Accounting For Credit Memos
2.Not all AutoAccounting types are defined
作者: jianping.ni 時間: 2009-2-16 09:14
Q:應付不能輸入外币**
A:Please apply the patch 6661327 in your test instance..
下載下傳patch時，需要oracle tar提供如下密碼:
the password for Simplified Chinese (ZHS) is RYJxedJU
the password for Traditional Chinese (ZHT) is lfWfUg4J
the password for Us english is rddp3osy
作者: jianping.ni 時間: 2009-2-16 15:44
Q:物料接口表将物料屬性更新為空值(也許也适用于其它接口表)
A:字元型的字段隻要寫'!',數值型寫-999999
作者: baohaiqi 時間: 2009-2-16 20:12
好資料 學習中
作者: baohaiqi 時間: 2009-2-16 20:13
在頂一下
作者: smirkface 時間: 2009-2-16 21:55
超級牛貼
作者: sail.sun 時間: 2009-2-17 19:51
老大這種Q&A的文章很有價值啊，大家得收hide啊
作者: jianping.ni 時間: 2009-2-18 17:20
不能建立會計分錄
--------------------------------------------------------------------------------
打更新檔:6826219和6901404
處理原理:
如果建立會計分錄失敗,隻要把xla_events.event_status_code和xla_events.process_status_code都改成'U',
然後送出<<建立會計科目>>請求或者直接在**界面建立會計分錄,
建立會計分錄程式不管xla_ae_headers和xla_ae_lines是否有與xla_events相應記錄，
都會重新建立xla_ae_headers和xla_ae_lines記錄
-----------------------------------------------------------------------------
處理應付**不能建立會計分錄例子一:
create table xla_events_bkp
as select * from xla_events
where event_id in (select event_id from xla_events e
where e.application_id = 200
and e.event_status_code ='P'
and not exists ( select 1 from xla_ae_headers h
where e.event_id = h.event_id ));
UPDATE xla_events
SET event_status_code = 'U',
process_status_code = 'U'
WHERE event_id IN (select event_id from xla_events e
where e.application_id = 200
and e.event_status_code ='P'
and not exists ( select 1 from xla_ae_headers h
where e.event_id = h.event_id ));
運作<<建立會計科目>>請求
-----------------------------------------------------------------------------
處理應付**不能建立會計分錄例子二:
**号200803005(已取消) 部分建立會計分錄,付款号1102000006 不能建立會計分錄
因為先有**再有付款,是以思路
1.先試圖建立**的會計分錄
SELECT invoice_num,invoice_id,doc_sequence_id,doc_sequence_value FROM ap_invoices_all
WHERE invoice_num = '200803005'
select event_id,ae_header_id,a.* from xla_ae_headers a
WHERE doc_sequence_id = 130
AND doc_sequence_value = '210401983'
SELECT event_id,a.* FROM xla_ae_headers a
WHERE event_id IN (70300,80395)
找到那條xla_ae_headers記錄沒有建立會計分錄的event_id=70300,ae_header_id=57016
DELETE FROM xla_ae_lines
WHERE ae_header_id = 57016
DELETE FROM xla_ae_headers
WHERE ae_header_id = 57016
UPDATE xla_events
SET event_status_code = 'U',
process_status_code = 'U'
WHERE event_id = 70300
運作<<建立會計科目>>請求
2.再試圖建立付款的會計分錄
SELECT * FROM xla_ae_headers
WHERE DESCRIPTION LIKE '%1102000006%'
AND je_category_name = 'Payments'
DELETE xla_ae_lines
WHERE ae_header_id IN (101270,101271)
DELETE xla_ae_headers
WHERE ae_header_id IN (101270,101271)
UPDATE xla_events
SET event_status_code = 'U',
process_status_code = 'U'
WHERE event_id IN (70302,80394)
運作<<建立會計科目>>請求
-----------------------------------------------------------------------------
處理應付**不能建立會計分錄例子三
ET1104應付 **号8000480849/859/862沒有建立會計分錄的原因是：
該**行１和 **行２ 已放棄．
損益行中的帳戶無效。如果您已定義損益日記帳行類型，請在日記帳行定義中檢查附加至該類型的帳戶推導規則。否則，請檢查映射至會計屬性“彙兌收益帳戶”和“彙兌損失帳戶”
的來源值。
無法建立帳戶，因為 &OWNER 擁有的帳戶推導規則 &COMPONENT_NAME 的所有條件均不滿足。請更新 &COMPONENT_NAME 的條件，或配置設定其它帳戶推導規則至 &PAD_OWNER 擁有的
應用産品會計定義 &PAD_NAME.
子分類帳會計無法使用 &OWNER 擁有的帳戶推導規則 &COMPONENT_NAME 導出會計科目代碼組合。請複核帳戶推導規則，并確定對于為此事務處理傳送的來源值，此規則可以導出
有效的會計科目彈性域組合。
請根據以上錯誤資訊，檢查 當**行被放棄時，彙兌損益 相關的帳戶推導規則 ，映射至會計屬性“彙兌收益帳戶”和“彙兌損失帳戶”的來源值，
但是顧問沒有檢查出來設定是否有問題。這也許是oracle的一個bug.
臨時處理方法:
直接在表中删除了放棄行的**配置設定行和**行
CREATE TABLE AP_INVOICE_DISTRIBUTIONS_0427
AS SELECT * FROM AP_INVOICE_DISTRIBUTIONS_all
WHERE invoice_id = 15761 and invoice_line_number IN (1,2)
SELECT * FROM AP_INVOICE_DISTRIBUTIONS_0427
CREATE TABLE AP_INVOICE_LINES_0427 as
SELECT * FROM AP_INVOICE_LINES_all
WHERE invoice_id = 15761
AND line_number IN (1,2)
SELECT * FROM AP_INVOICE_LINES_0427
DELETE FROM AP_INVOICE_DISTRIBUTIONS_all
WHERE invoice_id = 15761 and invoice_line_number IN (1,2)
DELETE FROM AP_INVOICE_LINES_all
WHERE invoice_id = 15761
AND line_number IN (1,2)
直接在**界面建立會計分錄
最終處理方法:建議使用者提tar由oracle官方解決
-----------------------------------------------------------------------------
處理應付**不能建立會計分錄例子四:
這張**2008030888.不能建立會計分錄的原因是 沒有錄入**的配置設定資訊
-----------------------------------------------------------------------------
處理應付**不能建立會計分錄例子五:
标準**核銷預付款**後，部分會計分錄不能建立。已入帳顯示：部分
措施:
先在**界面上驗證相關**,然後在**界面上建立會計分錄
-----------------------------------------------------------------------------
處理應付**不能建立會計分錄例子六:
駱勇平員工由于EBS bug,再導入費用報表後,産生兩個駱勇平供應商,經過删除其中一個供應商和供應商地點後
産生的出來會計分錄資訊居然還有被删除供應商的ID,供應商地點ID
措施:
找到了xla_ae_lines.party_id(這裡找到有些會計分錄的建立是根據以前會計分錄記錄來建立的,比如ref_event_id,ref_ae_header_id)
于是将xla_ae_lines.party_id,xla_ae_lines.party_site_id統統改成了現在的駱勇平供應商ID和供應商地點ID
運作cux_fix_invoice_accounting_pkg.fix_invoices程式,修正資料
運作<<建立會計科目>>請求
----------------------------------------------------------------------------
修正資料的程式包cux_fix_invoice_accounting_pkg:
CREATE OR REPLACE PACKAGE cux_fix_invoice_accounting_pkg IS
PROCEDURE fix_invoices(p_invoice_id IN NUMBER);
PROCEDURE fix_payments(p_payment_num IN VARCHAR2);
END;
/
CREATE OR REPLACE PACKAGE BODY cux_fix_invoice_accounting_pkg IS
PROCEDURE fix_invoices(p_invoice_id IN NUMBER) IS
CURSOR cur_invoice(i_cur_invoice_id IN NUMBER) IS
SELECT doc_sequence_id,doc_sequence_value FROM ap_invoices_all
WHERE invoice_id = i_cur_invoice_id;
CURSOR cur_xla_ae_headers(i_cur_doc_sequence_id IN NUMBER,i_cur_doc_sequence_value IN NUMBER) IS
SELECT event_id,ae_header_id from xla_ae_headers
WHERE doc_sequence_id = i_cur_doc_sequence_id
AND doc_sequence_value = i_cur_doc_sequence_value;
BEGIN
FOR rec_invoice IN cur_invoice(p_invoice_id) LOOP
FOR rec_xla_ae_headers IN cur_xla_ae_headers(rec_invoice.doc_sequence_id,rec_invoice.doc_sequence_value) LOOP
INSERT INTO xla_ae_lines080421
SELECT * FROM xla_ae_lines
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
INSERT INTO xla_ae_headers080421
SELECT * FROM xla_ae_headers
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
DELETE xla_ae_lines
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
DELETE xla_ae_headers
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
END LOOP;
END LOOP;
UPDATE xla_events
SET event_status_code = 'U',process_status_code = 'U'
WHERE event_id IN (SELECT event_id FROM xla_events e
WHERE e.application_id = 200
AND e.event_status_code ='P'
AND NOT EXISTS (SELECT 1 FROM xla_ae_headers h
WHERE e.event_id = h.event_id ));
COMMIT;
END;
PROCEDURE fix_payments(p_payment_num IN VARCHAR2) IS
CURSOR cur_xla_ae_headers(i_cur_payment_num IN NUMBER) IS
SELECT event_id,ae_header_id from xla_ae_headers
WHERE description LIKE '%'||i_cur_payment_num||'%'
AND je_category_name = 'Payments';
BEGIN
FOR rec_xla_ae_headers IN cur_xla_ae_headers(p_payment_num) LOOP
INSERT INTO xla_ae_lines080421
SELECT * FROM xla_ae_lines
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
INSERT INTO xla_ae_headers080421
SELECT * FROM xla_ae_headers
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
DELETE xla_ae_lines
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
DELETE xla_ae_headers
WHERE ae_header_id = rec_xla_ae_headers.ae_header_id;
END LOOP;
UPDATE xla_events
SET event_status_code = 'U',process_status_code = 'U'
WHERE event_id IN (SELECT event_id FROM xla_events e
WHERE e.application_id = 200
AND e.event_status_code ='P'
AND NOT EXISTS (SELECT 1 FROM xla_ae_headers h
WHERE e.event_id = h.event_id ));
COMMIT;
END;
END;
/
--=============================================================================
處理應收事務處理不能建立會計分錄例子:
貸項通知單11040000002921不能建立會計分錄
通過界面找到貸項通知單11040000002921對應的原始**11040000002801,
發現11040000002801沒有建立會計分錄,在界面上将11040000002801建立會計分錄成功。
貸項通知單11040000002921按完成按鈕後,發現不能儲存,做跟蹤限制值,
發現跟蹤檔案的最後幾句
*******************************************************************************
SELECT AE.EVENT_ID , AE.EVENT_DATE , AE.EVENT_STATUS_CODE, AE.EVENT_TYPE_CODE
FROM
XLA_EVENTS AE, XLA_TRANSACTION_ENTITIES_UPG XT, RA_CUSTOMER_TRX_ALL TRX
WHERE TRX.CUSTOMER_TRX_ID = :B3 AND NVL(XT.SOURCE_ID_INT_1,-99) =
TRX.CUSTOMER_TRX_ID AND XT.ENTITY_CODE = 'TRANSACTIONS' AND XT.LEDGER_ID =
TRX.SET_OF_BOOKS_ID AND XT.ENTITY_ID = AE.ENTITY_ID AND XT.APPLICATION_ID =
222 AND AE.APPLICATION_ID = 222 AND NVL(AE.EVENT_DATE, TO_DATE('01-01-1900',
'DD-MM-YYYY')) = :B2 AND AE.EVENT_STATUS_CODE <> 'P' AND :B1 =
AE.EVENT_TYPE_CODE
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.00 0.00 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 1 0.00 0.00 0 11 2 1
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 3 0.00 0.00 0 11 2 1
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 44 (recursive depth: 1)
*******************************************************************************
SELECT MESSAGE_TEXT, MESSAGE_NUMBER, TYPE, FND_LOG_SEVERITY, CATEGORY,
SEVERITY
FROM
FND_NEW_MESSAGES M, FND_APPLICATION A WHERE :B3 = M.MESSAGE_NAME AND :B2 =
M.LANGUAGE_CODE AND :B1 = A.APPLICATION_SHORT_NAME AND M.APPLICATION_ID =
A.APPLICATION_ID
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 0 0.00 0.00 0 0 0 0
Execute 1 0.00 0.00 0 0 0 0
Fetch 1 0.00 0.00 0 0 0 0
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 2 0.00 0.00 0 0 0 0
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 44 (recursive depth: 1)
********************************************************************************
ROLLBACK TO AR_PAYMENT_SCHEDULE
SELECT AE.EVENT_ID , AE.EVENT_DATE , AE.EVENT_STATUS_CODE, AE.EVENT_TYPE_CODE FROM XLA_EVENTS AE, XLA_TRANSACTION_ENTITIES_UPG XT, RA_CUSTOMER_TRX_ALL TRX WHERE TRX.CUSTOMER_TRX_ID = :B3 AND NVL(XT.SOURCE_ID_INT_1,-99) = TRX.CUSTOMER_TRX_ID AND XT.ENTITY_CODE = 'TRANSACTIONS' AND XT.LEDGER_ID = TRX.SET_OF_BOOKS_ID AND XT.ENTITY_ID = AE.ENTITY_ID AND XT.APPLICATION_ID = 222 AND AE.APPLICATION_ID = 222 AND NVL(AE.EVENT_DATE, TO_DATE('01-01-1900','DD-MM-YYYY')) = :B2 AND AE.EVENT_STATUS_CODE <> 'P' AND :B1 = AE.EVENT_TYPE_CODE
END OF STMT
PARSE #358:c=0,e=53,p=0,cr=0,cu=0,mis=0,r=0,dep=1,og=1,tim=4237611529714
BINDS #358:
kkscoacd
Bind#0
oacdty=02 mxl=22(21) mxlc=00 mal=00 scl=00 pre=00
oacflg=13 fl2=206001 frm=00 csi=00 siz=24 off=0
kxsbbbfp=110ad52a0 bln=22 avl=04 flg=09
value=22716
Bind#1
oacdty=12 mxl=07(07) mxlc=00 mal=00 scl=00 pre=00
oacflg=13 fl2=206001 frm=00 csi=00 siz=8 off=0
kxsbbbfp=110ad52d0 bln=07 avl=07 flg=09
value="5/23/2008 0:0:0"
Bind#2
oacdty=01 mxl=32(09) mxlc=00 mal=00 scl=00 pre=00
oacflg=13 fl2=206001 frm=01 csi=871 siz=32 off=0
kxsbbbfp=110ad4a60 bln=32 avl=09 flg=09
value="CM_CREATE"
将具體參數值代入sql語句，得到:
SELECT AE.EVENT_ID, AE.EVENT_DATE, AE.EVENT_STATUS_CODE, AE.EVENT_TYPE_CODE
FROM XLA_EVENTS AE,
XLA_TRANSACTION_ENTITIES_UPG XT,
RA_CUSTOMER_TRX_ALL TRX
WHERE TRX.CUSTOMER_TRX_ID = 22716
AND NVL(XT.SOURCE_ID_INT_1, -99) = TRX.CUSTOMER_TRX_ID
AND XT.ENTITY_CODE = 'TRANSACTIONS'
AND XT.LEDGER_ID = TRX.SET_OF_BOOKS_ID
AND XT.ENTITY_ID = AE.ENTITY_ID
AND XT.APPLICATION_ID = 222
AND AE.APPLICATION_ID = 222
AND NVL(AE.EVENT_DATE, TO_DATE('01-01-1900', 'DD-MM-YYYY')) = to_date('2008-05-23 00:00:00','YYYY-MM-DD HH24:MI:SS')
AND AE.EVENT_STATUS_CODE <> 'P'
AND 'CM_CREATE'= AE.EVENT_TYPE_CODE
也就是說在按完成按鈕是不應該出現以上SQL語句有值,即XLA_EVENTS.EVENT_STATUS_CODE <> 'P'的記錄應該不存在
措施:
1.AE.EVENT_STATUS_CODE,ae.process_status_code暫時都改為'P',
然後再按完成按鈕,這次儲存成功。
2.将AE.EVENT_STATUS_CODE,ae.process_status_code都改回'U',
檢查 xla_ae_headers,xla_ae_lines是否有資料,
SELECT * FROM xla_ae_headers--no row
WHERE event_id IN (162517,162518)
SELECT * FROM xla_ae_lines--no row
在界面上将11040000002801建立會計分錄成功
作者: jianping.ni 時間: 2009-2-18 17:21
Q:有一筆付款單1104060585，做了建立會計分錄動作。結果卻是付款單的會計狀态是正在進行中，導緻無法看會計分錄，也無法再建立。
A:檢查如下:
1.ap_invoice_payments_all.posted_flag和ap_payment_history_all.posted_flag的值都為'S'
2.通過以下xla_events.event_id=ap_invoice_payments_all.accounting_event_id
關聯，執行如下SQL語句:
SELECT * FROM xla_events
WHERE event_id = ap_invoice_payments_all.accounting_event_id
傳回event_status_code和process_status_code都為'U'的記錄
SELECT * FROM xla_ae_headers
WHERE event_id = ap_invoice_payments_all.accounting_event_id
沒有傳回記錄
猜測建立會計分錄時，意外原因導緻建立會計分錄隻執行了部分動作。
措施:
UPDATE ap_invoice_payments_all
SET posted_flag = 'N'--old is 'S'
WHERE check_id =
UPDATE ap_payment_history_all
SET posted_flag = 'N'--old is 'S'
WHERE check_id =
更新後,付款界面可以執行建立會計分錄動作了。
執行建立會計分錄動作後，會計分錄建立成功。
![無效的源發行版: 9 解決辦法[圖]](data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=)