Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Difference between ‘balance forward payment terms’ and other ‘payment terms’

Posted on January 16th, 2013 by Sanjit Anand ||Email This Post Email This Post

Balance forward billing payment terms pass the balance forward billing cycle to the Create Balance Forward Bill program . The billing cycle determines when customer balance forward bills are generated.

Because balance forward bills cannot be split across installments , all settings related to installments on balance forward billing payment terms are disabled.

You cannot change existing payment terms back and forth for use as both a non-balance forward billing and balance forward billing payment terms.

Posted in Oracle Receivable | No Comments »

Getting Started with DRM

Posted on January 13th, 2013 by Sanjit Anand ||Email This Post Email This Post

DRM is a master data management tool used to administer hierarchies, attributes, and metadata used by various types of applications.

The DRM tool can act as a centralized enterprise hierarchy management solution serving a wide range of downstream BI, EPM, ERP, operational, and other systems.

Common applications of the DRM tool include management of GL chart of accounts,customer and employee attributes, and product information .

Oracle Hyperion Data Relationship Management (DRM), Fusion Edition functions as a master data management solution where reporting structures are maintained, analyzed, and validated before moving throughout the enterprise. Data Relationship Management does the following:

  • Manages business entities, hierarchies, attributes, and mappings across multiple systems.
  • Validates data relationships and calculates attribute values using business rules.
  • Enforces referential integrity across all subscribing systems and hierarchies.
  • Enables you to create and manage alternate views.
  • Merges independent data sets from different sources and combines them into a master set.
  • Maintains historical versions for comparative reporting and analysis.
  • Tracks all hierarchy and attribute changes with a full-featured audit log.
  • Can serve as the main point-of-entry to update subscribing systems or be used subsequently for reconciliation and analysis.

You can use Data Relationship Management to manage charts of accounts segment values and hierarchies for Oracle General Ledger.

You can create new segment values, edit their properties, and maintain hierarchies using DRM. This information can be synchronized to one or more general ledger instances using a concurrent request program in the Oracle E-Business Suite.

DRM can integrate with other systems, Oracle or non-Oracle systems. The simplest way to let flow the data in between systems is by Import/Export.

Export can be done to a flat file or a database table where as import can be done via flat file. Additionally, customization can be done through API to perform the same.

DRM is also an Analytical Master Data Management tool. It allows creation of an enterprise view of analytical dimensions, reporting structures, performance measures and their related attributes.

DRM can also be considered a change management tool, as it is often used to facilitate the combination of disparate General Ledgers, product mappings, customer data sets, and other business information.

Mergers and acquisitions are frequently reliant on DRM to enable different systems to be able to communicate with each other.

DRM enables organizational consistency, managed change and becomes the foundation for any technology project

Posted in Hyperion, MDM, Oracle Receivable | No Comments »

General Ledger Transfer (ARGLTP) used in 11i is obsolete in Release 12.

Posted on January 12th, 2013 by Sanjit Anand ||Email This Post Email This Post

Prior to posting to the General Ledger, the Receipts Journal Report and Sales Journal display the transactions that would be posted to the General Ledger .

In Release 12 this program has been replaced by the following:

  • Create Accounting or Submit Accounting – This generate accounting entries in Sub-ledger Accounting (XLA). You can run this from any AR Manager responsblity , and can be done via Control > Request > Run (Create Accounting).
    • The Parameter Transfer to General Ledger denotes whether or not the records created by Create Accounting in the XLA tables will be posted to the the General Ledger Tables.
      • If YES – the process will automatically call Transfer Journal Entries to General Ledger for you and your records are transferred from XLA to GL and your entries are posted.
      • If NO – then you need to explicitly run program Transfer Journal Entries to General Ledger to pickup the final accounted transactions from the subledger (XLA Tables) and move them on to GL.
      • Take a note : If you have transactions with Accounting Rules, you need to run Revenue Recognition PRIOR to running Create Accounting otherwise the invoice will not be picked up for accounting, OR you can use Submit Accounting instead.
  • Submit Accounting – This process is an Oracle Receivables-specific counterpart of the create accounting process .
    • The Parameter Create Accounting determines whether you want to spawn the Create Accounting process as well – this is equivalent to running it standalone as in step 1 above
    • The Parameter Transfer to General Ledger denotes whether or not the records created by Create Accounting in the XLA tables will be posted to the the General Ledger Tables.
    • If you enter YES – the process will automatically call Transfer Journal Entries to General Ledger for you and your records are transferred from XLA to GL and your entries are posted.
    • If you enter NO – then you need to explicitly run program Transfer Journal Entries to General Ledger to pickup the final accounted transactions from the subledger (XLA Tables) and move them on to GL. See step 3 on how to do this.
  • Transfer Journal Entries to General Ledger : If in either of the previous steps: Create Accounting OR Submit Accounting, you entered NO for the parameter Transfer to General Ledger, then you need to run this step explicitly.

a Data Flow: When this Transfer done , these tables tables involved in the Transfer to GL and GL posting.

Subledger Tables

  • XLA_AE_HEADERS
  • XLA_AE_LINES
  • XLA_DISTRIBUTION_LINKS

Transfer Journal Entries to GL (XLAGLTRN) process takes the subledger journals and inserts records into the Interface Tables

Interface Tables

  • GL_INTERFACE / XLA_GLT_<groupid>
    • If you are using primary and secondary ledger , Two group IDs are created
    • One for the primary ledger and one for the secondary ledger.
    • Two journal import processes are spawned in this case, one for each group_id.

There is profile option “Disable Journal Import” (when set to Yes) prevents the GL Transfer from invoking the Journal Import.

The interface table used in this case is GL_INTERFACE. Setting this profile option is not recommended if you are using Oracle General Ledger.

Journal Import (GLLEZL) then reads from the interface table and creates records in the GL Tables

GL Tables

  • GL_JE_BATCHES
  • GL_JE_HEADERS
  • GL_JE_LINES
  • GL_IMPORT_REFERENCES

Hope this helps.

Posted in Oracle Receivable | No Comments »

Oracle R12 : Hierarchy Manager Limitations

Posted on January 11th, 2013 by Sanjit Anand ||Email This Post Email This Post

arrow-up-3 Account Hierarchy Manager in GL

Account Hierarchy Manager is fully integrated with Oracle General Ledger. With this you can create and manage values and hierarchies for your Accounting Flexfields using the Account Hierarchy Manager just as you can in General Ledger.

All changes made in Account Hierarchy Manager are reflected in GL upon saving and your entire chart of accounts is available in Account Hierarchy Manager.

Working with account structures and hierarchies in Account Hierarchy Manager is easy and intuitive because of the graphical interface. In addition, performing what-if manipulations for account structures is a simple process using the Account Hierarchy Manager.

You can:

  • Graphically create, maintain, and review account structure hierarchies.
  • Define new parent and child segment values, as well as change parent/child dependencies.
  • Create new rollup groups from the Account Hierarchy Manager and have your changes reflected automatically in both the Key Segment Values and Rollup Groups windows.

arrow-up-3 Oracle R12 – Hierarchy Manager Limitations

Oracle Release 12 in its standard form supports a repository for master data in the form of segment values.

Oracle Hierarchy Manager does not cater to maintenance of multiple forms of hierarchies within a CoA Segment

Integration with non-financial systems not possible and hence the flexibility to report on multiple business scenario’s for non financial \ MIS data not possible, therefore no flexibility to version hierarchies for ‘What-if’ analysis

arrow-up-3 Oracle DRM solution

Oracle DRM manages the core / alternate hierarchies and acts as source of hierarchies for downstream systems. Next post will be focus on Oracle DRM solution.

Posted in Hyperion, Oracle Receivable | No Comments »

What happens if I don’t enter an AutoInvoice grouping rule?

Posted on December 15th, 2012 by Sanjit Anand ||Email This Post Email This Post

Do you Know assigning the AutoInvoice grouping rule to Imported transaction sources that AutoInvoice uses to group imported transaction lines.

If you do not assign a grouping rule to an Imported transaction source, AutoInvoice uses the following hierarchy to determine which rule to use:

  • Grouping rule assigned to the transaction source of the transaction line.
  • Grouping rule assigned to the bill-to customer site profile of the transaction line.
  • Grouping rule assigned to the bill-to customer profile of the transaction line.
  • Grouping rule assigned to system options.

Therefore this is important to review the autoInvoice Grouping Rules set up .Define additional grouping rules or update the default grouping rule provided by Receivabless

Understanding AutoInvoice Grouping Rules: Example


Here is example illustrates how to use grouping rules to group transaction lines into transactions during AutoInvoice import.

Assume you defined an AutoInvoice grouping rule that specifies that to appear on the same invoice, items must match on all mandatory attributes, such as currency and customer bill-to address , and must also match on the optional attribute of sales order type

Below diagram illustrates how three imported invoices are created according to the AutoInvoice grouping rule defined in this example:

grouping rule

Items A and B share the same currency and sales order type, so they appear on the same invoice (Invoice 1). Item C has the same currency as A and B, but it has a different sales order type, so it appears on its own invoice (Invoice 2). Items D and E share the same currency and sales order type, so they appear on the same invoice (Invoice 3).

Hope this helps.

Posted in Oracle Receivable | No Comments »

UNDERSTANDING Oracle Bill Presentment Architecture (BPA ): Flexible Invoicing Solution

Posted on December 13th, 2012 by Sanjit Anand ||Email This Post Email This Post

Oracle Bill Presentment Architecture [BPA] is a bill presentment tool [aka user manageable capability] that helps to create and present comprehensive and more-customer-focused invoices that increase the likelihood and timeliness of payment.

BPA provides the architecture to retrieve billing data from multiple data sources, including transaction flexfields and other data not interfaced and stored in Oracle Receivables.

This means that the physically presented bill is no longer limited to information contained within Oracle Receivables.

BPA provides a framework for collecting billing data stored in:

  • Oracle Receivables
  • Oracle applications seeded in BPA, such as Oracle Order Management and Oracle Service Contracts
  • Other Oracle applications
  • Legacy systems and other non-Oracle applications

You then design billing templates for each transaction class, choosing the layout and content to determine how you want billing data to appear in an online or printed bill, and assign the templates to customers or customer categories.

You can print bills individually or in batches from your billing templates created within BPA or uploaded from external sources. Customizing the bills that your customers see helps them reconcile bills with purchase requests and facilitates timely bill payment.

Your customers can view summarized billing information and drill down using hyperlinks to detailed billing information and other related details necessary to understand and pay the bill. This means that the physically presented bill is no longer limited to information contained within Oracle Receivables.

By separating bill presentment from transaction accounting, Oracle BPA allows for more understandable and comprehensive bills, increasing the likelihood and timeliness of bill payment.

BPA provides all the invoice specific functionality needed for a full-fledged invoicing solution from Applications .

dgreybarrow COST /PRICING

BPA is included in the Oracle E-Business Suite Financials family of applications. It’s included with Receivables. When reviewing the diagnostic catalog BPA will show up under Receivables.

dgreybarrow BPA TECHNOLOGY

Oracle BPA uses the same Self-Service Framework as all Oracle’s ERP Self-Service products.

BPA uses XML Publisher to physically generate the PDF output of a printed invoice.

BPA is MLS-enabled. Multilingual Support is the ability to install and run multiple NLS (National Language Support) releases within one instance

BPA can use the following delivery channels are possible:

  • Internet Printing Protocol (IPP) Printer
  • E-mail
  • Fax
  • FTP

Using using the Balance Forward Billing (BFB) feature.you can opt to create consolidated invoices using BPA [This is possible in Release 12]

dgreybarrowWHAT YOU CAN DO WITH BPA

With Bill Presentment Architecture (BPA), you can customize the content and format of bills to be viewed online or printed by your customers and your internal users.You can:

  • Design layout and select content for a bill
  • Display on bills information that is not stored in Oracle Receivables
  • Create hyperlinks that enable access to related billing information
  • Display summary and child lines
  • Provide online drilldown to transaction line details
  • Upload external templates
  • Incorporate attachments on online bills
  • Assign bill formats to specific customers or user-defined customer categories
  • Print transactions and bills
  • Preview billing templates using real-time data

dgreybarrow IMPLEMENTATION AND SETUP STEPS

BPA helps bypass the complex coding and customization traditionally associated with creating customer or industry centric invoices. Though Oracle Documentaion hoighlighted

  1. Registering Data Source
  2. Creating Database Views
  3. Registering Data Source View
  4. Configuring Hyperlinks
  5. Uploading Logo
  6. Creating Custom Message
  7. Template Management
  8. Assigning Templates
  9. External Template Upload
  10. External Template Assignment
  11. Testing the Template

More or less , with these simple five-step process, we can create a customized billing template, and preview it with actual transaction data easily in couple of hrs. These steps are subset of above as follow as:

  1. Create Template to present bills :BPA collects, formats, and presents billing data online and in printed bills, according to templates that you define
  2. Template Assignment :BPA assigns completed billing templates to customers based on the assignment rules that you define. Each rule uses predefined criteria with user-defined conditional values to match templates with customers.
  3. View online bills :Internal users and external customers can view bills online using Oracle Receivables, OracleiReceivables, Oracle Collections or other calling application.
  4. Register Data Sources : This is Required for all nonseeded data sources.
  5. Print BPA invoices

dgreybarrow BENEFITS ON BPA

Major benefits of the BPA functionality are as below :

  1. Expedite Payment and Improve Cash Flow : The invoice designs we create can be assigned to particular customers or particular transactions.This format consistency will help customers process their bills quickly. To efficiently address disputes, billing personnel, receivables clerks, and collectors can view bills in Oracle iReceivables,
    Oracle Receivables, or Oracle Collections, in the same format the customer sees.
  2. MLS enabled : This is the Biggets advantage is MLS-enabled. Templates can be created using any available session language. When printing bills, BPA selects the appropriate template file based on language associated with customer’s address
  3. Flexibility to incorporate Company logo: Custom images and messages can be incorporated in BPA templates
  4. Template for transaction classes other than Invoice :BPA supports template creation for invoices, credit memos, debit memos, chargebacks, guarantees and deposits. Oracle provides seeded templates for the above mentioned transaction classes
  5. Incorporate hyperlinks on online invoices BPA supports creation of hyperlinks and associating them to any content presented in wer online bill, including in the billing lines
    or in the detail lines. Links can be generic, such as access to a company home page, or they can be transaction-specific, such as access to the actual sales order listed on the bill.
  6. Grouping of billing lines For Oracle Service Contracts bills, we can provide summarized billing lines for customers who desire less detail than is stored in Oracle Receivables.

Posted in Oracle Receivable | No Comments »

Implementing Oracle Advanced Collections

Posted on November 19th, 2012 by Sanjit Anand ||Email This Post Email This Post

Oracle Advanced Collections is an enterprise application for collection professionals that simplifies and optimizes the task of performing the various collection activities. This module provides visibility into the collections cycle, helping companies plan and manage effective collection activities thereby reducing the DSO.

It is integrated in the E-Business Suite and covers key collections activities from managing delinquencies to customer interaction to collections.

Oracle Collections is integrated with AR, trade management, Lease Management and Oracle Loans

Advanced Collections is used to contact delinquent customers to collect overdue invoices. The collection process can be handled at various levels

  • Customer
  • Account
  • Bill To
  • Delinquency

Oracle Advanced Collections can be configured for

  • Collection Strategies/Dunning Plans
  • Processing Payments and for capturing Promise to Pay details
  • Recording Disputes
  • Scheduling customer Call-backs
  • Sending Dunning letters to customers

dgreybarrow Mandatory Setups for Advanced Collections

  1. Setting Up Users and Reporting Hierarchy
  2. Setting Up a Group
  3. Verify Group Setup
  4. Setting Up Manager Roles
  5. Creating a Resource, and Assigning Roles and Resource Groups
  6. Setting Up Employees as FND Users and Assigning Responsibilities
  7. Setting Up Collectors
  8. Setting Up Employees as CRM Resources
    • Responsibility:- CRM Resource Manager : Navigation:- Maintain Resources -> Import Resources
  9. Setting Up Preferred Currency
  10. Setting Up and Enabling Currency Conversion
  11. Setting Up Currency Codes
  12. Setting Up the Accounting Calendar
  13. Setting Up Calendar Types
  14. Setting Up Period Type Mapping
  15. Setting Profile Options for Multiple Currency
  16. Setting Up Reporting Currencies
  17. Setting Up Quarters as a Time Period in the General Ledger
  18. Entering GL Daily Conversion Rates
  19. Running Concurrent Programs to Set Up Pseudo Period Rates
  20. Setting Up Lookup Codes
    • Responsibility:- Collections Administrator : Navigation:- Lookup Types
      Add Lookup codes for IEX_Delinquency_Status, IEX_Dispute_Reasons, IEX_History_Type, IEX_UWQ_Labels
  21. Setting Up AR Aging Buckets
  22. Setting Up Collections Operational Data level
    • Responsibility:- Collections Administrator : Navigation:- Setup Checklist -> Operational Setup -> General Collections Information
    • advance collection
    • Select values for Aging Bucket, Operational Data Level, Access Level and functionality access
    • Select values for Default tab, Default Search Type, Default Payment Method etc
  23. Setting Up Collectors Access Levels
  24. Setting Up Notes, Tasks, and Calendar
  25. Setting up Scoring Components
  26. Setting Up Scoring Engine
  27. Setting Up Strategies/Dunning Plans
    • Create Dunning Plans – Select Name, Dunning Level, Aging Bucket, Effective Dates etc.
      • Responsibility:- Collections Administrator : Navigation:- Setup Checklist -> Collections Method Setup -> Create Dunning Plans
    • Create Dunning Plans – Select Aging Bucket Line details
      • Responsibility:- Collections Administrator : Navigation:- Setup Checklist -> Collections Method Setup -> Create Dunning Plans
  28. Enabling Multi-Organization Access
    Responsibility:- Collections Administrator : Navigation:- Setup Checklist

dgreybarrow Profiles that need to be set

  • IEX: Strategy Disabled :IF Strategies are being used select ‘No’ else this should be ‘Yes’
  • IEU: Queue % :Select ‘Yes’ if the node has to be displayed in UWQ
  • IEU: Queue Order % :Enter the number to select the display sequence in the UWQ
  • IEX: Strategy Default Template (only if strategies are being used) :Select the Default Strategy to be used
  • MO: Security Profile :Grouping of Operating Units that can be accessed.
  • MO: Default Operation Unit :Identify the default Operating unit

dgreybarrow Key R12 Enhacement

  • Multi-Org Access Control
  • Enhanced Customer Credit Card and Bank Account Management
  • New Implementation Checklist and questionnaire
  • Collections Functionality of AR migrated to Oracle Advanced Collections
  • Functionalities of Collections Forms Administrator and Collections HTML Administrator combined to a single responsibility Collections Administrator
  • Configuration process has been simplified.
  • Setup is performed using a questionnaire and Setup Checklist
  • Scoring Engines, Strategies and Dunning Plans configuration performed using setup checklist

Posted in Advance Collection, Oracle Receivable | No Comments »

Overview : Receipt-to-Receipt Applications

Posted on November 3rd, 2012 by Sanjit Anand ||Email This Post Email This Post

This is not new feature .

In simple layman :Feature that “allow you to apply an open receipt against another open receipt”

Receipt to Receipt Applications lets you apply receipts to other open receipts that have on-account and unapplied cash.

This provides you with an efficient approach to settling open cash, because it eliminates the need to open multiple receipts to apply on-account and unapplied cash.

From just one receipt, you can apply one receipt to another open receipt, and the balances and accounting are automatically updated on both receipts.

If you use Oracle Marketing Online’s Trade Management to manage claims, then you can now apply to receipts that have open claim investigations, which will in turn update amounts, or cancel claims, in Trade Management. This lets you net underpayments with overpayments in the system. For example, you might do this if you determined that a short payment on a remittance was due to an overpayment on another receipt that resulted in a claim investigation.

Working with Receipt-to-Receipt Applications

You apply a receipt against another open receipt in order to move funds between receipts. Open receipts include receipts that have either unapplied cash or on-account cash. You can then apply the resulting unapplied receipt balance to a transaction.

To use receipt-to-receipt applications, you must set up a clearing account under the Receivables activity Payment Netting to manage the offset of the one receipt against the other.

Both receipts in a receipt-to-receipt application must be in the same currency. If both receipts are in a foreign currency, the result of the receipt application may be an exchange gain or loss. The exchange gain or loss is realized on the target receipt at the time of receipt application. If you later adjust the conversion rate on either receipt, the accounting is rederived using the adjusted conversion rate.

You can unapply a receipt that was applied to another open receipt, provided that neither receipt is drawn negative by unapplying it.

Hope this helps.

Posted in Oracle Receivable | No Comments »

Golden Tax

Posted on October 11th, 2012 by Sanjit Anand ||Email This Post Email This Post

VAT is an important component of the China Government’s entire taxing regime.

China mandates that Value Added Tax calculation, invoice generation, and reporting to tax authorities be done by Chinese certified software certified as “Golden Tax”. Through partnership with Hangtian, a software company for “Golden Tax” software, Oracle R12 offers a plug-and-play interface between Oracle AR and Golden tax system which is called Golden Tax Adaptor.

The official VAT is computed and official VAT invoices as well as reporting of collected VAT to the Chinese tax authorities can be entered and generated in the golden tax system. Information is then sent back through the Golden Tax Adaptor to Oracle AR where collection and accounting are actually done.

The Golden Tax project refers to an integrated nationwide value-added tax (VAT) monitoring system and was launched in a bid to establish a national computerized taxation network. Under this Golden Tax project, all businesses operating in Mainland China are required to use a government certified tax software referred to as the Golden Tax software for generating VAT invoices, VAT calculation, and statutory tax reporting. Chinese government policy requires all businesses to issue all VAT invoices through this Golden Tax system.

Invoice printing VAT Invoices is legal Requirement in China.

Golden Tax Adaptor

In Mainland China it is mandatory to use government authorized software, called Aisino Golden Tax system , for generating VAT invoices and statutory tax reporting.

Golden Tax Adaptor provides seamless integration between Oracle Receivables and the interface of Aisino Golden Tax software and streamlines the process of creating VAT invoices against the Receivables documents to make sure data consistency between Oracle Receivables and the Golden Tax software.

Goldan

The preceding diagram illustrates the integration of Golden Tax Adaptor with the Aisino Golden Tax System.

1Key points about the Golden Tax Adaptor are:

  1. The Golden Tax Adaptor is built on top of Oracle Receivables and Oracle E-Business Tax.
    • The Golden Tax Adaptor is a central repository of data used by Oracle Receivables and the Aisino Golden Tax system.
  2. The Golden Tax Adaptor application consists of tables, a workbench, concurrent programs, and XML publisher reports.
  3. Receivables data for invoices, debit memos, and credit memos can be transferred to the Golden Tax Adaptor by request or periodically.
    • The Golden Tax Invoice Workbench lets you manage, consolidate, and modify the data that is transferred from Receivables before you export the data.
    • You can export data from the Golden Tax Adaptor to a data file. All required validations are performed at the time of export.
    • You can export Golden Tax Adaptor data files into the Aisino Golden Tax system. You can then generate VAT invoices from the Aisino system and send them to customers.
  4. Aisino software allows you to export the VAT invoice data from its system to a data file.
  5. You can import the data file containing the VAT invoice data from the Aisino software into the Golden Tax Adaptor. During this import, the VAT invoice data is validated with the corresponding receivables invoice data in the Golden Tax Adaptor and then updated.
  6. Using the Golden Tax Invoice Workbench , you can view VAT invoice information against the corresponding receivables invoice in the View VAT Invoices window and from the Receivables Transactions window.
  7. Golden Tax Discrepancy and Invoice Mapping reports let you audit and report discrepancies in data between receivables and VAT invoices.
  8. You can use the Golden Tax Invoice Consolidation Mapping report to view the mapping between Golden Tax Adaptor invoices and Consolidated Golden Tax Adaptor Invoices.

1 Golden Tax Process

This feature is built on top of Oracle Accounts Receivable and Oracle E-Business Tax.

The key processes for a typical workflow are as below:

Goldan Tax Process

  1. Create receivables invoices manually or by using auto-invoice from Oracle Order Management.
  2. Transfer receivables transactions to the Golden Tax Adaptor.
  3. Modify the data in the Adaptor using the Golden Tax Invoice Workbench.
  4. Consolidate multiple invoices to an invoice based on the Consolidation rule.
  5. Export the invoice information either from the Golden Tax Invoice Workbench or a separate concurrent program.
  6. Import the flat file into the Aisino Golden Tax System (perform this activity in the Golden Tax software.)
  7. Generate corresponding VAT invoices in the Aisino Golden Tax System (perform this activity in the Golden Tax software.)
  8. Export the VAT invoice information from the Aisino Golden Tax System (perform this activity in the Golden Tax software.)
  9. Import the VAT invoices data file back into the Golden Tax Adaptor.

Hope this helps.

Posted in Oracle Receivable | No Comments »

Service Contract Amortization Process

Posted on July 13th, 2012 by Sanjit Anand ||Email This Post Email This Post

When billing, the system moves the entire billed amount to long-term revenue. When you use amortization, the system moves anything from today’s date plus twelve months to short-term revenue. The system moves anything from the beginning of the contract through the end of the amortization period to recognized revenue.

For service contracts, the Amortization Process is a method of moving long-term revenue to short-term revenue, and then short-term revenue to recognized revenue.

Long-term revenue is contracted for more than a 12-month period.

Short-term revenue is contracted within a 12-month period. Recognized revenue is contracted from the beginning of the contract through the end of the amortization period.
Amortization enables you to manage revenue by moving long-term revenue to short-term revenue, and then to earned or recognized revenue. This system only amortizes billed
revenue. When billing, the system moves the entire billed amount to long-term revenue.

When you use amortization, the system moves anything from today’s date plus twelve months to short-term revenue. The system moves anything from the beginning of the
contract through the end of the amortization period to recognized revenue.

In Oracle EBS , you don’t have any out-of-box feature , you can customize, in order to get , which consist of two process , identifing the new schedule line and GL journal line.

Posted in Oracle Receivable, Service Contracts | No Comments »

« Previous Entries Next Entries »