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.