Highlights in DC1 V11

Available quantity: This column displays the availability for the item according to today’s date.

Available date: If the available quantity in stock does not cover the quantity on the sales/quotation line, this column displays the date, according to the time axis, when the quantity will be available.

A Due date calendar field has been added to the Terms of payment table. If a due date calendar is defined on the TOP, it will be verified that the calculated due date is a working day according to the defined calendar. If not a working date, the next working date will be used as due date.

1. In previous releases it was only possible to activate one DI method per DI document. This has now been changed for ORDRSP and DESADV. For these DI documents it is now possible to activate DI method ACCEMAIL together with one other method. This means that it will be possible to both send, e.g., an EDIFACT-message and an e-email.
2. It is now also possible to define a sales order type to ignore the sending of DI, even if this is defined for the customer.

This enquiry has been enhanced as follows:

• Non-stocked items (item class = 2) are displayed if there is available stock <> Zero (including all orders regardless of planning time). If there is available stock of a non-stock item, it shall always be considered as excess stock, since it is never purchased to put in stock. (It could be a customer return that created this situation).
• Item class has been added as an XT column.

The Default and replacement table has been preloaded with the following keys: IRO and MDC (Group = ORDSRACT, Level = ORDSOURCES).

A new option has been introduced in Work with pickings, making it possible to cancel a part of or the entire pick confirmed quantity.

The Drug Supply Security Act (DSCSA) is forcing pharmaceutical wholesale distributors to adhere to a stricter process of traceability and reporting. These new regulations will enhance the ability for US Food and Drug Administration (FDA) to protect consumers from stolen, counterfeit or potentially harmful drugs.

In order for DC1 to accommodate this new regulation, Pharma serial number functionality is developed. This allows the possibility to keep serial numbers for batch items, on each unit activated for an item. This means that if a user scans the serial number for, e.g., a whole pallet, the system will know the serial numbers for all inner boxes down to the serial number for each specific piece of unit.

Pharma serial number handling is available in all processes that affect stock. Each action for a Pharma serial number is saved in the Pharma serial number history. This makes it possible to follow the history for a specific serial number allowing tracking to see from where it was purchased and to which customer it was sold.

Purchase pricing is enhanced to give it more flexibility and to utilize some of the functionality within DC1 that already was available for sales pricing.

This enhancement includes:

• Purchase price lists – Functionality to create price lists and allowing item purchase prices for the same supplier but for different price lists.
• Purchase pricing methods – Functionality that allows flexible set-up of purchase prices and discounts using DIS control keys; similar to the existing Sales pricing methods functionality in DC1. Note that Purchase pricing methods does not include all functionality that exists for sales pricing methods. For example, it will only be possible to create methods for types N (Normal) and C (Chain discounts).
• Limit dependent pricing – Purchase price 1 – 5 are removed and replaced with the same type of limit dependent pricing that is exists for sales pricing. This allows the system to handle an unlimited number of quantity or amount limits, each holding a specific price or discount.
• Purchase line discounts – Discount percentage fields 1 – 9 are removed. Instead the functionality for adding discounts to, e.g., a purchase order line is changed to work in the same way as it works for sales order lines. This will allow the system to handle an unlimited number of discounts for, e.g., the PO line, and it will be possible to mix discount percentages with discount amounts.

The possibility to also view the “Received order value” on purchase orders, and “Invoiced order value” on sales orders has been introduced via new fields in the purchase order header and sales order header.

You can view the new amounts in the header sub-file, via the Edit columns feature, in the programs listed below. Note that in the purchase related programs, the amounts can be viewed in both order currency and system currency. In the sales order related programs, the amounts can be viewed in order currency.

• Work with purchase orders
• Purchase order enquiry
• Work with held purchase orders
• Work with sales orders
• Sales/Service order enquiry
• Work with held sales/service orders

To expedite the process, a new Item sales price reorganisation program has been added. Via this program, the user can delete sales prices that are older than the given date, for a specific sales price list, or for all sales price lists.

• Introduction of license plate picking
• Inbound shipment handling from R/F
• Inventory transaction from R/F
• R/F performance reports
• Dynamic allocation of default zone/locations (earlier set up at the warehouse level)

Changing the customer number can, e.g., be useful for companies that work with cash sale orders. If an error occurs during the registration of the cash sales order, and the sales clerk has access to several customer numbers, one could switch to a customer number that carries the correct prices to avoid having to re-register the entire cash sales order.

Changing the sales order type can, e.g., be useful for companies that work with cash sale orders. If the customer decides that the order should be invoiced instead of being directly paid, this new functionality makes it easier to handle this situation.

The below mentioned UI_fields have been added to DSR12101 and DMR30001 panels:

Del addr name
Del addr 1, Del addr 2, Del addr 3, Del addr 4
Del addr postal
Del addr country
Del addr county
Del addr St/Prov
Inv addr name
Inv addr 1, Inv addr 2, Inv addr 3, Inv addr 4
Inv addr postal
Inv addr country
Inv addr county
Inv addr St/Prov

The following selection fields have been added to the DSR12111 panel:

Item
Warehouse
Batch
Pick list
Transport note
Note: Selection of both Batch + Pick list and/or Batch + Transport note has been restricted. The user will not be able to use the above mentioned field in the more selection functionality to select required records.

A new First panel field has been added to the View control function making it possible to control which panel to display first when accessing the enquiry. User can choose from the following:

Order header
Order header more selections
Order lines
Order lines more selections

A new function key has also been added on the More selections panels making it possible to switch between viewing the more selection possibilities for order header and lines.

• If any of the sales order panels for header and/or addresses should be mandatory to run through for a sales order handler
• The sequence of the panels for header, addresses and lines

It is also possible to set the system up to not print/send the sales prices on the SO confirmation.

• Stock take templates – new functionality has been added making it possible to save a specification and selection for a stock take creation. This makes it easier to regularly run the same kind of stock take.
• New function key to set all not counted lines equal to zero
• New sequence fields
• Possibility to define the stock take creation to break into several stock take lists
• New selection fields. The existing selection fields have also been changed to use standard DC1 selection codes
• Print stock take control list in line sequence.

• An All warehouses view has been added. This view displays pickings for all warehouses.
• Requested dispatch date has been added as a new XT column allowing you to more easily decide what picking is the most urgent.

SIE (Standard Import Export) is the Swedish import/export report file standard for transferring account balances and transactions (financial reporting data) between different programs. The SIE format has become the de-facto standard in Sweden.

The standard has been agreed by a group of administration program developers (known as the SIE-group. See SIE Gruppen)

The concerned routines are the following:

• Work with SIE export options (new)
• Work with IFS communicator types (prerequisite)
• Work with default and replacements (prerequisite)

To support the situation when an item’s commodity code is changed after the concerned Sales/Purchase orders are completed, a Change commodity code (Y/N) field has been added where you indicate whether the original or new commodity code should be applied at declaration print.

Processing – Credit notes not related to goods transfer

If both the Credit note and the credited document belong to the same declaration box, the declared amount of the credited document is adjusted/decreased with the credit note amount.

Processing – Invoiced ancillary costs

For some countries (like Finland) where VAT is posted on G/L level, certain costs (costs posted with VAT code applicable for goods transactions) are to be declared as part of goods transfer. These invoiced costs (total amount), which are referred to as invoiced ancillary costs, are now updated in the Intrastat file and, at declaration print, are allocated proportionally between the Intrastat transactions created for the invoiced item related lines.

A dedicated commodity code is used for such cost related Intrastat transactions, and it is identified by its Commodity code type. The Commodity code type is a new field added to the Commodity codes table.

New column Reported has been added to the printout to indicate if a transaction was already printed on a Final declaration.

• A/P payment proposal control list
• A/P, A/R and G/L revaluation list

When a G/L revaluation transaction is posted on a Cash book control account, then the corresponding transaction, with a dedicated revaluation type, is automatically created in the Cash book ledger (SROCBA file).

• New option A/R – A/P document has been added to view details of an A/* document to which the indicated accounting belongs.
• Aperio panel to view A/* document on the XT UI panel when the focus is set on a sub-file line (Note that this is ongoing and planned for 11.01)

Possibility to create RF Creditor Reference (Bank reference number) to selected debtors.
The variable part in the RF number is defined in the Control file.
The check digits part in the RF number are calculated according to the RF Creditor reference rule.

Possibility to validate Bank reference number according to the RF Creditor reference rule. If it is not a RF number, the number is validated according to existing local rules (OCR in Sweden, KID in Norway, etc).

Creditor Reference number ISO11649 is supported by the following ISO20022 messages:
pain.001.001.0x
pain.008.001.02
camt.053.001.02
camt.054.001.02

Please note that usage of Creditor Reference number ISO11649 in other file formats must be verified with concerned banks.

In Work with FIN agreements you enter an agreement header (a binder enclosing the indicated Business partner’s agreements) and drill down to enter and/or maintain BP’s external/internal agreements.

By setting up FIN agreement groups, you have a possibility to group agreements into different groups and prevent users from viewing/using all agreements.

The possibility also exists to print either External reports for the selected business partners, or Internal reports.

Agreements can also be reached from Work with reminders.

Options and selections
The new Payment order option creates transactions to Work with A/P payment status reports.

The Change option is protected when transaction have been created to Work with A/P payment status reports.

The Display and Payment status reports options are new.

The selection on Bank reference number is enabled on the following panels:

• A/P payment proposal, Add document
• A/P payment proposal, Paid documents (display mode)

New selection fields have been added on the Work with A/P payment proposal, Overview panel.

New fields in Work with Credit Transfer schemes are enabled and affect creation of the ISO20022 pain.001.001.03 (MDR 2009) file for all scheme versions.

Local schemes CT/SEPA ISO 20022 pain.001.001.03 (MDR 2009)

Norway
Local NO ISO 20022 pain.001.001.03 (MDR 2009), version 1.5, is enabled.

Switzerland
Local CH ISO 20022 pain.001.001.03 (MDR 2009), version 1.7.2, is enabled.

Sweden
Local SE ISO 20022 pain.001.001.02 (MDR 2009)
The new Short name version field in Work with Credit Transfer schemes affects creation of the file format ISO 20022 pain.001.001.03 (MDR 2009). The new field replaces the Bank groups SEB and NOR.

Import payment status reports in the XML format ISO 2002 pain.002.001.03 is enabled.

The message provides information about the payment status (e.g., rejection, acceptance) of the Credit Transfer initiation sent to the agent.

The process starts from Work with A/P payment proposals when the routine creates the XML ISO20022 pain.001 file and saves the payments and payment details (paid documents) in Work with A/P payment status reports.

Integrator interprets and imports the ISO 20022 pain.002.001.03 file and starts a job in DC1. The setup in DC1 controls if the import will be done automatically or manually from Work with imported A/P payment status reports.

DC1 updates the imported payment status information in Work with imported A/P payment status reports for found payments, and the rejected payments are also deleted in the A/P payment proposals.

Work with imported A/P payment status reports:

• Displays payment details (paid documents) and related payment saved from A/P payment proposal. See above.
  From payment details you reach the payment and the imported payment status reports as well as information when the imported payment from the ISO 20022 camt.054.001.02 Debit Notification file was updated in the A/P ledger and G/L ledger.
• Possibility to import unprocessed payment status report files.

Import A/P payments in the XSL format ISO 20022 camt.054.001.02 provided as Debit Notification is enabled.

The message provides information about the A/P payments withdrawn from the bank account.

The process starts from Work with A/P payment proposals when the routine creates the XML ISO 20022 pain.001 file.

Integrator interprets and imports the ISO 20022, camt.054.001.02 Debit Notification file and starts a job in DC1.
The setup in DC1 controls if the import will be done automatically or manually from Work with imported A/P bank statements.

DC1 processes the imported A/P payments and for found payments in A/P payment proposals updates A/P ledger and G/L ledger via Work with A/P payment proposals, update and receives a status code in Work with imported A/P payment status reports if used.

Work with imported A/P bank statements is a limited version to import A/P payments from camt.054.001.02 Debit Notification and update A/P ledger and G/L ledger.
The routine displays all imported files. Possibility to toggle between processed/unprocessed files and to import unprocessed files. No possibility to drill down to view any details.

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

Bank deposit data belongs/is linked to a Cash book related payment.

The Change option is protected when transactions have been created to Work with A/R payment status reports.

The Display and Payment status reports options are new.

Bank reference number selection is enabled on the A/R payment proposal; Paid documents (display mode) panel.

New selection fields are added on the Work with A/R payment proposals; Overview panel.

SEPA Direct Debit
From Work with A/R payment proposals maintenance panel you reach SEPA Direct Debit payment details to override data from the Business partner’s A/R payment mode data.

The message provides information about the payment status (e.g., rejection, acceptance) of the Direct Debit initiation sent to the agent.

The process starts from Work with A/R payment proposals when the routine creates the XML ISO 20022 pain.008.001.02 file and saves the payments and payment details (paid documents) in Work with A/R payment status reports.
Integrator interprets and imports the ISO 20022 pain.002.001.03 file and starts a job in DC1.
The setup in DC1 controls if the import will be done automatically or manually from Work with imported A/P payment status reports.

DC1 updates the imported payment status information in Work with imported A/R payment status reports for found payments and the rejected payments are also deleted in the A/R payment proposal.

• Work with imported A/R payment status reports:
  Displays payment details (paid documents) and related payment saved from A/R payment proposal, see above. From payment details you reach the payment and the imported payment status reports as well as information when the imported payment from the ISO 20022 camt.053.001.02/camt.054.001.02 files was transferred from Work with imported bank statements to Work with open batches.
• Possibility to import unprocessed payment status report files.

• A/P invoice enquiry
• A/P settlement entry
• A/P settlement enquiry
• A/P invoice matching – search additional lines
• G/L transaction enquiry

Inventory management info
When initialising the Inventory management information file (SROIMI) in a new warehouse, it could previously only be done from a default setup using the item templates/defaults. This meant that all items in the new warehouse received the same setup.

However, if you already have a warehouse with the same items and you want to have the same setup in the new warehouse, you can now enter a warehouse from which the item setup will be copied.

Forecast file, customer demand, and production demand
When initialising the Forecast file, Customer demand file, and Production demand file in a new warehouse, it could previously only be done from existing data in the Sales statistics file (SROISDPL) and Open sales order lines in SROORSPL. This meant that if there was no historic sales in the new warehouse, no history could be built.

However, if you already have a warehouse with the same items and you believe that you will have a similar sales pattern in the new warehouse, your forecasts in the new warehouse would benefit significantly from better historical data if you could copy historical demand information from one warehouse to another. A function exists allowing you to copy forecast and demand data from one item/warehouse to another item/warehouse, but this requires the manual task of drilling down into each item/warehouse and clicking a function key. Depending on the number of items, this could take significant time.

To decrease the amount of manual work and time, you can now enter a warehouse from which the demand data will be copied.

However, when creating forecast in the Forecast file, the number of years has been restricted to one year into the future. For long range planning, a forecast creation for one year into the future has not been sufficient.

A Future years field has been added to the IC control file giving you the possibility to enter a value of 1 to 9, denoting the number of years into the future (the possibility of up to 9 years) you want to create the forecast.

This flexibility is achieved with the possibility to define rounding rules in percentage, on Item/Warehouse level, to denote if the suggested quantity should be rounded up or down to the closest pallet and/or pack size, or if the pallet/pack size should be broken. It is also possible to enter a number of multiples that will always induce a round up (i.e. when you reach a certain number of pallets/pack sizes you stop breaking them).

Note that if no rounding rules are defined, the system will work as before, i.e. always round up to the next multiple of pack size with no consideration of pallet size.

The processes that use these rounding rules are:

• Create purchase suggestion
• Create internal replenishment suggestion
• Interactive line buy (Increase order size).

A new table, entitled Work with suggestion blocks, with a header and a detail level has been introduced.

On the Suggestion block detail level it is possible to enter one or several entries denoting the time frame in which suggestions are blocked (i.e. From MMDD and To MMDD).

On the Suggestion block header level, the following two parameters exist:

Buy to sales order
If this parameter is set to NO, then suggestions will always be blocked.

If this parameter is set to YES, then suggestions are blocked, but the block is ignored if sales orders for this item are waiting to be picked. The item will appear on the suggestions with just enough quantity to cover what is already sold.

Date comparison
This parameter denotes if block dates should reflect the ‘Suggestion run date’ (today), or Expected arrival date’ (Today + planning time).

An item/warehouse is connected to a Suggestion block by entering the Suggestion block on the Item file maintenance, Inventory management panel. The IC purchase suggestion creation and IC internal replenishment suggestion processes will search for blocks before creating the line. Note that only automatic creations of suggestions will be blocked. It will still be possible to manually enter purchases and replenishments.

The manual process to move suggestion lines to an internal replenishment suggestion can be time consuming if there are a large number of lines. To expedite this process, Supply exception policies are now available which will automate this process. By using a Supply exception policy, the manual step to move suggestion lines to an internal replenishment suggestion is no longer required.

The automated process works as follows:

• When you want a warehouse to look for excess stock in other warehouses before suggesting a supply from an external supplier, a Supply exception policy for each warehouse can be defined in the Item file on the Inventory management panel.
• When the job is run to create purchase suggestions from external suppliers, if the system can find a warehouse in the supply exception policy that has excess stock, the system will create an internal replenishment suggestion instead from that warehouse.

This will lead to lower stock levels and less tied up capital since the excess stock is being used in a more efficient way.

In addition, for non-BtB orders, the calculated priority value on the order when the order was created can be useful to select orders for batch clearance function. A Calculated priority value selection parameter has been added.

To expedite the structure maintenance for these kinds of changes, two new tables (Work with master BOR and Work with master BOM) are now available to be used in the normal structure maintenance.

When you refer to a master BOR and/ or master BOM on the structure header by entering the BOR and/or BOM ID, the details are copied to the normal structure files.

If a master BOR or BOM is used on a structure, the operations or material from a master BOM BOR should not be available to maintain on the items structure as those are created from a master, but it will be allowed to enter additional operation and/or material.

A new selection parameter (Include sales return) has been added for sales order return (stock update), allowing you to decide if those should be included in the MRP or not.

In the MRP re-scheduling function a new option has been added to be able to re-schedule the order according to the suggested “new requirement date” without going into the order maintenance and performing the changes.

When this new enquiry is displayed the cost elements are re-calculated so that included sub-assemblies within an order in the network are removed from the parent (material cost). Instead the cost of the sub-assemblies cost elements will be added to the parent order. The same re-calculation will be done for the sub-assemblies order/item if there are also sub-assemblies items/orders (lower levels).

With this new enquiry functionality, the following views are available:

• Element details – Displays the cost for all orders within the network by order
• Expand by order – Displays the costing elements by order
• Expand by oper – Displays the costing element by order/operation.

• Calculate one level, now making it possible to run the costing for one level. This means that structures will not calculate to the bottom unless there are phantoms, which is similar to how it works for a manufacturing order.
• Last pur price (in the Item cost type section), making it possible to use the last purchase price as the item cost type.

Formulas can be used to retrieve default value for an attribute or on components in CFG BOM to calculate additional price that will end up on the sales price on the CFG end item.

A new variable has been added for Discounted sales price (&62) to allow you to extend the different prices that can be retrieved, but will not change the standard CFG solution that drives the formula calculation when adding component prices to the parent configuration sales price.

Currency code has been added in basic data BOR and on manufacturing order operations. Only system currency and supplier primary currency will be valid. If you leave the new Currency code field blank, the currency will be according to the system currency.

This change affects:

• Basic data maintenance
• Basic data product costing calculation
• Product configuration, including MDC handling
• Project operation maintenance
• Manufacturing order creation
• Manufacturing order operation maintenance
• Purchase order creation from sub contract operation
• Purchase order reception update to manufacturing order operation
• Manufacturing order statistics creation

Warning message DM307FB “Warning: Normal stock holds quantity to cover requested quantity” has been preloaded in standard DC1 to be used as an example for other messages for customer modifications.

For debtors defined to use the RF Creditor Reference, the local Payment ID is not printed on the external documents above. It means that these debtors cannot use the payment ID as a reference for the payment.

Standard handling of Bank reference number applies for the solution.

Standard handling of Business partners’ bank data applies for the solution.

The validation method N08 (8 digits mandatory) is new for validating bank account number. The new validation method is not country specific.

It means it is possible to select a dedicated Printer queue which enables Printing to Excel and to save a file created at the declaration print, as an Excel or CSV file. The save function is available on the Work with spool files XTUI panel.

The file format and its content is defined according to the Finnish regulation described in the Instructions for creating and uploading CSV files document

To fulfil the Finnish regulation the following handling of Credit document applies:

Credit purchase orders not related to goods transfer are not included in the Finnish declaration.

Sales credit notes not related to goods transfer are included only if the credited document is found an belongs to the same declaration box.

Invoiced ancillary costs
For Finland and for some countries where VAT is posted on G/L level certain costs (costs posted with VAT code applicable for goods transactions) are to be declared as part of goods transfer.

These costs which are referred to as invoiced ancillary costs are now stored in the Intrastat file and, at declaration print, are allocated proportionally to the reported item line amount.

Goods related cost amount calculated/allocated between invoiced lines and printed on the Final Intrastat list is now stored in the Intrastat file.

• New functionality supporting VAT regulation – Split payment functionality.
• “Loading bank statements” function merged to the country standard (function available in release 6 as a PL country modification).

Sending/receiving local Direct Debit (Autogiro) payments in the BGC layout from 201607 is enabled.
No new functionality has been added.

Work with BG Autogiro control file (former name Work with Bank giro Autogiro proposal) controls the Direct Debit (Autogiro) file version from/to BGC.

New fields exist in Work with business partner A/R payment mode, AG09.

• SIE export options
• IFS communicator