Migration Cockpit Migration Object Modeler S/4HANA Basics

This blog explains the basics of the Migration Cockpit Migration Object Modeler .

Before reading this blog make sure to already your aware of the Migration Cockpit

Transaction : LTMC  .You can find detailed information in the below blog  

https://blogs.sap.com/2017/02/28/getting-started-with-the-s4hana-migration-cockpit-onpremise/

Introduction :

It is a part of the Migration cockpit which integrates Custom objects or  standard objects not provided in the S/4 Hana Migration Cockpit template.

NOTE : Its available only on On-Premise systems

Transaction for MOM : LTMOM (SAP_CA_DMC_MC_DEVELOPER role should be assigned to user to access it

Source Structures :

The structures are shown in a hierarchy way  which are visible in different tabs shown in the excel template in Migration cockpit.

You also have the possibility to make the field ( required ,visible or non-Visible ) in the excel template Right click on the structure->Display view will open the below view

Target Structures :

Target Structures are the strucutres to which the sources structures are mapped .They can be single or multiple fields or tables.

There is a Function Module on the top of the structure which is used transfer data from source structure to relevant target structure to S/4 System.

Structure Mapping : : ‘>>’ this symbols represents that the Target structure is mapped with the source structure.You can also Drag and Drop for the structure mapping in the edit mode.

Field Mapping : This section display all the fields which are mapped and also not mapped

Mapped target fields are displayed with green icon and the others with red.

You can also drag and drop the fields then MOVE statement will appear showing that the field is mapped.

You can also create own

Rules :

There are some rules similar to the enhancements where you can change the values of fields or add custom code .

Field Based rules : These are used to change the target  field values during the migration.(Exmaples like internal and external numbering of customers  )Event Based  : Custom coding can be inserted at some predefined points of predefined events(Like strart of loop or start of record ) .You have an option to write the below three in the drop down of the variant type.(You can also

Free Code

Fixed value

Translation Object

Internal Rules : These are re-usable code modules which can shared across the other rules.This is triggered either with the field-based or event based rules

Translation Objects : This is used for the translation like Country keys, Language keys .

NOTE : Can be enabled only by the field-based or internal rules.

For further information on how to extend the or add new fields please look at the below blog :

https://blogs.sap.com/2017/06/20/discover-the-s4hana-migration-cockpit-migration-object-modeler-onpremise-nltmom/

Fonte: https://blogs.sap.com/2018/02/04/migration-cockpit-migration-object-modeler-s4hana-basics/

SAP S/4 HANA: Simplifications in Sales & Distribution Data Models

SAP S/4 HANA is the new offering from SAP built on the high performance In-memory platform HANA with an enriching user experience using FIORI apps.This new system includes major changes and massive simplifications ranging form changes in underlying data models to new user interface through FIORI apps.

Objective:

The objective of this blog is to understand the data model simplifications in SD area through a comparative study with a non S/4 system.

Below are the major simplification points:

• Status tables VBUK and VBUP have been eliminated and the new status fields have been added to:

• VBAK and VBAP for sales order header and item
• LIKP and LIPS for delivery document header and item
• VBRK for billing document header
• No status fields are present for billing items.

• Simplification of document flow table VBFA

• Document index tables like VAKPA , VAPMA etc. have been done away with.

Comparison:

Let us understand the differences by looking at the table structures:

• VBUK and VBUP are still present in S/4 HANA but they are not filled when an order is created.
• The status fields have been added through append structure.

Table Name	Description	Append Name
VBAK	Sales Order Header	VBAK_STATUS
VBAP	Sales Order Item	VBAP_STATUS
LIKP	Delivery Header	LIKP_STATUS
LIPS	Delivery Item	LIPS_STATUS
VBRK	Billing Document Header	VBRK_STATUS

• If any custom fields have been added to VBUP or VBUP tables in source system, they will have to be added to respective document tables in S/4 HANA system.
• An append field to the document header status table VBUK must be added to one or several of the document header tables VBAK, LIKP, or VBRK. This decision depends on which of the document types the respective field is relevant for.
• An append field to document item status table VBUP must be added to one or more of the document item tables VBAP or LIPS.

VBAK:

VBAP:

When a sales order is created in  a non S/4 HANA system:

Sales Order: 7137:

VBAK table holds the order header details

Order status information is present in VBUK table

Sales Order in S/4 HANA system:

VBAK table contains both the header details as well as the header status

Header status fields are now added to VBAK table

Table VBUK is present but is not filled.

Reason VBUK / VBUP are still present in S/4 HANA:

Since the status tables are not being filled it can be questioned why the tables are still present and not removed from system altogether. The reason for this is to enable smooth transition for those opting for migration to S/4 HANA system.

New function modules have been written which read the document status fields from VBAK , LIKP aur VBRK tables and populate in output whose structure is similar to that of VBUK.

For example FM SD_VBUK_READ_FROM_DOC is a new FM that fills VBUK structure for one SD document out of document header tables. The data is fetched depending upon the document type.

• The output structure ES_VBUK still refers to VBUK table.
• Any custom fields added to appends like VBAK_STATUS will be read by this FM.

Advantages:

• Reduced memory footprint : Since fewer tables are involved this means reduction of redundant data and simplified document flow.
• Now if we need to query the order table on the basis of document status we can simply do so by 1 single query on VBAK table instead of join on VBAK and VBUK.

NOTES:

• OSS Note 2198647 can be referred for further information.

Acknowledgment:

• Reference taken from Simplification List for S/4 HANA 1511 0302.

Fonte: https://blogs.sap.com/2016/07/03/sap-s4-hana-simplifications-in-sales-distribution-data-models/

#S/4HANA 1610: Use case series intro and collection

The adoption of SAP #S4HANA in the last year has been tremendous, which means it is well on its way to becoming the de-facto standard business suite for the digital economy. Last year, with the motivation to clarify the motivation for SAP S/4HANA, we published a series of blogs talking about concrete use cases.

With the SAP S/4HANA 1610 release on October 31^st, we want to continue with this tradition, as it was very well received last time. These use cases explain best how SAP S/4HANA 1610 supports you on your digital transformation journey, including of course all innovations and enhancements of the previous 1511 release.

Again we will answer questions like: How the digital transformation has changed the way of working? What is the outcome? Which benefit does it provide? How do I prioritize, what change do I need to foresee?

Below you can see what has been enhanced or even added as innovations to SAP S/4HANA on-premise with the 1610 release.

From the 15 scenarios mentioned before, we will be covering 9, each with 2 blogs, in the course of the next months. Same as last time, this series will always have 2 angles: The BUSINESS benefit view (a) and the TECHNOLOGY view (b).

While this series unfolds, don’t hesitate to give us your feedback and start discussions on the topics you are interested in. We are looking forward to engaging with you. Stay tuned and do not miss the information sources described in the blogs itself.

Additionally you can always check the newly launched SAP S/4HANA 1610 Release Info page and the SAP S/4HANA 1610 Release & Innovation Summary blog.

Last but not least we want to make you aware, that we are currently working on a new openSAP course, called “Find your path to SAP S/4HANA”, which will be about the three different transition scenarios. It is planned to start in the beginning of 2017.

And follow me via @SDenecken to stay on top of the latest.

_________________________________________________________________________________________________________

The Collection

#S4HANA 1610 use case series: 1a – advanced Availability to Promise (biz view)

#S4HANA 1610 use case series: 1b – advanced Availability to Promise (tech view)

#S4HANA 1610 use case series: 2a – Industry to Core – Retail (biz view)

#S4HANA 1610 use case series: 2b – Industry to Core – Retail (tech view)
#S4HANA 1610 use case series: 3a – Procurement (biz view)

#S4HANA 1610 use case series: 3b – Procurement (tech view)

#S4HANA 1610 use case series: 4a – Warehouse Management (biz view)
#S4HANA 1610 use case series: 4b – Warehouse Management (Tech view)

#S4HANA 1610 use case series: 5a SAP Fiori 2.0 (biz view)

#S4HANA 1610 use case series: 5b SAP Fiori 2.0 (tech view)

#S4HANA 1610 use case series: 6a – Integrated Quality Management (biz view)

#S4HANA 1610 use case series: 6b – Integrated Quality Management (tech view)

#S4HANA 1610 use case series: 7a – Finance (biz view)

#S4HANA 1610 use case series: 7b – Finance (tech view)

#S4HANA 1610 use case series: 8a – Product Lifecycle Management (biz view)

#S4HANA 1610 use case series: 8b – Product Lifecycle Management (tech view)

#S4HANA 1610 use case series: 9a – Production Planning and Detailed Scheduling – PP/DS (biz view)

#S4HANA 1610 use case series: 9b – Production Planning and Detailed Scheduling – PP/DS (tech view)

#S4HANA 1610 Use Case Series Finale and SAP #S4HANA #Cloud Use Case Announcement

Fonte: https://blogs.sap.com/2016/11/09/s4hana-1610-use-case-series-intro/

Transações Basis

SU01 Manutenção Usuário	AL11 Exibe SAP Diretórios
SU01D  Display do Usuário	BD54 Manutenção do Sistema Lógico (Logical Systems)
SU02 Manutenção de Profiles	OSS1  Logon para  Sistema de Suporte online SAP
SU03 Manutenção	SALE IMG para idoc
SU05 Manutençao de Usuários  Internet	SARA Gerenciamento de  arquivamento (Archive Management)
SU10 Manutenção em Massa dos Usuários	SICK  verificação da Instalação (Installation Check)
SMLG Manutencao de Logon Group	SM14  Administrador  de Update
SUPC Geração em Masa dos perfis	SM35 Monitor  de Batch Input
SUIM Relatórios sobre  Usuários	SM56   Monitor  Buffer de Numeração
PFCG Geração de Perfis	SM58 Asynchronous RFC Error Log
PFUD  Recoonciliação dos Profiles X Usuários	SM59  Manutenção RFC
	SAINT  Aplicador de  SAP Add-on
	SPAM Aplicador de Patch
Administração de Client:	SPAU Mostra os objetos Modificados
	SPDD Mostra os objetos DDIC modificados
SCC3 Verifica o log da cópia de  Client	ST11 Exibe Traces de Desenvolvedor
SCC4 Administração  Client
SCC5 Deleção de Client	Daily monitoring TCodes:
SCC7 Post-Processing copia de Client	SM04 Lista de Usuários
SCC8 Exportação de Client	AL08 Usúarios ativos
SCCL Cópia Local de Client	SM12 Exibe de DeletaLocks
SCC9 Cópia remota de Client	SM13 Exibe  registos que estão sendo Atualizados
	SM21 Log do Sistema
Database Administration:	SM50 Work Process
	SM51 Listagem de Servidores  SAP
DB01 Análise  de locks no banco	SM66 Existe todos os Work Process
DB02 Análise de Tabelas e Indexes	ST22 ABAP/4 DUMP
DB12 Monitor de Backup do BD	ST01 Trace de Sistema
DB13 DBA jobs	ST02 Exibe os  Buffers do Ambiente
DB15 Manutençao de Archivemento de Tabelas	ST04 Atividade do BD (SQL Server Performance Analysis)
ST04 SQL Server  Analise de Performance	ST05 trace de Desempenho
DB50	ST06 or ST06N Monitoramento do Sistema Operacional
RZ20 CCMS monitoring	ST10 Estatisticas de Chamada das Tabelas
Transport Management System:	ST03N Performance , do sistema SAP
	SU56 Analise do Buffer por usuário
STMS Transport Management System	STAD  Analise das trasacoes por usuário
SE01 Transport and Correction System	OS07N Analise de todo o ambiente SAP
SE06 Set Up Workbench Organizer	SM02 Enviar menssagem para todo o sistema
SE07 CTS Status Display	Other Monitoring Tcodes:
SE09 Workbench Organizer ( Release Transport )
SE10 Customizing Organizer	OS01 LAN check with ping
SE11 ABAP/4 Dictionary Maintenance	RZ01 Job Scheduling Monitor
SE16 Data Browser	RZ03 Presentation, Control SAP Instances
SE80 Repository Browser	ST07 Application monitor
SM30 Call View Maintenance	STAT Local transaction statistics
SM31 Table Maintenance
SCC1 Transport Role from one Client to Other	Other Useful Transactions Codes
Background Jobs Administration:
	AL22 Dependent objects display
SM36 Define Background Job	BAOV Add-On Version Information
SM37 Background Job Overview	SA38 ABAP reporting
SM39 Job Analysis	SE38 ABAP Editor
SM49 Execute External OS commands	Manutençao do Idocs e Buffers
SM62 Maintain Events	ICON Exibe todos os  Icones do Sistema
SM64 Release of an Event
SM65 Background Processing Analysis Tool	WE02  Existe IDoc
SM69 Maintain External OS Commands	WE07 IDoc estatisticas
	WE20  Definição dos Partner profiles
Administração de Spool:	WE21 Definiçao das Portas
	WE46  Administrador de IDoc
SP01 Visualizador dos Spool	WE47 Manutenção de mensagem do sistema
SP11 TemSe Diretorio	$TAB Refreshes buffer de tabela
SP12 TemSe Administração	$SYNC  Refresh todos os buffers menos  buffers de programa
SPAD Administração de Spool

Fonte: http://sapdicas.blogspot.com.br/2013/08/transacoes-basis.html