Req Logic
Req Logic
User Guide
Created by:
Tectura Channel Products ReQlogic
333 Twin Dolphin Drive
Suite 750
Redwood City, CA 94065
Date:
3/22/2007
Document version: 1.00
All rights reserved. Tectura is a registered trademark owned by Tectura Corporation and registered in the
U.S. and several European and Asian jurisdictions. All company, brand, or product names are marks of their
respective holders.
The information contained herein is subject to change without notice. Tectura shall not be liable for technical
or editorial errors or omissions contained herein.
Page 2 of 172
Contents
1
Introduction ........................................................................................................................9
1.1
Logging in........................................................................................................................9
1.2
Homepage ......................................................................................................................11
1.3
Preferences....................................................................................................................12
ReQlogic Administrator...................................................................................................14
2.1
Page 3 of 172
2.1.9.1
PunchOut GL Codes...........................................................................................53
2.1.9.1.1 Adding PunchOut GL Codes...........................................................................53
2.1.9.1.2 Deleting PunchOut GL Codes.........................................................................53
2.1.9.2
GL Code Access .................................................................................................54
2.1.9.2.1 Adding GL Code Access .................................................................................54
2.1.9.2.2 Deleting GL Code Access Entries...................................................................55
2.1.10 Request For Quotes (RFQ) Supplier ......................................................................56
2.1.10.1
2.2
Customization ...............................................................................................................59
Administration...............................................................................................................69
Page 4 of 172
3.1
Requisition Routing.............................................................................................98
Requisition Follow-up.................................................................................................104
3.5
3.6
Reviewer .........................................................................................................................109
4.1
4.2
Reviewing a Requisition.............................................................................................109
Page 5 of 172
4.3
Approving a Requisition.............................................................................................112
4.5
4.6
4.7
Buyer ...............................................................................................................................116
5.1
Printing..............................................................................................................121
Emailing ............................................................................................................121
Transmit via cxml..............................................................................................122
Appending to an Existing PO............................................................................122
Fulfillment ....................................................................................................................123
Receiving ........................................................................................................................127
6.1
Typical User.................................................................................................................128
6.2
Expenses ........................................................................................................................131
7.1
Entering an Expense...................................................................................................131
Page 6 of 172
7.2
Creating/Accepting RFQ.............................................................................................146
8.2
Supplier Portal.............................................................................................................148
Budgets...........................................................................................................................150
9.1
Introduction .................................................................................................................150
9.2
Budget Sources...........................................................................................................150
Page 7 of 172
11.3.11
Page 8 of 172
1 Introduction
ReQlogic is the leading web-based procurement, requisitioning, expense processing, and workflow
application integrating seamlessly with each of the Microsoft Dynamics ERP products:
Microsoft Dynamics AX : Microsoft Dynamics GP : Microsoft Dynamics NAV : Microsoft Dynamics SL
ReQlogic automates purchasing and employee expense cycles, improving the efficiency and accuracy of the
transactions, driving down costs. Developed using the Microsoft .NET Framework, ReQlogic harnesses the
power of .NET and XML web services. With ReQlogics easy to use 100% browser interface and real-time
integration with Microsoft Dynamics, employees can submit and review requisitions any time, from anywhere.
1.1 Logging in
The ReQlogic login page may be accessed via any Internet Explorer (5.5 or higher) or Netscape (6.2 or
higher) browser. Users specify the application URL; enter their User Id and password, along with the
database to which they are seeking access.
Accounts are created in ReQlogic under Setup Tasks ! User Setup. Once a User Id has been established,
the user then can login to ReQlogic:
User Id: Initial access to ReQlogic via the ADMIN (no password). User Id allows full access rights to
all pages for the purpose of initializing setups and assigning access rights. Additional User Ids are
created in Setup Tasks ! User Setup.
Page 9 of 172
Password: Passwords are initially assigned to users in Setup Tasks ! User Setup. Once a User Id
has been established, users can reset their passwords via the Preferences button on their Home
Page.
NOTE: In the event that a user forgets his/her password, the link on the login page Forgot my
password allows users to enter their email address, click Submit, and receive an email notifying
them of their current password.
In the event that a user does not have an account and would like to request one, the link on the login
page I dont have an account displays a message that will explain to the user how to request an
account. The message displayed can be edited to your organizations preferences.
Page 10 of 172
1.2 Homepage
The ReQlogic Homepage displays the users most recent requisitions submitted, and if the user is a
Reviewer, a full listing of requisitions queued for approval. You can return to your Homepage at anytime by
clicking on the Home button in the upper right of your page.
The name of the page you are on is displayed under the ReQlogic logo at the upper left of the page. The
date, the name of the company that the user is currently logged into, and the users name displays in the
upper right corner. The display of the company name is especially useful when multiple companies can be
accessed.
The menu system is displayed as blue rectangles, each with its own list of options. Menus are fully
customizable using Administration ! Menu Administration. Access to the menu options are controlled by
using Administration ! Access Rights.
Page 11 of 172
1.3 Preferences
The user has the ability to view and configure certain fields related to their user in ReQlogic. The following
fields are configurable by the user: Email Address, Phone, Password, Delegate Id, Delegation Date Range,
Email Notifications and Language.
The Delegate Id and Delegation Date Range fields enable Reviewers who will be out of the office or
unavailable to delegate their approval authority another Reviewer. To delegate your approval, select another
Reviewer in the Delegate Id field, and define the Delegation Date Range. The dates selected in the
Delegation Date Range fields are inclusive for the period that you will be unavailable.
The Email Notifications checkboxes control the email notification triggers for the individual user. Email
messages will be sent to the user based on the following events.
a. Submit an email message will be sent to the user if the user is an reviewer or buyer.
b. PO Creation an email notification will be sent to the user when a Purchase Order has
been created from his or her requisition.
c.
Approval an email notification will be sent to the user when his or her document has been
fully approved.
d. Reject an email notification will be sent to the user when his or her document has been
rejected.
e. Receipt an email notification will be sent when a receipt has been issued against his or her
Purchase Order.
Page 12 of 172
f.
Voucher an email notification will be sent when a voucher has been created against his or
her Purchase Order.
g. Buyer Updates an email notification will be sent to the user when a buyer edits or deletes
a line on an approved requisition, or when a purchase order is manually changed within the
Microsoft Dynamics ERP product. Changes can be viewed using the Requisition Audit
Report.
Page 13 of 172
2 ReQlogic Administrator
This section describes the functions applicable to the set up and configuration of ReQlogic, which is typically
done using the Admin user Id.
Page 14 of 172
3. Catalogs: Determines where ReQlogic will obtain the list of Items that will be available to request for
purchase. There must be at least one catalog selected. Both catalogs can be selected. The
choices are
a. Inventory Select if using the Inventory Module in the Microsoft Dynamics product and
would like the Inventory items defined in the Inventory module to be available for purchase
requests in ReQlogic.
b. ReQlogic Select to activate the ReQlogic Catalog and would like the items defined in the
ReQlogic Catalog to be available for purchase requests in ReQlogic. The ReQlogic Catalog
can be populated manually or by importing items using the ReQlogic Utilities.
4. Buyer Id: Specify the default Buyer Id that ReQlogic will use where a buyer is not assigned. The
lookup will display all users who have been defined with a user type of buyer.
5. Buyer Assignment Source: Specify here how buyers can be assigned to requisitions outside of any
assignment defined through Routing Policies. Through the Buyer Assignment Source, buyers can be
assigned to users requisitions one of two ways.
a. User/Department ReQlogic will obtain the Buyer to assign to a requisition from the
requesters User Setup record. If the User Setup record does not have a default Buyer
assigned, ReQlogic will obtain the Buyer from the requesters Department Setup record. If
the Department Setup record does not have a default Buyer assigned, ReQlogic will obtain
the Buyer from General Settings.
b. Requisition Header User Fields Using the Customization module, you can use a user field
on the requisition header to store the Buyer that will be assigned to each requisition. You
can allow the requester to assign the Buyer manually in the user field, or you can use
custom business rules to default the Buyer in the requisition header user field.
NOTE: ReQlogic enables Buyers to be assigned to requisitions based on specific criteria
defined on individual Routing Policy steps. This means of assigning Buyers is very flexible and
can be used in conjunction with the Buyer Assignment Source on the General Settings page.
6. Buyer Queue-Buyers allowed to share queues: Check this box if buyers can view and process the
requisitions assigned to other buyers in the Buyer Review and Selection page. To view and process
the requisitions assigned to another buyer, the buyer would overwrite the default buyer Id with that of
another buyer.
7. Currency Id: Select the base currency of the database in which the default company is defined
(multicurrency implementations only).
Page 15 of 172
8. Rate Type: Select the default conversion rate defined in the Microsoft Dynamics product that
ReQlogic will use for multicurrency rate conversions.
9. Forward approved lines to buyer individually: Check this box if using Line Level Approval in
your routing policies and you want approved requisition lines to be sent to the buyer as soon as they
are done with their approval path, instead of waiting for all lines on the requisition to be completed
with their approval path. When this option is enabled, Re-routing and Re-calling are disabled.
10. Auto assign blanket requisitions: When checked, ReQlogic will automatically assign a requisition
line to a blanket requisition if the requisition line is for the same Item as the blanket requisition.
When unchecked, the requester must manually select the blanket requisition to which requisition
lines will be assigned.
11. Reminders (days in the review queue): Enter the number of days a reviewer is given to review a
requisition. If the requisition is not reviewed by the reviewer within the given time frame, ReQlogic
will send an email reminder to the reviewer and to the ReQlogic Admin user.
12. Budget Source: This field identifies the budget source of the Budget Control module. See the
Budget section for further explanation. (Microsoft Dynamics SL & Microsoft Dynamics GP only)
13. Over Budget Action: This field determines the action that ReQlogic takes when a submitted
transaction is over budget. The Over Budget Action does not apply to budgets setup and defined in
the ReQlogic Budget Setup, only to the budgets defined in the Microsoft Dynamics product.
(Microsoft Dynamics SL & Microsoft Dynamics GP only)
14. Item Defaults: The following fields will default the values defined when entering a new requisition
line or when creating a new ReQlogic Catalog item.
a. GL Account Enter the default inventory account that will default on the requisition line
entry. The account you enter here must exist in the Microsoft Dynamics product. The lookup
will display all valid accounts defined in the Microsoft Dynamics product.
b. GL Subaccount (Microsoft Dynamics SL only) Enter the inventory subaccount that will
default on the requisition line entry. The subaccount you enter here must exist in the
Microsoft Dynamics product. The lookup will display all valid subaccounts defined in the
Microsoft Dynamics product.
c.
Site Id Enter the Site Id that will default on the requisition line entry. The lookup will display
all valid sites from the Inventory module, if used. If the Inventory module is not used, all valid
sites from Setup Tasks ! Site Maintenance in ReQlogic will display (Microsoft Dynamics
SL only).
d. Purchase Type Enter the default Purchase Order Type to use when creating a requisition.
2005 Tectura Corporation
Page 16 of 172
e. PO Unit Enter the default unit of measure (each, case, bundle, etc.) that will default on the
requisition line entry.
15. Company (required): This setting is used to determine the default Company Id. The lookup will
display all valid companies setup in your Microsoft Dynamics ERP product.
16. Policy Id: Enter the default routing policy ReQlogic will assign to a requisition when a routing policy
is not assigned at the Department or User level. The policy entered here must be setup in Setup
Tasks ! Routing Policies. The lookup will display all valid policies available for selection.
17. Batch Prefix: Specify the prefix used for inventory fulfillment, receipt and expense batches
generated by ReQlogic. (Microsoft Dynamics GP only)
18. Inventory Fulfillment: The following choices are available for Inventory Fulfillment.
a. Last Batch Number For Microsoft Dynamics GP installations, you can specify the next
Inventory Fulfillment batch number to be used by ReQlogic. For Microsoft Dynamics SL
installations, ReQlogic will obtain the next inventory issues batch number to be used by
ReQlogic from Microsoft Dynamics SLs Inventory Setup. ReQlogic will add inventory
fulfillment transactions to the same batch until it has been posted/released, at which time a
new batch is automatically created according to the applicable numbering scheme.
b. Require fulfillment verification When this option is checked, inventory fulfillment
transactions will be submitted to a Physical Fulfillment queue before creating an inventory
transaction entry in the Microsoft Dynamics product. The Physical Fulfillment queue is
accessible from the Buyer Tasks menu and is intended for use by the user who will verify
the quantity to be fulfilled and generate the inventory transactions in the Microsoft Dynamics
product.
NOTE: In Microsoft Dynamics AX installations, inventory transactions are not created by
ReQlogic, the inventory fulfillment functionality is limited to updating the item status. .
19. Receipt Options: The following settings pertain to the On-line Receiving module, which enables
users to create receipts for items purchased.
a. Last Batch Number For Microsoft Dynamics GP installations, you can specify the next
receipt batch number to be used by ReQlogic. For Microsoft Dynamics SL installations,
ReQlogic will obtain the next receiving batch number to be used by ReQlogic from Microsoft
Dynamics SLs Inventory Setup.
b. One receipt per batch When this option is checked, ReQlogic will generate one receipt
per batch. If unchecked, ReQlogic will add receipts to the same batch until it has been
Page 17 of 172
Allowed over price variance (%) This is the percentage that a receipt price is allowed
over the price on the Purchase Order.
d. Allowed over receiving variance (%) This is the percentage that a receipt quantity is
allowed over the quantity on the Purchase Order.
20. Last Expense Batch: For Microsoft Dynamics GP installations, you can specify the next expense
batch number to be used by ReQlogic. For Microsoft Dynamics SL installations, ReQlogic obtains
the next receipt batch number to be used by ReQlogic from Microsoft Dynamics SLs Inventory
module.
21. Password Rules: You can define several rules that govern the use of ReQlogic user passwords:
a. Minimum length You can set a minimum length for user passwords.
b. Require alphanumeric mix You can require both alpha and numeric values for
passwords.
c.
Password expires in (days) You can set an expiration period after which password need
to be reset by the users.
d. Reject previously used passwords Prevents users from entering passwords in the
Preferences that they have previously used.
22. PO Number Source (Microsoft Dynamics AX): This option is valid for Microsoft Dynamics AX
installations only. The following choices are available:
a. Default ReQlogic will use the purchase order numbering sequence defined in Microsoft
Dynamics AX when creating Purchase Orders.
b. ReQlogic ReQlogic will use the purchase order numbering sequence defined using the
following corresponding fields PO Number Prefix and Last number fields.
23. Non-inventory item Id (Microsoft Dynamics AX and Microsoft Dynamics NAV only): Enter a
non-inventory Item Id, defined in the Microsoft Dynamics product, that will be used as the Item Id on
the Purchase Order for requisition line items not defined in the Microsoft Dynamics product (i.e.
Items defined in the ReQlogic Catalog).
24. Enable VAT/GST (Microsoft Dynamics NAV only): When checked, this option enables ReQlogic to
calculate and display VAT/GST tax on requisitions.
25. Enable FBT (Microsoft Dynamics NAV only): When checked, this option enables ReQlogic to
calculate and display FBT tax on expenses.
2005 Tectura Corporation
Page 18 of 172
26. Distribution Option (Microsoft Dynamics GP only): This field determines which financial
distribution option is being used, if any:
a. none No distribution option is being used.
b. GL Distribution Distribute a requisition line amount over a number of GL Codes. ReQlogic
uses the account distribution to create the proper distribution on receipts for requisitions, and
on AP vouchers for expense reports.
c.
27. Analytical code validation (Microsoft Dynamics GP only): Determines whether Analytical
Accounting codes are validated as each requisition is saved or if validation is delayed until the
requisition is approved and in the buyer queue.
a. Validate in Buyer Queue
b. Validate during entry
28. Email Configurations: Use the following fields to set email.
a. SMTP Server Enter the mail server ReQlogic will use to send email messages. If left blank
ReQlogic will use the SMTP Service, if enabled, on the IIS Server to send email messages.
b. Email from Address Enter the email address where all ReQlogic email messages will be
sent from.
c.
Send test email to Enter a valid email address to test the ReQlogic mail functionality. You
cannot be in Edit mode to send a test email.
29. Administration Reports: These reports can be used by system administrators to keep track of
important system settings. Each of these reports can be displayed in PDF, Word or Excel.
a. Access Rights This report lists the access rights for all users in ReQlogic. This report is
accessible from both Administration ! Access Rights and Setup Tasks ! General
Settings.
b. Department/Users This report lists departments and the users assigned to the
department. This report is accessible from both Setup Tasks ! Department Setup and
Setup Tasks ! General Settings.
c.
Failed Login Attempts This report documents all failed login attempts. This report is a
requirement of Sarbanes Oxley.
Page 19 of 172
30. Re-routing triggered when the following fields are modified: This option works in conjunction
with the re-routing functionality defined in the routing policy. When re-routing is turned ON, this
option allows you to control which field modifications will trigger re-routing. Select the fields that when
edited by a reviewer will trigger the routing policy to re-route. Refer to the Routing Policy section for
more information about re-routing.
NOTE 1: The rejection of a requisition line will trigger re-routing only when the option Any
Field is selected and the re-routing functionality is turned on. A rejection of a requisition line is
considered a modification.
NOTE 2: The Line Total % is used to enter the desired minimum percent change in a line total
that will require a requisition to be re-routed. Zero indicates any change in the line total will require
re-routing.
Page 20 of 172
Page 21 of 172
7. Buyer Id: Enter the buyer for the department. The lookup will display all users that have been
defined with the user type of Buyer in User Setup. If a default buyer has been defined in the General
Settings, that buyer will be displayed in red to the right of the Buyer Id field. If a buyer is not assigned
to the department, the default buyer defined in General Settings, appearing to the right of the field,
will be used.
8. Addl. Reviewer (2)-(6): You can define additional reviewers for this department. Additional reviewers
defined for the department can be used in the Routing Policies as reviewers. This will give you more
flexibility in defining your routing policies.
HINT: The Addl. Reviewer fields are the only fields that do not roll down to members in the
department.
9. Default values from business rules overwrite user entries in: ReQlogic uses business rules
defined in the Microsoft Dynamics product to default values to certain fields on requisitions. For
example, when an Item Id is selected on a requisition, the following fields, if defined, will potentially
default automatically: Description, Vendor, Account, Site, Price, Unit and Dimensions. If a user is
authorized to enter a value in any of those fields, he or she can overwrite the default. If the user then
changes the Item Id to a different Item, ReQlogic will attempt to replace the values already entered
with the defaults of the new item. In certain situations, the user might not want ReQlogic to overwrite
or re-default values in certain fields. This option allows you to uncheck the fields that you do not
want ReQlogic to overwrite if a value has been entered. If the field is blank, defaulting will occur.
NOTE: ReQlogic uses the Default Values from business rules settings from the User Setup, not the
Department Setup settings. These settings are on the Department Setup record so they can be
defaulted to members of the department.
10. Save/Cancel: Click Save to save the department setup. Click Cancel to discard the creation of the
department.
or arrow keys
2. Click the Edit button. The edit button must be selected in order to edit a department in Department
Setup. When clicked, it will enable the Save, Delete, and Cancel buttons. It will also enable lookup
functionality on the fields where applicable.
3. Select Delete to delete the entire department record. ReQlogic will not allow a department to be
deleted if any users are assigned to the department.
Page 22 of 172
HINT: Consideration should be given to coordinating the ReQlogic User Ids with Network User
Ids and User Ids from the Microsoft Dynamics product. Coordination with Network User Ids enables
Windows Authentication Integration functionality. Coordination with the Microsoft Dynamics product
2005 Tectura Corporation
Page 23 of 172
User Ids allow, for example, requisitions to be routed to Project Managers and for Buyer Ids to flow
over to the purchase order from ReQlogic.
3. User Name (required): Enter the name that is associated with the User Id.
4. Department Id (required): Specify the department to which the user belongs. The lookup will display
all valid departments that are set up in Setup Tasks ! Department Setup in ReQlogic.
5. Language Id (required): Use the drop-down list to specify the language the user will be using. If a
default language was defined in General Settings or in the Department the user is assigned to, that
language will default.
6. Password: To enter or change the password for the user, click on the Update Password checkbox.
You will be prompted to enter and confirm the password.
7. Status: Set the status of the user. If the checkbox is marked, the user is Active. This means the user
can login and use ReQlogic. The User Id will also be available in the lookups for User Ids. If the
checkbox is unmarked, the user is Inactive. This means the user will not be able to login to ReQlogic
and will not be displayed in the lookups for User Ids. When a user is marked as inactive, it also
means the user will not be counted against the user license count.
8. Network Login Id: This field maps the ReQlogic login Id to a domain/network login Id. This is used
for Windows Authentication integration when the ReQlogic User Id is different from the users
Network Login Id.
9. Vendor Id: This field is for the Expense module only. Assign a Vendor Id from the Microsoft
Dynamics product to the user to be used for expense processing. When the user enters an expense
report, the expense report will be issued for the Vendor assigned here.
10. Buyer Id: Enter the specific buyer for this user. The lookup will display all users that are defined with
a user type of buyer. To the right of the Buyer Id field the default Buyer Id will be displayed and is
inherited from either the General Settings (red) or the users department (green). If the department
assigned to the user has a default buyer, the Buyer Id from the Department Setup will be displayed in
green. If assigned department does not have a default buyer setup, the Buyer Id from General
Settings will be displayed in red. If a Buyer Id is not assigned to the user, the default appearing to the
right of the field will be used.
11. Policy Id: Enter a specific routing policy for the user. The lookup will display all policies setup in
Setup Tasks ! Routing Policies. To the right of the Policy Id field, the default Policy Id will be
displayed from either the Department Setup or the General Settings. If the department assigned to
the user has a default policy, the Policy Id from Department Setup will be displayed in green. If
assigned department does not have a default policy setup, the Policy Id from Global Setup will
Page 24 of 172
display in red. If a Policy Id is not assigned to the user, the default appearing to the right of the field
will be used.
12. Manager Id: Enter the Manager Id for the user. The lookup will display all users with the user type of
Reviewer.
13. Addl. Reviewer (2-6): You can define additional reviewers for the user. Additional reviewers defined
for the user can be used in the Routing Policies as reviewers. This will give you more flexibility in
defining your routing policies.
14. Delegate Id: Indicates that a user has been selected to act as a delegate for this user. In the event
that a user will be unable to review documents during a certain time period, they can delegate all
documents assigned to them for review to another user. This ensures the review processing will not
be impeded. The lookup will display all valid users with a user type of reviewer.
15. Delegation Date Range: Specifies the time period during which all requisitions will be delegated to
another user. The lookup will display a valid calendar from which date can be selected. The From
date cannot be less than the To date. After the time period has expired, delegation will stop. The
date range activates the delegation process.
16. Apply delegation to Doc Nbr: Allows a single document that is already in a reviewers approval
queue to be delegated on behalf of the reviewer who is out of the office. This field is available once a
valid Delegate Id and Delegation Date Range are entered. If this field is used, all other documents
will remain in the reviewers approval queue.
17. Approval Limit: Enter the maximum amount a user is allowed to approve should the user be
marked as a reviewer. The approval limit is used in conjunction with the routing policy. Limits are
assumed to be in the base currency.
18. Email Address: Enter the users valid email address. The email address is used to for all ReQlogic
email notifications.
19. Phone: Enter the users contact telephone number.
20. Can change expense vendor: (ReQlogic Expense module only). Check this field if you want the
user to be able to change the default expense vendor on expense reports. This will allow the user to
create expense reports on behalf of other users.
21. Can Receive for Department: (ReQlogic Receivng Module only). Check this box to give the user
the ability to receive items that were requested by any member within their department. Leave
unchecked if the user should only be able to receive items he or she has requested.
22. User Type: Use the user type checkboxes to indicate what type the user will be in ReQlogic. The
following types are available.
2005 Tectura Corporation
Page 25 of 172
All fields that are required by the Microsoft Dynamics ERP product will display as
required in requisition entry for users defined with the user type of buyer
b. Reviewer: Select if the user is a reviewer. A reviewer is someone who has the authority to
approve or reject requisitions and expenses.
c.
Super User: Select if the user is a Super User. Super User abilities include:
Ability to search through all requisitions in Search and Duplicate, even those
marked private.
Can create receipts using ReQlogic OnLine Receiving on behalf of all requesters.
NOTE: A user can have multiple user types. A user can be a Reviewer, a Buyer and a
Super User or any combination of these.
22. Default values from business rules overwrite user entries in: ReQlogic uses business rules
defined in the Microsoft Dynamics product to default values to certain fields on requisitions. For
example, when an Item Id is selected on a requisition, the following fields, if defined, will potentially
default automatically: Description, Vendor, Account, Site, Price, Unit and Dimensions. If a user is
authorized to enter a value in any of those fields, he/she can overwrite the default. If the user then
changes the Item Id to a different Item, ReQlogic will attempt to replace the values already entered
with the defaults of the new item. In certain situations, the user might not want ReQlogic to overwrite
or re-default values in certain fields. This option allows you to uncheck the fields that you do not
want ReQlogic to overwrite if there is a value entered. If the field is blank, defaulting will occur.
2005 Tectura Corporation
Page 26 of 172
HINT: Even though the effective value is defined at the user level, these settings can be made at
the department level and then defaulted to all members in the department.
23. Email notifications are triggered by these events: These checkboxes control the email notification
triggers for the individual user. Email messages will be sent to the user based on the following
events.
a. Submit an email message will be sent to the user if the user is a reviewer or buyer.
b. PO Creation an email notification will be sent to the user when a Purchase Order has
been created from their requisition.
c.
Approval an email notification will be sent to the user when their document has been
approved.
d. Reject an email notification will be sent to the user when iftheir document has been
rejected.
e. Receipt an email notification will be sent when a receipt has been issued against their
Purchase Order.
f.
Voucher an email notification will be sent when a voucher has been created against their
Purchase Order.
g. Buyer Updates an email notification will be sent to the requester when a buyer edits or
deletes a line on an approved requisition, or when a purchase order is manually changed
within the Microsoft Dynamics ERP product. Changes can be viewed using the Requisition
Audit Report.
NOTE: The content of these email notification messages may be edited by using the
ReQlogic Customization Module. Navigate to Customizations ! Email Messages to make
changes.
HINT: The user can make changes to the notifications they wish to receive using User
Preferences. To access User Preferences navigate to the Home Page and click the Preferences
button on the header.
24. User Roles/Roles: Select a role for the User so that Access Rights can be assigned to the User via
the role, and then click New Record to assign the user to the role. The User can be assigned to more
than one role.
25. Save/Cancel: Click Save to save the User. Click Cancel to discard the User.
Page 27 of 172
or arrow keys
2. Click the Edit button. The edit button must be selected in order to edit user information in User
Setup. When clicked, it will enable the Save, Delete, and Cancel buttons. It will also enable lookup
functionality on the fields where applicable.
3. Select Delete to delete the entire User record. ReQlogic will not allow a user record to be deleted if
any requisitions are associated with the user record.
NOTE: If the user is no longer valid, mark the record inactive. If a user is inactive they can no
longer access ReQlogic and will not be displayed in user lookups.
4. Make any necessary change.
5. Click Save to save the changes made. Click Cancel to discard any changes made to the user
record.
A user may have more than one Role. For example, a given individual may be both an Reviewer and a
ReQlogic Administrator. As another example, new Roles can be added when a co-worker goes on vacation
and removed when that colleague returns.
2005 Tectura Corporation
Page 28 of 172
While the use of Roles to establish security is optional, it provides a powerful tool for the ReQlogic
administrator in streamlining the setup of new users.
The Roles page is used to add and maintain roles. Users can be assigned to roles in this page or roles can
be assigned to user in User Setup (see section 2.1.3). The list of pages available to members of a Role is
assigned in Administration ! Access Rights.
or arrow keys
4. Click the New Record button to add the user to the role.
HINT: You can also assign a role to a user record in User Setup.
or arrow keys
NOTE: You cannot delete a Role while users are assigned to it. You must first remove all of
the users assigned to a Role before you can delete it.
Page 29 of 172
or arrow keys
NOTE: Clicking the delete button immediately removes the selected user. There is no
confirmation.
Page 30 of 172
Step number
Criteria
Route to section
The Step Number identifies the routing steps and defines the sequence of the routing rules. The Criteria
section defines the criteria that must be met in order to perform the routing instruction. Up to three conditions
can be defined for each routing step. The Route To section defines who needs to review the document in
the event the criteria are met.
Page 31 of 172
Routing step criteria can be based on any field in any table. The routing step criteria can be a combination of
document (requisition or expense) header, detail line fields (e.g., line amount, total document amount, item,
project, task, requester, GL account, etc.) or fields from related tables (e.g., item product class, GL account
type, project business manager, etc.). ReQlogic provides pre-defined criteria that are used most often in the
Criteria section. To add tables or fields that are not pre-defined to the Routing Policy criteria section, refer to
the ReQlogic Software Developers Kit.
Policies can also be nested into another policy allowing a single general policy that branch across multiple
policies.
Documents can be routed to an unlimited number of reviewers, based on the criteria of the routing policy step
being met. Documents can be approved, rejected and/or modified at either the line or header levels. Steps
can be sent to reviewers in parallel or sequentially.
Routing steps also provide the option of allowing reviewers the ability to modify the document prior to
approval. Reviewer edits can result in rerouting, starting the routing process over, and/or returning the
document to the requester, depending on the flag settings at the policy header.
NOTE: Reviewers can also delegate authority for a predefined period (e.g., vacation) or forward a
particular document to another reviewer. (See User Setup: Delegate Id.)
Routing policies are assigned to users (as submitters of documents) on the basis of a hierarchical system of
defaults. The Policy Id specified in General Settings is the overall default for a Department/User unless an
alternative policy is specified for that Department/User. (See User Setup: Policy Id.)
The Routing diagram (below) outlines the process flow of document transactions beginning with their point of
entry in My Requisitions or My Expenses through the process of building routing steps (when submitted for
approval) and the subsequent approval routing in accordance with those steps, and for requisitions, to Buyer
Review and Purchase Order creation.
The Routing Step diagram (below) outlines the process flow of approval routing once the document has been
submitted for approval and its routing steps have been built.
Page 32 of 172
Page 33 of 172
Page 34 of 172
Page 35 of 172
9. Customized: Check this box to enter the name of the stored procedure that holds the custom policy
steps (e.g., XW_Routing_Customized).
10. Save/Cancel: Click Save to save the policy setup. Click Cancel to discard the policy setup.
11. Add new Policy Step: Click this button to display the entry page for entering a new routing policy
step.
or arrow keys
2. Click the Edit button. The edit button must be selected in order to edit policy information in Routing
Policies. When clicked, it will enable the Save, Delete, and Cancel buttons.
3. Select Delete to delete the entire routing policy.
4. Make any necessary changes.
5. Click Save to save the changes made. Click Cancel to discard any changes made to the policy.
Page 36 of 172
Parallel When this option is checked, the steps approval routing occurs in parallel with
that of another step or steps, and reviewers applicable to both steps receive notification of
the submission at the same time. When this option is unchecked, reviewers for each step
receive notification of the submission sequentially (i.e., one at a time in step order).
d. Nested Policy Id The Policy Id to which this step branches in lieu of completing
subsequent steps.
NOTE 1: The Type must be Branches to a different policy in order for a policy to be
specified in this field.
NOTE 2: If a Nested Policy inadvertently references back to its source policy, a circular
reference (or closed loop) in the routing logic may be created. The result is an irresolvable
loop in the routing criteria that would circle indefinitely, routing documents between policy
steps and back again with no means of moving on to a reviewer. In the event the policy to
which a user is assigned is nested with others in a circular reference scenario, the user
receives a warning message that submission failed due to a circular reference. The circular
reference must be resolved and the document resubmitted.
3. Criteria: Each step in a policy has up to three Conditions, or sets of criteria, that can be defined. A
documents header (see Scope: Apply to the document as a whole) or detail (see Scope: Apply on a
line by line basis) is evaluated against all Conditions that have been defined when determining the
documents approval routing. When all defined Conditions are met, the document as a whole or its
relevant lines (depending on the Criterias Scope) will be routed in accordance with the steps Route
To parameters. If any of the defined Conditions are not met, the Build Routing Steps process (that
occurs when a document is submitted), will skip the step and move on to evaluating the next step.
(Assuming the step option, Dont process subsequent Steps is not checked.)
Page 37 of 172
HINT: Its important to remember that one, two or all three Conditions can be defined for
a step, and that the document or its relevant lines will be routed according to the steps
Route To only if all defined Conditions for the step are met.
a. Scope The following scope choices are available.
i. Apply on a line by line basis fields applicable to the document line as well as
those included in associated document detail tables (see Data Table below) and
their corresponding values are possible parameters for defining a Condition.
ii. Apply to the document as a whole fields applicable to the document header as
well as those included in associated document header tables (see Data Table
below) and their corresponding values are possible parameters for defining a
Condition.
b. Data Table and Data Fields The Scope of a steps Condition determines which tables
(and fields) are applicable as possible parameters when defining the Condition. Any field in a
document header or detail table (or associated table) may be specified as the Conditions
parameter.
Apply on a line by line basis:
i.
ii.
Assigned GL Account
iii.
Assigned Project
iv.
v.
vi.
Assigned Ship To Id
vii.
viii.
Budget Commitments
ix.
Department Manager 1
x.
Department Manager 2
xi.
Department Manager 3
xii.
Department Manager 4
xiii.
Department Manager 5
xiv.
Department Manager 6
xv.
Document Header
xvi.
Document Line
xvii. Requester
xviii. Requesters Department
xix.
Selected Item
xx.
Selected Vendor
Page 38 of 172
Department Manager 1
NOTE 1: Requester includes a field called Within Limit. This field can have a value of Y or N.
Y indicates the amount of the requisition is less than or equal to the Approval Limit defined on the
requesters user record. This field can be used if spending or approval limits are defined as criteria
in routing policies.
NOTE 2: Department Manager 1 includes a field called Within Limit. This field can have a
value of Y or N. Y indicates the amount of the requisition is less than or equal to the Approval Limit
defined on the manager Id user record. The Manager Id is based on the requesters department Id.
Department Manager 2 thru 6 are identical to the Department Manager 1 except that they refer to
the Addl Reviewer (X) defined on the requesters department record where (X) is 2 thru 6. This
field can be used if spending or approval limits are defined as criteria in routing policies.
c.
Comparison This is the operator that associates the Conditions source (table/field) with
its value. Valid comparison values include:
i. Equals
ii. Begins with
iii. Contains
iv. Less than
v. Greater than
vi. Range
vii. Apply to all
viii. Not equal to
Page 39 of 172
d. Value This is the value against which the documents corresponding field (or associated
field) will be compared when evaluating the record against a steps Condition. Value is not
required when Comparison is set to Apply to All or Range.
e. Range from/Range to These fields are only applicable when the Comparison field is set to
Range. Range From specifies the starting (lowest) value of comparison. Range To specifies
the ending (highest) value of comparison. In the event that the document fields value falls
within the Range From and Range To parameters, it will be evaluated as matching a steps
Condition. The values entered in the Range From and Range To fields are included in the
range.
4. Route to: Each step in a policy has an Approval Rule that defines to whom a document is routed in
the event that it meets the Conditions of the steps Criteria. If all of the defined Conditions are met,
the document as a whole or, its relevant line (depending on the scope of the Conditions) will be
routed to a reviewer in accordance with the steps Route To parameters.
The Routing Step diagram (above) outlines the process flow of Approval routing once the document
has been submitted for approval and its routing steps have been built.
a. Type There are three Route To types available:
i. Standard The reviewer source parameters (which may include either a Specific
Approver Id or reference to a table/field parameter that links back to a User Id) are
applicable. No additional Policy Criteria need be evaluated prior to routing being
initiated.
ii. Branches to a different policy reviewer source parameters are not applicable in
this case, however, the steps Criteria is. After evaluating the requisition against the
steps Criteria, the routing process branches out to another policy (see Conditional
Policy Id below).
1. Nesting - the branch to a subsequent policy is established without prior
evaluation of Criteria in the Criteria section of the step
2. Conditional Policy - the branch to a subsequent policy is established with
prior evaluation of Criteria in the Route To section of the step
* Linking Policies together via Nesting (1) or via specification of a Conditional Policy (2),
allows for complex Routing rules to be established where by multiple Criteria must be
evaluated to determine appropriate reviewers for different types of documents.
iii. FYI no action required This option is similar to the Standard option defined
above, except that the reviewer will not be required to approve/reject the document.
2005 Tectura Corporation
Page 40 of 172
Approver Source This field is applicable only when the Route To Type is set to
Standard.
i. Budget Owner
ii. Manager
iii. Project Manager
iv. Project Business Manager
v. Specific Person
vi. Select from Table
When the option Select from Table is selected, the fields Data Table and Data Field are enabled
and required (see Data Table and Data Fields below).
d. Specific Approver Id When the option Specific Person is selected, the field Specific
Approver Id becomes enabled and is required (see below).
e. Data Table and Data Fields The scope of the step determines which tables (and fields)
are applicable as possible parameters when defining approval sources. Any field in
requisition header or detail tables (or associated tables) that links to a ReQlogic User Id may
be specified as an approval source.
HINT: A one-to-one mapping between ReQlogic User Ids and the User Id of the Approval
Source is necessary. For example, implementing ReQlogic with Project Controller requires that
ReQlogic User Ids be the same as Project Controller Employee Ids. Similarly, in the event that
Project Customers (on a Cost Plus project) are established as an Approval Source, ReQlogic
User Ids must be the same as Customer Ids.
Page 41 of 172
ii.
Assigned GL Account
iii.
Assigned Project
iv.
v.
vi.
Assigned Ship To Id
vii.
viii.
Budget Commitments
ix.
Department Manager 1
x.
Department Manager 2
xi.
Department Manager 3
xii.
Department Manager 4
xiii.
Department Manager 5
xiv.
Department Manager 6
xv.
Document Header
xvi.
Document Line
xvii. Requester
xviii. Requesters Department
f.
xix.
Selected Item
xx.
Selected Vendor
Reviewer can make changes When this option is checked, reviewers of documents that
meet the steps criteria are able to make changes to the document. Related options at the
policy header level: Re-routing required if documents are updated by reviewers and Return
documents to requester when re-routing is required prescribe whether or not a document
edited by its reviewer must (in addition) be re-routed and returned to its submitter. When this
option is not checked, reviewers of documents that meet the steps criteria are not able to
make changes to the requisition and rejecting the document automatically returns it to its
submitter.
g. Dont process subsequent steps - When this option is checked, subsequent steps in the
policy are not evaluated and the documents approval routing ends with the reviewer
assigned in this steps Approver Source.
5. Click Save this step to save changes to this step.
6. Click Cancel if you wish to cancel any changes to this step.
Page 42 of 172
or arrow keys
button.
Page 43 of 172
HINT: If using ReQlogic Catalog items with inventory items, ReQlogic Catalog Item Ids cannot
be the same as any inventory item Ids.
3. Description (required): Enter the description of the ReQlogic item.
4. Active Item: Mark if the item is active or not. If the checkbox is marked, the item is active. This
means the ReQlogic item can be used in transactions and will be displayed in the lookups for Item
Page 44 of 172
Ids (default). If the checkbox is unmarked, the item is inactive. This means the ReQlogic item cannot
be used in transactions and will not be displayed in the lookups for Item Ids.
5. Item Type: Specifies an item type for the item. If no lookup is displayed with this field, the field allows
free-form text entry. If a lookup is associated with the field, a value must be selected from the lookup.
NOTE: The ReQlogic Administrator can use the Data Field Customization function to associate
the Item Type field in the ReQlogic Catalog with a table or view. See the Data Field Customizations
and View Definitions section for more information.
6. Vendor: Identifies the vendor Id that will be used as the default vendor for a requisition item. The
default vendor can be changed at requisition entry. The lookup will display all active Vendors in the
Microsoft Dynamics product.
7. GL Account: Specifies the inventory account affected by the purchase of the item. The lookup will
display a list of all valid accounts in the Microsoft Dynamics product.
8. GL Subaccount: Specifies the inventory subaccount. The lookup will display a list of all valid
subaccounts in your Microsoft Dynamics ERP product.
9. FBT Account (Microsoft Dynamics NAV only): Assign an account to be assigned to FBT expense
lines. Refer to the My Expenses section for more details on how FBT is handled.
10. Vendor Part #: Specifies the default vendors item Id for the item. The value that you enter defaults
to the requisition line.
11. Site Id: Site Id is the identifier of the default inventory site where you normally store the item. The
identifier that you enter here must be set up either in ReQlogic Site Maintenance (for Microsoft
Dynamics SL integrations), or in the other Microsoft Dynamics products (if ReQlogic is integrated
with one of those products). The lookup will display all valid sites.
12. PO Unit: PO Unit is the item's unit of measure (each, case, bundle, etc.). A lookup with a list of all
valid units of measure can be defined for this field.
NOTE: For implementations with Microsoft Dynamics NAV, the PO Unit must be a valid
Microsoft Dynamics NAV unit of measure. For expense items, a valid Microsoft Dynamics NAV unit
of measure must be assigned to the catalog item, which will then default to the expense line. If a
generic item is defined in General Settings to be used for noninventory catalog items, the PO Units
that are defined for the noninventory catalog items must be valid for that generic item as its defined
in Microsoft Dynamics NAV. If a generic item is not defined in General Settings, the PO Units defined
for noninventory catalog items must be valid global units of measure in Microsoft Dynamics NAV.
If no inv item is defined in general settings, the unit must be a valid "global" unit in NAV
2005 Tectura Corporation
Page 45 of 172
13. Price: Enter the items last cost (per stocking unit).
14. Image: Enter the path and file under the ReQlogic folder on the Web Server that contains an image
of the item, if used. See section 2.1.6.3 for further information.
15. Expense Options: These options are defined for items that will be used as expense items.
a. Expense Item Determines if an item is an expense item. If an expense item, the item will
display only on the item lookup in My Expenses.
b. Reimbursable expense Determines if the requester will be reimbursed for the purchase of
the item.
c.
16. Save/Cancel: Click Save to save the Catalog item. Click Cancel to discard the Catalog item.
or arrow keys
2. Click the Edit button. The edit button must be selected in order to edit a department in
Department Setup. When clicked, it will enable the Save, Delete, and Cancel buttons. It will
also enable lookup functionality on the fields where applicable.
3. Select Delete to delete the Catalog item.
4. Make any necessary changes.
5. Save/Cancel: Click Save to save changes made to the Catalog setup. Click Cancel to discard
any changes made to the Catalog item.
Page 46 of 172
You would also need to modify the "Req-Item" View Definition by going to Customizations -> View
Definitions and add the ImageLocation field as an additional column marked as an image file. You need to
modify the width and height boxes that will appear. A suggested width and height is 40 x 40.
Page 47 of 172
Page 48 of 172
10. Country: Enter the two-digit Id code of the country where the site is located. Lookup will display all
valid country Ids that are entered into the Microsoft Dynamics product.
11. Save/Cancel: Click Save to save the site. Click Cancel to cancel the site setup.
or arrow keys
2. Click the Edit button. The Edit button must be selected in order to edit a site in Site Maintenance.
When clicked, it will enable the Save, Delete, and Cancel buttons. It will also enable lookup
functionality on the fields where applicable.
3. Select Delete to delete the Site.
4. Make any necessary changes.
5. Click Save to save the changes made. Click Cancel to discard any changes made to the Site.
Page 49 of 172
HINT: Prior to setting up a PunchOut Catalog, set up a generic PunchOut item, preferably in
the ReQlogic Catalog (non-inventory). See Section 2.1.6 on setting up a ReQlogic Catalog item.
Also, the PunchOut Vendor must also be set up in the Microsoft Dynamics product.
Page 50 of 172
6. Item Id: ReQlogic uses this item Id as the generic Id for items requested from this PunchOut catalog
if a specific item Id that matches the vendors item Id is not set up in ReQlogic or the Microsoft
Dynamics product. This item can be set up as a non-inventory item in the ReQlogic Catalog.
NOTE: When punching out items from a vendor site, the vendor item Id will always be used in
the vendor part # field on the requisition line.
7. PunchOut URL (required): This URL is provided by the vendor. This URL is required for ReQlogic to
be able to establish a PunchOut session with the vendors site.
8. PO URL: This URL is provided be the vendor. Its required to be able to electronically submit
purchase orders via cXML to the vendor. This part is NOT required to simply be able to browse and
select items and then send purchase orders back to the vendor in ways other than electronically via
cXML.
9. cXML PunchOut Request (required): This XML template is used to store account and
authentication information which is vendor specific. Typically, the <From> Identity, the <Sender>
Identity and the <Sender> Sharedsecret entries are provided by the vendor.
10. Save/Cancel: Click Save to save the PunchOut setup. Click Cancel to discard the PunchOut setup.
or arrow keys
2. Click the Edit button. The edit button must be selected in order to edit a PunchOut in PunchOut
Catalog Setup. When clicked, it will enable the Save, Delete, and Cancel buttons. It will also
enable lookup functionality on the fields where applicable.
3. Select Delete to delete the existing PunchOut Catalog setup.
4. Make any necessary changes.
5. Click Save to save the changes. Click Cancel to discard any changes made to the PunchOut
Catalog Setup.
Page 51 of 172
Activation of this feature occurs in the Web.config file. Set the value for key
PUNCHOUT_SETACCESS_ENABLED to Y to activate this feature.
NOTE: If this feature is activated after the definition of some PunchOut Catalogs, the
administrator must edit and save each catalog definition to create the Access Rights resource.
Page 52 of 172
PunchOut GL Codes
When a PunchOut item is imported, the application will first attempt to find a GL code mapping for the items
universal code. If a mapping is found, the GL code is defaulted accordingly; otherwise, the standard GL code
default routine is applied.
to display
an existing record.
3. Click the New Record button to add the entry to the PunchOut GL Codes list.
Page 53 of 172
PunchOut GL Codes cannot be edited. If an entry is not correct you must delete it and re-add it.
1. Click the delete button
th
th
th
th
You may also enter partial code with one or more wildcard characters (% and/or ?). An asterisk (*) in
the Department Id field is used to indicate a global setting that effects all users.
2. User Id: Enter a valid User Id or use lookup button
3. GL Account (required): Enter a General Ledger account number or use lookup button
to pull up
an existing record. You may also enter partial code with one or more wildcard characters (% and/or
?).
Page 54 of 172
4. Click the New Record button to add the entry to the GL Code Access list.
NOTE: You cannot leave both the Department Id and the User Id fields blank. At least one of
those fields must have entry.
Page 55 of 172
Only users who have been granted access to the Can Create RFQ resource on the Access Rights page can
create RFQs. The RFQ task can occur at any time before a purchase order is created from a requisition. In
various scenarios, a requester can create an RFQ before the requisition is submitted; or a requisition can be
routed to a reviewer who has the responsibility to create the RFQ; or a buyer can create an RFQ after a
requisition has been fully approved.
Users can also enter RFQs after they have been manually obtained from vendors. This after-the-fact
functionality enables tracking of all RFQs and reporting of them in the Quotes report.
See Request for Quotes for information on creating and accepting RFQs.
Page 56 of 172
linking them to a vendor account in the Microsoft Dynamics product. This link is required, however, if a quote
is later accepted from the supplier and before the supplier can be assigned to a requisition.
Supplier contact information on the profile includes an email address, which is used to send suppliers their
login information and to notify them of requests for quotes.
Using the Valid for all items parameter on the profile, users can be included suppliers on the RFQ Supplier
list, which is used to select suppliers for requests for quotes. Suppliers can also be automatically assigned to
specific items when quotes are requested for those items.
1. Click the New Record button.
2. Import from Vendor: Select a vendor defined in the Microsoft Dynamics product to default that
vendors information into a new supplier record.
3. User Id (required): The Id for the supplier. If a vendor in the Microsoft Dynamics product is imported
as a supplier, the vendor Id defaults into this field, but can be changed.
4. Vendor Name (required): This is the name of the supplier. If a vendor in the Microsoft Dynamics
product is imported as a supplier, the vendor name defaults into this field, but can be changed.
5. Internal Vend. Id: This is the vendor Id from the Microsoft Dynamics product. If a vendor in the
Microsoft Dynamics product is imported as a supplier, the vendor Id defaults into this field.
6. Language Id (required): This is the language used for the supplier of the supplier portal page.
7. Password/Retype: This is the password that the supplier uses to log into the supplier portal.
8. Status (Active): This field determines whether the supplier record is active or inactive.
9. Website: This is the web site of the supplier.
10. Valid for all items: This check box determines if the supplier will be included in the RFQ Supplier list
for any item selected for a request for quote.
11. Contact information: Contact information includes a contact name, email address, phone number
and mailing address.
12. Notes (visible to supplier): This is information intended for the supplier that appears on the
suppliers portal page.
13. Notes (not visible to supplier): This is information about the supplier that is meant for internal use.
14. Save/Cancel: Click Save to save RFQ Setup. Click Cancel to cancel the setup of this RFQ Supplier.
15. Send Login: This button appears once the supplier record is saved and is used to send the
suppliers Id and password for logging into the supplier portal.
Page 57 of 172
16. Assigned Items: Suppliers can be assigned to specific items and be automatically included as
recipients of quote requests for those items. Any assigned items are listed under this heading.
17. Item Id: This field is used to select items that are assigned to suppliers. Suppliers will automatically
receive requests for quotes for these items.
Page 58 of 172
2.2 Customization
ReQlogic allows you to customize many aspects of the product.
2. Msg Id (required): The next available message Id will automatically default in.
2005 Tectura Corporation
Page 59 of 172
HINT: When using the Message Text and Comment fields, you can enter a word or part of a
phrase, and ReQlogic will return all instances that include that word or words. For example, if
you enter Id, ReQlogic will find all records that have Id somewhere in its comments.
2. Click the edit
3. The message Id is used in Menu administration. See Administration section 2.3 for more
information.
4. Language: choose the language the text is in.
5. Text: This is what is viewed by the users.
6. Comment: edit the comment about the text.
7. Save/Cancel: Click the save
changes made.
8. Delete: To delete a message click the delete
Page 60 of 172
HINT: If you preface all definitions you create (i.e. Z_NEW VIEW), it will be easier to identify
what are standard definitions and which are customized.
3. Title (required): This is the description of the definition.
4. Source (required): Select a table as the Source. This may be an existing table or a validation table
that youve created using the Validation Tables tab in the ReQlogic Utilities.
5. Stored Procedure (required): The Stored Procedure defaults and should remain
XW_PV_Template.
6. Columns: This defines the columns of data viewed.
a. Unique Id (required) This is the Id field of the table being used in this view.
Page 61 of 172
b. Description (required) This is the description of the Id field of the table being used in this
view.
c.
Additional Columns Select the columns that will be included in the view definition
(lookup). The columns that you can select are from the Source table that you selected
above. Also enter a description for each column.
d. Image Mark the checkbox if you want to include an image of this field. When you mark the
checkbox, an additional field comes into view.
e. Image Size If the Image checkbox is marked, the image size is available where you can
note how big you want the image to be.
7. Restrictions: You can also restrict what specific sets of users can see in a view definition by defining
a restriction on the view definition. When restrictions are in place, users can be restricted to seeing
only the items, accounts, sites, classes, etc. that apply to them or their department/location.
8. Save/Cancel: Click Save to save the View setup. Click Cancel to cancel the View setup.
9. Preview: After you save the record, the Preview button becomes active. Click on the Preview button
to preview the results of your work.
Page 62 of 172
b. Greater than
c.
Less than
d. Begins with
e. Contains
f.
Not equal to
4. Choose what you want to restrict the field to. The choices are:
a. Value Then add a constant value for comparison.
b. User Field Choose which field of the User setup you want for comparison.
c.
Department Field Choose which field of the Department setup you want for comparison.
5. You can have one restriction or select the And/Or choice to add another restriction.
2. Click the Edit button. The Edit button must be selected in order to edit a View Definition. When
clicked, it will enable the Save, Delete, and Cancel buttons. It will also enable lookup functionality
on the fields where applicable.
3. Select Delete to delete an existing View.
NOTE: Do not delete Views that were not created by you.
4. You can edit a view definition by adding, deleting, or changing columns that are included in the view.
5. Click Save to save the changes made. Click Cancel to discard any changes made to the View.
Page 63 of 172
The following email messages can be customized to fit your companys needs.
Email Message
Description
APPROVAL
BUYER
Notification to buyer
BUYERDELETES
BUYERUPDATES
RECALLED
PARTAPPROVAL
Partial Approval
POCREATED
RECEIPT
Receipt notification
REJECTION
FYI
Email notification
POEMAIL
Page 64 of 172
Email Message
Description
REMINDER
Review Reminder
RFQ-NEWLOGIN
RFQ-NOTIFICATION
RFQ-QUOTE-SUBMIT
QUESTION
POCHANGE
ROUTING
VOUCHER
Voucher notification
2. Click the Edit button. The Edit button must be selected in order to edit an Email message. When
clicked, it will enable the Save and Cancel buttons.
3. Message Id: This is predefined and non-editable.
4. Description: The description of the email message can be modified if you need a better description.
5. Subject: This is the text that will appear in the subject line of the email message sent and can be
edited.
6. Body: This is the code that displays the content of the email message. Common field codes are
listed on the right along with the description of what the codes mean.
7. Save/Cancel: Click Save to save changes made. Click Cancel to cancel any changes.
NOTE: The Field/Description chart on the right side of the page give a listing of codes used in
the email text and what those codes stand for. For example, in an email message, wherever
%REQ% exists will display a text of Requisition Number.
Page 65 of 172
Expense Header
d. Expense Line
e. ReQlogic Catalog
f.
Requisition Header
g. Requisition Line
h. RFQ Supplier
i.
User Preferences
Page 66 of 172
j.
User Setup
there is no inheritance from higher level definitions down to lower level ones. If a Department
level customization is defined, the Global level no longer applies to any member of the
department. If a User level customization is defined, the Global level or a Department level
customization no longer applies to the specific user.
3. Department Id: Enter the department to which the customization applies. This is applicable only
when the Customization level is Department.
4. User Id: Enter the user Id to which the customization applies. This is applicable only when the
Customization level is User.
5. Copy from Department: Copies customizations from another department to use as a template. This
is applicable only when the Customization level is Department.
6. Copy from User: Copies customization settings from another user to use as a template. This is
applicable only when the Customization level is User.
7. Copy from Global: Copies customization settings from the Global Customization level to the current
selected level (to use as a template).
8. Delete Customizations: Deletes customization settings for the selected department or user as
applicable.
HINT: To define customizations for a department or user, first enter that department Id or user Id
from the list of valid options, and then copy from either global or another department or user Id (copy
from fields).
9. Refresh view.
10. Field Properties: To edit field properties, click the edit button
Page 67 of 172
d. Width Enter the width of the field on the form if different from default (displayed). The
maximum number of characters is automatically set according to the database field size.
e. Read Only Allows/prevents users to modify the default value.
f.
Default Value The value that the application should use when initializing a new record. For
the Requisition Line, additional values are available for user fields. %REQNBR% will
automatically default the value to requisition number being edited, and %USERId% will
automatically default the value to the user Id associated with the requisition.
NOTE: For Microsoft Dynamics SL implementations, user field values in the Requisition
Line flow to the purchase order database fields on a one-for-one basis (for example, user 1
to user 1).
j.
Validation Controls whether values are validated, and provides lookup functionality to the
user. A validation source can be selected from the list. If a new validation list is needed, one
can be created by the administrator in the View Definitions page from the Customizations
menu.
k.
Box Type Specifies whether the control associated with the field is a lookup or a
dropdown. If a Dropdown box is selected, the dropdown list can contain up to 50 records.
Whether a lookup or dropdoen the source is selected in the Validation field.
11. Save/Cancel:
Click the Save to save changes made. Click Cancel to cancel the
Page 68 of 172
2.3 Administration
The following menu options are available from the Administration tab:
Menu Administration
Access Rights
License Information
Delete History
button next to the menu group you want to modify. It will refresh the Menu
Page 69 of 172
button.
NOTE: Deleting a menu choice will delete it for all users in ReQlogic.
3. Click the Edit
4. Name: The menu group name can either be hard-coded, or refer to a message number (as defined
in the Text Administration section 2.2.1). To use a message number, simply enter the message
number followed by the @@ characters (without the quotes). Any comment can be added to after
the @@ characters.
5. Order: This is the order the menus are listed from left to right. Order # 10 is the menu choice on the
far left. For example, to move the Buyer Tasks menu choice to between the Customization and
Setup Tasks menus, enter an order # that is between 30 and 70.
6. Save/Cancel: Click the save
changes made.
7. You must log out and log back in for the changes to take effect.
Menu Items for: Displays a list of current menu items for the selected menu group.
button next to the menu group you want to modify. It will refresh the Menu
button.
NOTE: Deleting a menu item will delete for all users in ReQlogic.
3. Click the Edit
Page 70 of 172
4. Resource Id: Resource Ids control access rights. When moving a menu item to a different or new
menu group, make sure you accurately copy the Resource Id. For new items, the administrator can
assign a resource Id. Access rights will not be affective for new menu items unless those new items
are designed to enforce access rights rules. For reports, refer the separate developer documentation
for instructions on how to enable web reports.
5. Name: The name to be displayed in the menu.
6. URL: The http path to the menu item.
7. Order: The order this menu group/item should be listed in.
8. Save/Cancel: Click the save
changes made.
9. You must log out and log back in for the changes to take effect.
Page 71 of 172
Rights are organized into two groups. Menu Items correspond to ReQlogic pages that are accessed from the
menu system. Resources are additional functionality available within ReQlogic. The Available Resources
are:
Append to PO This resource enables users to add a requisition line to an existing purchase order.
This feature is enabled for only Microsoft Dynamics GP and Microsoft Dynamics SL.
Budget Inquiry Allows users to open a window that display budget information while entering
requisitions or expense reports. This feature provides read-only access to Microsoft Dynamics GP
Project and Encumbrance budgets and Microsoft Dynamics SL General Ledger and Project budgets.
Buyer queue edits allowed This resource grants users access to make changes to approved
requisitions in the buyer queue. Without this resource, buyers will only be able to convert an
approved requisition to a purchase order without the capability to edit the requisition first.
Can Create Blanket Requisitions Enables the Blanket checkbox in My Requisitions. This
permits the user to create a Blank Requisition that can be used as a template for future requisitions.
Can Create RFQ This resource allows a user to create a Request for Quote (RFQ) for a
requisition.
Can issue inventory while receiving Users who dont have access to Issue will not be able to
enter an issue quantity or see the Issue All button in the Receiving page.
Can view Analytical Accounting Codes (GP) Supports Analytical Accounting in Microsoft
Dynamics GP. Permits users to the open a window to see the Analytical Accounting codes entered
by others in My Requisitions and My Expenses.
Can view/edit Analytical Accounting Codes (GP) Supports Analytical Accounting in Microsoft
Dynamics GP. Users with this resource can both view and edit Analytical Accounting codes in My
Requisitions and My Expenses.
PunchOut Catalog (Vendor Name) If the Access Control for PunchOut Catalogs feature is
activated, a resource is created for each vendor added in PunchOut Catalog Setup. This allows you
to limit selected users to PunchOut only to certain vendors. (See the Assigning PunchOut Catalogs
section for more information.)
Quick approval Granting this access to a reviewer enables the reviewer to approve requisition and
expense documents directly from the review queue grid. This is intended for reviewers who do not
always need to see the details of each document prior to approving. Other review options such as
rejecting, line level approval, review comments, forwards and returns will still require the reviewer to
open the document details.
Page 72 of 172
Add All Click on this option to grant access to all Available Resources.
d. Remove All Click on this option to remove access to all Authorized Resources.
9. Authorized menu items/Authorized Resources: This is a list of the menu items or resources to
which access has been granted either globally, for a department, a user or a role.
NOTE: Moving menu items and/or resources from Available to Authorized or back immediately
updates the access list for the department, user, role or globally. There is no separate save or
confirm step, nor is there an option to cancel changes made in error.
Global
Department A
Role Z
User X
Menu Items
Access Rights
Budget Maintenance
Page 73 of 172
Resource
Global
Department A
Role Z
User X
Budget Transactions
Buyer Review - Summary
Buyer Review and Selection
Code Setup
Data Field Customizations
Delete History
Department Setup
Email Messages
Expense Audit Report
Expense Transactions
General Settings
Import Expenses
Inventory Fulfillment Report
License Information
Menu Administration
My Approvals
My Expenses
My Requisitions
Physical Fulfillment
PunchOut Catalog Setup
Purchase Orders
Quotes
Receipts
Receiving
ReQlogic Catalog
Requisition Audit Report
Requisition Import
Requisitions List
Review Queue
RFQ Supplier
Roles
Routing Policies
Search and Duplicate
Serial Numbers
Site Maintenance
Text Administration
User Setup
View Definitions
Resources
Page 74 of 172
Resource
Global
Department A
Role Z
User X
Append to PO
Budget Inquiry
Buyer queue edits allowed
Can Create Blanket
Requisitions
Can Create RFQ
Can issue inventory while
receiving
Can view Analytical Accounting
Codes (GP)
Can view/Edit Analytical
Accounting Codes (GP)
PunchOut Catalog - (Vendor
Name)
Quick approval
Page 75 of 172
Page 76 of 172
It is advisable to take a backup of the data before deleting the transactions, in the event that the wrong date
is entered, or you wish to inquire on historical transactions.
Only transaction data is deleted (i.e., requisitions), and not setup data, such as User Ids, ReQlogic Catalog
items, etc.
Page 77 of 172
2.4.1 Logging In
Provide the SQL server login information. The SQL server account must have ownership access to the SQL
database you are trying to configure. An example of an account with such access is the sa user account.
When installing ReQlogic on a case-sensitive SQL server, select the case-sensitive checkbox. This option
will cause all database interaction to happen in a case-sensitive compatible way.
After you login, select a database from the list.
Page 78 of 172
Page 79 of 172
as the ReQlogic Catalog Item, on a periodic basis to update the table with the latest information
such as vendor catalogs, pricesetc.
5. Display records from database: This button will load the grid from the database instead of an Excel
file. The purpose of this button is to update the records that are in the database or add new ones,
without the need for an Excel file.
6. Export to Excel: Click this button to export the records in the grid to Excel.
7. Import Using Excel: This feature is no longer necessary.
8. Import all Files: This button will automatically load all Excel files in the default installation folder, and
import them into the database.
IMPORTANT: The Import All Files is for new installations only. Doing this in an existing install
could override existing records.
9. Import Upgrade Files: This button will automatically load all Excel files in the default upgrade folder,
and import them into the database. The default folder depends on the product selected. The purpose
of this button is to automate the import of multiple files.
Page 80 of 172
HINT: If you preface all validation tables you create (i.e. Z_NEW), it will be easier to identify what
are standard tables and which are customized.
2. Click Create Table.
Once a validation table is created, you can use the Record Import tab to populate it. Alternatively, you
can create an automated SQL process or (DTS) to automatically populate/refresh the validation table
periodically.
The default schema for validation tables is
Enter records below the header (do not leave empty lines in between)
Page 81 of 172
SQL database that is not on the same server as ReQlogic, but is linked to the server (linked server)
Page 82 of 172
Page 83 of 172
7. The Data Mapping lists of all available ReQlogic Catalog columns (the catalog schema).
8. Select the Database and Table or View in which the source catalog resides.
Page 84 of 172
9. The list of columns from the source table/view is automatically displayed as soon as a source is
selected.
10. Drag and drop source columns over data mapping columns as appropriate.
11. To undo a column assignment, either replace it with another column, or simply drag and drop the
<Default> column.
12. To map a specific hard coded value to a column, simply drag and drop the <Specific> source
column to the mapping column to which you want to assign the value. A pop-up prompt will open
and ask for the value to be assigned. (Examples of columns usually hard coded are:
Catalog=OfficeDepot or Engineering, DfltPOUnit=EACH or BOX, Supplr1=V0123.)
NOTE: In some situations, you might want to only expose a subset of the external catalog. For
example, there might be a Discontinued flag in the source catalog. To expose only non-discontinued
items where the Discontinued column = 0, you can map the column to a field such as user10 and then
drag and drop the <Filter> source column. A pop-up prompt will ask for the value to filter on. In this
example, it would be 0. Other examples of filter situations are: Category Id, class Id, Item Type, etc.
Alternatively, an SQL view can be created to implement more complex filters. The view can then be
used as the data source.
13. Click the View sample records button to see the result of your data mapping before committing it.
This is especially useful when using filters
14. Click Save to save the catalog definition and make it available to ReQlogic users for item search and
selection.
Page 85 of 172
Page 86 of 172
Page 87 of 172
Description
Required/Optional
ItemId
Required
Catalog
Optional
Descr
Item description
Optional
InvtType
Item Type
Optional
StdCost
Unit Price
Optional
Supplr1
Default Vendor Id
Optional
QtyAvail
Available quantity
Optional
Class
Item class
Optional
DfltPOUnit
Optional
Page 88 of 172
3 Requester
This section describes the functions applicable to a Requester.
Transactions ! My Requisitions
Page 89 of 172
7. Base Amt: The total amount of the requisition in the base currency as defined in the General
Settings (multicurrency implementations only).
8. PO Nbr: Purchase Order Number that the requisition created. This will only show once a purchase
order is created in the Microsoft Dynamics product.
9. Currency Id: Identifies the currency of the requisition (multicurrency implementations only).
10. Requester (required): User who is entering in the requisition. The requester will default to the user
who is logged in to ReQlogic. The lookup will display all valid users. Only a Super User can change
the requester for the requisition.
11. Routing Policy (required): Specifies the routing policy the requisition will use. The lookup will display
all policies setup in Setup Tasks ! Routing Policies. The policy will default from the User Setup
Policy Id field. Only a Super User can change the policy Id for the requisition.
12. Company: Company that the requisition will be submitted to. The lookup will display all valid
companies.
13. Vendor: Select a vendor that will default to the requisition line items when they are created. This is
especially useful for if the requisition is entered for one vendor.
14. Project: Select a project that will default to the requisition line items when they are created. This is
especially useful for if the requisition is entered for one project. This is applicable for Microsoft
Dynamics SL and Microsoft Dynamics GP.
15. Task/Cost Category: Select a task/cost category that will default to the requisition line items when
they are created. This is especially useful for if the requisition is entered for one task. This is
applicable for Microsoft Dynamics SL and Microsoft Dynamics GP.
16. Append to PO: Select a purchase order number that will default to the lines of the requisition. If a
requisition line contains an Append to PO value, the line will be appended to the purchase order
when the purchase order creation process is run from the Buyer queue. This functionality is available
for Microsoft Dynamics SL and Microsoft Dynamics GP. Access to this functionality is controlled
through Access Rights.
17. Private: Unmark the checkbox if the requisition can be copied to another requisition. Only a Super
User can see requisitions marked private in the ReQlogics Search and Duplicate page. See Section
3.6 for futher information on duplicating requisitions.
18. Blanket: Select if the requisition is a blanket requisition.
19. Attachments: Click Upload to add a file to the requisition. Any type of file can be attached.
Documents attached here are viewable by all who review the requisition.
Page 90 of 172
20. Notes: A requester can add notes to the requisition. Notes can be entered in the following three
areas:
a. General Notes Designed to provide more information to the Reviewer.
b. Notes to Vendor Designed to provide more information to the Vendor. Is passed to the
Purchase Order.
c.
21. Save/Cancel: Click the Save button to save the requisition information. Click the Cancel button to
cancel the current requisition.
22. Print: After one or more line items have been added to the requisition, you can click the Print button
to get a Requisition Report.
23. Submit: Click the Submit button to submit the current requisition to be approved. See section
3.1.5.1 about submitting requisitions.
1. From the Summary or Detail tab, click New Line to add a line item to the requisition.
Page 91 of 172
2. Item Id: This is the item that is being purchased. The lookup will display all valid items from the
inventory module (if installed) and the ReQlogic Catalog (if being used). The favorites button
will
display all valid items marked by the user as a favorite. To add an item to your favorites list:
a. Click the lookup button to see a list of all requisition items.
b. Click the Add to Favorites button
3. Description (required): Enter a description of the item you are purchasing. If an item is selected, the
description will default from the items description. If no item is entered the user must enter in a
description of the item they are requesting.
NOTE: For Microsoft Dynamics AX, if a specific item description has been defined in Microsoft
Dynamics AX for the Item/Vendor combination selected on the requisition line, that description is
defaulted into the ReQlogic item description field. If no Item/Vendor description is found, the standard
description defaults to the line.
4. Vendor Part #: Enter any vendor part number or catalog number. It can be printed on purchase
orders to enable vendors to process the order. This field allows any value without validation, but a
lookup function enables users to search for pre-established vendor part relationships. Once a user
selects a Vendor Part number from the list, the associated ReQlogic item Id will default in. If an item
Id is selected, and it has a pre-established Vendor part number, that number will default in.
Default values, however, will not overwrite values that have already been entered. If an item Id has
been entered, and then a vendor part number is entered, the associated item Id (if different from
whats been entered), will not be displayed. The same applies to selecting an item Id after entering a
vendor part number.
Depending on the setup of the Microsoft Dynamics product, new vendor part numbers can be
automatically added to ReQlogic, establishing a relationship between Item Id/Vendor/Vendor part
number.
5. Purchase type: Select the purchase type which identifies the type of goods or services that appear
on the requisition. This field is required if the requisitioner is also a buyer.
6. Quantity (required): Enter the quantity ordered for the item.
7. Unit: Enter or select the unit of measure of the item. This field is required if the requisitioner is also a
buyer.
8. Price: Enter the price per item. The price can default from the selected item.
Page 92 of 172
NOTE: For Microsoft Dynamics AX, price can be derived from the Price Unit functionality that
can be defined for an inventory item.
9. Total for Item: The price of the item multiplied by the quantity, multiplied by the unit of measure. If
you enter a quantity and price, this field calculates itself. You can enter an amount here in which the
Price field will be calculated.
10. Company: This is the company the for which the requisition is being created. This is used if MultiCompany is installed and defaults from the header. This field is required if the requisitioner is also a
Buyer.
11. Vendor: Enter the Vendor Id from which the item is being purchased. This field is required if the
requisitioner is also a Buyer.
12. Dimension (1 5): Select the financial dimensions, if appropriate, for the requisition line.
Dimensions are applicable to Microsoft Dynamics AX and Microsoft Dynamics NAV only. For
Dimension fields, ReQlogic Administrators may modify the field labels to accurately identify the
dimensions.
NOTE: For implementations with Microsoft Dynamics AX, dimensions may be validated
according to the dimension validation settings based on GL account. If an account is entered on the
requisition line, the validation will be based on that account. If no account is specified, validation is
based on the posting account associated with the item group for the inventory item.
13. Posting Group: Select the posting group, if appropriate, for the requisition line. Posting groups are
applicable to Microsoft Dynamics NAV only.
14. Ship to: Enter or select the site where the item will be shipped. This field is required if the
requisitioner is also a Buyer.
15. Project: Identifies the project for which the item is purchased. This field is only enabled if the Project
module is installed.
16. Task/Cost Category: Identifies the task for which the item is purchased. This field is only enabled if
the Project module is installed.
17. GL Account: Displays the General Ledger account updated by the amount of the transaction detail
line on the purchase order. For Microsoft Dynamics SL, the account must have an account category
if the Purchase Type is set to Goods for a Project or Services for Project.
18. GL subaccount (Microsoft Dynamics SL only): Displays the General Ledger subaccount updated by
the amount of the transaction for the purchase order. This field defaults from the project and task if
they have been selected.
2005 Tectura Corporation
Page 93 of 172
19. Required by: Displays the date when the receipt of this item is required.
20. Append to PO: Select a purchase order number if the requisition line is to be appended to an
existing purchase order. Only purchase order to which lines can be appended will display in the
lookup for this field. Any requisition line that contains an Append to PO value will be appended to
the purchase order when the purchase order creation process is run from the Buyer queue. This
functionality is available for Microsoft Dynamics SL and Microsoft Dynamics GP. Access to this
functionality is controlled through Access Rights.
21. Inspected: Use to indicate if goods have been physically inspected by requester. May be used in
reporting.
22. VAT/GST (Microsoft Dynamics NAV only): When enabled in the General Settings page, this field
displays the VAT/GST value which calculated based on the GL Code setup in Microsoft Dynamics
NAV.
23. Attachments: Click Upload to add a file to the requisition. Any type of file can be attached.
24. Notes: A Requester can add notes to the requisition detail line. Notes can be entered in the following
three areas:
a. General Notes Designed to provide more information to the Reviewer.
b. Notes to Vendor Designed to provide more information to the Vendor. Is passed to the
Purchase Order.
c.
25. Save/Cancel: Click Save this item to save the detail line to the requisition. This will also perform
data validations. Click Cancel changes to cancel the changes made to the detail line item.
26. Copy: Click the Copy to new line icon
next to the line item if you want to create a new line with a
Page 94 of 172
A new GL Distribution button is available next to the GL Account label on the document line. Clicking the
button opens a pop-up window for the user to enter distribution accounts. The first time the distribution
window opens, it will default the GL Account field to the account defined on the document line.
Distribution can be done my amount or percent. Percent distributions are automatically converted to
equivalent amount distribution when the document line is saved. Total distributions must equal the amount
on the line unless no distribution exists for the line. If percentage distributions are used, the total of all
percentages must equal 100%. Validation happens when the line is saved.
The Account distribution feature is enabled for requisitions only where the ReQlogic Receiving module is
registered. GL distributions are created at the receipt stage for requisitions and the AP voucher for
expenses. When ReQlogic creates Microsoft Dynamics GP receipts or vouchers, it uses the account
distribution (if any) to populate the corresponding table on the Microsoft Dynamics GP receipt or voucher.
2005 Tectura Corporation
Page 95 of 172
When distribution is used, the account defined on the document line is not used on the receipt or voucher.
When no distribution is defined for a line item, the standard logic is used and the full line amount is assigned
to the account defined on the document line.
The Requisition Summary tab and Buyer Queue grids have a new button at the line level that opens the
distribution window in a read-only mode.
or arrow keys
c.
d. Save/Cancel: Click Save to save changes made to the document header. Click Cancel to
discard any changes made to the document header.
3. To edit Detail Line information:
Page 96 of 172
next to the line item you want to edit. When clicked it will open the
document detail entry page so the user can edit the line item. Edit will not be enabled once
the document has been submitted.
c.
Click Remove this item button to delete the detail line from the document.
If any email triggers are turned on, an email notification will be sent.
Page 97 of 172
If you have a budget setup and a notification turned on in General Settings, a notification will be displayed if
your requisition will send you over the budget.
1. Step Nbr: This is the number of the steps, in order, the document will be routed.
2. Reviewer Name: This is the name of the user who will review the requisition for the routing step.
3. Action taken: Action taken by the reviewer.
4. Delegate To: If the document was delegated, this field will display the reviewer the requisition was
delegated to.
5. Reviewer Comments: Displays any comments the reviewer added to the document during the
review process.
6. Date/Time: This displays the date and time the reviewer reviewed the requisition.
Page 98 of 172
When a document has been recalled, the Status tab will be updated as shown.
Page 99 of 172
Blanket requisitions are not submitted for approval as are regular requisitions. When a requisition is marked
as Blanket, the Submit button is grayed out.
2. On the pop-up window, search for the appropriate blanket requisition by filtering on the Blanket
requisition number, the Item Id, or Vendor.
HINT: The lookups will only display requisitions marked as blanket, items that are on blanket
requisitions and vendors assigned to blanket requisitions.
3. Click Apply Filter.
7. At the same time, the Receipts tab on the blanket requisition is updated with information from the
regular requisition.
At the same time, the Receipts tab on the blanket requisition is updated with information from the regular
requisition.
Once the quantity on the receipts tab matches the quantity on the blanket, the requisition will automatically
close.
2. ReQlogic starts a cXML PunchOut session with the site and directs the user to the sites catalog.
3. The user browses the web site and builds a shopping basket utilizing all the search functionality
available at the site.
4. When done, the user uses the sites Checkout function.
5. The site automatically transmits the basket in cXML to ReQlogic.
6. ReQlogic adds the items to a requisition.
7. The user can add to or modify the requisition and submit it for approval.
NOTE: If you manually add items to a PunchOut requisition, check with the vendor on how those
manually added items will be handled.
or
Summary Tab: Displays a summary of the individual line items that have been entered to the requisitions in
a grid format.
Details Tab: The Details tab display a detail listing of the individual line items that have been entered to the
requisitions.
Receipts Tab: The Receipts tab displays information for requisition lines that have been received using the
Online Receiving module.
Quotes Tab: The Quotes tab displays quote information for each requisition line that has a quote associated
with it.
Routing Tab: The Requisition Routing tab display the approval route the requisition will take.
Status Tab: The Requisition Status tab displays the step-by-step actions taken for the requisition. All entries
in this tab are system generated.
PO Details Tab: The PO Details tab displays information regarding the purchase order(s) created for each
line of the requisition.
1. Requester: The Requester defaults with the users login. Only Buyers and Super Users can change
the Requester.
2. Description: Enter a Description that ReQlogic will use as the description for the requisition that will
be created.
3. File Location: Browse to and select the requisition spreadsheet that you want to import.
4. Accept duplicate file name: Mark the checkbox if you want to import a spreadsheet that has the
same file name as a previously imported file.
5. Sample File: If you want to display a sample requisition spreadsheet and use it as a template for
creating a new one, click the Sample File link.
6. Click Import to import the file.
A new requisition is created using the information that was imported from the spreadsheet. It can now be
pulled up and reviewed/submitted under Transactions ! My Requisitions.
To paste the requisition lines that were copied in the Search and Duplicate page, click the Paste from
Clipboard link. This will paste the requisition lines into the new requisition. The requisition can now be
submitted or edited.
Note: There is no need to click Add an item to the requisition as well as the Paste form Clipboard, to copy
these lines from the clipboard. They are completely separate functions.
4 Reviewer
This section describes the functions applicable to a Reviewer.
Transactions ! My Approvals
My Approvals allows Reviewers to approve requisitions or expense documents, reject them or delegate their
review privileges to another user.
Reviewers can access a requisition for review by clicking on the document icon
This will open the requisition in the My Requisitions page in a summary view. The reviewer can then view the
details tab (for requisitions), the routings tab and the status tab. The last tab Approval Options is where the
review can delegate the requisition to another user or add comments.
On the Summary tab, you can view further information by moving your mouse over text fields in blue.
The following information is viewable on the Summary tab:
1. Nbr: This is the line number
2. Status: This is the status of the line item.
3. Description: This shows the description of the line item.
4. Vendor: If a vendor was selected for this item, the vendor Id is shown here.
5. Project: This will show if the item is assigned to a project.
6. Cost Category: This will show if the item is assigned to a cost category in a project.
7. Ship: This is the ship to site.
8. GL Account: This will show the GL account number assigned to this item.
9. GL Subaccount (Microsoft Dynamics SL only): This displays the General Ledger subaccount
updated by the amount of the transaction for the purchase order.
10. Price: This is the unit price of the item.
11. Quantity: This is the total quantity for the item ordered.
12. Total for Item: This is the extended price (price x quantity) of the item.
13. Approve: This shows the items that are set to be approved.
From the Details tab, click the Edit link for the line you want to edit.
When clicked, the Edit link will enable the Save this item, Cancel changes and Remove this item buttons.
It will also enable lookup functionality on the fields where applicable.
NOTE: If a line item does not have a checkbox next to it, you do not have approval
rights to that line item. This is based on the routing policy criteria.
b. In the Approval Options tab, add any comments about your review.
c.
2. If the applicable policy routing step does not allow line level approval you must approve the
requisition as a whole.
a. In the Approval Options tab, add any comments about your review.
b. Click the Approve button in the header
NOTE: If line level approval is not allowed, the checkboxes next to each line item will be
inactive and you will not be able to check or uncheck them.
2005 Tectura Corporation
3. After the document has been approved, you will be taken to the My Approvals page.
NOTE: If a line item does not have a checkbox next to it, you do not have approval
rights to that line item. This is based on the routing policy criteria.
b. In the Approval Options tab, add any comments about the rejection.
c.
2. If the applicable policy routing step does not allow line level approval you must reject the requisition
as a whole.
a. In the Approval Options tab, add any comments about the rejection.
b. Click the Reject button in the header
NOTE: If line level approval is not allowed, the checkboxes next to each line item will be
inactive and you will not be able to check or uncheck them.
3. After the document has been rejected, you will be taken to My Approvals page.
5 Buyer
This section describes the functions applicable to a Buyer.
The filter criteria includes the Show line notes and Show line attachments checkboxes, which need to be
marked if you want to see line item notes and attachements for each line item. With these checkbox checked,
the Notes and Attachments also display.
will appear if the requisition line item is valid and there are no errors. This means the
If the requisition line item is not valid or data is missing, an information symbol
requisition line can be selected to include on a purchae order, it must have a check mark in the valid column.
With the mouse, a buyer can hover over the information symbol and a Validations Messages box will display
all the errors associated with the requisition detail line. The following fields must be validated before a line
item can be processed into a purchase order:
1. Item Id The item must be a valid Item from the Inventory module or from the ReQlogic Catalog
2. Purchase Type The Purchase Type is required and must be valid. The following are validations for
Purchase Type:
a. Inventory Goods Item must be a Stock Item and a project and task must not be assigned.
b. Goods for Project Item must be a Stock item and a project/task must be assigned
c.
Non Inventory Goods Item must be a non-stock item. Project and task not required.
d. Service for Expense Item must be a non-stock item and a project/task cannot be
assigned.
e. Service for Project Item must be a non-stock item and a project and task must be
assigned.
3. Ship to/Site Id Must be a valid Site Id from the Inventory module or from the ReQlogic Site
Maintenance (Microsoft Dynamics SL only).
4. GL Account Must be a valid GL Account. If a project and task are assigned, the account must
have an account category.
5. GL Subaccount (Microsoft Dynamics SL only) Must be a valid GL Subaccount
6. Vendor Id Must be a valid Vendor in the Microsoft Dynamics product.
7. Unit Must be a valid Unit of Measure in the Microsoft Dynamics product.
A buyer can change the status of a line item by clicking on the blue diamond in the status column. A new
window opens and allows the buyer to change the status, depending on what the original status was.
2005 Tectura Corporation
The Status Update window displays the document number, item description and the original item status. The
Change Status To drop-down box provides a list of available statuses for this item. Make the change and
click Submit. The following is a list of statuses and their meaning:
Status Id
Description
AP
Approved
RT
Routing
NS
Not Submitted
PO
Purchase Order
HD
On Hold
PN
Pending
SS
Suspended
IN
deleted.
NOTE: An email notification is sent to the requester when an item is edited or deleted in the buyer
queue if the requester chooses to be sent a notification.
HINT: To mark all line items for a requisition, click on the Select for PO heading.
This
6. Once the purchase order is processed, it will give you 3 options, to Print, Email or Transmit via
cXML.
5.2.1.1 Printing
Click on the Print icon
from the purchase order processing window to print the purchase order. This will
open the purchase order in Adobe and a hard copy can be printed.
NOTE 1: The purchase order is standard but can be customized using Crystal Report writer.
NOTE 2: For Great Plains, Axapta, and Navision installs, the tax information has been added
to the Standard Purchase Order Report.
5.2.1.2 Emailing
Click on the Email icon
from the purchase order processing window to email a copy of the purchase
order. The email processing page will open, and you can customize the email message, subject and the to
and from name and email addresses. Emailing will send the purchase order in a PDF, Excel or Word format.
email is setup there, you can manually type the email address before sending. A To email address
is required in order to send.
4. Email from Name/Email address: This information pulls from the user information setup in
ReQlogic.
5. Send me a copy: Check this box if you want a copy of the email to be sent to you as well.
6. Email Content Subject/Body: The email subject and body are standard email text setup under
Customizations ! Email Message. The message and subject can be modified prior to sending.
7. Send Email: Click the Send Email button to send the purchase order via email.
purchase order via cXML. A PO URL needs to be defined for the PunchOut vendor in the Setup Tasks !
PunchOut Catalog Setup in order to send a purchase order to the vendor via cXML.
that some lines can no longer be appended is displayed. Buyers must then either delete that ignored lines, or
edit the lines by removing the Append to PO value and include the lines on a new purchase order.
This functionality is available for Microsoft Dynamics SL and Microsoft Dynamics GP. Access to this
functionality is controlled through Access Rights. Once a user is given access to this functionality, that user
can select any existing purchase order in the system that still accept appended lines.
5.3 Fulfillment
Sometimes, there are enough items in stock to cover a requisition request. Instead of creating a new
purchase order to order more of that item, you can fulfill a requisition from quantity in stock.
To select an item from inventory, the buyer can change the status of the line from Approved (AP) to Fulfilled
from Inventory (IN).
1. Click on the blue diamond Status indicator
3. The buyer can change the status of the requisition line to Fulfilled from Inventory
4. Adjust the quantity you want to fulfill from inventory. The default number is the quantity from the
requisition.
5. Select the Site Id and Bin # from which you want to fulfill.
6. Click Submit. Depending on the set up of ReQlogic, a batch is created in the Microsoft Dynamics
products Inventory module. Once this batch is released and posted, this will release these items
from inventory. The next requisition line that the buyer processes for that same inventory item will
automatically reflect the new reduced available quantity.
NOTE: If Require Verification is checked on the General Settings page, inventory fulfillment
becomes a two-step process. See the Physical Fulfillment section for more information.
There are several exceptions to the process of fulfilling from inventory:
ReQlogics inventory fulfillment process does not support the fulfillment of serial and lot tracked
items. Batch inventory transactions cannot be created from ReQlogic for these types of items,
although the status of requisition lines containing these items can be changed to Fulfilled from
Inventory.
For ReQlogic integrations with Microsoft Dynamics NAV and Microsoft Dynamics AX, batch
transactions for inventory fulfillment cannot be created from ReQlogic, although the status of
requisition lines can be changed to Fulfilled from Inventory.
For Microsoft Dynamics GP implementations, the bin from which items are fulfilled cannot be
selected on the Change Status dialog box. Items are automatically fulfilled from the default bin for
that item.
For Microsoft Dynamics SL integrations, users can assign reason codes to inventory fulfillment
transactions. The Reason Code field is available on the Change Status pop-up window. The field is
not required but has a lookup into the Microsoft Dynamics SL reason code table and flows to the
Microsoft Dynamics SL Inventory Issues page. When a Reason Code is attached to a fulfillment
transaction, the Account and Subaccount default from the Reason Code setup if account and
subaccount values are associated with the reason code in the reason code maintenance page.
In the case that only a partial quantity is fulfilled, the remaining quantity can simply stay in the queue for later
fulfillment, or be marked for cancellation, in which case it is put back in the Buyer Review and Selection
queue.
NOTE: In Microsoft Dynamics AX installations, the inventory fulfillment functionality is limited to updating
the item status. Inventory transactions are not created by ReQlogic.
1. If there is a long list of items to fulfill, you can use the filter criteria to restrict the items you see.
2. Enter the quatity you want to fulfill in the Qty Fulfilled field.
3. If the quantity to be fulfilled is less than the quantity requested, click the Cancel Remaining Qty
checkbox to cancel the remaining quantity.
4. Save This button updates the database according the Qty Fulfilled and Cancel Remaining Qty
columns. An inventory batch is either created or appended with the resulting transactions.
2005 Tectura Corporation
5. Fulfill all Items This button updates the Quantity Fulfilled column with the quantity requested.
The database is not updated until the Save button is pressed.
6. Cancel all Items This button updates flags all items for cancellation of remaining quantity. The
database is not updated until the Save button is pressed.
Inventory account (InvtAcct) and Inventory Subaccount (InvtSub) default from the item site master
record (ItemSite)
COGSAcct and COGSSub default from the Inventory Setup record (Issues Acct/Sub) as they would
during a manual Microsoft Dynamics SL Issues transaction. Functionality has been added to
ReQlogic to facilitate customizing the default COGSAcct and COGSSub. ReQlogic will attempt to
use the value in field Rsvd06 as the COGSAcct, and the value in field Rsvd02 as the COGSAcct.
Those values can be populated using a ReQlogic customization according to custom business rules.
ReQlogic will use the Rsvd06 and Rsvd02 fields only when a value has been populated in them. Its
also possible to override one field and not the other. For example, if the Rsvd06 field on the ReqLine
is blank, but the Rsvd06 field has a Subaccount value, ReQlogic will default COGSAcct from
Inventory Setup, and COGSSub from the field Rsvd02 on the Requisition line.
The Fields (Acct and Sub) will default from the requisition line (GLAccount/GLSub). In cases, where
one or both of the fields are blank, ReQlogic will use the default values from inventory setup for the
missing field, as would happen during a manual issues transaction in Microsoft Dynamics SL.
6 Receiving
This section describes the functions applicable to Receiving in ReQlogic.
Transactions ! Receiving
Online receiving enables users to create receipts for items on their requisitions. Receipts can then be viewed
on the Receipts tab of the requisition document.
Receipt options on the General Setting page control the receiving process in ReQlogic. See the General
Settings for more information. Access to the Qty Issued field and the Receive and Issue All button
requires that the user have the resource Can issue inventory while receiving included in the users access
profile. Without these rights, the field and the button are disabled. See the Access Rights section for more
information.
NOTE: The Date on the Receiving page allows the user to select a receivings date other than
the current date. This allow back dating of receivings in the Microsoft Microsoft Dynamics product.
The following is the general flow of the receiving process:
1. The user creates a requisition and submits it for approval.
2. The requisition is approved and routed to the buyer for processing.
3. The buyer converts the approved requisition to a purchase order.
4. The purchase order is communicated to the vendor.
5. Items are shipped and are received by the user.
6. The user creates a receipt in ReQlogic indicating the quantity received. Users can use the requisition
number, the purchase order number, or the vendor to locate the items to be received.
7. If appropriate, the user can track the serial numbers of the receipts in ReQlogic. This is done by
clicking the Serial icon on the receipt line.
8. ReQlogic creates a corresponding batch receipt in the Microsoft Dynamics product in real-time.
9. If the items received are inventory items, the user has the option to enter the issue quantity, which
creates an issue batch transaction in the Microsoft Dynamics product.
10. Receipt information is visible on the Receipts tab in the requisition document.
NOTE: For Microsoft Dynamics NAV implementations, ReQlogic does not create the batch
transactions described in steps 8 and 9 above.
a. Doc Nbr: This is the ReQlogic document number. The lookup will display all requisitions that
the user entered and which a purchase order was issued against.
b. PO Nbr: This is the Purchase Order number that was issued when the buyer created the
purchase order in ReQlogic.
c.
Vendor: This will display all vendors that are on Purchase Orders that were created for
requisitions entered by this user.
c.
PO Nbr: This is the Purchase Order number that was issued when the buyer created the
purchase order in ReQlogic.
d. Vendor: This will display all vendors that are on Purchase Orders that were created.
2. QTY Received: Enter the quantity of the item received.
3. QTY Issued: Enter the quantity you want to issue. If the item is an inventory item, the user can issue
and receive the items at the same time.
4. Serial: Click on the Serial icon to open the serial number entry window where the user can enter the
serial number of this item(s).
5. Receive All: Clicking the Receive All button will automatically fill in quantity to receive all quantities.
6. Receive and Issue All: Clicking the Receive and Issue All button will automatically fill in quantity to
receive and issue all quantities.
7. Save: Enter save if youve entered a quantity received or issued. Saving will create the receiving
and, if applicable, the issuing transaction in the Microsoft Dynamics ERP product. The receipt
number can be viewed on the Receipts tab of the requisition.
7 Expenses
This section describes the functions applicable to the Expense module in ReQlogic.
1. New Line: From the Summary or Details tab, click New Line when you wish to add a detail line that
contains an expense item to the document.
2. Item Id (required): This is the expense item. The lookup
3. Description (required): This displays the default description of the expense item. It can be edited by
the user.
4. Vendor part #: If applicable, the vendor part number assigned to this item will be displayed. You can
select an item by the Item Id (above) or by Vendor Part #.
5. Expense type (required): This identifies the type of expense. There are two choices from the drop
down list:
a. Paid by employee This is an expense incurred by the user. This expense type will
generate a voucher in the Microsoft Dynamics product when the expense is approved.
b. Corporate account This is an expense paid for through a corporate account. This
expense will be listed on the expense document report, but will not generate a voucher.
6. Quantity (required): Enter the quantity of the item expensed.
7. Unit (required): Enter or accept the default unit of measure for the item.
8. Price (required): Enter or accept the default price for the item. If the item was setup as fixed price,
the price cannot be overridden.
9. Total for item: The price of the item is multiplied by the quantity multiplied by the unit of measure.
10. Company (required): The company for which the expense is created defaults from the header
information.
11. Ship to: This is the site associated with the expense. Accept the default or use the lookup to select a
different site. The Id defaults first from General Settings then from the ReQlogic Catalog item.
12. Project: Identifies the project for which the expense is created. This field is only used if the Project
module is installed. A value can default from the header information.
13. Task/Cost Category: Identifies the task/cost category for which the expense is created. This field is
only enabled if the Project module is installed and defaults from the header information.
14. GL Account (required): The General Ledger account for the expense defaults from General Settings
or from the ReQlogic Catalog Item.
15. GL Subaccount (Microsoft Dynamics SL only): Displays the General Ledger subaccount updated by
the amount of the transaction. This field defaults from the project and task if they have been
selected.
16. Tran. Date (required): Enter the date that the expense was incurred. The lookup
will display a
valid calendar from which the user can choose the date.
17. FBT (Microsoft Dynamics NAV only): This field enables the user to enter an FBT percent value. For
example, if a meal expense was for 10 people, 6 of the 10 were customers, and 4 of the 10 were
employees. The user would enter an FBT value of 60. This will cause the application to split this line
when Microsoft Dynamics NAV is updated. The FBT portion will be included on a separate line and
its GL Code set to the FBT Account assigned to the expense item in the ReQlogic Catalog Setup
page.
2005 Tectura Corporation
18. Attachments: Click Upload to add a file to the expense document detail line. Any type of file can be
attached.
19. Notes: The requester can add notes to the expense document detail line. Notes can be entered in
the following two areas:
a. General Notes Designed to provide more information to the Reviewer.
b. Voucher Notes Designed to provide information to be passed to the voucher.
20. Save/Cancel: Click Save this item to save the detail line to the expense document. This will also
perform data validations. Click Cancel changes to cancel the changes made to the detail line item.
21. Copy: Click the Copy to new line icon
next to the line item if you want to create a new line with a
or arrow keys
c.
d. Save/Cancel: Click Save to save changes made to the expense document header. Click
Cancel to discard any changes made to the expense document header.
3. To edit Detail Line information:
a. To delete the line item, click the delete button
b. Click the edit button
next to the line item you want to edit. When clicked, it will open the
expense document line so the user can edit the line item. Edit will not be enabled once the
expense document has been submitted.
c.
Click Remove this item button to delete the detail line from the expense document.
If any email triggers are turned on, an email notification will be sent. See the ReQlogic Administrator section
for more information on email notification.
1. Step Nbr: This is the number of the steps, in order, the document will be routed.
2. Reviewer Name: This is the name of the user who will review the expense document for the routing
step.
3. Action taken: Action taken by the reviewer.
4. Delegate To: If the expense document was delegated, this field will display the reviewer the expense
document was delegated to.
5. Reviewer Comments: Displays any comments the reviewer added to the expense document during
the review process.
6. Date/Time: This displays the date and time the reviewer reviewed the expense document.
next to the
expense you want to review. This will open the expense in the My Expenses page in a summary view. The
reviewer can then view the details tab, the routing tab and the status tab. The last tab Approval Options is
where the reviewer can delegate the expense to another user or add comments.
From the Details tab, click the Edit link for the line you want to edit.
When clicked, the Edit link will enable the Save this item, Cancel changes and Remove this item buttons.
It will also enable lookup functionality on the fields where applicable.
2005 Tectura Corporation
i.
NOTE: If a line item does not have a checkbox next to it, you do not have
approval rights to that line item. This is based on the routing policy criteria.
b. In the Approval Options tab, add any comments about the rejection.
c.
d.
2. If the applicable policy routing step does not allow line level approval, you must reject the expense
document as a whole.
a. In the Approval Options tab, add any comments about the rejection.
b. Click the Reject button in the header.
NOTE: If line level approval is not allowed, the checkboxes next to each line item will be
inactive, and you will not be able to check or uncheck them.
3. After the document has been rejected, you will be taken to My Approvals page.
NOTE: If a line item does not have a checkbox next to it, you do not have
approval rights to that line item. This is based on the routing policy criteria.
b. In the Approval Options tab, add any comments about your review.
c.
2. If the applicable policy routing step does not allow line level approval, you must approve the expense
document as a whole.
a. In the Approval Options tab, add any comments about your review.
b. Click the Approve button in the header
NOTE: If line level approval is not allowed, the checkboxes next to each line item will
be inactive, and you will not be able to check or uncheck them.
3. After the document has been approved, you will be taken to the My Approvals page.
Excel spreadsheet
Bank statement
Importing transactions from an online bank or credit card account is a 3-step process. First you download
the transactions from your online account and save that file to your local hard disk. Second, you import the
file into ReQlogic. Finally, you review the imported transactions and match them with expense items to
complete the import process.
Step 1: Download Transactions
7. Log into the web site of your online bank or credit card.
2005 Tectura Corporation
8. Download transactions to your local hard disk. Make sure you select either MS Money (OFX) or
Quicken (QFX) as your desired export file format.
Step 2: Import Transaction File
1. File Type: Select OFX/QFX MS Money or Quicken file format.
2. User: Defaults with the users login. Only Buyers and Super Users can change the user. The user
must have a valid Vendor Id assigned in User Setup or an error will result when the Import button is
clicked.
3. Description: Enter a Description that ReQlogic will use as the description for the expense report that
will be created.
4. File Location: Browse to and select the transaction file that you want to import.
5. Accept duplicate file name: Mark the checkbox if you want to import a file that has the same file
name as a previously imported file.
6. Click Import to import the file.
Step 3: Review and Match
1. Expense type (required): This identifies the type of expense. There are two choices from the drop
down list:
a. Paid by employee (default) This is an expense incurred by the user. This expense type
will generate a voucher in the Microsoft Dynamics product when the expense is approved.
b. Company account This is an expense paid for through a company account. This expense
will be listed on the expense document report, but will not generate a voucher.
2. New Item Id: (required): This is the expense item. The lookup
3. Click the link Apply Item Id to this line to match the expense with the Item Id displayed. You do not
need to import every line in the file. Only those transactions that have been matched with and Item
Id will be imported. Be careful, you cannot change an Item Id once it has been applied. If you make
a mistake, you can either cancel the import process or change the Item Id once the transaction file
has been imported as an Expense Report.
NOTE: Only positive amounts in your transaction file can be imported. Negative amounts
(credits) are displayed for your information but cannot be imported.
4. Click the Import button to import the file or click Cancel if you wish to abandon the import of this
transaction file.
A new expense report is created using the information that was imported from the spreadsheet. It can now be
displayed and reviewed/submitted under Transactions ! My Expenses.
Users have the ability to enter quotes after they have been manually obtained from vendors. If a
quote has been obtained in this manner, the price can also be entered here.
3. Upon clicking Next, a supplier selection page opens. Suppliers who have been assigned to the
selected items via their supplier profile are already listed. See Section 2.1.10 for further information
about setting up suppliers and assigned items. To add other suppliers, use the RFQ Supplier list. If a
manually obtained quote is being entered, select the vendor associated with the quote and delete the
suppliers already listed.
4. Upon clicking Next, the notification option page displays. Users can select notification options and
make attachments available to suppliers.
NOTE: If manual quotes are obtained from non RFQ Suppliers, this step in the process is
skipped.
5. Click the Finish button. Requests for quotes are displayed on the Quotes tab. When suppliers
respond to a request, the information is updated on the Quotes tab. Multiple quote responses are
listed by lowest price first.
Any requisition line that contains an open request for quote has an icon appearing on the Summary tab.
6. The user accepts a quote by clicking on the submitted price on the Quotes tab. The quoted price
then becomes the requisition line price.
NOTE: The ReQlogic administrator should create a separate instance of the ReQlogic web
components that is configured specifically for suppliers to log into the portal.
Suppliers can perform two tasks once they log into the supplier portal:
View history
To submit a quote for a requisition line, the supplier can enter a price and click the Submit Quotes button. A
vendor part number and a comment can also be entered. To decline an RFQ for a requisition line, the
supplier clicks the decline button
, and the line will move to the View History page. An email notification is
sent to the user who created the RFQ when a quote is submitted.
The View History page displays all RFQs that are not currently open. This includes the RFQs that the
supplier had replied to, the declined RFQs, as well as the expired open RFQs. RFQs on this page can be
sorted by the Reply By date or the Request Number.
9 Budgets
This section describes the functions applicable to the Budget module in ReQlogic.
9.1 Introduction
ReQlogic allows you to associate requisitions with budgets. The budget source can be a budget defined in
the Microsoft Microsoft Dynamics product, or you can create a budget in ReQlogic. Requisition lines from a
submitted requisition are committed to active budgets when information on the requisition lines matches the
budgets criteria, such as a project or a GL account. The default date used for the commitment is the
Required By date on the requisition line. If no Required By date is defined, the requisition date on the
requisition header is used.
The budget source is selected on the General Settings page. In addition, for budget sources that are defined
in a Microsoft Dynamics product, an Over Budget Action is also selected. The Over Budget Action
determines how over-budget requisitions will be handled and can be No Action or Warning Message.
For each of the Microsoft Dynamics product budget sources, budgets can be reviewed from the requisition
line by double-clicking on Budget Inquiry icon. Access to the Budget Inquiry function is controlled using
Access Rights under the Administration menu.
Commitments to budgets and the type of information displayed on the Budget Inquiry vary by budget source.
Details for each budget source follows.
The following is a sample Budget Inquiry window for a Microsoft Dynamics SL project budget.
All updates or additions to requisition lines are validated and committed to the appropriate budgets. If an
update to a requisition line causes it to no longer be applicable to a budget, the commitment is reversed from
that budget. The deletion, rejection, or recalling of a submitted requisition line will also cause commitments to
be reversed from applicable budgets.
Budgets can be set up based on amount, quantity, or both. Budgets are time sensitive and can be configured
to validate at the period level, yearly level, or both.
or arrow keys
2. Click the Edit button. The Edit button must be selected in order to edit a department in Department
Setup. When clicked, it will enable the Save, Delete, and Cancel buttons. It will also enable lookup
functionality on the fields where applicable.
3. Select Delete to delete the entire department record.
4. Make any necessary changes.
5. Click Save to save the changes made. Click Cancel to discard any changes made to the department
3. Distribute: If the validation level is defined at the period level, click the Distribute button to distribute
the yearly budget amount evenly across the twelve budget periods.
4. Validation Level: The validation level determines if the validation of requisition lines against the
budget will occur at the period level, yearly level, or both.
5. Yearly Budget Quantity: If the budget type is based on quantity, enter the entire budgeted quantity
for the year.
6. Distribute: If the validation level is defined at the period level, click the Distribute button to distribute
the yearly budget quantity evenly across the twelve budget periods.
7. Enforcement Level: The enforcement level determines how over-budget requisitions will be
handled. Options are:
a. No enforcement: Allow the commitment of all requisition lines to the budget, even
requisition lines that are over budget.
b. Warning message only: Display a warning message when a requisition containing overbudget lines is submitted, but allow the commitment of the over-budget lines. The warning
message listing the exceeded budgets will display. A warning symbol is also displayed next
to the status on the requisition lines that exceed the applicable budgets. Clicking on the
symbol displays a list of exceeded budgets. This symbol serves as a visual queue to
reviewers and buyers.
c.
Reject over-budget transactions: Prevent the submission of requisitions that contain overbudget lines. A message listing the exceeded budgets will display.
8. Period: Identifies each of the twelve periods that are used if budget validation is defined at the period
level.
9. Date Range From/To: Identifies the date range that defines a budget period.
10. Budget Amount: Defines the budgeted amount for a period. This amount can be modified.
11. Budget Quantity: Defines the budgeted quantity for a period. This quantity can be modified.
12. Actual Amount: Displays the actual amount that has been committed to a budget for the period.
13. Actual Quantity: Displays the actual quantity that has been committed to a budget for the period.
14. Available Amount: Displays the budgeted amount for a period still available. This amount cannot be
less than zero.
15. Available Quantity: vailable Displays the budgeted quantity for a period still available. This quantity
cannot be less than zero.
16. Total Budget Amount: This is the sum of all period budget amounts.
17. Total Budget Quantity: This is the sum of all period budget quantities.
18. Total Actual Amount: This is the sum of all period actual amounts.
19. Total Actual Quantity: This is the sum of all period actual quantities.
20. Total Available Amount: This is the sum of all period available amounts.
21. Total Available Quantity: This is the sum of all period available quantities.
The spreadsheet format must be based on Budget spreadsheet that is located in the Records Import File
folder in the default ReQlogic installation directory.
This module cannot be used in conjunction with the GL Distribution option that permits users to allocate a
single requisition or expense line among multiple GL account codes. If Analytical Accounting is active, each
requisition or expense line may have only one GL account code but many transaction dimension
assignments.
A second General Settings option determines whether Analytical Accounting transaction dimensions are
validated as each requisition is saved or if validation is delayed until the requisition is approved and in the
buyer queue.
The purpose of delaying validation is to accommodate implementations that require transaction dimensions
to be valid at the time the associated lines get to the buyer, as well as for implementations that dont allow
typical users access to Analytical Accounting and require that dimensions and their assignments only be
maintained by the buyer. Validation for expense report lines is always done when the entry is saved
regardless of the validation option selected for requisitions. A requisition cannot be converted into a purchase
order, or an expense document into a voucher, until any Analytical Accounting validation error is corrected.
If the Analytical Accounting window is not opened prior to saving a new requisition or expense line, ReQlogic
will auto populate the window with any default or fixed values in the background as part of saving the line.
11.2.2 Department/Users
This report lists departments and the users that belong to each. Accessible from both the Department Setup
page and General Settings page.
11.3.6 Receipts
Reports & Inquiries ! Receipts
This report displays information all receipt lines associated with the filter criteria entered.
11.3.7 Quotes
Reports & Inquiries ! Quotes
This report lists request for quote information for all requisition lines that match the filter criteria entered.
11.3.10
Expense Transactions
11.3.11
Serial Numbers