Create AR Invoice and accounting flow


Create a AR transaction of invoice class

Fill transaction source, transaction type, transaction date, GL date, currency in the header section of transaction

Select Ship-To, Bill-To customer details. This will auto-populate customer account number, site address information from customer master

Once Bill-To customer is selected, it will auto-fill with Sold-to Customer and paying customer.

Select payment instrument to be recorded for this transaction

Payment term is defaulted based on transaction type or customer profile classes. due-date is automatically determined

Navigate to invoice lines tab to quickly fill following,

a. choose product item you are going to bill for customer. UOM and description is populated automatically based on item you choose from list of values
b. enter quantities and unit selling price
c. Line amount is auto calculated based on quantity and unit selling price
d. save the transaction and complete

Once you complete the transaction, system will not allow to edit AR invoice.

Invoice balance due is displayed on top-right corner of invoice window sub-classified with line, freight, and tax balances

Invoice number and document number is auto-generated if doc. sequence is configured automatic in transaction sources

In more tab region, you can enter special instructions or comments related to invoice. Track customer purchase order, revision number and date if any

Accounting class, GL account, Distribution percent and amount can be viewed through Distributions

Tools -> Create Accounting

Create accounting for the document: 0000

a. Create Draft accounting
b. Create Final accounting
c. Create final accounting post to GL

Receivables account - DR
Revenue account - CR

View sub ledger journal entries for each accounts

Sub-Ledger Journal entry page will display following details,
a. balance type - ACTUAL
b. gl date
c. journal entry status - FINAL
d. ledger
e. journal category - Sales Invoices
f. journal entry type - standard
g. completion date
i. Description - Transaction class || transaction type || transaction number || document sequence category || invoice document number





Comments

Post a Comment

Popular posts from this blog

How to use lexical parameters in Data template (XML document) R12

Lexical parameters can be added in data definition using &variable name This is flexible variable string where you can execute runtime conditions based on user-inputs Example 1. Append &gc_journal_filter at the end of sql statement 2. Define beforereport function in package signature FUNCTION beforereport RETURN BOOLEAN; 3. Define all the report parameters as a package variable in package signature including lexical parameters 4. Implement beforereport function by building your runtime conditions to be added to SQL statements  FUNCTION beforereport RETURN BOOLEAN IS  BEGIN          IF p_journal_source IS NULL THEN       gc_journal_filter := ' AND jh.je_source IN (''AutoCopy'',''Manual'')';     END IF;          IF p_journal_category IS NULL THEN       gc_journal_filter := 'AND jh.je_category IN (''Other'') ';     END IF;    RETURN TRUE;  END;
Read more

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR
Read more

Sub Inventory Transfer API.

Image
Sub Inventory transfer is used to move materials from one sub-inventory to another within same organization. This is especially used to 1. Adjust on-hand quantities between sub-inventories 2. Transfer to another sub-inventories for specific business need like additional sales 3. Damages/expiry products can be moved to non-asset sub-inventories to discard it from inventory valuation report and so on., Key elements 1. From sub inventory 2. To sub inventory 3. Organization 4. Inventory item 5. Transact quantity 6. Transact unit of measure 7. Transaction type 8. Transaction action 9. Transact Reference 10. Transact date 11. Lot Number Open Interfaces mtl_transactions_interface - is used to populate sub inventory transfer details mtl_transaction_lots_interface - is used to populate lot details for particular sub inventory transfer Base Tables mtl_material_transactions - is used to get all type of material transactions like sub-inventory transfer, inter-org tra
Read more