ERP-RO01-6.1.0.1

A Romanian version will soon be available here:
https://ebs.socrates.academy/note-de-versiuni/index.html

New features and extensions

1. Miscellaneous improvements

1.1 Updating a Person's activity by profession

A new possibility was implemented in the Person entity, to prevent the Activity being updated by the Profession of the person. Until now, by manually changing the profession, the activity was automatically updated.

For example, the Activity of this person is “RETAIL SUPER MARKET COMMERCE, SPECIALIZED IN THE FOOD INDUSTRY”:

With the default behavior of the application, by changing the Profession to "SUPER MARKET", the Activity automatically changes to "Super market":

For cases where the user wants to avoid this automatic updating, a new company parameter was created in the Contact administration category, “Update person's activity from description” (UpdatePersonActivityFromDescrition), with default value True.

When the value of the parameter is YES, the Activity of the person receives the value of their profession. When the value of the parameter is NO, then the Activity of the person if they already have a value does not receive the value of their profession.

1.2 Stock valuation - Cost Prices per period and branch

An improvement was made in the "Cost prices per period" dialog in order to be easier to use.

By default, the Period field now comes empty. This way, when the user enters a Period and focus somewhere outside the field, a arrow appears to the left of the line that was just filled in. By pressing this arrow, the form with the fields for the "Cost prices per site" opens below.

1.3 New UDFs in Services

In the Service entity (Menu > Sales > Items & Prices > Services), 2 additional user-defined fields were added. These fields can be added to the form using the Form Designer (Ctrl + Shift + F8).

From the Entity fields, select Entity fields > Item and you can add Flag 11 and 12 anywhere you wish in the form.

New features and enhancements in the Romanian version

2. Use of planning of payments for VAT on payment invoices

The existing functionality of Payments planning has been extended in order to cover the invoices with VAT on payment.

The details of the existing process are described in EBS User guide (application folder ESBooks, chapter Planning of Payments).

What is new:

• At the detail level, invoices info, the field VAT on payment is visible
• The creation of the payment document verifies this field and, in case of VAT on payment invoices, it fills in all needed details.

In case the user selects multiple invoices, with/without VAT on payment status, there will be created 2 documents for each status.

This way, the process fully covers:

• Accounting entries
• Operational entries
• VAT statement

The new document type used is PMF, described in the section New document types.

The change of company parameter TRANSFERS_PAYMENT_PLANNING_DOC_TYPE is needed.

The document will be included in the scroller Cash transfer Payment planning, used to export the payment file for the bank.

2.2 Improvements in D394 Statement

Under menu Accounting\Financial declarations\Data calculation, a new entry has been added: Calculate data Declaration D394(2025)

This option did not change the actual way of calculation but it uses only ES files. This will ensure an easier maintenance in the future.

The improvements were added to the automation that creates the .xml file of D394:

Section “Detaliu”. It is reconciled with section OP11, in case of transaction types C or V.

Sections Series and Invoices: covers sending either only the Serie code (as it is now, in most cases) or Prefix of the document type plus the Serie Code. By default, only the serie code is sent.

2.3 VAT non-deductible

A new scroller has been added under menu Accounting\Period completion processes\VAT Tasks: non- Deductible VAT.

The report contains all purchase invoices that contain at least and belong to the selected Reference period.

The criteria Reference period is related to:

• Invoice registration date – if it not under VAT on payment
• Payment registration date – if it is under VAT on payment

An automation is available, for selected invoices, to transfer the non-deductible VAT on an expense item. The created document type is OED, located in Accounting\Expenses\Expenses – adjusting entries.

The needed configuration is referring to limited deductibility. In this case:

• 2 different generic items should be used: one for the deductible part and the other for the non-deductible part.
• Each generic item should have separate analytical accounts.
• The deductible item should have:

• 50% in the field % Tax exemption

• The GL account related to the non-deductible item in the field Account for differences.

This configuration will serve not only the scroller but:

• Use of the automation nonDeductible (available in the source invoice).

• Appropriate Tax Codes in SAFT General Ledger Entries.

2.4 New document types

Several new document types were created to serve various transactions registrations.

The process of importing them is the know one, via Import from Entersoft xml (from ESMasterConfig\2.Document Types)

Stock transfer with cost (SAE)

This document type is recommended in cases when:

1. One item is transferred from one branch (independent) to another one
2. One item balance is transferred to another item (same or different branch)

The document type is located in Inventory\Stock entries\Stock adjusting documents.

In the first tab the import items will be registered while in the second tab the export items will be registered.

In order to link the cost between the items in both sections, action Cost transfer, from the first tab, will be used.

The user will have to choose the export items that will “give” cost to import items.

During the stock valuation, after the export items will be valuated, their cost will be allocated to import items. In case import items have also export transactions, stock valuation will allocate the appropriate cost.

Corrective entry of Pending Orders (DRP)

It is used to correct the pending quantities from orders e.g. Expected from suppliers, Customer orders, Reserved.

In the first tab quantities to be increased will be registered. In the second tab, quantities to decrease will be registered.

The document type does not affect the dimensions of the items.

The document type is located in Inventory\Stock entries\Stock adjusting documents.

Corrective entry of Pending Orders by dimensions (DRS)

It is used to correct the pending quantities from orders e.g. Expected from suppliers, Customer orders, Reserved.

In the first tab quantities to be increased will be registered. In the second tab, quantities to decrease will be registered.

The document type affects only the dimensions of the items.

The document type is located in Inventory\Stock entries\Stock adjusting documents.

Expenses capitalization to fixed assets (CCHV)

This document is used to transfer expenses to fixed assets for depreciation purposes. You must enter the fixed asset to be debited in the first tab and the expenses to be credited in the second tab. The credited amount must equal the debited amount.

For the fixed asset, the value will be added to the selected depreciable acquisition.

The document type is located in Accounting\Fixed Assets\Adjusting entries.

Transfer between third parties (ANK)

This document is used to transfer stock items or fixed assets from one trade account/branch to another trade account/branch.

The document type is located in Inventory\Stock entries\Item movements.

Receipts from third parties (Cost of other imports) PCT

It is used for the receipt of goods from a business partner, tracked as a third-party warehouse. The business partner is specified for informational purposes at the header level. The warehouse from which items or fixed assets are issued is the "Default Warehouse" associated with the document series, while the destination warehouse is specified in the "DESTINATION" field. It updates costs and quantities for other inflows (positive for the destination branch or warehouse, and negative for the branch or warehouse associated with the line item). It proposes a suggested valuation (spot value), which can be modified by the user and is not altered by the valuation process. If a journal is specified, the accounting records are updated. It also covers the return of fixed assets held in custody.

The document type is located in Inventory\Stock entries\Item movements.

Delivery to third parties (Cost of other exports) AXT

It is used for shipments to a business partner where the goods are tracked as third-party inventory. The warehouse from which stock items or fixed assets are issued is specified in the header's "Position" field, while the warehouse receiving the items is the document series' "Default warehouse." The business partner and delivery address are entered in the header under "Destination." It updates quantities associated with other issues (positive for the issuing branch or warehouse, and negative for the destination branch or warehouse). Valuation updates the cost of these entries.

The document also covers the transfer of fixed assets into custody.

The document type is located in Inventory\Stock entries\Item movements.

Payments to multiple suppliers (VAT on payment supported) PMF

The document type combines the functionalities of 2 existing document types:

• FPL – Bank account credited versus multiple supplier lines debited
• DPV- impact in VAT journal for cases with VAT on payment plus accounting and operational impact. Used as one document for each trade account.

The PMF document contains:

• In header: the cash/bank account. In case VAT on payment is involved, this field will be filled in accordingly.
• In supplier lines: all suppliers and amounts paid.
• In Related items: the invoices that are paid, in case of VAT on payment. This is needed for VAT statement reasonings.

The document is recommended to be used in the process of Planning of payments. The advantages are:

• Automatic creation of documents split in cases with/without VAT on payment.
• All necessary fields are filled in by the automation
• The matching between payment and invoices are automatically done.

The document type is located in Accounting\Accounting processes\ Trade accounts corrective entries.

2.5 Improvement for pharma sector

A new document type has been created in order to register the stock items and the batches that are about to be withdrawn from the market.

The document is located in Inventory\Stock entries\Stock adjusting documents.

In the lines of the document will be registered all items involved in the process of withdrawal.

A separate tab, Distribution List, presents all trade accounts to whom these items were delivered. 2 automations create separate document types for Notifications to be sent to each trade account.

Bug fixes

General bug fixes

Document Types\ Series

• Encountered an error that appeared on the Documents and Series > Document Series > Document Series List > Open Series screen, in seven-digit counter series.

Delivery – Invoicing

• Fixed an error that would occur when transferring a value from previous item movements, where the system incorrectly transferred the value to a base MU instead of the selected alternative MU. The value is now transferred and calculated correctly based on the MU selected by the user.
• The "Update meteo data" service for the “Items sales in relation to weather conditions" cube had stopped working due to the removal of the old Yahoo weather API. It was replaced with the Google weather API and at the same time the retrieval table for branch geographical coordinates updated from the old ES00GSMGeoLocation table to the new ESGOSites .

Orders – Reservations

• Fixed an issue of failure to assign a route from an address in documents.

Projects - Contracts

• Fixed an issue where the project name would not display when selecting it in the  LineItem of Cash documents.

Fixed assets

• Fixed an error “VAT calculation basis” field (VATCalculationValue) on the fixed asset management screen, which was not working via the UI, causing Margin Profit Plan settings not to be saved properly. The field now functions normally without the need to use mass change as a work-around.

Master entities (Item, Trade account, Person, etc.)

• Fixed incorrect system behavior in the configuration of the debit/supplier codes, during which the system checked the length of the code and created a new one only under certain conditions of character number.
• Fixed an issue that caused the erroneous calculation of the schedule and Expiry date in a Document payment settlement.

Import\Export & Migration

• When creating or executing an EMI with a target entity "Service request (lite)", a DataSet initialization error would occur, due to null foreign column in ServiceRequestLiteDS, so that no EMI using this entity could be executed. The problem has now been resolved.

ODS Extender

• It is now possible to assign a GID from another company's ESFILineItem to an extension field without being rejected by the ForeignKeyConstraint check. Through the new checkbox "Cross Company" in the Entity Designer, the user can define the assistant relation that overrides the company filter and allows the assignment of a GUID from any company.

EAS Performance

• When running Tools > Connection to the application server > Network metrics, the result diagram would not display due to the use of an old (outdated) chart component (SoftwareFX.ChartFX). The component was replaced with a new one and the diagram now appears normally with a renewed UI.

System setup

• When attempting to log in via EntraID to version 6.x, an error occurred due to a Microsoft.Identity.Client.Broker.dll library version incompatibility. Login was impossible and there was no alternative. The issue was fixed by upgrading the library.

Miscellaneous

• An Object reference error was encountered in a LEAD context scroller, with the message "An error occurred during search. Please check the search parameters again”.

Relevant cases

PS-114449, PS-114187, ΥΠΘ_SUP-236023, PS-119682, PS-120137, PS-121581, PS-121542, PS-122298, PS-122867, PS-123607, PS-115520, PS-122645, PS-105951, PS-120888, PS-113550, PS-118688, PS-120935, PS-121675, PS-117321, PS-124065

Fixes for the Romanian version

There are no fixes in this version

PDF Version