tomcat request 參數 utf-8 設定

參考文章 http://stackoverflow.com/questions/4470787/spring-rest-pathvariable-character-encoding

如果要在網址後傳遞 UTF-8 的參數http://localhost:8080/CattonOAuth1/tel/%E8%B3%87%E8%A8%8A

要設定 tomcat conf/server.xml


Connector port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443"  加上
              URIEncoding="UTF-8"

spring security oauth 1 client logout

這樣應該就可以作 logout的動作

OAuthSecurityContext context = OAuthSecurityContextHolder.getContext();
       
 Map accessTokens = context.getAccessTokens();
  accessTokens.remove(resource id);
  session.removeAttribute("OAUTH_TOKEN#"+resourceid);
       
   


參考文件
http://forum.springsource.org/showthread.php?104433-Revoked-expired-access-token-in-oauth1

會科查詢 sql, chart of account

SELECT a.segment_name,

        c.flex_value,

        d.description,

        a.application_column_name,

        c.parent_flex_value_low,

        a.segment_num,

        a.display_flag,

        a.display_size,

        a.maximum_description_len,

        a.concatenation_description_len,

        e.set_of_books_id

 FROM   applsys.fnd_id_flex_segments a,

        applsys.fnd_flex_values c,

        applsys.fnd_flex_values_tl d,

        gl_sets_of_books e

 WHERE  a.flex_value_set_id = c.flex_value_set_id

 AND    a.application_id = 101

 AND    a.id_flex_code = 'GL#'

 AND    c.flex_value_id = d.flex_value_id

 AND    d.LANGUAGE = USERENV('LANG')

 AND    e.set_of_books_id = :ledger_ID

 AND    e.chart_of_accounts_id = a.id_flex_num;

列出 chart account segment 明細資料

我們公司會計負責的ＧＬ人員不知道那邊有報表可以列出Segment Values
 ，一直要叫 MIS 提供給他，其實會計人員可以使用 GL的報表如下，就可以列出所有明細了。

Chart of Accounts - Segment Values Listing

Create an iFrame Window for Ext Js 4

使用 autoEL這個方式就可以

items : [{
        xtype : "component",
        autoEl : {
            tag : "iframe",
            src : "http://www.yahoo.com"
        }
    }]

參考網址
http://stackoverflow.com/questions/6025814/extjs-4-create-an-iframe-window

如何取消void prepayment 的付款

Prepayment invoice, and it has been fully applied. Therefore, the check can be Voided only after the prepayment has been unapplied.

如果是 prepayment的發票且狀態是 fully applied的話，要先將此發票作 unapplied 的動作，其付款 payment才可以作void.

資料一直卡在 AP_Invoices_Interface無法拋轉

如果資料一直卡在 AP_Invoices_Interface無法拋轉，而且 Rejection Report 也沒有資料的話，可以開啟 FND Log再跑一次 Payables Open Interface Import Program，如果有 log 有出現
IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromContext: Fatal: Exception when attempting to perform exact match for given payee context.
IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromContext: SQL code: -1422
IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromContext: SQL err msg: ORA-01422: exact fetch returns more than requested number of rows
IBY_DISBURSE_SUBMIT_PUB_PKG.deriveExactPayeeIdFromContext: EXIT
IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : ERROR: Exception occured during call to API 
IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : ERROR: Exception occured during call to API 
IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : SQLerr is :ORA-01422: exact fetch returns more than requested number of rows
IBY_DISBURSEMENT_COMP_PUB.Get_Default_Payment_Attribute : SQLerr is :ORA-01422: exact fetch returns more than requested number of rows

請下載 Patch:13857555:R12.AP.B for 12.1 (

R12: Generic Data Fix (GDF): Duplicate Payee in IBY_EXTERNAL_PAYEES_ALL [ID 1315812.1]

)

後執行 data fix‧