What's New in Version 6.0

Accounts Receivable 6.0 includes the following new features and improvements:

• Changes to Refund Entry

  If you use Payment Processing, you can now use the A/R Refund Entry screen to process credit card refunds for credit notes.

  • When you select a credit note, an SPS Credit Card option is now available in the Payment Type column.
  • A new Receipt No. column allows you to select a receipt, prepayment, or unapplied cash transaction for which a Paya credit card transaction has been processed.

For more information, see Accounts Receivable help.

Inventory Control 6.0 includes the following new features and improvements:

• Ability to Ensure that Serial Numbers are Unique to Individual Items.

  In earlier versions, Inventory Control allowed you to assign the same serial number to multiple items. This is now a default that you can override.

  To ensure that no serial number is assigned to more than one item, you edit the IC.INI file. In the General section of the IC.INI file, change the value of the AllowSameSerialForMultiItems switch to No.

  Note: Setting this switch to No does not change existing assigned serial numbers, so any existing duplicated serial numbers remain.

• Alternate Method for Generating Physical Inventory Adjustments for Standard Cost Items.

  In earlier versions, Inventory Control used an item's standard cost when computing inventory adjustments for the Generate Inventory Worksheet screen. Standard cost is now a default that you can override if you require a different inventory valuation.

  To adjust standard cost items using the average (actual) cost, rather than the standard cost, you edit the IC.INI file before generating inventory worksheets. In the Physical Inventory section of the IC.INI file, change the value of the UseActualCostForPI switch to Yes. The next time you use the Generate Inventory Worksheet screen to adjust inventory, the adjustments will be based on average cost.

Product Update 1 includes support for Payment Processing 6.0—a Sage 300 program that lets you process credit card payments from your customers. For detailed information about product features and integration with Accounts Receivable and Order Entry 6.0, see the "Payment Processing Overview" topic in the Payment Processing help.

Payment Processing 6.0 includes the following new features:

• New Payment Processing Screens
  • A new Process Credit Card screen lets you pre-authorize, process, void, and refund credit card payments. You open this screen from Order Entry screens (Order Entry, Shipment Entry, and Invoice Entry) and Accounts Receivable screens (Receipt Entry, Invoice Entry, and Refund Entry).

  • A new Processing Codes setup screen lets you set up processing codes, which specify the bank, currency, and merchant account that will be used to process credit card transactions.

    Each processing code includes a merchant ID and merchant key for a Paya merchant account. Payment Processing supports credit card transactions in USD and CAD, so if you use multicurrency accounting, you must set up a separate merchant account for each currency in which you will process credit card transactions.

• New Payment Processing Security Authorizations
  • Setup Maintenance authorization allows you to use the Processing Codes screen to view, add, edit, and delete merchant account information.
  • Customer Card Maintenance authorization allows you to add, edit, and delete customer credit card information in Payment Processing and Accounts Receivable.
  • Card Transaction Processing authorization allows you to process the following transactions in Payment Processing, Accounts Receivable, and Order Entry:
    • Pre-authorize a credit card payment
    • Capture a pre-authorized credit card payment
    • Void a pre-authorized credit card payment
    • Process a credit card payment
    • Void a credit card payment
    • Void a credit card refund

Bank Services 6.0 Product Update 1 includes the following new features and improvements:

• Enhanced G/L Integration to allow you to set the G/L Detail Reference, G/L Detail Description, and G/L Detail Comment for a Bank Entry Transaction Type. When the bank entry is posted, the reference fields in the corresponding G/L journal entry detail (corresponding to the Bank Account) are updated accordingly.
• When reconciling deposits, in addition to being able to clear whole deposits, you can now clear individual receipts within a deposit. This new functionality applies whether you reconcile manually or with an OFX statement.
• On the Deposit Details screen, the Sort By feature has been changed to Sorted By, and is now display-only. To specify how transactions are sorted on the Deposit Details screen, use Sort Deposit Details By on the Processing tab of the Bank Options screen.
• On both the Deposit Register report and the Reconciliation Status report, you can now filter deposits with a status of Reconcile by Deposit Detail.

Accounts Receivable 6.0 includes the following new features and improvements:

• Changes to Receipt Entry
  • You can now see and edit the Deposit Date on the Receipt Entry screen.
• Changes to Support New Payment Processing Module

  Accounts Receivable supports Payment Processing, a Sage 300 program that lets you process credit card payments from your customers. You use it with Sage Exchange, a secure payment-processing application that integrates Sage 300 with Paya.

  • A new SPS Credit Card payment type lets you define payment codes you will use for Paya credit card transactions. To process a credit card payment for a transaction in Paya, you must select a payment code with the SPS Credit Card payment type for the transaction.
  • On the A/R Customers screen, a new Credit Card tab allows you to view, add, edit, and delete credit card records for customers. From this tab, and from other screens in Accounts Receivable and Payment Processing, you can open the Credit Card Information screen, which you use to set up credit card records and add or edit card details.
  • On the Receipt Entry screen, when you select a payment code that uses the SPS Credit Card payment type and then add a receipt, a new Charge button lets you process a credit card for a prepayment, receipt, unapplied cash, or miscellaneous receipt. After you process the payment, a new Void button lets you void the payment if it has not been settled in Paya.
  • On the Invoice Entry screen, when you click the Prepay button and select a payment code that uses the SPS Credit Card payment type, a new Charge button on the Prepayment screen lets you process a credit card payment for the invoice. After you process the payment, a new Void button lets you void the payment if it has not been settled in Paya.
  • On the Refund Entry screen, when you select a transaction that has been paid by credit card in Paya, a new Credit button lets you apply a full or partial refund to the card that was used for the transaction. (You can refund credit card transactions by cash or check, or by applying a credit to the card used for the transaction.) If you apply the refund to the card, after you process the refund, a new Void button lets you void the refund if it has not been settled in Paya.
  • A new option lets you include customer credit card information in the A/R Customers report.
  • The A/R Receipt Confirmation report now includes card details and the authorization code for Paya credit card transactions.

Accounts Payable 6.0 includes the following new features and improvements:

• A new T5018 (CPRS) Electronic Filing screen is available in Periodic Processing.

  If you file more than 50 T5018 slips for a calendar year, the Canada Revenue Agency (CRA) requires you to file original and amended T5018 information returns over the Internet. You use the new T5018 (CPRS) Electronic Filing screen to create your T5018 information return in the required XML format. You can then submit the generated file using the CRA's Internet File Transfer application.

  If you are filing fewer than 50 slips, you can submit the file to the CRA on electronic media.

Order Entry 6.0 includes the following new features and improvements:

• You can now return serialized and lotted items to a location other than the location from which the items were shipped. (Previously, if you shipped and invoiced an order that included serialized or lotted items, and then selected the invoice in Credit Note Entry and tried to change the ship-to location, serial and lot numbers for the items were cleared.) For more information, see Knowledgebase article 210-31332.

• Order Entry now supports Payment Processing, a program that lets you process credit card payments from your customers. You use it with Sage Exchange, a secure payment-processing application that integrates with Sage 300.

  After you install Payment Processing and Product Update 1, the following features are added to Order Entry:

  • In Accounts Receivable, a new payment type ("SPS Credit Card") is added to the list of available selections on the Payment Codes setup screen. In Order Entry, when you select a payment code that uses this payment type, you can pre-authorize or process a credit card prepayment for an order, shipment, or invoice.
  • On the Order Entry, Shipment Entry, and Invoice Entry screens, you can click the Prepayment button to process or void a credit card prepayment. On the Prepayment screen, when you select a payment code that uses the SPS Credit Card payment type and add a prepayment, Charge and Void buttons become available and allow you to process or void a credit card prepayment for an order, shipment, or invoice.
  • On the Order Entry screen, three new buttons—Pre-authorize, Capture, and Void—allow you to pre-authorize, capture, or void a credit card prepayment.
  • On the Shipment Entry screen, a Capture button allows you to capture a pre-authorized credit card payment. If no pre-authorized credit card payment exists, a Prepayment button appears instead and allows you to process a prepayment.
  • On Order Entry screens where you can pre-authorize or process a credit card prepayment, a Processing Code field allows you to select a processing code, which specifies the bank, currency, and merchant account that will be used to process the transaction. (You set up processing codes in Common Services, under Payment Processing.)

Project and Job Costing 6.0 includes the following new features and improvements:

• You can now create a new invoice batch in Accounts Receivable when you post a billing worksheet, even if there is an unposted job-related batch in Accounts Receivable. A new option on the PJC Options screen enables you to always create a new Accounts Receivable batch whenever you post a billing worksheet.

The Sage 300 Portal is a web-based interface that lets you use Sage 300 in a browser window.

The portal delivers all the features you're familiar with from previous versions. It also introduces the following features that are designed to help you extract, analyze, and report on your accounting data:

• Shortcuts to tasks and reports you use most often.
• Snapshots that present your General Ledger, Accounts Payable, and Accounts Receivable data graphically. You can drill down to detailed reports for further analysis.
• A convenient Inquiry tool that you can use to quickly and easily retrieve information from your company database, and create and save ad-hoc reports.
• A new Learning Center to help you with all of your tasks. In the Learning Center, you will find links to a series of videos designed to help you become familiar with the new features in Sage 300 6.0 in record time.

You can continue to use the Sage 300desktop, as before—but these new visualization and analysis tools are available only in the portal.

Follow the links in the Getting Started snapshot to find articles, videos, and other resources that will help you get the most out of Sage 300 6.0.

Note: Third-party programs, macros, and customized user interface screens are not available in the portal, but you can continue to use them from the Sage 300 desktop.

The installation program now installs components that support the use of Sage 300 in a new web portal. To learn more, see the Sage 300 Installation and System Administrator’s Guide.

System Manager 6.0 includes several significant changes and new features.

• A Portal button in the Database Setup screen that opens a new Configure Portal screen

  You use the Configure Portal screen to specify settings to connect the portal program to the portal database, including the database format, server machine name and port, database name, and user credentials.

• New security authorizations for Accounts Payable, Accounts Receivable, General Ledger, and Inventory Control to support snapshots and Sage 300 Inquiry, two of the portal's innovative features.
  • You can assign the following authorizations to view individual snapshots:
    • For Accounts Receivable, you can assign Aged Receivables Snapshot and Days Receivables Outstanding Snapshot authorizations.
    • For Accounts Payable, you can assign Aged Payables Snapshot and Days Payables Outstanding Snapshot authorizations.
    • For General Ledger, you can assign Balance Sheet Snapshot and Income Statement Snapshot authorizations.
  • You can also authorize users to query specific data sources using Sage 300 Inquiry, as follows:
    • Assigning Sage 300 Inquiry authorization for Accounts Receivable lets users inquire on customers and Accounts Receivable transactions.
    • Assigning Sage 300 Inquiry authorization for Accounts Payable lets users inquire on vendors and Accounts Payable transactions.
    • Assigning Sage 300 Inquiry authorization for General Ledger lets users inquire on General Ledger accounts, net changes, and transactions.

    Note that users must also have Export authorization for the program to print or to export the results of their queries.

  • Software developers should be aware of the new Developer Inquiry authorizations available for Accounts Receivable, Accounts Payable, and Inventory Control. Third-party programs that require access to the corresponding views and tables must incorporate these authorizations in their security structures. (Existing authorizations that provided access to the ARCUS, APVEN, and ICITEM tables continue to provide this access.)
• Individual program locks in the Fiscal Calendar

  The Fiscal Calendar now lets you lock and unlock fiscal years and periods separately for each Sage 300 program your company uses to process transactions. (Previously, you could only lock or unlock fiscal periods for all programs at once.)

  Note: To prevent posting to locked fiscal periods, you must select Error for the Locked Fiscal Period option in the Company Profile. (This feature is the same as in previous versions.)

  Important! If you are upgrading, you should review the fiscal calendar carefully in version 6.0. Fiscal periods will continue to be locked or unlocked for all programs that were activated in your earlier version, consistent with the fiscal period locks in the earlier version.

  If you activate additional (new) programs in version 6.0, fiscal periods will be locked or unlocked for the new programs, as follows:

  • For fiscal years that were active in your previous version, fiscal periods will be unlocked for the new programs in version 6.0, consistent with the locks in your earlier version.
  • For fiscal years that were inactive in your previous version, fiscal periods will be locked for the new programs in version 6.0.
• The Fiscal Calendar Report prints in landscape format

  This report now prints information for all periods, including the Adjustment and Closing periods, in rows, and includes a column for each activated Sage 300 program.

• Reports that are designed for printing from the new portal screens (for Snapshots, Inquiry, and Quotes to Order), use the Crystal 2008 Java runtime.

  Reports that were designed for printing from the Sage 300 Desktop or from Web-Deployed Sage 300 use the SAP Crystal Reports runtime engine for .NET Framework 4.

• Crystal Reports is now used as the default format, rather than PDF, when you print reports to file or export them from a report preview screen. To view reports you export in Crystal Reports format, you must have SAP Crystal Reports® installed.
• The Setup Wizard has been discontinued in this version.
• Optional Field Conversion and Optional Tables (which were designed to facilitate conversion from much older versions) have been removed from version 6.0.

Fiscal periods are now locked separately for each Sage 300 program in Common Services' Fiscal Calendar. Although this change does not affect the way you enter transactions in Bank Services, you should note the following points:

• The system checks the status of a fiscal period when you enter dates in transactions.

  It also prevents other modules from posting to Bank Services if a fiscal period is locked for Bank Services. This means that you cannot post in Accounts Payable, Accounts Receivable, and Canadian or US Payroll, checks, receipts, or refunds to a period that is locked for Bank Services, even if the period is not locked for the module where you entered the check or receipt.

  For example, if the period is locked for Bank Services, but not for Payroll, you will receive an error message after printing checks.

• If a fiscal period is locked for General Ledger, but not for Bank Services, you may be able to generate transactions for General Ledger, but not post them in General Ledger. However, this situation is unlikely if you create and post General Ledger batches for outstanding Bank Services transactions before locking General Ledger.

Because you can now lock fiscal periods separately for each Sage 300 program, you should know how this change affects the flow of transactions from the point of entry through posting in General Ledger:

• The program checks the status of a fiscal period when you enter certain dates in transactions, or (in some cases) when you add transactions.

  If the period is locked for the module you are working with, the system displays an error, a warning, or no message, depending on the setting for the Locked Fiscal Period option in the Company Profile.

• You cannot post transactions in General Ledger to a period that is locked for General Ledger, regardless of the Locked Fiscal Period setting. (This behavior is the same as in earlier versions.)
• If a fiscal period is locked for General Ledger, but not for an accounting module (such as Bank Services or Accounts Receivable), you may be able to generate G/L transactions in the other module, but the transactions will be placed in an error batch when you try to post them in General Ledger.

  However, this situation is unlikely if you create and post General Ledger batches for outstanding transactions in other modules before you lock periods for General Ledger.

• The system prevents other modules from posting to Bank Services if a fiscal period is locked for Bank Services.

  This means that you cannot post in Accounts Payable, Accounts Receivable, and Canadian or US Payroll, checks, receipts, or refunds to a period that is locked for Bank Services, even if the period is not locked for the module where you entered the check or receipt.

  For example, if the period is locked for Bank Services but not for Payroll, you will receive an error message after printing checks.

• Day End Processing is not affected by locked fiscal periods.

  If a fiscal period is locked for General Ledger but not for Inventory Control, for example, you can create transaction batches for General Ledger during Day End Processing or using the Create G/L Batch icon (depending on Inventory Control's G/L Integration settings).

• Locking a fiscal period for PJC does not normally prevent other Sage 300 programs from updating information in the Contract Maintenance screen. For example, posting a job-related invoice in Accounts Receivable or Accounts Payable updates the associated values for the contracts, projects, categories, and resources in PJC.

  An exception to this rule can occur if you post material usage or material return transactions to a period that is later locked for PJC. If the period is locked before running Day End Processing, Day End Processing will not process these transactions, and will generate an error. To clear the error, you must unlock the period for PJC, and then run Day End Processing. (Material allocation transactions do not produce this error.)

• Locking a fiscal period for Inventory Control does not prevent Day End Processing from creating transactions for, or from updating contracts in, PJC. However, if the period is locked for PJC, you might not be able to post the transactions in PJC.
• You can create revenue recognition worksheets for a period that is unlocked for Project and Job Costing. However, if the period is locked for General Ledger, you cannot post the resulting batch in General Ledger. If the option to create and automatically post G/L batches is selected on the G/L Integration screen, the transactions will be placed in an error batch in General Ledger when you post the worksheet.
• You can create billing worksheets for a period that is unlocked for Project and Job Costing. However, if the period is locked for Accounts Receivable, you cannot post the resulting invoice batch in Accounts Receivable. Also, if the option to post A/R batches automatically is selected on the PJC Options screen, the transactions will be placed in an A/R error batch when you post billing worksheets for periods that are locked for Accounts Receivable.
• ICT checks the status of a fiscal period when you enter dates in transactions, when you create batches, and when you post transactions.
  • When you create an Accounts Payable batch in ICT, the program checks the status of the fiscal period for Accounts Payable in the ICT company. If the fiscal period is locked for Accounts Payable and if the Locked Fiscal Period option is set to Error or Warning, the program displays a warning message.
  • When you enter an Accounts Payable invoice, debit note, credit note, or interest charge in ICT, the program checks the Fiscal Calendar in the originating company. If the fiscal period is locked for Accounts Payable, the program displays an error or a warning message, or no message (depending on the settings in the Company Profile).
  • When you post an Accounts Payable batch in ICT, the program checks the status of the fiscal period for General Ledger and for Accounts Payable in each originating company.

    If the fiscal period is locked for General Ledger, you cannot post the batch. The program creates an error batch, and records the entry in an error report.

    If the fiscal period is locked for Accounts Payable and the Locked Fiscal Period option is set to Error, you cannot post the batch. The program creates an error batch, and records the entry in an error report.

  • When you enter a General Ledger journal entry in ICT, the program checks the status of the fiscal period for General Ledger in the originating company. If the period is locked for General Ledger, the program displays an error.
  • When you post a General Ledger batch in ICT, the program checks the status of the fiscal period for General Ledger in each remote company. If the fiscal period is locked for General Ledger in any of the companies, the program displays an error, and you cannot post the batch.

General Ledger 6.0 includes the following new features and improvements:

• Changes in Processing to Respect New Fiscal Period Locks

  Fiscal periods are now locked separately for each Sage 300 program in Common Services' Fiscal Calendar. Although this change does not affect the way you enter transactions in General Ledger, you should note the following points:

  • The program checks the status of a fiscal period when you enter dates or when you add transactions.
  • If a fiscal period is locked for General Ledger, but not for another Sage 300 program, you may be able to generate transactions for General Ledger in the other program, but not post them in General Ledger.

  However, this situation is unlikely if you create and post General Ledger batches for outstanding transactions in other programs before locking General Ledger.

• Revised Account Groups

  In Version 6.0, we modified the standard set of account groups that comes with Sage 300 program.

  To use the sample reports that come with Financial Reporter with your own data, your accounts must be assigned to the same standard account groups.

  To use the new "snapshots" that are available in the Sage 300 Portal, all your accounts must be assigned to account groups and all account groups must be assigned to group categories.

  If you don't want to use general ledger data snapshots, you don't need to remap existing accounts to new account groups.

  If you have not used account groups previously, note that the G/L Account Groups screen appears only if the Use Account Groups option is selected on the G/L Options screen.

• New Group Categories

  Group categories organize your accounting information especially for presentation in the Sage 300 Portal. The new Income Statement and Balance Sheet snapshots retrieve data from group categories that are linked to your general ledger accounts through account groups.

  If you plan to use the general ledger snapshots, you must first:

  1. Ensure that all account groups are assigned to an appropriate category from the new set of group categories. (Assign group categories using the G/L Account Groups setup screen.)
  2. Ensure that all general ledger accounts are assigned to appropriate account groups. (Assign account groups to group categories using the G/L Account Groups setup screen.)

• Rollup Accounts for All Editions

  Rollup accounts are now available for all editions of Sage 300. Previously, rollup accounts were available only for Sage 300 Premium.

• New FR Sample Statements

  Financial Reporter includes a new set of sample statements that use the new account groups.

  If you want to use the new sample statements with your own data, you must ensure that your accounts use the new standard account groups. (If you use different account groups, you must customize the report forms so that they use your account groups.)

  If you do not want to use the new set of sample financial statements, you can continue to use the statements that shipped with earlier versions.

• New Portal-Related Security Authorizations

  Two new authorizations—Balance Sheet Snapshot and Income Statement Snapshot—allow users to view and configure the Balance Sheet snapshot and the Income Statement snapshot in the Sage 300 Portal.

  The new Accpac Inquiry authorization allows users to query General Ledger data using Inquiry in the Sage 300 Portal. If they also have Export General Ledger Data authorization, they can print or export the results of these queries.

Accounts Payable 6.0 includes the following new features and improvements:

• Changes in Processing to Respect New Fiscal Period Locks

Accounts Payable supports changes to Common Services' Fiscal Calendar.

Fiscal periods are now locked separately for each Sage 300 program. Although this change does not affect the way you enter transactions in Accounts Payable, you should note the following points:

• The system checks the status of a fiscal period for Accounts Payable when you enter certain dates in Accounts Payable transactions. It also checks the status of the fiscal period for Bank Services when you print a payment check.
• If the period is locked for Accounts Payable, you receive a warning, an error message, or no message, depending on the setting for the Locked Fiscal Period option on the Company Profile’s Options tab.
• If the period is locked for Bank Services and the Locked Fiscal Period option is set to Error, you receive an error message when you add a receipt or print a refund cheque. (Otherwise, no warning or error appears.)

Generally, you should lock a period for Accounts Receivable, Bank Services, and Accounts Payable at the same time, to avoid this situation.

• If a fiscal period is locked for General Ledger but not for Accounts Payable, you can create batches for General Ledger during posting or using the Create G/L Batch icon (depending on Accounts Payable's G/L Integration settings). When you try to post transactions to a locked period in General Ledger, however, the transactions will be placed in an error batch. You can avoid this situation if you create and post General Ledger batches for outstanding Accounts Payable transactions before locking a period for General Ledger.
• New Portal-Related Security Authorizations
  • Two new authorizations—Aged Payables Snapshot and Days Payable Outstanding Snapshot—allow users to view and configure the Aged Payables snapshot and the Days Payable Outstanding snapshot, respectively, in the new Sage 300 Portal.
  • The new Sage 300 Inquiry authorization allows users to query Accounts Payable data in the new Sage 300 Portal. If they also have Export Processing authorization for Accounts Payable, they can print or export the results of these queries.
  • A new Vendor Developer Inquiry authorization supports the new portal's Inquiry feature. Developers of third-party programs, including macros, should incorporate this resource in their security structures.

Accounts Receivable 6.0 includes the following new portal-related security authorizations:

• Changes in Processing to Respect New Fiscal Period Locks

  Accounts Receivable supports changes to Common Services' Fiscal Calendar.

  Fiscal periods are now locked separately for each Sage 300 program. Although this change does not affect the way you enter transactions in Accounts Receivable, you should note the following points:

  • The system checks the status of a fiscal period for Accounts Receivable when you enter certain dates in Accounts Receivable transactions. It also checks the status of the fiscal period for Bank Services when you add a receipt or print a refund check.
  • If the period is locked for Accounts Receivable, you receive a warning, an error message, or no message, depending on the setting for the Locked Fiscal Period option on the Company Profile’s Options tab.
  • If the period is locked for Bank Services and the Locked Fiscal Period option is set to Error, you receive an error message when you add a receipt or print a refund cheque. (Otherwise, no warning or error appears.)

    Generally, you should lock a period for Accounts Receivable, Bank Services, and Accounts Payable at the same time, to avoid this situation.

  • If a fiscal period is locked for General Ledger but not for Accounts Receivable, you can create batches for General Ledger during posting or using the Create G/L Batch icon (depending on Accounts Receivable's G/L Integration settings). When you try to post transactions to a locked period in General Ledger, however, the transactions will be placed in an error batch.

    You can avoid this situation if you create and post General Ledger batches for outstanding Accounts Receivable transactions before locking a period for General Ledger.

• New Portal-Related Security Authorizations
  • Two new authorizations —Aged Receivables Snapshot and Days Receivable Outstanding Snapshot—allow users to view and configure the Aged Receivables snapshot and Days Receivable Outstanding snapshot, respectively, in the Sage 300 portal.
  • The new Accpac Inquiry authorization allows users to query Accounts Receivable data in the new Sage 300 portal. If they also have Export Processing authorization for Accounts Receivable, they can print or export the results of these queries.
  • A new Customer Developer Inquiry authorization supports the new portal's Inquiry feature. Developers of third-party programs, including macros, need to incorporate this resource in their security structures.

Inventory Control 6.0 includes the following new features and improvements:

• Changes in Processing to Respect New Fiscal Period Locks.

  Inventory Control supports changes to Common Services' Fiscal Calendar.

  Fiscal periods are now locked separately for each Sage 300 program, including Inventory Control. Although this change does not affect the way you enter transactions, you should note the following points:

  • The program checks the status of a fiscal period when you enter certain dates in Inventory Control transactions.
  • Day End Processing is not affected by locked fiscal periods.

    Day End Processing creates transactions and updates costs for General Ledger, Accounts Payable, Accounts Receivable, and Project and Job Costing (depending on your system and settings), as usual. However, if a fiscal period is locked for a ledger receiving these transactions from Inventory Control, the transactions may fail to post in the other ledger.

  • If a fiscal period is locked for General Ledger but not for Inventory Control, you can create transaction batches for General Ledger during Day End Processing or using the Create G/L Batch icon (depending on Inventory Control's G/L Integration settings).

    However, when you try to post transactions to a locked period in General Ledger, the transactions will be placed in an error batch. You can avoid this situation if you create and post General Ledger batches for outstanding Inventory Control transactions before locking the period for General Ledger.

• New Portal-Related Security Authorization.

  We have added a new authorization, Item Developer Inquiry, for Inventory Control to support the new Inquiry feature in the Sage 300 portal. Developers of third-party programs, including macros, need to incorporate this resource in their security structures.

Order Entry version 6.0 supports the following changes to Sage CRM Integration, which now lets you update Sage 300 quotes and orders directly from Sage CRM:

• The Sage CRM Setup screen includes a new Suspend O/E Integration Option To Sage CRM option.
• The Processing tab of the O/E Options screen includes a new Clear Expired Quotes option, which you use to specify whether to delete quotes after they expire, as well as the number of days between expiry and deletion.
• You can no longer manually link quotes to opportunities in the O/E Inquiry screen. (You must use the new Quote Entry and Order Entry screens to enter a quote or an order, and link it to an opportunity.)

For more detailed information about these changes, see the Sage CRM Integration Update Notice and the Sage CRM Integration Guide.

• Changes in Processing to Respect New Fiscal Period Locks 

  Fiscal periods are now locked separately for each Sage 300 program, including Purchase Orders. Although this change does not affect the way you enter transactions, you should note the following points:

  • The program checks the status of a fiscal period when you enter certain dates in Purchase Orders documents.
  • Day End Processing is not affected by locked fiscal periods, and creates transactions for General Ledger, Accounts Payable, and Project and Job Costing (depending on your system and settings) and updates costs, as usual. However, if a fiscal period is locked for a ledger receiving the resulting transactions, the transactions can fail to post in the other ledger.

Project and Job Costing 6.0 includes the following new features and improvements:

• Project and Job Costing 6.0A (PJC) supports changes to Common Services' Fiscal Calendar.

  Fiscal periods are now locked separately for each Sage 300 program, including Project and Job Costing. Although this change does not affect the way you enter transactions, you should note the following points:

  • The program checks the status of a fiscal period when you enter certain dates in Project and Job Costing transactions.
  • Locking a fiscal period for PJC does not normally prevent other Sage 300 programs from updating information in the Contract Maintenance screen. For example, posting a job-related invoice in Accounts Receivable or Accounts Payable updates the associated values for the contracts, projects, categories, and resources in PJC.

    An exception to this rule can occur if you post material usage or material return transactions to a period that is later locked for PJC. If the period is locked before running Day End Processing, Day End Processing will not process these transactions, and will generate an error. To clear the error, you must unlock the period for PJC, and then run Day End Processing. (Material allocation transactions do not produce this error.)

  • Locking a fiscal period for Inventory Control does not prevent Day End Processing from creating transactions for, or from updating contracts in, PJC. However, if the period is locked for PJC, you might not be able to post the transactions in PJC.
  • You can create revenue recognition worksheets for a period that is unlocked for Project and Job Costing. However, if the period is locked for General Ledger, you cannot post the resulting batch in General Ledger. If the option to create and automatically post G/L batches is selected on the G/L Integration screen, the transactions will be placed in an error batch in General Ledger when you post the worksheet.
  • You can create G/L batches for a fiscal period that is not locked for Project and Job Costing. However, if the period is locked for General Ledger when you try to post the G/L batch, the transactions will be placed in an error batch in General Ledger. If the option to create and automatically post G/L batches is selected on the G/L Integration screen, the transactions will be placed in an error batch in General Ledger when you create the batch in Project and Job Costing.

For a complete list of customer-facing changes and upgrade information for Sage CRM 7.0 integrated with Sage 300 6.0, see the Sage CRM Integration Update Notice.

For system requirements and instructions on setting up Sage CRM integration with Sage 300, see the Sage CRM Integration Guide.