What's New

Update 24B

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle Fusion Cloud SCM: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Configure Offerings.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Sales and Operations Planning

Sales and Operations Planning

Plan for Critical Components at Category Level

Subassembly items can be sold directly as finished goods in addition to being used as critical components of other final assembly bills. This duality of purpose can trigger independent and dependent demand for these items. Prior to this update, there was no way to aggregate supply plans for subassembly items modeled at the category level. However, with this new capability, you can specify subassemblies within a category-level assembly in the sales and operations bills of resources. This improves the aggregate planning of these items and addresses both their independent and dependent demands.

Use the Supply Chain Planning Bill Of Resources file-based data import (FBDI) template to load bills of resources for category-level assemblies. Subassembly items planned at a category level have their own bills of resources that must be loaded as category-level assembly items. The Catalog Name and Category Name columns are required when the Assembly Item Level is Category in the FBDI template.

Supply Chain Planning Bill of Resources FBDI Template

When used as a component in a category-level assembly, enter a concatenation of the Catalog Name and Category Name columns separated by a colon in the Component Item Name column. For example, the format would be Catalog Name:Category Name. Let’s say, for example, that the catalog name is RTSOP1_EX4CATALOG, and the subassembly category name is RTSOP1-SUBASSEMBLY. Then you’d specify RTSOP1_EX4CATALOG:RTSOP1-SUBASSEMBLY in the Component Item Name column.

Category-Level Subassembly Loaded as a Component in a Bill of Resources

In plan options, you need to select catalog categories in the Category Level Members field that include subassemblies modeled at the category level.

Category-Level Subassembly in Category-Level Members

After running the plan to refresh it with current data, you can define the Criteria for the Aggregate Build Plan table. In the Aggregate Build Plan tab, click the Criteria list and then click Manage. In the Manage Criteria dialog box, click Add and enter the values for the Name, Description, and Access fields. In the Details section, select Category and then select the Catalog and Category for the subassembly. Click Refresh Lists to list the components and resources used in the assembly of the selected category from the bill of resources. For example, RTSOP1-SUBASSEMBLY is the category-level subassembly. It has item-level components but could also include subassemblies modeled at a category level.

Category-Level Subassembly in an Aggregate Build Plan

In the Manage Criteria dialog box, click Add and enter the values for the Name, Description, and Access fields for the category-level parent assembly. In the Details section, select Category and then select the Catalog and Category for the assembly. Click Refresh Lists. You can include components and resources in the bills of resources for both the assembly and subassembly. For example, RTSOP1_EX4CATALOG:RTSOP1-SUBASSEMBLY is the component item name for the category-level subassembly in the RTSOP1-TABLETS category-level assembly. Components can be a combination of other subassemblies modeled at a category level or item-level components. If the assembly or subassembly had another category-level subassembly modeled as a component, then it would appear as RTSOP1_EX4CATALOG:Category Name of other subassembly. The bill of resources for the other subassembly would also need to be uploaded using the Supply Chain Planning Bill Of Resources FBDI template before running the plan and defining the Criteria in the Aggregate Build Plan table.

Category-Level Assembly and Subassembly in an Aggregate Build Plan

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• The Create Bills of Resources scheduled process doesn’t generate bills of resources for category-level subassemblies and assemblies. You must use the Supply Chain Planning Bill of Resources FBDI template to create bills of resources for category-level subassemblies and assemblies with category-level components.

• If you plan subassemblies at the category level, you must assign “make at” and “transfer from” sourcing rules at the category level in the plan’s assignment set.

• You can’t load category-level subassemblies as components in an item-level assembly.

• To transfer category-level subassemblies (and assemblies) from a source organization, you must define bills of resources in destination organizations to create aggregate items. For example, if the subassembly RTSOP1_EX4CATALOG:RTSOP1-SUBASSEMBLY is transferred from MFGE01 to MFGE02, you must load a corresponding record in the bill of resources for MFGE02.

Supply Chain Planning Bill of Resources FBDI Template

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

• Perform Order Orchestration and Planning Data Load (MSP_PERFORM_ORDER_ORCHESTRATION_AND_PLANNING_DATA_LOAD_PRIV)

This privilege was available prior to this update.

Copy a Measure Between Plans with Aggregated Customer Levels

In a previous update, you could create forecasts at aggregated levels of customer hierarchies, such as a geographical entity that aggregated all customer sites in a region. In this update, the functionality has been extended so that you can take advantage of existing functionality to move measure data between plans or from one measure to another within a plan. Using the Load Measures from Other Plans task, you can move measure data between plans that have aggregated customer levels or from a plan that isn’t aggregated to a plan that’s aggregated on a customer dimension.

Load Measures from Other Plans Page

The Load Measures from Other Plans task and Orchestrate Load Measures Processes scheduled process have been enhanced to support copying measure data between the following:

• From a demand plan without a planning level profile to a demand plan with a planning level profile.

• Within a demand plan with a planning level profile.

• From one demand plan with a planning level profile to another demand plan with the same planning level profile.

• From a sales and operations plan with the Use global demand option selected and Planning Customer Level set to Customer Site to a demand plan with a planning level profile.

• From a sales and operations plan with the Use global demand option not selected to a demand plan with a planning level profile.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Any existing demand plan with a planning level profile must be run after updating to 24B to utilize the plan with the enhanced Load Measures from Other Plans functionality.

You can’t use the Load Measures from Other Plans to copy measure data between the following:

• From a demand plan with a planning level profile to a demand plan without a planning level profile.

• From a demand plan with a planning level profile to a sales and operations plan.

• From a sales and operations plan with the Use global demand option selected and Planning Customer Level set to Zone to a demand plan with a planning level profile.

• From one demand plan with a planning level profile to another demand plan with a different planning level profile.

Key Resources

• Oracle Cloud Readiness > Sales and Operations Planning
  • Load Data from One Measure to Another Measure Across Plans (update 20A)
  • Schedule Batch Processes to Load Measures (update 20B)

• Oracle Cloud Readiness > Demand Management
  • Copy Measure Data Within a Plan (update 21A)
  • Plan at Flexible Levels for the Customer Dimension (update 24A)

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to the Load Measures from Other Plans task or the Orchestrate Load Measures Processes scheduled process will automatically be able to use this feature.

Users who are assigned a configured job role that contains this privilege can access this feature:

• Load Measure Data from Other Plans (MSC_LOAD_MEASURES_FROM_OTHER_PLANS_PRIV)

This privilege was available prior to this update.

Export Data in Planning Tables with Expanded Volume Limits

Export data from tables with as many as 1 million rows and 4,000 columns, subject to a maximum of 2 million cells. The Export Data in Format Specified in a Planning Table feature introduced in the 24A update is now enhanced to support increased volume limits. In addition, you can now export using either Microsoft Excel file format or CSV file format.

Export Data in Table Format Page

Previously, the Export Data in Table Format function supported exporting tables with up to 65,536 rows and 256 columns. These limits have been extended to 1 million rows and 4,000 columns with a maximum of 2 million cells. For example, you can now export a table with any of the following combinations (all of which equate to 2 million cells.)

• 1 million rows and 2 columns
• 500,000 rows and 4 columns
• 100,000 rows and 20 columns

This function has also been enhanced to support exporting in CSV (comma-separate values) format in addition to XLS (Microsoft Excel) format.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

Microsoft XLS format has a limit of 256 columns and 65,536 rows per sheet. When exporting in XLS format:

• The number of columns will be limited to 256.

• If the table selected for export has more than 65,536 rows (but less than 1 million rows), then the output will be split into multiple sheets within the same Excel workbook with each sheet having 65,536 rows or less.

• The resulting XLS file will include a macro that automatically runs the first time the file is opened. This macro will merge the multiple sheets into a single sheet and convert the file from an XLS format to an XLXS format.  Microsoft XLXS format has a limit of 1 million rows.

Key Resources

• Export Data in Format Specified in a Planning Table (update 24A)

Access Requirements

There are no new roles or security privileges needed to access this feature.

• Users who currently have access to open planning tables will automatically be able to use this feature.

Users who are assigned a configured job role that contains one or both of these privileges can access this feature:

• Maintain Planning Tables (MSC_MAINTAIN_PLANNING_TABLES_PRIV)
• View Planning Tables (MSC_VIEW_PLANNING_TABLES_PRIV)

These privileges were available prior to this update.

Secure Plan Data Considering Unassigned Entities

Secure plan data providing visibility to unassigned members at the lowest level of the hierarchy for the customers, suppliers, organizations, or products dimension. With this update, you can provide visibility to data that’s currently not applicable to a dimension. For example, by assigning a particular organization to a user, you can now provide visibility to measures that aren’t striped by organization, such as supplier capacity.

You can configure planning data security with an enhanced option to include unassigned members of the Product, Organization, Customer, and Supplier entities. Doing so allows you to access measures that don’t use a dimension’s hierarchy levels. For example, the Supplier Capacity Available measure includes the Product, Organization, Supplier, and Time dimensions. The measure is computed at the Item, Supplier-Supplier site, and Day levels of the Product, Supplier, and Time dimensions. Because the measure value isn’t specific to an Organization, the Organization level isn’t included in the measure’s computation. In such a scenario, you can set up a data access set to get access to specific organizations as well as measures that aren’t specific to an organization (such as Supplier Capacity Available).

The following are examples of Supply Planning measures that can now display values by configuring data security with the Organization entity that has the Include unassigned planning level member check box selected:

• Supplier Capacity Available
• Supplier Capacity Required
• Net Supplier Capacity Available
• Supplier Capacity Utilization Percentage
• Supplier Capacity Required by Supplier Capacity Constraint Date
• Additional Capacity Required by Supplier Capacity Constraint Date

Secure Plans Considering Unassigned Entities applies at the lowest level of the hierarchies for the Product, Organization, Customer, and Supplier dimensions. It is applicable to views displaying measures and planning analytics details for the Product, Organization, Customer, and Supplier dimensions in Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, Replenishment Planning, Global Order Promising, and Backlog Management.

The Administer Data Security view has been enhanced as follows:

• The data access set condition configuration has a new Include unassigned planning level member check box. You can select this check box only when the condition being created includes the Product, Organization, Customer, or Supplier entities at their lowest hierarchy level.

• You can select the Include unassigned planning level member check box along with other lowest-level members of the Product, Organization, Customer, and Supplier hierarchies.

Perform the following steps to secure plan data with unassigned members:

1. Select Product, Organization, Customer, or Supplier as an entity in a data access set.

2. Select the lowest level for Product, Organization, Customer, or Supplier.

Create a Data Access Set on the Administer Planning Security page

3. Select the Create action to create a condition for Condition Name and select the Include unassigned planning level member check box.

Create a Condition for an Organization Entity

4. Create a condition by providing a Condition Name and selecting the Include unassigned planning level member check box. Add other level members if required to configure the data condition.

New Include Unassigned Planning Level Member Check Box

5. Save the condition and assign it to the selected entity.

Assign the Condition to the Organization Entity

Let’s walk through some examples of Supplier Capacity measure details displayed when the Include unassigned planning level member check box is selected in the Supply Planning work area.

We will see how the data access set configured in the preceding screenshot is applied to the measure values in a table. The following pivot table shows Planned Orders measure values for organization-level members M1 and M2 and Supplier Capacity measure values for the unassigned organization-level member. The example shows a data security condition is created with organization-level members M1 and M2, and the Include unassigned planning level member check box is selected.

Pivot Table Created with Organization-Level Members

Let’s see what happens when we configure a data access set with the Include unassigned planning level member check box selected and with other lowest level members. Data security applies an In condition. In the following screenshot, a data security condition was created by selecting Include unassigned planning level member, M1, and M2 for an Organization. The condition applies data security for measures where the organization value can be unassigned, M1, or M2.

The pivot table shows values for Planned Orders and Supplier Capacity Available measures when the data security condition is configured with M1, M2, and unassigned organization-level members.

Data Security Condition for Organization-Level Members and Pivot Table Details

You can enable Include unassigned planning level member across multiple entities within a data access set. When enabled within a data access set, security is applied as an "AND" condition.

When Include unassigned planning level member is selected for an Organization and Customer entity, data security is applied and displayed for the measures when both Organization and Customer combinations are unassigned in a pivot table.

The pivot table shows values for user-defined measures with unassigned-level members for organization and customer entities.

Data Security Condition for Organization- and Customer-Level Members and Pivot Table Details

When you enable Include unassigned planning level member across data access sets, security is applied as a "OR" condition.

In the following example, enabling Include unassigned planning level member for Item in data access set1 and Organization entity in data access set 2, data security is applied and displayed for users for the measures when either Item or Organization have unassigned as lowest-level members in a pivot table.

The pivot table displays values for user-defined measures with unassigned level members for organization or customer entities.

Data Security Conditions for Data Sets and Pivot Table Details

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Oracle Global Order Promising respects data security for the Organization entity only.

• Customer and Supplier data security configurations are applied for planning analytics user interfaces like pivot tables or graphs in these work areas: Supply Planning, Demand Planning, Demand and Supply Planning, Sales and Operations Planning, and Replenishment Planning.

• You can’t enable Include unassigned planning level member for existing data conditions. You must create a new data condition to enable it.

• You can delete data conditions with Include unassigned planning level member using Manage Conditions only if the condition isn’t assigned to an entity across a data access set.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

• Administer Planning Security (MSC_ADMINISTER_PLANNING_SECURITY_PRIV)

This privilege was available prior to this update.

Use a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning

Use deep links to create more connected analytics and a seamless user experience between external applications and Oracle Fusion Cloud Supply Chain Planning. Deep links are a type of hyperlink used to open pages without using menus or navigating through a menu structure. With this update, you can easily navigate from an application, such as Oracle Fusion Analytics Warehouse, to specific pages in Oracle Supply Chain Planning. For example, you could create a deep link to navigate from Oracle Fusion Analytics Warehouse to the plans for an item in Oracle Supply Chain Planning.

This feature is supported for the following work areas: Supply Planning, Demand Management, Demand and Supply Planning, Replenishment Planning, and Sales and Operations Planning. With this feature, you can now navigate to the page layout and table or graph in the respective work areas. Additionally, you can navigate to the Exceptions or Supplies and Demand page.

The sample deep link URL for accessing this feature consists of three parts:

https://<host>/fscmUI/faces/deeplink?objType=<OBJECT_TYPE>&objKey=<Entity;Plan;FilterContext>

Base URL                                            Object Type Path                    Object Key Values

• Base URL: This part must include the host information with “/fscmUI/faces/deeplink?” appended after it; for example, https://<host>/fscmUI/faces/deeplink?

• Object type path: This part should have the work area name under objTypethat that you want to open. For example, if you want to open the Supply Planning work area, pass objType = “MSC_SP_WORKAREA”. This path is appended to the base URL and contains details about the work area you are creating the link to.

• Object key values: 
  • Entity: Pass the table or graph or layout option that you intend to open; for example, objkey=Entity=Material Plan or objkey=Entity=Forecast Graph or objkey=Entity=Plan Summary.
  • Plan name: Pass the plan name or plan ID of the Oracle Supply Chain Planning plan that you intend to open; for example, Plan=RTSP-Supply-Plan.
  • Filter context: The filter context contains details about the hierarchies, levels, and level members of the dimension in the table, graph, or hierarchies and level members details of the dimension in the table or graph. It allows you to filter data records based on the details of the dimension you choose to filter. This information is appended to a combination of a base URL and object type path; for example, hierarchy1=Enterprise;level1=Organization,member1=M1.                       

You can pass the object key values using the following parameters:

• Parameters: Pass the parameters under the object key values; for example, hierarchy1=Product;level1=Item,member1=Laptop_1GB or hierachy1=Product;levelmember1=512342

When using this feature to link an Oracle Analytics report from Oracle Fusion Analytics Warehouse, construct the URL using the reporting platform features that support tokens as follows:

• Token values: Pass the column name under the object key values; for example, hierarchy1=${keyValuesForColumn:Hierarchy};level1=${keyValuesForColumn:level};member1=${keyValuesForColumn:Prd_Member_Id}; or hierachy1=${keyValuesForColumn:Hierarchy;levelmember1=${keyValuesForColumn:Prd_lvl_Member_Id}

The ObjType parameters for the work areas are as follows:

• Demand Management                 MSC_DM_WORKAREA
• Supply Planning                           MSC_SP_WORKAREA
• Demand and Supply Planning     MSC_ISD_WORKAREA
• Replenishment Planning              MSC_REPL_WORKAREA
• Sales and Operations Planning   MSC_SOP_WORKAREA

For example, the following URL takes you to the Material Plan table in the Supply Planning work area from the Oracle Fusion Analytics Warehouse application.

With token values:

https://host/fscmUI/faces/deeplink?objType=MSC_SP_WORKAREA&objKey=entity=MaterialPlan;plan=${keyValuesForColumn:PLAN_ID};hierarchy1=${keyValuesForColumn:HIERARCHY_ID};levelMember1=${keyValuesForColumn:ORG_LVL_MEMBER_ID};hierarchy2=${keyValuesForColumn:HIERARCHY_ID};levelMember2=${keyValuesForColumn:PRD_LVL_MEMBER_ID};hierarchy3=${keyValuesForColumn:HIERARCHY_ID};levelMember3=${keyValuesForColumn:TIM_LVL_MEMBER_ID}

With parameters:

https://host/fscmUI/faces/deeplink?objType=MSC_SP_WORKAREA&objKey=entity=Material Plan;plan=RTSP-KB-SP-PL01;hierarchy1=SP_Catalog;level1=Item;member1=KB-CSP-ALLOY;hierarchy2=APS Calendar;level2=Week;member2=1/7/30;hierarchy3=Enterprise;level3=Organization;member3=M1

Additionally, it’s possible to pass the parameters of Member Id, Hierarchy Id, and Level Id details up to 5 parameters with names like member2, level2, hierarchy2, etc. All context details are appended with the AND clause. For example, if multiple Member Id, Level Id, and Hierarchy Id details are passed, then the filter context will be represented as (Member Id1, Level Id1, Hierarchy Id1) AND (Member Id2, Level Id2, Hierarchy Id2).

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

The Supplies and Demand page and the Exceptions page in their respective work areas support only the Item and Organization dimensions. However, it's important to note that this feature isn’t supported for Tiles and Tile sets within Graph sections.

If any of the parameters are missing or incorrectly passed, the following error is displayed.

Key Resources

• Watch the Use a Deep Link to Access Oracle Fusion Cloud Supply Chain Planning demo.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

• Monitor Demand Management Work Area (MSC_MONITOR_DEMAND_MANAGEMENT_WORK_AREA_PRIV)
• Monitor Demand and Supply Planning Work Area (MSC_MONITOR_DEMAND_AND_SUPPLY_PLANNING_WORK_AREA_PRIV)
• Monitor Replenishment Planning Work Area (MSC_MONITOR_REPLENISHMENT_PLANNING_WORK_AREA_PRIV)
• Monitor Sales and Operations Planning Work Area (MSC_MONITOR_SALES_AND_OPERATIONS_PLANNING_WORK_AREA_PRIV)
• Monitor Supply Planning Work Area (MSC_MONITOR_SUPPLY_PLANNING_WORK_AREA_PRIV)
• View Planning Tables (MSC_VIEW_PLANNING_TABLES_PRIV)

Users must have access to the individual pages and tables.

Selected Sales and Operations Planning Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Sales and Operations Planning works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Export Data in Format Specified in a Planning Table

In Update 24A, we introduced the Export Data in Format Specified in a Planning Table feature. This feature lets you export tables to Microsoft Excel while retaining the original table layout. With this feature, you can export tables that you weren’t previously able to open because they exceeded the 250,000 cell limitation. You can invoke this feature in the following ways:

• Use the Actions drop-down button in an open plan.
• Use the Actions menu on the Manage Plans page of the selected plan.
• Run the Export Data in Table Format scheduled process with a Plan and Table Name selected.

After this feature was introduced, we discovered that exporting tables with more than 2 million cells could cause an out-of-memory issue and, in some cases cause a server to stop functioning or operating correctly. To protect against this, we are introducing a limitation in Update 24B that will prevent the export of a table that contains more than 2 million cells. It’s possible that you successfully exported a table that exceeded this limitation in Update 24A. If so, this will no longer be possible in Update 24B and later releases.

Oracle reference: 36275383

Steps to Enable

You don't need to do anything to enable this feature.

IMPORTANT Actions and Considerations

Changes to File-Based Data Import (FBDI) Templates

Some Supply Chain Planning FBDI templates have changed in this update. For details of the specific changes, refer to the Instructions tab of these FBDI templates:

• Bill of Resources (ScpBillOfResourcesImportTemplate)

• Purchase Order Shipments Receipt History (ScpPurchaseOrderRcvHistoryImportTemplate)

You can find the latest templates in the Supply Chain Planning section of Oracle Fusion Cloud SCM: File-Based Data Import (FBDI) for SCM, available on the Oracle Help Center.