Initiate Checkout Process
The Checkout page allows you to generate the appropriate transaction based on the items selected in your Shopping Cart. The following fields are displayed on the Checkout page.
The Code field determines the Transaction Code of the transaction to be generated by the Checkout process. The Code field initially defaults to the applicable Transaction Code based on the configuration done on the Shopper Configuration (SCNFG) page.
The Code pick list will not display Transaction Codes of the UR Transaction Sub Type if the ‘Shopper Transaction Control’ field is set to False on the Shopper Configuration page and vice-versa.
If 'Restrict RQ referencing MA' is set to True on the Shopper Configuration page then the system will not allow Requisition transactions to be created referencing a MA transaction in the 'Available from MA' and/or 'Available from Catalog' sections.
The Code pick list will not display Transaction Codes of the UR Transaction Sub Type if the ‘Shopper Transaction Control’ field is set to False on the Shopper Configuration page and vice-versa.
If Transaction Code is manually entered and the Transaction Code is inactive on the DCTRL page, the system issues an error message.
Code defaults to the default UR Transaction Code specified on the ‘Requisition Default Transaction Code’ field on the Shopper Configuration page.
If the contents of the shopping cart are from multiple Sources of Supply, or if they are all from the Similar Purchases tab or Commodities tab. In these situations, an error is issued if you enter a Transaction Code that is not of the UR Transaction Subtype.
If the contents of the shopping cart are from one vendor on the same Master Agreement or MA Catalog and the USE_DO_PRC_SHOPPER parameter on the Application Parameters page is set to DO, then Code defaults to the value specified in the Delivery Order Default field on the System Options page. You may select an alternate Transaction Code with a DO Sub-Type on Transaction Control (DCTRL). The pick list for the Code is automatically filtered to only display valid values.
If the contents of the shopping cart are from one vendor on the same Master Agreement or MA Catalog and the USE_DO_PRC_SHOPPER parameter on the Application Parameters page is set to PRC, then Code defaults to the value specified in the Payment Request Default field on the System Options page. You may select an alternate Transaction Code with a PRC Sub-Type on Transaction Control (DCTRL). The pick list for the Code is automatically filtered to only display valid values.
If the contents of the shopping cart are from one vendor on the same Master Agreement or MA Catalog and the USE_DO_PRC_SHOPPER parameter on the Application Parameters page is set to blank (that is, no value entered), then a value is not defaulted in the Code field. You must select a valid value from the pick list before selecting the Checkout button.
If the Commodity Lines in the Shopping Cart reference a Master Agreement, the pick list is filtered based on the allowable values for the MA on the Transaction Allowable Reference (DARF) page to ensure that the DO/PRC created is a valid transaction combination. If a user manually enters a value, then the system will issue an error if the Code is not valid for the MA on DARF.
The Department and Unit field default from the User (SCUSER) page in the CGI Advantage Administration Application. Department is a required field on the Checkout page. Unit is an optional field on the Checkout page.
Either the ID field must be populated or the Auto Numbering check box must be selected. If Auto Numbering is selected, then the Transaction Code must be valid on the Auto Numbering (ADNT) page for your Department for the current Fiscal Year.
The Shipping Location and the Billing Location are required fields. The fields default from the Procurement User (USER) page, but can be changed to other valid values as established on the Procurement Location (PLOC) page. The pick list only displays valid values on PLOC.
The Accounting Template and Accounting Profile default from the Procurement User (USER) page. Both fields are optional. Only one of these fields can be populated at a time.
The Delivery Date field is required and must be greater than or equal to the current system date.
The PCard ID field provides a pick list to the Procurement Card Administration (PRCUA) page. The PCard ID is an optional field on the Checkout page.
The PCard Expiration Date field is inferred from the PRCUA page based on the value in the PCard ID field.
The Group Purchases By field is used to determine how commodities are organized into UR Commodity Groups and, in turn, how they are grouped into the generated transactions. Valid values for this field are: Allow System to Choose Grouping and Group All PO Commodities Together.
The Requesting Unit is only displayed if an item in your Shopping Cart is associated with Inventory. This field can only be edited if the selected item is associated with Inventory, and is required if the selected item is associated with Inventory. This field allows you to specify the organizational unit that is requesting the stock items. The pick list only displays valid values from the Unit (UNIT) page, based on the current Fiscal Year and Department.
The Ship Whole Indicator is an optional check box field that is only displayed if at least one item in your Shopping Cart is associated with Inventory. Select this option if the request should only be released if all items requested have been reserved (that is, the Available Quantity is greater than or equal to the requested Quantity).
The Edit Shopping Cart button transitions you to the Shopping Cart page, which displays the items that were added to the Shopping Cart. The Shopping Cart page allows you to update specific information about the selected items and the purchase as a whole. Refer to the “Shopping Cart” topic for more information.
The Continue Shopping button transitions you to the Shopper (SHOP) page, which allows you to search for additional items that you want to purchase. Refer to page help for the “Shopper” page for more information.
If a Universal Requestor (UR) transaction is being generated, then all Commodities in your Shopping Cart must be established on the Universal Requestor Control (URCTRL) page for your Department. Departments use the Universal Requestor Control (URCTRL) page to identify the Dollar Threshold, Procurement Type, and Buyer associated with a commodity. Refer to the “Universal Requestor Setup” topic for more information.
The Checkout button initiates the process of transaction generation. Upon clicking the Checkout button, a pop-up confirmation window is displayed. Select Cancel if you do not want to initiate the checkout process; you will remain on the Checkout page. Select OK if you are ready to checkout. The system will create the appropriate transaction as specified by information in the Code/Dept/ID fields on the Checkout page, and you are transitioned to the created transaction. The Shopping Cart is cleared when the transaction is successfully generated.
Note: The system will issue an error, if the ‘Verify Check-Out’ flag is set to True on the Shopper Configuration (SCNFG) page and the user is trying to check out with a loose commodity and items on a Master Agreement (MA) together in the same cart.
When the Checkout process generates a UR, it incorporates all of the selected Commodity Lines from the Shopping Cart, as well as any Vendor Quotes that have been entered (regardless of whether they were added to the Shopping Cart) into the Commodity Comparison tab of the UR transaction. This allows you to retain historical documentation of vendor quotes.
When the Checkout process attempts to generate a transaction where the component line limit for the Transaction Type would be exceeded, then generation of that transaction will fail. When this happens for the Commodity Group or Commodity Line components, then some of the items in your Shopping Cart should be removed and re-selected after the Checkout process has completed for the current Shopping Cart. The alternative is to request a larger limit from the system administrator.
