Every process type has a set of base transactions defined for it. A transaction is a logical unit of work that is necessary for performing activity within Sterling Selling and Fulfillment Foundation.
Base transactions are predefined transactions that contain information about how the transaction behaves, such as how many copies of a transaction can be kept in a process type and whether or not it can have configurable base pick and drop statuses. Base transactions can be used to create new transactions. These transactions can be changed within the limits defined in the base transaction.
To view the transaction details for a return receipt pipeline:
Field | Description |
---|---|
Change Receipt | This transaction represents any modifications that may be made to a return receipt. |
Close Pre-Receipt | This transaction represents the completion of the pre-receiving process. |
Inspect | This transaction represents the return receipt being manually inspected. |
Pre-Receive | This transaction represents the pre-receipt of a container. The contents of the container are not known by the system until the actual receipt is performed. |
Purge Receipt | This transaction represents the process of moving return receipts to the history tables. |
Purge Receipt History | This transaction represents the process of purging return receipts from the history tables and removing them from the system. |
Receipt Complete | This transaction represents the completion of a receipt. |
Receive | This transaction represents the process of receiving a return receipt. |
Start Receipt | This transaction indicates the start of the return receipt process. |
Unreceive | This transaction represents the reversal of any performed receipt. This is used to correct any receipt that may have been recorded incorrectly. |