Skip to main content
Skip table of contents

Requisition Delete Transaction - PD

A user or approver can cancel an order at any point in time. Before the final approver, this results in a "Requisition Delete" transaction being sent to the client's ESM service. This transaction occurs when the user cancels the order at ESM before the final approval. If the user performs the final approval and the requisition becomes a Purchase Order, at the time the user cancels the order (which they still can), the transaction sent via ESM to the client's ESM Service is not a Requisition Delete transaction request; it is an Encumbrance Delete command, which cancels the Purchase Order rather than simply delete it as it would with a Requisition Delete transaction request.

The following is an example of a "Requisition Delete" transaction request.

This transaction request contains the same header fields that an Insert or Update transaction request would contain. However, it does not include any particular information other than the high-level information. This is because this is a Delete request.

If the transaction request validates successfully, the Purchase Request in the purchasing subsystem is purged completely from the tables. This includes all purchasing and encumbrance records associated with the transaction request. 

If the transaction is successful, the response is marked as "Success." There is no extra information returned in this response.

Although an error can occur during processing, it would be due to an error in the formatting or content of the transaction request since the only processing that occurs is the deleting of purchasing and encumbrance records. Once all updates take place and all approvals have occurred, the last approval on the ESM Easy Purchase side will result in a "Purchase Order Insert." This is also referred to as the "Encumbrance Insert" transaction since it inserts the necessary encumbrance records after converting the Purchase Request to a Purchase Order assigning it a PO Number. The following section discusses an example of a "Purchase Order Insert" transaction request.

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.