Troubleshooting

This appendix covers the following topics:

Loading Data

The following table lists issues you might encounter while loading data and their solutions.

Problem Solution
You successfully uploaded an order forecast using supplydemand.dat, but you cannot view data in any Oracle Collaborative Planning screens. Run the Build Collaborative Planning Calendar concurrent program. Without this calendar file, uploads in weekly or monthly buckets fail.
You attempted to upload an order forecast using supplydemand.dat but received a Publisher is Not Valid error message. The system cannot find a match between the value for publisher and valid customer and supplier values. Verify that MSC:Operator Company Name matches the Publisher value. Verify that Customer Name in Oracle Order Management or Supplier Name in Oracle Purchasing matches the Publisher value.
You uploaded supplydemand.dat and received a Publisher Site is Not Valid error message. The system cannot find an exact match between the publisher site value and a valid inventory organization, customer site, or supplier site. Verify that Customer Site in Oracle Order Management or Supplier Site in Oracle Purchasing matches the value used for publisher site.
You uploaded supplydemand.dat with sync indicator D to delete records. The records still appear in the vertical view. For each record that you want to delete, you must provide: item, publisher, publisher site, supplier, supplier site (or customer, customer site for sales orders), and order type.
For purchase orders, sales orders and ASNs, you must also provide:
  • Order number

  • Release number

  • Key date

  • Line number

  • End order number

  • End order line number

You successfully uploaded supplydemand.dat with allocated onhand records. After uploading serialnumber.dat, you are unable to navigate to the serial number screen in Oracle Collaborative Planning. Your item must be serial-controlled. Verify that you have set the serial controlled flag to Yes in the item master.
Records uploaded using ExcelLoad.xlt does not spread out based on the bucket type and bucket end date. If the bucket type on the order is Day, the system creates a record for each day beginning on the start date and ending on the end date.

Vertical View

The following table lists issues you might encounter while using vertical view in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
You are unable to update the date or quantity for a record in the vertical view. You can only update a record in the vertical view if your company is the publisher of the record or if the publisher of the record provides you with update privileges. Update privileges are granted using security rules.
Your customer successfully published an order forecast but you are unable to view any records in Oracle Collaborative Planning. The system is unable to determine which company's user you are. The system administrator must run collections with the Enable User-Company Association parameter set to Yes.

Vendor Managed Inventory with Suppliers

The following table lists issues you might encounter while using supplier-facing vendor managed inventory in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
Purchase order releases were created in Oracle Purchasing for supplier-facing VMI items, but they do not appear on the Vendor Managed Inventory screen. Only Vendor Managed Inventory-enabled items appear in the Vendor Managed Inventory screen. Verify whether the item is Vendor Managed Inventory- enabled in the Approved Supplier List.
New purchase orders appear only after the collections program runs.
You set up a blanket purchase order for a Vendor Managed Inventory item but no purchase releases are created after you approved replenishments in the Vendor Managed Inventory screen. You must associate a planner with the Vendor Managed Inventory item. Define planners in Oracle Inventory.

Vendor Managed Inventory with Customers

The following table lists issues you might encounter while using customer-facing vendor managed inventory in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
The demand plan name for the customer-facing VMI did not show up in publish forecast to customer. Only the plans at the floor level will show up in the plan name while publishing an order forecast to customers.
The create or update request for a consumption advice throws an error. Set the Default Order Line Type same as the order type used in Assign line flows.
The collected ASN is not displayed on the Collection Workbench, but displayed in Collaborative Planning. The collected ASN is not displayed on Collection workbench.
Requests for create or update orders for customer-facing VMI throws an error without displaying any workflow error. The order type used in the consumption advice must be same as the order type associated to the customer site.
In-process quantity is not populated when a VMI item is auto released. When an unconsigned VMI item is auto released, the in-process quantity will be updated only if the sales order release for the item is successful.

Horizontal View

The following table lists issues you might encounter while using horizontal view in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
You set your preferences to display the Planned Supply/Planned Demand graph but are unable to view the graph in the horizontal view. To view a Purchase Order/Sales Order graph you must include the order types Purchase Order and Sales Order in your preference set.
Select the order forecast and supply commit order types for display.
The Horizontal View displays more records than the value set in the profile option FND: View Object Max Fetch Size. This happens only when the result set for the search criteria contains more records than the value you have set in the profile option FND: View Object Max Fetch Size. The system also displays a warning message that there are potentially more records in the result set and hence you should modify the search criteria.
Supplier items are not displayed for all suppliers in the Horizontal View. If a supplier item is associated to more than one suppliers, then the supplier item will be displayed only for the first supplier record.
Customer receiving calendar is not applied in the Horizontal View. APS is a single language product, which means it can work only in one language at any point of time. Therefore, if you run data collection in multiple languages for the same instance, the receiving calendar for the customers will not be applied in the Horizontal View as expected

Security Rules

The following table lists issues you might encounter while using security rules in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
You defined a group and its member companies. You also created a security rule that gives viewing privileges to members of the group. You are unable to view any records that group members should see in the vertical view. Your company must be included in a group even if you defined the group and its members. Add your company to the group using groupcompany.dat.

Exceptions

The following table lists issues you might encounter while using exceptions in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
You can view exceptions but are not receiving any notifications.
  1. You must be an item planner or listed as a site contact to receive exception notifications.

  2. Verify in the workflow mailer configuration file that the AUTOCLOSE_FYI parameter is set to No.

Supplier is getting an E-mail notification for the Supplier Supply Commit Exceeds Order Forecast exception. But the OEM organization is not receiving the E-mail notification. This issue may arise if the same planner creates more than one application usernames. Create different E-mail addresses for different usernames to solve this problem

Forecast Comparison

The following table lists issues you might encounter while using the forecast comparison program in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
Forecast comparison takes more than three minutes to query. This issue may arise if you have a large amount of data on your source system. Run Purge Collaborative Planning Historical Records program before using the Forecast Comparison program.
You can specify any of the following parameters while deleting the history table:
  1. From Date

  2. To Date

  3. Order type


Note that if you do not specify any parameter, the history table will be truncated.

XML Gateway

The following table lists issues you might encounter while using XML Gateway in Oracle Collaborative Planning. Solutions are also listed in the table.

Problem Solution
The XML Gateway execution engine fails to process XML messages. Review the error messages of the log file located ECX: Log File Path profile option. Review ECX_OBJECTS and verify that 000_sync_fore-cast_001.dtd is loaded. Review ECX_OBJECTS and verify that a map is loaded.