defer cogs

Functional Test Script Template

45931928.doc Cost Management

FUNCTIONAL TEST SCRIPT Oracle Cost Management TEST FLOW: DEFER COGSAuthor: Creation Date: Last Updated: Version: Release: Execution Start Date: Srinivas Raju Venkatesan March 10th, 2005 November 19, 2010 1.01 12i [ST date not yet available]

Execution Completion Date: [ST date not yet available] Test Executor: Status: Srinivas Raju Venkatesan IN REVIEW (IN PROGRESS, DRAFT, IN REVIEW, APPROVED) Disclaimer: The following information is confidential and is for internal use only. There is no commitment on content or scheduling for the functionality contained within this document.

11/19/2010 11/19/2010

Oracle Confidential - For internal use only

Page 1



11.1

Document ControlChange RecordPosition QA Project Lead Senior QA Engineer Date Mar 10, 2005 May 05,2005 Document Version 1.00 1.01 Description of Change Including Section of Script Initial creation Incorporated review comments from development

Name P Chandra Shekar Srinivas Raju Venkatesan

1.2Name

Document Review and Approval HistoryRole Author Contributor Author Reviewer/ Approver Position QA Project Lead Senior QA Engineer Project Lead Document Review Status (Completed / Approved) Date Reviewed Comments Incorporated

P Chandra Shekar Srinivas Raju Venkatesan Bryan Kuntz

1.3

Document ReferencesType of Reference Word Doc Word Doc Document Location http://files.oraclecorp.com/content/MySharedFolders/CSTDEV/11.5.11/Development/ Deferred%20COGS/cst_Deferred_COGS_rdd.doc http://files.oraclecorp.com/content/MySharedFolders/CSTDEV/11.5.11/Development/ Deferred COGS/cst_Deferred_COGS_FDD.doc

Name Costing RDD for this project Costing FD for this project

1.4

Resource Estimates [Optional]

Resource Estimate (Hrs) for Manual Execution of this Test Script is11/19/2010 11/19/2010 Oracle Confidential - For internal use only Page 2

Functional Test Script Template Resource Estimate (Hrs) for Automated Execution of this Test Script is


11/19/2010 11/19/2010


Page 3



2

Table of Contents1 DOCUMENT CONTROL..................................................................................................2 1.1 CHANGE RECORD......................................................................................................................................................2 1.2 DOCUMENT REVIEW AND APPROVAL HISTORY...............................................................................................................2 1.3 DOCUMENT REFERENCES ...........................................................................................................................................2 1.4 RESOURCE ESTIMATES [OPTIONAL]..............................................................................................................................2 2 TABLE OF CONTENTS....................................................................................................4 FUNCTIONAL TEST OVERVIEW...................................................................................5 2.1 INTRODUCTION/OVERALL TEST OBJECTIVES..................................................................................................................5 2.2 TEST OUTLINE..........................................................................................................................................................6 2.3 PROCESS FLOW [OPTIONAL].....................................................................................................................................24 3 DEPENDENCIES/REQUIREMENTS............................................................................25 3.1 TEST SCRIPT LIMITATIONS........................................................................................................................................25 3.2 TEST SCRIPT DEPENDENCIES / ASSUMPTIONS...............................................................................................................25 3.3 DEFAULT SETUP [OPTIONAL]....................................................................................................................................25 4 TEST SCENARIOS ..........................................................................................................27 4.1 [CLICK HERE AND TYPE THE NAME OF THE SCENARIO]...................................................................................................27 4.1.1 [Click here and type the name of the Test Case].........................................................................................27 5 SUMMARY OF RESULTS/ISSUES...............................................................................28 5.1 ISSUES LOG ...........................................................................................................................................................28 6 APPENDIX........................................................................................................................29 6.1 APPENDIX A - TEST SCRIPT REVIEW TEMPLATES........................................................................................................29 6.1.1 Outline Review Template.............................................................................................................................29 6.1.2 Test Script Review Template (after first Draft)...........................................................................................31 6.1.3 Test Script Review Template (after first Round Testing).............................................................................32

11/19/2010 11/19/2010


Page 4



Functional Test Overview

2.1

Introduction/Overall Test ObjectivesThis script is intended to verify that the following functionality is working successfully: The principle that will ensure the consistency between revenue and cost of goods sold is that all instances of COGS recognition will be driven by revenue recognition or changes in the billable quantity. The proportion of total shipment cost that is recognized as COGS will always match the proportion of total billable quantity that is recognized as revenue. The Cost Management module will not make an adjustment to the COGS proportion for any order management transaction without either an event from Receivables indicating that a proportional adjustment has been made to the revenue, or an event (from OM or Inventory) indicating that the billable quantity has changed. For a regular sales order, at the time of ownership transfer the Costing Module will debit a new account called the Deferred COGS account for the entire cost of the shipment. This action replaces the actual COGS account debit that we make today. Based on some event that is related to contingencies (or the lack thereof), AR will decide to recognize revenue that was deferred at the time of shipment. At the same time, they will publish an event that notifies Costing of the proportion of total revenue that has been recognized. Costing will subscribe to this notification and create an event in MMT to reflect the COGS recognition to the shipment line or lines that relate to revenue line. Costing will create the accounting for this event by crediting the deferred COGS account and debiting the actual COGS to achieve the same proportion of recognition that exists in the revenue accounts. RMAs will be accounted for such that the distribution of credits between deferred COGS and actual COGS will maintain the existing proportion that Costing is aware of. This proportion can be adjusted once an MMT COGS recognition event is created indicating that AR has changed its proportion of total receivables that is recognized as revenue (possibly due to a related credit memo). Also regarding RMAs, we will need to change the way we perform the accounting for them today. RMAs should ideally be received into inventory at the same cost at which they were issued. Today we treat them as cost derived transactions, meaning they are received at the current average cost. For this project we should fix that so that wherever possible they are treated as cost owned transactions: Receive at the sales order cost and update the current average cost with this new value. PAC will support revenue / COGS matching in the same way as perpetual. It will use the same deferred COGS, outbound materials, and scrap accounts that are setup in the organization parameters form.

11/19/2010 11/19/2010


Page 5



2.2

Test Outline

Scenario 5.1: Sales orders without Customer Acceptance support in standard costing Org

Priority (H,M,L)

Effort Requi red to write detail test script (in days)

Effor t Requ ired to exec ute man ual test scrip t (in hour s)

Effort Require d to Record Automa ted Script (in days)

Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is not enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal

Test Case1 Sales Order Issue and full Revenue Recognition for the Sales Order

DescriptionSales Order Issue from Standard Org, Full Revenue Recognition for the Sales Order and RMA for Partial Qty with credit memo for Asset Item and receive the RMA in Asset subinventory Sales Order Issue from Standard Org, 50% Revenue Recognition for the Sales Order and RMA for Partial Qty with credit memo Sales Order Issue from Standard Org, Customer Billed for the Sales Order and RMA for Partial Qty with credit memo RMA Order with credit memo for Asset Item and receive the RMA in Asset subinventory without reference to Sales order shippedOracle Confidential - For internal use only

M

2 Sales Order Issue and 50% Revenue Recognition for the Sales Order 3 Sales Order Issue and customer Billed for the Sales Order 4 RMA not tied to Original Sales Order

H

H

L

11/19/2010 11/19/2010

Page 6

Functional Test Script Template Scenario 5.1: Sales orders without Customer Acceptance support in standard costing Org

45931928.doc Cost Management Priority Effort Effor Effort (H,M,L) Requi t Require red to Requ d to write ired Record detail to Automa test exec ted script ute Script (in man (in days) ual days) test scrip t (in hour s)

Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is not enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal 5 Sales Order Issue and No invoicing Sales Order Issue from Standard Org and no customer invoice for sales order

H

11/19/2010 11/19/2010


Page 7

Functional Test Script Template Scenario 5.2: Sales orders without Customer Acceptance support in Average costing Org


Automa ted Y/N?



DescriptionSales Order Issue from Average Org, Full Revenue Recognition for the Sales Order and RMA for Partial Qty with credit memo for Asset Item and receive the RMA in Asset sub inventory Sales Order Issue from Average Org, 50% Revenue Recognition for the Sales Order and RMA for Partial Qty without credit memo Sales Order Issue from Average Org, Customer Billed for the Sales Order and RMA for Partial Qty without credit memo Sales Order Issue from Average Org and no customer invoice for sales order M

2 Sales Order Issue and 50% Revenue Recognition for the Sales Order 3 Sales Order Issue and customer Billed for the Sales Order 4 Sales Order Issue and No invoicing

H

H

L

11/19/2010 11/19/2010


Page 8

Functional Test Script Template Scenario 5.3: Sales orders without Customer Acceptance support in FIFO costing Org

45931928.doc Cost Management Priority (H,M,L) Effort Requi red to write detail test script (in days) Effor t Requ ired to exec ute man ual test scrip t (in hour s) Effort Require d to Record Automa ted Script (in days) Automa ted Y/N?



DescriptionSales Order Issue from FIFO Org, Full Revenue Recognition for the Sales Order and RMA for Partial Qty with credit memo for Asset Item and receive the RMA in Asset subinventory Sales Order Issue from FIFO Org, 50% Revenue Recognition for the Sales Order and RMA for Partial Qty without credit memo Sales Order Issue from FIFO Org, Customer Billed for the Sales Order and RMA for Partial Qty without credit memo RMA Order with credit memo for Asset Item and receive the RMA in Asset sub inventory without reference to Sales order shipped Sales Order Issue from FIFO Org and no customer invoice for sales order Sales Order Issue from FIFO Org, Full Revenue Recognition for the Sales Order FOROracle Confidential - For internal use only

H

2 Sales Order Issue and 50% Revenue Recognition for the Sales Order 3 Sales Order Issue and customer Billed for the Sales Order 4 RMA not tied to Original Sales Order

H

H

H

5 Sales Order Issue and No invoicing 6 Sales Order Issue and full Revenue Recognition for the Sales Order11/19/2010 11/19/2010

L M

Page 9

Functional Test Script Template Scenario 5.3: Sales orders without Customer Acceptance support in FIFO costing Org


Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is not enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal Qty with two different Layer and perform a RMA for Partial Qty with credit memo for Asset Item and receive the RMA in Asset subinventory.Validate for the Layer Cost Created for the RMA.

11/19/2010 11/19/2010


Page 10

Functional Test Script Template Scenario 5.4: Sales orders with Customer Acceptance support in standard costing Org


Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is enabled from OM. Perform pick release and ship the sales order to customer. Customer accepts the full shipment and billing is doen for the sales order. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal

Test Case1 Sales Order Issue and full acceptance for the Sales Order

DescriptionSales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform billing cycle for the sales order and 50% revenue recognition. Create RMA for Partial Qty with credit memo for Asset Item and receive the RMA in Asset subinventory Sales Order Issue from Standard Org, Accept the Full qty of the shipment. Create RMA for Scrap Qty with credit memo and receive the RMA in expense subinventory Sales Order Issue from Standard Org and no customer invoice for sales order H

2 Sales Order Issue and RMA

M

3 Sales Order Issue and No invoicing

L

11/19/2010 11/19/2010


Page 11

Functional Test Script Template Scenario 5.5: Sales orders with Customer Acceptance support in Average costing Org


Automa ted Y/N?



DescriptionSales Order Issue from Avergae Org, Accept the full shipment for the Sales Order. Perform billing cycle for the sales order and 50% revenue recognition. Create RMA for Scrap Qty without credit memo for Asset Item and receive the RMA in Asset subinventory Sales Order Issue from Average Org,. Perform Pre-billing cycle for the sales order and revenue recognition. Create RMA for Qty with credit memo for Asset Item and receive the RMA in expense subinventory Sales Order Issue from Average and no customer invoice for sales order H

2 Sales Order Issue and Pre-billing with RMA

M


L

11/19/2010 11/19/2010


Page 12

Functional Test Script Template Scenario 5.6: Sales orders with Customer Acceptance support in FIFO costing Org


Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is enabled from OM. Perform pick release and ship the sales order to customer. Customer accepts the full shipment and billing is does for the sales order. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal


DescriptionSales Order Issue from FIFO Org, Accept the full shipment for the Sales Order. Perform billing cycle for the sales order and 100% revenue recognition. Create RMA for Scrap Qty with credit memo for Asset Item and receive the RMA in Expense subinventory Sales Order Issue from FIFO Org,Perform Pre-billing cycle for the sales order and revenue recognition. Sales Order Issue from FIFO Org, Accept the Full qty of the shipment. Perform Post billing cycle for the sales order and revenue recognition. Perform a SO Issue & Full Acceptance generate all the Events except Revenue Recognition .Generate a Back dated Revenue Recognition Event & validate on the Accounting H

2 Sales Order Issue and Pre-billing for the Sales Order 3 Sales Order Issue and Post Billing for the Sales Order

M

L

4 Sales Order Issue and full acceptance for the Sales Order & perform a back dated Revenue Recognition Event

L

11/19/2010 11/19/2010


Page 13

Functional Test Script Template Scenario 5.6: Sales orders with Customer Acceptance support in FIFO costing Org


Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is enabled from OM. Perform pick release and ship the sales order to customer. Customer accepts the full shipment and billing is does for the sales order. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal 5 Sales Order Issue and full acceptance Perform a SO Issue & Full Acceptance. Generation for the Sales Order & Back dated RMA of all Recognition Event(COGS & Revenue).After this perform a RMA.Validate on the Events. after Recognition 6 Validate the impact of Back dated Events with Future Events with all AR Period are kept Open AR periods are kept open & to validate on the impact in the past to examine how creation of backdated events will affects future events.

M

M

11/19/2010 11/19/2010


Page 14

Functional Test Script Template Scenario 5.7: Sales orders without Customer Acceptance support for ATO and PTO Items


Automa ted Y/N?



DescriptionSales Order Issue with ATO Item from Standard Org, Full Revenue Recognition for the Sales Order and RMA for Scrap Qty with credit memo for and receive the RMA in Asset subinventory Sales Order Issue with PTO Item from Average Org, 50% Revenue Recognition for the Sales Order and RMA for Scrap Qty with credit memo Sales Order Issue with ATO from FIFO Org, Customer Billed for the Sales Order and RMA for Qty with credit memo RMA Order with credit memo for ATO and PTO Item and receive the RMA in Asset subinventory without reference to Sales order shipped Sales Order Issue ATO and PTO items from Standard Org and no customer invoice for sales orderOracle Confidential - For internal use only

M

2 Sales Order Issue and 50% Revenue Recognition for the Sales Order

H

3 Sales Order Issue and customer Billed for the Sales Order 4 RMA not tied to Original Sales Order

H

L


L

11/19/2010 11/19/2010

Page 15

Functional Test Script Template Scenario 5.7: Sales orders without Customer Acceptance support for ATO and PTO Items


Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is not enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal 4 Sales Order and full acceptance for Sales Order Issue from Standard Org, Accept SO ,Invoicing for shippable Child Item the full shipment for the Sales Order. Perform only Invoicing for shippable Child Item only item in the Configuration 5 Sales Order and acceptance for SO ,Invoicing for Child & Parent Item Sales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform Invoicing for shippable Child & parent Item in the Configuration

M

M

11/19/2010 11/19/2010


Page 16

Functional Test Script Template Scenario 5.8: Sales orders with Customer Acceptance support for ATO and PTO Items


Automa ted Y/N?



DescriptionSales Order Issue from Avergae Org, Accept the full shipment for the Sales Order. Perform billing cycle for the sales order and 50% revenue recognition. Create RMA for Qty without credit memo for Asset Item and receive the RMA in Asset subinventory Sales Order Issue from Average Org, Perform pre billing cycle for the sales order. Create RMA for Qty with credit memo for Asset Item and receive the RMA in expense subinventory Sales Order Issue from Average and no customer invoice for sales order Sales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform Invoicing for shippable Child Item only item in the Configuration Sales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform Invoicing for shippable Child & parent Item inOracle Confidential - For internal use only

M

2 Sales Order Issue and Pre billing acceptance for the Sales Order

M

3 Sales Order Issue and No invoicing 4 Sales Order and full acceptance for SO ,Invoicing for shippable Child Item only 5 Sales Order and acceptance for SO ,Invoicing for Child & Parent Item11/19/2010 11/19/2010

L M

M

Page 17



Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is enabled from OM. Perform pick release and ship the sales order to customer. Customer accepts the full shipment and billing is doen for the sales order. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal the Configuration 6 Sales Order and acceptance for SO ,Invoicing for Parents Parent Item Sales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform Invoicing for shippable parents parent item in the Configuration Sales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform Post-billing cycle for the sales order and 70% revenue recognition. Create RMA for all Configured item defined in the BOM & receive the RMA in Asset subinventory Sales Order Issue from Standard Org, Accept the full shipment for the Sales Order. Perform billing cycle for the sales order and 70% revenue recognition. Create RMA for all Configured item defined in the BOM & receive the RMA in Asset subinventory Sales Order Issue from Standard Org & perform prebilling & Invoicing before shipmentOracle Confidential - For internal use only

M

7 Sales Order Issue and Full Acceptance for the SO & RMA for all Configured Item

H

8 Sales Order Issue and Full Acceptance for the SO & RMA for few Configured & All Mandatory Item

M

9 Sales Order Issue and Full Acceptance for the Non-Ship Model & Validate for the Transaction11/19/2010 11/19/2010

M

Page 18



Automa ted Y/N?

Description / Objective: Create sales order with order line for which customer acceptance is enabled from OM. Perform pick release and ship the sales order to customer. Customer accepts the full shipment and billing is doen for the sales order. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal 10 Validate the Create COGS Events Concurrent request Event Handling Delay the Launch of Create COGS Events Concurrent Request. For few minutes after executing Revenue Request.Validate on the how Event are Aggregated Delay the Launch of Cost Manager Concurrent Request. for few minutes after creating the COGS Recognition Evevts.Validate that there is interdependence L

11 Validate the Interdepence between the Cost Manager & COGS Recognition Concurrent Request

L

11/19/2010 11/19/2010


Page 19

Functional Test Script Template Scenario 5.9: Internal dropship sales orders without Customer Acceptance and with Customer Acceptance


Automa ted Y/N?

Description / Objective: Create internal dropship order with order line for which customer acceptance is not enabled/enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal with reference to customer facing operating unit.

Test Case1 Internal Dropship Sales Order Issue where shipping OU selling OU for Asset Item without Customer Acceptance 2 Internal Dropship Sales Order Issue where shipping OU selling OU for ATO Item without Customer Acceptance 3 Internal Dropship Sales Order Issue where shipping OU selling OU for Asset Item with Customer Acceptance 4 Internal Dropship Sales Order Issue where shipping OU selling OU for ATO Item with Customer Acceptance

DescriptionInternal Sales Order Issue with Asset Item from Standard Org where shipping OU selling OU, Full Revenue Recognition for the Sales Order Internal Sales Order Issue with ATO Item from Average Org where shipping OU selling OU, full acceptance Internal Sales Order Issue with Asset Item from Average Org where shipping OU selling OU, Full Revenue Recognition for the Sales Order and RMA for partial qty Internal Sales Order Issue with ATO Item from FIFO Org where shipping OU selling OU, Full acceptance for the Sales Order and RMA for partial qty and receive into expense subinventory Sales Order Issue ATO and PTO items from Standard Org and no customer invoice forOracle Confidential - For internal use only

H

H

H

H

5 Internal Dropship Sales Order Issue where shipping OU selling OU for11/19/2010 11/19/2010

H

Page 20

Functional Test Script Template Scenario 5.9: Internal dropship sales orders without Customer Acceptance and with Customer Acceptance


Automa ted Y/N?

Description / Objective: Create internal dropship order with order line for which customer acceptance is not enabled/enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal with reference to customer facing operating unit. ATO Item with Customer Acceptance sales order

11/19/2010 11/19/2010


Page 21

Functional Test Script Template Scenario 5.10: External dropship sales orders without Customer Acceptance and with Customer Acceptance


Automa ted Y/N?

Description / Objective: Create external dropship sales order with order line for which customer acceptance is not enabled/enabled from OM. Perform pick release and ship the sales order to customer. Perform revenue recognition for various percentage of value to ensure that the ratio is always maintained. Perform RMA receipt and create credit memo to ensure that the ratio between Deferred-to-Actual ratios for Revenue and COGS are always equal with reference to customer facing operating unit.

Test Case1 External dorpship Sales Order Issue where shipping OU is selling OU for Asset Item without Customer Acceptance 2 External dorpship Sales Order Issue where shipping OU is selling OU for ATO Item without Customer Acceptance 3 External dorpship Sales Order Issue where shipping OU selling OU for Asset Item with Customer Acceptance 4 External dorpship Sales Order Issue where shipping OU selling OU for ATO Item with Customer Acceptance 5 External Sales Order Issue with type (PROCURING) and No invoicing11/19/2010 11/19/2010

DescriptionExternal dropship Sales Order Issue with Asset Item from Standard Org where shipping OU is selling OU, partial Revenue Recognition for the Sales Order External dropship Sales Order Issue with ATO Item from Average Org where shipping OU is selling OU, partial Revenue Recognition for the Sales Order External dropship Sales Order Issue with Asset Item from FIFO Org where shipping OU selling OU, Full acceptance for the Sales Order External dropship Sales Order Issue with ATO Item from Average Org where shipping OU selling OU, Full acceptance for the Sales Order Sales Order Issue ATO and PTO items from Standard Org and no customer invoice for sales orderOracle Confidential - For internal use only

H

H

H

H

H

Page 22



Scenario 5.11: Verify the PAC accounting entries for sales orders without Customer Acceptance and with Customer Acceptance

Priority (H,M,L)

Effort Requi red to write detail test script (in days)

Effor t Requ ired to exec ute man ual test scrip t (in hour s)

Effort Require d to Record Automa ted Script (in days)

Automa ted Y/N?

Description / Objective: Verify the PAC Accounting entries for sales orders without Customer Acceptance and with Customer Acceptance for transactions performed in perpetual costing org

Test Case1 Sales Order Issue and 50% Revenue Recognition for the Sales Order without Customer Acceptance 2 Sales Order Issue and customer Billed for the Sales Order without Customer Acceptance 3 Sales Order Issue and Full acceptance for the Sales Order with Customer Acceptance 4 Sales Order Issue and Full acceptance for the Sales Order with Customer Acceptance 5 Internal Sales Order Issue where shipping OU selling OU for Asset Item without Customer Acceptance

DescriptionSales Order Issue from Standard Org, 50% Revenue Recognition for the Sales Order and RMA for Partial Qty with credit memo Sales Order Issue from Average Org, Customer Billed for the Sales Order and RMA for Partial Qty without credit memo Sales Order Issue from Standard Org, Accept the partial qty of the shipment. Create RMA for Partial Qty with credit memo and receive the RMA in expense subinventory Sales Order Issue from FIFO Org, Perform billing cycle for the sales order and revenue recognition. Accept the partial qty of the shipment. Internal Sales Order Issue with Asset Item from Standard Org where shipping OU selling OU, Full Revenue Recognition for the Sales OrderOracle Confidential - For internal use only

H

H

H

H

H

11/19/2010 11/19/2010

Page 23

Functional Test Script Template Scenario 5.11: Verify the PAC accounting entries for sales orders without Customer Acceptance and with Customer Acceptance


Automa ted Y/N?

Description / Objective: Verify the PAC Accounting entries for sales orders without Customer Acceptance and with Customer Acceptance for transactions performed in perpetual costing org

6 External dropship Sales Order Issue where shipping OU selling OU for Asset Item with Customer Acceptance 7 Period Close in PAC

External dropship Sales Order Issue with Asset Item from FIFO Org where shipping OU selling OU, Full acceptance for the Sales Order Perform a Period Close in PAC after closing the AR period.Validate the Pending Transactions

H

M

2.3

Process Flow [Optional]Use a flow diagram to illustrate the overall flow of the test script

11/19/2010 11/19/2010


Page 24



3

Dependencies/Requirements

3.1

Test Script LimitationsThe test script is intended to test the defer COGS feature from the costing perspective and ensure correct accounting entries are created for the transactions with OM order line for which customer acceptance is enabled and also for lines where customer acceptance is not enabled

3.2

Test Script Dependencies / AssumptionsTest Script has no dependency but the setup should be performed before performing the transactions

3.3

Default Setup [Optional]

Test EnvironmentDatabase: Base Release: XX Release: RDBMS Version: Jinitiator Version: Browser: Freeze Date:

Responsibilities[Click here and type the required responsibility to run the script]

Other Products[Click here and type the names of other products that need to be installed during testing]

11/19/2010 11/19/2010


Page 25



Profile OptionsFill in the table below with any necessary profile options setups Profile Site Level User

Operating Units[Click here and type the name of all the needed Operating Units to run this script]

Security Rules[Click here and type the name of the Security Rules]

Additional Test Data[Click here and type any additional test data or setup document names]

11/19/2010 11/19/2010


Page 26



44.14.1.1

Test Scenarios[Click here and type the name of the scenario][Click here and type the name of the Test Case]

Detail Description [Optional]Step No. Navigation Path Actions Data Field: Value(s) Expected Results / Check Points (Automation) Issues and Comments Pass/ Fail

Login: [Click here and type the user name /password] Resp: [Click here and type the responsibility] 10 20

11/19/2010 11/19/2010


Page 27



5

Summary of Results/Issues

This section is used for any problems or issue found during the testing. It may also include any bugs or enhancements that were logged and any comments on the functionality, ease of use, etc.

5.1

Issues Log

Test Case Reference

Issue Description

Resolution / Action

Status [Click here and type Open or Closed] [Click here and type Open or Closed]

Bug Number

11/19/2010 11/19/2010


Page 28



66.16.1.1

AppendixAppendix A - Test Script Review TemplatesOutline Review Template

Page No.1 2

Step No.

Issue DescriptionBryan: FIFO/LIFO, test a sales order issue that comes from multiple layers with different layer costs Bryan: 1. configurations where a shippable item is not invoicable, but its parent is. 2. configurations where a shippable child item is invoicable, as is the parent 3. configurations where the child is not invoicable, nor is the parent, but the parent's parent is invoicable 4. configurations where nothing is invoicable Bryan: RMAs for configurations - complicated for ATOs 1. need to test cases where we return the entire configured ("star") item 2. need to test cases where we return one component of the star item - one of the mandatory (bom) items in the configuration Bryan: Validate the Period Close in PAC

Action Taken (by QA)Incorporated New Test Case: 5.3.6 Incorporated Test Case: 5.7.4,5.7.5, 5.8.4,5.8.5,5.8.6 Incorporated New Test Case: 5.8.7,5.8.8 Incorporated in New Test Case: 5.11.7 Incorporated in New Test Case: 5.8.9,5.8.10, 5.8.11

StatusClosed Closed

3

Closed

4 5

Closed Closed

Bryan:1.Impact on Non-ship-model-complete shipments of included items in configurations - invoicing happens before shipment 2. Do not run the Create COGS Events concurrent request for a long time after the revenue events are created test how events are then aggregated. 3. Do not run the cost manager for a long time after creating COGS recognition events - this will test how independent the event creation is from the processing of the events.

6 7

Bryan: Deletion of partial acceptance (Customer Acceptance Tests) in Scenario 5.5 and 5.6 Bryan: Since acceptance project no longer has much of an impact on revenue / COGS matching avoid repeating in different Costing Method

Deletion done in 5.5. & 5.6 Variation in test case spread across the different costing method Incorporated in

Closed Closed

811/19/2010 11/19/2010

Bryan: Oracle Confidential - For internal use only

ClosedPage 29

Functional Test Script Templatea) backdate a revenue recognition event after other events have already been created ahead of it b) backdate an RMA after other events have already been created

45931928.doc Cost Management New Test Case: 5.6.4,5.6.5 Incorporated in New Test Case: 5.6.6 Closed

9

Bryan: Impact on keeping AR periods open in the past to examine how creation of backdated events affects future events

11/19/2010 11/19/2010


Page 30

Functional Test Script Template 6.1.2 Test Script Review Template (after first Draft)


Page No.1 2 3 4 5

Step No.

Issue Description

Action Taken (by QA)

Status[Click here and type Open or Closed]

11/19/2010 11/19/2010


Page 31

Functional Test Script Template 6.1.3 Test Script Review Template (after first Round Testing)


Page No.1 2 3 4 5

Step No.

Comments

Action Taken (by QA)

StatusClosed

11/19/2010 11/19/2010


Page 32

defer cogs

Documents