quinta-feira, 4 de abril de 2019

List of SAP Fiori Specific T-codes

This Document Contains a list of All Transaction Codes Required for SAP Fiori Development[Front-End,Back-End and Gateway]. For utilization of Workflows in Custom SAP Fiori Apps,Workflow related transactions would be used.Some of these will be available in Frontend[SAP Gateway] and Some will be for SAP Back-End, in case of Central HUB deployment of SAP Gateway. In case you have an Embedded Gateway Deployment,both Back-End and Front-End Transactions would be available in a single system.

The list of T-codes is based on the following system:
EHP7 for SAP ERP 6.0(Release = EHP7 FOR SAP ERP 6.0)
SAP ERP(Release = 2005(SAP ERP 6.0))
SAP Netweaver(Release = 7.4)

and the following Software Components:
SAP_BASIS    Release = 740 SPLevel = 0010    Support Package = SAPKB74010    SAP Basis Component
SAP_ABA    Release = 740    SPLevel = 0010    Support Package = SAPKA74010    Cross-Application Component
SAP_GWFND    Release = 740    SPLevel = 0013    Support Package = SAPK-74013INSAPGWFND    SAP Gateway Foundation 7.40

[Note:]
This list is divided into 3 columns.
(01)T-code
(02)Description of T-code
(03)Alternate T-code called,for example in case of Front-End and Back-End Transaction Codes.
(04)Overview Description of commonly used Transaction codes is provided[New]
[Note:]

Standard T-codes Required:

Odata Service Development T-codes:

SEGW Gateway Service Builder
[Description = Used for Testing SAP Fiori Apps Odata services and also used for enhancing Odata Service like redefining a standard method in the DPC class of the relevant Standard Odata Service. Best way to enhance a standard applications,as all changes are recorded in one project].

Administrative T-codes:

SU01    User Maintenance
[Description = Used for creating users and assigning them roles,especially useful when creating copies of Fiori based roles based on standard template roles].

PFCG    Profile Generator
[Description = Used for creating roles,especially useful when creating copies of Fiori based roles based on standard template roles].

SICF    Maintain Services
[Description = For Testing and Activating Services associated with the Standard Fiori Framework Services as well as Standard and Custom Fiori Applications].

LPD_CUST    Launchpad
[Description = Provides a list of all Fiori Launchpads(Standard[

] and the custom[

] created ones) containing Fiori app URLs,copy,edit,Transport,provided System Alias etc.].

SMLG    CCMS: Maitain Logon Groups
SM59    RFC Destinations (Display/Maintain)
[Description = This is where all Trusted RFC(TRFC’s) for communication between SAP Gateway system and ECC system are setup,with the ability to test them as well].

_____
SPRO    Customizing – Edit Project
Would require access to the following nodes in IMG(Implementation Guide):

SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway
SAP Customizing Implementation Guide > SAP Netweaver > SAP Gateway Service Enablement
SAP Customizing Implementation Guide > SAP Netweaver > UI Technologies

Figure 01 : SPRO Nodes Specific to SAP Fiori

_____
RZ10    Maintain Profile Parameters
RZ20    CCMS Monitoring
RSRT    Start of the report monitor
PTARQ    Test Environment for Leaves
[Description = This is a Suite of Apps,especially for testing and configuring Leave based Scenarios. Pertains to both the Leave based HCM Fiori apps such as ‘My Leave Requests‘(For Employees) and ‘Approve Leave Requests‘(For Manager)].

EXTID_DN    External Identification Type DN
SPAM    Support Package Manager
[Description = This tool is used by the Basis Consultant during Fiori Landscape setup].

SMICM    ICM Monitor

ABAP Related Backend Development T-Codes:

SE93    Maintain Transaction Codes
SE01    Transport Organizer (Extended)
SE80    Object Navigator
SE11    ABAP Dictionary Maintenance
SE18    Business Add-Ins: Definitions
[Description = This tool is used if BADI’s are provided for a Fiori Apps,instead of creating a project in SEGW(Gateway Builder) e.g: ‘HCM_B_PEP_PROF‘ for People Profile Fiori App].

SE24    ABAP Class Builder
[Description = Used when editing or redefining methods of DPC(Data Provider Class) and MPC(Model Provider Class) classes associated with a Gateway Builder Project for the given Fiori App in Transaction SEGW].

ST22    ABAP Dump Analysis
SE63    Translation Editor
SE43    Maintain Area Menu
SE38    Abap Editor
SBWP    SAP Business Workplace
SM30    Call View Maintenance
____
Note:
Authorization for SM30 is required when accessing or configuring Configuration tables for example
creation of Semantic Objects using T-code ‘/UI2/SEMOBJ‘ which makes use of Maintenance Tables.
____

Workflow related T-codes:

SWDD    Workflow Builder
SWIA    WI Administration Report
SWDC    Workflow Definition: Administration
PFTC    General Task Maintenance
/IWWRK/WF_FILTER    Handle Activation of WF item filter

For Front End SAP UI5 Development:

All Transaction code starting with ‘/UI2/‘ and ‘/UI5/‘.

Transaction Codes starting with ‘/UI2/’:

/UI2/73000001    Register POWL APPLID    SICF_INST
/UI2/73000003    Maintenance view for SAP GUI Tags(user defined tags)    SICF_INST
/UI2/73000004    NWBC Configuration – Define Parameter Names(Customer)    /UI2/NWBC_CFG_P_CUST
/UI2/73000005    NWBC Configuration – Define Parameter Names(Customer)    /UI2/SAPLNWBC_CFG
/UI2/73000007    NWBC Configuration – Define Parameter Names(Customer)
/UI2/73000008    Maintain Services    SICF
/UI2/73000009    Trust Manager    STRUST
/UI2/73000010
/UI2/73000011    Trust Manager    STRUST
/UI2/73000012
/UI2/73000013
/UI2/73000014    Server Communications    CLB2_PLATF
/UI2/73000015    Application Server Assignment    CLB2_APPLI_PLATF
/UI2/73000016    badi Creation    SE18
/UI2/73000017    Semantic Objects
/UI2/73000019    SAPLS_CUS_IMG_ACTIVITY(Catalog)
/UI2/73000020    Catalogs
/UI2/73000021    Catalogs
/UI2/73000022
/UI2/73000023    Configuration of RFC Connections
/UI2/73000024
/UI2/73000025    Manage SAP System Aliases    /UI2/GW_SYS_ALIAS
/UI2/73000026    Activate and Maintain Services    /IWFND/MAINT_SERVICE
/UI2/73000027
/UI2/73000028    Maintain Services    SICF
/UI2/73000029    Role Maintenance    PFCG
/UI2/73000030    Data Browser    SE16
/UI2/73000031    Semantic Objects
/UI2/73000032    Launchpads    LPD_CUST
/UI2/73000033    Fiori Launchpad Checks    /UI2/FLC
/UI2/73000034    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG
/UI2/73000035    SAP Netweaver gateway Application Log Viewer    /IWFND/APPS_LOG
/UI2/73000036    Odata Services
/UI2/73000037    Fiori Launchpad Intent Resolution Analysis
/UI2/73000038    Not runnin
/UI2/73000039    badi Creation    SE18
/UI2/73000040    SAPLS_CUS_IMG_ACTIVITY
/UI2/73000041    SAPLS_CUS_IMG_ACTIVITY
/UI2/73000042    SAPLS_CUS_IMG_ACTIVITY    PFCG
/UI2/73000043    SAPLS_CUS_IMG_ACTIVITY
/UI2/73000044    SAPLS_CUS_IMG_ACTIVITY
/UI2/73000045    SAPLS_CUS_IMG_ACTIVITY
/UI2/73000046    Collaboration Tunnel Service    CLB2_TUNNEL
/UI2/73000047    Define Background Job    SM36
/UI2/73000048    Simple Job Selection    SM37
/UI2/73000050
/UI2/73000051    bgRFC Configuration    SBGRFCCONF
/UI2/73000053    Odata Service Settings for Notifications
/UI2/73000054    UI2 Global Cache Invalidation
/UI2/73000055    /UI2/USER_FEEDBACK_Setup    /UI2/FEEDBACK_SETUP
/UI2/73000056    CCMS(maintain Logon Groups)
/UI2/73000057    Badi Creation    SE18
/UI2/73000058    Badi Creation    SE18
/UI2/73000059    Events for Change Document    SWEC
/UI2/73000060    Collaboration Service    CLB2_SERVICE_C
/UI2/CACHE    Register service for UI2 cache us
/UI2/CACHE_DEL    Delete cache entries
/UI2/CHIP    Chip Registration
/UI2/CUST    Customizing of UI Technologies
/UI2/FEEDBACK_SETUP    UI2 Setup User Feedback Service    /UI2/FEEDBACK_SETUP
/UI2/FLC    Fiori Launchpad Checks
/UI2/FLIA    Fiori Launchpad Intent Analyis
/UI2/FLP    SAP Fiori Launchpad
/UI2/FLP_CONTCHECK    Fiori Launchpad – Content Checks
/UI2/FLP_INTENTCHEC    Fiori Launchpad – Intent Checks
/UI2/FLPD_CONF    Fiori Lpd. Designer (cross-client
/UI2/FLPD_CUST    Fiori Lpd. Designer (client-spec.
/UI2/GW_ACTIVATE    Gateway – Activation    /IWFND/IWF_ACTIVATE
/UI2/GW_APPS_LOG    Gateway – Application Log
/UI2/GW_ERR_LOG    Gateway – Error Log
/UI2/GW_MAINT_SRV    Gateway – Service Maintenance
/UI2/GW_SYS_ALIAS    Gateway – Manage SAP System Alias    /UI2/GW_SYS_ALIAS
/UI2/INVAL_CACHES    Global Invalidation of UI2 chache
/UI2/NAV    Register navigation objects
/UI2/NAVPROV    Define navigation provider
/UI2/NWBC    Start UI2 NWBC
/UI2/NWBC_CFG_CUST    NWBC Configuration (Customer)
/UI2/NWBC_CFG_P_CUST    NWBC Config: Define Parameter (Cust)
/UI2/NWBC_CFG_P_SAP    NWBC Config: Define Parameter (SAP)
/UI2/NWBC_CFG_SAP    NWBC Configuration (SAP)
/UI2/PERS_DEL    Cleanup Personalisatation Service
/UI2/POWL    Register POWL for OData consumption
/UI2/SEMOBJ    Define Semantic Object – Customer
/UI2/SEMOBJ_SAP    Define Semantic Object – SAP

Transaction Codes starting with ‘/UI5/’:
/UI5/78000001    ICF: Report for Activating Special Service During Installation    SICF_INST
/UI5/78000002    ICF: Report for Activating Special Service During Installation    SICF_INST
/UI5/THEME_DESIGNER    UI Theme Designer
/UI5/THEME_TOOL    UI Theme Tool

SAP Fiori Front End Specific T-codes:

/IWFND/32000004    Role Maintenance    PFCG
/IWFND/32000011    Activate/Deactivate Metadata cache    /IWFND/MED_ACTIVATE
/IWFND/32000012    Cleanup of Model Cache    /IWFND/CACHE_CLEANUP
/IWFND/32000013    Activate and Maintain Services    /IWFND/MAINT_SERVICE
/IWFND/32000017    Assign Data Provider to data model
/IWFND/32000018    Change View Assign SAP System Aliases to Odata Service
/IWFND/32000020    IMG Activity not found for transaction /IWFND/32000020
/IWFND/32000021    IMG Activity not found for transaction /IWFND/32000021
/IWFND/32000022    IMG Activity not found for transaction /IWFND/32000022
/IWFND/32000023    IMG Activity not found for transaction /IWFND/32000023
/IWFND/32000024    IMG Activity not found for transaction /IWFND/32000024
/IWFND/50000001    Choose Activity
/IWFND/50000003    SAP Netweaver Activation code    /IWFND/IWF_ACTIVATE
/IWFND/50000004    Manage SAP System Aliases
/IWFND/50000005    Configuration of RFC connections    SM59
/IWFND/50000006    SAP gateway client
/IWFND/50000007    SRT_WS_IDP_CUSTOMIZE[Shedule Switch]
/IWFND/50000008    There are no executable transactions assigned to the IMG activity
/IWFND/50000009    Define Background job    SM36
/IWFND/50000010    cleanup for SAP Netweaver gateway Cache and Persistency Frameworks    /IWFND/CLEANUP
/IWFND/50000011    Simple Job Selection    SM37
/IWFND/50000013    There are no executable transactions assigned to the IMG activity
/IWFND/50000014    Role Maintenance    PFCG
/IWFND/50000015    Role Maintenance    PFCG
/IWFND/50000018    Logon Ticket Administration for Single Sign-On    SS02
/IWFND/50000019    There are no executable transactions assigned to the IMG activity
/IWFND/50000022    Deactivate Logging of Variables T100 Messages
/IWFND/50000027    maintaince dialog is incomplete or not defined
/IWFND/50000031    Registration in System Landscape Directory    RZ70
/IWFND/50000038    IMG Activity not found for transaction /IWFND/50000038
/IWFND/50000039    IMG Activity not found for transaction /IWFND/50000039
/IWFND/50000040    IMG Activity not found for transaction /IWFND/50000040
/IWFND/50000043    the maintenance dialog for /iwfnd/v_coobgr
/IWFND/50000044    There are no executables assigned to this
/IWFND/50000045    There are no executables assigned to this
/IWFND/50000046    Class Builder    SE24
/IWFND/50000051    Configuration of RFC Connections    SM59
/IWFND/50000052    bgRFC Configuration    SBGRFCCONF
/IWFND/50000053    Consumer Activation
/IWFND/50000054    Maintenance view for the GW CCMS Structure
/IWFND/50000055
/IWFND/50000056    Enter Correct SNC Names in Table View VUSREXTID(from SAP R/3 4.5)    /IWFND/BULK_USER_MAP
/IWFND/50000057    Change View Logical File Path Definition    FILE
/IWFND/50000058
/IWFND/50000059
/IWFND/50000060
/IWFND/50000061    No transaction found
/IWFND/50000062    Role Maintenance    PFCG
/IWFND/50000063    SAP gateway client
/IWFND/50000065    WSS_SETUP    /IWFND/WSS_SETUP
/IWFND/50000066    User Maintenance    SU01
/IWFND/50000068    Badi /IWFND/BD_DCS_PROCESS_PLUGIN
/IWFND/50000071    IMG Activity not found for transaction /IWFND/50000071
/IWFND/50000072    SAP Netweaver Gateway Log Level
/IWFND/50000073    Configuration of RFC Connections    SM59
/IWFND/50000074    Trust Manager:Display    STRUST
/IWFND/50000075    bgRFC Configuation    SBGRFCCONF
/IWFND/50000076    bgRFC Monitor    SBGRFCMON
/IWFND/50000077    Business Communication Services – Administration    SCOT
/IWFND/50000078    Directory Service Connection    LDAP
/IWFND/59000010    Cleanup Notifications    /IWFND/NOTIF_CLEANUP
/IWFND/59000011    SAP Netweaver Gateway Virus Scan Profile Configuration    /IWFND/VIRUS_SCAN
/IWFND/59000012    Creating Badi    SE18
/IWFND/59000013    Creating Badi    SE18
/IWFND/59000018    SAP Netweaver gateway : Error Log    /IWFND/ERROR_LOG
/IWFND/59000019    SAP Netweaver gateway:Tracing Tools    /IWFND/TRACES
/IWFND/59000020    SAP Netweaver Gateway Application Log Viewer    /IWFND/APPS_LOG
/IWFND/59000021    Simple Job Selection    SM37
/IWFND/59000022    Creating Badi    SE18
/IWFND/59000023    Context based SAP System Alias Configuration
/IWFND/59000024    (BADI Implementation)(Implementations for Badi Definition
/IWFND/59000025    Parallelization for Multiple Origin Composition    /IWFND/MOC_PARALLEL
/IWFND/59000026
/IWFND/59000027
/IWFND/99000004
/IWFND/99000005
/IWFND/99000006    Enable or Disable Soft State
/IWFND/APPS_LOG    SAP Gateway Application Log Viewer
/IWFND/BULK_USER_MAP    Transaction to Perform Bulk User M
/IWFND/CACHE_CLEANUP    Cleanup of Model Cache
/IWFND/CLEANUP    Execute Cleanup
/IWFND/CLEANUP_JOBS    Manage cleanup jobs
/IWFND/CRE_DEF_JOBS    Create Default Cleanup Jobs
/IWFND/ERROR_LOG    SAP Gateway Error Log
/IWFND/ERROR_LOG_E2E    SAP Gateway Error Log – E2E
/IWFND/EXPLORER    Service Explorer
/IWFND/GW_CLIENT    SAP Gateway Client
/IWFND/INIT_CCMS    Initialize SAP Gateway CCMS Contex
/IWFND/IWF_ACTIVATE    Activate / Deactivate SAP Gateway
/IWFND/MAINT_SERVICE    Activate and Maintain Services
/IWFND/MED_ACTIVATE    Activate/Deactivate Metadata Cache
/IWFND/MED_SA_ACTIV    Activate system alias based cachin
/IWFND/MOC_PARALLEL    Parallelize Multi-Origin Compositi
/IWFND/NOTIF_CLEANUP    Cleanup Notifications
/IWFND/NOTIF_MONITOR    Notification Monitor
/IWFND/SERVICE_TEST    Service Explorer
/IWFND/SOFTSTATE    Enable or Disable Soft State
/IWFND/STATS    SAP Gateway Statistics
/IWFND/TRACES    SAP Gateway Traces
/IWFND/V4_PUBLISH    SAP Gateway Service Publication
/IWFND/VIEW_LOG    SAP Gateway Application Log Viewer
/IWFND/VIRUS_SCAN    Configuration of SAP GW Virus Scan
/IWFND/WF_WEBGUI    WebGUI For Executing Workflow Item
/IWFND/WSS_SETUP    Configure WS Message-Based

SAP BackEnd Specific T-codes:

/IWBEP/01000001

/IWBEP/57000001 Configuration of RFC Connections SM59
/IWBEP/57000002 Gateway Settings

/IWBEP/57000003

/IWBEP/57000004    Event Definition
/IWBEP/57000005    Choose Activity
/IWBEP/57000006    Event Type Linkages
/IWBEP/57000007    bgRFC Configuration    SBGRFCCONF
/IWBEP/57000008    bgRFC Monitor    SBGRFCMON
/IWBEP/57000009    Check Configuration Report    /IWBEP/CONFIG_CHECK
/IWBEP/92000002    Maintain Model    /IWBEP/REG_MODEL
/IWBEP/92000003    Maintain Service    /IWBEP/REG_SERVICE
/IWBEP/92000004    Simple Job Selection    SM37
/IWBEP/92000005    SAP Netweaver Application Log Viewer    /IWBEP/VIEW_LOG
/IWBEP/92000006    Clean Up of Model Cache    /IWBEP/CACHE_CLEANUP
/IWBEP/92000007    BADI Creation    SE18
/IWBEP/92000009    Program SRT_WS_IDP_CUSTOMIZE    WSIDPADMIN
/IWBEP/92000012    BADI Creation    SE18
/IWBEP/92000013    Implementation for BADI Definition    SE18
/IWBEP/92000014    BADI Creation    SE18
/IWBEP/92000015    BADI Creation    SE18
/IWBEP/92000016    User Request Management – Application Configuration

/IWBEP/92000017

/IWBEP/92000018    User Request Management – Cleanup Report    /IWBEP/UR_CLEANUP
/IWBEP/92000019    User Request Management – User Category
/IWBEP/92000020    Role Maintenance    PFCG
/IWBEP/92000021    Role Maintenance    PFCG
/IWBEP/92000022    Role Maintenance    PFCG
/IWBEP/92000023    Maintain Annotation Models    /IWBEP/REG_VOCAN
/IWBEP/92000024    User Self Service Remote Destination Configuration
/IWBEP/92000025    Range Maintenance : GW User Self Service    /IWBEP/UM_NR_INT
/IWBEP/92000026    Parallelization of Batch Queries    /IWBEP/BATCH_CONFIG
/IWBEP/97000002    Display Models
/IWBEP/97000003    Gateway Log Level for the Application Log
/IWBEP/97000004    User Maintenance    SU01
/IWBEP/97000005    Structure of the GW CCMS Context
/IWBEP/97000007    Generate ODATA Channel Implementation    /IWBEP/IMPORT_MODEL

/IWBEP/97000008
/IWBEP/97000009
/IWBEP/97000010
/IWBEP/97000011
/IWBEP/99000001
/IWBEP/99000002
/IWBEP/99000003

/IWBEP/99000004    Program /IWBEP/R_COS_CLNUP_JOB_CREATE    /IWBEP/CRE_DEF_JOBS
/IWBEP/99000005    Simple Job Selection    SM37
/IWBEP/ANA_SRV_GEN    Analytics Service Generator
/IWBEP/BATCH_CONFIG    Batch Parallelization
/IWBEP/CACHE_CLEANUP    Cleanup of Model Cache
/IWBEP/CLEANUP_JOBS    Manage Cleanup Jobs    SM37
/IWBEP/CONF_SERVICE    Configuration for IWBEP services
/IWBEP/CONFIG_CHECK    Check Configuration of BEP
/IWBEP/CRE_DEF_JOBS    Create Default SAP GW Cleanup Jobs
/IWBEP/ERROR_LOG    SAP GW Backend Error Log
/IWBEP/ERROR_LOG_E2E    SAP GW Backend Error Log – E2E
/IWBEP/IMPORT_MODEL    Service Description File Importer
/IWBEP/NOTIF_MONITOR    SAP GW Backend Notification Monitor
/IWBEP/OCI_SRV_GEN    OData Srvc.(SAPGW)Generator for OSCI
/IWBEP/REG_MODEL    Maintain Model
/IWBEP/REG_SERVICE    Maintain Service
/IWBEP/REG_VOCAN    Maintain Vocabulary Annotations
/IWBEP/RFC_BOP_DEL    OData Channel : Delete RFC BOP
/IWBEP/RFC_BOP_GEN    OData Channel : Generate RFC BOP
/IWBEP/SB    SAP Gateway Service Builder
/IWBEP/SBS    SAP Gateway Service Builder Setup
/IWBEP/TRACES    SAP GW Backend Traces
/IWBEP/UM_NR_INT    MGW Number Range Interval
/IWBEP/UR_CLEANUP    User Request Clean Up
/IWBEP/V4_REGISTER    SAP Gateway Service Registration
/IWBEP/VIEW_LOG    SAP Gateway Log Viewer
/IWBEP/WS_BOP_DEL    OData Channel : Delete WS BOP
/IWBEP/WS_BOP_GEN    OData Channel : Generate WS BOP

[Note:]
    > While running T-codes starting with a Forward Slash ‘/‘,append ‘/n‘ before them to run the transaction
        code.

[Note:]
    > You can also create an Area Menu with these T-codes and organize them into folders,using T-code
        ‘SE43‘(Maintain Area Menu).

Figure : All SAP Fiori T-codes organized into an Area Menu

[Note:]
> Many of the T-codes are repeated,as they are referenced through another t-code.
> Many of the T-codes are also referenced in the IMG Implementation Guide[SPRO] based nodes as provided earlier in the document.

Extras:

(01)How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?:
click the link below to access the document:
How to Access SAP Fiori Launchpad and other Browser based Transactions in an SAP Fiori Deployment?

(02)How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page?:
click the link below to access the document:
How to Make Customizations in the SAP Fiori Logon Landing(Launch) Page[Doc]?

(03)How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad:

click the link below to access the document:

How to assign Fiori Launchpage to Fiori Launchpad and redirecting to it when logging off from Fiori Launchpad[Doc]?

[Note: This list will be further categorized and updated in the future]

Source: https://blogs.sap.com/2015/12/21/list-of-sap-fiori-specific-t-codes/

Back to Basics – SAP HANA and the Virtual Data Model

The SAP HANA intelligent data platform has been available for eight years, and with each passing year, we continue to see more and more innovation. You can expect the same in the next few weeks with the release of HANA 2.0 SPS04. However, I wanted to take an opportunity to step back and have a look at some “basics” of SAP HANA – what made it different back in 2011 and how this difference continues to add value in 2019 and beyond. This is part one of a two-part series, with another blog post planned for next week. For now, I’ll focus on the in-memory and columnar structure of SAP HANA as well as the value it enables via a virtual data model.

In-Memory and Columnar
I do not intend to get into the technical detail and internals of SAP HANA as there is plenty of help documentation for that. It’s worth mentioning again that SAP HANA pioneered the concept of having a single copy of data in an in-memory and columnar structure and continues to be the market leader in this space. The “single copy” part of my statement is what truly differentiates SAP HANA, meaning we don’t have to transact in a row-based structure and then re-persist the same data in a column-based structure creating redundancy and latency. With the technology advancements in SAP HANA, we’re able to transact directly on the in-memory columnar structure and immediately reap the benefits. This enables optimal performance for both transactional and analytic workloads. Even if we don’t transact directly on SAP HANA, it can handle the load of transactional replication. This means that we can do real-time replication from other databases into this in-memory columnar structure without having to batch up the data with an ETL tool like in the past (though we can do that too if you’d like; perhaps because the source can’t handle the load). Ultimately, the in-memory columnar technology is a key enabler for application advancements like SAP S/4HANA and SAP BW/4HANA, but it also has merit outside those applications which is what I will discuss next.

Virtual Data Model
In the first 6-9 months of SAP HANA being generally available, and before BW on HANA came along, there really was just one use case: SAP HANA as a data mart solution. Sure, we gave it some other names like “side-car,” agile data mart, operational reporting, and application accelerator, but in the end all of these rely on loading data into the platform, modeling the data into a nice structure for analytics, and then connecting either an application or a BI tool to read the data. That sounds easy enough in concept, but what was different was how we were able to accomplish this with SAP HANA. To explain that part, I’m going to try to use the same analogy I’ve been using since 2012…

This may miss the mark with some of my millennial and Gen Z friends, but growing up in the 80s and 90s (Xennials rule!) I was no stranger to the “mix tape.” If I wanted to make a compilation of ‘Love Songs’ for my girlfriend or ‘Raver’s Beats’ for my buddies, it was a big effort. The steps were something like the following:

	Mix Tape
1.	Identify the theme
2.	Determine songs and order – this also involved a calculation of the cassette duration and what could fit
3.	Get the songs – usually recorded onto a raw tape from the radio by lining up the microphone of my boombox with the speakers of my brother’s boombox (and yes, we called the radio station to request the songs)
4.	Copy the songs from the raw tape onto the mix tape in the proper order – being careful to maintain time between songs, etc.
5.	Rework over and over until I like the result
6.	Hand write the insert for the cassette – with “correction fluid” to help me out based on #4 (As a side note, did you know Wite-Out [or Tipp-Ex for my European friends] and Liquid Paper are still selling well?)
7.	Deliver the finished product

This was a true labor of love, and in some ways I miss it. Over time it got a little easier with the introduction of dual cassette decks, the CD, the MP3, and Napster (I admit no wrong doing)…but the game totally changed in 2001 when Apple introduced iTunes and the iPod. Ever since then, I can easily buy my music online and simply drag and drop it into a playlist that automagically syncs to my device. Importantly for my analogy, the digital playlist isn’t making physical copies of the songs but rather simply stores pointers to the one copy in the library or on the device. This allows an easy adjustment at the click of a button if I decide my taste has changed. I may not be making playlists for the same themes as my old mix tapes, but it’s sure easy to maintain my ‘Running Music’ and ‘Kids Songs’ these days.

While that was a fun little diversion to the 80s/90s for me, there must be a reason I brought it up in the context of SAP HANA. In my mind, the 2011 introduction of SAP HANA to the world of business data was similar to the introduction of iTunes to the consumer music world in 2001. Think about it for a minute from a data and business analytics perspective. I can easily draw a comparison between the steps for my “mix tape” and the high-level steps involved in a business analytics project:

	Mix Tape		Business Analytics
1.	Identify the theme	>	Identify the business domain/process
2.	Determine songs and order	>	Determine the necessary data sets (in many cases specific fields)
3.	Get the songs	>	Get the data (often an arduous effort of batch extraction)
4.	Copy the songs from the raw tape onto the mix tape in the proper order	>	Restructure the data for consumption (layers of persisted transformations)
5.	Rework over and over until I like the result	>	Rework (the business needs will inevitably evolve as the output is better understood)
6.	Hand write the insert for the cassette	>	Document the solution
7.	Deliver the finished product	>	Deliver the finished product

The difference with SAP HANA comes in steps 3-5 with the introduction of the virtual data model. Everyone who has worked on a data mart/warehouse project knows that the vast majority of the effort encapsulated in the above steps comes in trying to prepare the data to answer business requirements. With SAP HANA, we changed the game as follows:

Get the data – Simplify the process and do straight 1:1 replication from source to target only applying logic like filter conditions or excluding fields if a specific requirement (i.e. security) dictates the need to do so. I recommend to customers that they establish a principle that data gets stored “exactly once in its most raw format” in SAP HANA.
Restructure the data for consumption – This is the not-so-secret sauce of SAP HANA; because of the previously mentioned technology we can now build a completely virtual data model (aka playlist). The graphic modeler in SAP HANA allows us to build an information model (special types of views) that integrates all of the raw data into a virtual structure that is ready for consumption. This means any aggregations, calculations, transformations, joins, etc. (including the often-requested currency conversion, unit of measure conversion, and hierarchies) all happen dynamically at the time of access. In-memory columnar enables this on-the-fly processing, and the result is that we have removed latency and redundancy from the process – the data is ready for consumption the moment it lands in its raw format. [Note: I recognize that there is still the possibility of extremely costly processing that need to be persisted and of course we need to manage those…but only on an exception basis!]
Rework – While I love the above bullet, this is the one that gets me the most excited about the virtual data model. A former manager of mine used to talk about how you could “fail fast” with SAP HANA. This sounds counter-intuitive asking you to fail, but the reality is that business users rarely know exactly what they need on the first try. With the virtual data model, we can quickly get a model in front of the user, recognize the gaps (failures), and tease out the real business needs. This agility comes from the on-the-fly nature of the virtual data model and avoidance of waiting for overnight batch ETL jobs to complete. In addition, because we’ve brought over all fields from the source, it isn’t an issue when a new data element is requested – a very different experience from the past when we might have also had to change our extraction jobs. The result of these changes is that it becomes much more realistic for developers and business users to sit together and work through challenges in an agile manner.

An example of a virtual data model built as a graphical calculation view in SAP HANA. In this relatively simple case, we have an integrated view of four tables that are modeled together to provide a single semantic layer for consumption.

I mentioned that this type of data mart was essentially the only use case in the first 6-9 months of general availability for SAP HANA. It is also a key part of the foundation for what differentiates applications on SAP HANA (consider the new data model and embedded analytics in SAP S/4HANA) – including the architecture of a full-blown data warehouse. Today, this remains one of the most common use cases for SAP HANA with thousands of customers using a virtual data model productively to provide real-time information to their business users. Use cases run the gamut in both type of data and purpose, but the message is clear that the SAP HANA approach with the virtual data model is a differentiated method of preparing business data for consumption.

In conclusion, the SAP HANA intelligent data platform offers a truly unique capability with the powerful virtual data model – allowing improved agility, reduced latency of information access, and avoiding data redundancy. While this may seem a “basic” use case for SAP HANA, it continues to drive business value for SAP customers as they look to avoid legacy approaches to providing business information and, often, repatriate analytics back to the transactional system for trusted data. Stay tuned for my post “It Just Keeps Getting Better – SAP HANA as a Multi-Model Processing Engine” next week where I’ll explore the more advanced capabilities of SAP HANA that take the virtual data model to the next level.

Source: https://blogs.sap.com/2019/03/27/back-to-basics-sap-hana-and-the-virtual-data-model/?source=social-global-sap+developers-linkedin_company-audienceengagement-developers-saphana-spr-2223420227&campaigncode=CRM-XB19-MKT-DGEALL

Central Finance as an approach to a S/4HANA run Enterprise

Central Finance as an Approach to S/4HANA Profitability Analysis
Central Finance is a deployment mode of S/4HANA that facilitates Companies to move to SAP S/4HANA by bringing together Financial information from multiple ERP’s (both SAP or non-SAP). Central Finance is a SAP S/4HANA system by itself.
In the below example all 4 Company Codes Can run central functions dependent on their option selection on following slide & Solutions available in target landscape

Payments
Cash Mgt & Treasury
Credit, Collection & Disputes Mgt
Closing
Group Close & Reporting
Consolidation
Planning
Legal Compliance Reporting (ACR)
Shared Services

Alternatively, the financials of 3 company codes that originate outside CFin can be merged into the 4th / a different company code. The above business functions can be performed in S/4HANA Cfin in this new company

Value Scenarios for Central Finance
Reporting – Transform Global Financial Reporting – Availability of global financial data in real-time and in great detail (drill down to the source document), and presented in a modern, user-friendly interface, leveraging the user experience capabilities of SAP Fiori and Design Studio. It allows for a common and flexible reporting structure
Processes – Central Receivables/Payables management, Cash & Treasury – Improves the back office operations. Centralized Receivables management & Central payments allows increased efficiency. Higher productivity, security and lower cost of operations. Centralized Credit Management, collections, disputes, rebates, dunning. Cash applications. Centralized Payments.
Merger & Acquisition Template – Quickly absorb new organizations into reporting and financial controls
Landscape transformation – Phased adoption of S/4 HANA Least disruptive S/4 HANA adoption strategy with immediate benefits linked to HANA in-memory processing, universal ledger, fiori reports & common and flexible reporting.
Note: Not a supported pathway as of S/4HANA 1809 to bring logistics on as a second step. But specific “Customer projects” are underway.

Central Finance Applied to a “Customer Environment”

Restrictions at SAP S/4HANA 1809 – Courtesy SAP
Central Payment for SAP Central Finance is released in SAP S/4HANA 1709 with the status “Released with Restrictions”. SAP will use Pilot Note 2346233 to limit read access and list restrictions, ensuring that customers understand and accept restrictions

Restriction	Potential Mitigation
Logistics processes in the source systems that depend on actual clearing status of invoices in the source system may need to be modified: with the technical clearing of the documents in the source system, AP and AR reports in the source system do not indicate the actual clearing status.	No changes planned in standard Central Finance product (except for down payments) In implementation projects, custom scenarios can be built to push status back to source system (not recommended). Logistics process can be modified to query status in the Central Finance system.
Down Payment integration with SD is supported and down payment integration with MM should be solved by project.	Down Payment integration with MM is not included in 1809, but remains a roadmap topic for Central Payment.
Credit card can be used only when settlement run is triggered from the source systems.	The clearing and settlement status from source systems can be centrally monitored in the Central Finance system
The historic open items that you have in the source systems before switching to Central Payment have to be paid and cleared in the source systems. To avoid double payment in both source and Central Finance system, you can apply SAP Note 2654572 to set ‘Payment Block Reason’ to block the payment for legacy open items in the Central Finance system.	Payment for historic open items in Central Finance system with setting technically cleared indicator in source system is not supported in 1809, but remains a roadmap topic for Central Payment.
When you run FS-CML(Consumer and Mortgage Loans) in a company code in source ERP systems, you cannot activate Central Payment for the company code.	No change planned
Paying centrally also requires VAT and withholding tax reports to be executed in the Central Finance system. There are restrictions on tax reporting.	It needs to be verified for each company code if tax reports show the correct values in the Central Finance system before Central Payment activation in the productive system
For the scenario that customer’s source system(s) is third-party system(s), note 2597587 should be implemented if a customer wants to use Central Payment functionality.
Following Restrictions occur for re-activation of Assets in Central Payment scenario: • Decentral Asset Accounting: Central Payment is only released for those company codes in which no re-activation of assets is necessary after cash discount is taken or no cash discounts are used at all. • Asset Accounting runs centrally: No restrictions in regards of re-activation of Assets in Central Payment scenario.
The Central Finance system needs to be configured in a way that at least as many decimal digits are defined for a currency as maintained in the source system. For further details see also SAP Note: 2599964 and 2292043.

Innovation in 1809 – Side Panels, Centralized Payments

Side Panel displays Central Finance data related to the concerned source transactions in a side screen area of SAP GUI / Business Client.
Side Panel for Central Finance can provide Central Finance data for the source user.
In Release SAP S/4HANA 1709, FPS2 side panels for FI documents and some master data were delivered.
In SAP S/4HANA 1809, SAP SE has enabled MM invoice and SD invoice for Side Panel. When the user displays an MM invoice or an SD invoice in the source system, the replicated FI documents for the relevant of the FI documents of this invoice will be displayed in the Side Panel .

Courtesy SAP SE

There are other limitations to be assessed e.g. if FI Document splitting is not active in the downstream SAP ERP, then it is not advisable to have the same in CFIN. In these scenarios it might not be possible to move logistics processes into the same S/4HANA system as the CFIN unless the downstream SAP ERP is fully decommissioned.

Source: https://blogs.sap.com/2019/04/01/central-finance-as-an-approach-to-a-s4hana-run-enterprise/

segunda-feira, 1 de abril de 2019

S/4HANA Classical MRP vs MRP Live

Classical MRP:

The main function of material requirements planning is to guarantee material availability, that is, it is used to procure or produce the required quantities on time both for internal purposes and for sales and distribution. This process involves the monitoring of stocks and, in particular, the automatic creation of procurement proposals for purchasing and production.

In doing so, MRP tries to strike the best balance possible between

optimizing the service level and
minimizing costs and capital lockup.

The automatic planning run in MRP determines any shortages and creates the appropriate procurement elements. The system generates messages for critical parts and unusual situations so that you can rework the planning results in a specific area with problems.

MRP Live:

Using MRP Live, you can benefit from improved performance and execute the planning run in much shorter cycles. This means that you can execute several planning runs daily providing the MRP controller with the following benefits, for example:

More up-to-date supply and demand information on which to base decisions.
Faster reaction to demand changes reduces the risk of stock-outs and means that you can reduce safety stocks.
Match demand and supply more efficiently than was previously possible.
Identify and react to issues faster than was previously possible.

The report MRP Live (with the technical name PPH_MRP_DISPATCHER) is a copy of the report RMMRP000 and provides the following options for carrying out the planning run:

MRP Live (transaction MD01N) calls MRP on HANA
MRP Live (transaction MD01N) calls classic MRP

Planning selection MRP Live and Classical MRP

During the planning run, the system plans the materials according to the sequence determined by the low-level codes that are defined in the bill of materials. That is, for the first low-level code (0), the system determines which materials can be included in MRP Live on HANA and plans these first. In a second step, the system determines the materials with the same low-level code that could not be planned in MRP Live on HANA and then automatically plans these materials using classic MRP. Included in this second step are also the materials that were planned in MRP Live on HANA but for which an error occurred. Both the planning in MRP Live on HANA and classic MRP has to be completed for one low-level code before the system commences the planning of the next low-level code (1).

That is, during the planning process, the system divides the materials into groups:

Materials that can be planned using MRP Live on HANA
Materials that still have to be planned in classic MRP because:
- They require a planning feature that is not yet supported by MRP Live.
- You have set the Plan in Classic MRP indicator in transaction md_mrp_force_classic. In this report, the system displays all materials with active MRP views in the material master and you can define that the planning run is to be executed using classic MRP for individual materials. You should check which materials require the processing of a BAdI during the MRP run and always set this indicator for these materials.
Materials that cannot be planned in either MRP Live on HANA or in classic MRP because of inconsistent master data, for example. The system creates exception MRP lists for such materials that cannot be planned.

Parameters Differences

Additional References:

https://launchpad.support.sap.com/#/notes/2268085
Best Regards,
Lingaiah

Source: https://blogs.sap.com/2019/03/25/s4hana-classical-mrp-vs-mrp-live/?

Central Finance as an approach to a S/4HANA run Enterprise

Payments
Cash Mgt & Treasury
Credit, Collection & Disputes Mgt
Closing
Group Close & Reporting
Consolidation
Planning
Legal Compliance Reporting (ACR)
Shared Services

Restriction	Potential Mitigation
Logistics processes in the source systems that depend on actual clearing status of invoices in the source system may need to be modified: with the technical clearing of the documents in the source system, AP and AR reports in the source system do not indicate the actual clearing status.	No changes planned in standard Central Finance product (except for down payments) In implementation projects, custom scenarios can be built to push status back to source system (not recommended). Logistics process can be modified to query status in the Central Finance system.
Down Payment integration with SD is supported and down payment integration with MM should be solved by project.	Down Payment integration with MM is not included in 1809, but remains a roadmap topic for Central Payment.
Credit card can be used only when settlement run is triggered from the source systems.	The clearing and settlement status from source systems can be centrally monitored in the Central Finance system
The historic open items that you have in the source systems before switching to Central Payment have to be paid and cleared in the source systems. To avoid double payment in both source and Central Finance system, you can apply SAP Note 2654572 to set ‘Payment Block Reason’ to block the payment for legacy open items in the Central Finance system.	Payment for historic open items in Central Finance system with setting technically cleared indicator in source system is not supported in 1809, but remains a roadmap topic for Central Payment.
When you run FS-CML(Consumer and Mortgage Loans) in a company code in source ERP systems, you cannot activate Central Payment for the company code.	No change planned
Paying centrally also requires VAT and withholding tax reports to be executed in the Central Finance system. There are restrictions on tax reporting.	It needs to be verified for each company code if tax reports show the correct values in the Central Finance system before Central Payment activation in the productive system
For the scenario that customer’s source system(s) is third-party system(s), note 2597587 should be implemented if a customer wants to use Central Payment functionality.
Following Restrictions occur for re-activation of Assets in Central Payment scenario: • Decentral Asset Accounting: Central Payment is only released for those company codes in which no re-activation of assets is necessary after cash discount is taken or no cash discounts are used at all. • Asset Accounting runs centrally: No restrictions in regards of re-activation of Assets in Central Payment scenario.
The Central Finance system needs to be configured in a way that at least as many decimal digits are defined for a currency as maintained in the source system. For further details see also SAP Note: 2599964 and 2292043.

Innovation in 1809 – Side Panels, Centralized Payments

Side Panel displays Central Finance data related to the concerned source transactions in a side screen area of SAP GUI / Business Client.
Side Panel for Central Finance can provide Central Finance data for the source user.
In Release SAP S/4HANA 1709, FPS2 side panels for FI documents and some master data were delivered.
In SAP S/4HANA 1809, SAP SE has enabled MM invoice and SD invoice for Side Panel. When the user displays an MM invoice or an SD invoice in the source system, the replicated FI documents for the relevant of the FI documents of this invoice will be displayed in the Side Panel .

How do I prepare for S/4HANA as a Developer?

This is a blog post based on a presentation I gave at SIT Maidenhead this year.
I am Senior SAP Developer at the University of Warwick and we are in the early stages of a S/4HANA conversion project. For our well-established system, the step to S/4HANA represents a considerable undertaking and needs to be planned well. It also means that in a multi-disciplinary team like ours at the University, different team member roles require a different transformation of skills. Here, I would like to give you an early take from my perspective on what I see as the new key skill areas for a SAP Developer when faced with a S/4HANA conversion.
Please note that this is not a “How-To-Implement-S/4HANA-Guide”, but a take from a SAP Developer perspective on what new topics and tasks may be lurking on the horizon for you. It is also a snapshot of my current understanding.

Background

Our SAP system was implemented at the University in the late 90s. We are currently running Suite on HANA, which obviously takes the sting out of HANA-related ABAP changes, since these have already been performed as part of the upgrade to HANA.

“our” S/4HANA OnPrem journey

For an envisaged S/4HANA on premise brownfield conversion, we have started to use an iterative sandbox approach (build->convert->test->scrap->build->convert->test->scrap etc). This means that several conversions will take place in order to acclimatise the team with the steps and tasks required in order to perform a conversion. This is helpful for the following reasons:

it gives the team a more realistic view on timelines for build and conversion
it prepares the team for any data cleansing or tidying tasks necessary
it allows for increase the release level (first 1709, then 1809, then plus Feature Packs) and experience the benefits of an improving digital core

I’d like to stress the importance of the second point re data cleansing and tidying: it is important to realise that any of these changes need to be applied to all systems in your landscape. Eventually, the data related changes will need to be signed-off by somebody in charge in your organisation once these are to be applied to a Productive environment. Plan and include the timelines for this in your project plan at an early stage.
Once the team has sufficient knowledge and confidence with the new environment, User Workshops with key “Superusers” will be woven into the sandbox iterations. This will guide team members on which user group will require which set of functionality / UI (Fiori, Fiori Enhanced, UI5 bespoke, SAP GUI for HTML, Personas or good-old- GUI for Windows/Java). Moreover, it will start the dissemination of new features and create excitement about the opportunities of the upcoming new SAP release.

How to prepare as a SAP Developer?

As Donald Rumsfeld once said, “there are knowns and unknowns”. There are also “known unknowns”. The importance here is to eliminate the latter through preparation and training. In terms of skills and tasks I would separate these into 3 areas: Basics, Must-Haves and Nice-To-Haves.

Basics

The first thing you should get your head around are ABAP Adaptations. You need to find out what the development effort is to adapt your custom ABAP code in order to make it work in the new S/4HANA world. For instance, Customers and Vendors have now been moved to Business Partners (customer-vendor integration, or CVI for short). Material numbers are now 40 and not 18 characters anymore. All this drives development effort and all eyes are on you to figure out by when you can get the system working again.
Tip 1: use SAP’s own Readiness Check. This will give you a first flavour of what a conversion to a S/4HANA system in your landscape could be like. The Readiness Check dashboard (pictured) gives you a high-level custom code analysis.

The Readiness Check also gives you a good overview for other Business Process Analytics (“how many orders are not closed?” for instance), which can be a good conversation opener for functional colleagues in user workshops.
Tip 2: use a remote ATC check from a remote system (preferably on ABAP Stack >=7.52) to get the full picture on ABAP Adaptation effort. At the University, we downloaded the full list and then separated each of the findings into “easy” (0.25 days), “medium” (0.5 days) and “hard” (1 day) adaptations. This gives you a very crude total figure that will nonetheless make your Project manager very happy.
Tip 3: use data collectors as early as possible in Solution Manager to collect usage data for custom code in your Productive System. This will pinpoint any custom code which is not used at all. “Dead custom code” is a no brainer when it comes to retiring old code before you convert and adapt (Custom Code Lifecycle Management).
The above should give you some basic requirements and effort planning to get started. I can highly recommend the blog posts by Olga Dolinskaja for ABAP Adaptations and ATC setup.

Must-Haves

Fiori Launchpad

Let’s get two things out of the way first:

you will enable A LOT of Fiori tiles
you will troubleshoot QUITE A FEW Fiori tiles

But it’s fine, because during the sandbox iterations it will help you to familiarise yourself and develop skills with Launchpad Designer, Fiori Apps Library and Fiori Frontend Server (“nuspeak” for Gateway) service enablement (transaction /IWFND/MAINT_SERVICE). When it comes to so-called KPI Fiori tiles (the ones with the fancy dynamic display), you also need to learn how to dig deeper and enable integrated BW components, for example, of the system to make these work.
I would also recommend to have a look at your current security concepts, since the new FLP-based world might force you to review some of the existing roles and authorisations in your landscape. My relatively early take on this is: if you are using a lot of bespoke authorisations with very granular restrictions then you might want to set aside time in your project plan to redesign this in the new S/4HANA world.
If Fiori apps can not provider your users with the luxuries they have become accustomed to then you have to dig a little deeper into your Fiori Enhancement box-of-tricks. This is likely going to include Javascript skills to understand and develop UI5, develop Gateway services. You may also decide to develop a completely bespoke UI5 app, use Personas or simply drop into SAP GUI for HTML when a Fiori tile is clicked. Further down I will talk more about the importance to know and differentiate between these UI options. In other words, a timely delivery of the S/4HANA project will also depend on your skills to evaluate effort to deliver on a user requirement needed on Day 1.

ABAP Core Data Services

I can only scrape the surface of this HUGE topic here, but rest assured you will need CDS skills, because so many things cascade from this, such as:

Code Pushdowns (move processing from the application to the database layer, where possible)
Gateway Service exposure (most of SAP’s Fiori applications use CDS exposed services and so should your bespoke apps)
Embedded Analytics (one of the cornerstones of why you should move to S/4HANA is enabled through CDS) – there is also a good introductory SAP Press book on this.
Custom reports in Fiori Custom Analytics apps (helps you to move away from custom reports and to a world where users can model their own reports)

Use SAP’s own Help and Training materials to learn about CDS views. There is also a SAP Press book on CDS coming to a virtual or real bookshelf soon.

Nice-to-haves for a Developer

Having identified FLP and CDS as must-haves, we are now moving into the greyer area of nice-to-haves for Developers – if you disagree with some of my suggestions here, please leave a comment below as I’d love to hear more. These are mainly about UI and UX, helping me to help other team members to promote the system to users.

UI Options

The first key skill to gain is to get a handle on UI options, by which I mean to become proficient in knowing when to suggest or use the multitude of SAP-based UI variations offered with S/4HANA:

Fiori (ie “vanilla”)
Fiori enhanced (using so-called “hooks”)
SAP GUI for HTML
Personas
WebDynpro
bespoke UI5

The above list obviously represents a sliding scale in terms of development effort and skill levels needed. The point I am trying to make here is that it can be very helpful for a developer to know when to use which. As a consequence, this level of knowledge can be very helpful when it comes to project and timeline planning (“how long is it going to take you to rebuild a bespoke Goods Issue UI5 app?”, for example).

Enterprise Search

Each time I observe end users interacting with S/4HANA, I notice that Enterprise Search appeared to be one of the feature highlights. It is not hard to see why: it is practically Google for the Enterprise and allows you to experience a SAP system in a very new way by simply searching for any keywords and receiving a quick response. This is a far cry from navigating around using transactions.
Developers should see this as an opportunity to promote benefits such as this to their end users. In other words, if there is a feature that makes SAP more popular, make sure it works and is responding fast. Also, look into any options to create your own Enterprise Search for custom business objects. For example, there may be a bespoke transaction which creates data in Z* tables. Why not create a custom Enterprise Search help to let users search for these, too?

Summary

On the whole, I would summarise my experiences thus far into the following points:

Plan in iterative cycles, sandboxes
Include key (“super”) users at the earliest stage possible
Capture conversion issues early and plan these into your delivery
Focus on the basics and Must-have skills listed above
If you are about to deliver a lot of new code, also embrace new(er) paradigms like ABAP Test Cockpit (ATC), ABAP Unit testing and Test-Driven Development (TDD)
Great topical bloggers to follow are: Jocelyn Dart, Olga Dolinskaja
Get clued-up on embedded analytics and Enterprise Search

As mentioned in the introduction, my summary here is merely a first experience sharing exercise. It also represents a snapshot in time. I would be very to hear about your experiences or feedback comments below.
Thank you for taking the time.

Source: https://blogs.sap.com/2019/03/27/how-do-i-prepare-for-s4hana-as-a-developer/?source=social-global-sap-developers-linkedin_company-audienceengagement-developers-saps4hanacloud-spr-2215645769&campaigncode=CRM-XB19-MKT-DGEALL

terça-feira, 26 de março de 2019

SAP S/4 HANA – FAQ Answered

Interested in getting to know

Why SAP introduced S/4 HANA?
What are the common features of the new offering?
What value it adds to the businesses?
How it can be acquired and utilized?
Where you can get more information? and
Who should learn the subject and earn its qualification?

I got answers to all of the above questions and in this blog, I’m sharing with you what I’ve learned.

Digital and Connected World

I am talking to you through a media, which in this case is an online collaboration platform, without which maybe I couldn’t even have known your name. We are living in a digital world and are connected. I’m “talking”, like many others, here and also at other forums. We can have business as well, no matter where we live on this planet, through the globalization of business networks.
It’s not only us who are connected but different devices & objects as well; the Internet of Things, in addition to the Big Data being produced by such networks, is another amazing revolution which has impacted our daily lives. Do you see how complex it is becoming day-by-day and how many solutions are now needed to solve the challenges we face? There are new business models which require Technology to support them.

Technological Developments

Remember the time when opening multiple files on a PC at one time was challenging? Or when opening a web page was like waiting for a bus which used to come on a stop after a long time?
Time changed and now with the latest technology, speed isn’t an issue anymore. Imagine how it’s on the machines used by the businesses. The advancement in this area, such as Big Memory, Larger Disk Space, and Multi-core Processors, has allowed the processing to be really fast. The latest hardware supports the businesses in dealing with challenges such as handling multiple tasks at one time and avoiding delays to get the required information in real time.

Business Applications

Staying competitive in the market requires a business to respond to its customers’ needs in a timely manner and it’s possible only if it has the right information available at a time when it’s needed, to decide and act to produce & deliver the required products/services.

The smart Applications support businesses with reading, analyzing, and predicting customer behaviors.

SAP has led the market for a long time, in this space, by providing the needed Solutions, leveraging the IT Trends AND underlying Technology of the specific era such as the mainframe, client/server, web-based, and now the cloud.
S/4HANA Solutions exploit the power of Technological Advances and support the latest Business Models to be able to serve the global customer base.

Core and LoB Solutions

The SAP S/4HANA splits its Solutions to meet different & varying requirements of individual businesses, the Enterprise Management to support the Core Business Processes, and Line of Business Solutions to extend and enhance the selected Business Functionalities.
It’s advantageous for many reasons including the usage according to the needs while still benefiting from the

underlying powerful in-memory data management and application platform, called HANA, and
advanced and flexible User Experience across devices through a design approach, called FIORI.

I’m impressed with such an offering; you pay only as much as you use. The Customers interested in the S/4HANA Solutions don’t need to buy the complete suite, instead, they can just start with the core and extend it as their businesses grow.

Key Characteristics

To support a business with maintaining transactions concurrently across its functions and to build & use analytical reports, previously OLTP and OLAP activities were performed separately, by SAP and other tools. The traditional way of having insights on the data, maintained in the SAP ERP and other Solutions, was to extract the data from the source systems and load it into the target BW system, to transform it into meaningful information.
The HANA powered SAP Solutions combine the Online Transaction AND Analytical Processing (OLTP and OLAP) which for business means having access to real-time information within a system.
It’s just ONE example of the powerful features of the S/4 HANA offering, another noticeable feature is unified & better User Experience across devices, provided through FIORI, turning “Complexity” to “Simplicity”.

Deployment Options

If you want to align your business with the standard practices, followed by many other organizations around the world, and want to avoid the hassle of maintaining the Data Center, Operations, and Technical Support of the best-run solutions, you can now take advantage of SAP offerings which runs on SaaS (Software as a Service) model. It’s based on subscription, allowing you to pay on usage. You can always upgrade/downgrade depending on your current business needs.
There are a variety of Solutions, to support different Lines of Business, which are provided according to the specific business needs, in-cloud as well as on-premise. The on-premise S/4 HANA solutions can also be managed by 3rd parties, thus allowing customers with the flexibility of customization, in addition to managed operations & support services. Such an option is known as HEC (HANA Enterprise Cloud).

Starting Point

Exploring the features of best-practices Solutions was never as easy as it’s now. You’re an Enterprise, running a Professional Services Business, or in Marketing/Sales domain, SAP provides you with the options to try pre-configured Solutions with master & transactional data populated for such business models. Here’s the place where you can start your journey.

https://cal.sap.com/catalog
The trial is provided for 30 days and you can either get the solutions hosted in the cloud, downloaded and installed to your own hardware. If you think the Solutions meet your business requirements, you can proceed with getting these activated for your productive usage. Having such an option is particularly useful to explore the features before making investment decisions.

Transformation Journey

Depending on your particular circumstances, you can choose the

new implementation, if you are ready to re-engineer your existing business processes around S/4 HANA best-practices,
conversion, if you want to leverage the capabilities of the new solutions without interrupting your current processes, or
landscape transformation, scenario if you are consolidating your existing systems to a single Solution.

Whatever journey customers choose to have, SAP provides step-by-step guidelines as well as the required resources to help them with migrating to the new environment as smoothly as possible.
The SAP Activate, combining the best-practices, guided configuration, and methodology, help customers with implementation and support, which is often referred as “build smart and run simple”.

Know How to Learn and Use SAP Activate?

Major Activities

The customer journey to S/4 HANA Solutions is made very simple by SAP. It not only provides the tools and best-practices for Data Migration, which is considered the most complex activity on such projects but also on Custom Code Management, to allow customers to analyze the existing code & align it with the new Solutions.
In addition to the Technical work, it also assists businesses with ensuring User Readiness, an activity which is required to prepare the ground, by providing the necessary guidelines & content.
Those of you who have worked on earlier Solution Implementation Projects may see the value of such offering. With the step-by-step guides available for each of the aforementioned and additional activities, the customers can now have a quicker time to value.

Additional Resources

If you are already familiar with SAP Business Suite or ERP Solutions and want to learn about the S/4 HANA, the S4H01 is the course which provides the necessary information on the new Solutions. And if you want to learn in detail what I’ve explained in a summarized form, the S4H100 is the right course.
These courses are good for Project Managers, Solution Architects, and Consultants, and are available for consumption within the SAP Learning Hub.

Qualification > Experience > Skills

The SAP S/4HANA Implementation Tools and Methodology Learning Journey provides the details on how to earn the C_S4IMP and C_ACTIVATE qualifications through which you can help businesses with implementing the latest SAP Solutions. The summary I’ve provided above can

set you up with understanding the core concepts, taught within the SAP Business Suite to SAP S/4HANA Delta and SAP S/4HANA Implementation Scenarios, and
help you with learning them in detail when you explore both the courses.

I’ve also created a short video to describe the basic concepts for those who are new to the subject which can be seen here:

Those of you who are, or going to be, engaged on S/4 HANA Projects, may find the above coursework very useful. I’ve gone through it, have learned the skills, earned the qualifications (as can be seen here and here) and find myself ready to support such transitions, and I recommend the same to YOU as well.
If you’ve any questions or suggestions, please leave your comments.

Source: https://blogs.sap.com/2019/03/20/sap-s4-hana-faq-answered/?

quinta-feira, 21 de março de 2019

Reconcile S/4HANA Credit Management with SD Credit Management on a System Conversion

When doing a system conversion to S/4HANA you may notice that Credit Management (FI-AR-CR) is not available anymore. This functionality is replaced by SAP Credit Management (FIN-FSCM-CR). Note 2270544 will give you all the information about the business impact for this simplification item.
So now you will have to set up SAP Credit Management in S/4HANA to fulfill the business needs that where contented by the previous Credit Management functionality. This usually means that customers require similar functionality and process as they where using on ECC before the conversion. This is where we get to the crux of the matter. Trying to reconcile open value for SD Documents between these two functionalities is not an easy task.
After the conversion all the structures that belonged to the old SD Credit Management functionality will be empty, the master data transaction would be not accessible, and all the credit information on credit exposure will be again calculated by FSCM.
In FSCM you can run the reports as UKM_COMMITMENTS to display all the information by Credit Exposure Category. For FI Documents, these reports can be relatively easily compared to reports such as FBL5N and FBL5H after conversion to check if the credit exposure was successfully updated.

Credit Exposure Categoy	Name	Report FSCM	Report to compare
200	Open Items from FI	UKM_COMMITMENTS	FBL5N, FBL5H
300	Special Credit Exposure	UKM_COMMITMENTS	FBL5N, FBL5H

But for sales documents, there is no report that can easily compare Credit Exposure. As mentioned before, structures where this credit exposure is updated, are empty after the conversion. And even before the conversion, these structures (S066 and S067) will have an accumulation, and no detail by document.
Note 377165 describes how the open values are updated in the old Credit Management functionality, and the structures where it is stored. If you want to do a comparison, these values must be listed and keep before the conversion.

Credit Exposure Categoy	Name	Report FSCM	Value before conversion
100	Open Orders	UKM_COMMITMENTS	S066-OEIKW
400	Delivery Value	UKM_COMMITMENTS	S067-OLIKW
500	Billing Document Value	UKM_COMMITMENTS	S067-OFAKW

If there are update errors, it would be a good idea to run report RVKRED77 to reorganize credit data before getting the values from the structures mentioned before.
Still, the structures will have an accumulated value by period, and no information on the specific documents that are affecting the open value. Unfortunately, there is no standard report to get this information.

If it is imperative to get this detailed information, again note 377165 will give more information on how to get this information.
Sales Order Open Value
Open Sales Order Value is calculated from the open schedule line quantity (VBEPD-OLFMNG) multiplied with the item credit price (VBAP-CMPRE). Consider that the material availability date will define the period in which the open sales order value is updated. Only items with confirmed quantity (VBEP-BMENG) will update an Open Sales Order Value, so this logic must be considered to correctly calculate the Credit Exposure for a Document. Some exceptions to these rules are explained in the note mentioned before.
Let’s see an example: Sales order 5523 has a net value of 1.000,00 BRL. If the item data is checked, the credit price is 126,73 BRL, this is the net value plus tax value. This document has one schedule line with confirmed quantity, so the open schedule line quantity (confirmed minus delivered) will be the base for the open value calculation, and updated for September 2018, adding a total of 1.267,28 BRL.

Fortunately, this is the only sales order for this customer on this period, so the value on structure S066 match the calculation performed.

Open Delivery Value
For Open Delivery Value, the value updated in structure S067 is not separated in time periods. This means you will get one value per credit control area and credit customer. The value is again calculated from the credit price and the open delivered quantity. Delivered quantity may be fetched from the document flow table VBFA. Consider that this open quantity is affected even from credit blocked deliveries, so you will have to check delivered quantities not yet billed.

Open Billing Documents
Same as Open Delivery Value, the Open Billing documents only consider credit control area and credit customer, not time periods. Same as before, you will have to fetch the billed quantity not yet posted to accounting and multiply to the credit price. Billed Quantity may be fetched again from the document flow table.

As you may get the feeling by now, the Open Value Calculation at sales document level is not an easy task, and different logic that must be considered to perform a correct calculation. You may consider create a custom report to be executed before and after the system conversion to properly compare credit exposure between SD credit Management and FSCM in S/4HANA.

Thanks,

S/4HANA RIG

Source: https://blogs.sap.com/2019/03/21/reconcile-s4hana-credit-management-with-sd-credit-management-on-a-system-conversion/

S/4HANA Subcontracting with MRP Area

In subcontracting, the vendor is provided with materials (components), which he uses to produce the finished product. From the point of view of materials planning, subcontracting is initiated by the special procurement key Subcontracting.
The special procurement key is allocated to the finished product or the assembly in the material master ( MRP 2 view).
In order to plan specific material requirements for each individual subcontractor, you can use MRP areas. You can thereby create an individual MRP area for every subcontractor

Main differences between S/4HANA and ECC.

ECC – with vendor segment

S/4HANA – without vendor segment

If you do not use MRP areas for components to be provided to the subcontractor, there is no separation of provision stocks and subcontracting requirements. The system displays the provision stocks and requirements to be provided as usual stocks and requirements in the net requirements segment of the plant. The provision stock that is already available for a subcontractor (supplier) will be considered as unrestricted-use stock in the plant. The system uses this stock to cover all requirements inside the net requirements segment, not only the requirements for components to be provided to the subcontractor (supplier).

S/4HANA subcontracting process redefined with flexible functionality. In SAP S/4HANA MRP uses default planning parameters if MRP-area-specific material master records do not exist. You only have to create an MRP area for every subcontractor. Of course, it is still possible to create MRP area/supplier-specific material master data if required.

This simplification has the following advantages:

Separate planning of every subcontractor is possible without having to create an MRP-area-specific material master record.
The planning logic is simplified. There are two rather than three different ways to plan parts to be provided to a subcontractor.

The default way of planning parts to be provided to subcontractors is based on MRP areas. A subcontracting MRP area should be created for every subcontractor. It is not required to create an MRP-area-specific material master record for every part to be provided to the subcontractor, but of course, it is possible if you want to overrule the default planning parameters.

If you have several subcontractors requiring the same component materials and if you do not yet use MRP areas to plan the required components then proceed as follows:

Create MRP areas for every subcontractor (can be done before or after upgrade)
Run regenerative MRP after the upgrade

Subcontractor MRP area configuration

You can follow SAP navigation path or transaction code OMIZ directly to configure MRP areas.
Click on New Entries and create MRP area as below.

After maintenance of MRP area click on double click on Subcontractor (one entry per MRP area) and maintain the vendor details as below.

Components Planning with Subcontracting Process

Master Data MRP Area

MRP area called SUB_001 available to plan separately associated components. SAP suggested maintaining the MRP area parameters to all components which are planned under the MRP area in MRP 1 view (Material R-100-101).

Click on MRP areas and maintain the MRP parameters as like plant parameters.

It is important to maintain MRP 2 special procurement to 45 – Stock transfer from plant to MRP area.

Make a note that you need to adopt data while entering MRP area parameters and save material.

Subcontracting Process Execution

Demand Flow

Forecast updated for subcontracting header material called F-100-101.

MRP Live

After forecast updated runs MRP live.

Based on MRP live log total of 4 materials planned 1 material with classic MRP and another 3 with MRP on HANA.

Analyzing MRP results

After MRP run completed purchase requisitions created for header article based on planning horizon.

Now go to component R-100-101 and analyze the result at a plant level and MRP area level.
Plant level – Stock transfer reservations from the plant to the provision stock of the subcontractor.

MRP area level – Procure the components that you provide to a subcontractor for the production of an assembly, by transferring stock from a plant to the MRP area of the subcontractor.

Mass maintenance

Mass processing reports RMMDDIBE and RMMDDIBE02 can be used for maintenance of MRP areas.

Additional references:

https://launchpad.support.sap.com/#/notes/2586059
https://launchpad.support.sap.com/#/notes/2227532
https://launchpad.support.sap.com/#/notes/2268044
https://launchpad.support.sap.com/#/notes/2516504
https://help.sap.com/viewer/fe39e10a9a864a8f8dc9537704f0fa13/1709%20000/en-US/60adce5314894208e10000000a174cb4.html
https://blogs.sap.com/2017/10/19/5-reasons-to-use-subcontracting-mrp-areas-in-s4hana./
Best Regards,
Lingaiah

Source: https://blogs.sap.com/2019/03/19/s4hana-subcontracting-with-mrp-area/

terça-feira, 19 de março de 2019

SAP S/4HANA Coding block and extension to Fiori

Hello all,
I am writing this blog about coding block in S/4HANA Finance and how we can extend it to Fiori and other reporting tool provided by standard SAP.
What is coding block
SAP allows to have additional dimensions to be captured for the financial posting. This will allow business to add reporting dimensions needed which cannot be catered by say existing fields ( e.g. profit center , text , assignment etc.).
Example can be Depot number for a downstream O&G business or Maturity date for a trading business.
Capturing this data as level of journal allows Finance team to perform analysis and downstream activities ( consolidation etc.)
How do we set it up
Enabling Coding block is not changed ( in term of configuration node) from SAP ECC,
The node is present in Customer fields and under edit coding block.

Once created the field is updated in ACDOCA & BSEG along with COBL structure which is referenced by multiple views ( reporting) and structures & tables ( e.g. MSEG)
I will not go deep in the steps as it is pretty much the same as it was years ago.
Enabling for Fiori reporting ( for Coding block fields)
This is part which is quite interesting as you can use standard features provided by SAP and enable reporting on the coding block fields.
SAP provides an extensibility feature ( read this below blog from Ulrike -https://blogs.sap.com/2017/01/20/sap-s4hana-extensibility-tutorial/).
This can be used for coding block too and then enable reporting tiles
e.g. G/L Line item reporting view:-

Or Trial balance tile:-

Steps to be followed
The below items assumes that the coding block field is defined and field is available in ACDOCA.
Steps 1- Run SCFD_EUI to enable fields for custom fields and logic.In this step you can select the field and enable it.

Once you execute the program you can select the field and enable the field.

Enabling for one structure will enable the coding block field for other structures
2) Enable the field in Fiori tiles- You will need Fiori basis role for below task.
The two key tiles needed are shown below:-

2.1) Register field for transport- As shown below, you will have a transport linked to your coding block field.

2.2) Custom field and logic- In this tile select the field and enable for different Fiori apps.
As shown below, you will see the list of the available coding block fields and you have option to publish the field.

Once you publish you will also have option to enable the field for the reporting tile.
So as shown below we have option to enable the coding block field on the Fiori tile e.g. Clear Gl account etc.

This way you can help your client and business counterpart to use the additional dimensions provided in SAP and avoid performing any custom developments or reports.
This also helps use the existing Fiori tiles in optimal manner and ease the reporting needs.
I would like to thank Adam Gilbert who showed us how the above steps are done.
I hope you find this blog useful and help your clients in optimizing their financial system on S/4HANA.
Regards
Rishab Bucha

Source: https://blogs.sap.com/2019/03/17/sap-s4hana-coding-block-and-extension-to-fiori/?