7 Supplier Administration
The following topics are covered in this chapter:
Alerts
Select the Alerts option from the Admin drop-down list. The following options are available in the left pane:
Mailing Lists
Mailing lists can be used to create a predefined list of recipients to receive alerts.
To create a mailing list:
-
Select the New Mailing List action. The New Mailing List tab opens.
-
Enter the name of the mailing list. This field is mandatory.
-
Select the list of users from which you can choose the recipients in this mailing list. You can select Sites, Suppliers, or Sites & Suppliers. Open the Recipients tab to select from the list of available users.
-
Select the Save action.
Manage Alert Status
This option enables you to view the alert status codes and descriptions defined for each. To edit the list, select the Edit action. You can change the descriptions and add new status codes.
Figure 7-1 Alert Status Page
Manage Alert Response Status
This option enables you to view the alert status response codes and the descriptions defined for each. To edit the list, select the Edit action. You can change the descriptions and add new status response codes. The Alert Response Status page has the same format as the Alert Status page shown in Figure 7-1.
Suppliers & Sites
Billing Codes
This option is used to define the billing codes used when creating a new supplier. The billing code determines how costs are calculated during the registration process. Billing codes are optional. If billing is not applicable or a portal, a code could be defined with a zero charge.
During the registration of a new supplier in the Supplier module, the values in this table are used to determine the cost charged for the registration:
Registration Cost equals Fixed Price plus (Charge Per Site multiplied by the number of sites registered)
For more information, see the Oracle Retail Supplier Evaluation Cloud Service Supplier User Guide.
Figure 7-2 Billing Codes Page
To edit the list of billing codes, select the Edit action. The table opens in edit mode. The code and any existing descriptions cannot be edited.
To add a new billing code, click Add. A new row is added to the table. Enter the code, charge per site, fixed price, description in the default language. Enter any translations. Select the Save action.
Supplier Statuses
This option is used to define the statuses that can be associated with the registration of a supplier. The codes are defined by the system; new codes cannot be added. To edit the existing codes, select the Edit action. The table opens in edit mode. Any translations that do not already exist can be added. No other changes can be made.
Figure 7-3 Supplier Statuses Page
Site Statuses
This option is used to define the statuses that can be associated with a site. The statuses are defined by the system; new statuses cannot be added. To edit the existing statuses, select the Edit action. The table opens in edit mode. Any translations that do not already exist can be added. No other changes can be made.
Figure 7-4 Site Statuses Page
Business Categories
Select the Business Categories option in the left pane. The list of defined business categories appears in the right pane. Each top-level category can be expanded to show its child categories.
Figure 7-5 Business Categories Page
To edit a category entry, select the entry in the left pane and then select the Edit action in the right pane. The category opens in edit mode. The descriptions can be edited. For an example of the content of this page, see Figure 7-6.
To create a new top-level category:
-
Click Create new top-level category. The Business Category Details page opens.
Figure 7-6 Add Business Category Details Page
-
Enter the details for the new category:
-
Enter the code. This is a mandatory field.
-
Enter the description for the default language. This is a mandatory field. Enter any translations.
-
-
Select the Save action. The business category is added to the list of categories.
-
To add child categories, select the top-level category and then select the Add Child Category action.
-
Enter the details for the child level and select the Save action.
Supplier Types
This option is used to define the types of suppliers that can be created.
Figure 7-7 Supplier Types Page
To edit the list of supplier types, select the Edit action. The table opens in edit mode. For existing supplier types, only the translated descriptions that do not already exist can be edited. To add a supplier type, click Add. A new row is added to the table. Enter the new supplier type and description in the default language. Enter any translations. Select the Save action.
Site Types
This option is used to define the types of sites that can be created.
To edit the list of site types:
-
Select the Edit action. The table opens in edit mode. For existing site types, only the translated descriptions that do not already exist can be edited.
-
To add a site type:
-
Click Add. A new row is added to the table.
-
Enter the new site type and description in the default language. Enter any translations.
-
-
Select the Save action.
Maintenance Audit Reasons
This option is used to define the reasons why a maintenance audit needs to take place. The Maintenance Audit Reasons page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of reasons, select the Edit action. The table opens in edit mode. For existing reasons, only the translated descriptions that do not already exist can be edited. To add a maintenance audit reason, click Add. A new row is added to the table. Enter the new reason code and description in the default language. Enter any translations. Select the Save action.
Invoicing Systems
Invoicing systems are used in the Billing Details area of the Supplier and Site records to assign alternative account codes, such as the supplier's account number in the retailer's corporate purchasing system. This option is used to define the available invoicing systems. The Invoicing Systems page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of invoicing systems, select the Edit action. The table opens in edit mode. For existing invoicing systems, only the translated descriptions that do not already exist can be edited. To add an invoicing system, click Add. A new row is added to the table. Enter the new invoicing system code and description in the default language. Enter any translations. Select the Save action.
Supplier Top Grades
This option is used to define the grades that can be associated with a supplier for an audit/visit, for example, A, B, and C. The Supplier Top Grades page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of grades, select the Edit action. The table opens in edit mode. For existing grades, only the translated descriptions that do not already exist can be edited. To add a new grade, click Add. A new row is added to the table. Enter the new grade code and description in the default language. Enter any translations. Select the Save action.
Site Top Grades
This option is used to define the grades that can be associated with a site for an audit/visit, for example, A, B, and C. The Site Top Grades page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of grades, select the Edit action. The table opens in edit mode. For existing grades, only the translated descriptions that do not already exist can be edited. To add a new grade, click Add. A new row is added to the table. Enter the new grade code and description in the default language. Enter any translations. Select the Save action.
Reference Statuses
This option is used to define the reference codes that can be associated with a supplier site, for example, the health mark codes used in the UK or the FDA registration numbers used in the US. The Reference Status page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of statuses, select the Edit action. The table opens in edit mode. For existing statuses, only the translated descriptions that do not already exist can be edited. To add a new status, click Add. A new row is added to the table. Enter the new code and description in the default language. Enter any translations. Select the Save action.
Reference Types
This option is used to define the reference types, or certificate types, that can be associated with a supplier.
Figure 7-8 Reference Types Page
To edit the list of reference types, select the Edit action. The table opens in edit mode. For existing types, only the translated descriptions that do not already exist can be edited. To add a new type, click Add. A new row is added to the table. Enter the new type code and description in the default language. Enter any translations. Select the Save action.
Business Units
This option is used to define the classifications of suppliers and sites.
Figure 7-9 Business Units Page
To edit the list of business units, select the Edit action. The table opens in edit mode. For existing business units, only the translated descriptions that do not already exist can be edited. To add a new business unit, click Add. A new row is added to the table. Enter the new business code and description in the default language. Enter any translations. Select the Save action.
Currencies
This option is used to define the supported currencies, for example, Sterling and Dollars. The Currencies page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of currencies, select the Edit action. The table opens in edit mode. For existing currencies, only the translated descriptions that do not already exist can be edited. To add a new currency, click Add. A new row is added to the table. Enter the new currency code and description in the default language. Enter any translations. Select the Save action.
Countries
This option is used to define the list of countries used throughout the system (in addresses, countries of origin, countries of manufacture, and so on).
The maintenance of Countries also incorporates Areas and Regions. Areas are geographical areas that are not countries, but may be referenced in a similar way within the system. For example, the country of origin of a product may be a country or may be an area, such as the Atlantic Ocean.
When the user selects from the pick-list of countries, it either contains a list of just Countries (for example, where completing an address), or Countries and Areas (for example, where selecting a country of origin).
A list of Regions can be maintained against a Country to provide, for example, the states or countries of that country. The list can be used to provide a pick-list of the states/counties for use when entering the address for that country.
Figure 7-10 Countries Page
To edit a country entry, select the entry in the list and then select the Edit action. A tab opens in edit mode. Translated descriptions that do not already exist and additional regions can be added. For an example of the content of this page, see Figure 7-11.
To add a new country:
-
Select the New Country action. The New Country tab opens.
Figure 7-11 New Country Page
-
In the Details section:
-
Type: Select whether this is a country or area.
-
Code: Enter a code for the country.
-
Country Name: Enter the country name in the default language. This field is mandatory. Enter any translations.
-
Postcode Mask: The Postcode Mark is used to define the format of the postal or zip code for the country. Enter a post code mask to be used for this country.
-
Internet Domain Suffix: Enter the Internet domain suffix used for this country.
-
-
In the Regions section, enter any regions for this country or area. To add a region, click Add. A row is added to the table. Enter the code for the region. Enter a description in the default language. The description is a mandatory field. Enter any translations.
-
Select the Save action.
Other Production Details
This option is used to define the list of production details that can be assigned to a site. The Other Production Details page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of production details, select the Edit action. The table opens in edit mode. For existing details, only the translated descriptions that do not already exist can be edited. To add a new production detail, click Add. A new row is added to the table. Enter the new detail code and description in the default language. Enter any translations. Select the Save action.
Area
This option is used to define the supported areas. The Areas page has the same format as the Supplier Statuses page shown in Figure 7-3.
To edit the list of areas, select the Edit action. The table opens in edit mode. For existing areas, only the translated descriptions that do not already exist can be edited. To add a new area, click Add. A new row is added to the table. Enter the new area code and description in the default language. Enter any translations. Select the Save action.
Delete Supplier
This option is used to delete suppliers. In order for a supplier to be deleted, the following criteria must be met:
-
The supplier has not gone through the registration process, that is, only a supplier with sites at a status of AWAITING REGISTRATION can be deleted.
-
There is no Alert Response record beyond the status of OUTSTANDING for the supplier being deleted.
-
There are no Assessments beyond the status of FUTURE for any of the sites of a supplier being deleted.
To delete a supplier:
-
Select the Delete Supplier option from the Admin drop-down list. The Select Suppliers page appears.
-
To display the list of suppliers, select the icon. The Suppliers to Delete page appears.
Figure 7-12 Suppliers to Delete Page
-
Select the suppliers to be deleted and click Ok. The selections are shown in the right pane.
-
To delete the suppliers, select the Submit action. A dialog box appears to enable you to confirm the deletion. To confirm the deletion, click OK. A batch job is submitted to perform the deletion.
Figure 7-13 Delete Suppliers Confirm Change Dialog Box
Note:
Supplier accounts may also be deleted as a result of deleting all Site accounts individually. For details, see the Oracle Retail Supplier Evaluation Cloud Service Supplier User Guide.
Delete Site
This option is used to delete sites. In order for a site to be deleted, the following criteria must be met:
-
The site has not gone through the registration process, that is, only sites at a status of AWAITING REGISTRATION can be deleted.
-
There is no Alert Response record beyond the status of OUTSTANDING for the site being deleted.
-
There are no Assements beyond the status of FUTURE for the site being deleted.
To delete a site:
-
Select the Delete Site option from the Admin drop-down list. The Select Sites page appears.
-
To display the list of sites, select the icon. The Sites to Delete page appears.
Figure 7-14 Sites to Delete Page
-
Select the sites to be deleted and click Ok. The selections are shown in the right pane.
-
To delete the sites, select the Submit action. A dialog box appears to enable you to confirm the deletion. To confirm the deletion, click OK. A batch job is submitted to perform the deletion.
Figure 7-15 Delete Sites Confirm Change Dialog Box
Note:
Site accounts may also be deleted individually. For details, see the Oracle Retail Supplier Evaluation Cloud Service Supplier User Guide.
Upload Supplier and Site Data
Retailer users with the Upload Administrator authority profile have access to the Upload Data option within the Admin menu for the upload of suppliers and sites.
To upload new suppliers and sites:
-
Select the Import action from the Suppliers List View actions menu. The Data Upload dialog box opens.
Figure 7-16 Data Upload Dialog Box
-
Click Browse to search for the upload file.
-
Enter any comments to describe the reason for the upload.
-
Select whether the system is to automatically send email to the primary contact user of each newly created supplier/site on successful completion of the upload. The email will invite the user to register on the portal. The default is No, which will not send an email.
-
To upload the file, select either the Submit or Submit Go to Manage Batch Jobs action. At this point, the system will create a background job to process the spreadsheet. The spreadsheet used to upload the data will be stored within the Attachments tab of the batch job.
Note:
An email will be sent to the job submitter if the date within the upload file fails validation.
Download Supplier and Site Upload Spreadsheet
Retailer users with the Upload Administrator authority profile also have access to the option to download a blank spreadsheet.
To download the latest version of the upload spreadsheet:
-
Select the Download Blank Spreadsheet action from the Suppliers List View actions menu. An operating system specific dialog box opens with the option to either open or save the file.
-
Select the save option to download the ZIP file to your desktop.
Note:
The ZIP file contains a spreadsheet workbook with the first tab used to upload the data. The second tab contains guidance notes and the remaining tabs contain the valid glossary values.
The column heading text shown on the first tab is in the user's language. If translations are not present for the user's language, the system the portal's default language is substituted. An asterisk (*) is shown in a column heading if an entry is mandatory.
Assessments
Select the Assessments option from the Admin drop-down list. The following options are available in the left pane:
Assessment Questions
Each assessment template is comprised of a series of questions which may be selected from this glossary.
Figure 7-17 Glossary Assessment Question Page
To edit a question, select the question and then select the Edit action. A tab opens with the record in edit mode.
To create a new assessment question:
-
Select the New Question action. The Assessment Question tab opens.
Figure 7-18 New Assessment Question Page
-
In the Details section:
-
Question Id: Enter the ID for this question. The ID must be between 3 and 10 characters and unique. The value cannot be changed once the question has been created. This field is mandatory.
-
Status: The status is set to Deactivated.
-
Question: Enter the question in the default language. This field is mandatory.
-
Sequence: Enter the sequence number for this question. The sequence number is used to set the default order of questions within the assessment template.
-
Question Type: Select the type of question:
-
Universal questions are automatically added to a assessment template. These questions may be removed and individually re-added as required (if configured in System Parameters to allow removal).
-
General questions are manually added to a assessment template from the questions glossary.
-
-
Comments: Enter any comments. This field is not mandatory.
-
-
In the Answers section:
-
Answer Type: Select the type of answers allowed for this question.
-
Includes Comments: If set to Yes, a text field is included in the questionnaire to enable the user to enter any comments.
-
To add an answer choice, click Add. Enter the answer in the default language. This is a mandatory field. Enter any translations.
-
-
Select the Save action.
Assessment Templates
Assessments provide a means for the retailer to assess their suppliers on an on-going (or ad hoc) basis against a set of predefined criteria. Assessments are made up of a series of questions which may be answered by the suppler as a self-assessment or completed by the retailer.
Any number of types of assessment can be configured, with the option to use weighted scoring for the overall grading of suppliers' responses. On completion of a assessment, the next one can be automatically scheduled based on a predefined periodic or quarterly frequency.
Assessment templates define the rules that control the behavior of the different types of assessments. Every assessment is created from a template which defines the rules for how it behaves within the system, that is, the set of questions and permitted answers, the setting of basic default values, and whether certain fields are used or hidden.
Figure 7-19 Glossary Assessment Templates Page
To edit a template, select the entry and then select the Edit action. A tab opens in edit mode to enable you to edit the template. For an example of the content, see Figure 7-20.
To create a new template:
-
Select the New Assessment Template action. The New Assessment Template tab opens.
Figure 7-20 New Assessment Template Page
Table 7-1 describes the fields in the Details section.
Table 7-1 New Assessment Template Fields
Field Description Code
Enter a unique code for this template. This field is mandatory.
Assessment Name
Enter the name for the template in the default language. This field is mandatory. Enter the translations.
Status
The status is set to Deactivated.
Supplier Can Create Assessment
If checked, the supplier user can choose to create this type of assessment. The default is unchecked.
Supplier Can Change Due Date
If the supplier can create this type of assessment and this field is checked, the supplier user may also change the due date of this type of assessment. The default is unchecked.
Supplier Can Complete Assessment
If checked, the supplier user may choose to complete this type of assessment. The default is unchecked.
Approval Required
If the supplier can complete this type of assessment and if this field is checked, the retailer user is required to approve this assessment before the supplier can complete it. The default is unchecked.
Grace Period
Enter the number of days or weeks after the assessment's due date when it becomes overdue.
Overdue Email
If checked, an email is automatically generated to the supplier if the supplier has not completed the assessment by the time it becomes overdue.
Contact Roles
Select the roles for which supplier users receive the notifications if the assessment becomes overdue. The field is mandatory.
Future Date Derived From
These fields are used to control the rules for automatically scheduling subsequent assessments of this type, and when a assessment becomes overdue.
Automate Future versus Auto Schedule
If a assessment’s template is set to Automate Future the system will automatically create the next future assessment of this type for active sites that have previously had this type of assessment and do not already have one currently scheduled, or do have one scheduled but its due date has been reached. This ensures all sites that have this type of assessment always have one scheduled.
If a assessment’s template is set to Auto Schedule, the system prompts the user with the option to auto-schedule the next future assessment of this type for the site when the existing assessment is completed.
Automate Future
Auto Schedule
Default Frequency
Due Day Of Week
Level of Business Category
Enter the number of levels of business category to be recorded for this type of assessment. Set to zero if none are required. This is a mandatory field.
Business Category Required
If checked, the business category becomes mandatory when the assessment is completed.
Comments
Enter a comment regarding this template.
Supplier Evaluation Type
This is used to determine the type of assessment that is scored and potentially included in the integration with Merchandising.
Once the template has been made active, the type cannot be changed.
-
Set the questions for this type of assessment in the Questions tab using the tables of questions for Universal, General, and Ad Hoc Questions:
-
Universal questions are automatically added.
-
General Questions are selected from the glossary of Assessment Questions.
-
Ad Hoc questions can be entered specifically for this type of assessment.
Once the questions have been added, the Refresh Preview action can be used to show the assessment as it will be presented to the supplier.
-
-
Select any scoring rules for this type of assessment in the Scoring subtab.
-
Select the Save action.
Assessment Status
This option enables you to view the assessment status codes and descriptions defined for each. To edit the list, select the Edit action. You can change the descriptions and add new status codes. The Assessment Status page has the same format as the Alert Status page shown in Figure 7-1.
Audits & Visits
Select the Audit & Visits option from the Admin drop-down list. The following options are available in the left pane:
Certification Bodies
Certification bodies are assigned to audits/visits that are carried out by a third-party organization. A certification body defines the details of an organization that carries out an audits. On the Certification Bodies page, the name and contact details of existing auditors and certification bodies are shown.
To edit the details for a certification body, select the entry and then select the Edit action. A page opens in edit mode with the details of the certification body. For an example of the content, see Figure 7-21.
To add a new certification body, select the New Certification Body action. The New Certification Body tab opens. The Name and Type fields are mandatory. The contact details and address may also be entered.
Figure 7-21 New Certification Body Page
Audit/Visit Templates
Audit/visit templates define the rules that control the behavior of the different types of audits and visits. Every audit or visit is created from a template which defines the rules for how it behaves within the system, that is, the setting of basic default values and whether certain fields are used or hidden.
Figure 7-22 Audit/Visit Templates Page
To edit a template, select the entry and then select the Edit action. A tab opens in edit mode to enable you to edit the template. For an example of the content, see Figure 7-23.
To create a new template:
-
Select the New Audit/Visit Template action. The New Audit/Visit Template tab opens.
Figure 7-23 New Audit Template Page
-
Table 7-2 describes the fields in the Audit/Visit Details section.
Table 7-2 Audit/Visit Template Fields
Field Description Active
Check the box if this template is set active when created.
Allowable Audit/Visit Standards
Click the icon to select the standards for this audit/visit.
Allowable Score Options
If scoring is used, click the icon to select the scoring options to use.
Audit/Visit Standards Used
If set to Yes, this type of audit is aligned with a particular standard.
Audit/Visit Template Name
Enter the name for the template in the default language. This field is mandatory. Enter the translations.
Audit/Visit Type
-
Select Internal if the audit/visit is carried out by the retailer.
-
Select Third Party if a third-party auditor or certification body carries out the audit/visit.
Audit/Visit Visibility
This field determines whether the supplier knows in advance of an audit/visit. If Unannounced, the supplier is not notified until it is time for them to collaborate.
Auto Schedule
If set to Yes, a new future audit/visit is automatically scheduled on completion of the current audit/visit.
Business Category Levels Required
If the Business Categories Required field is set to Yes, enter the number of levels of business category to use on the audit/visit record.
Business Categories Required
If set to Yes, a business category is required for this type of audit/visit.
Code
Enter a unique code for this template. This field is mandatory.
Comments
Enter a comment regarding this template.
Cost Recovery
If set to Yes, the all or part of the cost of the audit/visit is recharged to the supplier.
Cost Recovery Comments
If the Cost Recovery field is set to Yes, the amount to be recharged can be entered as a comment.
Create Issues
If set to Yes, issues can be raised against audits/visits of this type regardless of whether the issue is created by the supplier or retailer.
Default Audit/Visit Frequency (months)
Enter the frequency of the audit/visit in months. This is used when auto-scheduling the next audit/visit.
Default Issue Completion (days)
Enter the number of days an outstanding issue must be completed by before being flagged as urgent.
Record Date of Last Audit/Visit
If set to Yes, the site record is updated with the date when the latest audit is completed.
Record Type
Select whether this template is for an audit or a visit.
Scope
This is the summary of the purpose of the audit/visit. This is the default text for the Scope field in the audit/visit.
Score Audit/Visit
If set to Yes, an overall score/grade is required.
Supplier Evaluation Type
This is used to determine the type of audit/visit that is scored and potentially included in the integration with Merchandising.
Once the template has been made active, the type cannot be changed.
Score Mandatory
If set to Yes, scoring is mandatory when scoring is being used.
Supplier Generated
If set to Yes, the supplier can create new audits/visits of this type.
-
-
In the Auditors subtab, select the certification bodies and internal auditors who are allowed to perform the audit:
-
If All is selected, all defined certification bodies or internal auditors are allowed to perform the audit.
-
If Only Allowable is selected, the list of certification bodies or internal auditors is chosen. Click the icon and select the certification bodies or internal auditors.
Figure 7-24 New Audit Template Auditors Subtab
-
-
Select the Checklists subtab. Add any checklists to be used for the audit. When an audit/visit is created, if its template has checklists assigned, the checklists are automatically created as Audit/Visit Checklist records for completion during the audit/visit.
-
In the Attachments subtab, attach any documents to the audit.
-
Select the Save action.
Audit/Visit Issue Types
Audit/visit issue types define the types or levels of non-conformance that can be raised against an audit. An audit/visit template may not be edited once it has been made active; to make any changes it must first be deactivated. The Audit/Visit Issue Types page has the following columns:
-
Set to Yes if the issue type is active.
-
Code for the issue type.
-
Description for the issue type in the default language.
-
Descriptions for each supported language.
Figure 7-25 Audit/Visit Issue Types Page
To edit the list of issue types, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new issue type, click Add. If the issue type should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Auditor Types
Audit types are used to differentiate between individuals (Auditors) and organizations (Certification Bodies). The Auditor Types page has the same format as the Audit/Visit Issue Types page shown in Figure 7-25.
To edit the list of auditor types, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new auditor type, click Add. If the auditor type should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Audit/Visit Risk Levels
Where used, the levels of risk may be assigned to a site based on the type of product the site produces, for example, High Risk and Low Risk. The levels can be used, based on risk level, to vary the frequency of an audit/visit type per site. The Audit/Visit Risk Levels page has the same format as the Audit/Visit Issue Types page shown in Figure 7-25.
To edit the list of risk levels, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new risk level, click Add. If the risk level type should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Audit/Visit Scores
Audit/visit scores provide the scoring or grading options for audits, for example, Red and Green. The Audit/Visit Scores page has the same format as the Audit/Visit Issue Types page shown in Figure 7-25.
To edit the list of scores, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new score, click Add. If the score should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Audit/Visit Standards
Each type of audit can be aligned with a specific standard. The Audit/Visit Standards page has the same format as the Audit/Visit Issue Types page shown in Figure 7-25.
To edit the list of standards, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new standard, click Add. If the standard should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Audit/Visit Statuses
Statuses define the names of the stages of the Audit/Visit workflow.
To edit the list of statuses, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
Figure 7-26 Audit/Visit Statuses Page
Issue Statuses
Issue statuses define the names of the stages of the Issues (non-conformances) workflow. The Issue Statuses page has the same format as the Audit/Visit Statuses page shown in Figure 7-26.
To edit the list of statuses, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
Visit Locations
Only used in visits, the locations are a predefined list of options for specifying where the visit takes place, for example, Head Office or Conference Room. The Visit Locations page has the same format as the Audit/Visit Issue Types page shown in Figure 7-25.
To edit the list of locations, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new location, click Add. If the location should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Visit Reasons
Only used in visits, the reasons are a predefined list of options for why the visit takes place, for example, Audit Follow-up or Complaint Investigation. The Visit Reasons page has the same format as the Audit/Visit Issue Types page shown in Figure 7-25.
To edit the list of reasons, select the Edit action. The table opens in edit mode. Only the translated descriptions can be edited.
To add a new reason, click Add. If the reason should be set active, check the box in the Active column. The code and description in the default language are mandatory fields.
Checklist Templates
A checklist is the breakdown of items to be assessed as part of an audit or visit. The items may correspond to individual clauses in corporate standards or policy documents. A checklist template is the grouping together of checklist questions and their permissible answers to form reusable common questionnaires for completion during an audit.
Figure 7-27 Checklist Templates Page
To edit a template, select the Edit action. The template record opens in edit mode.
To add a new checklist:
-
Select the New Checklist Template action. The New Checklist Template tab opens.
Figure 7-28 New Checklist Template Page
-
In the Details section:
-
Code: A unique Code must be entered when the template is created, after which it is read-only. This field is mandatory.
-
Checklist Name: Enter the name that appear in the audit/visits. The name must be unique. The name is editable after the record has been created. Enter any translations. This field is mandatory.
-
Status: The status is set to Deactivated.
-
General Comments: If set to Yes, a general comments field is included in the checklist.
-
-
In the Questions section: To add questions, click Add. The Select Glossary Questions dialog box appears with the list of available questions. Select questions and then click Ok.
-
In the Block Answer Options section: Allow block answers adds an option to the checklist to allow the user to block answer all the questions with the answers specified here, where it is one of the permissible answers for the question. For example, if block answering is set to Not Assessed, all questions in the checklist that have Not Assessed as one of the answer options are answered in that way. The contents of the Allow Block Answer pick-list are dynamically built based on the set of answers associated to the questions present in this checklist. Any duplicates are excluded.
-
Select the Save action.
Checklist Answers
The sets of available checklist answers are managed using this option.
Figure 7-29 Checklist Answers
Figure 7-30 shows an example of checklist answers.
Figure 7-30 Checklist Answers Example
To edit a set of checklist answers, select the entry and then select the Edit action. The template record opens in edit mode.
To add a new set of checklist answers:
-
Select the New Checklist Answer option. The New Glossary/Answers page opens.
Figure 7-31 New Checklist Answer Page
-
In the Details section:
-
Code: Enter a unique code for this answer set. This field is mandatory.
-
Answer Name: Enter a unique identifier of this answer set in the default language. This field is mandatory. Enter any translations.
-
Answer Type: Select the type of answer presented to the user:
-
Single Choice presents a pick-list.
-
Multi Choice presents a multi-select pick-list.
-
Text presents an auto-expanding text area.
-
-
Include Comments: This field determines a comment is required. If the selected answer type is Text, this field is set to No and cannot be changed.
-
Comments: Use this field to enter a comment regarding this checklist answer glossary.
-
Use Default Answer: If the answer type is Single Choice or Multi Choice, the Use Default Answer option is used to control whether a default value is to be set for this answer when presented in a checklist. If Yes is selected, the Default Answers field presents a checklist of the answers that have been added to the Answers table for one to be selected. If No is selected the selector is hidden.
-
-
The table of answers defines the answer choices and is only presented if the answer type is Single Choice or Multi Choice. To add answer, click Add to add a row to the table:
-
Enter the answer in the default language. This field is mandatory.
-
The N/C Creation field determines whether, when the chosen answer is given to this question, the system should generate an issue for the question.
-
The N/C Type field determines for what issue type an issue is automatically generated. The selection is made from the Issue Types glossary, for example, Critical, Major, Minor, or Recommendation.
-
Enter the descriptions in the supported languages.
-
-
Select the Save action.
Checklist Questions
The sets of available checklist questions are managed using this option.
Figure 7-32 Checklist Questions
To edit a checklist question, select the entry and then select the Edit action. The question record opens in edit mode.
To add a checklist question:
-
Select the New Checklist Question action. The New Glossary/Question tab opens.
Figure 7-33 New Checklist Question Page
-
In the Details section:
-
Id: This is a unique identifier of each question. It is automatically assigned as an incrementing sequence number.
-
Audit Type: Select the type of audit associated with this question from the drop-down list. This field is mandatory.
-
Answer Type: Select the type of answer associated with this question from the drop-down list. This field is mandatory.
-
Section: Select the section of the questionnaire from the drop-down list. This field is mandatory.
-
Question/Text Statement: Enter the question in the default language. This field is mandatory. Enter any translations.
-
Comments: Use this field to enter a comment regarding this checklist question glossary entry.
-
-
In the Answers section: The table of Answers is automatically built based on the selected answer type. The table is only applicable for Single Choice and Multi Choice answer types. For more information, see Checklist Answers
-
Select the Save action.
Checklist Question Colour Management
This option is used to define the rules for color-coding within checklists. The system uses this table to apply to present the text in the specific color if it encountered as part of a checklist question.
To edit the list of colors, select the Edit action. The table opens in edit mode. The color and descriptions can be edited.
To add a new color, click Add. A row is added to the table. Enter the code, color, and description in the default language. Enter any translations.
Figure 7-34 Checklist Question Colour Management
Roles and Permissions
Select the Contact Roles option in the left pane. The Contact Roles page opens.
Figure 7-36 Contact Roles Page
The set of contact roles is configurable. Each portal can build their own set of roles that contacts are to be recorded for at the supplier and site levels. The roles may be set as mandatory, in which case, a contact must be assigned to that role for the supplier/site account to be approved.
Some roles are mandatory because they are used by the system to automatically notify the relevant users as part of the system's workflow, for example, an Audits &Visits Main Contact would be notified when an audit requires action.
Where there are mandatory roles that have not been assigned a contact, the supplier/site administrator is alerted through the Urgent Item Manager (UIM) app.
For more information on adding and editing contact roles, see Managing Contact Roles.
Integration with Merchandising
SE and Merchandising will hold corresponding accounts for suppliers and their individual site locations. The accounts will originate in Merchandising, with new accounts and updates being fed to SE through the Merch Supplier API. The synchronization is one-way only: from Merchandising to SE. This will include the automatic creation of the initial supplier user, for them to complete the supplier registration process in SE.
Supplier and Site Integration
The following system parameters must be set in order to enable the Supplier and Site integration:
-
Check Integration Enabled is set to enabled/disabled accordingly.
-
Configure the Merch API URL and credentials.
-
Set the Integration Interval. Utilize Do not run Integration before and Do not run Integration after to avoid it running during peak times of the day. The default is to run every 90 minutes.
-
Set the account coding rules for the allocation of Supplier and Site codes.
-
Set the default value for the Technologist. This is the contact that is notified of new Merch sites requiring activation.
The nominated default Technologist is recommended to be a user with appropriate additional Admin permissions, who can assign Sites to the required individual Technologists using Global Changes.
Note:
The default Technologist is a regular user account. The client needs to decide what email address they attribute to the retailer user account of the designated default Technologist.
-
Set the default values, first ensuring the value is present in the respective glossary:
-
Business Category
-
Supplier Type
-
Site Type
-
Business Unit
-
-
Set the Merchandising Invoicing System, first ensuring the value is present in the glossary.
-
Set which user role defines the Supplier Administrator role, used when creating the initial supplier user.
-
Set the Site Status mapping rules:
-
The table will be pre-populated with entries for A=Active and I=Inactive, with Active creating new accounts and Inactive triggering auto de-list in SE.
-
-
A prerequisite for the integration to succeed will be that the portal be configured so that GLN codes are non-mandatory for suppliers and sites, as the codes are not currently available in the data sent from Merchandising. Validation will reject the creation of a new supplier/site if GLN codes are configured to be mandatory.
-
If the Merchandising supplier and site codes are to also be used as the SE codes, a prerequisite for the integration to succeed will be that the SE supplier and site coding rules be configured in a way that allows for the Merchandising codes being in the range 1 to 9999999999, in particular, the minimum length parameter.
-
Set the Number of days to keep Outbound Message Queue data purging interval. The default is 90 days.
-
Set the External Primary Language system parameter.
-
Check that the glossaries of Countries in Merchandising and SE correspond. The two character ISO code is used as the key. This mapping is used when populating the Supplier/Site addresses.
-
Configure and additional Regions in the Countries glossary, to match those used in Merchandising. Only UK counties, US states, and CN provinces are added automatically by the data generator.
Inbound Message Queue
If an inbound message fails due to missing or invalid Merchandising data, the message’s status will be set to Failure.
If the data is subsequently added or corrected in Merchandising, that maintenance action will trigger a new message, which will be processed by SE separate to the original failed message.
The inbound message queue will automatically retry the original message, however as the message contains a snapshot of the original data, it will continue to fail with the same data exception. The retry does not re-retrieve data from Merchandising, it simply retries the original message.
Messages at Failure status continue to be retried until they are successfully processed or are manually set to Permanent Failure. The purge routine automatically cleans up Permanent Failure messages, but not Failure messages.
While the auto-retry processing will deal with exceptions due to record locks, it will not deal with data exceptions; for these, the administrator must manually set these messages as Permanent Failure, to be removed next time the purge routine runs.
Note:
It is not feasible for the system to automatically set the messages to Permanent Failure, as it must cater for the scenario where data subsequently becomes mandatory in SE, but is not available from Merchandising.
Supplier Evaluation Data Integration
The outbound integration with the Merchandising system allows the data relating to certain events and calculated scores to be automatically fed to Merchandising, where dashboards enhance the supplier data with the latest Supplier Evaluation information.
When Documents, Assessments, and Audits are configured to capture supplier evaluation data, and calculate supplier evaluation scores, details of the related events and scores are automatically fed back to Merchandising (for sites that have been synchronized through the Supplier & Site Integration).
For more information, see the Oracle Retail Supplier Evaluation Cloud Service Supplier User Guide.
The following system parameters must be set in order to enable the outbound Supplier Evaluation Data integration:
1. Check Integration Enabled is set to enabled/disabled accordingly.
2. Configure the Merch API URL and credentials.
3. Set the number of messages to be sent per call. The default is 1.
4. Set the Supplier Evaluation Types that are to be included in the integration.
5. Set the External Primary Language to correspond with the primary language of the Merchandising system.
6. Set the purging interval. The default is 90 days.
Outbound Message Queue
The outbound messages are managed through the Outbound Message Queue, which is located in the Batch Jobs section of the Admin area.
If a message fails, the message’s status will be set to Failure. The outbound message queue will automatically retry the original message. Messages at Failure status continue to be retried until they are successfully processed or are manually set to Permanent Failure. The purge routine automatically cleans up Permanent Failure messages, but not Failure messages.
Supplier Evaluation Scoring
This section provides information on the Scoring glossaries. For information on the system parameters used for scoring, see System Parameters.
The SE Integration & Scoring group in the Admin Area contains the Reporting and System Control options. Access is restricted to the Oracle Authorized Administrator, Configuration Editor, and Integration Administrator authority profiles.
This menu contains the following entries for maintenance of the SE Integration and Scoring related glossaries:
-
Supplier Evaluation Types
-
Supplier Evaluation Scores
-
Supplier Evaluation Scoring Rules
-
Supplier Evaluation Site Type Group
Supplier Evaluation Types
Supplier Evaluation scores are calculated for Sites, typically representing the environment, ethical, and governance element. In order to identify which Assessments, Audits, and Documents contribute to the scoring, the Supplier Evaluation Type glossary is used. The configured types can then be assigned to the types of record which contribute to the scoring.
The glossary is delivered with predefined entries, but the retailer may maintain it to suit their requirements.
The glossary is accessed by using the SE Integration & Scoring>Supplier Evaluation Types menu option in the Admin area.
The Supplier Evaluation Type is also used in the reporting of Supplier Evaluation data; it is used as a report filter and when determining which records are included in the Supplier Evaluation Dashboard.
In a new installation of the SE portal, the following values will be data generated in the Supplier Evaluation Types glossary:
-
Ethical
-
Environmental
-
Governance
Supplier Evaluation Scores
The Supplier Evaluation Scores glossary is used to define the available supplier evaluation scores as a description.
The glossary is accessed via the SE Integration & Scoring>Supplier Evaluation Scores menu option in the Admin area.
Supplier Evaluation Scoring Rules
The rules for calculating Supplier Evaluation scores for Sites are configurable within the Supplier Evaluation Scores glossary. The entries define the scoring rules for each Supplier Evaluation Type (a one-to-one relationship, so a single scoring rule per SE Type).
The glossary will be delivered with predefined entries, but the retailer may maintain it to suit their requirements.
The glossary is accessed through the SE Integration & Scoring>Supplier Evaluation Scoring Rules menu option in the Admin area.
The contents are grouped by the following tabs:
-
Details - identifies the scoring rule and which Supplier Evaluation Type it represents.
-
Criteria - a table for each Supplier Evaluation event, with their scores/weighting points.
-
Scoring - a table of the Supplier Evaluation scores, their description and optionally a graphic.
-
Change History - standard Change history logging.
The list view contains columns for SE Type, Description, Code, Version, and Status. The default sequence is ascending SE Type order.
Any changes to the scoring rules are applied by the scoring process the next time it runs.
Supplier Evaluation Site Types Groups
The Supplier Evaluation Site Type Groups glossary is used to combine entries in the existing Site Types glossary, to form logical groupings of Sites. The groupings enable the roll-up scores for Sites with different functional purposes, such as Primary Manufacturing Sites, Supplier Chain Sites, Stores, and do on. The glossary is accessed via the SE Integration & Scoring>Supplier Evaluation Site Type Group menu option in the Admin area.
System Parameters
To maintain the parameters used to support Supplier, select the System Control option and then System Parameters.
Table 7-3 shows the specific system parameters, by subtab on the System Parameters page, used to support Supplier.
Table 7-3 System Parameters to Support Supplier
Subtab | Parameter | Description | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Assessments |
Allow creation of Assessments from Assessments list |
If checked, assessments can be created from the assessments list views. If not checked, assessments can only be created directly from within a Site record. |
||||||||||||||||
Assessments |
Grace period |
Select if the assessment completion overdue grace period is in days or weeks. |
||||||||||||||||
Assessments |
Email Agent run on |
Controls which days of the week reminder emails are generated for overdue assessments. Specific days can be selected. Buttons are available to select or clear all days. |
||||||||||||||||
Assessments |
Allow ad hoc (non glossary) questions |
If checked, assessment templates have the option to have questions added that do not appear in the questions glossary. |
||||||||||||||||
Assessments |
Allow removal of universal questions |
If checked, whether universal questions may be removed from a assessment template (if not, all universal questions will appear on every assessment type |
||||||||||||||||
Audits & Visits |
Allow creation of Audits from Audits List |
If set to Yes, users may create new audits/visits from within the Audits & Visits area (in which case, they select the supplier and site) as well as through the Site record. If set to No, new audits/visits are created through the Site record (in which case there is no need to select the supplier and site). Default is No. |
||||||||||||||||
Audits & Visits |
Max Time Spent (hours) |
Sets the maximum value a user may record as the time spent on an audit/visit. This prevents excessive time being accidentally entered. Default is 20. |
||||||||||||||||
Audits & Visits |
Use Risk Levels |
Determines whether levels of risk are being assigned to Sites (based on the type of product produced). If set to Yes, a Risk Level classification can be set on the Site record, and the frequency of an audit/visit may be set differently per risk level; thus allowing an audit/visit to be scheduled more (or less) frequently for sites that supply particular types of products. Default is No. |
||||||||||||||||
Audits & Visits |
Days to show Scheduled in Tasks App |
Used to control when Scheduled audits/visits appear in the user's Task App in order to limit the list of audit/visits to just those that will become due in the next 28 days, for example, thereby excluding those that are currently scheduled but not due for a number of months. Default is 28. |
||||||||||||||||
Audits & Visits |
Edit Score on Completion |
If set to Yes, where an audit/visit is scored, the score can be assigned or changed when the audit/visit is completed (through the completion confirmation dialog box). If set to No, any scoring has to be assigned directly within the Audit/Visit record. Default is No. |
||||||||||||||||
Log On |
Site Details Update Reminder |
Number of working days between a reminder being shown in a user's UIM when a user has logged in. It is used to ensure that Mandatory Contact details are kept up to date on both the supplier and sites. Default is 90 days. When the first supplier user logs in, they see an entry in the UIM drawing their attention to this. If they use the Confirm Details action, this stamps the date onto the record so that the next time a user logs in, the system checks if the current date is greater than the stamped date. |
||||||||||||||||
Registration |
Notify Lead Technologist |
If set to Yes, the Technologist is notified by email when a supplier completes the registration for a site for which they are the Lead Technologist. Default is No. |
||||||||||||||||
Registration |
Notify Others |
User roles, with Role Type equal to Retailer, for which users should be copied on the email sent to a Technologist when a supplier completes registration. For example, it is used to notify Auditors when sites are ready to be audited. Parameter is linked to the user roles. |
||||||||||||||||
Registration |
Create Initial Audit |
If set to Yes, additional fields are made available to allow the user to create the initial audit when a site is approved. Default is No. |
||||||||||||||||
Registration |
Notify Accounts |
If set to Yes, the Account Administrator is automatically notified by email (REG3) that an order has been created when the supplier has completed their part of the registration process (for a standard supplier registration). Default is Yes. |
||||||||||||||||
Registration |
Create initial assessment |
If set to Yes, additional fields are made available to allow the user to create the initial assessment when a site is approved. Default is No. |
||||||||||||||||
Registration |
Registration Ts & Cs Active |
If set to Yes, suppliers are required to accept the portal's terms and conditions during the supplier registration process. Default is Yes. This parameter can only be seen and maintained by users with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Supplier Code Allocation |
If Auto, the system will automatically assign supplier codes to new Suppliers. If Auto/Edit, the system will automatically assign supplier codes, however the auto-allocated code may be manually changed to a unique alternative during the creation process. If Manual, the retailer user must assign a unique supplier code during the creation process. Default is Auto. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Supplier Code Editable |
If checked, the supplier code may be edited in the Supplier record after the account has been created. If Supplier Code Allocation is set to Auto, this parameter is set as unchecked and cannot be changed. Default is unchecked. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Site Code Allocation |
If Auto, the system will automatically assign site codes to new Supplier sites. If Auto/Edit, the system will automatically assign site codes, however the auto-allocated code may be manually changed to a unique alternative during the creation process. If Manual, the retailer user must assign a unique site code during the creation process. Default is Auto. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Site Code Editable |
If checked, the site code may be edited in the Site record after the account has been created. If Site Code Allocation is set to Auto, this parameter is set as unchecked and cannot be changed. Default is unchecked. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Site Code Format |
If Numeric, the site coding will follow an incrementing number sequence, starting at 1 for each supplier (with leading zeroes), such as, 0001 > 0002 … 9999 > 10000 … If Alpha, the site coding will follow an incrementing alpha code sequence, starting at AAAA for each supplier, such as, AAAA > AAAB … AAAZ > AABA … AZZZ > BAAA … This parameter cannot be changed once the first site has been created. Default is Numeric. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Prefix Site Code with Supplier Code |
If checked, the supplier code is automatically prepended to the site code when creating a Site account, with a hyphen, such as A0001-AABD. This parameter cannot be changed once the first site has been created. Default is checked. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Site Code Unique Across Portal |
If checked, the system will continue incrementing the site code across the entire portal rather than just within the supplier, to ensure the uniqueness across the portal. For example: If site codes are not required to be unique across the portal,
the coding may be:
If site codes are required to be unique across
the portal, the coding would be:
This parameter cannot be changed once the first site has been created. Default is unchecked. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Minimum Site Code Length |
The minimum number of digits or characters in the site code. This parameter cannot be changed once the first site has been created. Default is 5. Note: This parameter can only be seen and maintained by a user with the Oracle Authorized Administrator authority profile. |
||||||||||||||||
Registration |
Registered Company Number Mandatory at Registration |
Use this to control whether the Registered Company Number is mandatory or optional when the supplier completes the Registration wizard. Default is checked/Yes (mandatory). |
||||||||||||||||
Registration |
Generate Reference Due Emails |
If checked, enables email notifications for Site References when they become due. Default is unchecked. |
||||||||||||||||
Registration |
Becomes due prior to expiry date (days) |
Determines when a Site Reference becomes due based on its expiry date (the number of days prior to the expiry date). Default is blank. |
||||||||||||||||
Registration |
Re-send Reference Due email frequency (days) |
Controls the frequency of the Reference Due email (the number of days since it was previously sent). Default is blank. |
||||||||||||||||
Registration |
Generate Reference Due Assignments |
If checked, enables assignment task notifications for Site References when they become due. Default is unchecked. |
||||||||||||||||
Registration |
Generate Reference Expired Emails |
If checked, enables email notifications for Site References when they expire. Default is unchecked. |
||||||||||||||||
Registration |
Re-send Reference Expired email frequency (days) |
Controls the frequency of the Reference Expired email (the number of days since it was previously sent). Default is blank. |
||||||||||||||||
Registration |
Generate Reference Expired Assignments |
If checked, enables assignment task notifications for Site References when they expire. Default is unchecked. |
||||||||||||||||
Registration |
Notify if Site Status |
A multi-picklist of Site Statuses, this controls which statuses of site are to have Site Reference notifications. Default is Active and Awaiting Approval. |
||||||||||||||||
Registration |
Notify Lead Technologist by Email |
If checked, controls whether the site's Lead Technologist is to be a recipient of Site Reference email notifications. Default is unchecked. |
||||||||||||||||
Registration |
Notify Lead Technologist by Assignment |
If checked, used to control whether the site's Lead Technologist is to be a recipient of Site Reference assignment notifications. Default is unchecked. |
||||||||||||||||
Registration |
Notify Supplier/Site Contacts by Email |
A multi-picklist of mandatory Supplier and Site Contact Roles, this determines the recipients of Site Reference email notifications. |
||||||||||||||||
Registration |
Notify Supplier/Site Contacts by Assignment |
A multi-picklist of mandatory Supplier and Site Contact Roles, this determines the recipients of Site Reference assignment notifications. |
||||||||||||||||
Supplier Evaluation Scoring |
SE Scoring Enabled |
Controls whether SE Scoring is Enabled or Disabled. Default is Disabled. |
||||||||||||||||
Supplier Evaluation Scoring |
Scores Snapshot Interval |
Controls whether a snapshot of the scores is taken Daily, Weekly, or Monthly. Default is Monthly. |
||||||||||||||||
Supplier Evaluation Scoring |
Day of Week |
Sets the day of the week when the scores snapshot is taken. Mandatory when Average Scores Calculation Interval is Weekly. |
||||||||||||||||
Supplier Evaluation Scoring |
Scores Last Snapshotted |
Date and time a snapshot of the scores was last taken. |
||||||||||||||||
Supplier Evaluation Scoring |
Full Score Re-Calculation Required |
Determines if a full score recalculation is required. Default is No. |
||||||||||||||||
Supplier Evaluation Scoring |
Average Scores Calculation Interval |
Controls whether the average scores are calculated Weekly or Monthly. Default is Monthly. |
||||||||||||||||
Supplier Evaluation Scoring |
Day of Week |
Sets the day of the week when the average scores are calculated. Mandatory when Average Scores Calculation Interval is Weekly. |
||||||||||||||||
Supplier Evaluation Scoring |
Average Scores Last Calculated |
Date and time the average scores were last calculated. |
||||||||||||||||
Integration |
Integration Enabled |
Controls whether the integration process is active. This can be used to temporarily disable integration without having to change other parameters. If Enabled, other parameters must also be set for the integration to succeed. Default is Disabled. |
||||||||||||||||
Integration |
Integration Interval (mins) |
Sets the integer number of minutes used to control how frequently the integration runs (if it is enabled). For example, a value of 1 will run every minute; 60 will run hourly; 1440 will run once daily. If not set, or zero, the integration will not run. Default is 90 minutes. |
||||||||||||||||
Integration |
Do not run Integration before |
Used to limit the times that the integration routine will execute the integration processing. Sets the time that the integration will not run before. The job will still run on interval, but will check whether it is within the available run window before commencing processing, otherwise it will stop and schedule again for the next interval. |
||||||||||||||||
Integration |
Do not run Integration after |
Used to limit the times that the integration routine will execute the integration processing. Sets the time that the integration will not run after. The job will still run on interval, but will check whether it is within the available run window before commencing processing, otherwise it will stop and schedule again for the next interval. |
||||||||||||||||
Integration |
Last Run |
Date and time that the last integration was run. |
||||||||||||||||
Integration |
API URL |
Set the URL to the Merch Supplier API called by the integration job. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Messages per Call |
Defines the maximum number of messages to be retrieved per call from Merchandising. The default is 1000. Must be greater than zero. This parameter is mandatory. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Invoicing System |
Identifies the entry in the Supplier and Site records' Billing Details table that holds the fields relating to Merchandising integration. This parameter is mandatory for integration to be enabled, and cannot be changed once integration has occurred that is, at least one Site has a Merch key) in which case it becomes read only |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Supplier Administrator Role |
Defines the role equates to the SUPPLIER ADMINISTRATOR role used when creating an initial supplier user. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Default Technologist |
Sets the default value for the Technologist role when creating a new Site record using the integration. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Default Supplier Type |
Sets the default value for the Supplier Type when creating a new Supplier record using the integration. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Default Site Type |
Sets the default value for the Site Type when creating a new Site record using the integration. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Default Business Category |
Sets the default value for the Business Category when creating a new Site record using the integration. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Merch Active Description in SE |
Holds the Merch Active status shown in SE. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Merch Inactive Description in SE |
Holds the Merch Inctive status shown in SE. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Auto Create in SE for Active Merch Status |
If checked, sites with Active status in Merchandising are automatically created in SE. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Auto Delist in SE for Inactive Merch Status |
If checked, sites with Inactive status in Merchandising are automatically delisted in SE. |
||||||||||||||||
Supplier and Site Integration (Inbound) |
Number of days to keep Inbound Message Queue data |
Controls the auto-purging of the Inbound Message Queue. If blank, no purging occurs; a setting of zero indicates immediate purging. The default is 90 days. |
||||||||||||||||
Supplier and Site Integration (Outbound) |
Messages per Call |
Defines the number of messages to be sent per call to Merchandising. The default is 1. Must be greater than zero. This parameter is mandatory. |
||||||||||||||||
Supplier and Site Integration (Outbound) |
External Primary Language |
Defines the corresponding primary language of the Merchandising system. |
||||||||||||||||
Supplier and Site Integration (Outbound) |
Supplier Evaluation Types |
Sets the Supplier Evaluation Types that are to be included in the integration. |
||||||||||||||||
Supplier and Site Integration (Outbound) |
Number of days to keep Outbound Message Queue data |
Controls the auto-purging of the Outbound Message Queue. If blank, no purging occurs; a setting of zero indicates immediate purging. The default is 90 days. |
||||||||||||||||
Urgent Items |
Show Alert Items |
If set to Yes, Alert KPIs are shown in the UIM. Default is Yes. |
||||||||||||||||
Urgent Items |
No. Days Before Alert Response is overdue |
Number of days before this KPI is shown. Default is two days. |
||||||||||||||||
Urgent Items |
Show assessments |
If set to Yes, assessments are shown in the UIM. Default is Yes. |
||||||||||||||||
Urgent Items |
Assessment Overdue Off-set days |
Number of days before an overdue assessment is shown. Default is two days. |