Site-Wide Profile Items
The Site-Wide Profile Items page is used to configure and update settings that apply to the entire VPO system. On this page, the administrator can configure the URL path for the Punchout Shopping item on the Action Bar in Purchasing's Requisition Listing page (Purchasing > Entry & Processing > Requisition Processing > Requisitions). Clicking the item displays the Start New Order page in VPO.
The administrator can also use the Site-Wide Profile Items page to set up additional IP addresses and configure information regarding the test and live environments.
Menu Path: To display the page, click Site-Wide Profile Items on the Administration menu.
VPO Environments
VPO provides the ability to work in the following environments:
Test Environment | Enables you to test connections with vendors and train users without actually making purchases. |
Live Environment | Enables you to use VPO for placing purchases with vendors. |
When your organization is ready to allow users to shop, the administrator can switch VPO from the Test Environment to the Live Environment.
Fields
Fields | Description |
|---|---|
URL for Punchout Access | URL for the Live Environment of VPO accessed by the Punchout Shopping action item located in Purchasing > Entry & Processing > Requisition Processing > Requisitions. |
URL for Test Punchout Access | URL for the Test Environment VPO accessed by the Punchout Shopping action item located in Purchasing > Entry & Processing > Requisition Processing > Requisitions. |
Test or Live Environment | Field indicating whether the VPO environment is currently test or live. Enter: T - for Test environment. |
Active Directory Login | Field indicating whether your organization is using a Windows username and password to log in. Enter: Y - for Yes if you are using a Windows username and password for logging in. N - for No if you are not using a Windows username and password for logging in. |
Active Directory Domain | The domain name for the Active Directory server. Enter X if not using Active Directory. |
Path to LDAP directory | The IP address and port number used in Active Directory authentication. Enter X if you are not using Active Directory. |
3 character Equal Level Punchout Code | Enter the code identifying your site for use in VPO's Equal Level feature. If you are uncertain of the code to use, contact your system administrator for VPO. Character/3 |
Vendor Punchout (VPO) log recycling and purging
If users allow VPO to write to debug logs without ever deleting them, they grow to very large sizes, making it difficult to review the logs and filling up server space. Users can configure when new VPO log files should be created and decide whether to purge old logs.
Generate Log Files
To generate log files, the web.config file must have Debug set to Y. In Site Wide Profile Items, there are two new fields for users to configure, and one new read-only field:
Number of Days in Logs: Defaults to 30 days.
VPO uses the value in this field to determine when to create a new log file. Files affected are Web/errorlog2.txt and Web/errorlog_createreq.txt.
Purge Logs After (Days): This field defaults to 0 (zero) days, which disables purging.
VPO uses the value in this field to determine when to delete old log files. Files affected are Web/errorlog*.txt, Web/errorlog_createreq*.txt, and PUNCHPO/errorlog.txt. Set this field to a value larger than the Number of Days in Logs to enable purging.
Current Logs Filename Data: This field is informational only. It contains the most recent date value being used for log file writing.
File purging is attempted by the SPISender process after purchase orders have been processed. SPISender.exe, the process that sends completed/printed purchase orders to the vendor, will continue to create a new log file daily.