Material Ledger is mandatory in SAP S/4HANA. What do you need to know?

                             

Switching on the material ledger (ML) is mandatory in SAP S/4HANA as stated in the simplification list of release 1511 and is embedded in the product. This allows you to leverage the existing functionality of the ML to create a sub-ledger including multiple currencies and valuations for more granular detail on inventory transactions. NOT mandatory is the activation of actual costing functionality.
SAP Enterprise Support Academy will release two webinars in May to support you in activating the ML.

1. The first meet-the-expert (MTE) session covers material ledger deployment – for customers NOT using actual costing. If you have never used ML before, or already have data processes in place in maintaining your inventory valuation tables, this session will explain how ML works in SAP S/4HANA, and what has to be taken care of during system conversion or a new implementation, as well as the benefits ML will deliver.
2. The second MTE session is geared towards those of you who use ML today and are reporting your companys inventory and cost of sales at actual cost. You will see what has changed in SAP S/4HANA with respect to actual costing and what has to be taken care of during system conversion.

Before you can access the registration links, a one-time registration in SAP Learning Hub, edition for SAP Enterprise Support, is required. A detailed step-by step guide to registration can be found here.
Registration is open for the MTE sessions (recordings will be made available via the same links).

• SAP S/4HANA Material Ledger Without Actual Costing  | May 16, 2019 12:00 PM CET/Berlin
• SAP S/4HANA Material Ledger With Actual Costing | May 23, 2019 12:00 PM CET/New York

For more reading, please see the following two-part blog providing further insights on:
Why ML is mandatory in SAP S/4HANA
Use cases & scenarios in ML valuations

SAP S/4HANA Fully-Activated Appliance: Demo Guides

3 Likes 76 Views 0 Comments

This blog gives information on the pre-configured sample demo scenarios in the SAP S/4HANA Fully-Activated Appliance.
If you stumbled across this blog “by accident” and are still interested, please see this overview for the SAP S/4HANA Fully-Activated Appliance.
And here’s the direct link nin SAP CAL to the latest appliance release that fits to the demo guides below (SAP S/4HANA 1809 FPS01 Fully-Activated Appliance).

Table of content

A) Demo guides (valid for the SAP S/4HANA 1809 FPS01 Fully-Activated Appliance)
B) General remarks on the demo guides (scope, support, ….)
C) Post-deployment steps
D) System log-on
E) Archive: Demo guides for earlier appliance releases

A) Demo guides

Below are links to the pre-configured demo guides.
They are valid for the SAP S/4HANA 1809 FPS01 Fully-Activated Appliance (demo guides for older appliance releases can be found at the end of this blog).
Important:
Before you start with these guides , please be sure to read sections B), C) and D) below at least once to prepare your system in the best way.

1. Overview pages for Sales / Finance / Procurement
2. Sell from Stock with Outbound Delivery Processing
3. Warehouse Inbound Processing from Supplier
4. Plan to Produce using Advanced Planning for Capacity Utilization
5. Accounting, Financial Close & Closing Cockpit
6. Lease-In Accounting
7. Investments
8. Data Migration
9. Extensibility (Fiori custom fields & applications)
10. Print Form Customization
11. SAP Screen Personas
12. Working with predictive applications and models
13. Customer Management
14. Transportation Management
15. Portfolio & Project Management
16. Master Data Governance, MDG (separate blog with multiple scenarios)
17. Demand-driven replenishment
18. SAP BusinessObjects BI Platform & SAP Analytics Cloud Platform (coming soon)

B) General remarks

What does pre-configured demo scenarios mean ?

The appliance is largely based on the fully-activated scope of SAP Best Practices.
SAP Best Practices provide a suggested pre-configuration for a large variety of business processes so that these processes can be executed “out-of-the-box” in the prescribed way (see https://rapid.sap.com/bp/#//BP_OP_ENTPR for details) .
In addition, some further capabilities that are not covered by the SAP Best Practices have been pre-configured in the appliance (such as Master Data Mgmt., Customer Management, Portfolio Mgmt., etc.).
The demo guides take you on a “guided tour” through some of the pre-configured areas but your are also free to step away from these tours.
However, if you explore additional features of the SAP S/4HANA system beyond what is provided in the demo guides (or the more comprehensive test scripts of SAP Best Practices, see link above), you might find functions or processes that are not pre-configured and, hence, will not provide a meaningful system response. In this case, you need to configure those scenarios or functions using SAP standard procedures (e.g. via transaction SPRO) to make them work.
You might also find errors and bugs as you explore the appliance. In this case, please search for SAP Notes and corrections and decide if you want to apply them. The system behaves like a regular customer system once you have your own instance and will NOT be updated automatically by SAP i.e. you will need to implement these fixes in your system.

Where to get support ?

If you are using the appliance as part of a 30-day trial (the default if you don’t close any contract with SAP), support is offered via the SAP Community (https://answers.sap.com/questions/metadata/24005/sap-cloud-appliance-library.html). There, SAP employees, customers and partners will do their best to help you, however, there is no guaranteed service level agreement attached to it.
For support of appliances within the SAP CAL subscription license (i.e. appliances that are running longer than 30 days), please report an incident on components BC-VCM-CAL (for SAP CAL & connectivity issues) or the respective functional components (e.g. FI-* or LO-*).

Master data structure in the appliance

The SAP Best Practices customizing and sample master data have been activated in client 100 of your SAP S/4HANA system. Typically, the demos flows use the company code 1710 (US-based) since only this contains transactional data for the demo scenarios.

Initial system performance

When you access the system for the very first time, you will need to wait some time (can be as much as a few minutes) until the Fiori Launchpad or the SAP GUI show up. Using system functions such as the Create Sales Order Fiori tile for the first time will be significantly slower.
This is a normal behavior since the system needs to cache certain areas for first use after startup. The performance will improve significantly if you continue working with the system (note to administrators: SGEN has been performed).
Also, if the system has been re-activated after a “Suspend” period in SAP CAL , the system response will be slower during the first clicks on applications.

Browser messages about certificates & pop-ups

When accessing the Fiori Launchpad for the first time, you will be prompted about missing / unsigned certificates that might be rated as a security thread (exact message depends on the browser version). This behavior happens since the appliance doesn’t contain signed root CA certificates for the connection between browser and backend.
Please ‘ignore’ these messages and add the Fiori Launchpad URL to the list of secure sites in your browser.
Also, some of the Fiori apps will open in a separate browser tab/window. If you have a pop-up blocker activated, please confirm that you always would like to open pop-ups from vhcals4hcs.dummy.nodomain.

C) Post-deployment steps & system log-on

When you start an instance for the very first time, certain time-based settings are still at the date when the appliance was assembled for shipment. For the appliance to fully work, you should adapt these settings to the actual date when you use the appliance.
Below you can find a list of the most important settings to change, but depending on how you use the appliance, you might need to touch further areas.

Open Inventory Management Period

To post any goods movements (goods receipts for procurement or goods issues for outbound processing), the inventory posting period must be the same as the goods movement date.
When you start an instance for the very first time, the open period is 03/2019 (i.e. March 2019). If you want to post goods receipts or goods issues with the current period (e.g. August 2019), you must first close all previous periods and open the period for the current date. This action must be performed sequentially and only once for each month.
The procedure below uses SAP GUI (TCode MMPV) but you can also use the Fiori Launchpad (user S4H_MM_DEM, tile Close Periods). If you are using the system for a longer period, you might also consider creating a scheduled job that  automatically adapts the MM period each month.

What to do	What you will see
Log on to SAP GUI (see below if you don’t know how to do this). Enter tCode MMPV Enter these values at the first run From company code: 1710 To company code: 1710 Next period: 04 Fiscal year: 2019 Check and close period:X Click Execute. Repeat for all periods until you have reached the current month.	Right-click and open in separate tab to enlarge

D) Log-on to the system

To logon, open the Fiori Launchpad via the following link after completing the steps below; https://vhcals4hcs.dummy.nodomain:44301/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html
IMPORTANT:
The URL above uses the system alias vhcals4hcs. To make this link work on your local computer, you need to maintain your local Windows ‘hosts’ file.
If you access the trial via the included remote desktop of the appliance, these settings have been maintained already on the remote desktop.
Both methods as well as the access via SAP Logon are described in detail in the Step-by-Step Quick Start Guide on https://go.sap.com/cmp/oth/crm-s4hana/s4hana-on-premise.html.

E) Archive: Demo guides for earlier releases of the fully-activated appliance

1809 (SP00): Demo Guide /  Quick Start Guide
1709 FPS01: Demo Guide / Quick Start Guide
1709 (SP00): Demo Guide  /  Quick Start Guide
1610 (SP00): Demo Guide  /   Quick Start Guide


Source: https://blogs.sap.com/2019/04/23/sap-s4hana-fully-activated-appliance-demo-guides/

How to install a FIORI app

Info
This guide will focus on the installation of a ‘Create Sales Orders’ Transactional Fiori App in an ABAP environment on ERP 6.0 EHP 7 running embedded Gateway using transaction SAINT. There are also other ways to install the apps with SAP Maintenance Planner not described here.

Prerequisites
Make sure you have installed and configured the Gateway and all necessary SAPUI5 components.

Business Scenario
You have been asked to simplify the user experience at your company to save up on training for new and existing employees for Field Sales Representatives. You have heard of FIORI but are not sure how to start.

Step 1 – Find a FIORI app to simplify Sales Orders creation
Access the following link: https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/ and search for ‘Create Sales Orders’ app.
The above website should be the main starting point when implementing a FIORI app. It describes the app features, installation information, configuration as well as extension points which tell you what features of the standard app can be enhanced. If you can’t find a relevant FIORI app, you may consider creating a custom one.
Once you have found the required app, you may want to check the database it runs on as well as the prerequisites for installation:

‘Any DB’ means we don’t need the HANA database. If the above says ‘HANA’ then we either need SAP Business Suite on HANA or S/4 Hana in order to install and run the app.

Step 2 – Deploy the Front-End Components
a)    Download the Front-End component files
From the FIORI catalogue identify the front ends components to be installed (Implementation Information/Installation/Front-End Components):

Download the above component from: https://launchpad.support.sap.com/#/softwarecenter
Along with all the corresponding support packages 0001-0010
Example:

b)    Install the files
Log in to client 000 of your system.
Run transaction SAINT.   
Install the downloaded UI components.
c)    Activate the SICF for App URL
Identify name of the app from the Fiori apps library (Implementation Information/Configuration/SAPUI5 Application)

Run transaction SICF and use the following path: default_host -> sap -> bc -> UI5_UI5 -> sap -> sd_so_cre

You can see that the service is grey which means inactive. Right click it and activate.

Step 3 – Deploy the Back-End Components
a)    Download the Back-End components files
From the FIORI apps catalogue identify the front ends components to be installed (Implementation Information/Installation/Back-End Components):

Download the above component from: https://launchpad.support.sap.com/#/softwarecenter

Along with the support packages 0001 – 0008

 b)    Install the files
Log in to client 000 of your system.
Run transaction SAINT.
Install the downloaded Back-End components.
c)    Activate the OData service
 Identify the name of the OData Service from the Fiori apps catalogue (Implementation Information/Configuration/OData Services)

Run transaction /IWFND/MAINT_SERVICE and click ‘Add Service’:

Choose the System Alias and Technical Service Name:

Select the displayed Backend Service and click on ‘Add Selected Services’: 

You will get an ‘Add Service’ pop up. Assign a package (I am using a local object for test purposes – in real scenario create a package)

And press continue.
The OData service should now be visible in the Service Catalog of transaction /IWFND/MAINT_SERVICE

Step 4 – Authorizations
SAP provides you with role templates once you install the relevant app components. You can either use the existing components or take a Z copy of the template. It is up to your authorization team and should be adapted to your authorization concept.
Since I am using embedded Gateway the following steps may differ if using Gateway Central Hub Deployment where you need to take care of authorizations both on the ECC side and the Gateway side.

a) Create PFCG role with Launchpad Start Authorization

Copy role SAP_UI2_USER_700 under the Z namespace e.g. Z_UI_USER
Click on the ‘Menu’ tab and add ‘Authorization Default’

Add IWSG authorizations for: ZINTEROP_0001 and ZPAGE_BUILDER_PERS_0001

Go to tab ‘Authorizations’ click on ‘Change Authorization Data’

Click:

Add the following authorization objects:

Make sure the traffic lights are green by clicking on them:

Generate the authorization profile and save it.

Assign the authorization role to the user in the ‘User’ tab and click on ‘User Comparison’


b) Create PFCG Role for Launchpad Catalogues and Groups
Find the business role template in the FIORI apps library documentation for our SD app.

Go to transaction PFCG and copy it into the Z namespace e.g. ZSAP_SD_BCR_FIELDSALESREP_X1
In our new role we can see that the following elements have been copied:

Which gives users access to the tile catalogue and tile group in the FIORI Launchpad.
Generate a profile and assign to the user just like in step a)
c) Create PFCG role to access oData services
Copy roles SAP_SD_SO_CRE_APP under Z namespace e.g. ZSAP_SD_SO_CRE_APP
Add IWSG authorizations for: ZSRA017_SALESORDER_CREATE_SRV_0001
Go to the ‘Menu’ tab and click on add ‘Authorization Default’

Enter the following details:

Save the role menu and you should now see the following:

Generate the profile and assign to the user just like in step a)
Note: In backend the user must have authorization to RFC trusted connection if you have a central hub gateway.
To check for authorisation issues to the backend use transaction: IWFND/ERROR_LOG

Step 5 – Test the app
The natural environment as an entry point for FIORI apps is the FIORI Launchpad which is a container for all your FIORI apps and it should be used in the production environment. After the installation you may want to test if the app is working correctly and test it in the standalone mode.
In order to run the app in a standalone mode you need to use the following link format:

http://<server>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<client>#Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=<ComponentName>&sap-ushell-url=<Encoded-URL>&<AdditionalApplicationParameterKey>=<AdditionalApplicationParameterValue>

Server and port
This is your server name and port your app will be running on
Component Name
To get the Component name run the following link: http://<server>:<port>/sap/bc/ui5_ui5/sap/sd_so_cre/Component.js
And get the component name:
        
Shell url
This is the URL pointing to the app resource file location on the server: /sap/bc/ui5_ui5/sap/sd_so_cre
The full link will look as follows:
http://server_name:8000/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=060#Shell-runStandaloneApp?sap-ushell-SAPUI5.Component=cus.sd.salesorder.create&sap-ushell-url=/sap/bc/ui5_ui5/sap/sd_so_cre
You should now be able to test your app in the standalone mode. The configuration of the Fiori Launchpad will be described in my next blog.


Source: https://blogs.sap.com/2016/09/27/how-to-install-a-fiori-app/

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/

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/?