Back
 

Oracle Order Management: Sales Order Using Cascading Order Header Information to Order Line in Oracle R12 Order Management – Part I

iWare Logic > Blog  > Oracle Order Management: Sales Order Using Cascading Order Header Information to Order Line in Oracle R12 Order Management – Part I

Oracle Order Management: Sales Order Using Cascading Order Header Information to Order Line in Oracle R12 Order Management – Part I

When a header attribute is updated and the lines are entered, any header changes are cascaded down to the lines. In the reconfiguration flow, the header information will be derived from the item instance that was selected, together with any Oracle Order Management defaulting rules. Because the header information defaults from the information available for the selected item instance in the installed base, there is a high possibility that the header information will need to be updated after the order is created and/or Booked For this reason, it is necessary to provide an option to cascade many of the changes to the order header to the respective fields on the order line of the order. The Cascading setup will not work if there is any Processing constraint is defined for restricting changes in Sales Order Header.Oracle has introduced new feature for cascading the Changes in Order Header information to Order Line.

This feature will bring following advantages:

  • Reduce Manual Work of updating multiple Lines
  • Increases productivity
  • Increases accuracy

The Following setup is required for using the Cascading Functionality:

  • Enable the cascading attributes by setting up the quick codes. This will allow you to define which attributes available for Cascade using this functionality.
    ** Please note that if the attributes are not enabled in Quick Code system will not Cascade the changes made at header level automatically to Sales Order Lines

Navigation:

Setup → Quick Codes → Order Management

Select Type = OM_HEADER_TO_LINE_CASCADE

Fig 1 - Order Management

 

Fig 2 - Order Management

In above case we have enabled Payment Term. This will cascade the changes in Payment Terms on Order Line. However the changes will not be cascaded for Sales Person as the Sales person attribute is not enabled.

In addition to Quick codes for using the cascading functionality we also need to set the new profile option in R12 OM: Sales Order Form: Cascade Header Changes to Line.

Oracle provides 3 values for the profile option:

  • Automatic
  • Manual
  • Ask Me

We’ll provide more details along with transactional effects in the next paper (Part 2).

Share