testing samples

8/3/2019 Testing Samples

1/22

TABLE OF CONTENTS

Explicit Revenue ..................................................................................................................................................................... 1

Customer Acceptance ............................................................................................................................................................. 4

Setup ................................................................................................................................................................................... 4

Pre-billing Acceptance ......................................................................................................................................................... 5

Post-Billing Acceptance ....................................................................................................................................................... 9

Prebilling implicit acceptance ............................................................................................................................................ 14

Contingency Expiration Removal Event ................................................................................................................................ 17

How to Remove the Revenue Contingency for Removal Event Proof of Delivery ............................................................. 19

How to create and then remove a payment based contingency ........................................................................................... 20

EXPLICIT REVENUE

This note shows an example of how to use the seeded contingency 'Explicit Acceptance' to defer revenue and how torecognize it later by using the 'Customer Acceptance' removal event. In this example you might want to require customer'ABC Corporation Worldwide' to always manually accept an item on its transactions before revenue can be recognized. Toaccomplish this you can implement the following:

1. Connect using Revenue Management Super User responsibilityPath: Revenue Contingencies -> Contingencies Definition

1.1 Review that following seeded contingency exists:

Deferral reason = Explicit Acceptance

Description = Post-Billing Acceptance

Removal Event = Customer Acceptance


2/22

1.2 Click on 'Define Assignment Rules' button and create a new rule as follow:

General Information

Rule Name = Any name e.g. 'RR Explicit Acceptance'

Revenue Contingency Name = Explicit AcceptanceEnabled = Yes

Criteria Match All Criteria = Yes

Parameter: Bill To Customer

Conditions: IN

Case sensitive: No

Values: ABC Corporation Worldwide


3/22

2. Connect to an Oracle Receivables responsibility .e.g. 'Receivables, Vision Operations (USA)'Path: Navigate > Transactions > Transactions.

3. Create an invoice for customer 'ABC Corporation Worldwide'

Enter one invoice line

Complete the invoice.

Click on invoice distribution and check that the amount affects the 'Unearned Revenue' account. Revenue will be deferreduntil customer acceptance is manually recorded.

4. ManuallyPath: Control/Accounting/Revenue Accounting

Query for invoice created in step 3


4/22

Click on Manage Revenue -> Record Acceptance -> All Lines Requiring Acceptance -> Finish

5. Use transaction workbench to review that revenue was recognized for invoice created in step 3.Path: Navigate > Transactions > Transactions >(B) Distributions

CUSTOMER ACCEPTANCE

SETUP

1. ENABLING THE FULFILLMENT ACCEPTANCE AT THE ORDER

Responsibility: Order Management Super User

Navigation: Setup -> System Parameters -> Values

2. SETTING UP THE DEFERRAL REASON IN THE RECEIVABLES REVENUE MANAGEMENT

SETUP

Responsibility: Revenue Management Super User


5/22

Navigation: Revenue Contingencies -> Contingency Definition.

In the deferral reason setup, by setting the value for the 'Removal event', you can specify the kind of Acceptance (pre-

billing or post-billing) you would like to use. OM supports pre-billing and post-billing acceptance.

For a pre-billing deferral reason, choose the Removal Event as "Invoicing".

For a post-billing deferral reason, choose the Removal Event as "Customer Acceptance".

To specify a deferral reason to be implicit, we need to specify the optional "Time attribute" fields. OM supports only Ship

Confirm date as the Event attribute. The setup of the deferral reason can be seen as mentioned in the Diag3.

Diag 3

PRE-BILLING ACCEPTANCE

In case of the pre-billing acceptance, the acceptance comes into picture before the Invoicing activity. The list of activities

in pre-billing acceptance is as follows.

Record Acceptance explicit or implicit

Line status moves to closed and line gets interfaced to AR

Invoice generation and Revenue Recognition happen subsequently.

Another feature that can be observed in this flow is that the Sales Order Line will be in a new status called "Pending Pre-

billing Acceptance"

In this scenario the Invoice is generated after the Acceptance of the goods has been completed explicitly. Customer or

CSR logs into the Order Information Portal or uses order import to record acceptance explicitly. The detailed flow of Pre-

billing Explicit Acceptance is as follows.

STEP 1

Deferral reason in Receivables Revenue Management should be setup as shown in Diag4. Make sure that the Removal

event is set to "Invoicing".


6/22

Step 2

Enter the sales order from the Order Management Super User responsibility and select the Acceptance name from the

'Others' tab of the sales order line. Acceptance name can be found from the Folders-> Show field. Select the value of the

Deferral reason i.e. pre-billing_explicit from the list of values of the Acceptance name. From the Diag5 it can be seen that

the Acceptance Type is invoicing.

Book the order, Pick-release the order and Ship-confirm the same.

Step 3

After the line has been shipped run the Workflow Background Process for the OM order Line. A new status of the sales

order line "Pending pre-billing acceptance" can be seen as shown in Diag6. This status indicates that the line is waiting for

the Acceptance to happen.

Diag 6

STEP 4


7/22

Explicit Acceptance can be done from Actions-> Fulfillment Acceptance. The same is shown in Diag7.

Diag 7

The Fulfillment Acceptance action attribute has to be clicked to launch the OIP to record explicit acceptance of goods and

services.

STEP 5

Fulfillment Acceptance action attribute launches the OIP page as in Diag8.

Diag 8

In this page Acceptance Date is not populated and the Acceptance Status is 'Pending'. To initiate Acceptance click on

'Go' button.

Step 6


8/22

On the click of 'Go', the page seen in Diag 9 comes up. The user can enter information related to acceptance like

Acceptance comments and signature. The details given here will be available in Sales Order on re-querying.

Diag 9

STEP 7

On click of the Submit button, a confirmation message comes up indicating that Acceptance/ rejection has been

completed successfully. The same is indicated in Diag10.

Diag 10

After the confirmation the change in Acceptance date and Acceptance status is reflected on the OIP, the Acceptance

status is changed to 'Accepted' and the 'Acceptance Date' is populated with date value on which the Acceptance was

done. The same is shown in Diag11.

Diag 11

STEP 8

Customer Acceptance information recorded in the OIP page can be found on the others tab of the sales order line. The

same is shown in Diag12


9/22

Diag 12

STEP 9

After the Auto invoice concurrent program is run in Receivables responsibility, the Invoice can be generated and the

revenue recognition would follow.

Diag 13

POST-BILLING ACCEPTANCE

In case of the post-billing acceptance, the acceptance comes into picture after the Invoicing activity. The list of activities

in post billing acceptance is as follows.

Invoice generation> Revenue recognition

Record Acceptance explicit or implicit

Line status moves to closed

Revenue Recognition happens once acceptance is completed

Another feature that can be observed in this flow is that the Sales Order Line will be in a new status called Pending Post-

billing Acceptance. Apart from the above, there are two more kinds of Acceptance viz.

Explicit acceptance - In Explicit Acceptance Customer or Customer Sales Representative (CSR) logs into the

Order Information Portal or uses order import to record acceptance explicitly.

Implicit acceptance - In Implicit acceptance after a specific expiration period a request set is submitted to record

the acceptance. Deferral reason has to be defined in AR with event attribute as Ship Confirm date and expiration

days. There is Implicit Acceptance Request Set, which is part of OMs standard concurrent programs for recording

implicit acceptance.

Request Set has two concurrent requests

I. Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance

II. Revenue Contingency Analyzer for Post-billing, Implicit Acceptance


10/22

Once the expiration date has got elapsed, the above set of concurrent programs are submitted and the Acceptance is

recorded

In the case of Post-billing explicit acceptance, the invoice will not wait till the acceptance happens, instead the Invoice is

generated first and later the Acceptance happens. Customer or CSR logs into the Order Information Portal or uses order

import to record acceptance explicitly. The detailed flow of Post-billing Explicit Acceptance is as follows.

STEP 1

Deferral reason in Receivables Revenue Management should be setup as shown in Diag14. Make sure that the Removal

event is set to 'Customer Acceptance'. The Navigation for setting up the Deferral reason is as follows.

Revenue Management Super User -> Contingency Definition -> This launches this HTML page.

Diag 14

STEP 2


'Others' tab of the sales order line. Acceptance name can be found from the Folders-> Show field. Select the value of the

Deferral reason i.e. post-billing_explicit from the list of values of the Acceptance name. From the Diag15 it can be seen

that the Acceptance Type is Customer Acceptance.

Diag 15

Book the order, Pick release the order and Ship confirm the same.


11/22

Step 3

After the line has been shipped run the Workflow Background Process for the OM order Line. A new status of the sales

order line 'Pending post billing acceptance' can be seen as shown in Diag16. This status indicates that the line is waiting

for the Acceptance to happen.

Diag 16

STEP 4

From the Receivables responsibility run the Autoinvoice concurrent program and the invoice gets generated (ref Diag 17).

Diag 17

STEP 5

In Diag 18, you can see that the Invoice has already got generated with the line status still in 'Pending post billing

acceptance'. The revenue recognition happens once acceptance is completed.


12/22

Diag 18

STEP 6

The Fulfillment Acceptance action attribute has to be clicked to launch the Order Information Portal (OIP) to record explicit

acceptance of goods and services. Explicit Acceptance can be done from Actions -> Fulfillment Acceptance. Fulfillment

Acceptance action attribute launches the OIP page as in Diag 19. In this page Acceptance Date is not populated and the

Acceptance Status is 'Pending'.


13/22

Diag 19

To initiate Acceptance click on 'Go' button.

STEP 7

On the click of 'Go', the page seen in Diag 20 comes up. The user can enter information related to acceptance like

Acceptance comments and signature. The details given here will be available in Sales Order on requerying.

Diag 20

STEP 8

On click of the Submit button, a confirmation message comes up indicating that Acceptance/rejection has been completed

successfully. After the confirmation the change in Acceptance date and Acceptance status can is reflected on the OIP,

the Acceptance status is changed to 'Accepted' and the 'Acceptance Date' is populated with date value on which the

Acceptance was done. The same is shown in Diag11.

Customer Acceptance information recorded in the OIP page can be found on the others tab of the sales order line. The

same is shown in Diag 21.

Diag 21


14/22

PREBILLING IMPLICIT ACCEPTANCE

In this scenario the Invoice is generated after the Acceptance of the goods has been completed implicitly. In Implicit

acceptance after a specific expiration period a request set is submitted to record the acceptance. Deferral reason has to

be defined in AR with event attribute as Ship Confirm date along with a value for expiration days. The detailed flow of

Pre-billing Implicit Acceptance is as follows.

Step 1

Deferral reason in Receivables Revenue Management should be setup as shown in Diag22. Makes sure that the Remova

event is set to 'Invoicing'. The Optional time attributes should be set for Implicit Acceptance 'Event Attribute' field is set to

'Ship confirm date' and a value is specified for the field 'Days added to event attribute'

The Navigation for setting up the Deferral reason is as follows.

Responsibility: Revenue Management Super User -> Contingency Definition

Diag 22

STEP 2


Others tab of the sales order line. Acceptance name can be found from the Folders -> Show field. Select the value of the

Deferral reason i.e. pre-billing_implicit from the list of values of the Acceptance name. The same can be seen from Diag

23.


15/22

Diag 23

STEP 3

Book the order, Pick release the order and Ship confirm the same. After the line has been shipped run the Workflow

Background process for the OM order Line. A new status of the sales order line Pending pre billing acceptance can be

seen on order line. This status indicates that the line is waiting for the Acceptance to happen.

STEP 4

Implicit Acceptance is done through a request set.

Navigation: Order Management Super user -> Requests->

Submit a request set.

Request Set has two concurrent requests (ref Diag 24). Generate Pre-billing Acceptance Program for Pre-billing, Implicit

Acceptance Revenue Contingency Analyzer for Post-billing, Implicit Acceptance

Diag 24a

STEP 4 (A)


16/22

The concurrent program Generate Pre-billing Acceptance Program for Pre-billing, Implicit Acceptance accepts two

parameters

I. Org_Id: Acceptance for all the Order Lines waiting at Pre-billing acceptance will be done. This is not a mandatory field

II.Acceptance Date: It accepts two values 'System Date' or 'Expiry Date'. If the value is 'System Date', the current system

date is taken as the acceptance date for the Order Line. If the value is 'Expiry Date' the expiry date is calculated by adding

the Number of Expiry Days to the Actual Shipment Date (if this is not available the Fulfillment date is considered), and this

date is considered as the acceptance date. Please note this parameter was added via ER numbers 7609564 (OM) and

7556149 (AR).

Diag 24b

STEP 5

When a line is implicitly accepted, the 'Implicit Acceptance' check box reflects that on the 'Others' tab of the sales order

lines. Also, the acceptance date, the user who ran the concurrent request set and the accepted quantity get updated

automatically. The same is indicated in the Diag 24.

Diag 25

STEP 6


17/22

Once the Acceptance is completed, Line status moves to closed and line gets interfaced to AR. Invoice generation and

Revenue Recognition happen subsequently.

CONTINGENCY EXPIRATION REMOVAL EVENT

1. Connect using Revenue Management Super User responsibility

Path: Revenue Contingencies -> Contingencies Definition

1.1 Create a New Revenue Contingency entering following information:

Deferral reason = Any name e.g. 'RR EVENT BASED'

Related General Policy = None

Removal Event = Contingency Expiration

Optional Time Attributes

Event Attribute: Transaction Date

Days Added to Event Attribute: 0

1.2 Click on 'Define Assignment Rules' button and create a new rule as follow:

General Information

Rule Name = Any name e.g. 'RR Transaction Type'


18/22

Revenue Contingency Value = RR EVENT BASED (Deferral reason Created in 1.1)

Enabled = Yes

Criteria

Match All Criteria = Yes

Parameter: Transaction Type

Conditions: IN

Case sensitive: No

Values: Inv-Consult-East

2. Connect to an Oracle Receivables responsibility .e.g. 'Receivables, Vision Operations (USA)'

Path: Navigate > Transactions > Transactions.

3. Create an invoice using transaction type 'Inv-Consult-East'.

Enter one invoice line

Complete the invoice.

Click on invoice distribution and check that the amount affects the 'Unearned Revenue' account.


19/22

4. Run Revenue Contingency Analyzer program

Path: Control >Accounting > Revenue Recognition

Select concurrent program Revenue Contingency Analyzer

Select your Operating Unit

Alternatively you can run 'Submit Accounting' (in release 12) and it will spawn Revenue Contingency Analyzer program.

Note. Revenue Contingency Analyzer is the program that automatically initiates revenue recognition for the expired

contingencies. In this example the contingency expires when trx_date is lower or equal than sysdate.

5. Use transaction workbench to review that revenue was recognized for invoice created in step 3.

Path: Navigate > Transactions > Transactions >(B) Distributions

HOW TO REMOVE THE REVENUE CONTINGENCY FOR REMOVAL EVENT PROOF OF

DELIVERY

Proof of Delivery is entered at time in Shipping Execution when goods are shipped, and theend-customer signs documentation verifying that he/she has received the shipment. Thisinformation is entered by doing the following:

1. Navigate to the Shipping Transactions form, and search for the delivery to be confirmed.

2. In the Deliveries tab, click on the Details button.3. In the Delivery Details form, click on the 'Legs' tab4. Click on the Details button in this form.5. This brings up a form that is labeled "Bill of Lading" In this form there are two fields whichmay be updated by the user: POD signed by, and POD date.

A2: Entering this information will not remove the revenue contingency in AccountsReceivable. After extensive analysis inBUG 6665402, development concluded that the onlyother Oracle Application which actually uses Proof of Delivery information is FTE OracleTransportation Execution; and FTE has been de-supported with release 12.1. The
https://support.oracle.com/CSP/main/article?cmd=show&type=BUG&id=6665402https://support.oracle.com/CSP/main/article?cmd=show&type=BUG&id=6665402https://support.oracle.com/CSP/main/article?cmd=show&type=BUG&id=6665402https://support.oracle.com/CSP/main/article?cmd=show&type=BUG&id=6665402


20/22

replacement product, Oracle Transportation Management, does not use proof of deliveryinformation. Additionally, there is no interface between Shipping Execution and AccountsReceivable which would tell AR to remove the revenue contingency.

Since the POD information entered in the "Bill of Lading" form is not used by any other Oracleapplication, these fields should be viewed as customer information or comment fields. Usersof the Accounts Receivable product will need to review Accounts Receivable documentation

to find another way to remove the revenue contingency. Alternatively, AR users may decideto implement other contingencies in lieu of the revenue contingency.

It is not possible to manually remove a POD contingency. This can only be done through theWarehouse management responsibility or through the script.

Example:

BEGINar_revenue_management_pvt.process_event(p_cust_trx_line_id => &trx_line_id,p_event_date => '20-OCT-2006',p_event_code => 'PROOF_OF_DELIVERY');END;

HOW TO CREATE AND THEN REMOVE A PAYMENT B ASED CONTINGENCY

This note shows an example of how Revenue Management Engine defers revenue on aninvoice because the customer is not creditworthy. Also the note shows how to recognize therevenue after registering a receipt application.

SOLUTION

In this example you might want defer revenue to all invoice lines for a particular customer (e.g

customer number 1006) because the customer is not creditworthy. To accomplish previous

scenario you can implement the following:

1. DEFINE YOUR REVENUE POLICY

1.1 Connect using Revenue Management Super User responsibility

Path: Revenue Policy -> Revenue Policy

1.2 Select your Operating Unit (e.g Vision Operations)

1.3 Under Credit Classifications enter Credit Classification 1 =

(e.g 'New Customer')


21/22

2. ASSIGN THE CREDIT CLASSIFICATION AT THE CUSTOMER PROFILE LEVEL, OR

AT CUSTOMER ACCOUNT OR SITE LEVEL. IN THIS EXAMPLE WE WILL ASSIGN THE

CREDIT CLASSIFICATION AT CUSTOMER SITE LEVEL.

2.1 Connect to an Oracle Receivables responsibility .e.g. 'Receivables, Vision

Operations (USA)' Path: Customers -> Customers

2.2 Look for your customer (e.g 1006). At customer site level under profile tab assign

the credit classification used in 1.3 ('New Customer')

3. Create an invoice (manual or Autoinvoice) for customer number 1006. Complete the

invoice. Click on invoice distribution and check that the amount affects the 'Unearned

Revenue' account. Revenue will be deferred until a payment is created.


22/22

4. Create a receipt for the invoice created in step 3. When applying a partial receipt,

receivables used a weighted average formula to calculate the revenue amounts to

recognize for each line.

5. Use transaction workbench to review that revenue was recognized for invoice

created in step 3.

Path: Navigate > Transactions > Transactions >(B) Distributions

testing samples

Documents