Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 20 Next »

Table of Contents

NBP Exchange Rate Integration

To deploy the exchange rate integration script:

  1. Go to Customization > Scripting > Scripts.

  2. Search for [STA] Update FX Rates SS (id: customscript_sta_update_fxrates)

  3. Click the View link.

  4. Go to the Deployments tab.

  5. Click Script Deployment record

  6. Click the Edit button.

  7. Check Deployed box.

  8. Select Status to Scheduled

  9. Go to the Parameters subtab.

    1. Check any of the currency checkboxes (NBP, MNB, ECB) if this set of parameters only applies to specific currencies. Leaving all checkboxes unchecked will apply the parameters to all enabled currency exchange rate integrations in [STA] FX Rates Update Preferences.

    2. Select the Get Exchange Rate: You can choose between two options on which date the FX rate will be based.

      • Before Effective Date - exchange rates published a day before the effective date will be used. If the day before falls on a weekend, published rates from the previous Friday will be used.

      • On or Before Effective Date - exchange rates published on the day or a day before the effective date will be used. If the day before falls on a weekend, published rates from the previous Friday will be used.

  10. Go to the Schedule subtab.

    1. Select Daily Event > Repeat Every Weekday.

    2. Select Start Date.

    3. Select Start Time.

  11. Click the Save button.

For scheduled runs, the effective date will always be based on the CET timezone.

Important: If you are using NetSuite’s exchange rate provider (e.g., Xignite, etc.), there could be instances where the previously updated exchange rates by NBP integration will be overridden. To make sure that the PLN exchange rates will be reverted to the rates coming from NBP, create another script deployment which should be scheduled to run after the update from NetSuite’s exchange rate provider.

Vendor Whitelisting

Script Deployment

Upon installation, the scripts for the on-demand and scheduled whitelisting must be properly deployed to ensure that the feature works as expected. Below are the steps administrators need to take to deploy the vendor whitelisting feature fully:

Deploy/Undeploy On-Demand Whitelisting on Vendor

To deploy the On-Demand Whitelisting on the Vendor Record:

  1. Go to Customization > Scripting > Scripts.

  2. Search for a script named [STA] UE PL Vendor Whitelisting (id: customscript_ue_sta_vendorwhitelisting)

  3. Click the View link next to the script.

  4. Navigate to the Deployment subtab and view the deployment for the Vendor record.

  5. Edit the deployment record and make the necessary adjustments:

    1. Deployed - Check the box to deploy the script.

    2. Status - Select the Released status as default.

    3. Execute As Role - Select the [STA-PL] Admin Role as default.

    4. Roles - Check the Select All box.

    5. Employees - Check the Select All box.

  6. Click the Save button.

  7. Go to Customization > Scripting > Scripts.

  8. Search for a script named [STA] SL PL Vendor Whitelisting (id: customscript_sl_pl_vendorwhitelisting)

  9. Click the View link next to the script.

  10. Navigate to the Deployment subtab and view the deployment record.

  11. Edit the deployment record and make the necessary adjustments:

    1. Deployed - Check the box to deploy the script.

    2. Status - Select the Released status as default.

    3. Execute As Role - Select the [STA-PL] Admin Role as default.

    4. Roles - Check the Select All box.

    5. Employees - Check the Select All box.

  12. Click the Save button.

Deploy/Undeploy On-Demand Whitelisting on Transaction

To deploy the Scheduled Whitelisting on the vendor record:

  1. Go to Customization > Scripting > Scripts.

  2. Search for a script named [STA] UE PL Vendor Whitelisting (id: customscript_ue_sta_vendorwhitelisting)

  3. Click the View link next to the script.

  4. Navigate to the Deployment subtab and view the deployment for the Vendor Bill record.

  5. Edit the deployment record and make the necessary adjustments:

    1. Deployed - Check the box to deploy the script.

    2. Status - Select the Released status as default.

    3. Execute As Role - Select the [STA-PL] Admin Role as default.

    4. Roles - Check the Select All box.

    5. Employees - Check the Select All box.

  6. Click the Save button.

  7. Repeat Steps 1-6 for each of the following transaction records:

    1. Purchase Order

    2. Vendor Credit

  8. Go to Customization > Scripting > Scripts.

  9. Search for a script named [STA] SL PL Vendor Whitelisting (id: customscript_sl_pl_vendorwhitelisting)

  10. Click the View link next to the script.

  11. Navigate to the Deployment subtab and view the deployment record.

  12. Edit the deployment record and make the necessary adjustments:

    1. Deployed - Check the box to deploy the script.

    2. Status - Select the Released status as default.

    3. Execute As Role - Select the [STA-PL] Admin Role as default.

    4. Roles - Check the Select All box.

    5. Employees - Check the Select All box.

  13. Click the Save button.

Deploy/Undeploy Scheduled Whitelisting on Vendor

To deploy the scheduled whitelisting on the vendor record:

  1. Go to Customization > Scripting > Scripts.

  2. Search for a script named [STA] MR PL Vendor Whitelisting (ID: customscript_mr_sta_pl_vendorwhitelist).

  3. Click the View link next to the script

  4. Navigate to the Deployment subtab and view the deployment record.

  5. Edit the deployment record and make the necessary adjustments:

    1. Set Status to Scheduled

    2. Define the desired recurrence schedule:

      1. Select Daily Event

      2. Repeat Every is set to 1 by default, but you may change this to any other value if you do not wish to run the script daily.

      3. Enter the Start Date and Start Time

      4. Define whether the schedule will end on a certain date by entering an End By date value,

      5. Or having the schedule run indefinitely by checking the No End Date field.

    3. Optionally, configure any of the following fields:

      1. Priority - Available options are High, Standard, and Low. The default option is Standard. This field determines the urgency of the script processing. The higher the priority of the script run, the higher up the queue it will be included.

      2. Concurrency Limit - Determines the number of job queues that can be used to process runs of this script. The default option is 1. Depending on your licensing agreement with NetSuite, you may have other values available. You should only increase this value if regular vendor whitelisting is at the top of your priority list and several thousands of vendors are eligible for regular checks. Otherwise, please keep this value to 1.

      3. Yield After Minutes - This is a soft time limit on how long a script can run before yielding. The default value is 60 minutes. You can enter any value from 3-60. It is highly suggested that this is kept at 60. Only reduce the value if necessary.

      4. Buffer Size - This value determines how many records can be processed in parallel before information about the job’s progress is saved to the database. A low Buffer Size minimizes the risk of any records being processed twice. The default value is 1. It is generally suggested to leave this value to 1 unless special circumstances dictate otherwise.

  6. Click the Save button.

Deploy/Undeploy Scheduled Whitelisting on Transactions

To deploy the scheduled whitelisting on transaction records:

  1. Go to Customization > Scripting > Scripts.

  2. Search for a script named [STA] MR PL Vendor Whitelisting By Trxn (ID: customdeploy_mr_sta_pl_vw_by_trxn)

  3. Click the View link next to the script

  4. Navigate to the Deployment subtab and view the deployment record.

  5. Edit the deployment record and make the necessary adjustments:

    1. Set Status to Scheduled

    2. Define the desired recurrence schedule:

      1. Select Daily Event

      2. Repeat Every is set to 1 by default, but you may change this to any other value if you do not wish to run the script daily.

      3. Enter the Start Date and Start Time

      4. Define whether the schedule will end on a certain date by entering an End By date value,

      5. Or having the schedule run indefinitely by checking the No End Date field.

    3. Optionally, configure any of the following fields:

      1. Priority - Available options are High, Standard, and Low. The default option is Standard. This field determines the urgency of the script processing. The higher the priority of the script run, the higher up the queue it will be included.

      2. Concurrency Limit - Determines the number of job queues that can be used to process runs of this script. The default option is 1. Depending on your licensing agreement with NetSuite, you may have other values available. You should only increase this value if regular vendor whitelisting is at the top of your priority list and several thousands of vendors are eligible for regular checks. Otherwise, please keep this value to 1.

      3. Yield After Minutes - This is a soft time limit on how long a script can run before yielding. The default value is 60 minutes. You can enter any value from 3-60. It is highly suggested that this is kept at 60. Only reduce the value if necessary.

      4. Buffer Size - This value determines how many records can be processed in parallel before information about the job’s progress is saved to the database. A low Buffer Size minimizes the risk of any records being processed twice. The default value is 1. It is generally suggested to leave this value to 1 unless special circumstances dictate otherwise.

  6. Click the Save button.

Send an email to support@staria.com for questions or concerns regarding this topic.

  • No labels

©2024 Staria. All rights reserved. No part of this publication may be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording, or other electronic or mechanical methods, without the prior written permission of the publisher.