segunda-feira, 7 de outubro de 2019

TDF SP14 – What’s New

Olá pessoal,

Hoje o Support Package 14 do TDF foi liberado trazendo melhorias para os tópicos a seguir:

Messaging Framework
EFD ICMS IPI
EFD Contribuições
Atualizações a partir do Customer Influence
Atualizações dos guias do TDF

Para verificar os pré-requisitos e recomendações para o SP14, veja a Release Information Note https://launchpad.support.sap.com/#/notes/2791877.

Seguem abaixo mais detalhes sobre as principais modificações.

Messaging Framework

A solução agora suporta as Notas Técnicas 11, 12, 13 e 14 do eSocial.

Adicionalmente, a partir de agora você poderá ver detalhes dos logs referentes aos eventos do Messaging Framework processados a partir da nova aba Log Monitor no Cockpit do Messaging Framework (conforme imagem a seguir).

Para mais informações sobre a solução, veja https://help.sap.com/viewer/product/SAP_TAX_DECLARATION_FRAMEWORK_FOR_BRAZIL/1.0.14/pt-BR -> Ajuda da aplicação -> Messaging Framework -> Cockpit do Messaging Framework > Monitor de log do Messaging Framework.

EFD ICMS IPI

O relatório EFD ICMS IPI está atualizado com o leiaute 14. A partir dessa entrega, novas tabelas Shadow foram disponibilizadas para preenchimento das informações requeridas. Veja o blog post a seguir para mais detalhes sobre essa atualização: TDF: Novidades do leiaute 14 do relatório EFD ICMS IPI.

Para mais informações sobre a solução, veja https://help.sap.com/viewer/product/SAP_TAX_DECLARATION_FRAMEWORK_FOR_BRAZIL/1.0.14/pt-BR -> Ajuda da aplicação -> Relatórios -> EFD ICMS IPI – Informações de Background.

EFD Contribuições

O relatório EFD Contribuições agora suporta a versão 1.31. do Guia Prático do relatório EFD Contribuições.

Atualizações a partir do Customer Influence

A partir dessa entrega, as soluções para os tópicos abaixo que foram sugeridos via Customer Influence estão disponíveis:

Atualizações dos guias do TDF

Algumas modificações foram feitas nos guias do TDF (todos disponíveis em Inglês). Confiram:

- Guia de configuração:

Acesse o guia de configuração para buscar ajuda sobre como configurar o TDF. A seção Configure SOAMANAGER for Government Communication foi alterada listando os webservices que possibilitam a comunicação dos eventos do Messaging Framework com o governo.

- Guia de instalação:

Acesse o guia de instalação para ter acesso ao passo a passo de como instalar/atualizar o seu sistema com o SP14 de acordo com o seu cenário de instalação.

Não deixe de conferir também os demais guias do TDF:

- Guia do administrador
- Guia do desenvolvedor

Vale lembrar que o IMG, o menu e a tradução só são atualizados via Support Package. Por essa razão, recomendamos fortemente a instalação do SP14.

Gostaríamos muito de saber o seu feedback. Deixe seu comentário abaixo caso tenha alguma dúvida ou sugestão para um próximo post. E não esqueça de seguir a tag SAP Tax Declaration Framework for Brazil aqui na SAP Community para ficar ligado nas últimas notícias sobre o Tax Declaration Framework (TDF).

Até a próxima!

Ailane Kuhn

Time de desenvolvimento do TDF

***

Hi everyone,

The Support Package 14 of TDF has been released bringing improvements to the following topics:

Messaging Framework
EFD ICMS IPI
EFD Contribuições
Updates based on Customer Influence
Updates on TDF guides

To check the prerequisites and recommendations for SP14, check the Release Information Note https://launchpad.support.sap.com/#/notes/2791877.

Find below more details about the main changes.

Messaging Framework

The solution now supports Technical Notes 11, 12, 13 and 14 of the eSocial.

Additionally, from now on you can see details of the logs related to the Messaging Framework events processed from the new Log Monitor tab page in the Messaging Framework Cockpit (as per image below).

For more information about the solution, see https://help.sap.com/viewer/product/SAP_TAX_DECLARATION_FRAMEWORK_FOR_BRAZIL/1.0.14/pt-BR -> Application Help -> Messaging Framework -> Messaging Framework Cockpit > Messaging Framework Log Monitor.

EFD ICMS IPI

The EFD ICMS IPI report is updated with the layout 14. As of this release, new shadow tables are available to fill in the required information. See the following blog post for more details about this update: TDF: New layout of layout 14 of the EFD ICMS IPI report.

For more information about the solution, see https://help.sap.com/viewer/product/SAP_TAX_DECLARATION_FRAMEWORK_FOR_BRAZIL/1.0.14/pt-BR -> Application Help -> Reports -> EFD ICMS IPI – Background Information.

EFD Contribuições

The EFD Contribuições report now supports the 1.31 version of the EFD Contribuições Guia Prático.

Updates based on Customer Influence

As of this release, the solutions for the topics below that have been suggested via Customer Influence are available:

Updates on TDF guides

Some changes were made to the TDF guides (all available in English), as follows:

- Configuration Guide:

Go to the configuration guide to find help on how to configure TDF. The Configure SOAMANAGER for Government Communication section has been changed by listing the webservices that enable the communication of Messaging Framework events with the government.

- Installation Guide:

Go to the installation guide to find the step by step in how to install/update your system with SP14 according to your installation scenario.

Don’t forget to have a look at the other TDF guides too:

- - Admin Guide
  - Developer Guide

Keep in mind that the IMG, menu, and translation is only maintained via Support Package. For this reason, we recommend you to install SP14.

Feel free to leave your feedback, comment or question in the space provided below. And don’t forget to follow the SAP Tax Declaration Framework for Brazil tag to stay tuned on Tax Declaration Framework latest news.

Regards,

Ailane Kuhn

Source: https://blogs.sap.com/2019/09/30/tdf-sp14-whats-new/

Reporte de Medios Magnéticos de Colombia en SAP S/4HANA: Razones porque implementar la solución en su sistema

Hoy le traemos razones porque reportar los medios magnéticos al gobierno de Colombia puede ser mucho más fácil con SAP. Conozca la solución de Reportes de Medios Magnéticos en SAP S/4HANA utilizando el marco de ACR (Advanced Compliance Reporting).

En el video abajo, le enseñamos el alcance, la arquitectura, y los pasos para empezar a implementar la solución en su compañía.

La solución de Reporte de Medios Magnéticos es desarrollada en el marco de Advanced Compliance Reporting, una robusta herramienta que extrae datos de la base de datos HANA. Al utilizarla, además de automatizar la extracción de datos de su sistema, usted logra a procesarlos en grand cantidad y en tiempo real.

Una vez que la solución es flexible en customización, usted puede configurar todos los indicadores de IVA, retención y cuentas por formato y por concepto.

Al instalar la solución de reportes de medios magnéticos, la cual está disponible desde la versión SAP S/4HANA 1610, usted recibe 7 formatos por defecto:

Además, usted puede crear otros reportes específicos que necesite en la misma herramienta de ACR, lo que confiere simplicidad a los procesos que tiene en su compañía, pues que todo lo que necesita reportar esta centralizado en una única plataforma.

Usted aún puede configurar los accesos de acuerdo a los roles, lo que le asegura seguridad al procesar y reportar datos de su compañía.

¿Le gustó la solución? Mira los pasos para implementarla en su compañía:

Para ser nuestro cliente:

Revise sus licencias con su ejecutivo de cuenta.
Instale las Notas de SAP o support packages.
Configure sus fuentes de datos.
Empiece a ejecutar la solución en ACR.

Para ser nuestro socio de negocio:

Contacte el LPM para obtener su certificación en ACR.

Usted encuentra más detalles en la documentación de la solución. Accede a help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE > Product Assistance > Country/Region Versions > Americas > Colombia > Apps for Finance in Colombia > Advanced Compliance Reporting for Colombia.

Gracias y hasta la proxima.

¿Quiere leer este post en inglés?

Si le gustó este post, le puede interesar este otro: Reporte de Medios Magnéticos: Datos Maestros para Interlocutores Comerciales (Business Partners)

Source: https://blogs.sap.com/2019/04/22/reporte-de-medios-magneticos-de-colombia-en-sap-s4hana-razones-porque-implementar-la-solucion-en-su-sistema/

SAP S/4HANA 1909, Innovation Highlights of the Intelligent Suite

SAP S/4HANA 1909 is out! The 5th release in a row of SAP’s next generation ERP for the on-premise market has been shipped with many functional and technical innovations. Many of you have surely read the SAP S/4HANA 1909 launch blog.

We had shared similar product update videos for the respective SAP S/4HANA 1709 and the 1809 launches. Here is your update for SAP S/4HANA 1909:

What you can expert from this release? First of foremost, SAP S/4HANA is the foundation of the “intelligent enterprise” and comes as an innovative, robust and scalable core ERP.

There are 3 principles that define intelligent ERP, and ultimately provide a Hands-free ERP wherever possible:

Digital age user experience: we will continue and extend the usage of SAP Fiori, coming with the brand new Fiori 3 theme “Quartz”, and this consistently for all business innovations covered it this session. Wherever meaningful we will including conversational design at the heard of the processes
Next-generation processes: Rethinking the way business gets done through the smart junction of technology and innovation. In this release we have new processes like the New Predictive Material and Resource Planning
And automation: leveraging machine learning capabilities and robotic process automation in the standard ERP processes. We will cover a few scenarios in this video.

In this SAP S/4HANA 1909 release, you will find line of business innovations like:

We will start with innovations in the Line of businesses Finance: group reporting and Integrated Financial Planning with SAP Analytics Cloud
Manufacturing with enhancement like the predictive MRP is to benefit from lower inventory levels due to buffer levels that are appropriately sized.
Available to promise innovation like additional check on product allocations, which is based on capacities after the product availability check in advanced ATP
Predictive analytics in Inventory Management: this innovation monitors and make time-dependent investigations of the slow or non-moving materials in your stock
Sourcing and Procurement with the automation of purchase requisitions through configuration of standard rules.

You will find in SAP S/4HANA 1909 industry innovations in those areas:

With SAP S/4HANA for Utilities Product Simplification, we are reducing the time to market for new commodity products
Re-design of the Venture Bank with a new joint venture accounting (JVA) universal journal data model that will replace JVA special ledger tables
In Retail with an innovation leveraging RFID to ease the transfer of goods between the different show floor.

This blog and its video will give you an overview about the highlights for SAP S/4HANA 1909, the digital core and foundation of the intelligent enterprise. Go to the next level of information to understand the value of SAP S/4HANA for your company. Those key assets will be your guide:

Discover S/4HANA
SAP S/4HANA Trial
Discover SAP Digital Roadmap
SAP S/4HANA Help Portal
SAP S/4HANA Business Value Advisor

Follow me on Twitter @ypeterschmitt

Source: https://blogs.sap.com/2019/09/23/sap-s4hana-1909-innovation-highlights-of-the-intelligent-suite/?source=social-global-voicestorm-LinkedIn&campaigncode=CRM-YA19-SSO-GETSOC1

sexta-feira, 4 de outubro de 2019

SAP S/4HANA Migration Cockpit – Introduction

Introduction

Data migration is a key task during the transition to SAP S/4HANA. Based on the different business scenarios it is important to choose the best ETL tool to make the transition into SAP S/4HANA a pleasant journey. These are some key questions to think about data migration requirements:

What deployment option is the target / receiver of the data? SAP S/4HANA or SAP S/4HANA Cloud?
Which data is needed from sources to operate S/4HANA the way wanted? Customizing? Master data? Open items? Balances?
What are the sources and sender systems of the data? Which is the number and type of the source systems? Is the central master data management active?
Can date be migrated “as is” or is it needed to transform it on the fly? Complexity? Are data transformations needed? Is data quality improvement necessary?
Who needs to be involved? Which are the decisions to be taken? Are there major stakeholders?

Prerequisites

To transfer data using the SAP S/4HANA Migration Cockpit, role SAP_CA_DMC_MC_USER is required. To use the SAP S/4HANA Migration Object Modeler (transaction LTMOM), role SAP_CA_DMC_MC_DEVELOPER is required.

The corresponding role for each migration object is also required.

For additional considerations see SAP note 2481235.

Setting up

When working with migration cockpit, the first step is always to create a migration project where the necessary migration objects will activated/created.

To do so, access transaction LTMC and click on the create button.

A pop-up will show up and a name must be entered for the project. There is also a button to select whether the source of data is imported from files or from staging tables (involves a staging DB and schema). These two options cannot be selected at a time and it determines the way the tool will receive the input data.

Transfer data from file: This option allows to perform data extraction from files. The files have to be completed based on XML templates that can be downloaded once an object is generated within the project. The file format and layout should not be changed. When working with files there are some considerations to be taken into account, as described in this SAP Blog by Sybille Lackermeier. Note that file-based projects can handle up to 1,048,576 records, as it is the limit of an excel file, or 100 MB, which is the size limit Migration Cockpit can receive without changing icm/HTTP/max_request_size_KB parameter. Changing it will allow to upload files up to 160 MB as described in note 2719524.
Transfer data from staging tables: When selecting this option, a HANA database and schema is required. In this schema staging tables will be created when an object is generated. It will create as many tables as source structures are defined for the generated object. There are some prerequisites: Firstly, database connections must be available. This can be checked by using transaction DBCO. Secondly, if the connections are available in DBCO, they have to be white-listed in table DMC_C_WL_DBCO using transaction SM30.

When creating a staging table-based project it is mandatory to define a database connection where staging tables will be generated. Take into consideration that this database connection will connect migration cockpit with a HANA staging database and has to be set up prior to the project creation.

For any kind of project a 3-digit mass transfer ID (MID) must be selected. It will identify the project and its objects unequivocally. Each object created / activated in this project will have its name ending with this MID (e.g.: an object’s name in a project identified with MID “00A” will end in “…_00A”. For example: “Z_WORK_CNTR_00A).

This MID is exclusive when exporting / importing projects as well.

Standard object list

Migration Cockpit comes packed with a set of pre-existing objects which can be used by activating them. This object list is increased with every new release.

A full object release can be found in the following SAP Help documents:

Generating a migration object

While working with Migration Cockpit, data will be transferred using the migration objects, which have their own set of source and target structures and fields. Migration Cockpit already contains a set of standard objects which can be used; but sometimes these objects do not fulfil specific needs or there is not an existing one to transfer the needed data. In those cases, development of new objects or enhancements of the existing ones are required.

Working with standard objects

To start working with a standard object go inside the created project, search for the one you need and click on it, and click the OK button which will appear in the pop up.

Depending on the selected migration approach, two different screens will appear.

In the case of a staging table-based project, there are three important buttons above the table which shows the name of the staging tables and their details:

Start transfer: Starts the migration process, which will consist of three mandatory (Validate Data, Map Values, and Execute Import) and one optional step (Simulate Import).
Start synchronization: When changes are made to the source structures, a synchronization is mandatory to apply these changes to the staging tables.
Restart transfer: This button will stop existing transfer processes if they have already been started and it is necessary to start over.

To start the data transfer for a staging table-based project, it is necessary to have entries in the header table.

In the case of a file-based project there are seven important buttons above the table of imported files and their details:

Delete: Deletes the selected file from the list.
Download: Downloads the selected file from the list.
Download template: Downloads an XML file which must be completed with the data which will be transported.
Upload file: Allows upload of XML files for their transfer.
Activate: Flags the file for transportation.
Deactivate: Deletes flag for transportation.
Start transfer: starts the migration process, which will consist of three mandatory (Validate Data, Map Values, and Execute Import) and one optional step (Simulate Import).

To start the data transfer for a filed-based project, there must be at least one file loaded and activated in the list. This file must contain at least one record on the mandatory tabs.

Enhancing a standard object or creating a new one

There are cases when standard objects don’t completely suit custom needs. These cases can be addressed by using another tool: The Migration Object Modeler. It can be accessed via transaction LTMOM, and it allows to change source structures (new structures and fields as well as modify existing ones), structure and field mappings and add rules to manipulate data before it is sent to the target BAPI as well as creating new objects from scratch.

The Migration Cockpit Modeler is composed by five parts:

Global Data: Where global variables and constants which can be used in all rules are declared.
Source Structures: Where the input structures and fields are defined, changing the schema of the template file or the staging tables.
Target Structures: Here is defined the target function module as well as the importing method, the return structure and the testing field for the data simulation.
Structure Mapping: The source and target structures and mapped here.
Field Mapping: Fields are mapped here, depending on the structure mapping done before.

Process of transfer for an object in a file-based project

To load a file-based object, go into said object and click the Download Template button. An XML file will be downloaded. To see its contents, it must be opened in Excel. Do not modify this file’s structure.

Go into the corresponding tabs and complete the necessary data.

When finished, save and close it. Then go back to migration cockpit and click on the Upload File button.

Select the corresponding file and add a relevant description for it.

It is possible to load multiple files to process them at the same time.

To activate it, select it and click on the Activate button. To deactivate an already active file, click on the Deactivate button.

When the files are loaded and activated, click on the Start Transfer button to begin transferring the data.

Wait until validation ends and check that there are no errors in the step, if there are, correct them and validate again. This step will validate the entries sent in the file by checking that identification numbers are in the correct number range and that the information used exists in target system.

If no errors are displayed, click on the Next button to continue to the Value Mapping.

Here each translation rule will show errors if new values are found for the field. If one of the items is clicked, a window like the following one will show up:

There are three types of messages for the items:

Inactive (gray square): which means that the source value is correct but needs to be accepted.
Open (red circle): which means that the system did not find a suitable target value and must be specified manually or changed in the source (file).
Completed (green square): which means that there is a suitable target value and has already been accepted.

For those values marked as open, it is necessary to specify a target value manually. While those marked as inactive can be Checked to mark them as completed if the proposed value is correct.

Once all mapping values have been marked as completed, click on Confirm to save them. Then click Save.

Repeat this process until there are no more mappings to validate and click on Next to continue the process.

Wait until simulation ends and check for errors. If there are, correct them first and repeat from Data Validation. Then click on Next to continue to data import.

Wait until import is finished and check there are no errors. If there are not, click on the Finish button to end the process. If there are errors, correct them and restart the transfer process.

The status of the transferred files will now be set to “Finished”.

As a last step, check on the corresponding tables if the entries have been correctly created.

Process of transfer for an object in a staging table-based project

As a prerequisite to load a staging table-based project, there must be at least one entry in the header table. If there is, then it is possible to start the transfer by clicking the Start Transfer button.