ATCUD para Portugal: Prepare-se para o novo requisito legal da Portaria 195/2020

[AilaneKuhn]

(Scroll down for the English version)

Olá,

 

Como já deve saber, o governo português publicou a Portaria 195/2020 e, juntamente com o código QR, introduziu o Código de Documento Único (ATCUD) como um novo requisito legal.
Com o Despacho 351/2021.XXII publicado dia 11 de novembro de 2021, ATCUD será opcional em 2022 e obrigatório a partir de janeiro de 2023.

As empresas precisam obter um novo código de validação de série e usá-lo para gerar o ATCUD, sendo este um código único atribuído a documentos fiscais relevantes, como faturas e notas de crédito.

O ATCUD é reportado no ficheiro (SAF-T) e incluido no código QR. Ele deverá também ser incluido nos documentos impressos e eletrônicos.

Para mais informações sobre a solução de código QR, veja o blog post Código QR e ATCUD para Portugal: Fique por dentro das últimas atualizações da Portaria 195/2020.

 

A solução SAP

Um framework centralizado para gerir as séries e os códigos de validação AT por módulo será disponibilizado, suportando a comunicação manual e eletrônica.

Essa solução está planejada para estar disponível em duas fases:

• Fase 1: Âmbito reduzido (serviços web não incluídos). Está planejado para ser disponibilizado em meados de novembro de 2021.


• Fase 2: Funcionalidade relacionada aos serviços web. Está prevista para ser disponibilizada em meados de dezembro de 2021.

 

Os pré-requisitos

Existem algumas atividades de preparação que podem ajudar a acelerar as etapas de implementação assim que a solução estiver disponível:

Implementação de SAP Notes

Certifique-se de que implementou as SAP Notes relacionadas ao Despacho 8632/2014:

• 
  
  
  
  • SAP ERP: 2268552
  
  
  • SAP S/4HANA: 2375055
  
  
  
  

Comunicação com as autoridades fiscais

Pode utilizar os serviços da Web para comunicar automaticamente com as autoridades fiscais. Para esta comunicação, é necessário integrar o seu sistema com SAP Cloud Integration.

Para mais informações, consulte a SAP Note 2903776 ou entre em contato com seu gestor de conta SAP.

Atividades de configuração

Certifique-se de atualizar as configurações necessárias:

• 
  
  
  
  • Crie novos intervalos de numeração e defina as respectivas séries únicas para assinatura digital. A nova nomenclatura deve seguir os requisitos legais (não são permitidos caracteres especiais). Para mais informações sobre as atividades de customizing, veja Customizing for Digital Signature of Invoices. Aguarde também as novas instruções que serão publicadas em breve.
  
  
  • Atribua os novos intervalos de numeração aos respectivos tipos de documento SAF-T.
  
  
  • Adapte os seus layouts de impressão para incluir o ATCUD nos formulários.
  
  
  
  

Poderá utilizar os intervalos de numeração e séries atuais enquanto prepara os novos intervalos de numeração. Após 1 de janeiro de 2022, deverá utilizar os novos intervalos de numeração.

 

SAP Notes lançadas e atualizadas em 2022

Agora você já pode consultar a nota coletiva 3154599 que lhe dará toda a informação relevante para a implementação da solução, inclusive nos diversos módulos (SD, FI, FI-CA, Settlement Management, etc.). Veja também a documentação incluída. Esta nota será atualizada sempre que for liberada a solução de um novo módulo.

 

Guia de solução de problemas e perguntas frequentes

Consulte o SAP Knowledge Base Article 3274103 para um guia de solução de problemas e respostas a perguntas frequentes para ajudar você no processo de implementação da solução.

 

Fique atento às notícias mais recentes

Fique atento! Pretendemos atualizar este blog regularmente.

Também pode verificar mais informações no grupo SAP Jam SAP Portugal Collaboration Forum. Se ainda não for membro deste grupo, envie sua solicitação de convite para o seguinte e-mail: marta.pereira@sap.com.

Fique à vontade para deixar seus comentários abaixo se tiver alguma dúvida ou sugestões para uma publicação futura. E não se esqueça de seguir a tag do SAP S/4HANA aqui na SAP Community para ficar atento às notícias mais recentes.

Até à próxima,

Ailane Kuhn

#SAPGoGlobal #SAPLocalization

 

 

***

 

 

ATCUD for Portugal: Get ready for the new legal requirement on Portaria 195/2020

 

Hi everyone,

As you might be aware, the Portuguese government published Portaria 195/2020 and, together with the QR code, introduced AT-Validation Code (ATCUD) as a new legal requirement.
With Despacho 351/2021.XXII published on November 11, 2021, ATCUD will be optional in 2022 and mandatory as of January 2023.

Companies need to obtain a validation code for their series and then use it to generate the ATCUD, which is a unique document code assigned to relevant documents, such as invoices and credit memos.

You must include the ATCUD on printed documents and in electronic invoices and also report the ATCUD via the Standard Audit File for Tax Purposes (SAF-T). It must also be included in the QR code.

For more information about the QR code solution, see QR Code and ATCUD for Portugal: Stay Tuned to the Latest Updates on Portaria 195/2020.

 

The SAP solution

A centralized framework to manage the Series and AT-Validation Codes across modules will be provided, supporting both the manual and the automatic communication.

This solution is planned to be available in two phases:

• Phase 1: Reduced scope (web services not included), planned to be available not earlier than mid November 2021.


• Phase 2: Web service-related functionality, planned to be available not earlier than mid December 2021.

 

The prerequisites

There are some preparation activities that could help you to speed up the implementation steps once the solution is available:

SAP Notes implementation

Make sure you have the SAP Notes related to Despacho 8632/2014 implemented:

• 
  
  
  
  • SAP ERP: 2268552
  
  
  • SAP S/4HANA: 2375055
  
  
  
  

Communication with the tax authorities

You can use webservices to communicate with the tax authorities automatically. For this communication, you need to integrate your system with SAP Cloud Integration.

For more information, see SAP Note 2903776 or contact your account executive.

Configuration activities

Make sure you maintain the required configuration settings:

• 
  
  
  
  • Create new number ranges and define their unique series for Digital Signature. The new nomenclature should follow the legal requirements (special characters aren’t allowed). For more information about the Customizing activities, see Customizing for Digital Signature of Invoices. Further instructions will be published soon.
  
  
  • Assign the new number ranges to the respective SAF-T document types.
  
  
  • Adapt your print layouts to include the ATCUD in the forms.
  
  
  
  

Note that you can use the current number ranges and series while defining the new number ranges. After January 1, 2022, you must use the new number ranges.

 

New and Updated SAP Notes Released in 2022

The Collective Note 3154599 has been released with all the information you need to know about the solution implementation for ATCUD in different modules. You can also check the product documentation for more information.
This SAP Note will be updated every time there's a new solution release for the different modules. Stay tuned!

 

Troubleshooting Guide and FAQ

Check the SAP Knowledge Base Article 3274103 for a troubleshooting guide and answers to frequently asked questions to help you in the implementation process.

 

Stay tuned to the latest news

Stay tuned! We plan to update this blog post regularly.

You can also check out the SAP Jam group Portugal SAP Collaboration Forum. If you are not a member of this SAP Jam group yet, please send your invitation request to the following email: marta.pereira@sap.com           .

Feel free to leave your comments below if you have any questions or suggestions for an upcoming post. And don’t forget to follow the SAP S/4HANA tag here on SAP Community to stay tuned to the latest news.

 

See you next time,

Ailane Kuhn

#SAPGoGlobal #SAPLocalization

[former_member713824]

Hi Thomas

Unfortunately we cannot downport the solution for lower releases, and because of that since last year we requested customers to do the upgrade before 01.01.2023

I strongly advice you to perform the upgrade ASAP. Until then you need to check with your consultants the best approach to be legal compliance with the Requirement.

Regards,

Marta

[former_member234717]

Hello Marta,

The SD number range that is assigned for billing type ZF4 is common for all countries, so we can't change the billing number range code in the basic SD configuraton.

That's why it's important to know how we can derive the new number range and serie nummer in this table SIPT_NUMBR_SD_V without changing the default number range code at billing type level in the basic SD configuration.

Please advise.

Thanks.

Best regards,

JPB

[former_member613011]

Hi Martha,

would you please be so kind to reply to our question ?

the solution supplied is not  covering those standard scenarios

[former_member825370]

Hello Marta,



My question is whether SAP has requested or will soon have a SELO DE VALIDAÇAO AT (SVAT) for the SAF-T de Contabilidade,

since today it does not have one.



Regards,

Juan Carlos

[former_member817342]

Hi Martha,

would you please be so kind to reply to our question ?

 

Thank you in advance and best regards

Barbara

[former_member613011]

HI ,

we got the answer / solution from SAP opening an SAP ticket .

If we change the country of the Sales Organization  to Portugal "PT"  then we could add the  Sales org in SIPT_CCODE_SD_VC and after that the Digital signature is done for the billing documents for those foregin c.codes  without having neither plants abroad activated nor a portuguese plant for the involved foreign c.code

regards

 

[former_member613011]

HI Marta ,

could you please clarify if in those cases of Foreign C.codes , the field  "A:NIF do
emitente"  in the QR code  should be the VAt reg number of the c.code in PT  table t001n-stceg for country PT or the  VAT reg number from the C.code table t001-stceg ?

I'm asking because cheking the  GET_QRCODE  functon supplied by SAP for Foreig C.codes is returning the field A: populated with the VAT reg number from t001-stceg  .

Beside of this , we realize that the fields "A:  NIF do emitente" and "B: NIF do adquirente"  are popuated including the country prefix , while inthe technical decrption is described :

"Preencher com o NIF do emitente sem espaços e sem prefixo do País"

Is this a bug in the fucntion or are we missing simething ?

thanks for your help

[former_member774751]

Hello Marta:

As you suggested, we have reported this question in e-balcao of AT and in their answer they have referred only to the communication via web service. They say nothing about the actual or future existence of a TEST portal.

In their answer they only refer to the web service communication detailed in the “Manual de Integraçao de SW - Aspectos Especificos” available in the following link:

https://info.portaldasfinancas.gov.pt/pt/apoio_contribuinte/Faturacao/Comunicacao_Series_ATCUD/Pagin...

According to this document (point 2), there are four different web service methods:

2. Registar Séries (Point 2.1) à Ok


3. Anular comunicaçao de series (Point 2.2) àOK


4. Finalizar series (Point 2.3) àOK


5. Consultar Series (Point 2.4) à ¿?

Is it available in SAP the functionality to implement the operation for “Consultar series”? When you run the Manage Series Validation code for Portugal (transaction code GLO_PT_SVC) , in this moment you are able to:

1. Register serie via web service.


2. Cancel series via web service.


3. Finish series via web service.

But there is no way/option to consult serie (point 2.4) , so I have two questions related to this issue:

• Is it available in SAP the functionality to consult a serie? We think it´s not available.


• If it´s available, how can we execute this operation for the serie?

We have implemented the whole existing notes so far for this issue but we are not able to see the consulting option.

The consulting option could be unnecessary if everything works fine and there is no problem with the series´ registration. Nevertheless, it´s necessary if you face problems with the series communication and this is just our situation now:

We sent three FI series via web service registration but there was some problem in the process (we don´t know exactly what was the problem) because now we have those series with initial status (I) and we didn´t receive the validation code.

Afterwards, when I select a single row with one of these series in initial status (I) I receive the following error message:

“Registration not possible. Series XXXX of doc type FT/NC/ND is already registered”

So, actually, we have the following situation:

1. We can´t use the serie because we don´t have the validation code (initial status)


2. There is not a TEST portal to check the series’ information and the validation code.


3. The consulting option via web service is not available in SAP or we don´t know how to manage this situation.

What´s the solution for this issue?

 

Thank you in advance.

 

Best Regards,

[Private_Member_742483]

Hello Marta,

 

My question is about Self-Billing(ATCUD). SAP has not released any development for collector series related to self-billing? We run "Manage Series Validation Code"=S transaction and I don't see any collector.

When we check the BADI_GLO_PT_SERIES_COLLECTOR only we see to SD, FI and delivery.

Thanks for your help.

 

Sandra Santos

[former_member826395]

Hi Marta,

I have same question. if there are two number ranges for same document type but with different series, how SAP will only pick new one ? To be noted that :Start date: is already greyed out and can not be entered.

 

thank you

jignesh

[former_member613011]

Deliveries Ranges doesnt appears in GLO_PT_SVC

HI

I've set up new number ranges for Outbound deliveries in SIPT_NUMBR_OBD_V following  the series naming convention starting by "D" and four digits . Also assinged the SAFT document type for each one , but when i go to GLO_PT_SVC ,selecting deliveries , i got the messages "No series identifier found for the given filter criteria"

Does anybody knwo where the issue could be ?

thanks in advance for your help

[Private_Member_742483]

Hello Leston,

Check in debug this enhancement: BADI_GLO_PT_SERIES_CLTR_MOG maybe you will found the issue.

Best Regards,

Sandra Santos

[lpisco]

Durante os testes verificámos também que, após configuração dos novos number ranges e series, ao reimprimir um documento que tem uma série anterior à nova configuração, não é gerado QR Code – que é atualmente obrigatório.

A seleção de dados para o QR Code parte das tabelas de configuração SIPT_NUMBR* para obter os detalhes da assinatura digital nas tabelas SIPT_* (SIPT_LIKP por ex.).

Teoricamente estaríamos em incumprimento numa situação dessas, já tinham detetado esta situação?

[former_member613011]

Hi Sandra ,

thanks a lot for your feedback . UNfortunalty we have found that such enhacement doesn't exist in our system. We are gonna check OSS notes which could be missing in our system

 

[former_member613011]

we have the follwing note still not implemented and seems its' related to such enhachement but i'm not really sure . could anybody confirm it ? We didn0t imeplemented so far because it's linked to the

GST india implementation and has a lot to prerequisites relatred to such india sutff that we are trying to avaoid to  implement as we have not any bussines in india

3140877

Portugal ATCUD Legal Change: Code Changes for SD Deliveries

[former_member713824]

Hi Leston

There are several notes for localization of deliveries that are a pre-requisite for ATCUD deliveries.

All the pre-requisites are exclusive for Portugal and not related with any law in India.

Regards,

Marta

[former_member549608]

Hi Marta,

 

We also have this issue.

The table is already maintained for the document type.

In the last session, it was not clear that we had to delete the actual entry in order to maintain the new one.

Can you please clarify?

 

Thank you.

Regards,

Patricia

[former_member713824]

Hi Patricia

I strongly recommend you to follow the steps from the help.

There you have the explanation about what you need to do regarding the deliveries.

But yes, you need to delete the old entries and substitute them by the new ones

Regards,

Marta

[amitash]

Hello @Marta Pereira,

for Automatic Web Integration, is it mandatory to have CPI Cloud Interation or can this be done via other adapters like e.g. Biztalk? Can you please answer?

 

Thanks

Warm Regards

Amitash

[former_member713824]

Hi Amitash

I am not a technical person, but I believe that is only with SAP CPI.

But you can always open one incident asking about that to get one correct answer from the responsible colleagues from the solution.

Component XX-CSC-PT-LO

Regards,

Marta

[amitash]

Hello Marta,

 

Thanks for the quick reply :). I will check that.

Warm Regards

Amitash

[shubham1988]

Hi Marta,

Can you please let me know even if we are going for manual update then still do we need below SAP Notes to be implemented?

3137271 Portugal ATCUD Legal Change: Web Service Proxy objects

3137385 Portugal ATCUD Legal Change: Web Service Utilities Objects

Regards,

Shubham

[former_member713824]

Hi Shubham

In that case those 2 notes are not necessary

Regards,

Marta

[frank_r]

Dear Marta,

I write you regarding SD Billing, we want to inform a Series Validation Code (SVC) in GLO_PT_SVC report to do test, but we are finding some troubles. At the moment, we have just implemented SAP NOTES for ATCUD requirement in development environment.

We have two client (100 and 200), in client 100 the table "SIPT_NUMST_SD" doesn't contain any register, and we can access to GLO_PT_SVC report without any problem. However, in client 200, in the same table(SIPT_NUMST_SD), there are records, and we cannot access to the report SAP send out a pop-up "No series identifier found for the given filter criteria".

I have been looking for how I can update this table, but I haven't found any clue. Also, there is a note 3143345 - Digital Signature Portugal: ATCUD SD and FI - Prerequisite Objects DDIC Post which speaks about SIPT_NUMST_SD_V1, but "Where-used list" fucntion doesn't return any information about it.

Do you know if this table (SIPT_NUMST_SD) is mandatory to have records in this table, or it is obsolete ? Do you know if SAP has to release more notes for SD Invoice or for GLO_PT_SVC report?

I hope I have explained myself.

Thanks a lot!

[former_member713824]

Hi Francisco

The table SIPT_NUMST_SD_V is now called SIPT_NUMST_SD_V1, and nothing changed in this table

Table SIPT_NUMST_SD is not maintained by customers, is automatically populated by the system.

An additional table was added and is SIPT_NUMST_SD_V2

Maybe you need to check if you already implemented all the notes for SD ATCUD.

Regards,

Marta

[former_member724869]

Hi Marta,

We have implemented all the relevant notes for ATCUD for SD and FI documents.

As I understand, the ATCUD number will be generated not at the time of posting the document but at the time of either Print OR running the SAF-T report.

We are not using Adobe form, so, will ATCUD get generated ONLY after we run the SAF-T report?

 

Could you help clarify?

 

 

Thanks,

Jay

[former_member613011]

Hi Francisco

check you have properly mantained SIPTV_DT_SCOPE & SIPT_NUMBR_SD_V2 . If  i remember well i had same issue and once i completed those tables then i got the Billing number ranges visible in GLO_PT_SVC

hope it helps

[former_member613011]

Hi ,

fyi , finally we have a solution from SAP for implementing the pending OSS notes / prerequisutes wihtout having to implement the Indian stuff .New notes were released 

3265326 - Data Dictionary Prerequisites for ODN functionality for countries other than India

3265376 - Corrections to ODN Function module OFF_NUMBER_GLOBAL_NUMBERING parameters for countries other than India

hope it helps to anybody else

[former_member613011]

Now , after implementing those notes above and being able to follow witht he next oss notes for Deliveryes  , Deliveries Ranges appears in GLO_PT_SVC

tregards

[silviaferreira]

Boa tarde Marta,

Como já reportado por outros utilizadores, verificámos que ao efetuamos os passos descritos para a criação de novas series para as Deliveries e pelo facto de eliminarmos os number ranges anteriormente em uso na tabela SIPT_NUMBR_OBD, não estamos a conseguir gerar o QR code nas reimpressões de documentos gerados anteriormente, pois deixa de ser possível a determinação da tag DOC_TYPE (CL_QRCODE_PT_OBD_UTILL -> GET_NUMBER_RANGE e GET_ATCUD).

O campo delivery_type apenas foi adicionado na tabela sipt_numst_obd com as notas do ATCUD e o number range em uso já se encontrava registado na referida tabela. Existe alguma forma de recuperar a informação para os campos adicionados na tabela para os Number Ranges já existentes na mesma?

Conseguem esclarecer se a SAP vai corrigir estas situações nos mapeamentos do QR Code?

Obrigada

Silvia Ferreira

[former_member817342]

Hi Marta

Is there any SAP note for ATCUD implementation in INVOIC IDOC?

 

Best regards

Barbara

[nucleosap_refer]

Olá Marta

Temos o ECC6 e estamos a implementar o ATCUD e após termos implementado os SP e as notas mencionadas na nota coletiva 3154599 temos a seguinte dúvida:

A SAP vai atualizar este método CL_SIPT_PR_UTIL-GET_ATCUD para o colocar a obter o ATCUD? é que no código continua a determinar o ATCUD a ZERO.

 

Conseguimos perceber que para as guias de remessa/transporte o método CL_QRCODE_PT_OBD_UTILL-GET_ATCUD já tem o código definido

[nucleosap_refer]

Acrescento ainda que a tabela SIPT_NUMBR_SD_V2 não tem o botão de criar novas entradas. Não conseguimos prosseguir com a parametrização do ATCUD.

Podes ajudar?

Obrigada

[former_member713824]

Hi Jignesh

Is not possible to have 2 NR for the same SAP document type with different series. This is a limitation from SAP.

Best Regars,

Marta Pereira

[lpisco]

As entradas são adicionadas automaticamente assim que configuradas na SIPT_NUMBR_SD_V com a nomenclatura definida.

[mipalacios]

Hi Marta

We have implemented all the relevant notes for ATCUD for SD and FI documents but we have a dump when access to view SIPT_NUMBR_SD_V2.

Our system is SAP_APPL: 600

SAP_APPL

600

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM', was

not caught in

procedure "JUSTIFY_ACTION_MODE" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The program "SAPLSIPTCUST2" is meant to execute an external PERFORM,

namely the routine "INITILIASE_SERIES_CLASS_SD " of the program "SAPLSIPTCUST2

", but

this routine does not exist.

This may be due to any of the following reasons:

1. One of the programs "SAPLSIPTCUST2" or "SAPLSIPTCUST2 " is currently being

developed.

The name "INITILIASE_SERIES_CLASS_SD " of the called routine may be incorrect,

or

the routine "INITILIASE_SERIES_CLASS_SD " is not yet implemented in the program

"SAPLSIPTCUST2 ".

-

2. If the program SAPMSSY1 is involved in the runtime error, one of

the function modules called via RFC is not flagged as remote-capable.

(see Transaction SE37  Goto -> Administration -> RFC flag)

3. There is an inconsistency in the system. The versions of the

programs "SAPLSIPTCUST2" and "SAPLSIPTCUST2 " do not match.

 

Also, when we acces to GLO_PT_SVC, we don´t see any option in the series business Process.

Thank you.

[amitash]

Hello maria_pereira20 ,

We are sending the Invoices to the customer via EDI. Is the ATCUD code also needs to be adapted in the EDI? Is there and SAP note for ATCUD implementation in IDOC?

Can you please provide the information?

Thanks

Warm Regards

Amitash

[catia1_ribeiro]

Hello Marta Pereira,

Can you please share any specific date regarding to the release of the OSS Notes linked with the MM self-Billing solution for ATCUD?

Thank you!
Regards,
Cátia Ribeiro

[amitash]

Hello All,

 

can anyone help with this?

 

Thanks

Warm Regards

Amitash

[former_member713824]

Hi Amitash

For the IDOC SAP did not deliver any solution. You need to include it by yourself in the IDOC.

Regards

Marta

[former_member812679]

Ola Marta, boa tarde,

É possivel usar a mesma serie em 2 ambientes diferentes: QAS e PRD.

A nosso objectivo é fazer as configurações relativas ao ATCUD em DEV e transportar depois para QAS e PRD.

È possivel?

Obrigado

JB

[former_member817342]

Dear Marta,

Do we have any news about ATCUD for customer selfbilling documents?

 

Thank you and best regards

Barbara

[paco_alvarez]

Hi,

this was resolved by implanting the note

3163798 - Digital Signature Portugal: ATCUD SD and FI - Maintenance Views .

 

Thanks,

Regards.

[paco_alvarez]

Hi,

You should implement the notes that apply from the following collective note 1981139 - SAF-T (PT): Collective note for RPFIEU_SAFT for Portugal.

ATCUD SAFT

 

Regards.

[former_member713824]

Olá João

 

Sim é possivel. O código de validação depois é que será distinto. Além disso os sistemas também eles são diferentes, em que apenas um é produtivo e oficial.

Tudo o que sair em termos de impressão do sistema QAS deve ser devidamente identificado como sistema de testes ou de formação.

 

Cumprs,

Marta

[former_member713824]

Hi Barbara

Solution will be released on november 28. Please check the notes on that day.

Regards,

Marta

[former_member713824]

Hi Barbara

SAP will not deliver any specific solution for IDOC ATCUD.

This needs to be adjusted in your project.

Regards,

Marta

[former_member713824]

Olá Silvia

Estamos a analisar esta questão.

Cumprs,

Marta

[former_member713824]

Hi Jay

Our solution is dynamic, this means that we will not keep ATCUD code in any table.

In the moment of the printing of the document, in the moment of QR Code generation or in the moment of SAF-T creation, the ATCUD will be dynamic generated.

This means that for our deliverable layouts (with ATCUD and QR Code) and for SAF-T SAP will concatenate the validation code kept in the Series cockpit with the internal document number of the document and will write that in document layout or SAF-T.

In you case because you are not using our layouts you should adjust your own layouts to have this dynamic behavior and in the moment of the printing to concatenate the validation code with the internal document number.

For SAF-T you don´t need to do anything.

Regards,

Marta

[former_member817342]

Thank you Marta. We will be monitoring it.

 

Best regards

Barbara