To better serve budget needs, the previous budget comparison screen was replaced by a scroller where it is now possible to make multiple selections with check boxes and get multiple sheets.

Multiple selection is done as before, i.e. with the Ctrl key.

The use of the new scroller is as follows:

Go to Budgets > Comparative Results > Search... to the Budget Sheets. Select one or more sheets and click Accept in the top right of the criteria, to display the selected sheet in the scroller. Finally, click on Accept at the bottom of the scroller.

image3.png

2. Data import

Data import from multiple companies

In the Configuration > Import/export data > Import data (advanced)… , the EMI was expanded to allow the user to import data from multiple companies, i.e. the system to respect the fCompanyCode column where the data is stored and to open/manage the sessions internally.

This need arises as we need, in a DI scenario, to support data transfer from headquarters to a branch for 9 companies, where the DI is supported via:

9 databases (not acceptable)
9 data types, one for each company (not acceptable)

The extension adds the "Import data from multiple companies" option to the EMI. In field mapping when an entity is imported, the entity's Company field must be assigned to an import source field. This company will then be used when adding the entry. Either the current branch will be used as branch (if it belongs to the other companies for which data is imported), or alternatively a branch to which the user has access.

The process is carried out as usual, except that we first activate the option "Import data from multiple companies" and then click "Run".

For example:

image1.png

image2.png

3. Promotions

The Promotions is an alternative subsystem for applying rate or value discounts to documents. Their special feature is that they are applied directly to the document, depending on the conditions that apply and always with user intervention.

From this version on, a significant extension applies to the offers, and it concerns the possibility of adding a gift to the document.

For this reason, in the promotion configuration screen is now added:

The type of promotion with values:

Item discounts and
Free product

The item-gift and its quantity
The gift quantity in the “Reward data” detail

Each time such an offer applies to a document, that is to say, it covers its target – and if the user selects it through the special form (see details on that in the ReadMe version 5.7.0.0, the free product is added to the specified quantity.

At the same time, “Reward data” defines the additional possibility of differentiating the quantity of the free product according to different values of the target field. For example, if the target of a promotion concerns the quantity of specific items and it's achieved, then up to quantity X 1 piece of the free product is given, while if the target extends up to quantity Y, 2 pieces of the free product are given and so on.

Here are some points that apply with this new feature:

In a new promotion entry, the default value in the Type field is: Item discounts.
In case the promotion type is Item discounts, the fields of the item-gift and quantity are disabled, while respectively, if the promotion type is Free product, the fields related to discounts are disabled (reward, discount % and discount type).
Like discounts, the free product is awarded if the target of the offer applies. The promotion target consists of a target field, a document line value field such as line quantity, value, etc. and a target numeric field, which must be achieved to give the reward.
In the case of a gift item, the "reward field" is by default "Discount1 %" and in the "Reward" field the default value is 100%
The free product after application and acceptance of the promotion by the user is transferred to the line of the document with 100% discount 1
When the target is set per line, then each item line that reaches its target receives the gift.

Additional changes to the Promotions subsystem

If a document has been awarded a discount on a item through the promotions application subsystem, then in the table with the discount analysis, the field "Update source type" received the new Promotion value, while until now it received the Invoicing policy price.
The Promotion application form now displays two different indications for progress regarding the offer application. These are:

Promotion evaluation (lines)
Promotion evaluation (header)

When initializing a document in which the declared display form is a form with promotions, nothing will appear in the list of "Available promotions" if no customer selection has been made. Promotions will appear once the customer is entered in the header of the document and they're the ones to which the selected customer belongs, as well as those that do not have a list of trader accounts.

4. Various Improvements

In Configuration & Tools > Systems Integration, the 11 different “Connection Settings” options for all courier services have now been reduced to one, titled “Courier - Connection Settings” and are now accessible via a sub-menu.

In order to better serve the accounting needs, we created the “Trial Balance (w/ balance analysis)” bit, during the export of which the relevant columns with the balance are displayed: 1. Debit balance – Balance, 2. Credit balance – Balance, 3. Final - Balance. The bit is located in the same folder as the Trial Balance (Accounting > Accounting Reports) and it's accessible from the drop-down menu in the bit title. For the new Bit, only one report was created, with the same columns as the Bit. This change was made in order to meet the need to monitor various different traders with the same TRN.
The "Branch Replenishment Proposal" process (from the Inventory > Replenishment process) is a fairly complicated and time-consuming process. During the execution of the process, there was no indication of the process progress and the estimated time of completion, which caused confusion among users.

For this reason, we added:

a message in the start of the process warning the user of its time-consuming nature and
an informative bar showing its progress, as well as special button where the user can cancel it from

CRM | In the Photo collection action (Marketing > Merchandise > Reports > Photos - gallery) an improvement was made, so that if a photo does not exist, then the process continues and the final zip file is generated. The process produced an error and would not complete, if there was an http folder in the company parameter "Photos from mobiles - Save in folder".

5. Specific improvements for the Romanian version

e-Transport – new automations

Update UIT data - the automation to resend a modified document that already has a valid UIT code was added. This is possible via the e-Transport Update UIT data button.
UIT Confirmation - the automation to receive UIT code confirmation was added. This is possible through the UIT Confirmation button.
Delete UIT - the automation to delete a UIT code was added. This is possible through the Delete UIT button.

Intrastat – additional MU reporting

It has been extended to the area from which the measurement MU of the item is taken if the item has an Intrastat code set with an additional MU.

The current mechanism identifies the MU on the item equivalent to the one on the Intrastat code as follows:

If the MU related to the Intrastat code is the one from the document line: the quantity from the document line is taken.

If the UoM is the basic UoM: take the Quantity field in UMB from the document line.

If the CU is an alternative CU, take the Quantity in the alternative CU from the document line.

If the HU is a Weight HU, take either the weight from the document line, if different from 0, or according to the relationship on the item card.

If the CU is UM Volume, take the Volume field from the document line.

The new functionality continues the check in any of the other CUs on the item card and applies the relationship to the UMB, taking also into account the relationship type.

Other improvements

New format Trade Register Number - Removed the warning that appeared when entering a “J” in the old format.

EBS-RO documentation and translations improvements

For more info, browse the EBS-RO website.

We constantly update it with instructions and documentation in Romanian language.

We also constantly update and correct all translation or localization errors, so that the application will better serve the Romanian users.

Bug Fixes

Horizontal functionality

Resolved an error that would occur when viewing a relevant document that is not stored in the database and the user is not an administrator.
Resolved a problem that would occur when exporting lists and reports to Excel that would cause the type of each field to not be identified, resulting in their incorrect formatting.
Resolved an error in the process of translating menu options from the process of “Menu configuration” (Configuration & Tools \ Development & customization tools), during which the Greek captions would not properly update.

Documents

Resolved a problem that would occur during the calculation of the VAT value in item-BOM, when the document type was selected in the field "Calculate VAT on totals".
Fixed an erroneous check that would prevent the creation of a document in cases where it included foreign currency and a discount would be applied on the entire document.
Fixed a problem that would prevent the conversion of documents linked to exchange differences documents, while a profile of access rights existed that would allow this.
Fixed a problem that would occur when printing via scheduling, where pdf files would look unprinted and would not be created. Additionally, it is now possible to perform "Cancel PDF printing" on a client or server by choice, via the main menu. In cases where multiple documents queue for printing and this causes a possible delay, new parameter {ESERPSERVER_USER_PRINTERS_CONFIG} was created, where the option of waiting time in seconds has been added for the completion of the previous printing. This is the maximum time that the system will wait for the previous printing to complete (if found in pending) before the next printing is sent to the printer.

Processes

Resolved errors when closing a B phase fiscal year, when the item would track color & size with an alternative measurement unit (AMU) as a service unit.

POS

Resolved a problem that would occur when collecting an open balance with card, where after calling the option “Transaction approval via POS”, a blank window would appear and the document would not save.

Automation – Business Rules

Fixed an error while running automation Update shipping indicator.

Price lists - Commercial promotions - Promotions

In entity form “Discounts and Promotions” (Configuration/Invoicing policy), where there is a list with the promotion items based on the Items list set, if items are removed from the list outside of the promotion and then the list is updated through the promotion, these items would still be there. A correction was implemented in this release for their removal.
In the application form of a Promotion that would opens through a document, the indication Evaluation of the condition of the promotion would not properly update based on the progress of the promotion implementation. In particular, the value would be “Not required” while it was Successful. This has been corrected.
Fixed an error message that would display when right-clicking on the detail Promotion items through the Promotion form.

Miscellaneous

In the "History log" scroller, in the "Data Interchange" menu option, the column with the consumption result was corrected.
An improvement was added so that, when exporting Register-type Bits into Excel, the trade account's name is also exported in addition to the code. This change was made to context bits of Customers and Debtors.
Resolved an error that would occur in the search in the Category in Addresses of persons, when it has multiple thousand entries (the Category to be used in addresses is defined in a relevant company parameter).
Fixed valuation error of "Cannot insert duplicate key in object 'dbo.ESFIDocumentAdjustment’. The duplicate key value is (ΧΧΧ)”. The valuation process would try to give the same GID in 2 documents under a specific condition.
Resolved a problem in the Field property profile, where the check action would not immediately trigger. This would cause confusion as was different to the way the application worked before.
Fixed an error that would occur when transferring a customer to another company through the Copy to other companies action.

Related cases:

PS-110198, PS-109968, PS-110003, PS-109936, PS-110059, PS-110196, PS-109907, ΥΠΘ_SUP-206353, ΥΠΘ_SUP-205307, ΥΠΘ_SUP-205317, ΥΠΘ_SUP-207560, PS-108815, ΥΠΘ_SUP-205762, PS-109819, PS-109924, ΥΠΘ_SUP-205580, PS-110110, ΥΠΘ_SUP-196177, PS-105298, PS-106232, PS-109028, PS-109185, PS-109443, PS-102106, ΥΠΘ_SUP-201063, PS-95158, PS-108808, PS-109552, PS-109632, PS-109806, PS-107689, PS-109822, PS-107884, PS-109276, PS-110610, PS-108030, PS-100617.

Bug fixes specific to the Romanian version

e-Factura Outbound

Changed the Person Type parameter in the list of invoices to be sent in SPV so it will bring, by default, all Person Types.
An additional condition has been added to the automation of sending invoices in SPV so that, until the final status is updated to Error or Success, no further attempts are made to resend them.
The requirement that the invoice must contain at least one item flagged for e-Factura has been removed.

e-Factura Inbound

The list of invoices received from the SPV shows with a negative sign the amount for type 384 documents. A column indicating the type of invoice has also been added to the report.
The document creation automation has been modified so that the document date is given by the supplier instead of the upload date in SPV.

Intrastat codes update

The Intrastat code update functionality has been completed with an additional condition that applies the mechanism only to codes that belong to the same country as the product variant used. For example, if you run the procedure on the EBS-RO application, the update will be done only for the codes that have in the ISO country code field the value RO.

Other fixes

Sales journal - Sales in Third party Countries case (tabel5 = 3 or 4).

Related cases:

1087502, 1098741, 1098465, 1098940, 1097239, 1090881, 1098924, 1098923, 1099185, 1098873, 1097717, 1097589.

Kind request: If you notice errors, inappropriate wording or lack of necessary information in this material, please do not hesitate and send an email to support.ebs@bitsoftware.ro with the subject "Documentation" and content that includes the link to this material accompanied by your observations . Thank you!

Page updated

Report abuse