1. Scheduled Processes for SCM
  2. Publish Plan

Publish Plan

Use the Publish Plan process to integrate data from Supply Chain Planning to other Oracle or external applications.

When to Use

Use this process to export Demand Management, Demand and Supply Planning, Planning Central, Replenishment Planning, Sales and Operations Planning, or Supply Planning pivot-table data to a CSV file. The file is compressed, and the resulting ZIP file is uploaded to Oracle Web Center Content.

Privileges Required

  • Publish Plan Data (MSC_PUBLISH_PLAN_DATA_PRIV)

Specifications

Review these specifications before setting up this scheduled process:

Specification Description
Job Type

The recommendation is to schedule the run the process either as standalone job or as part of an integrated job set, but it can be submitted on a spontaneous basis if required.
Frequency

Frequency could be daily, weekly, or monthly depending on the data requirement of other Oracle or external applications.
Time of Day

The recommendation is to run the process after work hours, but it can be scheduled or submitted any time based on your requirements. It’s not recommended to run the process while the plan is running or when users are using the plan.
Duration

Duration depends on plan size and pivot-table definition, which includes number of measures, granularity of measures, aggregation levels, time range, level member filters, and measure filters. Expect the process to run for minutes, or for hours.
Compatibility

The recommendation is not to run multiple publish-plan processes simultaneously to avoid plan contention. The process will remain in a blocked status if there is another process running for the same plan.

Parameters

Parameter Optional or Required Description Parameter Value Special Combinations Required Notes
Plan Name Required

Select a plan name.

 Valid plan name None N/A
Append request number to output file name Optional

Select this check box to append the process request number to the name of the published file. This enables easy identification of the file on the content server. The resulting file name, plan-name_pivot-table-name_request-number, is also used as the document title.

If you don't select this check box, the document title for the published file on the content server is PUBLISHPLANDATA.

Check box selected

Check box not selected

 None N/A
Table Name Required

Select a plan's pivot table for which want to publish data. Tables that you have permission to access are enabled in the work area of the plan.

 Valid pivot-table name None N/A
Source System Required Select a source system. Valid source system None

N/A

Troubleshooting Information

  • You can view the status of the Publish Plan process on the Scheduled Processes work area.
  • After the program is submitted, you can cancel the process on the Scheduled Processes work area.
  • Refer to the log file attached to the Load Measures from Other Plans child process for details, which include warning and error messages.
  • To publish the pivot-table data (aggregation levels and measures) in a consistent column order, define the profile option MSC_PUBLISH_USES_TABLE_LAYOUT and set it to True at the site level.
    Note: The Publish Plan process publishes both aggregation levels and measures as columns in a pivot table .
  • The security scan that Oracle Content Server runs limits file size to 7.5 GB. Oracle Content Server recommends limiting the published CSV file size to approximately 1 GB, and the compressed file size to 800 MB.

    If the Publish Plan process fails and displays the error Content item (null) was not successfully checked in. Infected file found during virus scanning operation on Content Server, then you must define profile option MSC_PUBLISH_MULTIPLES_FILES and set the profile option value to True at the site level. This will publish the pivot-table data in multiple files, each with a file of size of approximately 1 GB.

  • Consider setting the USE_SCALED_QUERIES_PARALLEL profile option at the user level—for example, the name of the administrator submitting the job—to improve process performance. Select a number between 4 and 8 for the profile-option value. Increasing the number should improve process performance at the cost of consuming more system resources.
  • We do not recommend publishing measures whose source data is integrated with Supply Chain Planning from other Oracle or external applications. For example, Shipments History, Bookings History, Shipments History 1 Year Ago, Bookings History 1 Year Ago, Sales Orders, and so on.
  • If the reason for errors isn’t clear from the log or you need assistance with process performance, contact product support.

Related Topics