http://receivablesar.blogspot.com/2016/10/how-to-sweep-unprocessed-receipt-in.html
Issue:
Period not Closing due to Unprocessed Receipts
Solution:
IN this case please run the following update to sweep the data:
1. backup
create table ar_rcpt_hist_4781 as
select * from AR_CASH_RECEIPT_HISTORY_ALL
where CASH_RECEIPT_HISTORY_ID in (4861, 4862)
and CASH_RECEIPT_ID = 4781;
create table ar_rec_appl_4781 as
select * from AR_RECEIVABLE_APPLICATIONS_ALL
where CASH_RECEIPT_ID = 4781;
create table ar_pmt_sched_4781 as
select * from AR_PAYMENT_SCHEDULES_ALL
where CASH_RECEIPT_ID = 4781;
create table xla_ev_4781 as
select ev.* from XLA_EVENTS ev
where ev.entity_id in (select et.entity_id from xla.xla_transaction_entities et
where et.source_id_int_1 = 4781
and et.application_id = 222)
and ev.APPLICATION_ID = 222;
2. datafix
update AR_CASH_RECEIPT_HISTORY_ALL
set REVERSAL_GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where CASH_RECEIPT_HISTORY_ID in (4861)
and CASH_RECEIPT_ID = 4781;
commit;
update AR_CASH_RECEIPT_HISTORY_ALL
set GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where posting_control_id = -3
and gl_date between to_date('01-SEP-2016','DD-MON-YYYY')
and to_date('30-SEP-2016', 'dd-mon-yyyy')
and CASH_RECEIPT_ID = 4781;
commit;
update AR_RECEIVABLE_APPLICATIONS_ALL
set GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where posting_control_id = -3
and gl_date between to_date('01-SEP-2016','DD-MON-YYYY')
and to_date('30-SEP-2016', 'dd-mon-yyyy')
and CASH_RECEIPT_ID = 4781;
commit;
update AR_PAYMENT_SCHEDULES_ALL
set GL_DATE_CLOSED = to_date('01-OCT-2016','DD-MON-YYYY'),
ACTUAL_DATE_CLOSED = to_date('01-OCT-2016','DD-MON-YYYY'),
GL_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where CASH_RECEIPT_ID = 4781;
commit;
update xla.XLA_EVENTS ev
set ev.EVENT_DATE = to_date('01-OCT-2016','DD-MON-YYYY')
where ev.event_date between to_date('01-SEP-2016','DD-MON-YYYY')
and to_date('30-SEP-2016', 'dd-mon-yyyy')
and ev.event_status_code <> 'P'
and ev.APPLICATION_ID = 222
and ev.ENTITY_ID in (
select et.entity_id
from xla.xla_transaction_entities et
where et.source_id_int_1 = 4781
and et.application_id = 222);
commit;
Thursday, 27 October 2016
Thursday, 29 September 2016
AR Checking Query
http://receivablesar.blogspot.com/2016/09/ar-checking-query.html
Customer Checking
select count(*)
from RA_CUSTOMER_TRX_ALL ll,
ar_customers kk,
RA_CUST_TRX_LINE_GL_DIST_ALL jj,
gl_code_combinations gcc,
Ra_Cust_Trx_Types_all tt
where kk.CUSTOMER_ID = ll.BILL_TO_CUSTOMER_ID
and jj.CUSTOMER_TRX_ID = ll.CUSTOMER_TRX_ID
and gcc.CODE_COMBINATION_ID = jj.CODE_COMBINATION_ID
and tt.CUST_TRX_TYPE_ID=ll.CUST_TRX_TYPE_ID
and ll.ORG_ID=jj.ORG_ID
and tt.ORG_ID= jj.ORG_ID
and jj.ORG_ID=82 --479
and gcc.SEGMENT2 = '001'
and kk.customer_id !=1040 --001
--and gcc.SEGMENT2='002'
--and kk.CUSTOMER_ID !=1043 --002
-- and gcc.SEGMENT2='002'
-- and kk.CUSTOMER_ID !=1047 --002
---------------------------------------------------------
Transaction Type and Line Item Location Checking
select count(*)
from RA_CUSTOMER_TRX_ALL ll,
ar_customers kk,
RA_CUST_TRX_LINE_GL_DIST_ALL jj,
gl_code_combinations gcc,
gl_code_combinations gc,
Ra_Cust_Trx_Types_all tt
where kk.CUSTOMER_ID = ll.BILL_TO_CUSTOMER_ID
and jj.CUSTOMER_TRX_ID = ll.CUSTOMER_TRX_ID
and gcc.CODE_COMBINATION_ID = jj.CODE_COMBINATION_ID
and tt.CUST_TRX_TYPE_ID=ll.CUST_TRX_TYPE_ID
and gc.CODE_COMBINATION_ID=tt.GL_ID_REC
and gcc.SEGMENT2!=gc.SEGMENT2
Customer Checking
select count(*)
from RA_CUSTOMER_TRX_ALL ll,
ar_customers kk,
RA_CUST_TRX_LINE_GL_DIST_ALL jj,
gl_code_combinations gcc,
Ra_Cust_Trx_Types_all tt
where kk.CUSTOMER_ID = ll.BILL_TO_CUSTOMER_ID
and jj.CUSTOMER_TRX_ID = ll.CUSTOMER_TRX_ID
and gcc.CODE_COMBINATION_ID = jj.CODE_COMBINATION_ID
and tt.CUST_TRX_TYPE_ID=ll.CUST_TRX_TYPE_ID
and ll.ORG_ID=jj.ORG_ID
and tt.ORG_ID= jj.ORG_ID
and jj.ORG_ID=82 --479
and gcc.SEGMENT2 = '001'
and kk.customer_id !=1040 --001
--and gcc.SEGMENT2='002'
--and kk.CUSTOMER_ID !=1043 --002
-- and gcc.SEGMENT2='002'
-- and kk.CUSTOMER_ID !=1047 --002
---------------------------------------------------------
Transaction Type and Line Item Location Checking
select count(*)
from RA_CUSTOMER_TRX_ALL ll,
ar_customers kk,
RA_CUST_TRX_LINE_GL_DIST_ALL jj,
gl_code_combinations gcc,
gl_code_combinations gc,
Ra_Cust_Trx_Types_all tt
where kk.CUSTOMER_ID = ll.BILL_TO_CUSTOMER_ID
and jj.CUSTOMER_TRX_ID = ll.CUSTOMER_TRX_ID
and gcc.CODE_COMBINATION_ID = jj.CODE_COMBINATION_ID
and tt.CUST_TRX_TYPE_ID=ll.CUST_TRX_TYPE_ID
and gc.CODE_COMBINATION_ID=tt.GL_ID_REC
and gcc.SEGMENT2!=gc.SEGMENT2
Monday, 22 August 2016
Default Draft Option When Create Accounting From Menu Tools For Receivables
http://receivablesar.blogspot.com/2016/08/default-draft-option-when-create.html
As workaround you can apply the following personalization in both screens through Help > Diagnostics > Custom Code > Personalize.
Please see below screen prints on how to implement this.
Those additionally include on how to disable the other 2 options.
As workaround you can apply the following personalization in both screens through Help > Diagnostics > Custom Code > Personalize.
Please see below screen prints on how to implement this.
Those additionally include on how to disable the other 2 options.
Wednesday, 10 August 2016
Changing Standard Oracle Message
http://receivablesar.blogspot.com/2016/08/changing-standard-oracle-message.html
DB_TO_RUNTIME <
application shortname> .msb
Why does concurrent program FNDMDGEN: Generate Messages only create message files on the Concurrent Manager tier?
SOLUTION
As per the development guide:
Make a copy of the resulting file (which is on the server side), and transfer the copy to the appropriate mesg directory for your application on other machines as needed (concurrent processing servers, forms server machines). The file should have the same name (such as US.msb) in each location.
The program was never intended to create the message files on all tiers as such manual copying of the files are required as per the guide.
- goal: How to generate messages?
- fact: FNDMDMSG - Define Messages
- fact: FNDMDGEN - Generate Messages
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.2
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All
rights reserved.
FNDMDGEN: Generate Messages
+---------------------------------------------------------------------------+
Current system time is 10-AUG-2016 15:51:10
+---------------------------------------------------------------------------+
Writing file /apps/test/TEST/fs1/EBSapps/appl/ar/12.0.0/mesg/US648412.tmp
Moving file /apps/test/TEST/fs1/EBSapps/appl/ar/12.0.0/mesg/US.msb
to /apps/test/TEST/fs1/EBSapps/appl/ar/12.0.0/mesg/US648412.old.
Moving file /apps/test/TEST/fs1/EBSapps/appl/ar/12.0.0/mesg/US648412.tmp
to /apps/test/TEST/fs1/EBSapps/appl/ar/12.0.0/mesg/US.msb.
Processed a total of 7060 messages
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
No completion options were requested.
Output file size:
0
+---------------------------------------------------------------------------+
Concurrent request completed successfully
Current system time is 10-AUG-2016 15:51:11
+---------------------------------------------------------------------------+
Bounce the Application Tier to see Changes
Why does concurrent program FNDMDGEN: Generate Messages only create message files on the Concurrent Manager tier?
SOLUTION
As per the development guide:
Make a copy of the resulting file (which is on the server side), and transfer the copy to the appropriate mesg directory for your application on other machines as needed (concurrent processing servers, forms server machines). The file should have the same name (such as US.msb) in each location.
The program was never intended to create the message files on all tiers as such manual copying of the files are required as per the guide.
Thursday, 30 June 2016
Credit Memo against Invoice
http://receivablesar.blogspot.com/2016/06/credit-memo-against-invoice.html
Please Copy and Paste the Below URL in your Browser
http://oracler12applicationfunctional.blogspot.com/2014/03/credit-memo-against-invoice-in-r12.html
Please Copy and Paste the Below URL in your Browser
http://oracler12applicationfunctional.blogspot.com/2014/03/credit-memo-against-invoice-in-r12.html
Wednesday, 1 June 2016
Receipt Workbench Issue: Custom Menu has Tools -> View Accounting Disabled. How can I enable it? (Doc ID 417417.1)
http://receivablesar.blogspot.com/2016/06/applies-to-oracle-receivables-version-11.html
Receipt Workbench Issue: Custom Menu has Tools -> View Accounting Disabled. How can I enable it? (Doc ID 417417.1)
GOAL
When you navigate to Receipts window using a Custom Responsibility that has Custom menu attached, the Tools > View Accounting menu is grayed out/disabled. How do I enable this option?
Responsibility: Receivables manager
Navigation: Receipt > Receipts
Invoke Menu Tools > View Accounting
Receipt Workbench Issue: Custom Menu has Tools -> View Accounting Disabled. How can I enable it? (Doc ID 417417.1)
GOAL
When you navigate to Receipts window using a Custom Responsibility that has Custom menu attached, the Tools > View Accounting menu is grayed out/disabled. How do I enable this option?
Responsibility: Receivables manager
Navigation: Receipt > Receipts
Invoke Menu Tools > View Accounting
It is grayed out on Receipts form
Function SLA: View Accounting - Lines Inquiries needs to be attached to the menu.
Perform the following steps:
Responsibility: System Administrator
Navigation: Application > Menu
Query the menu being used
Add a new line and enter the following values:
Seq# - enter a unique value
Prompt - leave blank
SubMenu - leave blank
Function - SLA: View Accounting - Lines Inquiries
Description - enter a description
Grant - Yes
Save your changes. Now, View Accounting should be enabled on Tools Menu on Receipts form.
SOLUTION
Function SLA: View Accounting - Lines Inquiries needs to be attached to the menu.
Perform the following steps:
Responsibility: System Administrator
Navigation: Application > Menu
Query the menu being used
Add a new line and enter the following values:
Seq# - enter a unique value
Prompt - leave blank
SubMenu - leave blank
Function - SLA: View Accounting - Lines Inquiries
Description - enter a description
Grant - Yes
Save your changes. Now, View Accounting should be enabled on Tools Menu on Receipts form.
Tuesday, 31 May 2016
Receipt Workbench Error: Listing of APP-AR Errors (Doc ID 460857.1)
http://receivablesar.blogspot.com/2016/05/receipt-workbench-error-listing-of-app.html
Receipt Workbench Error: Listing of APP-AR Errors (Doc ID 460857.1)
Receipt Workbench Error: Listing of APP-AR Errors (Doc ID 460857.1)
Thursday, 24 March 2016
How to enable Manage Exceptions on Oracle Receivables R12.2.4
http://receivablesar.blogspot.com/2016/03/how-to-enable-manage-exceptions-on.html
How to Setup the New Manage Accounting Exception Program in Receivables? (Doc ID 1937611.1)
APPLIES TO:
Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.
GOAL
How can I setup the new Consolidated Review and Manage Accounting Exception Program in Receivables?
SOLUTION
Please perform the following:
1. For Release 12.1, the Manage Exception Functionality is available through Patch 22482346, and in the FEB-2016 RPC Patch 22471504. For Release 12.2, it is available through Patch 16634326.
NOTE: The program will ONLY sweep those transactions that are in error (xla_events.event_status_code = U and xla_events.process_status_code = I)
2. Once the patch is applied, please make sure the function Accounting Exception: Manage (AR_ARXSUMPS_MANAGE_EXP) is available in the AR Control Accounting Menu:
a. Under your System Administrator Responsibility, please go to Application --> Menu
b. Query for Menu = AR_CONTROL_ACC_GUI
3. When you try to close the period the system will check for Unposted items. If there are any, the Manage Exception button will be enabled in the Open/Close Period form.
4. Click on Manage Exceptions and you will get the following warning:
5. If you choose to sweep the transactions, you will get another warning stating that the changes cannot be undone.
How to Setup the New Manage Accounting Exception Program in Receivables? (Doc ID 1937611.1)
APPLIES TO:
Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.
GOAL
How can I setup the new Consolidated Review and Manage Accounting Exception Program in Receivables?
SOLUTION
Please perform the following:
1. For Release 12.1, the Manage Exception Functionality is available through Patch 22482346, and in the FEB-2016 RPC Patch 22471504. For Release 12.2, it is available through Patch 16634326.
NOTE: The program will ONLY sweep those transactions that are in error (xla_events.event_status_code = U and xla_events.process_status_code = I)
2. Once the patch is applied, please make sure the function Accounting Exception: Manage (AR_ARXSUMPS_MANAGE_EXP) is available in the AR Control Accounting Menu:
a. Under your System Administrator Responsibility, please go to Application --> Menu
b. Query for Menu = AR_CONTROL_ACC_GUI
3. When you try to close the period the system will check for Unposted items. If there are any, the Manage Exception button will be enabled in the Open/Close Period form.
4. Click on Manage Exceptions and you will get the following warning:
5. If you choose to sweep the transactions, you will get another warning stating that the changes cannot be undone.
Monday, 8 February 2016
GL_Interface containing duplicate records which has already been posted in GL transferred from Receivables (Query)
http://receivablesar.blogspot.com/2016/02/select-h.html
SELECT
H.NAME,
H.DEFAULT_EFFECTIVE_DATE,
H.DESCRIPTION,
H.JE_HEADER_ID,
A.JE_HEADER_ID,
H.JE_SOURCE,
H.JE_CATEGORY,
H.LEDGER_ID,
H.ACTUAL_FLAG,
H.PERIOD_NAME,
A.GL_SL_LINK_ID,
H.CODE_COMBINATION_ID,
H.ENTERED_DR,
H.ENTERED_CR
FROM
(
SELECT * FROM GL_INTERFACE
WHERE USER_JE_SOURCE_NAME='Receivables' AND USER_JE_CATEGORY_NAME='Sales Invoices' AND LEDGER_ID=2021 AND ACTUAL_FLAG='A' -- 783
) A,
(
SELECT
H.JE_SOURCE,
H.JE_CATEGORY,
H.LEDGER_ID,
H.ACTUAL_FLAG,
H.PERIOD_NAME,
gll.CODE_COMBINATION_ID,
gll.ENTERED_DR, gll.ENTERED_CR,
ael.gl_sl_link_id,
H.NAME,
H.DEFAULT_EFFECTIVE_DATE,
H.JE_HEADER_ID,
H.DESCRIPTION
FROM
GL_JE_HEADERS H,
GL_JE_LINES gll,
XLA_AE_HEADERS aeh,
XLA_AE_LINES ael,
XLA_EVENTS aea,
GL_IMPORT_REFERENCES gir
WHERE 1=1
AND H.JE_HEADER_ID=gll.JE_HEADER_ID
AND ael.gl_sl_link_id = gir.gl_sl_link_id
AND gir.gl_sl_link_table in ('APECL', 'XLAJEL','XLAJEL')
AND aea.application_id = 222
AND aea.event_id = aeh.event_id
AND aeh.ae_header_id = ael.ae_header_id
AND gll.je_header_id = gir.je_header_id
AND gll.je_line_num = gir.je_line_num
AND H.JE_SOURCE='Receivables'
AND H.JE_CATEGORY='Sales Invoices'
AND H.LEDGER_ID=2021
AND H.ACTUAL_FLAG='A'
--AND H.DEFAULT_EFFECTIVE_DATE='20-JUL-2009'
--AND H.PERIOD_NAME='JUL-09'
--AND H.DESCRIPTION LIKE '%200900160%'
) H
WHERE 1=1
AND H.JE_SOURCE=A.USER_JE_SOURCE_NAME
AND H.JE_CATEGORY=A.USER_JE_CATEGORY_NAME
AND H.LEDGER_ID=A.LEDGER_ID
AND H.ACTUAL_FLAG=A.ACTUAL_FLAG
AND H.PERIOD_NAME=A.PERIOD_NAME
--AND H.CODE_COMBINATION_ID=A.CODE_COMBINATION_ID
--AND (H.ENTERED_DR=A.ENTERED_DR or H.ENTERED_CR=A.ENTERED_CR)
AND H.GL_SL_LINK_ID=A.GL_SL_LINK_ID
SELECT
H.NAME,
H.DEFAULT_EFFECTIVE_DATE,
H.DESCRIPTION,
H.JE_HEADER_ID,
A.JE_HEADER_ID,
H.JE_SOURCE,
H.JE_CATEGORY,
H.LEDGER_ID,
H.ACTUAL_FLAG,
H.PERIOD_NAME,
A.GL_SL_LINK_ID,
H.CODE_COMBINATION_ID,
H.ENTERED_DR,
H.ENTERED_CR
FROM
(
SELECT * FROM GL_INTERFACE
WHERE USER_JE_SOURCE_NAME='Receivables' AND USER_JE_CATEGORY_NAME='Sales Invoices' AND LEDGER_ID=2021 AND ACTUAL_FLAG='A' -- 783
) A,
(
SELECT
H.JE_SOURCE,
H.JE_CATEGORY,
H.LEDGER_ID,
H.ACTUAL_FLAG,
H.PERIOD_NAME,
gll.CODE_COMBINATION_ID,
gll.ENTERED_DR, gll.ENTERED_CR,
ael.gl_sl_link_id,
H.NAME,
H.DEFAULT_EFFECTIVE_DATE,
H.JE_HEADER_ID,
H.DESCRIPTION
FROM
GL_JE_HEADERS H,
GL_JE_LINES gll,
XLA_AE_HEADERS aeh,
XLA_AE_LINES ael,
XLA_EVENTS aea,
GL_IMPORT_REFERENCES gir
WHERE 1=1
AND H.JE_HEADER_ID=gll.JE_HEADER_ID
AND ael.gl_sl_link_id = gir.gl_sl_link_id
AND gir.gl_sl_link_table in ('APECL', 'XLAJEL','XLAJEL')
AND aea.application_id = 222
AND aea.event_id = aeh.event_id
AND aeh.ae_header_id = ael.ae_header_id
AND gll.je_header_id = gir.je_header_id
AND gll.je_line_num = gir.je_line_num
AND H.JE_SOURCE='Receivables'
AND H.JE_CATEGORY='Sales Invoices'
AND H.LEDGER_ID=2021
AND H.ACTUAL_FLAG='A'
--AND H.DEFAULT_EFFECTIVE_DATE='20-JUL-2009'
--AND H.PERIOD_NAME='JUL-09'
--AND H.DESCRIPTION LIKE '%200900160%'
) H
WHERE 1=1
AND H.JE_SOURCE=A.USER_JE_SOURCE_NAME
AND H.JE_CATEGORY=A.USER_JE_CATEGORY_NAME
AND H.LEDGER_ID=A.LEDGER_ID
AND H.ACTUAL_FLAG=A.ACTUAL_FLAG
AND H.PERIOD_NAME=A.PERIOD_NAME
--AND H.CODE_COMBINATION_ID=A.CODE_COMBINATION_ID
--AND (H.ENTERED_DR=A.ENTERED_DR or H.ENTERED_CR=A.ENTERED_CR)
AND H.GL_SL_LINK_ID=A.GL_SL_LINK_ID
Saturday, 6 February 2016
Complete/Incomplete In Oracle Receivable
http://receivablesar.blogspot.com/2016/02/we-are-having-issue-that-during.html
we are having issue that during the complete/incomplete of transactions in Oracle Receivables the system got stuck or takes too much time. Kindly review and share the reason to overcome through this problem because whenever user perform this action it irritates too much.
Please follow the below Document attached and upload it to Support
All About the SQLT Diagnostic Tool (Doc ID 215187.1)
SQLT Usage Instructions (Doc ID 1614107.1
-----------------------------------------------------------------------------------------------------------
The analyze percents of schema of AR, ZX are 10%.
Your database is 11.2.0.1.0. You can use the Auto_Sample_Size when you run the the Gather Schema Statistics.
I suggest you should run the Gather Schema Statistics with Estimate percent
as null (Auto_Sample_Size) and schema name as both AR and ZX after
applying patch 16410424:R12.FND.B according to the document below.
Best Practices for Gathering Statistics with Oracle E-Business Suite ( Doc ID 1586374.1 )
Patch 16410424:R12.FND.B
Fix version:
AFSTATSB.pls 120.12.12010000.19 or higher.
Please test the this issue after running the Gather Schema Statistics.
we are having issue that during the complete/incomplete of transactions in Oracle Receivables the system got stuck or takes too much time. Kindly review and share the reason to overcome through this problem because whenever user perform this action it irritates too much.
Please follow the below Document attached and upload it to Support
All About the SQLT Diagnostic Tool (Doc ID 215187.1)
SQLT Usage Instructions (Doc ID 1614107.1
-----------------------------------------------------------------------------------------------------------
The analyze percents of schema of AR, ZX are 10%.
Your database is 11.2.0.1.0. You can use the Auto_Sample_Size when you run the the Gather Schema Statistics.
I suggest you should run the Gather Schema Statistics with Estimate percent
as null (Auto_Sample_Size) and schema name as both AR and ZX after
applying patch 16410424:R12.FND.B according to the document below.
Best Practices for Gathering Statistics with Oracle E-Business Suite ( Doc ID 1586374.1 )
Patch 16410424:R12.FND.B
Fix version:
AFSTATSB.pls 120.12.12010000.19 or higher.
Please test the this issue after running the Gather Schema Statistics.
Saturday, 23 January 2016
Wrong Distribution Account in Receivable Transaction
http://nethpsl.blogspot.com/2016/01/wrong-distribution-account-in.html
Please check with your business that they want to use the same Revenue Account for both transaction and credit memo.
If yes, AR: Use Invoice Accounting for Credit Memos is set to Yes other set it to NO.
Here is detail related to above profile.
"Note: Receivables does not require you to enter a Revenue Account
for Credit Memo transaction types if the profile option
AR: Use Invoice Accounting for Credit Memos is set to Yes.
Otherwise, you must enter a Revenue Account."
"AR: Use Invoice Accounting for Credit Memos:
This profile option determines whether to assign your credit memo
to the same accounts that are assigned to the invoice you are
crediting.
The value for this option can be set by the system administrator
at the site, application, responsibility, and user levels, but
cannot be updated by the user."
Please check with your business that they want to use the same Revenue Account for both transaction and credit memo.
If yes, AR: Use Invoice Accounting for Credit Memos is set to Yes other set it to NO.
Here is detail related to above profile.
"Note: Receivables does not require you to enter a Revenue Account
for Credit Memo transaction types if the profile option
AR: Use Invoice Accounting for Credit Memos is set to Yes.
Otherwise, you must enter a Revenue Account."
"AR: Use Invoice Accounting for Credit Memos:
This profile option determines whether to assign your credit memo
to the same accounts that are assigned to the invoice you are
crediting.
The value for this option can be set by the system administrator
at the site, application, responsibility, and user levels, but
cannot be updated by the user."
Subscribe to:
Posts (Atom)