SAP S/4HANA Training - in Plain English

Identify your S/4HANA system by checking system status to confirm a HANA database, then view the product version and service pack level, and verify on premise installation.

Perform a hands-on sales order in SAP S/4HANA using look-ahead and type-ahead, and learn that index tables are now on-the-fly views via core data services, with Fiori UI.

Explore SAP S/4HANA's next generation browser-based UI, Fiori, with a focus on theory, architecture, and a library of 7000 standard apps including sales order, purchase order, and master data creation.

Learn how the SAP Fiori UI5 framework delivers a responsive, form factor agnostic, role-based interface that adapts purchase order workflows across desktop, tablet, and mobile browsers.

Discover how role-based apps in SAP S/4HANA show only the data needed to manage sales orders, enabling delivery blocks and status checks with fewer steps.

demonstrates how SAP UI5, an open-source web technology based on HTML, JS, and CSS, enables consistent, web-based interfaces across purchase and sales orders for S/4HANA apps.

Trace the evolution of SAP S/4HANA from R2 on mainframe to R3 on a client-server platform, then to HANA, with simple finance and simple logistics and rapid 2015–2016 releases.

Explore the challenge of migrating millions of lines of legacy ERP code to the HANA in-memory database, using views to retrofit aggregates and maintain performance during the transition.

Anticipate the future of SAP S/4HANA by examining how ongoing simplification models and the new database model will replace aggregates and indices, focusing on immediate impact like rebates.

Discover how SAP S/4HANA uses simplification lists to identify delta functionality, distinguishing mandatory changes from optional ones while keeping 90% of existing processes intact.

Explore how SAP S/4HANA unifies customers and vendors under the business partner concept, highlighting master data structure, data views, and the shift from old transactions to BP.

Develop hands-on skills in creating and extending an SAP S/4HANA business partner into customers and vendors, including search criteria, roles, and sales, finance, and purchasing views.

Explore how the SAP S/4HANA business partner acts as a shell for customer and vendor data, storing general data in BP 000 and extending with finance and purchasing views.

Explore why SAP S/4HANA adopts a business partner model to unify customer and vendor master data, improving integration with CRM, SRM, and other modules while preserving compatibility with existing code.

Configure BP grouping in SAP S/4HANA by defining BP groupings, number ranges (internal or external), and default groupings to control BP creation and synchronization with customer and vendor masters.

Define the BP category in SAP S/4HANA by choosing between person, org, or group, then configure marital status and occupations for B2B and B2C scenarios.

Apply a status profile to a business partner to manage onboarding, training, and order access through defined statuses such as onboarded, portal access granted, buyer profile generated, and training complete.

Map BP groupings to customer account groups to auto-create a BP when you create a customer and synchronize BP and customer number ranges for compatibility.

Extend material master by increasing the material number to 40 characters, removing foreign trade data, introducing a new service material type, and enabling 40-character length via extension fields for interfaces.

Credit management moves from the SD core to a standalone financial supply chain management module, with GTS as an independent system in the Hana-enabled landscape.

Explore how FSM introduces credit segments that replace the traditional credit control area and roll up local company code limits into a global segment.

Understand SAP S/4HANA FSCM credit management, no longer in enterprise structure, with main and sub credit segments, defined in the business partner view via ukm0001 to set per-segment limits.

Integrate external credit agencies via an xml based interface to automatically calculate risk categories and credit limits using a formula editor and enable dynamic credit management.

Explore credit management improvements: shift to credit segments from credit control areas, automate risk scoring with formulas, and integrate external ratings, pi, and workflow for better credit management.

Examine how output determination uses the condition technique to map invoice document types to output types like print, EDI, fax, and email.

Explore how SAP S/4HANA replaces output determination condition technique with BRFPlus, a flexible business rules framework that lets non-technical users configure rules for various processes, not just outputs.

Explore BRF+ first look: open BRF+ transaction, view output determination configurations for billing, delivery, and orders, and import XML to reveal the config as data objects, expressions, functions, and rules.

Explore BRFPlus, a visual no-code rules engine for if-then-else logic, used by functional consultants to configure rules and support output determination with condition records.

Explore output determination master data in SAP S/4HANA, compare traditional condition technique with b plus, and learn how rules determine output type, receiver, channel, and dispatch timing.

Select the document category and perform output type determination, then define a descriptive output type using billing type, sales org, and customer group, with a set dispatch time.

Explore how BRF+ enhances output determination in SAP S/4HANA by replacing the rigid standard condition technique with flexible, customer-driven rules that handle language forms, multiple ship-to and dealer scenarios.

Explore SAP S/4HANA output determination with the Braf Plus rules engine, comparing it to condition technique, and learn how receivers, channels, and dispatch options are configured without coding.

Pricing delta changes in SAP S/4HANA introduce four updates: conv replaced by PRCD_elements, three-digit counters, two-digit document/customer pricing procedures, and PRC_migration_post_processing after ECC migration.