Header
The GR transaction only contains a Header tab. The Header tab includes basic information such as the type of request, request date, request status and Procurement ID. The specific type of request is defined by the Category and Sub Category fields selected on the transaction. These values can be used, if needed, to define workflow rules based on the type of request.
The GR Transaction Type does not belong to any Procurement State; however, it can be associated with a Procurement Folder. When the Procurement Folder fields are populated, the View Procurement Folder action on the GR transaction is activated. The View Procurement Folder action transitions you to the Procurement Management page to view other GR transactions processed for the selected folder. The GR transactions appear within the Related Transactions tab of the Procurement Management page.
Field InformationField Information
Fields that are not self-evident are detailed below. As many fields are open to general use, please consult any external documentation on the various uses for the transaction. Both the Transaction Control (DCTRL) and Procurement Transaction Control (PRDOC) can be used to make certain fields required. Configurable Validations can be used to make other fields required or conditionally required to capture the necessary information for request approval.
The transaction contains many generic fields (dates, amounts, numbers, and indications) that are initially hidden, with the intention of being made visible with an updated label as routing needs present. The same three reporting fields found on other procurement transactions are also available.
|
Field Name |
Description |
|
Requested Date |
This optional date functions much like the common Record Date, where it can be manually entered or will default to the Application Date when the transaction goes to final. |
|
Status |
This required field intended to capture information about the request: Approved, Rejected, and Pending Review. The field must be one of the first two values before it will successfully validate. |
|
Sub-Category |
As any field on the transaction can be used to trigger workflow, these are intended to differentiate one request from another by one or both classifications. |
The following field is conditionally required based on site specific setup on the Procurement Transaction Control (PRDOC) table:
-
Requestor ID
