Thursday, March 20, 2014

Using R12 MOAC in RDF reports


We can use standard value sets and MOAC tables (synonyms) to show correct data.

Value sets given  -

1) Reporting Level FND_MO_REPORTING_LEVEL

Values will be -
1000 Ledger
2000 Legal Entity
3000 Operating Unit

2) Reporting Context FND_MO_REPORTING_ENTITY
Values will come based on above value set

See some standard reports how they have used these value sets.
Ex - AR Reconciliation Report

How to do?

Create lexical parameter - P_MOAC

srw.user_exit('FND SRWINIT');

/* Multi Org Access Control*/
fnd_mo_reporting_api.initialize(:p_reporting_level,:p_reporting_entity_id, 'AUTO');
:P_MOAC := fnd_mo_reporting_api.get_predicate('acr', NULL,:P_REPORTING_ENTITY_ID );

'acr' -- Alias name of your main table where we have to add where condition.
Ex - acr.org_id = 710

Use lexi parameter in Query - &P_MOAC

Wednesday, March 19, 2014

AP Invoice Validation Status

Link- 

http://appselangovan.blogspot.com/2013/12/ap-invoice-validation-status.html

AP Invoice Validation Status

(See Metalink doc ID 301806.1)
There is no column in the AP_INVOICES_ALL table that stores the validation status. Invoice distributions are validated individually and the status is stored at the invoice distribution level. This status is stored in AP_INVOICE_DISTRIBUTIONS_ALL.MATCH_STATUS_FLAG.
Valid values for the column are:

A – Validated (it used to be called Approved)
N or null – Never validated
T – Tested but not validated


The invoice header form derives the invoice validation status based on the following:
‘Validated’
- If all of the invoice distributions have a MATCH_STATUS_FLAG = ‘A’
‘Never Validated’
- If all of the invoice distributions have a MATCH_STATUS_FLAG = null or ‘N’
‘Needs Revalidation’
- If there are any rows in AP_HOLDS that do not have a release code.
- If any of the invoice distributions have a MATCH_STATUS_FLAG = ‘T’.
- If the invoice distributions have MATCH_STATUS_FLAG values = ‘N’, null and ‘A’ (mixed).

  Query:
========

select distinct match_status_flag from ap_invoice_distributions_all

We can use below function which is being used in AP_INVOICES_V

ap_invoices_pkg.get_approval_status( ail.invoice_id,ail.invoice_amount, ail.payment_status_flag,ail.invoice_type_lookup_code)
Values will be 
-- APPROVED - Validated
-- NEEDS REAPPROVAL
-- NEVER APPROVED
-- CANCELLED
Few other useful functions in API
AP_INVOICES_PKG.GET_POSTING_STATUS
AP_INVOICES_PKG.GET_AMOUNT_WITHHELD

Tuesday, March 18, 2014

AP Payments EFT file - eText RTF file


Good links on eText based RTF for EFT payments.



Previewing and testing eText templates

" 
Just a quick post today.

I've had a few emails asking how we test eText templates.


Rather than using the Word Plug in to preview the result, you test eText templates using the 'Template Viewer' included with the BIP desktop toolkit.


From the Windows Start menu, click on : All Programs, Oracle BI Publisher Desktop, Template Viewer:

Once the Template Viewer is open:
- select your working directory i.e. the folder containing your eText template and preview XML data
- change the output format to eText : 

and then click on the button 'Start Processing' to view the generated text file with Unix / Linux line endings:
"

Check some standard etext type RTF files for sample templates.





Report builder hiding in Task bar


https://community.oracle.com/message/932489#932489

Hello,
Can you check if your problem is not the one described here below :

PROBLEM DESCRIPTION
-------------------
When starting Reports Builder or Forms Builder on Windows, the icon appears
in the taskbar but the Forms or Reports Window is not visible.
If you right click on the icon in the taskbar and choose Maximize, the 
window appears.
As soon as you click on the Restore window button, the window is not 
visible on the screen anymore. 

SOLUTION
--------
Modify the file CAUPREFS.ORA or CAGPREFS.ORA and change the line 
containing window position information:

For reports:

Reports.root_x = 0
Reports.root_y = 0

for Forms

Forms.root_x = 0
Forms.root_y = 0

EXPLANATION
-----------
Sometimes, the values stored in this file are erroneous (too big). In this
case the window position is "out of the screen" and it is not visible.

Regards