R12 Internal Sales Order Cycle 1

R12 Internal Sales Order Cycle 1

IB Error -- Stale Data

Issue -- While Transferring the Item Instance from one account to another account , we received below error.

Error: Stale Data

The requested page contains stale data. This error could have been caused through the use of the browser's navigation buttons (the browser Back button, for example).

Cause:
The view object OwnerPartyAM.LocationRN542_LocationRN_oracle_apps_csi_instance_location_server_LocationAM.LocationPartySiteVO contained no record. The displayed records may have been deleted, or the current record for the view object may not have been properly initialized.

Solution -- Please apply the patch -- 19821318:R12.CSI.B  and test the issue in any teset instance and then move to PROD.

Generate COGS Recognition Events -- Error in CST_RevenueCogsMatch_PVT . Match_RevenueCOGS ( 50 )

Issue -- While Running "Generate COGS Recognition Events" , Program error outwith below error.

program_exception EXCEPTION IN Create_CogsRecognitionEvents
PROGRAM_EXCEPTION IN Match_RevenueCOGS at (50):
Failed to insert COGS Recognition Events into MMT due to a failed validation during bulk insertion.
Invalid item
Inventory item ID is invalid or does not have the flags enabled correctly to be processed by material processor
Error in CST_RevenueCogsMatch_PVT . Match_RevenueCOGS ( 50 )


Reason and solution.-- Few items are not defined as inventory items. ( In Our case Initially we defined item as Inventory item and created Sales Order and later user disabled the inventory flag. Due to this while running COGS Program we are getting below error ) . To find out the item details, Use below Query and enable  INVENTORY_ITEM_FLAG as 'Y" and then run "Generate COGS Recognition Events" Program.

SELECT organization_id,
MSI.SEGMENT1 ITEM_NUMBER,
MSI.DESCRIPTION,
MSI.INVENTORY_ITEM_FLAG
FROM apps.MTL_SYSTEM_ITEMS MSI
WHERE MSI.INVENTORY_ITEM_FLAG = 'N'
AND MSI.INVENTORY_ITEM_ID IN (SELECT CRTT.INVENTORY_ITEM_ID FROM apps.CST_REVENUE_COGS_MATCH_LINES CRTT
WHERE CRTT.INVENTORY_ITEM_ID = MSI.INVENTORY_ITEM_ID
AND CRTT.ORGANIZATION_ID = MSI.ORGANIZATION_ID
AND EXISTS (SELECT 1 FROM apps.cst_revenue_recognition_lines crrl
   WHERE crrl.revenue_om_line_id=crtt.revenue_om_line_id
    AND potentially_unmatched_flag IS NOT null)) ORDER BY MSI.SEGMENT1;

For more details, Please refer Metalink Note - 971355.1

Service Contract Not Imported From Sales Order

Issue -- Service contract Line is not created for one salesorder line.

Reason -- In My case user didnt populated Service Start date and End Dare @ Sales order line Level.

Solution -- Populate Servoice Start and End Dates and Reprocess the the record.

While searching for above issue,i came across below point from one of the blog.

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)