Default Release rule: Typically this is set for all the pause rule sets and since this

has the assign new

action, it should also have the highest priority.
Below rule should be configured in addition to default release rule. This rule is an example where
customer wants to pause the non-shippable lines until all the shippable lines in the order are shipped.
Send all the lines to invoicing together. This pause task is between Shipping and invoicing task.
Below rule should be configured in addition to default release rule. This rule is an example where
customer wants to pause the non-shippable lines until at least one of the shippable lines in the order is
shipped. Send all the non-shippable lines to invoicing as soon as the first shippable line is shipped. This
pause task is between Shipping and invoicing task.
Below rule should be configured in addition to default release rule. This rule is an example where
customer wants to send the group of shippable and non-shippable lines to invoicing together. Group is
identified by supplying same value in a specific EFF. In the example below assumption is that there is an
EFF context (FulfillLineContext1) and segment (FL1AttributeChar1) contains the value. This pause task is
between Shipping and invoicing task.
Below rule should be configured in addition to default release rule. This rule is an example where
customer wants to pause the non-shippable lines until all of the shippable lines in the orders are
received and delivered to inventory. Send all the lines to invoicing together. This pause task is between
Receiving and invoicing task.

Usercase below is to pause the lines for 90 days if an EFF date us not provided, if the EFF date is
provided then the line should be paused until that date. These 2 rules below are part of the pause
ruleset and in this case there is no default release rule as described in the examples above.
Assumption is that customer has configured and EFF Context(Quote) and segment (quoteexpiration) to
carry a date. Customer want to wait until this time if the value is supplied.
You have an orchestration process where you have tasks as below:

Task Type Task Name

1. Schedule Schedule
2. Reservation Reserve
3. Shipment Ship Goods
4. Pause Wait for delivery
5. Pause Wait for consolidated billing
6. Invoice Invoice
You want to wait until all the lines have been delivered before going to invoicing, and you want to send
all the lines to invoicing together. Here is the Pause you will configure for step 5 (Wait for consolidated
billing)
Usecase is you wanted to pause for something that is manually released or released via web service or
ESS then there is no need to have a condition nor a default release rule. Pause rule for the step 4 (Wait
for delivery) above. You would have only one rule and it would look like:

Below are the steps to find out the Context Code and Segment Code for EFF to be used in Pause rules:

Navigate to Manage Order Extensible Flexfields task in FSM

Search for the Appropriate Extensible flexfield. In this example we are looking at the
Fulfillment Line Information” Flexfields
Once you download the archive, you will get zip file. In the zip file you want to navigate to

Oracle\apps\scm\doo\processOrder\flex\<Flexname>ContextsB\View (In this example fulfillLine)

Locate the context you are interested in. It will be <EFFname><ContextNname>privateVO.xml (In this
example FulfillLineContext1privateVO.xml)

Open the xml file.

Search for “FND_ACFF_EFF_CONTEXT_CODE” This will give you the context code that you use in the
statement FLineEFF.context equals ignore case “FulfillLineContext1”.

Search for ViewAttribute tag, this gives you the segment name that you use in the statement

HeaderEFF.getFlexAttributeDateValue("_CompleteCompliancedate")

Or

FLineEFF. getFlexAttributeValue("_FL1AttributeChar1")