R12 New Features in QTC Track
1 / 39

O2 Lead Team - PowerPoint PPT Presentation

  • Uploaded on

R12 New Features in QTC Track NCOAUG 22-Feb-08 Ravi Sagaram Agenda Introduction Discuss Key New Features Questions and Answers Key Features Cascading Attributes from Header to Lines Customer Acceptance Deferred COGS and Revenue Exception Management Multi Org Access Sales Agreements

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'O2 Lead Team' - andrew

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Slide1 l.jpg

R12 New Features in QTC Track



Ravi Sagaram

Slide2 l.jpg


  • Introduction

  • Discuss Key New Features

  • Questions and Answers

Slide3 l.jpg

Key Features

  • Cascading Attributes from Header to Lines

  • Customer Acceptance

  • Deferred COGS and Revenue

  • Exception Management

  • Multi Org Access

  • Sales Agreements

  • Actual Ship Date

  • Parallel Pick Release

Slide4 l.jpg

Cascading Attributes


Cascade Modified Attributes from Order Header to Lines


  • Reduces Manual Update of Multiple Lines

  • Reduces Multiple Key Strokes

  • Increases Productivity

  • Increases Accuracy

Slide6 l.jpg

Cascading Attributes


  • Setup the Profile Option

    ‘OM: Sales Order Form: Cascade Header Changes to Line’

Slide7 l.jpg

Cascading Attributes


Enable the Cascading Attributes.

Setup  Quick Codes  Order Management  Type – ‘OM_HEADER_TO_LINE_CASCADE’

Slide8 l.jpg

Customer Acceptance


  • In high tech industries like Telecom, the order process may not end with the shipping of the goods and services to the customer.

  • In many cases, the goods that are shipped might have to be installed, tested, and accepted before invoicing and revenue recognition.

  • There is no feature in R11 to record Customer Acceptance.

Slide9 l.jpg

Customer Acceptance


  • R12 Provides a new feature ‘Revenue Contingency’ which can be used for pre billing or post billing customer acceptance.

  • In Pre-billing acceptance, the line gets invoiced, closed and revenue recognized after the acceptance.

  • In post Billing acceptance, the line gets closed and revenue recognized after the acceptance.

Slide10 l.jpg

Customer Acceptance


Process diagram

Slide11 l.jpg

Customer Acceptance


Invoice Pending Acceptance is New in R12 – Can be used as Pre billing Acceptance

Slide12 l.jpg

Customer Acceptance

Close Line – Pending Acceptance is the new feature in R12– Can be used as Post Billing Acceptance

Slide13 l.jpg

Customer Acceptance


  • Enable OM System Parameter ‘Enable Fulfillment Acceptance’

    Setup  System Parameters  Define  ENABLE_FULFILLMENT_ACCEPTANCE

Slide14 l.jpg

Customer Acceptance

Setups (Contd..)

  • Define a Deferral reason ‘Customer Acceptance’ in the Revenue Management . Specify the removal event. There are 5 removal events

  • Define an assignment rule to assign the deferral reason to a parameter like receivables transaction type, customer, customer site, item etc.

  • Enable the folder fields for Customer Acceptance in Order Lines.

Slide15 l.jpg

Customer Acceptance

Setups (Contd..)

Slide16 l.jpg

Customer Acceptance


  • Customer Acceptance is recorded by user in the OM in the order header or order lines.

  • It is not possible to record acceptance for partial quantity. Either accept or reject full qty.

  • The acceptance can be recorded explicitly by the user or implicitly by time out feature (like 30 days from shipping etc.)

  • Once the acceptance is recorded, the line will progress to invoicing and close in the case of pre-billing or just close after post billing.

Slide17 l.jpg

Customer Acceptance


A sales order with pre-billing customer acceptance

Slide19 l.jpg

Customer Acceptance


  • Use Additional Line Information or Order Information to record customer Acceptance

Slide21 l.jpg

Deferred COGS


  • Accounting Standards stipulate that COGS and Revenue are recognized in the same accounting period.

  • In R12, a new feature was provided to invoke deferred COGS instead of COGS upon shipment.

  • When revenue is recognized upon customer acceptance or a deferral reason, then an accounting transaction is created to hit the COGS account.

  • COGS will be recognized to the same percentage as the revenue.

Slide22 l.jpg

Deferred COGS


Setup deferred COGS account in inventory organization

Setup  Organizations  Inventory  Other Accounts tab

Slide23 l.jpg

Deferred COGS


  • Enter, Book and Ship an Order in OM

  • Accounting transactions are generated against deferred COGS.

  • Invoice and close the line removing the revenue contingency. The transactions will reverse form DCOGS to COGS.

  • If it is a ship only line, reversal from DCOGS to COGS will take place upon closing of the line.

Slide24 l.jpg

Exception Management


  • R12 provides a concurrent Program to preview and retry stuck transactions (due to errors in workflow)

  • In the Preview mode, a log is generated to give the reasons for the errors.

  • In the execution mode, the error WFs are retried

  • A concurrent Program was provided to retry these error WFS. The Program name is ‘Retry Errored Workflow Activities’

  • Schedule to run this program – probably once in a day.

Slide26 l.jpg

Multi Org Access


  • Multi Org Access feature in R12 provides access to data from multiple operating units without switching responsibilities.

  • Using this feature, users can

    • View and create orders, BSAs, quotes etc.

    • Do setups for different operating units from the same responsibility.

    • Run reports for multiple OUs.

Slide27 l.jpg

Multi Org Access


  • Create a security profile using HR responsibility

  • Assign different OUs to the security Profile.

  • Assign the Security profile to the system profile ‘MO: Security Profile’ at the responsibility level.

Slide28 l.jpg

Multi Org Access


  • Enable the Operating Unit field on the forms for BSA, Order Header, Quote Etc. This can be done using the Folder Tools.

  • Enter the value for OU before entering the other data. This will enable the other fields on the form.

  • When running reports, enter OU as the optional parameter.

Slide29 l.jpg

Sales Agreements


  • BSAs are renamed as Sales Agreements in R12

  • Sales Agreements have been enhanced to handle PTOs

Slide30 l.jpg

Actual Ship Date


  • R12 Provided a new feature to enter Actual Departure Date (It can be even a future date) on the following.

    • Pick Release Concurrent Program

    • Pick Release from the form

    • Ship Confirm Concurrent Program

Slide31 l.jpg

Actual Ship Date


Shipping Release Sales Orders  Release Sales Orders SRS

Slide32 l.jpg

Actual Ship Date


Shipping Release Sales Orders  Release Sales Orders

Select Ship Confirm Rule to enable the actual departure date

Actual Dep date

Slide33 l.jpg

Actual Ship Date


Shipping Release Sales Orders  Ship Confirm Deliveries SRS

Slide34 l.jpg

Actual Ship Date


Setup  Shipping  Global Parameters

Enable Allow Future Ship Date

Slide35 l.jpg

Parallel Pick Release


  • R12 Provides a new feature to launch Parallel Pick Release

  • This feature launches multiple workers for the pick release.

  • This will improve the performance of the pick release.

Slide37 l.jpg

Parallel Pick Release


  • Set up the profile option ‘WSH: Number of Pick Release Child Processes’ to the N child processes (N> 2)