SAP S/4HANA

Ace your homework & exams now with Quizwiz!

existing sap suite to s/4 hana

update to sap netweaver (abap) migrate database to sap hana --> convert existing erp system into s/4 hana - convert ecc onto s/4 hana on-premise edition

Building blocks

will have overlaps and be codependent detailed documentation of config settings

how do you develop and test

work further on q system and continue to work from q to p it is possible to build another q system to run simultaneously

new implementation of SAP from legacy system

- Install SAP Net weaver application server ABAP 7.5 - install sap s/4 hana system -deploy sap best practices - Migrate data to s/4 hana - Move to cloud edition

Why would I need public cloud

- get updated business innovations on a quarterly basis - pre-config best practices loaded on. -in-app extensibility- allows for the plugging in of solution products - avaialble in 13 countries and 10 languages - guided config by SAP and lifecycle management.

Scenario 2 sap system --> Sap s/4 hana (on premise or cloud)

1) All in ONE step (rapid database migration) Install s/4 hana software netweaver 7.5 abap (SWPM software provisioning manager)/ database change to s/4 hana and application transition (data migration) 2) no transition to cloud TOOL: software update manager (instead of cockpit) and database migration option (DMO).

Scenario 1 implementation legacy --> s/4 hana (on premise)

1) Install s/4 hana software netweaver 7.5 abap (SWPM software provisioning manager) 2)s/4 hana config with sap best practices 3) data migration tools: cockpit/lsmw (legacy software migration workbench)/sap data services

What does SAP s/4 hana do that's different from before

1) It is a business application suite designed to support all core ERP functionality 2) was designed to run exclusively on SAP HANA Cloud platform or SAP HANA one database

prepare for scenario 2 (analysis)

1) determine all related add-ons, scan information and determine industry and custom packages associated with that. 2) Analyze and map -check custom code to see it it will work on new system. 3) Unicode conversion 4) CVI (customer-vendor integration) 4) test and production (sandbox migration - proof of concept)

On-premise systems --> s/4 hana

1) prepare system (unicode conversion must be done) 2)customer code 3)data footprint 4)upgrade step 5)over system 6)introduce new s/4Hana features 7)

what do you have in s/4 hana abap

3 components: transactional logic, analytics, enterprise (search)

cloud marketing edition 2

6 business scenarios

cloud marketing edition 3 ( bus scenarios)

7 business scenarios 1) Consumer and Customer profiling 2) segmentation and campaign manag 3) commerce marketing 4) marketing resource managm 5) Marketing analytics 6) Marketing lead managm 7)** Loyalty management** - specific product on hybris via YAS market.

cloud system vs r/3

Cloud system is a two tiered system (starter system/ q system / psystem) cannot maintain more than 2 at any point

Cloud Edition vs Hybrid Scenarios

Hybrid Scenario- allows business to have more flexibility and more manual changes and need to be on-premise. Cloud edition- out of the box best business practices, simplifies business need to make updates. Configuration is not typically allowed. Access to IMG config functions is limited. Cloud customers do not have access to IMG in cloud edition.

S/4 hana deployment options

On premise- customizing features and functions available. Major logisitics and finance innovations. Feature functions are similar to ECC except it's on HANA and user experience is better On cloud- (2 options: private or public) private - config options, preconfig options (standardized by industry). Public - 3 packages to purchase (enterprise management/professional services/marketing)

deploy

P system (production)_

realize

Q system

explore

Q system (quality and testing system)

WHAT IS THE DIFFERENCE BETWEEN SAP HANA ONE AND SAP HANA

SAP HANA ONE is a variant of HANA cloud program designed to use less memory

semantic adoption

adapt custom code to comply with new s/4 hana functionality - adapt integration if applicable - rollout (implement)

Timeline of SAP software as a service innovation

SAP R/3 (1992) --> SAP HANA (2010) --> SAP HANA cloud platform; SAP HANA ONE (2012) --> SAP HANA ENTERPRISE CLOUD (2013) (managed private cloud) --> SAP s/4 HANA (2015)

What functionalities do you have in fiori shells

Sap screen personas (user screens), fiori apps, fiori launchpad (homepage), search.

prepare

Starter system ( use up to realize)

Finance Core

Suite spot service industries, companies looking to revise fnance system,

core finance

accounting, cost managment, fiancial risk managem, receivable managem

Starter systems

activities of service center service lead integration of SAP

change managment service

alerts security patching

preparation on start release

analysis of used business processes --> mapping to sap s/4 hana innovations --> identify required integration of target state --> run pre-transformation checks on source system --> mandatory preparation steps to be executed on source system

guided config

assistance with determin of best practices.

SSC UI

available to cloud and on-premise customer

s/4 hana marketing cloud Value proposition

brings a range of different predictive and agile analytics (loyalty, market data and events, sales and service date, financial data, industry data, social media, extensions.)

SAP expert config

carried out by SAP service center

content lifecycle

configured by project team tech project lead configs realize --> deploy (any starter system data transfers from starter system to q system)

Migrate/integration happens during realize phase

content config. of new data using standard sap solutions -Q system - Starter system Key UIs further ssc ui services not included w/o charge further config will be charged to add on (as needed)

SAP notes

content library and master material overview

professional services

contract to cash, project manag, time and expense

in-app extensibility

custom extensibility and changes within app

KEy user extensibility

custom fields and tables, change business rules (cloud ABAP web editor) q

enterprise tech

data migration

What do you have in sap hana

database full of tables

Move to DEV (realize phase/ development Q)

delta customizing, custom code adjustment

Analysis of custom process

determine if it will work on new system

Architecture for cloud marketing ed 3

ease of integration, predefined best practices and solutions, no need to extract data - run scores,

hr connectivity

employee central connectivity

professional service cloud

end-end project base system, integration of multiple processing, accounting, financial

business suite and non-sap to SAP s/4 hana

erp (with different start releases)

cloud-updates

every quarter

on-premise updates

every year

Additional config

expert support from SAP config help

onboarding material

guided tours for end users WPB (work performance builder tools) simulation of how to use applications. (theoretical

the tool for migration

implementation cockpit

technical implementation

install of sap s/4 hana (database and s/4 hana suite)

side by side extensibility

integrate with other cloud functions. use a full fledged development platform to build ext. applic)

professional service procedures

integration of sales orders (time expenses/ fixed price/ or combo) procurement --> new po Supplier invoice--> makes issuing invoices easier inter company invoice--> recording and managm of all business processes

SAp activate methodology

jam

s/4 hana

just 2 systems with the landscape instead of multiple

LOB

line of business (

Best practices

made from scope items "end to end processes" building blocks. Business processes to use.

SAP s/4 hanna marketing cloud

merge, trigger email camaigns

SAP Activate steps

methodology tool with several phases. PROJECT LIFE CYCLE: Discover (existing solutions)-- prepare (how many plants you need)-- explore FIT GAP based on model/company-- realize scope and config-- deploy (onboard and deploy) --> Operate, monitor, and support.

any erp (SAP system) 0-6 can move to sap s-4 hana on-premise

migration can be facilitated at any time (using implementation and migration packages)

Guided data migragtion

migration objects and templates to load data available

Professional service industry benefits

mobile service contract to cash, project management,

s/4 hana architecture

much more simplified. 3 layers SAP Hana --> s/4 hana abap -- Fiori shell

s/4 hana cloud advantages

no customization avaiable with cloud - fast innovation (updates every quarter). flexible platforms. Native integration - all sap products now function as features as solutions in the new cloud system. Effective governance helps in step by step process for projects.

database migration

one database to another and downtime must be managed testing must occur after the migration if done at the same time as the enhancement upload decreases testing time 6months (however sap has made the migration successfully in 55 days for simple finance)

s/4 hana cloud different implentations

one package for all different industries (standardized business process). Bugs are handled by SAP and updated on a quarterly basis. 2-25 week implementation timeframe. (much shorter than the past). Only one test tenant avaialble. Self project manangement- data migration tools are available/ testing and change management. SAP will provide tech support. (consultant- client relationship is no longer necessary, as SAP steps in to solve problems.

run phase

operational monitor and support change managment (total atuomated support system/ thresholds to send alerts) security back-up and monitor

order to cash

order and contract, inv managment, accounts receivable

what is plan to product

planning, processing, inventory management, maintanance manage

Starter system

preconfigured best practices

stages from on premise --> s/4 hana

preparation--> tech installation--> semantical adoption --> Cloud adoption

conversion data (migration/transfer/ change to s/4 H)

prepare/explore -- realize -- deploy

What is the difference between on-premise and cloud

private - dedicated by one customer (on-or off premise)

end to end processes of SAP s/4 hana

procure to pay - plan to produce - order to cash --core finance - HR

enterprise cloud

project

Content lifecyccle managment

protects against unwanted changes

Prepare phase

provisioning project set-up doc repository

Enterprise management functions (public cloud options vs on premise)

public - no config allowed, and single subscription contract, web-based, support comes from SAP,

What is the difference between public vs hybrid vs public

public cloud- not on the premise of the customer but the database of the cloud. Serves many tenants Private cloud- managed by company or third party. Goes through VPN. Hybrid- handled by cloud product and on-premise (not on website).

Embedded test tool

reduced extra efforts to test adaptations to test project. support provided by SAP for testing (one version) automated test runs changeable templates

Enhancement packages (release changes)

require less work packages are downloaded and tested

what came before sap s/4 hana marketing cloud and what does it do

sap hybris marketing solution --> product name for on-premise and the private cloud solutions where sap s/4 hana is public and on premise

SLT

sap landscape transformation

how to manage your solutions (spro/IMG/config)

scope summary including: functional scope of

How did SAP Hana start as and how did it get to where it is now?

simplified data model, new user experience, advanced processing, choice deployment. (In memory platform) .

start s/hana (role based learning)

step by step explanations

sap activate methodology

steps to get certification in SAP act100, act200 --> certification exam SAP activate associate C_act_2016

wrench tool

sum (software update manager) with DMO (Data migration option)

what is within procure to pay?

supplier , sourcing and contract managem, operational purchasing, inventory managem, invoice and payables

Cloud Transition scenarios (non-cloud --> to cloud)

system conversion (big company on old ERP system to On- premise)

data migration to s/4 hana

template based approach for non-sap customers or use sap business suite (r/3)

fit to standard workshop

test scripts and process diagrams on the best practices (in starter system to see if it fits your requirements).

data implementation cockpit

tool to migrate data to new system (old r/3 system) -based on scope items (bus scenarios) data migration objects are propsed -

Q - p system

transport system is done expert config is done SSCUI upgrades do not effect determinations functionality checks may be necessary Boundary situations:

discover

trial system (2 week)


Related study sets

Management Information Systems- Ch 1

View Set

CFA Level I - Quantitative Methods- Reading 6 Hypothesis Testing

View Set

Chapter 12 Section 1 Social Studies

View Set

College History Final Review Questions

View Set