Agenda

1.S/4 HANA Logistics Simplification items.

2.Business partner Introduction & Architecture.
3.FSCM Credit management.
4.Trade Finance Integrates with S/4HANA Sales(Documentary payments LC/BG).
5.Settlement management
6.Pricing Data model changes.
7.Field Length Extension & Elimination of Redundancies.
8.MRP Run
9.Conversion Activites for Logistics (Pre & Post).
10.Simplification item checks
 2

Simple Logistics | S/4 HANA Simplification items

ECC S/4HANA
Customer/ Vendor Business Partner

FIN-FSCM-CR SAP Credit Management

FI-AR-CR Credit Management
GTS
Foreign trade/Customs
Settlement Management

Rebates Documentary Payment through Trade

Finance- Treasury

Documentary Payment (L/C, BG) New MRP Run

Pricing Data Model with new features

MRP

Field lengths are extended

Elimination of unnecessary Tables

Business Partner| Introduction
• A Business Partner can be a person, organization, group of individuals, or a group of
organizations, in which a company has a business interest. Business Partner is the single
point of entry to create, edit, and display the master data for business partners, customers
and vendors. A Business Partner consists of general data like name, address, bank
information, etc. as well as role specific information i.e. customer/vendor/employee data.

=
 Business Partner| Business Partner Category

Person Organization Group

Business Partner| Master Data Views in ECC
Customer Master Data Vendor Master Data

General Data • Name, Address, Postal Code,… General Data • Name, Address, Postal Code,…

Company Code • Finance related Data such as

• Finance related Data such as
Company code
Data Recon account, Payment Term,…. Recon account, Payment
Data
Term,….

• Sales related data such as

Sales Area Data Shipping details, Sales district, Purchasing Data • Purchasing related information
Pricing, Partner Function,….
Business Partner Roles (T- code: BP )
General Data
View
000000
Contact Company
Person View Code View
BUP001 FLCU00

Counter Part
Sales View
View
FLCU01
TR0151

Credit BUSINESS PARTNER

Company
Management
Code View
View
FLVN00
UKM000 Purchasing
View
FLVN01
Simple Logistics | Business Partner complex interface `
 Simple Logistics | Business partner linking
ECC Synchronization Process S/4HANA 1809

Vendor
CVI_VEND_LINK CVI_VEND_LINK

LFA1 GUID
BUT000 BUT000 GUID LFA1

CVI_VEND_CT_LINK CVI_VEND_CT_LINK
Vendor Contact Person

Customer CVI_CUST_LINK CVI_CUST_LINK

GUID BUT000 BUT000 GUID KNA1

KNA1

CVI_CUST_CT_LINK CVI_CUST_CT_LINK
Customer Contact Person

Note:
• Link tables will be updated during synchronization process and also while creation of new business partner in S/4HANA1809.
• GUID “Globally Unique Identifiers” is linking the link tables to business partner tables
Absolute T codes List
The following SAP Business Suite transactions are no longer available or redirect to transaction BP:
1. FD01, FD02, FD03, FD05, FD06, FD08 (Create, Change, Display, Block, Deletion mark, Confirm Customer
(Accounting))
2. FK01, FK02, FK03, FK05, FK06, FK08 (Create, Change, Display, Block, Deletion mark, Confirm Vendor
(Accounting))
3. MAP1, MAP2, MAP3 (Create, Change, Display Contact Person)
4. MK01, MK02, MK03, MK05, MK06, MK12, MK18, MK19 (Create, Change, Display, Block, Deletion mark
Vendor (Purchasing))
5. V-03, V-04, V-05, V-06, V-07, V-08, V-09, V-11, V+21, V+22, V+23 (Create invoice recipient, payer, consignee,
one time Customer, ordering party, carrier, sales prospect, competitor, Business Partner (Sales/Centrally))
6. VAP1, VAP2, VAP3 (Create, Change, Display Contact Person)
7. VD01, VD02, VD03, VD05, VD06 (Create, Change, Display, Block, Deletion mark Customer (Sales))
8. XD01, XD02, XD03, XD05, XD06, XD07 (Customer: Create, Change, Display, Block, Deletion mark, Change
Account Group (Centrally))
9. XK01, XK02, XK03, XK05, XK06, XK07 (Vendor: Create, Change, Display, Block, Deletion mark, Change
Account Group (Centrally))
• FSCM-Credit Management
•
Introduction - SAP Credit
Management
 Credit management comes in the
initial stage of OTC Cycles. Before
approving the order and issuing
the invoice, credit worthiness is
assessed to avoid non payment.
 FI-AR-CR Credit Management is
not available in SAP S/4HANA, on
premise edition .
 It has been replaced by SAP Credit
Management (FIN-FSCM-CR) for
Financials and Sales and
Distribution (SD).
Simple Logistics | FSCM Credit Management
SAP Credit Management has now been simplified in SAP S/4HANA as follows:
• All IMG activities for SAP Credit Management are listed in Customizing under the following path:
Financial Supply Chain Management-Credit Management.
• Create credit segment out of Credit Control area.
• The credit limit check for sales document types can only be specified as type D( Automatic credit check) in SAP Credit Management or
can be left empty (no credit limit check). The credit limit check types A, B and C are no longer available.
• The credit check when changing critical fields has been removed from the SD side.
• The payment guarantee-related Letter of Credit has been removed from the SD side.
• Risk category - Risk class maintained for the whole business partner (not per customer & credit control area), as the probability of a
credit default of your customer does depend on the characteristics of your customer and not your internal organizational structures.
• Maintenance of customer Credit data in Business partner with Role UKM000.
• The credit checks carried out for a customer depend on the assigned check rule in the Business partner transaction. They do not depend
on the risk class (formerly risk category).
• Releasing blocked documents via Case Management (documents the blocking reason)
FSCM Credit Management – Master Data
• Maintain and check credit management role in business
partner
FSCM Credit Management – Master Data
• Check the credit exposure, credit limit, credit limit
utilization and risk class.
FSCM Credit Management – Master Data
• Check the credit exposure, credit limit, credit limit
utilization and risk class.
Checks in Classic Credit Management and
FSCM Credit
Management
Functionality ECC Credit FSCM Credit
Management Management
Controls OVA8 Available Available

Checks in OVA8 Available Check rule

Checks in Classic Credit Management and
FSCM Credit
Management
Integration Scenario between Trade
Finance and S/4HANA Sales
Simple Logistics | Trade Finance Integrates with
S/4HANA Sales
Retrieve Trade Finance Information in Sales Order
Trade Finance deal is assigned on item level of sales order. Relevant
fields include:
• Payment Guarantee Procedure
• Payment Guarantee Form
• Financial Document No.
F4 help can be used to search for Trade Finance
deals. Here the Financial Document No. is an internal
document number, not the transaction number in
Trade Finance. But there are mappings between
these 2 numbers, thus the user can navigate to Trade
Finance deal when double click the maintained value
of Financial Document Number.

• Depreciation
User can use this field to set the percentage of the
document value that is covered by the assigned
financial document and that is to be written off against
the total value of the financial document. For example,
the user can maintain 100% here in case the financial
document covers the total amount of the sales order
item.
Assign Trade Finance Deal in Sales Order
Assignment in Sales Order

• It is possible that only partial amount of

the sales order item is guaranteed by
L/C or BG, as user can maintain the
percentage in field Depreciation.
• It is possible that one sales order can
be guaranteed by multiple L/C or BG,
as user can assign different L/C or BG
to each item of the sales order
• After Financial Document Number is
assigned, the field Payment Guarantee
Form will be updated, thus user can
distinguish the selected financial
document is Letter of Credit, Bank
Guarantee or Standby Letter of Credit.
Settlement Management
Simple Logistics | Settlement Management
Simple Logistics | Settlement Management
Central Contract Administration
• Single point of entry for contract data and contract-related conditions
• Full support of business volume-related scenarios
• Intuitive data entry of settlement information
Full Transparency of Involved Documents
• Overview of all documents where a contract condition was determined and were accruals were posted
Detailed Settlement Overview
• Enables a detailed view on complex settlement scenarios (ALV and Graphical view)
• Overview of all settlement documents and it‘s financial (FI) status
Accrual Conditions Defined Independently from Settlement Conditions
• Supports different calculation type
• Accrual conditions can be determined within source documents
• Accruals will be cleared at settlement run
• Changes of settlement-related conditions will not influence the accruals
• Different handling of conditions within Profitability Analysis (CO-PA) possible
Pricing Data model changes
Simple Logistics | Pricing Data Model Changes

 Pricing table KONV is replaced with PRCD_ELEMENTS

 Access sequence Number is increased to 3 Digits.
 Pricing Formulae space is increased to 7 Digits.
 Pricing requirement space increased to 7 digits.
 Group condition routine space increased to 7 digits.4 digits
 Customer Pricing procedure( which we maintained in customer master data) & Document PP
(which we maintained in sales document types) is increased to 2 digits.
 Appended fields must be in New structure PRCS_ELEMENTS_DATA.
Field Length Extension & Elimination
of Redundancies
Simple Logistics | Field Length Extension & Elimination of Redundancies

 Sales document category is increased to 4 characters ( multiple document categoris)

 Eliminated Document index tables VAKPA, VAPMA, VLKPA, VLPMA, VRKPA, VRPMA
 Eliminated Index table VBOX (SD rebate processing)
 LIS Tables S066, S067 has eliminated
 Transactions VBO1 and VBOD are NOT VALID except for CRM TPM Customers
 SAP S/4 HANA can support a material number of 40 characters.
 IM (Inventory Management) data model consist of the two tables MKPF and MSEG in SAP R/3,
but in S/4 HANA data model has been changed significantly The new de-normalized MATDOC
table has been introduced because the most information is in one place : MATDOC
Simple Logistics | Field Length Extension & Elimination of Redundancies

Elimination of Status Tables

 VBUK ,VBUP are separate tables in R/3 due which Memory consumption – Higher in R/3

S/4HANA Change
 VBUK,VBUP included in VBAK,VBAP, LIKP, LIPS & VBRK Reduced memory footprint

Document Flow Table (VBFA)

 In R/3 document flow will display all documents related to a particular sales document in a
single screen which will lead the more time to process transaction

S/4HANA Advantage check

 Display of only linked sales document, which in turn transaction will be processed with in less
time
MRP RUN
Simple Logistics | MRP Run
Simple Logistics | MRP Run
Simple Logistics- Production Planning
BOM& Routing & Production versions

Description Risk / implication/Solution Depreciation / New Transaction

► Production versions are mandatory in ► With SAP S/4HANA, on-premise edition 1511, the
S/4HANA. MRP, planned order creation, functional relation between Bill of Material (BOM),
and production order creation only find a Routing and Production Version has changed. It is ► Archaic Transaction codes
BOM and routing alternative if a production now mandatory for Manufacturing BOMs to maintain
version is maintained for the BOM and the product version for correct BOM explosion.
routing alternative Production versions can automatically be created for
BOMs using report Product Version Migration for
BOM (report CS_BOM_PRODV ER_MIGRATION). ► New Transaction Codes
Production versions can automatically be created for
BOMs and routings using report Program for
production version migration for BOM determination
(report CS_BOM_PRODVER_MIGRATION02)

Business Impact :• Production versions allow to define which BOM alternative goes together with which routing alternative
• Mandatory production versions make MRP sourcing simpler. There is only one option to determine BOM and routing alternatives for a
manufactured material
• There is no need to control MRP sourcing with additional control indicators like the selection method MARC-ALTSL in the material master
SAP Note : 2215061, 2215123
Simple Logistics | MRP Run`
• MRP in ECC is run through batch jobs and during off peak hours. However, there is
no need of batch job in S4H and MRP can now be run in real time with HANA
• MRP can be run on plant and MRP area level, but not on storage location level
• SAP recommends to use MRP area with MRP type (ND in case of exclusion or VB for
re-order point planning) for those scenarios at storage location level. MRP with
subcontracting has also been simplified
• These production versions are already mandatory in PP/DS, and PP/DS as part of
the SAP
S/4HANA product. The production versions make sourcing MRP and PP/DS more
similar
• New MRP RUN 10 times faster than old MRP Run and reduced the 5 times storage
Conversion Activities
Simple Logistics | Conversion Activities
Pre –Conversion Post – Conversion
• Migration of existing customers / • FSCM Credit management
vendors to Business partners Configuration
(Master data Synchronization)
• Existing customer / vendor accounts • payment guaranties
groups • Settlement Management
link to Business partner(BP) • Post Migration reports.
• Clearing redundant Material Master entries (
like MARD, MARC,MSEG,MARDH)
• Configuration check for changed processes if
any
• payment guaranties
• Conversation with SAP for Business specific
requirements if required
• Pre-migration Consistency checks
Simplification Item Checks
• SI-Check can (and should) be run by
the customers manually in advance
and will be run by SUM when starting
the conversion (Report
/SDF/RC_START_CHECK) (This report is
for S/4HANA 1809)
• SI-Check check if serious issues exist in
the system which could cause the
system conversion/upgrade to fail.
Simplification Item Checks
Simplification Item Checks
Simplification Item Checks