4/19/2012

實務_關於Debit Note與Credit Note的分別


簡單的說, Credit Note就是承諾給錢, Debit Note就是索討欠款.


要開折讓單, 請問英文是用debit note 還是 credit note ?
答: 賣方給予買方折讓, 由賣方開Credit Note給買方, 買方可用來抵付別筆帳款或下次貨款; 換句話說, Credit Note就是等於要給錢的折讓單, 一旦開出等於送錢給對方.  


我做買方, 打算少付錢給對方, 請問在英文中 有沒有分別 ? 我是要開debit note 還是 credit note?
答: 要減少付錢給對方, 要開debit note, 由收款方簽認才生效. 例如買方退貨或因瑕疵而要求折讓時, 應就退或之數量及金額開立Debit Note給賣方, 賣方收到退貨或同意給予折讓時, 應開具Credit Note給買方.


同理, 賣方出貨或增加出貨、新增收費、追索欠款等等, 都應開立Debit Note給買方. 在出貨時, 賣方開的發票(Invoice)就是Debit Note的一種, 只是Invoice並不表示已否收款, Debit Note則必是尚未收款.


我記得是不管買方 或 賣方 沒有分別的都是叫做 credit note (折讓單)?答: 那要看是誰開出的Credit Note:
-- 賣方開出的Credit Note代表賣方要支付或少收這筆錢.
-- 買方開出的Credit Note代表買方承諾要付這筆錢.
總而言之, Credit Note就是代表錢, 不論對方簽署與否都有效, 故開立要謹慎. 


-------------------------------------------------------------------------------------------------------------------------------------

在Oracle AP之應付帳款模組中,將應付憑據(Invoice)分成了「standard」、「Credit memo」、「Debit memo」….等幾種不同的型式,而其中的Credit memo與Debit memo 之間的差異以及使用時機,可以簡單的描述如下:
Credit Memo :
當廠商將某張訂單的商品寄送至本公司後,由於其他因素(如:商品有瑕疵…等)主動要給予我們額外的折扣時,廠商會先開立一張credit Memo給我們, 當我們收到該通知時便可將其輸入到oracle AP的應付帳款系統中 , 接著再將此張credit memo invoice與之前的invoice 來做match,從而減少我們的應付帳款。

Debit Memo :
當我們要退貨給某家供應商時,需先通知該供應商,並待其核可此項退貨後,我們便可開立一張Debit memo形式的invoice,並將此張Debit memo invoice與之前的invoice 來做match,從而減少我們的應付帳款,接著再將商品退還給供應商。而此種Debit memo invoice在台灣比較少使用到,通常是用在廠商送過來的產品,並非是我方訂單所要求的項目時,才會開立一張Debit memo形式的invoice,來減少應付帳款。

簡單的說
Credit memo: 便是『廠商』 通知 『我們』 要給予貨品的折扣時,會開立credit memo 給我們,接著我們便要在oracle AP的應付帳款系統中輸入此張credit memo,而此種型式的 invoice便稱為credit memo invoice。
Debit memo: 便是『我方』要求『廠商』給與貨品的折讓時(如退貨),我們便要開立debit memo invoice,並且通知廠商,而此種型式的invoice便稱為 debit memo invoice。

(本文由中原資管羅國銘提供)


內文回應:


hello
隨便閒逛看到你的網頁
對於你這麼認真將oracle erp的學習心得記錄於blog中
深感敬佩
但本人在oracle erp的財務模組有幾年的經驗
不禁想要交流一下
你的解釋似乎來自user guide的觀念
但在台灣的實務中這樣解釋似乎較為恰當
credit memo or debit memo均為應付帳款的減項
但若帳務處理中需要區分進貨折讓與進貨退出的科目的話
則可以credit memo表進貨折讓(與量無關)
以debit memo表進貨退出(與量有關自然得原自po模組)
因為這樣便可避免oracle本身標準功能中
match 原invoice or po時均為原科目迴轉之由
然後可透過標準報表
於參數中選擇invoice type
自然可求得全年度之進貨折讓與進貨退出之總金額

當然
若帳務處理無需出現進貨折讓或是進貨退出之科目者
則兩者皆視為應付帳款的減項
只是是由廠商主動或是我方主動罷了

希望以上在實務上的運用
能更讓你了解
謝謝



來源:http://blog.roodo.com/oracle_erp/archives/4119969.html#comments

4/10/2012

問題記錄_AP_錯誤 APP-SQLAP-10199

Symptoms
--------------------------------------------------------------------
應付模組下,建立商業發票批次(Invoice Batches)時(功能路徑為Invoices:Entry:Invoice Batches)提示下列錯誤資訊:


APP-SQLAP-10199: You cannot navigate to the Invoice Batches window because invoice batch control is not enable for your system.
If you want to enable invoice batch control for your system, then ask your system administrator to enable the profile option AP: Use Invoice Batch Controls in the System Profile Options window.



Issue
--------------------------------------------------------------------

AP模組中有兩種立帳方式,一為Invoice Batches、另一為Invoices,二者只能取其一,因此需透過Profile設定來決定。
切換至系統管理員(System Administrator)職責,設定功能路徑為Profile:System,Profile Option Name為AP: Use Invoice Batch Controls,將Site由No改為Yes。

11/25/2010

問題記錄_FA_APP-OFA-48392 Error When Adding a New Asset in the Asset Workbench


APP-OFA-48392 Error When Adding a New Asset in the Asset Workbench [ID 275200.1]

 修改时间 04-DEC-2008     类型 PROBLEM     状态 PUBLISHED 

Applies To

Oracle Assets - Version: 11.5.9
This problem can occur on any platform.
FAXASSET - Asset Workbench 

Symptoms

When adding a new asset in Asset Workbench, in the Assignments window, when 
clicking Done, an error message appears: 

APP-OFA-48392: Unable to get the concurrent request status using procedure.

Cause

Invalid depreciation run status showing as 'Submitted'.

Fix


Change the Status to 'Error', resubmit Run Depreciation and let it complete
normally, rollback depreciation, then enter new assets.

1) Refresh a TEST instance with the Production data when experiencing this issue.

2) Run this update:

update fa_book_controls
set deprn_status = 'E'
where book_type_code = '&book'
and deprn_status = 'S';
commit;

3) Resubmit Run Depreciation WITHOUT Close Period option.

4) Rollback Depreciation.

Always TEST results prior to implementing in a Production database.

IMPORTANT
Help us improve our service. If you have any comments or questions regarding the solution
as documented in this Note (or ANY other questions related to Oracle Assets), please post on the
Oracle Assets Technical Forum on MetaLink. The FA Forum is monitored on a daily basis
by Oracle Support Services (OSS), and response time is generally within 24 hours.

Thank you for using MetaLink!

10/28/2010

問題記錄_FA_Create Accounting ERROR MESSAGE NUMBER:95937

Symptoms
----------------------------------------------------------------------------------------------------------------
於固定資產模組下,執行創建會計請求(Create Accounting)後,檢視輸出的報表(Subledger Accounting Program Report),內容顯示錯誤訊息:

Message Number:
95937
Message:
There are either non-accountable events existing in the system, or events which could not be processed because no data could be found on transaction objects. Please enable the profile option SLA: Enable Diagnostics,create accounting again, and run the report Transaction Objects Disagnostics to identify the problem.


Cause
----------------------------------------------------------------------------------------------------------------
造成此錯誤的原因主要分為兩項:
1.Oracle Patch Needed.
2.Unprocessed Records Exists(Orphan Records).


其中Patch是在Oracle Support查詢時,幾乎所有的資料都顯示要打這個Patch:8738842。另外在查詢會計事件的時候,也發現了有未處理並沒有產生分錄的事件(Accounting Events)。
經過Reproduce後,基本上確認是用戶手動新增固定資產後,又手動將其資產刪除,造成Orphan Records所引起的錯誤。


Solution
----------------------------------------------------------------------------------------------------------------
1)先執行Apps Check(可略過):
Please run the Diagnostics: Apps Check program for Oracle Assets

If the program doesn't exist, please add the program as follows
Sysadmin > Security > Responsibility > Request

Query the request as follows
Group - All reports
Application - Assets

And add the Diagnostics: Apps Check as follows
Type - Program
Name - from the list of value select Diagnostics: Apps Check
Application - Oracle Order Management

Save the changes. Now you can run the Diagnostics: Apps Check with
Assets as Parameter



依自身系統環境進行參數輸入,並檢查輸出的報表。


2)檢查下列Query:
Select bug_number, creation_date from ad_bugs where bug_number IN('8738842');


Select owner,object_name,object_type, status From all_objects Where status = 'INVALID' And object_name LIKE 'FA%';


3)在固定資產模組下查詢到未處理並沒有分錄的事件(Inquiry->Subledger Accounting->Accounting Events)。


4)執行下列Query檢查分錄事件表單(Table),可依情況自行修改一些ID參數:
SELECT xlt.ledger_id,
xlt.valuation_method,
xe.event_id,
xlt.entity_id,
xe.event_type_code,
xe.event_status_code,
xlt.transaction_number,
xe.event_date
FROM xla_events xe,
xla.xla_transaction_entities xlt
WHERE xe.entity_id = xlt.entity_id
AND xe.application_id = xlt.application_id
AND xlt.source_application_id = 140
AND xlt.entity_code = 'TRANSACTIONS'
AND xe.event_status_code <> 'P'
AND NOT EXISTS (SELECT fth.transaction_header_id
FROM fa_transaction_headers fth
WHERE fth.transaction_header_id = xlt.source_id_int_1);



5)備份及刪除表單中的Orphan Events
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 the following scripts in a TEST environment first:

a. Create table to list down the orphan records.

CREATE TABLE fa_orphan_events AS
SELECT xlt.ledger_id,
xlt.valuation_method,
xe.event_id,
xlt.entity_id,
xe.event_type_code,
xe.event_status_code,
xlt.transaction_number,
xe.event_date
FROM xla_events xe,
xla.xla_transaction_entities xlt
WHERE xe.entity_id = xlt.entity_id
AND xe.application_id = xlt.application_id
AND xlt.source_application_id = 140
AND xlt.entity_code = 'TRANSACTIONS'
AND xe.event_status_code <> 'P'
AND NOT EXISTS (SELECT fth.transaction_header_id
FROM fa_transaction_headers fth
WHERE fth.transaction_header_id = xlt.source_id_int_1);

b. Create Backup tables

CREATE TABLE xla_transaction_entities_bk
AS SELECT * FROM xla_transaction_entities xte
WHERE xte.application_id = 140
AND EXISTS (
SELECT xe.entity_id
FROM xla_events xe,fa_orphan_events oe
WHERE xe.event_id = oe.event_id
AND xe.entity_id = xte.entity_id
AND xe.application_id = 140);

CREATE TABLE xla_events_bk
AS SELECT * FROM xla_events xe
WHERE EXISTS (
SELECT oe.event_id
FROM fa_orphan_events oe
WHERE xe.event_id = oe.event_id)
AND xe.application_id = 140;


c. Delete the unwanted orphan records



DELETE FROM xla_transaction_entities xte
WHERE xte.application_id = 140
AND EXISTS (
SELECT oe.entity_id
FROM fa_orphan_events oe
WHERE oe.entity_id = xte.entity_id);

DELETE FROM xla_events xe
WHERE xe.application_id = 140
AND EXISTS (
SELECT oe.event_id
FROM fa_orphan_events oe
WHERE xe.event_id = oe.event_id);

COMMIT;

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

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

You can do this by running Sub-ledger Period Close Exception Report.

5. If you are satisfied that the issue is resolved, migrate the solution as appropriate to other environments.



6)再次執行Create Accounting請求,並確認錯誤訊息解除。

10/19/2010

問題記錄_GL_APP-FND-01388: Cannot read value for profile option FND_DEVELOPER_MODE in routine &ROUTINE

Symptoms
----------------------------------------------------------------------------------------------------------------
於修改總帳(GL)Segment Values的內容後,回到Key Flexfield Segments視窗重新進行Compile,於Requests查看沒有錯誤訊息,但重新進到Segment Values就會發生錯誤:「APP-FND-01388: Cannot read value for profile option FND_DEVELOPER_MODE in routine &ROUTINE」。

Cause
----------------------------------------------------------------------------------------------------------------
Form並未編譯(Compile)成功。

Solution
----------------------------------------------------------------------------------------------------------------
by METALink.


To implement the solution, please execute the following steps::

-1. Go into the responsibility: Navigate to the AU_TOP/resource directory

-2. Compile and generate manually CSQKMENU.pll, ensure CSQKMENU.plx gets generated successfully.

-3. Then compile BENAUTHE.pll and BENAUTHE.fmb successfully.

-4. Retest the scenario. This should fix the issue.

-5. Migrate the solution as appropriate

by myself.

我用appl的權限帳戶登入到R12 APP的Server上,執行以下指令即可(此為一行指令,因網頁才分段的):
frmcmp module=$AU_TOP/resource/CSQKMENU.pll userid=apps/apps output_file=$AU_TOP/resource/CSQKMENU.plx module_type=library batch=no compile_all=special

結果:

Forms 10.1 (Form Compiler) Version 10.1.2.2.0 (Production)

Forms 10.1 (Form Compiler): Release  - Production

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
     With the Partitioning, OLAP, Data Mining and Real Application Testing options
PL/SQL Version 10.1.0.5.0 (Production)
Oracle Procedure Builder V10.1.2.2.0 - Production
Oracle Virtual Graphics System Version 10.1.2.0.0 (Production)
Oracle Multimedia Version 10.1.2.0.2 (Production)
Oracle Tools Integration Version 10.1.2.0.2 (Production)
Oracle Tools Common Area Version 10.1.2.0.2
Oracle CORE     10.1.0.5.0      Production
Compiling library CSQKMENU...
  Invalidating Package Spec CS_QK_FILTER_LIB......
  Invalidating Package Spec CSQKMENU......
  Invalidating Package Body CS_QK_FILTER_LIB......
  Invalidating Package Body CSQKMENU......
  Compiling Package Spec CS_QK_FILTER_LIB......
  Compiling Package Spec CSQKMENU......
  Compiling Package Body CS_QK_FILTER_LIB......
  Compiling Package Body CSQKMENU......
 Done.