1 copyright © 2013, oracle and/or its affiliates. all ... sig minutes/sig-cost... · solving...

Solving Create Accounting and Other Cost Issues Using the Revised Self-Service Cost Mgmt Diagnostics

Samir OthmanPrincipal Technical Support Engineer


Objectives

Will aid in Problem Avoidance

Self Service Resolution

Reduction in Resolution Time


AgendaCosting Diagnostics Overview

– Reasons For Usage– Basic Characteristics– Installation

List of Costing Diagnostics

How to run Diagnostics

– How to Search Effectively– Reports– E-Business Suite Diagnostics Benefit Recap– Additional References

Q&A


E-Business Suite Diagnostics OverviewE-Business Suite Diagnostics provide the ability to quickly identify and resolve issues by executing diagnostic tests

Oracle DiagnosticFramework

Executes

Diagnostic Tests

RE-Active

PRO Active


Reasons for Usage

E-Business Suite Diagnostics aid in:– Problem Avoidance

– resolving configuration and data issues that would cause processes to fail

– Self Service Resolution– resolving problems without the need to contact Oracle Support

– Reduction in Resolution Time– minimizing the time spent to resolve an issue by increasing

Support Engineer efficiency


Basic Characteristics

No updates, inserts, or deletes

Sensitive customer information is not collected or displayed

Security model restricts access to information based on the FND security model (role-based)

All published tests have successfully passed Oracle security review


Installation

Primary Delivery Method is through the Oracle E-Business Suite Diagnostics Release Update Pack (RUP)

Complete installation / execution instructions available in Doc ID: 167000.1 Oracle E-Business Suite Diagnostics

Tests are primarily written in Java, but XML tests are also available (delivered with a java wrapper for execution within the Oracle Diagnostic framework)

New/updated diagnostics will be available in the next RUP







Q&A



Diagnostics are broken down by the following Categories:Cost Check DiagnosticsUncosted Transactions DiagnosticsInventory/WIP DiagnosticsGL/SLA DiagnosticsCOGS/DCOGS DiagnosticsPAC Diagnostics


List of Costing DiagnosticsCost Check Diagnostic (NEW)1. Cost Check Diagnostic (NEW)

This Diagnostic Test is to generate a report useful for Troubleshooting purposes. It contains basic troubleshooting information that will help provide a baseline.

Same as CSTCHECK.SQL (see Doc ID 246467.1)Added Patchset Level Family Pack detailsAdded to the output report under section: "Organization Structure"

• Landed Cost Management (LCM) enabled• Oracle Process Manufacturing (OPM) enabled


List of Costing DiagnosticsCost Check Diagnostic (NEW)1. Cost Check Diagnostic (NEW)

Sample Output

File


List of Costing DiagnosticsUncosted Transactions Diagnostic

1. Cost processing errors for Inventory and WIP Transactions2. To Check Uncosted Transactions At Period End 3. Transaction Interface Managers (NEW)



1. Cost processing errors for Inventory and WIP TransactionsThis script will retrieve diagnostic information for resolving Inventory and WIP transactions that are marked as an error during Cost processing.

Inventory transactions in error would have costed_flag as 'E' in table mtl_material_transactions

WIP transactions would have process_status =3 in table wip_cost_txn_interface



1. Cost processing errors for Inventory and WIP Transactions

Sample Output

File



2. Check Uncosted Transactions At Period EndThis script will provide list of unprocessed/uncosted transactions for an organization to provide diagnostic information related to period closing issues.

Similar to BDEprdcls.sql Diagnostics Script (Doc ID 246467.1)Added uncosted transactions in CST_LC_ADJ_INTERFACE tableParameters:

• Organization ID- Required LOV • Period ID- Required LOV



2. Check Uncosted Transactions At Period End

Sample Output

File



3. Transaction Interface Managers (NEW)This diagnostic test checks current status and configuration of the 4 interface transaction

managers:1) Cost Manager2) Lot Move Transaction3) Material transaction4) Move transaction

and provides information of the related worker processes.Similar to Doc ID 310000.1 Oracle Cost Management Interface Managers Activity Test (For R11i)



3. Transaction Interface Managers (NEW)

Sample Output

File


List of Costing DiagnosticsInventory / WIP Diagnostics

1. Item Cost Transactions2. Inventory Backdated Transactions (NEW) 3. MMT CQL Quantity Mismatch Summary Report for items for input

Organization and Cost Group 4. MMT CQL Quantity Mismatch Details Report for items for input Organization

and Cost Group 5. Job/Work-Order definition and

transaction details6. Receiving Inspection Information 7. Inter Org Transfer



1. Item Cost TransactionsThis script will retrieve transactions information for input Organization and Item.

Similar to txn.sql (Doc ID 378348.1)Item Information was added to the OutputParameters:

• Organization ID - Required LOV• Item ID - Required LOV • From Date - Optional. Enter From Date in the format yyyy-mm-dd• To Date - Optional. Enter To Date in the format yyyy-mm-dd

Related Note: Doc ID 1222453.1 Diagnostic Training for Oracle Cost Management Costing Transactions Setup Test



1. Item Cost Transactions

Sample Output

File



2. Inventory Backdated Transactions (NEW)Identify Inventory Backdated Transactions for a particular account where there are

discrepancies between Inventory, SLA and GL. Oracle does allow backdating of transactions, although it can affect the balance when doing reconciliation. Reconciliation issues can be avoided when backdating transactions using the Cost Cut off field in the Organization Parameter form. This ensures that backdated transactions are costed in the correct sequence. (applicable to Avgcost Org.)Parameters:

• Organization ID - Required • Start Date – Required - Enter in the format yyyy-mm-dd• End Date – Required - Enter in the format yyyy-mm-ddSimilar to BdatedDiag.sql (Doc ID 1578694.1)



2. Inventory Backdated Transactions (NEW)

Sample Output

File



3. MMT CQL Quantity Mismatch Summary Report for items for input Organization and Cost Group

The script identifies all the items for which the total quantity calculated using the transaction table mtl_material_transactions does not match the quantity stored in the costing table cst_quantity_layers in an Average Cost Org..It returns all costing related data and optionally, all transaction and accounting related data for all such items in an organization.The quantity discrepancy is measured at a Cost Group level.

Parameters:

• Organization ID – Required - LOV

• Cost Group ID – Required - LOV



3. MMT CQL Quantity Mismatch Summary Report for items for input Organization and Cost Group

Sample Output

File



4. MMT CQL Quantity Mismatch Details Report for items for input Organization and Cost Group

The script identifies input items' details for which the total quantity calculated using the transaction table mtl_material_transactions does not match the quantity stored in the costing table cst_quantity_layers. It returns all costing related data and optionally, all transaction and accounting related data for all such items in an organization. The quantity discrepancy is measured at a cost group level.

Parameters:


• Cost Group ID – Required - LOV

• Item ID: Comma Separated Values - Required. Enter Items as Comma Separated Values



4. MMT CQL Quantity Mismatch Details Report for items for input Organization and Cost Group

Sample Output

File



5. Job/Work Order definition and transaction detailsThis script will show you for a For Discrete job / work order definition along with relevant

setup information. Gather details and costing information of a specific Job

Parameters:• Organization ID – Required - LOV• WIP Entity ID – Required – LOV

Similar to Job.sql (Doc ID 378348.1)



5. Job/Work Order definition and transaction details

Sample Output

File



6. Receiving Inspection Information

The script will retrieve diagnostic information related to Receiving Inspection.

Run this diagnostic to troubleshoot issues with Inter Organization transactions.

Parameters:


• Code Combination ID – Required - Enter Code

• Start Date- Optional. Enter date in the format yyyy-mm-dd

• End Date- Optional. Enter date in the format yyyy-mm-dd



6. Receiving Inspection Information

Sample Output

File



7. Inter Org Transfer This diagnostic test will collect setup and transactional data for a specific interorg

shipment.The data collected can aid in the resolution of issues involving interorg shipmentParameters:

Organization Id –Required- LOVShipment Number – Required- LOVShipment Line Number-Optional-LOVReceipt Number – Required- LOV

This script requires either the combination of Shipment Number and Organization Id or Receipt Number and Organization Id as mandatory parametersAlternatively all the parameters can be entered at the same time.



7. Inter Org Transfer

Sample Output

File


List of Costing DiagnosticsGL/SLA Diagnostics

1. Reconciliation Diagnostic (NEW)2. XLA GL Transfer Diagnostics3. XLA Event Class Setup Diagnostic4. Account Information (NEW)5. Transaction Inventory to GL Flow (NEW)6. SLA Unprocessed (NEW)



1. Reconciliation Diagnostic (NEW)Troubleshooting information for Reconciliation between INV-SLA-GL or differences in GL

and INV. Please run on a monthly basis.

(Doc ID 1447211.1) INV Period Close & INV-SLA-GL ReconciliationParameters:

• Organization ID – Required - LOV • Start Date – Required - Enter the Start Date in the format yyyy-mm-dd• End Date – Required -Enter the End Date in the format yyyy-mm-dd• Ledger ID – Required - LOV • Code Combination ID - Enter the Reference Account for which GL and Sub-Ledger

values are not matching. [See (Doc ID 400088.1) for Account ID]



1. Reconciliation Diagnostic (NEW)

Sample Output

File



2. XLA GL Transfer DiagnosticUse this diagnostic to find possible invalid data issues for subledger data transferred from SLA to GL. Error and warning messages, followed by suggested actions, identify possible problem areas.

Parameters:• Ledger ID – Required - LOV • Application ID – Required - LOV (Costing=707) • Je Source Name – Required - LOV (Cost Management) • Start Date – Required. Enter Start date in the format yyyy-mm-dd• End Date – Required. Enter End date in the format yyyy-mm-dd



2. XLA GL Transfer Diagnostic

Sample Output

File



3. XLA Event Class Setup DiagnosticThis test provides all the relevant setup for an Event Class. Show the relevant setup for an

Event Class.

Parameters:• Ledger ID – Required - LOV • Application ID – Required - LOV (Costing=707) • Event Class – Optional - LOV



3. XLA Event Class Setup Diagnostic

Sample Output

File



4. Account Information (NEW)This Diagnostic Test will provide the data flow from Inventory to General Ledger for a

specific Account_Id.Execute this test for issues where there are discrepancies between Inventory, SLA and GL.Parameters:

• Code Combination ID - Enter the Reference Account for which GL and Sub-Ledger values are not matching. [Review (Doc ID 400088.1) How To Determine The DISTRIBUTION_ACCOUNT_ID For Inventory]

Similar to Account_Info_Ext.sql (Doc ID 1578792.1)



4. Account Information (NEW)

Sample Output

File



5. Transaction Inventory To GL Flow (NEW)This Diagnostic Test will provide the data flow from Inventory to GL for a specific

transaction, the data flow from GL to Inventory for a specific batch id, and the data flow from Work in Process to GL for a specific transaction.Subledger Accounting Diagnostic Scripts for Cost Management.Parameters:

• MTL Transaction ID - LOV. Transaction ID can be obtained from Inventory > Transactions > query for the specific transaction and under Transaction ID tab, scroll to the right and find column named Transaction ID

• WIP Transaction ID - LOV. Please enter a WIP TRANSACTION_ID. This Transaction ID will only apply to the WIP output

Similar to InvSlaGl.sql (Doc ID 1372269.1)



5. Transaction Inventory To GL Flow (NEW)

Sample Output

File



6. SLA Unprocessed (NEW)This Diagnostic Test will collect the unprocessed records from Inventory/WIP/Receiving to

SLA for a specific Period / Ledger. When there are invalid records existing in the system, execute this diagnostic to understand the relevant events in errors and the error messages. Used in conjunction with the Subledger Period Close Exceptions Report.Parameters:

• Ledger ID – Required - LOV • Appl ID – Required - LOV (Costing=707) • Start Date – Required. Enter Start date in the format yyyy-mm-dd• End Date – Required. Enter End date in the format yyyy-mm-dd

Similar to SLA_UNPROCESSED_CST.SQL (Doc ID 1580316.1)



6. SLA Unprocessed (NEW)

Sample Output

File


List of Costing DiagnosticsCOGS/DCOGS Diagnostics

1. DCOGS Balance Diagnostic (NEW)2. COGS Diagnose (NEW)



1. DCOGS Balance Diagnostic (NEW)The Diagnostic Test will identify the Sales Orders which constitute the Deferred COGS

account balance.This Diagnostic Test should help to identify the various aspects of the Sales Order related transactions which causes DCOGS BalanceParameters:

• Organization ID – Required - LOV• Start Date – Required. Enter Start date in the format yyyy-mm-dd• End Date – Required. Enter End date in the format yyyy-mm-dd

Similar to DCOGSDiag.sql (Doc ID 1565831.1)



1. DCOGS Balance Diagnostic (NEW)

Sample Output

File



2. COGS Diagnose (NEW)Execute COGS Diagnose for any Sales Order you wish to troubleshoot. This Diagnostic Test returns rows for all tables related to COGS recognition from OM, AR, Inventory and Costing.Parameters:

• Sales Order Number – Required - LOV

Similar to COGSDIAG.sql (Doc ID 1307906.1)



2. COGS Diagnose (NEW)

Sample Output

File


List of Costing DiagnosticsPeriodic Average Costing (PAC) Diagnostics

1. Periodic Costing Setup Data2. PAC - inventory transaction and cost data for a given item, PAC cost group

and PAC cost type3. PAC data for a job


List of Costing DiagnosticsPAC Diagnostics

1. Periodic Costing Setup DataThis script will retrieve diagnostic information for resolving Periodic Costing setup related

issues

Parameters:

• None



1. Periodic Costing Setup Data

Sample Output

File



2. PAC – Inventory transaction and cost data for a given item, PAC cost group and PAC cost type

The script will retrieve diagnostic information related to the costing of transactions for a particular item in a given PAC setup. Parameters:

• Legal Entity ID – Required - LOV • Cost Type ID – Required - LOV • Cost Group ID – Required - LOV • Item ID – Required - LOV



2. PAC – Inventory transaction and cost data for a given item, PAC cost group and PAC cost type

Sample Output

File



3. PAC data for a job

The script will retrieve diagnostic information related to the costing of a WIP Job for a given PAC setup. Script requires as input - job, inventory organization of the job, cost group and cost type.

Parameters:• Legal Entity ID – Required - LOV • Cost Type ID – Required - LOV • Cost Group ID – Required - LOV • WIP Entity ID – Required - LOV



3. PAC data for a job

Sample Output

File







Q&A


How to run DiagnosticsTo execute the test, do the following:

Login to Oracle E-Business SuiteSelect Responsibility = ‘Application Diagnostics’ Select ‘Diagnose’Select Application Name = ‘Cost Management’ from the ‘Application’ list of values or Application Short Name = ‘CST’Scroll down to Diagnostic group ‘+xxx’Select test name = ExecuteInput Parameters:


How to Search EffectivelyExample:

Under support.oracle.com, “Advanced Search”Search in the Source: Knowledge Base, ..Search for word: (ex: CST_MATCH_DATE_PERIOD)

– Use Quotation mark(") to search for an exact phrase

– Use asterisk(*)wildcard to match one or more characters

Product = Oracle Cost Management (CST)Can also Refine Search by:

• Source

• Product category

• Feature

• Product Release

• Document Type

• Update Date


How to Search Effectively


Reports

Run “Period Close Pending Transactions Report in R12”

> This report will list all the items that prevent the period close

> Doc ID 1222123.1 Oracle Inventory Period Close Activity Test [VIDEO]

Run for “Period Close Reconciliation”

> Doc ID 1485361.1 Analyzing Discrepancies in the Period Close Reconciliation report

> Doc ID 1447211.1 A guide to Inventory Period Closing activities and Inventory-SLA-GL Reconciliation

> Doc ID 295182.1 Period Close Reconciliation Report (CSTRPCRE)


E-Business Suite Diagnostics Benefit Recap

Information in a test output helps to– Identify and solve potential issues before suffering their symptoms– Identify and solve existing issues without external assistance– Increase self-service efficiency by verifying / eliminating possible cause / solution of

an existing issue– Reduce time to resolution when a service request is required by increasing the

Support Engineer’s efficiency

Execution of E-Business Suite Diagnostics is easy because– Central location of all tests– No special technical knowledge required– No special SQL*Plus/operating system access required


E-Business Suite Diagnostics Benefit Recap

Document Title Document ID

R12 Oracle Cost Management Diagnostic Scripts within E-Business Suite Application

1271813.1

Diagnostic Training for Oracle Cost Management Costing Transactions Setup Test

1222453.1

Diagnostic Test Catalog for 12.1.3 1083807.1

How to resolve Costing Errors & Problems 865438.1

Cost Manager Frequently Asked Questions 117832.1

How to resolve Pending or Error Cost Manager or Cost Worker 748704.1

Costing Programs and related Files 1314276.1

Understanding Cost Manager 304313.1

Resolving Period Close Pending Transaction R12 1069492.1

Data Collection Scripts for Cost Management 378348.1

Info Center: Oracle Cost Management 1417659.2

Info Center: Oracle Manufacturing Period Close 1399895.2

Additional Resources


Live Demo


Questions & Answers


Learn More

About Oracle Support Best Practices www.oracle.com/goto/proactivesupport

Get Proactive in My Oracle Supporthttps://support. oracle.com | Doc ID: 432.1

Get Proactive Bloghttps://blogs.oracle.com/getproactive/

Twitter: Get Instant updates on#COSTMGT

Available References and Resources to Get Proactive


THANK YOU

1 copyright © 2013, oracle and/or its affiliates. all ... sig minutes/sig-cost... · solving...

Documents