1. Integration Playbooks for SCM
  2. Export to Microsoft Excel

Export to Microsoft Excel

You can use the Export action to extract data from Oracle Fusion Cloud Supply Chain Planning to Microsoft Excel for further analysis.

The information in these sections is applicable to UI pages in Oracle Supply Chain Planning.

Pivot Tables

Key Features

Exports data from an opened pivot table to a Microsoft Excel formatted file.

Best Practices

  • When exporting measure data for integration with other Oracle or external applications it's recommended to use the Publish Data or Export Data in Table Format integration options rather than using the Export action.
  • The Export action is best suited to exporting data from a pivot table, changing the data in Excel, and then importing the changes using the pivot table Import from File.

Constraints

The table must be opened in the UI before it can be exported.

Supplies and Demands

Key Features

  • Export the supplies and demands that meet the search criteria to a spreadsheet.
  • You can export the Supplies and Demands view either from the pegging tree table or a flat table (without pegging).
  • The tree-table pegging mode has two export options: Include All Child Rows and Include Child Rows if expanded.

Best Practices

To maximize performance:

  • The maximum row limit to export is defined by the profile option FND_EXPORT_ROWLIMIT. If the profile isn't defined, the default limit is 20,000 rows. This profile should not be set to more than 20,000 rows as this might compromise the health of the UI server. A limit of 5,000 rows helps to limit the export time to 2-3 minutes. This row count includes root and branches for a tree table, or all rows of a flat table.
  • Avoid using the Include All Child Rows export option on a large data set. This option includes all nested child rows even when they're not visible in the UI. In addition, the same row and all rows nested below it, might be repeated multiple times, resulting in a very large volume of data. Because you'll choose what to export by expanding pegged rows in the UI, use the Include Child Rows if expanded option to avoid this problem.
  • Use key columns such as item, organization, and order type in the search, and use enough criteria to keep batches below FND_EXPORT_ROWLIMIT.
  • Limit the number of columns in the layout to increase performance. It's recommended that you use less than 80 columns.
  • The Export to Excel action performs better when the notes column is hidden. If the notes column is visible, then the export process checks for the presence of notes on every exported row even though the content of the notes isn't exported.

Constraints

  • Downloads that take too much time might end abruptly, resulting in errors.
  • The maximum number of root nodes for a tree table is 500.

Replenishment Planning Tables

Key Features

The tables export information about:

  • Planning clusters.
  • Segment groups.
  • Segmentation results.
  • Policy assignment sets and policy parameters.

The Supplies and Demands best practices and constraints are also applicable to Replenishment Planning Tables.

Backlog and Analysis Tables

Key Features

You can use Oracle Application Development Framework (Oracle ADF) and custom export to export sales-order data from Backlog Analysis Tables to an Excel spreadsheet to view a detailed analysis.

The first and second export options in the list are standard Oracle ADF exports. The third and fourth export options are custom exports, where all lines of a set are exported even if only one or two lines of the set display on the Backlog Analysis page.

  • Export All
  • Export Selected
  • Export All plus Set Lines
  • Export Selected plus Set Lines

Best Practices

  • For a standard order, use the standard Oracle ADF export (first and second options in the list).
  • For set orders, use the third and fourth export options.

Constraints

You can't export more than 10,000 records in normal table mode.

Related Topics