http://aporaclepayables.blogspot.com/2016/02/sorry-we-couldnt-find-excel-error.html
In my case
I Navigate to Excel Options Addins and press go from Excel Addin and uncheck the file creating error.
Wednesday 24 February 2016
Remit to Supplier
http://aporaclepayables.blogspot.com/2016/02/q.html
Q.
We are facing an issue in 12.2.4 that in invoice header "Remit to Supplier name" field is blank when we enter invoice but In the previous version of 12.0.6 it was not blank,it shows Supplier Name when we enter invoice.So we are facing some issues so kindly guide us about this issue.
R.
Starting with 12.1.1 and above, it is intended functionality that Remit to Supplier and site are not mandatory on invoice workbench.
Hence the fields do not have defaults like in 12.0
If the invoice requires payment to be made to a third party, user can use the LOV for the field and choose a third party.
Please note that in Payables Options , Invoices tab the option Allow Remit-To Supplier Override needs to be set up.
Q.
We are facing an issue in 12.2.4 that in invoice header "Remit to Supplier name" field is blank when we enter invoice but In the previous version of 12.0.6 it was not blank,it shows Supplier Name when we enter invoice.So we are facing some issues so kindly guide us about this issue.
R.
Starting with 12.1.1 and above, it is intended functionality that Remit to Supplier and site are not mandatory on invoice workbench.
Hence the fields do not have defaults like in 12.0
If the invoice requires payment to be made to a third party, user can use the LOV for the field and choose a third party.
Please note that in Payables Options , Invoices tab the option Allow Remit-To Supplier Override needs to be set up.
Saturday 20 February 2016
Payment Accounting Processed when create Accounting Program runs without clearing the Payment
http://aporaclepayables.blogspot.com/2016/02/payment-accounting-processed-when.html
R12.2.4 Functionality
Payment Accounting is when Payment Clears
1.Made the Invoice
2.Validate the Invoice
3.Made the Payment
4.Run the Create Accounting Program (Invoice Accounted to Yes & Payment Accounting to Processed)
5.Clears the Payment from Cash Management (Payment goes on Accounting Partial)
6.Run the Create Accounting again (Payment Accounting is Processed)
R12.0.6 Functionality
Payment Accounting is when Payment Clears
1.Made the Invoice
2.Validate the Invoice
3.Made the Payment
4.Run the Create Accounting Program (Invoice Accounted to Yes & Payment Accounting to Unprocessed)
5.Clears the Payment from Cash Management (Payment Accounting is still Unprocessed)
6.Run the Create Accounting again (Payment Accounting is Processed)
As you can see above there is a difference in Accounting Status Starts from step 4 in both 12.0.6 and 12.2.4 Functionalities.
Is this is a Standard Functionality in R12.2.4 that the Payment Accounting is Processed two times One Accounting through Program after Payment and Second Accounting after Clearing?
--------------------------------------------------------------------------------------------------------------------------
Initially system used to work as below
R12.0.6
1- Create and Account for an Invoice
2- Pay in Full
3- Run Create Accounting
In this case, the Payment Created remains in status U/U (unprocessed) in xla_events
This is modified in the bug 9245156 to work as below
R12.2.4
1- Create and Account for an Invoice
2- Pay in Full
3-Run Create Accounting
Now system will show the Payment is accounted and stamp Payment Created status N/P
This mainly to avoid the Payment showing in period close exception report before clearing the Payment.
This is modified in file apslappb.pls and system is working as intended in current version of application
This changes are done due to Period Closing Purpose
Hope this clarifies
R12.2.4 Functionality
Payment Accounting is when Payment Clears
1.Made the Invoice
2.Validate the Invoice
3.Made the Payment
4.Run the Create Accounting Program (Invoice Accounted to Yes & Payment Accounting to Processed)
5.Clears the Payment from Cash Management (Payment goes on Accounting Partial)
6.Run the Create Accounting again (Payment Accounting is Processed)
R12.0.6 Functionality
Payment Accounting is when Payment Clears
1.Made the Invoice
2.Validate the Invoice
3.Made the Payment
4.Run the Create Accounting Program (Invoice Accounted to Yes & Payment Accounting to Unprocessed)
5.Clears the Payment from Cash Management (Payment Accounting is still Unprocessed)
6.Run the Create Accounting again (Payment Accounting is Processed)
As you can see above there is a difference in Accounting Status Starts from step 4 in both 12.0.6 and 12.2.4 Functionalities.
Is this is a Standard Functionality in R12.2.4 that the Payment Accounting is Processed two times One Accounting through Program after Payment and Second Accounting after Clearing?
--------------------------------------------------------------------------------------------------------------------------
Initially system used to work as below
R12.0.6
1- Create and Account for an Invoice
2- Pay in Full
3- Run Create Accounting
In this case, the Payment Created remains in status U/U (unprocessed) in xla_events
This is modified in the bug 9245156 to work as below
R12.2.4
1- Create and Account for an Invoice
2- Pay in Full
3-Run Create Accounting
Now system will show the Payment is accounted and stamp Payment Created status N/P
This mainly to avoid the Payment showing in period close exception report before clearing the Payment.
This is modified in file apslappb.pls and system is working as intended in current version of application
This changes are done due to Period Closing Purpose
Hope this clarifies
Friday 19 February 2016
Solution on TEST server for orphan payments
http://aporaclepayables.blogspot.com/2016/02/solution-on-test-server-for-orphan.html
To Delete Check from System:
I was applied patch p10025422_R12.AP.A_R12_GENERIC.zip but before applying the patch I have some changes in /apps/10025422/ap/patch/115/sql/ap_invalid_check_sel.sql . Please check the below query i have comment one line APH.POSTED_FLAG <>''Y''.
After that I had applied /apps/10025422/ap/patch/115/sql/ap_invalid_check_fix.sql and my problem is resolved .
Note : I had applied above action plan on TEST, can I follow the same as on Production.
'CREATE TABLE AP_TEMP_DRIVER_10025422 AS
SELECT AC.CHECK_ID,
AC.CHECK_NUMBER,
AC.AMOUNT,
AC.STATUS_LOOKUP_CODE,
APH.ACCOUNTING_EVENT_ID,
APH.POSTED_FLAG,
AC.VENDOR_ID,
AC.VENDOR_SITE_ID,
AC.PAYMENT_ID,
AC.ORG_ID,
AC.PAYMENT_DOCUMENT_ID,
''Y'' PROCESS_FLAG
FROM AP_CHECKS_ALL AC,
AP_PAYMENT_HISTORY_ALL APH
WHERE AC.PAYMENT_ID IS NULL
AND AC.STATUS_LOOKUP_CODE NOT IN (''OVERFLOW'',''SET UP'',''SPOILED'')
AND AC.CHECK_ID=APH.CHECK_ID
AND NVL(APH.HISTORICAL_FLAG,''N'') <> ''Y''
--AND APH.POSTED_FLAG <>''Y''
AND NOT EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP
WHERE AIP.CHECK_ID = AC.CHECK_ID)
AND EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP1,
AP_CHECKS_ALL AC1
WHERE AIP1.CHECK_ID = AC1.CHECK_ID
AND AC.ORG_ID = AC1.ORG_ID
AND ((AC.VENDOR_ID = AC1.VENDOR_ID
AND AC.VENDOR_SITE_ID = AC1.VENDOR_SITE_ID)
OR AC.PAYMENT_DOCUMENT_ID =AC1.PAYMENT_DOCUMENT_ID)
AND AC.CHECK_NUMBER = AC1.CHECK_NUMBER ) ';
cd /apps/10025422/ap/patch/115/sql
Please follow the instruction on README.txt for patch 10025422
connect apps/apps
run apgdfals.pls
run apgdfalb.pls
For 12.2.4
Apply GDF infrastructure patch 21816876:R12.AP.C to get the latest data fix package files (apgdfals.pls and apgdfalb.pls).
run ap_invalid_check_sel.sql
--before fix the effected transaction please run beow command on production server
/*Update process_flag in AP_TEMP_DRIVER_10025422 to 'N'
for transactions that should not be operated on*
run ap_invalid_check_fix.sql
Note: Do not need to apply patch you just follow the above action plan.
--------------------------------------------------------------------------------------------------------------------------
To Void Check without any Accounting:
Please Download the script from the below link
https://drive.google.com/open?id=0B30-kT1pIOm_dGJUOFRFNFpzNmM
Please execute the script:ap_void_check_mark_np_no_aip.sql in the cloned instance.
Pass the check_id :
Detailed steps:
Verify whether Payment Voided and update us with the results
1.Apply the fix:ap_void_check_mark_np_no_aip.sql .The fix script will do the following
a.The Payment Cancellation event will be generated for the missing check_id in ap_invoice_payments which is existed in ap_payment_history.
b.The XLA_EVENTS status will be set to N/P for the Cancellation event.
c.The posted_flags in ap_payment_history_all,ap_invoice_payments_all,ap_invoice_distributions set to Y
d.Finally,the status of the check will be set to "Voided"
2.Retest the issue
3.Migrate the solution to the appropriate environments
To Delete Check from System:
I was applied patch p10025422_R12.AP.A_R12_GENERIC.zip but before applying the patch I have some changes in /apps/10025422/ap/patch/115/sql/ap_invalid_check_sel.sql . Please check the below query i have comment one line APH.POSTED_FLAG <>''Y''.
After that I had applied /apps/10025422/ap/patch/115/sql/ap_invalid_check_fix.sql and my problem is resolved .
Note : I had applied above action plan on TEST, can I follow the same as on Production.
'CREATE TABLE AP_TEMP_DRIVER_10025422 AS
SELECT AC.CHECK_ID,
AC.CHECK_NUMBER,
AC.AMOUNT,
AC.STATUS_LOOKUP_CODE,
APH.ACCOUNTING_EVENT_ID,
APH.POSTED_FLAG,
AC.VENDOR_ID,
AC.VENDOR_SITE_ID,
AC.PAYMENT_ID,
AC.ORG_ID,
AC.PAYMENT_DOCUMENT_ID,
''Y'' PROCESS_FLAG
FROM AP_CHECKS_ALL AC,
AP_PAYMENT_HISTORY_ALL APH
WHERE AC.PAYMENT_ID IS NULL
AND AC.STATUS_LOOKUP_CODE NOT IN (''OVERFLOW'',''SET UP'',''SPOILED'')
AND AC.CHECK_ID=APH.CHECK_ID
AND NVL(APH.HISTORICAL_FLAG,''N'') <> ''Y''
--AND APH.POSTED_FLAG <>''Y''
AND NOT EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP
WHERE AIP.CHECK_ID = AC.CHECK_ID)
AND EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP1,
AP_CHECKS_ALL AC1
WHERE AIP1.CHECK_ID = AC1.CHECK_ID
AND AC.ORG_ID = AC1.ORG_ID
AND ((AC.VENDOR_ID = AC1.VENDOR_ID
AND AC.VENDOR_SITE_ID = AC1.VENDOR_SITE_ID)
OR AC.PAYMENT_DOCUMENT_ID =AC1.PAYMENT_DOCUMENT_ID)
AND AC.CHECK_NUMBER = AC1.CHECK_NUMBER ) ';
cd /apps/10025422/ap/patch/115/sql
Please follow the instruction on README.txt for patch 10025422
connect apps/apps
run apgdfals.pls
run apgdfalb.pls
For 12.2.4
Apply GDF infrastructure patch 21816876:R12.AP.C to get the latest data fix package files (apgdfals.pls and apgdfalb.pls).
run ap_invalid_check_sel.sql
--before fix the effected transaction please run beow command on production server
/*Update process_flag in AP_TEMP_DRIVER_10025422 to 'N'
for transactions that should not be operated on*
run ap_invalid_check_fix.sql
Note: Do not need to apply patch you just follow the above action plan.
--------------------------------------------------------------------------------------------------------------------------
To Void Check without any Accounting:
Please Download the script from the below link
https://drive.google.com/open?id=0B30-kT1pIOm_dGJUOFRFNFpzNmM
Please execute the script:ap_void_check_mark_np_no_aip.sql in the cloned instance.
Pass the check_id :
Detailed steps:
Verify whether Payment Voided and update us with the results
1.Apply the fix:ap_void_check_mark_np_no_aip.sql .The fix script will do the following
a.The Payment Cancellation event will be generated for the missing check_id in ap_invoice_payments which is existed in ap_payment_history.
b.The XLA_EVENTS status will be set to N/P for the Cancellation event.
c.The posted_flags in ap_payment_history_all,ap_invoice_payments_all,ap_invoice_distributions set to Y
d.Finally,the status of the check will be set to "Voided"
2.Retest the issue
3.Migrate the solution to the appropriate environments
Thursday 18 February 2016
How to Check orphan Payments through SQL Query
http://aporaclepayables.blogspot.com/2016/02/how-to-check-orphan-payments-through.html
select check_id, check_number from ap_checks_all where check_id
not in
(select check_id from ap_invoice_payments_all)
-----------------------------------------------------------------------------
select aa.check_id, aa.check_number, aa.BANK_ACCOUNT_NAME, aa.AMOUNT, aa.CLEARED_DATE, aa.CHECK_DATE, aa.CREATED_BY from ap_checks_all aa where check_id
not in
(select check_id from ap_invoice_payments_all)
----------------------------------------------------------------------------
SELECT AC.CHECK_ID,
AC.CHECK_NUMBER,
AC.AMOUNT
FROM AP_CHECKS_ALL AC,
AP_PAYMENT_HISTORY_ALL APH
WHERE AC.PAYMENT_ID IS NULL
AND AC.STATUS_LOOKUP_CODE NOT IN ('OVERFLOW','SET UP','SPOILED')
AND AC.CHECK_ID=APH.CHECK_ID
AND NVL(APH.HISTORICAL_FLAG,'N') <> 'Y'
--AND APH.POSTED_FLAG <>'Y'
AND NOT EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP
WHERE AIP.CHECK_ID = AC.CHECK_ID)
AND EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP1,
AP_CHECKS_ALL AC1
WHERE AIP1.CHECK_ID = AC1.CHECK_ID
AND AC.ORG_ID = AC1.ORG_ID
AND ((AC.VENDOR_ID = AC1.VENDOR_ID
AND AC.VENDOR_SITE_ID = AC1.VENDOR_SITE_ID)
OR AC.PAYMENT_DOCUMENT_ID =AC1.PAYMENT_DOCUMENT_ID)
AND AC.CHECK_NUMBER = AC1.CHECK_NUMBER )
select check_id, check_number from ap_checks_all where check_id
not in
(select check_id from ap_invoice_payments_all)
-----------------------------------------------------------------------------
select aa.check_id, aa.check_number, aa.BANK_ACCOUNT_NAME, aa.AMOUNT, aa.CLEARED_DATE, aa.CHECK_DATE, aa.CREATED_BY from ap_checks_all aa where check_id
not in
(select check_id from ap_invoice_payments_all)
----------------------------------------------------------------------------
SELECT AC.CHECK_ID,
AC.CHECK_NUMBER,
AC.AMOUNT
FROM AP_CHECKS_ALL AC,
AP_PAYMENT_HISTORY_ALL APH
WHERE AC.PAYMENT_ID IS NULL
AND AC.STATUS_LOOKUP_CODE NOT IN ('OVERFLOW','SET UP','SPOILED')
AND AC.CHECK_ID=APH.CHECK_ID
AND NVL(APH.HISTORICAL_FLAG,'N') <> 'Y'
--AND APH.POSTED_FLAG <>'Y'
AND NOT EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP
WHERE AIP.CHECK_ID = AC.CHECK_ID)
AND EXISTS (SELECT 1
FROM AP_INVOICE_PAYMENTS_ALL AIP1,
AP_CHECKS_ALL AC1
WHERE AIP1.CHECK_ID = AC1.CHECK_ID
AND AC.ORG_ID = AC1.ORG_ID
AND ((AC.VENDOR_ID = AC1.VENDOR_ID
AND AC.VENDOR_SITE_ID = AC1.VENDOR_SITE_ID)
OR AC.PAYMENT_DOCUMENT_ID =AC1.PAYMENT_DOCUMENT_ID)
AND AC.CHECK_NUMBER = AC1.CHECK_NUMBER )
Wednesday 17 February 2016
Excel Report Completed with Warning with below Error
http://aporaclepayables.blogspot.com/2016/02/error-payables-version-12.html
Error
Error
+---------------------------------------------------------------------------+
Payables: Version : 12.2
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
APGSTDTL: GST Detail Report
+---------------------------------------------------------------------------+
Current system time is 17-FEB-2016 13:30:50
+---------------------------------------------------------------------------+
+-----------------------------
| Starting concurrent program execution...
+-----------------------------
Arguments
------------
P_DATE1='2015/01/01 00:00:00'
P_DATE2='2016/02/17 00:00:00'
P_ORG_ID='82'
------------
Forcing NLS_NUMERIC_CHARACTERS to: '.,' for XDO processing
APPLLCSP Environment Variable set to :
Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8
'.,'
Enter Password:
REP-0004: Warning: Unable to open user preference file.
Report Builder: Release 10.1.2.3.0 - Production on Wed Feb 17 13:30:52 2016
Copyright (c) 1982, 2005, Oracle. All rights reserved.
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
End of log messages from FND_FILE
+---------------------------------------------------------------------------+
+---------------------------------------------------------------------------+
Executing request completion options...
Output file size:
887739
+--------- 1) POST-PROCESSING ---------+
Beginning post-processing of request 1502577 on node TEMPTEST at 17-FEB-2016 13:31:15.
-- Publishing output
Post-processing of request 1502577 failed at 17-FEB-2016 13:31:15 with the error message:
One or more post-processing actions failed. Consult the OPP service log for details.
CONC-POST-PROCESSING RESULTS
-- PUBLISH:
oracle.apps.fnd.cp.opp.PostProcessorException: oracle.apps.fnd.cp.opp.PostProcessorException: oracle.apps.xdo.XDOException: apps/test/tmp/xdo1U4VhAgf2j021716_1331157785.fo (No such file or directory)
+---------------------------------------+
Finished executing request completion options.
+---------------------------------------------------------------------------+
Concurrent request completed
Current system time is 17-FEB-2016 13:31:15
+---------------------------------------------------------------------------+
Solution
Set the Temporary Directory in XML Publisher Administration
In my case: /apps/test/tmp
Tuesday 9 February 2016
Bank Setup
http://aporaclepayables.blogspot.com/2016/02/bank-setup.html
Please Download the file from Below URL
https://drive.google.com/open?id=0B30-kT1pIOm_S0hrVnlDNkVCNFk
Payment Uncleared is on “No Accounting Needed”
http://aporaclepayables.blogspot.com/2016/02/payment-uncleared-is-on-no-accounting.html
Please review the below Document from URL
https://drive.google.com/open?id=0B30-kT1pIOm_Z0ppTnVFZmRFSmM
Please review the below Document from URL
https://drive.google.com/open?id=0B30-kT1pIOm_Z0ppTnVFZmRFSmM
How to Open DFF on Supplier Site incl Personalization on DFF
http://aporaclepayables.blogspot.com/2016/02/how-to-open-dff-on-supplier-site.html
Read only for Approval Segment at Site Level
Global Data Elements|Bank Name|Bank Branch|Bank A/C Number|Sort Code|Approved($RO$)
All Access at Responsibility Level
Global Data Elements|Bank Name|Bank Branch|Bank A/C Number|Sort Code|Approved
Read only for Approval Segment at Site Level
Global Data Elements|Bank Name|Bank Branch|Bank A/C Number|Sort Code|Approved($RO$)
All Access at Responsibility Level
Global Data Elements|Bank Name|Bank Branch|Bank A/C Number|Sort Code|Approved
Monday 8 February 2016
How to give Supplier Inquiry Access to User
http://aporaclepayables.blogspot.com/2016/02/how-to-give-supplier-inquiry-access-to.html
Prompt Submneu Function Description
Supplier Inquiry PN_SUPPLIERS_RO_SUBMENU PN View Suppliers Suppliers Inquiry
Prompt Submneu Function Description
Supplier Inquiry PN_SUPPLIERS_RO_SUBMENU PN View Suppliers Suppliers Inquiry
Friday 5 February 2016
EVENT_STATUS_CODE and PROCESS_STATUS_CODE in XLA_EVENTS
http://aporaclepayables.blogspot.com/2016/02/eventstatuscode-and-processstatuscode.html
|
EVENT_STATUS_CODE
Event type code |
Meaning
|
|
I
|
Incomplete
|
|
N
|
No action
|
|
P
|
Processed
|
|
U
|
Unprocessed
|
|
PROCESS_STATUS_CODE
Processing status code |
Meaning
|
|
D
|
Draft
|
|
E
|
Error
|
|
I
|
Incomplete
|
|
P
|
Processed
|
|
R
|
Related event in error
|
|
U
|
Unprocessed
|
Draft : Draft will create journal entries,
which are not final, which means they are not ready to be transferred to GL.
You can create
accounting on this transaction again and again, which will delete the old
journal entries and create new ones. You can’t transfer these journal entries
to GL.
xla_events.process_status_code
= D
xla_events.event_status_code = U
xla_ae_headers.accounting_entry_status_code = D
xla_events.event_status_code = U
xla_ae_headers.accounting_entry_status_code = D
Final : Final will create journal entries,
which can be transferred to GL. Once it is finally accounted you can’t run
create accounting on the particular transaction (specifically on that event).
Run Transfer Journal
Entries to GL program
xla_events.process_status_code
= P
xla_events.event_status_code = P
xla_ae_headers.accounting_entry_status_code = F
xla_events.event_status_code = P
xla_ae_headers.accounting_entry_status_code = F
Final Post: Final Post will create journal entries in
final mode, transfer them to GL and post them.
xla_ae_headers.accounting_entry_status_code
= F
xla_ae_headers.transfer_status_code = Y
xla_events.process_status_code = P
xla_events.event_status_code = P
xla_ae_headers.transfer_status_code = Y
xla_events.process_status_code = P
xla_events.event_status_code = P
Tuesday 2 February 2016
XLA_EVENTS Query
http://aporaclepayables.blogspot.com/2016/02/xlaevents-query.html
XLA_EVENTS_PAYMENTS
------------------
select distinct xe.*
from ap_invoice_payments_all aip,
xla_events xe,
xla.xla_transaction_entities xte
where xte.application_id = 200
and xte.application_id = xe.application_id
and aip.invoice_id = '73936'
and xte.entity_code = 'AP_PAYMENTS'
and xte.source_id_int_1 = aip.check_id
and xte.entity_id = xe.entity_id
XLA_EVENTS_INVOICE
------------------
select distinct xe.*
from ap_invoices_all ai, xla_events xe, xla.xla_transaction_entities xte
where xte.application_id = 200
and xte.application_id = xe.application_id
and ai.invoice_id = '73936'
and xte.entity_code = 'AP_INVOICES'
and xte.source_id_int_1 = ai.invoice_id
and xte.entity_id = xe.entity_id
XLA_EVENTS_PAYMENTS
------------------
select distinct xe.*
from ap_invoice_payments_all aip,
xla_events xe,
xla.xla_transaction_entities xte
where xte.application_id = 200
and xte.application_id = xe.application_id
and aip.invoice_id = '73936'
and xte.entity_code = 'AP_PAYMENTS'
and xte.source_id_int_1 = aip.check_id
and xte.entity_id = xe.entity_id
XLA_EVENTS_INVOICE
------------------
select distinct xe.*
from ap_invoices_all ai, xla_events xe, xla.xla_transaction_entities xte
where xte.application_id = 200
and xte.application_id = xe.application_id
and ai.invoice_id = '73936'
and xte.entity_code = 'AP_INVOICES'
and xte.source_id_int_1 = ai.invoice_id
and xte.entity_id = xe.entity_id
Subscribe to:
Posts (Atom)