S No No Point No Topic Sub Topic Note Number

1 26 26.1 Logistics - PM S4TWL - Object List Number Field Length Extension 2580670

2 27 27.2 Logistics - PP S4TWL - MRP in HANA 2268085

3 27 27.5 Logistics - PP S4TWL - Forecast Based Planning 2268095

4 35 35.1 Procurement S4TWL - MM-PUR WebDynpro Applications 2267445
 MMPUR_VNDPARTNER_APP
5 35 35.2 Procurement 2267449
Display of Partner Roles of a Vendor

6 35 35.3 Procurement S4TWL - Dedicated SAP Supplier Lifecycle Management 2271188

(SAP SLC) business processes

7 35 35.4 Procurement S4TWL - Supplier Distribution via MDG-S 2267719

8 35 35.5 Procurement S4TWL - Authorization Concept for Supplier Invoice 2271189

 S4TWL - Foreign Trade within SAP S/4HANA
9 35 35.6 Procurement 2267740
Procurement
10 35 35.7 Procurement S4TWL - RFQ Simplified Transaction 2332710

11 35 35.8 Procurement S4TWL - Webdynpro Applications for Purchase 2200412

Requisition Transfer from ERP to SRM

12 35 35.9 Procurement S4TWL - Co-Deployment of SAP SRM 2271166

13 35 35.10 Procurement S4TWL - Supplier Invoice New Archiving 2578291

14 35 35.11 Procurement S4TWL - Co-Deployment of SAP Supplier Lifecycle 2267413

Management (SAP SLC)
15 35 35.12 Procurement S4TWL - Vendor evaluation based on LIS 2267414

16 35 35.16 Procurement S4TWL - Pricing Data Model Simplification 2267442

17 35 35.17 Procurement S4TWL - Output Management Adoption in Purchase 2267444

Order

18 57 57.1 Industry Utilities S4TWL - CVI Integration for SAP ISU 2344100
 S4TWL - IS-U Stock, Transaction and Master Data
19 57 57.9 Industry Utilities 2270505
Statistics (UIS, BW)

20 57 57.14 Industry Utilities S4TWL - Enterprise Services for SAP for Utilities (IS-U) 2270513
 Symptiom
You carry out a system migration from SAP ERP to SAP
S/4HANA On-Premise or Cloud edition. In SAP ERP, you use the
object list functionality in one or more logistical processes
(maintenance order, service order, inspection lot, delivery,
purchase, serial numbers). In this case, the following worklist
item is relevant for the SAP S/4HANA data transfer:

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You want to execute a transition of your ERP system to S/4

HANA.

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

Supplier Invoice Archiving does not fully support ILM

Integration

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion to SAP S/4HANA. In this

scenario, the following SAP S/4HANA Transition Worklist item
applies.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion from SAP ERP to SAP

S/4HANA. The following SAP S/4HANA Transition Worklist item
is applicable in this case.
You are doing a system conversion to SAP S/4HANA, on-
premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.

You are doing a system conversion to SAP S/4HANA, on-

premise edition. The following SAP S/4HANA Transition
Worklist item is applicable in this case.
 Prerequisites
In SAP ERP, you use the object list functionality in the
SAP standard system. You also access object lists in
customer-defined programs or change object lists with
customer-defined programs. It does not matter whether
the customer-defined programs are called within SAP
ERP (for example, Z reports) or from an external source
via interfaces.

MRP live is a synonym for MD01N and MRP live on SAP

HANA
CPPR (Collective Processing of Purchase Requisitions)
and SPPR (Single Processing Of Purchase Requisitions )
no longer available in S/4HANA
 Solution / Description
To enable the processing of even large object list volumes in a future-proof manner, SAP has decided to extend the object list
format INT4 to the data format INT8. In addition to the table OBJK, this change affects all further tables that contain a field wit
item "SI10: Logistics_PM" (title: S4TWL - Object List Number Field Length Extension).

Production planners have to make sure material is available when needed. MRP assists production planners with this task. The
orders, purchase requisitions, or delivery schedule lines to cover the expected material shortages. A shortage exists for a mate
quantity of material requirements (sales orders, stock transfer requirements, production requirements, and forecast requirem
receipts (inventory, production orders, purchase orders, delivery schedule lines, firmed planned orders, and firmed purchase r
SAP S/4HANA features MRP Live (MD01N); a new MRP run optimized for SAP HANA. MRP Live reads material receipts and req
requisitions all in one database procedure. This minimizes the volume of data that has to be copied from the database server
MRP Live (MD01N) has some additional advantages including the following, for example:
• The definition of the planning scope is more flexible. MRP Live allows you to plan a set of materials with all components, ma
across all plants.
• If a material is transferred from one plant to another then the stock-transfer requirement is not known in the supplying plan
determines the sequence in which materials have to be planned across several plants.
• MRP Live is a prerequisite for the future production planning and detailed scheduling PP/DS solution in SAP S/4HANA.
Classic MRP is still available as an interim solution(Functionality available in SAP S/4HANA on-premise edition 1511 delivery bu
for creating MRP lists.

In forecast based planning (MRP type VV) the MRP creates planned orders or purchase requisitions if total forecast demand up
same point of time. The total firmed receipt quantity includes inventory, production orders, purchase orders, firmed planned o
planning procedure, which does not require managing planned independent requirements. For Forecast based planning the fo
• MRP live does not perform forecast based planning in HANA but sends the affected materials into the classic ABAP planning
• Forecast demand and planned independent requirements are semantically very similar. Planned independent requirements
• The system records all changes of planned independent requirements which facilitates reporting
WebDynpro Applications of SAP ERP Materials Management (MM) are not available with SAP S/4HANA, on-premise edition 15
The corresponding functionality is replaced with existing SAP GUI transactions, Fiori applications or Smart Business within SAP
The coverage of Fiori applications will grow over time.
Classic SAP ERP Materials Management (MM) transactions and BAPIs for the business objects Purchase Order, Purchase Requi
transactions and BAPIs made available with SAP R/3 Enterprise 4.70.
With SAP S/4HANA, on-premise, these classic MM transactions and BAPIs will NO longer be available. The replacements that a

The following processes are supported with limitations:

- Supplier Evaluation
- Category Management
- Activity Management (internal)
The following processes of SAP Supplier Lifecycle Management (SAP SLC) are not available within SAP S/4HANA, on-premise e
- All sell-side processes (e.g. Supplier Registration and Supplier Data Maintenance)
- Several buy-side processes (e.g. Supplier Hierarchies, Supplier Classification, Area of Validity in Supplier Evaluation, Supplier Q
Business Value
It is a strategic decision of SAP to consolidate fuctionalities of Supplier Lifecycle Management (SLC) within SAP S/4HANA Suppl

After the conversion of SAP ERP to S/4HANA, customers who have been using SAP SLC as a standalone system communicating
supplier distribution.
Business Value
To ensure data secureness it is necessary to use MDG-S (Master Data Governance for Suppliers) for supplier distribution.

The previous concept was based on checking header data against the item authorization object for all items. The system check
plants.
With the new concept, the behaviour of the system is more comprehensive. The new concept introduces a header authorizati
checks:
• Check header data against the header authorization object (M_RECH_BUK). This authorization object checks the common ac
• Check item data against the item authorization object (M_RECH_WRK). This authorization object checks the common activiti
Business Value
The new authority concept for supplier invoice enables a simplified handling especially for invoice items w/o PO reference.
Currently there are two software services for international trade transactions: Foreign Trade and SAP Global Trade Services (G
SAP GTS is an external service that can be installed on a separate instance. With SAP S/4HANA on-premise edition 1511, the Fo
Services (GTS) is the successor for the business requirement.
For Intrastat a customer can leverage functionality within SAP S/4HANA, on-premise edition 1511.
Additional functions for import and export management are available with SAP Global Trade GTS.
Business Value
It is a strategic decision of SAP to use SAP Global Trade Services for international trade processes. Furthermore, selected inter
S/4HANA.
The previous concept was based on Request for Quote with a mandatory Supplier Field. In addition it was only possible to ent
Sourcing Integration Scenarios (Example Ariba Sourcing, Ariba Spot Quote…).
With the new concept, the behaviour of the system allows to send RFQ via Fiori App to external sourcing platforms without a S
Following IDOCS and Transactions related to Request for Quote are not considered as the target architecture (Functionality av
technology. Functional equivalent is not available).
It is planned to replace them with cXML messages:
REQOTE (Basic Idoc type = ORDERS05) is the IDOC for RFQ
QUOTES (Basic Idoc type = ORDERS05) is the Idoc for Quote
The following transactions are not strategic anymore and it is planned to replace them with corresponding Fiori Apps:
ME41 Create Create Request For Quotation
ME42 Change Change Request For Quotation
ME43 Display Display Request For Quotation
ME44 Maintain Supplement Maintain RFQ Supplement
ME45 Release Release RFQ
ME47 Maintain Create Quotation
ME48 Display Display Quotation
ME49 Price Comparison List Price Comparison List
ME4B RFQs by Requirement Tracking Number RFQs by Requirement Tracking Number
ME4C RFQs by Material Group RFQs by Material Group
ME4L RFQs by Vendor RFQs by Supplier
ME4M RFQs by Material RFQs by Material
ME4N RFQs by RFQ Number RFQs by RFQ Number
ME4S RFQs per Collective Number RFQs by Collective Number

SAP® S/4HANA is SAPs next-generation business suite, it is not a legal successor of any SAP Business Suite product. It is a new
today – SAP HANA® – and modern design principles with the SAP Fiori user experience (UX). SAP S/4HANA delivers massive sim
making, business processes, and models) and innovations (Internet of Things, Big Data, business networks, and mobile-first) to
In the approach to build SAP S/4HANA, SAP is re-architecting its solution for modern business processes demanded by an incre
growing over the past 25 years means and sometimes evolved into different data structures and architectures means as well t
forward. This is the only way how we can prepare the solution for more simplicity and faster innovation cycles.
Following the SAP Fiori user experience and simplification approach, the portal content and web dynpro applications for CPPR
Purchase Requisitions ) are no longer available in S/4HANA.

With SAP ERP it is possible to deploy SAP SRM as an AddOn. With SAP S/4 HANA this AddOn deployment is not possible anymo
converting the SAP ERP system to SAP S/4 HANA.

With upgade to 1809 ILM Integration is fully supported.

Please note: BAdI Implementations used in the old archiving reports (RM08RARC, RM08RADE) are no longer supported. The n
(ARC_MM_REBEL_WRITE, ARC_MM_REBEL_CHECK) which need to be newly implemented.
The goal is that - over time - the functional scope of SAP Supplier Lifecycle Management (SAP SLC) will be available within the
deployed SAP Supplier Lifecycle Management on SAP ERP and want to migrate to S/4HANA use those parts of the SAP SLC fun
to as "Supplier and Category Management". For the functional differences, see simplification item Dedicated SAP Supplier Life
using a standalone SAP SLC system can continue to use it, but have to use MDG-S for supplier data integration. For more infor
(SAP SLC) business processes.
The current vendor evaluation based on Logistics Information System (Note: If you use a material number longer than 18 char
2232362”.) is still available with SAP S/4HANA, on-premise edition 1511, but is not considered the target architecture (Functio
considered as future technology. Functional equivalent is available.). We recommend that you use the SAP HANA reporting ca
technology.

See the information provided in the Sales & Distribution area in simplification item "Data Model Changes in SD Pricing". https:
On a basic level, this information is also relevant for the pricing in procurement.

With SAP S/4HANA a new Output Management approach is in place. By design, the new output management includes cloud q
modification free configuration. Therefore, the complete configuration differs from the configuration that is used when outpu
accessible for Customers. In SAP S/4HANA, the target architecture is based on Adobe Document Server and Adobe Forms only
functionality is used (in this sense in combination with the message determination).
Nevertheless Output management based on NAST is still supported for new documents in purchase order. Purchase orders wh
been determined, can be processed with the new and with NAST technology. The user can decide whether he wants to use fo
Procurement for purchase order there is a need to adapt the configuration settings related to Output Management.
In purchase order it is recommended to use Adobe Forms but due to compatibility the form technologies known from Busines
the print reports.
In Purchase order processing it is recommended to use Adobe Forms but due to compatibility the form technologies known fr
also true for the print reports.
In contrast to the output management based on NAST the new output management supports only the Channels PRINT, EMAIL
channels are not supported by default.
Additional information to the new output management in SAP S4/HANA can be found in the general simplification item relate
Up to release OP1709 you can find more information about how to activate the NAST-based Output Management in the SAP C
Purchasing -> Purchase Order -> Activate or Deactivate SAP S/4HANA-Based Output Management.
As of release OP1809 you can find this customizing setting under Cross-Application components -> Output Control -> Manage
default solution, but a system upgrade will not change the previous selected output management.
Business Value
Additionally to the existing output management based on NAST a new Output Management solution is adopted S/4 HANA-wid
activities. The existing Output Management solution however still can be activated.

In SAP S/4HANA, on-premise edition, the central business partner approach(CVI) is mandatory. Customer and vendor master r
Partner functionality (Transaction 'BP'). For more information, see the simplification item Business Partner Approach (SAP Not
Consequently, the former concept of SAP IS-U Business Partner and SAP SD Customer integration in SAP ERP has been substitu
Please note that it is planned to check the introduction of the Customer/Vendor Integration in the pre-checks and the technic
where the customer/vendor integration is not in place will be declined for the transition.
Please note that CVI functionality described in this note is released for SAP S/4HANA only and SAP does not plan to make it av
IS-U Stock and Transaction Statistics based on Logistics Information System (LIS) is not available within SAP S/4HANA, on-prem
for Utilities (see documentation https://help.sap.com/viewer/6b356c79dea443c4bbeeaf0865e04207/1709%20000/en-US/dde
https://go.support.sap.com/innovationdiscovery/#/innovation/6CAE8B27FCC31EE6A080E3EEE0531B00) and SAP BW/4HANA
https://help.sap.com/viewer/06e872f914a44d77b6c692b0273ca400/1.0.1/en-US/a3e19257660b6c10e10000000a441470.htm
The corresponding functionality and transactions can be found in SAP Business Suite in the SAP Easy Access menu under "Utili
Statistics" and "Transaction Statistics", respectively. In SAP S/4HANA, "Stock Statistics" and "Transaction Statistics" are not ava
EI35
Set up stock statistics
EP01
Customizing: Transaction Statistics
EP02
Customizing: Stock Statistics
Usage of UIS is indicated by entries in database tables TE789C and TE790C with ACTIVE field set to ‘X’. If no entries exist, this n
Following BW Data Sources are not available anymore: Stock and Transaction statistics (in brackets please find alternatives): 0
0UC_ISU_14 (0UC_ISU_32) 0UC_ISU_15 (0UC_DEVINST_ATTR) 0UC_ISU_16 (0UC_SALES_STATS_02 or 0UC_SALES_STATS_03)
(0UC_DEVICE_ATTR and 0UC_DEVICER_ATTR) 0UC_ISU_19 (0UC_DEVICE_ATTR) 0UC_ISU_20 (0UC_DEVICE_ATTR) 0UC_ISU_2
0UC_ISU_24 (0UCCONTRACT_ATTR_2 and 0UCCONTRACTH_ATTR_2) 0UC_ISU_25 (0UCINSTALLAH_ATTR_2 or 0UCINSTALLA_
(0UCPREMISE_ATTR_2) 0UC_ISU_28 (0UC_DEVLOC_ATTR) 0UC_ISU_30 (0UC_DEVICE_ATTR and 0UC_DEVICER_ATTR) 0UC_ISU
Master Data and attributes (in brackets please find alternatives): 0UC_ACCNTBP_ATTR (0UC_ACCNTBP_ATTR_2) 0UC_CONNO
0UC_TRANSPORT_TEST 0UCCONTRACT_ATTR (0UCCONTRACT_ATTR_2) 0UCCONTRACTH_ATTR (0UCCONTRACTH_ATTR_2) 0U
(0UCINSTALLAH_ATTR_2) 0UCPREMISE_ATTR (0UCPREMISE_ATTR_2)
Other (in brackets please find alternatives):
0UC_ISU_CONSUMPT_02 (Sales Statistics shall be applied) 0UC_ISU_CONSUMPTION (Sales Statistics shall be applied)
0UC_SALES_SIMU_02 (0UC_SALES_SIMU_01, 0UC_SALES_SIMU_03)
0UC_SALES_STATS_01 (0UC_SALES_STATS_02, 0UC_SALES_STATS_03)

The following Enterprise Services for SAP for Utilities (IS-U) are not available in SAP S/4HANA, on-premise edition 1511, and fo
• TEST_UtilitiesConnectionStatusChangeRequestConfirmation_Out
• TEST_UtilitiesConnectionStatusChangeRequestCancelRequest_In
• TEST_UtilitiesConnectionStatusChangeRequestRequest_In
• UtilitiesConnectionStatusChangeRequestConfirmation_In
• UtilitiesConnectionStatusChangeRequestCancelRequest_Out
• UtilitiesConnectionStatusChangeRequestRequest_Out
• UtilitiesTimeSeriesBundleItemCreateConfirmation_In
• UtilitiesTimeSeriesBundleItemCreateRequest_In
• UtilitiesTimeSeriesBundleItemCreateConfirmation_Out
• UtilitiesTimeSeriesBundleItemCreateRequest_Out
There is no precise check on the usage of obsolete Enterprise Services. Looking for service messages of these obsolete enterpr
Processed XML Messages) and SRT_MONI indicates the usage.
Please check referenced notes 1541831 - UtilitiesConnectionProcessing enterprise services in EHP5 - and 1527380 - Deprecate
 Other Terms Remarks
SI10: Logistics_PM", OFLE, S4CORE PM

MRP live, MD01n

CPPR, SPPR
CVI, ISU
Utilities Information System, UIS
 Business Process Related Information
No effects on the standard SAP business processes are anticipated

Production planners have to make sure material is available when needed. MRP assists production planners with this task. The
creates planned orders, purchase requisitions, or delivery schedule lines to cover the expected material shortages. A shortage
driven planning and if the total quantity of material requirements (sales orders, stock transfer requirements, production requi
time exceeds the total quantity of material receipts (inventory, production orders, purchase orders, delivery schedule lines, fir
SAP S/4HANA features MRP Live (MD01N); a new MRP run optimized for SAP HANA. MRP Live reads material receipts and req
and purchase requisitions all in one database procedure. This minimizes the volume of data that has to be copied from the da
considerably improves performance. MRP Live (MD01N) has some additional advantages including the following, for example:
• The definition of the planning scope is more flexible. MRP Live allows you to plan a set of materials with all components, ma
or one material across all plants.
• If a material is transferred from one plant to another then the stock-transfer requirement is not known in the supplying plan
plant. MRP Live determines the sequence in which materials have to be planned across several plants.
• MRP Live is a prerequisite for the future production planning and detailed scheduling PP/DS solution in SAP S/4HANA.
Classic MRP is still available as an interim solution(Functionality available in SAP S/4HANA on-premise edition 1511 delivery bu
has to be used for creating MRP lists.
Production planners have to make sure material is available when needed. MRP assists production planners with this task. The
creates planned orders, purchase requisitions, or delivery schedule lines to cover the expected material shortages. A shortage
driven planning and if the total quantity of material requirements (sales orders, stock transfer requirements, production requi
time exceeds the total quantity of material receipts (inventory, production orders, purchase orders, delivery schedule lines, fir
SAP S/4HANA features MRP Live (MD01N); a new MRP run optimized for SAP HANA. MRP Live reads material receipts and req
and purchase requisitions all in one database procedure. This minimizes the volume of data that has to be copied from the da
considerably improves performance. MRP Live (MD01N) has some additional advantages including the following, for example:
• The definition of the planning scope is more flexible. MRP Live allows you to plan a set of materials with all components, ma
or one material across all plants.
• If a material is transferred from one plant to another then the stock-transfer requirement is not known in the supplying plan
plant. MRP Live determines the sequence in which materials have to be planned across several plants.
• MRP Live is a prerequisite for the future production planning and detailed scheduling PP/DS solution in SAP S/4HANA.
Classic MRP is still available as an interim solution(Functionality available in SAP S/4HANA on-premise edition 1511 delivery bu
has to be used for creating MRP lists.

If you decide to replace forecast based planning by MRP type planning proceed as follows:
• Step 1: Convert forecast requirements into planned independent requirements (PIR)
• Step 2: Change MRP type VV to one of the MRP types PD, P1, P2, P3, or P4
ABAP Web Dynpro Applications not available in SAP S/4HANA

WebDynpro Application
Description
SAP S/4HANA Replacement
MMPUR_CPPR_MAIN_APPL
Collective Processing of Purchase Requisition
SAP GUI report BBP_EXTREQ_TRANSFER, Fiori Application
MMPUR_SPPR_MAIN_APPL
Purchase Requisition Processing
SAP GUI transaction ME51N, Fiori Application
MMPUR_ACCOUNT_ASSIGN_COMP
Account assignments
MMPUR_ADDRESS_COMP
Display Address
MMPUR_BWLAUNCHER_APP
BW Starter
Smart Business? BW Integration?
MMPUR_CFOLDERS_EP_EVENT
Document Storage
MMPUR_CFOLDERS_URL_APP
Document Storage
MMPUR_DISPLSCHEDLINE_APP
Display of Delivery Schedule Lines for Item
MMPUR_DOCTRK_APP
Document Tracing
MMPUR_DOC_TRACE
Graphical document tracing
MMPUR_FINDSUPPLIER_COMP
Find Supplier
MMPUR_FORECAST_APP
Expected Contract Release Orders
Smart Business?
MMPUR_MAVERICK_APP
Maverick Buying Analysis
Smart Business?
MMPUR_PRICECOND_APP
No influence on business processes expected.

Transaction NOT available in SAP S/4HANA on-premise edition

ME21
ME22
ME23
ME24
ME25
ME27
ME28
ME51
ME52
ME53
ME54
ME59
MR01
MR1M

BAPIs NOT available in SAP S/4HANA on-premise edition

BAPI_PO_CREATE BAPI_REQUISITION_CREATE BAPI_PO_GETDETAIL

The functional scope of Supplier and Category Management in SAP S/4HANA is currently not identical with the SAP SLC functio
Coversion support is not available.

SAP S/4HANA leverages MDG-S for supplier distribution. The MDG-S license is not part of the SAP S/4HANA license.

No influence on business processes expected

The customer needs to check whether 3rd party foreign trade systems are in use for foreign trade processes. Because of the r
that 3rd party foreign trade system will need adjustments by the respective 3rd party Solution/Service Provider. However, SAP
foreign trade processes.

Transaction not available in SAP S/4HANA on-premise edition 1511

VX99 FT/Customs: General overview
EN99 General Foreign Trade Processing
VI09X Change FT Data in Purchasing Doc.
VI08X Display FT data in purchasing doc.
VI80X Change FT Data in Goods Receipt
VI79X Display FT Data in Goods Receipt
VI77X Change FT Data in Outbound Delivery
VI64X Display FT Data in Outbound Delivery
VI14X Change FT Data in Billing Document
VI10X Display FT Data in Billing Document
VIIM FT: Op. Cockpit: Purchase order
VIWE FT: Op. Cockpit: Goods Receipt
VIEX FT: Journal Export Actual
VE85 Change Statistical Value – Import
VE86 Display Statistical Value – Import
VE88 Change Statistical Value – Export
VE89 Display Statistical Value – Export
VE87 Change Stat.Value – Subcontracting
VEI3 Display Stat.Value – Subcontracting
OVE1 Commodity Code / Import code no.
VXCZ INTRASTAT: Form - Czech Republic
VXHU INTRASTAT: Form - Hungary
VXPL INTRASTAT: Form – Poland
VXSK INTRASTAT: Form – Slovakia
VEBE INTRASTAT: XML File - Belgium VECZ INTRASTAT: File - Czech Republic
VEHU INTRASTAT: File – Hungary
VEPL Create INTRASTAT CUSDEC EDI PL
VESK Create INTRASTAT CUSDEC EDI SK
VEIA Create INTRASTAT CUSDEC EDI SE
VEIB Create INTRASTAT CUSDEC EDI PT
VEID Create INTRASTAT CUSDEC EDI LU
VEI0 Create INTRASTAT CUSDEC EDI IE
Before using the new Fiori App you need to close your open RFQ created with the old transactions.

SRM Self-Service Procurement capabilities are re-implemented within SAP S/4 HANA. The functional scope is described in the
Service Requisitioning. The functional scope is not identical with the SAP SRM functionality. However it is planned to reach fun
the S/4 HANA capabilities. There are migration reports available to transfer the business data from the SAP SRM AddOn to the
Business Value
Providing Self-Service Requisitioning as an integral part of S/4 HANA has several business benefits compared to the old AddOn
• Data structures are simplified, e.g. no shopping cart data anymore, instead only purchase requisition data is used
• Seamless UI integration based on SAP Fiori (formerly GUI and WebDynpro) as well as seamless process integration
• No master data replication (formerly data replication between SRM AddOn and ERP core)

The functional scope of Supplier and Category Management in SAP S/4HANA is currently not identical with the SAP SLC functio
Master categories in purchasing category are not available. As a successor, material groups are available in purchasing categor
Business Value
It is a strategic decision of SAP to provide functionalities of Supplier Lifecycle Management (SLC) within SAP S/4HANA Supplier
solutions.
The current functions are unchanged within SAP S/4HANA, on-premise edition 1511. No influence on business processes expe
Business Value
The usage of SAP S/4HANA offers real-time supplier evaluation capabilities without building and referring to table and structur
much more analytical visualization options as LIS.

See simplification item Data Model Changes in SD Pricing.

Output Management for Purchase Order has to be configured. In cases where there is not customer specific configuration for
be possible to print purchase orders or to send purchase orders via e-mail or XML.

No influence on business processes expected.