Customers may want to remove orders with COMPLETE or CANCELLED status to clean their FOM/OMLR environment (database). This article explains how to do that.
 

This KB deals about purging COMPLETED/CANCELLED orders

ALL

The only recommended way to purge orders in FOM4/OMLR5 is to use drop/truncate partition scripts. They are provided for:
 
1/Oracle database, under "$AF_HOME/db/oracle/purge" directory. Please refer to Partition_Truncate_Readme.txt file for more details.

2/PostgresSQL database, under "$AF_HOME/db/postgreSQL/purge" directory. Please refer to  Partition_Drop_Readme.txt file for more details.

Note that purging orders using the web service functionality is deprecated since FOM 3.0.0. 
See https://docs.tibco.com/pub/af/3.0.0/TIB_af_3.0.0_relnotes.pdf
==
Deprecated Features
• The purge web service and command line utility is deprecated in this release. The database purge was
further optimized and gives better results than the java purge. Dependency on TIBCO ActiveSpaces has
been removed. So data does not need to be removed from TIBCO ActiveSpaces. A plain database purge
will do.
===

Also purging orders through SQL(OMS_purge_orders.sh) is no longer supported starting from FOM 4.0.0 version. See to https://docs.tibco.com/pub/af/4.0.0/TIB_af_4.0.0_relnotes.pdf?id=1
===
● The purge script for Oracle EE database has been removed. To purge orders, use the provided
truncate partitioning script to truncate orders from all order related tables
===
 

FOM 3.0.0 releasenotes
FOM 4.0.0 releasenotes