Searching

Once the given parameter is set to true, if a user navigates to the Transaction Catalog (DOCATLG) page via any navigation, the system loads the Transaction Catalog (DOCATLG) page as per the default Initial mode setup on the APGS (Initial mode setting or the Resource Targets' setup of the initial mode). Depending on the initial mode setup (Query/Browse) for the page, the user is required to enter search parameters to perform the search action, either upon landing on the page or when trying to perform the search with less than two filters as search criteria. If the user enters less than 2 criteria to perform the search action, the application displays a system feedback message to the user saying: "Transaction Code and one of the following search criteria must be entered: Transaction Dept, Transaction ID, Create User ID or Create Date.”, which indicates that the user has to provide values for at least 2 search parameters to perform the search action successfully. That is, Transaction Code and any other search field. Note: Application servers need to be bounced for parameter changes to take effect.

Some are listed separately or placed in the Primary Actions or Other Actions sub menus. There are instances where these actions will not appear because they are not valid for the state of the transaction (e.g. Submit will not appear for a transaction that is Final). There are other conditions in which these actions will not be allowed and an error message will be issued.

• Activate - Activates a transaction that was previously deactivated. Two activate options are available. One option allows the transaction to be reactivated immediately; the other option allows you to schedule the date and time for the transaction to be reactivated. Once activated, the restrictions put in place with the deactivation are lifted.

• Archive - Refer to the "Transaction Archiving" topic for more information on this complex action that is often tightly secured.

• Bypass Approval - Allows authorized users to skip the remainder of approvals required for a transaction. All edits are applied and the bypass action will be tracked in the Approval Log. Security to perform this action is rare.

• Copy – This action will transition you to the Copy Transaction page where the source transaction is identified in the Source Transaction section and you supply information to create the new transaction in the Target Transaction section. Finally, selecting the Copy Transaction action will attempt to create the new transaction.

• Copy Forward - Allows you to create a new transaction based on an existing transaction. This is different than the Copy action in that the source transaction has to be Final and the target transaction will contain some form of reference to the source transaction. The source and target transactions have to be defined as a valid copy forward for this action to complete.

• Deactivate - Deactivates a transaction so that modifications or cancellations are not allowed. Two deactivate options are available. One option allows the transaction to be deactivated immediately; the other option allows you to schedule the date and time for the transaction to be deactivated.

• Discard/Cancel – If the selected transaction instance is Draft, the system will discard (that is, delete) that draft after you confirm that is the action you intended to take. If the selected instance is Final, the system will create a Cancellation Draft, transitioning you to the Header of that cancellation where very few fields will be editable.

• Mark Hold - Indicates you do not want the transaction to be selected by batch processing.

• Mark Ready - Indicates you want the transaction to be selected by batch processing.

• Print - Prints the current version of the transaction using a pre-formatted form for the Transaction Type or Code.

• Schedule - Used to request system processing on a certain date that you define on the Transaction Schedule page.

• Submit - Applies the business rules to the current transaction version and attempts to commit all updates. For modified transactions, only lines that have been modified in the new version will be re-processed (for example, business rules re-applied).

• Validate - Applies the business rules to the current transaction version to verify whether or not the transaction will be accepted. It does not result in any updates. In the event that the transaction does not pass all the business rules, the transaction remains in a Draft phase, and displays the appropriate error messages.

• View PDF - Allows you to view a transaction in a pre-defined PDF format.

• Posting Line inquiry - This action transitions to the Posting Line Inquiry (PLINQ) to view all posting lines within the transaction in a single presentation. This is an alternative to viewing posting lines within the transaction where the presentation is for a single accounting line.

You must select the selection check box for more than one row in the grid to activate the Primary Actions and Other Actions available via the Grid Actions menu. If you only need to perform an action for only one transaction, then use the row-level menu. After selecting the selection check box for more than one row in the grid, you can select a valid action from the Grid Actions menu. The action will be applied to all selected transactions.  

Refer to the Row-level actions above for a description of each available action, and note that not all described above will appear because those actions that can only be taken against one transaction are hidden in the Grid Menu. One difference in actions is that Print in the Grid Menu is for a browser print and not to a defined form.