MSC Sourcing Rule Assignment Upload creates, updates and deletes assignment sets and the sourcing rule assignments within them on the Oracle ASCP / APS planning server for a selected planning instance, from Excel – mirroring the Sourcing Assignments setup window.
When to use it
- You maintain sourcing rule assignments on the ASCP/APS planning server (not in the source EBS instance) and want to mass-load them.
- Create new assignment sets and populate them with many assignments at once.
- Bulk-update existing (non-collected) assignments – for example re-point them to a different sourcing rule.
- Bulk-delete assignments, or remove an entire assignment set.
- Assign across instance, item, category, organization, customer or region scopes in one spreadsheet.
- Migrate or replicate assignments across instances or environments.
Before you start
- Blitz Report is installed and you are signed in with access to the planning organizations.
- A planning instance is registered and its data (items, trading partners, regions, categories, sourcing rules) is collected to the planning server.
- The sourcing rules you assign exist on the planning server and are planning-active.
- For Category-level assignments, the MSC sourcing-rule category-set profile is configured.
Step 1 – Choose a mode, set the parameters and download
In Blitz Report, open MSC Sourcing Rule Assignment Upload, choose an Upload Mode, and set the parameters:
| Parameter | Purpose |
|---|---|
| Planning Instance | The ASCP/APS instance to read from and write to (required). |
| Master Organization Code | The item-master organization that drives selectable items (required). |
| Upload Mode | Create (new only) or Create, Update (download existing to edit/delete). Default is Create. |
| Include Collected Data | Whether collected assignments are shown (they are read-only). |
| Assignment Set / Type / Sourcing Rule / Organization / Category / Customer / Region filters | Restrict which existing assignments are downloaded. |
Run the upload to download and open the Excel file. Each set and assignment is automatically handled as a create or an update depending on whether it already exists.
Step 2 – Enter the assignments
On each row enter the Assignment Set, the Assignment Type (the level – instance, item, category, organization, customer or region), the target columns that level requires, and the Sourcing Rule Type and Sourcing Rule Name to assign.
Step 3 – Delete assignments or sets (optional)
Set the Delete Option column to “Assignment” to delete one assignment, or “Assignment Set” to delete the whole set and its assignments. Deletion requires Create, Update mode. Collected rows cannot be deleted here.
Step 4 – Validate and Save
Click Validate and Save. This checks for missing required values and runs the upload’s validation, then saves the file. Correct anything it flags before continuing.
Step 5 – Upload and view the result
Back in Blitz Report, click Upload and select your saved file. This submits the Blitz Upload request, which creates, updates or deletes each set and assignment on the planning server. When it finishes, a result report opens showing each row as success or error.
What’s produced
- Created, updated or deleted assignment sets and sourcing rule assignments on the planning server.
- A result report listing every row with a status (success or error) and a message.
Common questions
How is this different from the MRP Sourcing Rule Assignment Upload?
This one writes to the planning server (MSC/ASCP) tables for a chosen planning instance; the MRP one writes to the source EBS instance’s sourcing tables. Use MSC when your assignments live on the planning server.
Why can’t I change some rows?
Rows from collected assignment sets/assignments are read-only; maintain those in the source instance and re-collect.
How do I delete an assignment or a whole set?
Set the Delete Option column to “Assignment” or “Assignment Set”, and run in Create, Update mode.
How does it know whether to create or update?
It looks the set name and the full assignment key up on the planning server – found = update, not found = create.
Which columns are required for my assignment type?
The Assignment Type decides – item types need an Item, category types need a Category, region types need a zone or region, and some columns must be left blank for each type.
Troubleshooting
| Message | Cause | What to do |
|---|---|---|
| You can not update / delete existing Assignments in Create Mode | The row matches an existing assignment or is flagged for delete while in Create mode. | Re-download with Create, Update mode, or remove the existing/delete rows. |
| You can not update / delete a collected Assignment (or Set) | The row belongs to a collected (read-only) set/assignment. | Maintain collected data in the source instance and re-collect. |
| The Sourcing Rule Type is invalid for this Assignment Type | A bill of distribution or org-specific rule was used where the level requires a global rule. | Use a sourcing rule type/org that matches the assignment type. |
| Category level assignments are not permitted – profile not set | A category-type assignment was used but the category-set profile isn’t set. | Set the MSC sourcing-rule category-set profile and use that set. |
| Columns can not be specified for this assignment type | Columns populated that aren’t valid for the chosen assignment type. | Clear the columns that don’t apply to that type. |