Wednesday 27 February 2019

Cash Management SQL

Cash Management SQLs:

CE_BANK_ACCOUNTS
CE_BANK_BRANCHES_V
CE_STATEMENT_HEADERS
CE_STATEMENT_LINES
CE_STML_BALANCES
========================

Buliding SQL for Cash Management Report

Bank statements sent are uploaded to ce_statement_headers

1.  ce_statement_headers
-> ce_statement_headers.bank_account_id     = ce_bank_accounts.bank_account_id

2. ce_bank_accounts
-> joins with account_owner_org_id:
[CE_BANK_ACCOUNTS || XLE_ENTITY_PROFILES ->ACCOUNT_OWNER_ORG_ID]

3. XLE_ENTITY_PROFILES  ->
-> XLE_ENTITY_PROFILES.legal_entity_id = CE_BANK_ACCOUNTS.ACCOUNT_OWNER_ORG_ID

4. SELECT CSH.*
   FROM
   CE_STATEMENT_HEADERS CSH,
   CE_BANK_ACCOUNTS CBA,
   XLE_ENTITY_PROFILES XEP
   WHERE CSH.BANK_ACCOUNT_ID = CBA.BANK_ACCOUNT_ID
     AND XEP.LEGAL_ENTITY_ID = CBA.ACCOUNT_OWNER_ORG_ID 


5. CE_LOOKUPS

6. CE_STML_BALANCES

This Table contains statement open booked and close booked balances based on bank_account_id and balance date.
    BANK_ACCOUNT_ID
    STATEMENT_HEADER_ID
    BALANCE_CODE
    BALANCE_AMOUNT
    BALANCE_DATE

===================================
7. How to get Bank Balance using GL

1. CE_STATEMENT_HEADERS -> Get Bank Account ID
2. CE_BANK_ACCOUNTS -> GET ASSET_CODE_COMBINTAION_ID
3. GL_BALANCES -> CODE_COMBINATION_ID
4. BASED ON PERIOD -> GET BALANCES
sum(glb.begin_balance_dr - glb.begin_balance_cr),0) OPENGLBAL

====================================

8. How to get Open and Close Balance for a Statement
1. CE_STATEMENT_HEADERS -> GET STATEMENT_HEADER_ID
2. CE_STML_BALANCES

===================================
9. Mapping of Transactions from Cash Management to AP/AR

Lets Say we have a record in 

1. query CE_STATEMENT_HEADERS -> 

2. query CE_STATEMENT_LINES -> get recon_history_id
3. query CE_RECON_HISTORY_ITEMS -> provide recon_history_id, and get source id -> sourec_id = check_id (ap), and sourec_id = cash_receipt_id (AR)

How To Link AR Receipt With Bank Statement


SELECT CASH_RECEIPT_ID
FROM FUSION.AR_CASH_RECEIPTS_ALL
WHERE RECEIPT_NUMBER = '&RECEIPT_NUMBER'
AND RECON_FLAG = Y;
SELECT RECON_HISTORY_ID
FROM FUSION.CE_RECON_HISTORY_ITEMS
WHERE RECON_SOURCE = 'AR'
AND SOURCE_ID = '&CASH_RECEIPT_ID';
SELECT STATEMENT_HEADER_ID
FROM FUSION.CE_STATEMENT_LINES
WHERE RECON_HISTORY_ID = '&RECON_HISTORY_ID';
SELECT STATEMENT_NUMBER
FROM FUSION.CE_STATEMENT_HEADERS
WHERE STATEMENT_HEADER_ID = '&STATEMENT_HEADER_ID'; 


Mapping of Transactions from Cash Management to AP/AR

Lets Say we have a record in 

1. query CE_STATEMENT_HEADERS -> 
2. query CE_STATEMENT_LINES -> get recon_history_id
3. query CE_RECON_HISTORY_ITEMS -> provide recon_history_id, and get source id -> sourec_id = check_id (ap), and sourec_id = cash_receipt_id (AR)

Tuesday 26 February 2019

How to Avoid extra carriage returns in BIP Output

Sometime, we see extra carriage returns in report output that we dont know from where it comes. There are two ways to suppress it.

1. using if:@inlines

2. Do not give any space before and after the tag or tag code, if there is a space after code/tag, it will generate a carriage return in output.

Wednesday 20 February 2019

How to Pass Muliple Values in Parameter and parse data in rtf

Sample XML:

<?xml version = '1.0' encoding = 'utf-8'?>
<DATA_DS>
<P_AIW>[1000,5000,9000,12000]</P_AIW>
<getAmt>
<return><amount>1000</amount>
<amountAr> آلف   درهم إماراتى</amountAr>
</return>
<return><amount>5000</amount>
<amountAr>خمسة الآف   درهم إماراتى</amountAr>
</return>
<return><amount>9000</amount>
<amountAr>تسعة الآف   درهم إماراتى</amountAr>
</return>
<return><amount>12000</amount>
<amountAr>إثناعشر آلف   درهم إماراتى</amountAr>
</return>
</getAmt>
<DATA_DS>
<G_PAYMENT_VOUCHER>
<ORG_ID>3000</ORG_ID><INVOICE_NUM>Invoice #1</INVOICE_NUM><PAYMENT_CURRENCY_CODE>AED</PAYMENT_CURRENCY_CODE><INVOICE_AMOUNT>1000</INVOICE_AMOUNT>
</G_PAYMENT_VOUCHER>
<G_PAYMENT_VOUCHER>
<ORG_ID>3000</ORG_ID><INVOICE_NUM>Invoice #2</INVOICE_NUM><PAYMENT_CURRENCY_CODE>AED</PAYMENT_CURRENCY_CODE><INVOICE_AMOUNT>5000</INVOICE_AMOUNT>
<G_PAYMENT_VOUCHER>
<G_PAYMENT_VOUCHER>
<ORG_ID>3000</ORG_ID><INVOICE_NUM>Invoice #3</INVOICE_NUM><PAYMENT_CURRENCY_CODE>AED</PAYMENT_CURRENCY_CODE><INVOICE_AMOUNT>9000</INVOICE_AMOUNT>
</G_PAYMENT_VOUCHER>
<G_PAYMENT_VOUCHER>
<ORG_ID>3000</ORG_ID><INVOICE_NUM>Invoice #4</INVOICE_NUM><PAYMENT_CURRENCY_CODE>AED</PAYMENT_CURRENCY_CODE><INVOICE_AMOUNT>12000</INVOICE_AMOUNT>
</G_PAYMENT_VOUCHER>
</DATA_DS>
</DATA_DS>


RTF template


<?xdoxslt:set_variable($_XDOCTX, ‘inv_amt2’, 0)?>

BU_NAME
INVOICE_NUM
Arabic
INVOICE_AMOUNT
F1 ORG_ID
<?xdoxslt:set_variable($_XDOCTX, 'inv_amt2', INVOICE_AMOUNT)?>
INVOICE_NUM
F <?if@inlines:number(amount)=xdoxslt:get_variable($_XDOCTX,‘inv_amt’)?><?amountAr?><?end if?> E  
INVOICE_AMOUNT  E1



F1 <?for-each:G_PAYMENT_VOUCHER?>
F2 <?for-each://getAmt/return?>
E1 <?end for-each?>
E2 <?end for-each?>

if@inlines is used to suppress spaces or line breaks created by for-each loop

Monday 18 February 2019

Tax Registration Number

-- Getting from Party Site

    (
        SELECT
            zr.registration_number trn_customer_site
        FROM
            zx_party_tax_profile zptf,
            zx_registrations zr
        WHERE
            zptf.party_id = hps.party_site_id
            AND zptf.party_tax_profile_id = zr.party_tax_profile_id
            AND zptf.party_type_code = 'THIRD_PARTY_SITE'
    ) trn_customer_site,

BI Publisher issue of Page Start Content starting with little space from page-2

BI Publisher issue of Page Start Content starting with little space from page-2.


Page 1 start at correct margin, but page-2 start at little more margin than page-1

Issue# It is because of <no spacing not selected on page break end tags>

for-each

----




----

page break end




Fix: in rtf > Home > Styles > No Spacing on  page break end tags

Wednesday 13 February 2019

How to Apply Custom Water Mark Text Based in RTF

Create a form field: and add below code into it.

You xml should have a element which value can be compared in ifelse

<xsl:variable name="wMark" select="xdoxslt:ifelse(//G_REP/D_TYPE='DUPLICATE','DUPLICATE','ORIGINAL')"/>


Place below text inside the watermark> Text Water Mark > Text

<?$wMark?>





How to create dependent LOV for ESS Job based on a table in Fusion

As per support note:

How to Use Table Value Set in ESS Parameter's LOV?
Can oracle.apps.fnd.applcore.flex.vst.model.publicView.ValueSetValuePVO be used for table value set?

Solution

If using the oracle.apps.fnd.applcore.flex.vst.model.publicView.ValueSetValuePVO for table value sets , there will not be any return value.

To create an ESS parameter LOV for a table validated value set the table VO must be used directly.

Ex.

Now Lets create an LOV for Check Number

1. Search for this document on google

Rel13_18B_Financials_OTBI_Database_Mapping_with_ViewObjects
( just remove protection from the excel file)

https://cloudcustomerconnect.oracle.com/posts/f53e634ec2

2. This will list VO -> Table -> Column Mapping

3. List down mappings, I found below mappings

This excel contains (VO NAME-> TABLE_NAME -> COLUMN NAME)
VO Definition Database Table Database Column
oracle.apps.financials.payables.invoices.transactions.publicView.analytics.InvoiceDistributionPVO AP_CHECKS_ALL CHECK_NUMBER
oracle.apps.financials.payables.payments.singlePayments.publicView.analytics.PaidDisbursementSchedulePVO AP_CHECKS_ALL CHECK_NUMBER
oracle.apps.financials.payables.payments.singlePayments.publicView.analytics.PaymentHistoryDistributionPVO AP_CHECKS_ALL CHECK_NUMBER
oracle.apps.financials.payables.payments.singlePayments.publicView.analytics.DisbursementHeaderPVO AP_CHECKS_ALL CHECK_NUMBER
oracle.apps.financials.payables.payments.singlePayments.publicView.analytics.PaidDisbursementSchedulePVO AP_CHECKS_ALL CHECK_VOUCHER_NUM
oracle.apps.financials.payables.payments.singlePayments.publicView.analytics.DisbursementHeaderPVO AP_CHECKS_ALL CHECK_VOUCHER_NUM
oracle.apps.financials.payables.payments.singlePayments.publicView.analytics.PaymentHistoryDistributionPVO AP_CHECKS_ALL CHECK_VOUCHER_NUM


4. Create Table based LOV in Manage List of Value Sources:

Find by class path:

List of Values Source Definition Name Start with FscmTopModelAM.FinApPmtSinglePaymentsAM.DisbursementHeaderPVO




Define ESS Program




Logout and login, this will create dependent LOV .




Tuesday 12 February 2019

How to Link two data sets without using any Join [group link or group filter]

Example

Data Set 1:

select cash_receipt_id, created_by from ar_cash_receipts_all

Create a group: G_RECEIPT

Edit created by property against the property icon:

Column Name
*AliasP_CREATED_BY
Display NameP_CREATED_BY
Data Type
Sort Order
Value If Null

Now create another dataset and use it as bind variable [:P_CREATED_BY]

Data Set 2:

SELECT 
CASE 
WHEN (SELECT COUNT(*) FROM PER_USERS WHERE USERNAME = :P_CREATED_BY AND PERSON_ID IS NOT NULL) > 0 THEN 
(SELECT distinct 
ppn.full_name||' ('||papf.person_number||')'
FROM
    per_users u,
    per_all_people_f papf,
    per_person_names_f ppn
WHERE
    papf.person_id = nvl(u.person_id,-1)
    AND ppn.person_id = papf.person_id
    AND trunc(SYSDATE) BETWEEN nvl(papf.effective_start_date,trunc(SYSDATE) ) AND nvl(papf.effective_end_date,'4712-12-31')
    AND trunc(SYSDATE) BETWEEN nvl(ppn.effective_start_date,trunc(SYSDATE) ) AND nvl(ppn.effective_end_date,trunc(SYSDATE) )
    AND ppn.name_type = 'GLOBAL'
AND U.USERNAME = :P_CREATED_BY
AND ROWNUM =1)
ELSE 
(SELECT USERNAME FROM PER_USERS WHERE USERNAME = :P_CREATED_BY)
END FULL_NAME

FROM DUAL


You will get a prompt to create this variable as parameter, just ignore same. 

[This way both dataset will be linked without actually creating a group link or group filter]

Receivables Tables: Points to Consider


Receivables Tables: Points to Consider

Help topic
|11/17/2018|Generic
Receivables uses the following tables to store all accounts receivable transaction, receipt, and adjustment activity:
  • RA_CUSTOMER_TRX
  • RA_CUSTOMER_TRX_LINES
  • RA_CUST_TRX_LINE_SALESREPS
  • RA_CUST_TRX_LINE_GL_DIST
  • AR_PAYMENT_SCHEDULES
  • AR_ADJUSTMENTS
  • AR_RECEIVABLE_APPLICATIONS
  • AR_CREDIT_MEMO_AMOUNTS
  • AR_CASH_RECEIPTS
  • AR_CASH_RECEIPT_HISTORY
  • AR_MISC_CASH_DISTRIBUTIONS
Each table stores information needed for one or more types of transactions, receipts, or adjustments. Each data element is stored as a unique record, based on the primary key of the table.

RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES tables

Important columns in the RA_CUSTOMER_TRX table include:
  • CUSTOMER_TRX_ID column
  • TRX_NUMBER column
  • BILL_TO_CUSTOMER_ID column
  • TRX_DATE column
The RA_CUSTOMER_TRX table stores invoice, debit memo, and credit memo header information. Each of these transactions is stored as a unique record, based on the primary key customer_trx_id. The transaction number, transaction date, and billing customer are stored in the trx_number, trx_date, and bill_to_customer_id columns respectively.
Additional information stored in this table includes ship-to customer, document sequence number, currency, and a transaction complete setting. The transaction type for the invoice is stored in the RA_CUST_TRX_TYPES table, but can be referenced using the foreign key cust_trx_type_id.
Important columns in the RA_CUSTOMER_TRX_LINES table include:
  • CUSTOMER_TRX_LINE_ID column
  • CUSTOMER_TRX_ID column
  • LINK_TO_CUST_TRX_LINE_ID column
  • LINE_TYPE column
  • EXTENDED_AMOUNT column
The RA_CUSTOMER_TRX_LINES table stores invoice, debit memo, and credit memo line level information. Each transaction line is stored as a unique record, based on the primary key customer_trx_line_id column. The customer_trx_id column is a foreign key to the RA_CUSTOMER_TRX table.
The line_type column identifies the type of data contained in the record. Valid line types are CHARGES, FREIGHT, LINE, and TAX. Any record with a line type of TAX or FREIGHT refers to the original invoice line from the link_to_cust_trx_line_id column, except for header freight transactions. The total amount for each transaction line is stored in the EXTENDED_AMOUNT column.

RA_CUST_TRX_LINE_SALESREPS and RA_CUST_TRX_LINE_GL_DIST tables

Important columns in the RA_CUST_TRX_LINE_SALESREPS table include:
  • CUST_TRX_LINE_SALESREP_ID column
  • SALES_REP_ID column
  • CUSTOMER_TRX_LINE_ID column
  • REVENUE_AMOUNT_SPLIT column
  • NON_REVENUE_AMOUNT_SPLIT column
  • PREV_CUST_TRX_LINE_SALESREP_ID column
The RA_CUST_TRX_LINE_SALESREPS table stores sales credit assignments for invoice lines. Each assignment is stored as a unique record, based on the primary key cust_trx_line_salesrep_id. If you base your accounting distributions on sales credits, the sales credit assignments in this table map to the RA_CUST_TRX_LINE_GL_DIST table. The sales_rep_id column identifies the salesperson receiving the credit for this transaction. The customer_trx_line_id column is a foreign key to the RA_CUSTOMER_TRX_LINES table.
The revenue_amount_split column stores the amount of the invoice line assigned to this salesperson. The non_revenue_amount_split column stores the amount of the non-header freight and tax lines assigned to this salesperson. If the sales credits are derived based on a percentage of the transaction line rather than a specific amount, the revenue_percent_split and non_revenue_percent_split columns store the percentages of the transaction lines assigned to this salesperson. The prev_cust_trx_line_salesrep_id column references another sales credit assignment to which the current record is being applied.
Important columns in the RA_CUST_TRX_LINE_GL_DIST table include:
  • CUST_TRX_LINE_GL_DIST_ID column
  • CODE_COMBINATION_ID column
  • CUSTOMER_TRX_LINE_ID column
  • ACCOUNT_CLASS column
  • AMOUNT column
The RA_CUST_TRX_LINE_GL_DIST table stores the accounting distribution for invoice, debit memo, and credit memo transactions. Each distribution is stored as a unique record, based on the primary key cust_trx_line_gl_dist_id. The customer_trx_line_id column is a foreign key to the RA_CUSTOMER_TRX_LINES table.
The account_class column describes the account type, while the code_combination_id column identifies the general ledger account. Valid account classes are CHARGES, FREIGHT, REC, REV, SUSPENSE, TAX, UNBILL, and UNEARN. The account_class REC represents the receivable account distribution. The amount column for REC records is equal to the sum of all invoice lines. Therefore, there is no link to the RA_CUSTOMER_TRX_LINES table and the column customer_trx_line_id is null for these records. The REC record is linked to the RA_CUSTOMER_TRX table from the customer_trx_id column. For all other account classes, credits are represented by positive numbers and debits are represented by negative numbers.

AR_PAYMENT_SCHEDULES table

Important columns in the AR_PAYMENT_SCHEDULES table include:
  • PAYMENT_SCHEDULE_ID column
  • AMOUNT_DUE_ORIGINAL column
  • AMOUNT_DUE_REMAINING column
  • CUSTOMER_TRX_ID column
  • CASH_RECEIPT_ID column
  • TRX_NUMBER column
  • STATUS column
  • AMOUNT_APPLIED column
  • CLASS column
The AR_PAYMENT_SCHEDULES table stores customer balance information at the transaction level. Each transaction balance is stored as a unique record, based on the primary key payment_schedule_id. The class column identifies the transaction type and determines which columns to update when a transaction is stored.
For billing transactions, the AR_PAYMENT_SCHEDULES table joins the RA_CUSTOMER_TRX table from the customer_trx_id column and stores NULL in the cash_receipt_id column. For payment transactions, the AR_PAYMENT_SCHEDULES table joins the AR_CASH_RECEIPTS table from the cash_receipt_id column and stores NULL in the customer_trx_id column.
This table illustrates the tables updated for billing and payment transactions:
TRANSACTION
CLASS
FOREIGN KEY
TABLE
Invoices
INV
customer_trx_id
RA_CUSTOMER_TRX
Debit Memos
DM
customer_trx_id
RA_CUSTOMER_TRX
Credit Memos
CM
customer_trx_id
RA_CUSTOMER_TRX
Chargebacks
CB
customer_trx_id
RA_CUSTOMER_TRX
Receipts
PMT
cash_receipts_id
AR_CASH_RECEIPTS
The status column identifies whether the transaction is open or closed, while the trx_number column stores the transaction number. The amount_applied column stores the sum of all transactions applied to the balance of the selected transaction. The amount_due_original column equals either the sum of the EXTENDED_AMOUNT column in the RA_CUSTOMER_TRX_LINES table for the given customer_trx_id or the sum of the amount column in the AR_CASH_RECEIPTS table for the given cash_receipts_id. The amount_due_remaining column represents the balance for the selected transaction.
For the amount_due_original and amount_due_remaining columns, debit items, such as invoices, are stored as positive numbers, and credit items, such as credit memos and payments, are stored as negative numbers. The current customer balance is reflected by the sum of the amount_due_remaining column for all confirmed payment schedules for a given customer.

AR_ADJUSTMENTS table

Important columns in the AR_ADJUSTMENTS table include:
  • ADJUSTMENT_ID column
  • AMOUNT column
  • CUSTOMER_TRX_ID column
  • TYPE column
  • PAYMENT_SCHEDULE_ID column
  • CODE_COMBINATION_ID column
The AR_ADJUSTMENTS table stores information about invoice adjustments. Each adjustment is stored as a unique record, based on the primary key adjustment_id. The amount column stores the amount of the adjustment. Receivables uses the customer_trx_id and payment_schedule_id to link the adjustment to the adjusted transaction and to update the amount_due_remaining and amount_adjusted columns of the adjusted transaction payment schedule in the AR_PAYMENT_SCHEDULES table.
The type column stores a description of the transaction to which the adjustment applies. Valid types include:
  • Charges Adjustments
  • Freight Adjustments
  • Invoice Adjustments
  • Line Adjustments
  • Tax Adjustments
The code_combination_id column stores the accounting distribution associated with the adjustment transaction.

Receivables Applications

The Receivables tables that manage data for receipt and credit memo applications are:
  • AR_RECEIVABLE_APPLICATIONS
  • AR_CREDIT_MEMO_AMOUNTS
  • AR_CASH_RECEIPTS
  • AR_CASH_RECEIPT_HISTORY
  • AR_MISC_CASH_DISTRIBUTIONS
Important columns in the AR_RECEIVABLE_APPLICATIONS table include:
  • RECEIVABLE_APPLICATION_ID column
  • AMOUNT_APPLIED column
  • STATUS column
  • PAYMENT_SCHEDULE_ID column
  • CODE_COMBINATION_ID column
  • CASH_RECEIPT_ID column
  • APPLIED_PAYMENT_SCHEDULE_ID column
  • APPLIED_CUSTOMER_TRX_ID column
The AR_RECEIVABLE_APPLICATIONS table stores account distributions for receipt and credit memo applications and maps the application transaction to the applied transaction. Each accounting distribution is stored as a unique record, based on the primary key receivable_application_id. The payment_schedule_id column links the receipt or credit memo to its payment schedule in the AR_PAYMENT_SCHEDULES table. The cash_receipt_id column stores the receipt ID of payment transactions, while the cust_trx_id column, which is not shown, stores the transaction ID for credit memo transactions. The applied_payment_schedule_id and applied_customer_trx_id columns reference the transaction to which this record applies.
The status column describes the state of the application transaction. For credit memos, the status is always APP to identify the credit memo as applied. For receipt transactions, valid status values are APP, UNAPP, UNID, REV, NSF, and STOP. The code_combination_id column stores the general ledger account for the application transaction, based on the status. The amount_applied column stores the amount of the receipt or credit memo as a positive value.
Important columns in the AR_CREDIT_MEMO_AMOUNTS table include:
  • CREDIT_MEMO_AMOUNT_ID column
  • CUSTOMER_TRX_LINE_ID column
  • GL_DATE column
  • AMOUNT column
The AR_CREDIT_MEMO_AMOUNTS table stores the accounting dates and amounts for credit memos to use when they are applied to invoices with rules. Each credit memo application date is stored as a unique record, based on the primary key credit_memo_amount_id. The customer_trx_line_id column references the transaction line to which a credit memo applies. The gl_date column stores the date the credit memo is applied to the invoice, and the amount column stores the amount to apply.
Important columns in the AR_CASH_RECEIPTS table include:
  • CASH_RECEIPT_ID column
  • AMOUNT column
  • STATUS column
  • RECEIPT_NUMBER column
  • TYPE column
The AR_CASH_RECEIPTS table stores a unique record for each receipt, based on the primary key cash_receipt_id. The status column describes the state of the receipt in relation to customer invoices and balances. Valid status values are:
  • UNID: The receipt customer is unidentified, and no customer balance was updated.
  • UNAPP: The receipt customer was identified, but the receipt has neither been fully applied to a specific invoice nor placed on account.
  • APP: The entire amount of the receipt was either placed on account or applied to specific customer invoices.
  • REV: The receipt was reversed.
  • NSF: The receipt was reversed due to insufficient funds.
  • STOP: The receipt was reversed by a stop payment.
The type column identifies the receipt as either CASH or MISC to indicate whether the receipt is a customer payment or a miscellaneous receipt (not related to a receivables activity). The amount column stores the net amount of the receipt, while the receipt_number column stores the receipt number.
Important columns in the AR_CASH_RECEIPT_HISTORY table include:
  • CASH_RECEIPT_HISTORY_ID column
  • AMOUNT column
  • STATUS column
The AR_CASH_RECEIPT_HISTORY table stores the current status and history of a receipt. Each status change is stored as a unique transaction, based on the primary key cash_receipt_history_id. The status column describes which step of the receipt life cycle the receipt has reached. Valid status values are:
  • APPROVED: This status is only valid for automatic receipts, and indicates that the receipt was approved for automatic creation. These record types are never postable.
  • CONFIRMED: This status is only valid for automatic receipts, and indicates that the receipt was confirmed by the customer.
  • REMITTED: This status is valid for both manual and automatic receipts, and indicates that the receipt was remitted.
  • CLEARED: This status is valid for both manual and automatic receipts, and indicates that the receipt was cleared.
  • REVERSED: This status is valid for both manual and automatic receipts, and indicates that the receipt was reversed.
As the receipt moves through its life cycle, Receivables inserts a new record into the AR_CASH_RECEIPTS_HISTORY table with the current_record_flag column set to Y. Receivables also updates the previous record related to this receipt, by setting the current_record_flag to NULL and by setting the reversal_gl_date. The amount column stores the amount of the receipt. The cash_receipts_id column links the AR_CASH_RECEIPTS_HISTORY table to the AR_CASH_RECEIPTS table.
Important columns in the AR_MISC_CASH_DISTRIBUTIONS table include:
  • MISC_CASH_DISTRIBUTION_ID column
  • CASH_RECEIPT_ID column
  • CODE_COMBINATION_ID column
The AR_MISC_CASH_DISTRIBUTIONS table stores the accounting distribution for miscellaneous cash receipts. Each distribution is stored as a unique record, based on the primary key misc_cash_distribution_id. The distributions are linked to the receipt by the cash_receipt_id column. The code_combination_id column stores the general ledger account assigned to this receipt.

Friday 8 February 2019

How to upload custom font in Fusion BIP


Uploading custom font:

Runtime Configuration, select Font Mappings.> Manage Custom Font > upload

just upload the fonts first so that its available for mapping

Creating a Font Mapping
From the Administration page, under Runtime Configuration, select Font Mappings.
To create a Font Mapping:
  1. Under RTF Templates or PDF Templates, select Add Font Mapping.
Enter the following on the Add Font Mapping page:
  1. Base Font — enter the font family to map to a new font. Example: Arial
  2. Select the Style: Normal or Italic (Not applicable to PDF Template font mappings)
  3. Select the Weight: Normal or Bold (Not applicable to PDF Template font mappings)
  4. Select the Target Font Type: Type 1 or TrueType
  5. Enter the Target Font
  6. If you selected TrueType, you can enter a specific numbered font in the collection. Enter the TrueType Collection (TTC) Number of the desired font.
  7. For a list of the predefined fonts see BI Publisher Predefined Fonts.



-> While assigning the font in rtf template same name should be given as in [Base Font — enter the font family to map to a new font. Example: Arial,  ]

Thursday 7 February 2019

AR Receipts Report

SELECT
 ACRA.RECEIPT_DATE
,ACRA.PAY_FROM_CUSTOMER
,ACRA.MISC_PAYMENT_SOURCE
,ACRA.TYPE
,ACRA.RECEIPT_NUMBER
,case when ACRA.TYPE != 'MISC' then (select hp.party_name from hz_parties hp, HZ_CUST_ACCOUNTS hca where hca.cust_account_id = ACRA.PAY_FROM_CUSTOMER and hca.party_id = hp.party_id)
 else ACRA.MISC_PAYMENT_SOURCE
 end CUSTOMER_NAME
,substr(arm.name,instr(ARM.name,'-')+1,length(arm.name)) receipt_method
,ACRA.AMOUNT
,(select IBY_AMOUNT_IN_WORDS.Get_Amount_In_Words(ACRA.AMOUNT,'AED',2) from dual) AMT_Words
,ACRA.COMMENTS Remark
,ARM.printed_name
,ACRA.created_by
,sysdate PRINTING_DATE
FROM
AR_RECEIPT_METHODS                 ARM
,AR_CASH_RECEIPTS_ALL               ACRA
WHERE 1=1
AND ARM.RECEIPT_METHOD_ID               =               ACRA.RECEIPT_METHOD_ID
and acra.org_id =:p_bu_id