Purge order details to an external system
Purge order details to an external system instead of history tables.
The current implementation of purge always moves data from transactional tables to history
tables. However, the process does not produce an output that can be used by other systems.
Therefore, a new user exit named YFSPurgeOrderToExternalDataStoreUE is added, which
takes in the order details XML as input and returns a document denoting whether the data was stored
to an external system or not.
To be able to purge order details to an external system, you must implement the
YFSPurgeOrderToExternalDataStoreUE user exit. The Purge Order agent constructs an
XML document that represents the records to be purged. The constructed XML document is then passed
to the user exit so that users can store the data according to their business requirements.
The purgeOrder API calls the
YFSPurgeOrderToExternalDataStoreUE user exit after the order details XML is
constructed. If the data is stored successfully in the external system, it is denoted by
<PurgeOrderToExternalDataStore PurgedOrderToExternal=‘Y’/> in the output. Then,
the data is deleted from the transactional tables in the database. If a different result is
returned, the records are not deleted from the transactional database and the purge does not take
place. If the user exit fails, the purge does not run. Also, if the user exit is not implemented,
the order details are purged to the history tables by default.
User Exit and Agent
To configure the user exit, go to and find
com.yantra.yfs.japi.ue.YFSPurgeOrderToExternalDataStoreUE in the user exit list.
For more information, see Defining user exits.
To configure the Purge Order transaction, go to . For more information, see Specifying a transaction as time-triggered.