狀況:
1.Create Accounting - Cost Management停在Running狀態超過20小時
2.有以下三種等待事件:
db file sequential read
latch free
latch: cache buffers chains
3.以GL的資料來看, 在執行的第一小時就已拋轉
解決方式:
1.Oracle文件註明, 若有指定拋GL, 執行時就不可cancel/terminate , 但再等應該也沒用, 於是cancel request
2.後續另有支Create Accounting - Cost Management也執行超久, 最後只能cancel
3.治標的方式, 是針對Parameter的Report項目選No Report
後續針對特定schema收統計, 再觀察.
Ref:
1."Create Accounting - Cost Management" Is Taking Longer Than Usual To Complete. (Doc ID 1444834.1)
2019年4月30日 星期二
2019年4月23日 星期二
Oracle EBS: Autoinvoice Master Program異常error
狀況:
1.在Request Set中, Autoinvoice Master Program status為Error, 但parent的concurrent仍處於Running/Paused
2.Autoinvoice Master Program沒有output, 在log中沒有error或warning, 看不出為何error
3.Completion Text中有以下訊息:
The concurrent program for your concurrent request exited to wait, but has no pending child requests to wait for. Routine AFPPRC received a return code of failure.
不定時發生, 目前都是治標, 直接cancel, 原因尚未確定.
1.在Request Set中, Autoinvoice Master Program status為Error, 但parent的concurrent仍處於Running/Paused
2.Autoinvoice Master Program沒有output, 在log中沒有error或warning, 看不出為何error
3.Completion Text中有以下訊息:
The concurrent program for your concurrent request exited to wait, but has no pending child requests to wait for. Routine AFPPRC received a return code of failure.
不定時發生, 目前都是治標, 直接cancel, 原因尚未確定.
2019年4月19日 星期五
Oracle EBS: There are no requests registered for the current stage
狀況: concurrent執行時出現error:
There are no requests registered for the current stage
原因: request set中有增加新的concurrent, 但已排程的request set未重排, 導致set執行時呼叫不到新增的程式
處理方式: 停止原排程, 另重排新排程並執行
There are no requests registered for the current stage
原因: request set中有增加新的concurrent, 但已排程的request set未重排, 導致set執行時呼叫不到新增的程式
處理方式: 停止原排程, 另重排新排程並執行
2019年4月18日 星期四
Oracle EBS: 客製SO上預設之warehouse (Defaulting rules)
在OM模組的設定中, 有defaulting rules可以使用, 除了warehouse之外, 還有很多欄位可以設定.
路徑:
Setup
-> Rules
-> Defaulting
在Entity Order Line中, 有Warehouse這項(圖1).
圖1.
點擊右下的 [Defaulting Rules...] 按鈕, 進入設定(圖2), 系統中有一組預設的, 把原有的停用, 另新增一組.
圖2.
在Default Sourcing Rules中, [Source Type] 指定 PL/SQL.API, 移至 [Default Source/Value] 欄, 出現設定畫面(圖3), 指定客製的Package Name和Function Name就大功告成了.
圖3.
function所使用的parameter及其中取值的方式有點特別, 可參考以下:
路徑:
Setup
-> Rules
-> Defaulting
在Entity Order Line中, 有Warehouse這項(圖1).
圖1.
點擊右下的 [Defaulting Rules...] 按鈕, 進入設定(圖2), 系統中有一組預設的, 把原有的停用, 另新增一組.
圖2.
在Default Sourcing Rules中, [Source Type] 指定 PL/SQL.API, 移至 [Default Source/Value] 欄, 出現設定畫面(圖3), 指定客製的Package Name和Function Name就大功告成了.
圖3.
function所使用的parameter及其中取值的方式有點特別, 可參考以下:
FUNCTION get_special_wh_id (p_database_object_name IN VARCHAR2,
p_attribute_code IN VARCHAR2)
RETURN NUMBER
IS
v_warehouse_id NUMBER;
v_org_id NUMBER;
v_line_type_id NUMBER;
v_price_list_id NUMBER;
v_item_id NUMBER;
v_cust_id NUMBER;
BEGIN
v_org_id := ont_line_def_hdlr.g_record.org_id;
v_line_type_id := ont_line_def_hdlr.g_record.line_type_id;
v_price_list_id := ont_line_def_hdlr.g_record.price_list_id;
v_item_id := ont_line_def_hdlr.g_record.inventory_item_id;
v_cust_id := ont_line_def_hdlr.g_record.sold_to_org_id;
v_warehouse_id := get_df_wh_id (v_org_id,
v_price_list_id,
v_item_id,
v_cust_id,
v_line_type_id);
RETURN (v_warehouse_id);
END;
2019年4月12日 星期五
Oracle EBS: 隱藏web畫面上的特定欄位
Personalize Page
-> Rendered
Site level選false, 代表預設所有人都看不到.
Responsibility level選true, 代表此responsibility看得到.
-> Rendered
Site level選false, 代表預設所有人都看不到.
Responsibility level選true, 代表此responsibility看得到.
2019年4月8日 星期一
Oracle EBS: ASCP執行memory-based snapshot worker時error
狀況: 出現以下error:
Calendar problem : mssdds_snp_other_demnads: 2458850 2458850 179
APP-MRP-22064: An internal error has occurred (mssdds_snp_other_demands, 1)
APP-MRP-20075: An internal error has occurred (mrsngi_snp_gross_rqmts, 8, , )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (mrsndi_snp_demand_info, 8, , )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (mrnspxt, 19, 10008, )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (mrnspgpt, 14, 202, 10008, )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (main, 13, , )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
原因:ASCP plan的日期區間超過calendar的日期區間, 也有SO的日期超過calendar的範圍
解法:
1.查看日期
select to_date(&julian_number,'j')Julian
from dual;
2.確認organization所使用的calendar, 並延長設定日期至少五年 (BOM/Setup/Calendars)
3.Rebuild calender (Tools/Build)
4.執行data collections
5.重執行ASCP plan
Ref:
1.MSCNSP Memory Based Snapshot On An Unconstrained Plan Errors With Calendar problem : APP-MRP-22064 mrsngs_snp_gross_rqmts (Doc ID 421723.1)
Calendar problem : mssdds_snp_other_demnads: 2458850 2458850 179
APP-MRP-22064: An internal error has occurred (mssdds_snp_other_demands, 1)
APP-MRP-20075: An internal error has occurred (mrsngi_snp_gross_rqmts, 8, , )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (mrsndi_snp_demand_info, 8, , )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (mrnspxt, 19, 10008, )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (mrnspgpt, 14, 202, 10008, )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
APP-MRP-20075: An internal error has occurred (main, 13, , )
@ERRORTET Cause: The current routine encountered the specified@ERRORTEXT x
原因:ASCP plan的日期區間超過calendar的日期區間, 也有SO的日期超過calendar的範圍
解法:
1.查看日期
select to_date(&julian_number,'j')Julian
from dual;
2.確認organization所使用的calendar, 並延長設定日期至少五年 (BOM/Setup/Calendars)
3.Rebuild calender (Tools/Build)
4.執行data collections
5.重執行ASCP plan
Ref:
1.MSCNSP Memory Based Snapshot On An Unconstrained Plan Errors With Calendar problem : APP-MRP-22064 mrsngs_snp_gross_rqmts (Doc ID 421723.1)
2019年4月2日 星期二
Oracle EBS: 工單關結, 直接人工效率差異出現過高有利差
狀況:
1.Routing中設定的Resource未變動
2.工單上的Applied高於Required, 應是不利差
原因:
1.財會維護的rate在接近月底時有調高了約36%
2.工單中多數成品在調高前就已完工入庫
3.標準人工的resource因採調高後的rate計算, 因此遠高於原先的估計值
後記:
這是在月中改設定值的後遺症哪...
1.Routing中設定的Resource未變動
2.工單上的Applied高於Required, 應是不利差
原因:
1.財會維護的rate在接近月底時有調高了約36%
2.工單中多數成品在調高前就已完工入庫
3.標準人工的resource因採調高後的rate計算, 因此遠高於原先的估計值
後記:
這是在月中改設定值的後遺症哪...
2019年4月1日 星期一
Oracle EBS: CST_INVALID_WIP error
錯誤訊息:
CST_INVALID_WIP error The wip entity is either not defined or does not have a period balance entry
狀況:
1.transaction停在pending, 無法產生分錄
2.transaction_source_id是個很大的負值 (後來才注意到)
解法:
1.請user提供交易當時所處理的工單
2.對應出wip_entity_id, 並更改transaction_source_id
3.重新處理未產生分錄的交易
後記:
原先以為是曾發生過的WIP_PERIOD_BALANCES無資料, 後來比對才發現transaction_source_id有問題, 目前還不知道原因.
參考資料都找了, 還是列一下.
補入資料:
INSERT INTO WIP_PERIOD_BALANCES
(ACCT_PERIOD_ID, WIP_ENTITY_ID,
REPETITIVE_SCHEDULE_ID, LAST_UPDATE_DATE,
LAST_UPDATED_BY, CREATION_DATE,
CREATED_BY, LAST_UPDATE_LOGIN,
ORGANIZATION_ID, CLASS_TYPE,
TL_RESOURCE_IN, TL_OVERHEAD_IN,
TL_OUTSIDE_PROCESSING_IN, PL_MATERIAL_IN,
PL_MATERIAL_OVERHEAD_IN, PL_RESOURCE_IN,
PL_OVERHEAD_IN, PL_OUTSIDE_PROCESSING_IN,
TL_MATERIAL_OUT, TL_MATERIAL_OVERHEAD_OUT, TL_RESOURCE_OUT,
TL_OVERHEAD_OUT, TL_OUTSIDE_PROCESSING_OUT,
PL_MATERIAL_OUT, PL_MATERIAL_OVERHEAD_OUT,
PL_RESOURCE_OUT, PL_OVERHEAD_OUT,
PL_OUTSIDE_PROCESSING_OUT,
PL_MATERIAL_VAR, PL_MATERIAL_OVERHEAD_VAR,
PL_RESOURCE_VAR, PL_OUTSIDE_PROCESSING_VAR,
PL_OVERHEAD_VAR, TL_MATERIAL_VAR, TL_MATERIAL_OVERHEAD_VAR,
TL_RESOURCE_VAR, TL_OUTSIDE_PROCESSING_VAR,
TL_OVERHEAD_VAR)
VALUES
(xxxx, yyyy, NULL, SYSDATE, 0, SYSDATE, 0, 0,
zzzz, ct, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0);
其中:
xxxx : Acct_period_id
yyyy : wip_entity_id
zzzz : organization_id
ct : class_type
Ref:
1.Oracle ERP R12. CST_INVALID_WIP (The wip entity is either not defined or does not have a period balance entry.) - Discrete Job
http://doggww.blogspot.com/2013/02/oracle-erp-r12-cstinvalidwip-wip-entity.html
2.CST_INVALID_WIP error The wip entity is either not defined or does not have a period balance entry (Doc ID 1531200.1)
CST_INVALID_WIP error The wip entity is either not defined or does not have a period balance entry
狀況:
1.transaction停在pending, 無法產生分錄
2.transaction_source_id是個很大的負值 (後來才注意到)
解法:
1.請user提供交易當時所處理的工單
2.對應出wip_entity_id, 並更改transaction_source_id
3.重新處理未產生分錄的交易
後記:
原先以為是曾發生過的WIP_PERIOD_BALANCES無資料, 後來比對才發現transaction_source_id有問題, 目前還不知道原因.
參考資料都找了, 還是列一下.
補入資料:
INSERT INTO WIP_PERIOD_BALANCES
(ACCT_PERIOD_ID, WIP_ENTITY_ID,
REPETITIVE_SCHEDULE_ID, LAST_UPDATE_DATE,
LAST_UPDATED_BY, CREATION_DATE,
CREATED_BY, LAST_UPDATE_LOGIN,
ORGANIZATION_ID, CLASS_TYPE,
TL_RESOURCE_IN, TL_OVERHEAD_IN,
TL_OUTSIDE_PROCESSING_IN, PL_MATERIAL_IN,
PL_MATERIAL_OVERHEAD_IN, PL_RESOURCE_IN,
PL_OVERHEAD_IN, PL_OUTSIDE_PROCESSING_IN,
TL_MATERIAL_OUT, TL_MATERIAL_OVERHEAD_OUT, TL_RESOURCE_OUT,
TL_OVERHEAD_OUT, TL_OUTSIDE_PROCESSING_OUT,
PL_MATERIAL_OUT, PL_MATERIAL_OVERHEAD_OUT,
PL_RESOURCE_OUT, PL_OVERHEAD_OUT,
PL_OUTSIDE_PROCESSING_OUT,
PL_MATERIAL_VAR, PL_MATERIAL_OVERHEAD_VAR,
PL_RESOURCE_VAR, PL_OUTSIDE_PROCESSING_VAR,
PL_OVERHEAD_VAR, TL_MATERIAL_VAR, TL_MATERIAL_OVERHEAD_VAR,
TL_RESOURCE_VAR, TL_OUTSIDE_PROCESSING_VAR,
TL_OVERHEAD_VAR)
VALUES
(xxxx, yyyy, NULL, SYSDATE, 0, SYSDATE, 0, 0,
zzzz, ct, 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0);
其中:
xxxx : Acct_period_id
yyyy : wip_entity_id
zzzz : organization_id
ct : class_type
Ref:
1.Oracle ERP R12. CST_INVALID_WIP (The wip entity is either not defined or does not have a period balance entry.) - Discrete Job
http://doggww.blogspot.com/2013/02/oracle-erp-r12-cstinvalidwip-wip-entity.html
2.CST_INVALID_WIP error The wip entity is either not defined or does not have a period balance entry (Doc ID 1531200.1)
訂閱:
文章 (Atom)