Wednesday Mar 11, 2015

Webcast: Inventory Sales Order Flow and Troubleshooting – R12

Webcast_icon.jpgWebcast: Inventory Sales Order Flow and Troubleshooting – R12


Date: March 18th, 2015 at 11:00 am ET, 10:00 am CT, 9:00 am MT, 8:00 am PT, 5:00 pm CET, 9:30pm IST


This one-hour adviser webcast is recommended for Order Management and Inventory technical and functional Users. We will review the sales order data flow from Order Management into Inventory with focus on R12, for a Discrete Inventory Org (non WMS enabled). Will provide basic troubleshooting techniques for stuck sales order type transactions in the MTL_TRANSACTIONS_INTERFACE (MTI) and review some of the diagnostics used by Oracle Inventory Support to troubleshoot stuck sales order records during regular daily and monthly end business cycles.

Topics will include:

  • Overview
  • Process Flow
  • Troubleshooting
  • Demonstration
  • Diagnostics: Tools Available
  • References

REGISTER.jpg
Details & Registration: Doc ID 1290983.1

Wednesday Aug 27, 2014

How healthy is your Order Management data?

Ever wonder how healthy your Order Management data is?  The new Order Management Analyzer has been released to assist you with this area!!  The Order Management / Sales Order Entry Analyzer is a 'Health Check' script which you can proactively use at any time to review the data relating to Sales Orders, including :
  • Sales Order Headers and Lines
  • Workflow Issues
  • Drop / Ship Orders
  • Models and Kits
  • Sets
  • Shipping / Delivery Data

Each script used by this report looks for specific symptoms which have been known to cause problems in the past.  The script can either be run manually in SQL*Plus, or as a concurrent request.  The script may be run safely at any time.   No data is created, updated, or deleted by this script.

To download the script, go to R12: Order Management (ONT) Sales Order Analyzer Diagnostic Script, Doc ID 1665244.1.  To see what others are saying about the script or to add a comment/request on the script, go to its' community thread.  

Monday May 19, 2014

Troubleshooting iStore Order Placement

If you use iStore then you won't want to miss our latest Integration Troubleshooting note: Integration Troubleshooting : iStore to Order Management (Doc ID 1621430.2). 

iStore is used for the entering of Sales Orders of both standard and configurable items.  It integrates with Order Management, via the Order Capture APIs, to create, update, and process Sales Orders. 

The purpose of Doc ID 1621430.2 is to aid in the diagnosis and troubleshooting of issues in the integration flow between:

  • iStore
  • Order Capture APIs
  • Order Management.

The document includes information about the business flow, integrations, important tables and troubleshooting throughout the iStore business process. Where iStore integrates with other applications, links to the information centers for those other products are listed as well.

Take a look at Doc ID 1621430.2 and let us have some feedback on what you like and what can be improved!

Tuesday May 06, 2014

Configuration Validation Resulted In Error(s) While Booking

Ever wonder how to troubleshoot a configuration validation error when booking a sales order? 

The Configuration Validation Resulted In Error(s) typically occurs when Oracle Configurator is used in batch mode and batch validation is not able to make a valid database connection. 

Well, we now have a step by step approach document to troubleshoot the error. 

The document will walk you through the debug, what to look for and where to find the error code.  The document lists all returned error codes and their meanings.  It then steps you through additional verification of your environment and setups to help you locate the actual issue along with their known resolutions.

The master note is:
Configuration Validation Resulted In Error(s) While Booking, Doc ID 1584974.1

Take a look at this note the next time you run into this issue.  Or take a look at the note now, so you know what to do if the error occurs.



Thursday Aug 22, 2013

Why Doesn't My Sales Order Generate A Contract?

When a Sales Order is created in Order Management which includes a Service line, when the order is booked and shipped a Service Contract is created (or amended depending on the order).

In some cases, the service contract is not created.  In this blog post I try to give some pointers to help you debug this integration point.  Note that in R12 there was a change in how this integration point works, here I refer only to R12 functionality.  If you are on an earlier EBS release please see Doc ID 463912.1 for troubleshooting steps.

Is your order interfaced?

Make sure that your order has been successfully shipped and the line has been interfaced.  Sometimes the order can be deferred until a future date.  Check the OM workflow to see if that's happened.  You'll see the deferred date in the OM Order Line (OEOL) 'Fulfill' node.  If it's not deferred to a future date but is not closed, then running the Workflow Background Process is required to progress the workflow.

Is the instance created in IB?

Make sure that the install base instance has been created.  Search in IB using the sales order number and make sure that the item with the linked service line is created as an instance.
Remember that the inventory item must be set up with 'Track in Installed Base' and 'Service Allowed' set to yes (ticked) in the item master.

What's the status of the interfaced record?

When the sales order is processed, a record is created in the OKS_REPROCESSING table.  Check the status of the this record in Service Contracts > Reprocess Order.
Query using the sales order number. This should return the sales order with a status of NEW (if the record is available for processing) or ERROR (if the record has been processed but failed to create the service contract).
If the status is NEW then all you have to do is select it for processing and then submit the Service Contracts Order Processing concurrent program.
If the status is ERROR then the error message displayed should give you an indication of why the contract creation has failed.

If all fails and you can't find the order in the Reprocess Order form, the query below will return order numbers with service lines which have not created a contract and are not in OKS_REPROCESSING table.   
select ord.order_number "Order_Number",
ord.header_id "Order_Id",
line.line_number,
instance_number,
line.service_reference_type_code,
line.service_reference_line_id "Reference ID",
line_id "Service_Line_ID"
from csi_item_instances ib,
oe_order_lines_all line,
oe_order_headers_all ord
where not ib.last_oe_order_line_id is null
and ib.last_oe_order_line_id = line.service_reference_line_id
and ord.header_id = line.header_id
and line.flow_status_code = 'CLOSED'
and line.service_reference_type_code = 'ORDER'
and line.line_id not in
(select order_line_id from oks_reprocessing);
You can then use this information to implement a workaround such as creating the service contract manually OR you can log a service request with Oracle Support to get a datafix which will insert the missing order lines into OKS_REPROCESSING.

The following notes also have useful information about this integration point:
Integration Troubleshooting: Order Management to Service Contracts (Doc ID 1455545.1)
R12 How to Process Order Lines from Order Management to Create Service Contracts (Doc ID 785760.1)
About

Welcome to the EBS Support Blog where Oracle insiders share news and information about EBS products including new releases, tips and tricks, troubleshooting guides, upcoming webcasts and links to EBS Communities.

Stay Connected

Twitter

Search

Archives
« March 2015
SunMonTueWedThuFriSat
1
2
4
6
7
8
10
12
13
14
15
16
17
18
20
21
22
23
24
25
27
28
29
30
31
    
       
Today