目前日期文章:200803 (3)

瀏覽方式: 標題列表 簡短摘要
噗,我已經管到 INV 模組了,哈

在做 Pick Confirm 的畫面:Transact Move Order 發現兩個問題

1. Move Order 無法正確的 Closed
    在資料面系統已經完成所有的 Transaction,但是 Move Order 還是掛在 Move Order LOV 裡面,是不影響整體動作,但是還是怪怪的。幸運的是,在 Metalink 找到相關的修正:
    Subject : Move Order Outstanding Reservation for Cancelled or Closed Order Lines
   
Doc ID : Note:396254.1
   

    A. CORRECT DATA
    To implement the solution, please execute the following steps:

    1. Ensure that you have taken a backup of your system before applying the recommended solution.

    2. Run scripts that remove the reservations and move orders in a TEST environment first.
    The script names are i2471362.sql and INVCLRMO.sql. See the following notes for details:
    Note 199887.1 For the Reservation Cleanup - i2471362.sql
    Note 169677.1 For the Move Order Cleanup - INVCLRMO.sql

    3. If you are satisfied with the results, issue a commit.

    4. Confirm that the data is corrected when viewed in the Oracle Applications.

    5. Migrate the solution as appropriate to other environments.

    B. AVOID ISSUE
    1. Download and review the readme and pre-requisites for Patch 5037043.

    2. Ensure that you have taken a backup of your system before applying
    the recommended patch.

    3. Apply the patch in a test environment.

    4. Confirm the following file versions:
    INVVTROB.pls 115.128.115100.19
    MOTransaction.java 115.13.115100.2

    You can use the commands like the following:
    grep '$Header' $INV_TOP/patch/115/sql/INVVTROB.pls
    strings -a $JAVA_TOP/oracle/apps/inv/transaction/server/MOTransaction.class |grep '$Header'

    5. Retest the issue.

    6. Migrate the solution as appropriate to other environments.

2. 不能 Transact Multiple Line
    正常的情形下,按下 Transact Button,應該可以把這整張的 Move Order 的 Line 全都 Transact 掉,不過,那是正常的情況 

        To implement the solution, please execute the following steps:

    1. Download and review the readme and pre-requisites for <Patch>.5633132

    2. Ensure that you have taken a backup of your system before applying
    the recommended patch.

    3. Apply the patch in a test environment.

    4. Confirm the following file versions:
    forms/US/INVTOTRX.fmb 115.256.115100.36
    You can use the commands like the following:
    strings -a $XX_TOP/INVTOTRX.fmb |grep '$Header'

    5. Retest the issue.

    6. Migrate the solution as appropriate to other environments.

Aloz 發表在 痞客邦 留言(0) 人氣()

原本以為這會是偶發的狀況,沒想到上線之後幾乎是每天都有 User 碰到這樣的問題

目前確定以下狀況在輸入中文時會造成整個 Oracle ERP 當機 (應該是 Java 當掉):
1. 使用新注音的使用者,要做選字動作時,要先把字 "選" 起來再按 ↓,不然會當機
2. 使用舊注音或舊倉頡,如果注音符號或倉頡字碼在輸入時超過該欄最大字數,也會當機
    (這個好解一點,因為大部份會打很多中文字的欄位大多是備註欄,把該欄位拉長一點就可以)

謝謝 CK 提供的資訊, 我已順利的跟 Oracle Support 要到修改方式, 測試過也已經 OK, 再次感謝

ACTION PLAN
============
1. Edit the appsweb_<SID>_<machine>.cfg as follows:
* Backup the file pointed to by $FORMS60_WEB_CONFIG_FILE
* Edit this file
* Locate the line: networkRetries=0
* After networkRetries=0, add the following line:
inlineIME=false

2. Edit the appsbase.htm as follows:
* Backup the $OA_HTML/US/appsbase.htm file
* Edit $OA_HTML/US/appsbase.htm
* Locate the section labled "IE Section"
* At around line 430, add the parameter inlineIME as follows:
(Aloz: 此動作需重開 Apache )
...
// Separate the less-than character from PARAM to prevent Appletviewer
// from seeing these as param tags outside of an applet tag.
IEhtml += '<' + 'PARAM name=type value="' + xpluginmimetype + ' ">';
IEhtml += '<' + 'PARAM name=codebase value="' + xcodebase + '">';
IEhtml += '<' + 'PARAM name=code value="' + xcode + '">';
IEhtml += '<' + 'PARAM name=inlineIME value="' + false + '">';

Aloz 發表在 痞客邦 留言(5) 人氣()

正式上線還真夠忙的,每天光修問題看設定就花掉一整天的時間 Orz

上線之後遇到比較大的問題是 Oracle 的 Credit Check Rule,不過網路上對這方面的討論好像不多(還是我找不到 @@"),簡單的寫點心得

Credit Check 要正常運作有三個地方要同時設定,缺一不可:
1. Customer / Address Profile
2. Order Transaction Type
3. Payment Term

其中,Transaction Type 的設定要配合 Main Page 的 Credit Check 設定 Check Rule,而且只能設定在 Order Type 上,不能設在 Line Type。

Credit Check Rule 設定:
1. Credit Check Level / Credit Hold Level
    這個很明白,不過如果 Check Level 要 by Line,Exposure 的 "Use Pre-Calculated Exposure" 會被強制打勾,那在被打勾的情況之下,"Initialize Credit Summaries" 就要安排定期執行,Customer 的 Credit Limit 才會被 Refresh
2. Override Manual Release / Days to Honor Manual Release
    簡單的說,就是該訂單如果被 Release Hold,幾天之內不會再被套用該 Check Rule
3. Exposure
    這個頁面就是選擇 Credit 要計算到的數值,一般比較常用的就是:
    A. Include Open Receivable Balance (Open AR)
    B. Include Uninvoice Orders (Open SO)
    C. Include Orders Currently On Hold
    D. Maximum Days Past Due
    不過,Oracle 也大多數的系統一樣,不會計算在 AR Interface 的資料,但是如果 AR 的 Autoinvoice 有常常執行的話,這個問題就不算大

雖然 Oracle 只能針對 Order Type 去設定要不要做 Credit Check,但是一個 Order Type 可以有很多 Line Type,對我們公司來說,有些 Line Type 是不需要 Check Credit 的,可是 Oracle 又不能針對 Line Type 去設定是否檢查,所以我利用 OM 模組特有的 Defaulting Rule + Payment Term (No Credit Check) 去達成;不過這樣的設定當然還是有風險,因為 Defaulting Rule 只是幫 User 把預設值帶出來,如果 User 還是有權力把預設值改掉,那效果就不見了。

Aloz 發表在 痞客邦 留言(0) 人氣()

您尚未登入,將以訪客身份留言。亦可以上方服務帳號登入留言

請輸入暱稱 ( 最多顯示 6 個中文字元 )

請輸入標題 ( 最多顯示 9 個中文字元 )

請輸入內容 ( 最多 140 個中文字元 )

請輸入左方認證碼:

看不懂,換張圖

請輸入驗證碼