Highlights in DC1 V10

• Define Line promotions as “Selectable”, meaning that order handler must manually apply the promotion.
• Order-level promotions, i.e. promotions based on the total order. Can apply automatically or manually.
• Define FOC items for order-level promotions.
• Extended functionality around how to set up and apply FOC items.
• Better follow-up functionality.

• Set-up controls what you want to restrict: What, From where, To whom, By whom

Other features that can be configured include:

• Validity period.
• An alert message to send to applicable personnel.
• Additional restraints to be applicable for the order line (minimum/maximum amount/quantity) or order (minimum/maximum amount/quantity).
• Exceptions to that defined in the purchase restriction, permitting the purchase under certain circumstances or with a lower degree of severity.

The degree of severity placed on the purchase restriction drives the handling of the order. Setup choices include Purchase not allowed (entry of order line will be stopped), or Warning (PO entry clerk will receive a warning but order line entry can proceed)

1. WAREHOUSE (warehouse code is secured as object). Used to secure access to warehouse operations like confirm pick list. List of all protected programs are available in system (via Where used option).
2. WHS_VIEW (program code is secured as object). Introduced to improve performance, this is used only to switch on/off Warehouse control on sub-files on selected programs. When this security is activated, only transactions for the allowed warehouse will be displayed on sub-file screen.

Stock take lists created for RF terminals could be maintenance only when all RF batches are closed (status 40).

Note: RF batches are not updated when quantity is manually changed.

• New Asset balance list based on the former Asset balance list (which is still available). The new list has additional selection and printout options.
• Able to define 9 depreciation types in DC1, using various depreciation rules but also various asset values that are different from the acquisition amount. That amount, now used instead of the acquisition amount to calculation residual value, is displayed on the new Asset balance list as the base depreciation amount.
• Base depreciation amount parameter is assigned to each depreciation type in Depreciation type table

In previous releases the Work with A/P payment proposals routine creates A/P payments to settle either unlimited number of transactions or a single transaction.

Now it is possible for A/P payment modes dedicated for Credit Transfer/SEPA to create/maintain A/P payments to settle a limited number of transactions.

Two new Split codes:

Split code 3:
Has the same functionality as the old code 1 but is only performed if no invoices exist on the credit note’s payment date (proposal number, payment mode, currency, supplier, payee, bank and payment date).
Note: The split does not affect unique payments.

Split code 4:
Has the same functionality as the old code 2 but is only performed if no invoices exist on the credit note’s payment date (proposal number, payment mode, currency, supplier, payee, bank and payment date).
Note: The split does not affect unique payments.

• If a Paypal-like fee is loaded into DC1 Financials A/R payment and settlement interface files as an A/R debit payment, DC1 Financials can automatically create a difference document that will settle this payment.
• Difference document type is defined for the applied settlement option.

• Integrator interprets and imports A/R payments from the ISO 20022 Payments messages BankToCustomerStatementV02, camt.053.001.02, and BankToCustomerDebitCredit NotificationV02, camt.054.001.02 (MDR 2009) and from the Teller Settlement report for Netstore payments to DC1 and starts a job in DC1.
• DC1 processes the imported A/R payments further. If an error is found, the A/R payments end in the Work with imported bank statements routine. Otherwise, depending on the setup, the A/R payments are automatically transferred to be processed further in the Work with open batches routine or they end in Work with imported bank statements.
• For A/R payments ended in Work with imported bank statements, you need to manually transfer them further.
• The imported bank statements in Work with imported bank statements are not deleted before the number of saved days has been reached, allowing you to search for received transactions even after they have been transferred to Work with open batches.

The solution should not be considered as a routine for Bank statement reconciliation.

• Integrator web server giving you the possibility to send G/L transactions created by an external system in a pre-defined XML format (defined by Iptor) via Integrator to DC1 Financials. This allows you to integrate DC1 Financials with, e.g., a payroll or travel expense system.
• Mapped data is loaded to the new, externally accessed interface files.
• The import is currently triggered via the Retrieve financial transactions routine.
• Zero VAT transactions holding only VAT reference amount can be generated automatically at import.

Now it is possible to create Demand plans based on Period forecast. These can be seen as ‘Time stamps’ of the quantity in Period forecast when the demand plan was created, to be used in the future to be able to see what the forecasts used to be in the past. Alternatively, you can create a Demand plan based on Period forecast, review it, and make some changes if need be, and then push it back to the Inventory control file to be used in the Inventory calculations.

1. Item interface file building
2. Picklist interface file building.
   This includes the following functionality:
   1. Outbound item interface file (WHOPAPRG)
   2. Outbound picklist interface file (WHOPAPLI)
   3. Fix program for updating pick methods
   4. Initial load panel for picking method program (Menus and menu options)
   5. Existing program updates for triggering the picking automat functionality and data building.
   6. Work with zones program updates for maintaining new field (PIME-Picking method)

• Changes implemented for manufacturing program to create instructions for material issue (*MOI) and manufacturing reception (*MOR).
• Extended validation for creation of manufacturing order. Not permitted to use order type defined with backflushing when warehouse is using NuRF.

• Includes functionality to send manufacturing orders to WMS system, which includes SROSNDMOH (order header) SROSNDMOA (Alt products) and SROSNDMOM (Order materials).
• Note: Manufacturing order operation is not sent. The process around operation must be handled within DC1.
• Reported result from WMS system includes the following message:
  
  – Order start. (WMSC429A)
  
  – Order reception. (WMSC429B)
  
  – Order close. (WMSC429C)
  
  – Material issue. (WMSC430A)
  
  – Material close.(WMSC430B)

• Inventory turnover report
• Customer service report
• Slow stock list
• Item analysis printout
• Non-conforming stock print
• Open sales orders list
• Sales statistics printout
• Purchase statistics printout
• A/P detail balance list
• A/R cancel settlement list
• Invoice/order matching list
• A/R & A/P analysis list
• EU VAT sales report
• VAT declaration lists
• A/P cancel settlement list