Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #48163 All Revisions ] Back to Issue ]
Summary 0048163: Product name SAF-T validation update request
Revision 2021-11-26 14:20 by ucarrion
Description Up to now, the SAF-T module does not allow any user to update the name of any product already sold into a store set as “Portuguese Configuration”=true. This requirement is based on changing this behaviour.

Specifically, the scenario to cover is the one below: the same product that is sold in several countries is sold first in Portugal and for any reason its name needs to be updated. Currently, this will not be allowed due to the current validation, even if the change is done for a need in another country.

From this point on, the validation should be done on the Portuguese translation record of Product>Translation tab (M_Product_Trl). The objective of the change request is avoiding the impact of the validation to other countries where the Portuguese Configuration, and therefore the SAF-T modules, is not applying.

Obviously, from a business point of view, it is important to remark that this change will not be a removal of the existing validation but an update.

In addition it is important to raise that the new rule will be always configurable, so can be adaptable in each case.

Development rule:
--A new flag “Use translation product name” will be added in the ‘Organization’ window, ‘Portuguese Configuration’ section. The new flag will indicate where the validation is done.
--In case the flag mentioned above is marked for a selected SAF-T informer organization, the value informed as product name in the SAF-T/e-Fatura file will be the Portuguese translation one. If not existing, will inform the header product name.


This could trigger the following scenarios:
-Use translation product name=false
--In this case, the validation won’t be modified. It will be based on the header name of the products even if a portuguese translation exists.

-Use translation product name=true
--For the products where a Portuguese translation exists, the validation will apply on the translation name.
--For the products where a Portuguese translation does not exists, the validation will remain based on the header name of the products.

As per the scenarios described above, there is a need to warn the users about a missing PT translation in case the new flag “Use translation product name” is enabled:
In such case, if a product with no PT translation is called into a Portuguese POS (this means, the related store has Portuguese Configuration=true) a warning popup message should be raised.
Regarding an eCommerce scenario, if a product with no PT translation is involved in an order requested to be integrated in Openbravo, a warning message should be raised.
Revision 2021-11-25 16:10 by ucarrion
Description Up to now, the SAF-T module does not allow any user to update the name of any product already sold into a store set as “Portuguese Configuration”=true. This requirement is based on changing this behaviour.

Specifically, the scenario to cover is the one below: the same product that is sold in several countries is sold first in Portugal and for any reason its name needs to be updated. Currently, this will not be allowed due to the current validation, even if the change is done for a need in another country.

From this point on, the validation should be done on the Portuguese translation record of Product>Translation tab (M_Product_Trl). The objective of the change request is avoiding the impact of the validation to other countries where the Portuguese Configuration, and therefore the SAF-T modules, is not applying.

Obviously, from a business point of view, it is important to remark that this change will not be a removal of the existing validation but an update.

In addition it is important to raise that the new rule will be always configurable, so can be adaptable in each case.

Development rule:
--A new flag “Use translation product name” will be added in the ‘Organization’ window, ‘Portuguese Configuration’ section. The new flag will indicate where the validation is done.

This could trigger the following scenarios:
-Use translation product name=false
--In this case, the validation won’t be modified. It will be based on the header name of the products even if a portuguese translation exists.

-Use translation product name=true
--For the products where a Portuguese translation exists, the validation will apply on the translation name.
--For the products where a Portuguese translation does not exists, the validation will remain based on the header name of the products.

As per the scenarios described above, there is a need to warn the users about a missing PT translation in case the new flag “Use translation product name” is enabled:
In such case, if a product with no PT translation is called into a Portuguese POS (this means, the related store has Portuguese Configuration=true) a warning popup message should be raised.
Regarding an eCommerce scenario, if a product with no PT translation is involved in an order requested to be integrated in Openbravo, a warning message should be raised.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker