This hotfix can be downloaded from the TIBCO Support Web User Interface using your username and password for the TIBCO Support Web.
Once logged in, you can find the hotfix under the Downloads Menu: "AvailableDownloads/ActiveFulfillment/5.0.0/LR-Hotfix-001rev"

The zip files TIB_om-lr_5.0.0_HF-001*.zip include the Readme file (which is also available in the hotfix directory). 
Please unzip the relevant file and look for the Readme file for the instructions on how to apply the hotfix. 

================================================================================
Closed Issues in 5.0.0_HF-001 (This Release)

AF-10532
The Order Capture System component of Order Management - Long Running 5.0 did not 
filter based on the segment.

AF-10513
After integration with TIBCO Fulfillment Subscriber Inventory 2.0, order processing 
failed during plan generation. 

AF-10478
Null pointer was seen when user tried to submit planitem resolution option from 
Order Management Server UI.

AF-10436
If you canceled one of the order lines involved in an affinity,then affinity
plan items were re‐created.

AF-10432
After the second amendment, the REDO plan items were not triggered for the
completed plan items.

AF-10430
Automated Order Plan Development "generatePartialPlan" did not work in
TIBCO Order Management - Long Running 5.0.0

AF-10428
An order remained in the EXECUTION status even after you performed the SUSPEND
or RESUME action.

AF-10427
Sequencing did not work in REDO and COMPENSATE plan items of an amended plan.

AF-10422
REDO plan items were added incorrectly after the second amendment.

AF-10420
Unexpected REDO plan items were generated in the plan after you amended
a plan with affinity plan items.

AF-10419
The database columns for PLAN_ITEM.RETRYCOUNT and PLAN_FRAGMENT.RETRYCOUNT were
not being updated.

AF-10418
When executing SyncSubmitOrder over JMS, the Order Management - Long Running
responded with SubmitOrderResponse instead of SyncSubmitOrderResponse.
As part of this defect, OrderService wsdl and schema are changed.

AF-10417
The omsServer database connections were not exposed in the container
environment variable.

AF-10412
The dependency between the plan items was in wrong state after the second
amendment.

AF-10387
During Order Management Server failure, batches were not loaded into the
DEAD_LETTER table.

AF-10384
When the value of enableOfferValidation was set as true, an error occured in
processing the submit order request.

AF-10381
Product crosslink affinity and the ProductRequiredFor (PRF) relationships did not
work as expected. When multiple products with same plan fragment defined with affinity
and same action, got more than one plan items instead of single plan item.

AF-10380
"Retry OPD" failed if Order Management Server was failed at any time between
two retry attempts.

AF-10377
Even if there were no change in orderLine user‐defined field while amendment,
REDO PlanItems were created for that orderLine. 
A flag was provided to disable parent items dependency impact functionality.

AF-10376
When a missing planItem had a dependent parent planItem, amendment failed
with a null pointer exception.

AF-10375
After amendment, sequencing did not work in REDO plan items.

AF-8870
In the Order Capture System user interface, the Quantity field validation for
groups did not work as expected. 
For any selected quantity in the Quantity field, an error message was displayed and 
the order could not be placed.