Cascade Headers to Lines
Cascade values from attributes on the order header to order lines.
Set the Cascade Order Header Values to Order Lines order management parameter to:
- All Lines. Cascade any modification that you make on the order header to all eligible order lines.
- Lines Not Overridden. Cascade values only to attributes that you haven't overridden on the order lines.
- Don’t Cascade. Don't cascade any value that you modify on the order header to any order line.
For background, see Manage Order Management Parameters.
Guidelines
Order Management defaults values when you create an order line. It cascades values only after you save the order.
default means Order Management copies the values for some attributes from the header to the line when you create the line, by default. It does this to reduce the amount of manual work that you have to do when you create an order line.
For example, Order Management defaults values for the Ship-To Address, Bill-To Address, Warehouse, and Shipping Method attributes from the header to the line. Order Management doesn't set default values on the line after you add the line.
cascade means you create a sales order, add a new order line, save the order, change a value on a header attribute, save again, then Order Management cascades that value.
For example, assume you set the warehouse to Seattle Manufacturing on the header and Order Management defaults it to all lines. Seattle has an emergency shutdown and you need to change it to Boston Manufacturing. Instead of manually updating each line, you change the warehouse on the header to Boston, save the order, and Order Management cascades Boston to each line.
overridden means you manually overrode a value on the order line. For example, Order Management defaulted a value from the order header when you created the line, and then you manually changed that value on the line.
Note
- Order Management cascades values that you modify on the header only after you save the order, modify a value on the header, then save the order.
- If you set the parameter to Lines Not Overridden, Order Management still considers the state of each, individual attribute. For example, if you override attribute x but don't override attribute y, Order Management will cascade x but not y. You can think of lines not overridden as actually meaning attributes not overridden.
- If the value for attribute x on the header doesn't match the value for attribute x on the line, then Order Management assumes you overrode attribute x on the line.
- Order Management cascades only to a line that's eligible. An eligible line is a line that Order Management hasn't already shipped, billed, closed, or cancelled.
- If you modify the value for attribute y on the header and then create a new line x, then Order Management will default the value for y onto x.
- If you modify an attribute on the order header and also modify the same attribute on the order line before you click Save, then Order Management will keep the value on the line and won't cascade.
- You might need to refresh the page to view the cascade results after you click Save.
- You can't cascade during import through REST API, FBDI, or web services.
Pairs of Attributes
Cascade maintains the relationship between these pairs of attributes:
- Warehouse and Shipping Method
- Warehouse and Subinventory
- Supplier and Supplier Site
- Bill-to Account and Bill-to Address
- Ship-to Customer and Ship-to Address
If you modify one of the attributes in a pair, then Order Management will cascade only to a line where it can maintain the relationship. Assume you set the parameter to All Lines and modify the supplier site on the header. Order Management will cascade the supplier site only to each line where the supplier on the line matches the supplier on the header.
Redesigned Pages and Classic Pages
You can cascade on redesigned pages or classic pages, but cascade on classic pages works only for the entire line. If you modify any attribute on the order line on a classic page, then Order Management assumes the entire line is overridden.
Assume you modify the warehouse on the order line on a classic page. If you need to update the shipment priority on the header, and if the shipment priority on line has the same value, then Order Management won’t cascade to the line. It assumes one of the attributes on the line is overridden, so it views the entire line as overridden. However, cascade on a redesigned page considers each individual attribute, not the entire line when it determines whether to cascade.
Use the examples in the rest of this topic to get a more grounded understanding of how cascade works.
Modify Attributes on the Order Header
Example 1
Assume you create a sales order, set the Shipment Priority attribute to High on the order header, click Save, then create these order lines:
Line | Status | Shipment Priority |
1 | Awaiting Shipping | High (cascade) |
2 | Awaiting Shipping | Medium (overridden) |
3 | Awaiting Billing | Low (overridden) |
4 | Closed | High (cascade) |
Assume you save the sales order, change the Shipment Priority from High to Low on the header, then click Save.
If you set the parameter to All Lines, your lines will have these values:
Line | Status | Shipment Priority | Description |
1 | Awaiting Shipping |
Low (cascade) High |
- |
2 | Awaiting Shipping |
Low (cascade) Medium |
You overrode the priority but Order Management cascades anyway because the parameter is All Lines. |
3 | Awaiting Billing | Low | This line isn't eligible to cascade because its status is Awaiting Billing, so it keeps its original value. |
4 | Closed | High | This line isn't eligible to cascade because its status is Closed, so it keeps its original value. |
Italics text means it’s the value that Order Management replaced when it cascaded the value from the header.
Example 2
Assume your order header has these values:
Shipment Priority | Shipping Method |
High | USPS Air |
You have these order lines:
Line | Shipment Priority | Shipping Method |
1 | High (cascade) | USPS Air (cascade) |
2 | Medium (overridden) | USPS Air (cascade) |
Assume you change these attributes on the order header and click Save:
- Change Shipment Priority from High to Low
- Change Shipping Method from USPS Air to USPS Ground
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Shipment Priority | Shipping Method | Description |
1 |
Low High |
USPS Ground (cascade) USPS Air |
You didn't override the priority or the method, so cascade both attributes. |
2 | Medium |
USPS Ground (cascade) USPS Air |
You overrode the priority, so no cascade. You didn't override the method, so cascade. |
Modify Request Types and Dates
Example 1
Assume your order header has these values:
Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date |
Ship On | 2/11/25 | 2/11/25 | 2/09/25 |
And you have these order lines:
Line | Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date | Description |
1 | Ship On | 2/09/25 (overridden) | 2/11/25 | 2/08/25 (overridden) | - |
2 | Arrive On (overridden) | 2/12/25 (overridden) | 2/13/25 (overridden) | Empty | Order Management automatically clears the Earliest Acceptable Date when you override the Request Type. |
You save the sales order, keep the dates on the header but change the Request Type from Ship On to Arrive On, then click Save.
If you set the parameter to All Lines, your order lines will have these values:
Line | Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date | Description |
L1 |
Arrive On (cascade) Ship On |
2/11/25 (cascade) 2/09/25 |
2/11/25 |
Empty 2/08/25 |
Order Management automatically clears the Earliest Acceptable Date when it cascades the Request Type. |
L2 | Arrive On |
2/11/25 (cascade) 2/12/25 |
2/11/25 (cascade) 2/13/25 |
Empty | You overrode the dates on the order lines, but you set the parameter to cascade all lines, so it removes your overrides and cascades the values. |
Example 2
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date | Description |
1 | Ship On |
2/09/25 (overridden) |
2/11/25 | 2/08/25 | The line has an override, so no cascade. |
2 | Arrive On |
2/12/25 (overridden) |
2/13/25 (overridden) |
Empty | The line has an override, so no cascade. |
Example 3
Assume your order header has these values:
Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date |
Ship On | 2/11/25 | 2/11/25 | 2/09/25 |
And you have these order lines:
Line | Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date | Description |
1 | Ship On | 2/09/25 (overridden) | 2/11/25 | 2/08/25 (overridden) | - |
2 | Arrive On (overridden) | 2/12/25 | 2/13/25 | Empty | Order Management automatically clears the Earliest Acceptable Date when you override the Request Type. |
You save the sales order, change the Request Date on the order header from 2/11/25 to 2/10/25, then click Save.
If you set the parameter to All Lines, your order lines will have these values:
Line | Request Type | Request Date | Latest Acceptable Date | Earliest Acceptable Date | Description |
1 | Ship On |
2/10/25 (cascade) 2/09/25 |
2/11/25 | 2/08/25 |
Order Management only cascades the date that you modify on the header, and only if the request type on the line matches the type on the header. If cascading the date attribute conflicts with another date attribute on the line, then Order Management will display an error when you click Submit. For example, when the cascade results in a latest acceptable date that happens before the earliest acceptable date. |
2 |
Ship On (cascade) Arrive On |
2/10/25 (cascade) 2/12/25 |
2/11/25 (cascade) 2/13/25 |
2/09/25 (cascade) Empty |
You changed only the date on the header, but the request type between the header and lines doesn't match, so Order Management cascades all date values from header to line. |
Modify Bill-to Account
Assume your order header has these values:
Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method |
Computer Service and Rentals | 1001 | 1001 - Site 1 | 1001 - Contact 1 | june_tsai@oracle.com |
And you have these order lines:
Line | Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method |
1 | Computer Service and Rentals | 1001 | 1001 - Site 2 (overridden) | 1001 - Contact 1 | june_tsai@oracle.com |
2 | FOM-Customer-001 | 2001 (overridden) | 2001 - Site 1 | 2001 - Contact 1 | li.yu@oracle.com |
You save the sales order and make these changes on the header:
Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method |
PennyPack Systems | 3001 | 3001 - Site 1 | 3001 - Contact 1 | diane.cho@oracle.com |
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method | Description |
1 |
PennyPack Systems(cascade) Computer Service and Rentals |
3001 (cascade) 1001 |
3001 - Site 1 (cascade) 1001 - Site 2 |
3001 - Contact 1 (cascade) 1001 - Contact 1 |
diane.cho@oracle.com june_tsai@oracle.com |
Order Management cascades values only to lines that have the same original value for the bill-to account on the header. |
2 | FOM-Customer-001 | 2001 | 2001 - Site 1 | 2001 - Contact 1 | li.yu@oracle.com | Order Management doesn't cascade values because the parameter is Lines Not Overridden lines and the accounts aren't the same on the header and line. |
Modify Bill-to Site
Assume your order header has these values:
Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method |
Computer Service and Rentals | 1001 | 1001 - Site 1 | 1001 - Contact 1 | june_tsai@oracle.com |
And you have these order lines:
Line | Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method |
1 | Computer Service and Rentals | 1001 | 1001 - Site 2 (overridden) | 1001 - Contact 1 | june_tsai@oracle.com |
2 | FOM-Customer-001 | 2001 (overridden) | 2001 - Site 1 | 2001 - Contact 1 | li.yu@oracle.com |
You save the sales order and change the Bill-to Address on the header to 1001 - Site 3.
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Bill-to Customer | Bill-to Account | Bill-to Address | Bill-to Contact | Bill-to Contact Method | Description |
1 | Computer Service and Rentals | 1001 | 1001 - Site 2 | 1001 - Contact 1 | june_tsai@oracle.com | Order Management doesn't cascade the bill-to site because the parameter is Lines Not Overridden and you overrode the address for the bill-to site. |
2 | FOM-Customer-001 | 2001 | 2001 - Site 1 | 2001 - Contact 1 | li.yu@oracle.com | Order Management doesn't cascade the Bill-to Site because the parameter is Lines Not Overridden and you overrode the bill-to account. |
Modify the Source
Order Management cascades values when the type of source on the header is the same as the type of source on the line. For example, if the source on the header is a:
- Warehouse. Order Management cascades the warehouse to all lines that also source from a warehouse.
- Supplier. Order Management cascades the supplier to all lines that also source from a supplier.
Assume your order header has these values:
Warehouse | Supplier | Supplier Site |
Seattle Manufacturing | Empty | Empty |
And you have these order lines:
Line | Warehouse | Supplier | Supplier Site |
1 | Seattle Manufacturing | Empty | Empty |
2 | Boston Manufacturing | Empty | Empty |
3 | Empty | My Supplier1 | My Supplier's Site |
4 | Empty | Empty | Empty |
You save the order, change the warehouse on the header to Denver Manufacturing, then save again.
If you set the parameter to All Lines, your order lines will have these values:
Line | Warehouse | Supplier | Supplier Site | Description |
1 |
Denver Manufacturing Seattle Manufacturing |
Empty | Empty | The source on the header is a warehouse, so Order Management cascades the warehouse to all lines that also source from a warehouse. |
2 |
Denver Manufacturing Boston Manufacturing |
Empty | Empty | Order Management cascades the value. You overrode the warehouse on the line but the parameter is All Lines. |
3 | Empty | My Supplier1 | My Supplier's Site | The parameter is All Lines, but the source on this line is a supplier which is different from the source on the header, so Order Management doesn't cascade to this line. |
4 |
Denver Manufacturing Empty |
Empty | Empty | Order Management assumes this line is overridden because the line's value for the warehouse doesn’t match the header, but it cascades anyway because the parameter is All Lines. |
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Warehouse | Supplier | Supplier Site | Description |
1 |
Denver Manufacturing Seattle Manufacturing |
Empty | Empty | - |
2 | Boston Manufacturing | Empty | Empty | Order Management doesn’t cascade because you overrode the warehouse on the line. |
3 | Empty | My Supplier1 | My Supplier's Site | - |
4 | Empty | Empty | Empty | Order Management assumes this line is overridden because the line's value for the warehouse doesn’t match the header. It doesn't cascade because the parameter is Lines Not Overridden. |
Modify the Type of Source
If you change the type of source on the header, then Order Management will cascade the change to all eligible lines regardless of the type of source on the line.
Assume your order header has these values:
Warehouse | Supplier | Supplier Site |
Seattle Manufacturing | Empty | Empty |
And you have these order lines:
Line | Warehouse | Supplier | Supplier Site |
1 | Seattle Manufacturing | Empty | Empty |
2 | Boston Manufacturing | Empty | Empty |
3 | Empty | My Supplier | My Supplier's Site |
4 | Empty | Empty | Empty |
You save the order, make these changes on the header, then save the order:
- Remove the warehouse.
- Set the Supplier attribute to Large and Associates.
If you set the parameter to All Lines, your order lines will have these values:
Line | Warehouse | Supplier | Supplier Site | Description |
1 |
Empty Seattle Manufacturing |
Large and Associates Empty |
Large and Associates Empty |
The type of source on the line doesn't match the source on the header, the parameter is All Lines, so Order Management cascades the value. |
2 |
Empty Boston Manufacturing |
Large and Associates Empty |
Large and Associates Empty |
- |
3 | Empty |
Large and Associates My Supplier |
Large and Associates My Supplier's Site |
The type of source on the line and header match, but the parameter is All Lines, so Order Management cascades the value. |
4 | Empty |
Large and Associates Empty |
Large and Associates Empty |
This line didn't have a source, the type of source on the line and header didn't match, so Order Management cascades the value. |
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Warehouse | Supplier | Supplier Site | Description |
1 |
Empty Seattle Manufacturing |
Large and Associates Empty |
Large and Associates Empty |
Some attributes are mutually exclusive. For example, you can specify the warehouse or the supplier, but not both. If you modify them, then cascade considers the attribute that you cleared when it determines an override. You cleared the warehouse on the header, so cascade compares the value in the warehouse attribute between the header and line to determine whether the line is overridden. The header and line both had Seattle Manufacturing before you cleared the value, so cascade assumes you didn't override this line and cascades the values. |
2 | Boston Manufacturing | Empty | Empty | If the line and header don't match, then Order Management assumes you overrode the value on the line. Parameter is Lines Not Overridden, so no cascade. |
3 | Empty | My Supplier | My Supplier's Site | Same as above. |
4 | Empty | Empty | Empty | Same as above. |
Modify Warehouse and Shipping Method
Order Management cascades the shipping method just like it does any other attribute. However, if it cascades the method but not the source, then it validates the method to make sure it's assigned to the source.
Assume your order header has these values:
Warehouse | Supplier | Supplier Site | Shipping Method |
Seattle Manufacturing | Empty | Empty | USPS Air |
And you have these order lines:
Line | Warehouse | Supplier | Supplier Site | Shipping Method |
1 | Seattle Manufacturing | Empty | Empty | USPS Air |
2 | Boston Manufacturing | Empty | Empty | USPS Air |
Assume you save the order, make these changes on the header, then save the order again:
- Change the warehouse to Denver Manufacturing.
- Change the shipping method to USPS Ground.
Note that Order Management validates the method on the header to make sure it's assigned to the source on the header.
If you set the parameter to Lines Not Overridden, your order lines will have these values:
Line | Warehouse | Supplier | Supplier Site | Shipping Method | Description |
1 |
Denver Manufacturing Seattle Manufacturing |
Empty | Empty |
USPS Ground USPS Air |
The type of source on the header and line match, and the method on the header and line match, so Order Management cascades the warehouse and the method. |
2 | Boston Manufacturing | Empty | Empty |
Empty USPS Air |
The value for the warehouse on the header and line don't match so Order Management assumes you overrode the line and doesn't cascade the warehouse. The shipping method on the header and line match, so Order cascades it, and then validates the method to make sure it's assigned to the source. If it isn't assigned, then Order Management removes the value from the Shipping Method attribute and leaves it empty. |