Sap Sd S4 Hana.docx

Introduction SAP S/4 HANA is the new offering from SAP built on the high performance In-memory platform HANA with an enriching user experience using FIORI apps.This new system includes major changes and massive simplifications ranging form changes in underlying data models to new user interface through FIORI apps. Objective: The objective of this blog is to understand the data model simplifications in SD area through a comparative study with a non S/4 system. Below are the major simplification points: 

Status tables VBUK and VBUP have been eliminated and the new status fields have been added to:

   

VBAK and VBAP for sales order header and item LIKP and LIPS for delivery document header and item VBRK for billing document header No status fields are present for billing items.



Simplification of document flow table VBFA



Document index tables like VAKPA , VAPMA etc. have been done away with.

User Community Identification of who the system is aimed at. There may be more than one group of people and each group may have slightly different requirements. Are we providing different functions to fulfil these or not? These groups of people are normally identified as use case roles (i.e. actors), and the functions assigned to each role as individual use cases. Where this information does not fit into the use case model, it should be captured in the main functional specification instead.

Administration Functions How will the system be administered? Are there separate functions for an administrator? Is there any security built in to stop others using administrative functions? Passwords?

Error Handling How errors should be handled should be stated. Identify the different types and reasons for the classification.

Security Security considerations are an important part of any project. This section should detail possibilities of abuse of the system.

Along with error handling, the specification has to handle “the negative path”. There is no point in having a system that does lots of good things if it also does lots of bad things.

Help What type of help is to be provided?

Printing Ensure any printing to be provided is stated.

Interfaces User This could be a chapter in its own right if it is a full definition. If it is deferred to the design specification stage, this should be stated. Software We may be interfacing to existing software. This should be stated, e.g. toolkits, back ends of existing packages. State versions. Do interface documents exist?

Boundary Conditions It should be clear what are the extremes to be taken into consideration. These items may have come up. This will vary with different systems but it could be items such as number of users, size of forms, number of forms.

Constraints All other constraints not specified under particular headings. For example: economic, political, technical, system, environmental, scheduling constraints.

Platforms We should list which platforms we will be supporting. Name a reference platform or platforms plus appropriate operating system versions.

Internationalisation Is this to be included in the product now or in the future?

Comparison: Let us understand the differences by looking at the table structures:  

VBUK and VBUP are still present in S/4 HANA but they are not filled when an order is created. The status fields have been added through append structure.

Table Name

Description

Append Name

VBAK

Sales Order Header

VBAK_STATUS

VBAP

Sales Order Item

VBAP_STATUS

LIKP

Delivery Header

LIKP_STATUS

Table Name

Description

Append Name

LIPS

Delivery Item

LIPS_STATUS

VBRK

Billing Document Header

VBRK_STATUS

 



If any custom fields have been added to VBUK or VBUP tables in source system, they will have to be added to respective document tables in S/4 HANA system. An append field to the document header status table VBUK must be added to one or several of the document header tables VBAK, LIKP, or VBRK. This decision depends on which of the document types the respective field is relevant for. An append field to document item status table VBUP must be added to one or more of the document item tables VBAP or LIPS.

VBAK:

VBAP:

When a sales order is created in a non S/4 HANA system: Sales Order: 7137:

VBAK table holds the order header details

Order status information is present in VBUK table

Sales Order in S/4 HANA system:

VBAK table contains both the header details as well as the header status

Header status fields are now added to VBAK table

Table VBUK is present but is not filled.

Reason VBUK / VBUP are still present in S/4 HANA: Since the status tables are not being filled it can be questioned why the tables are still present and not removed from system altogether. The reason for this is to enable smooth transition for those opting for migration to S/4 HANA system. New function modules have been written which read the document status fields from VBAK , LIKP aur VBRK tables and populate in output whose structure is similar to that of VBUK. For example FM SD_VBUK_READ_FROM_DOC is a new FM that fills VBUK structure for one SD document out of document header tables. The data is fetched depending upon the document type.

 

The output structure ES_VBUK still refers to VBUK table. Any custom fields added to appends like VBAK_STATUS will be read by this FM.

Advantages:  

Reduced memory footprint : Since fewer tables are involved this means reduction of redundant data and simplified document flow. Now if we need to query the order table on the basis of document status we can simply do so by 1 single query on VBAK table instead of join on VBAK and VBUK.

NOTES: 

OSS Note 2198647 can be referred for further information.

Acknowledgment: 

Reference taken from Simplification List for S/4 HANA 1511 0302.

S/4 HANA 1511 On Premise Edition – not as simplified as promissed? (comparing the Simplification List to an actual system) January 20, 2016 | 716 Views |

Joachim Rees more by this author SAP S/4HANA 1511comaringon premisreal systems/4hanasimplification list     

share 0 share 0 tweet share 0 like0

Follow Last week I got the chance to lay my hands on a S4 HANA 1511 OnPremise Edition system for the first time. While waiting for our system to be available, I have read the Simplification List (I’m using version 1.5 for references) in detail, so I had some expectations what I will see (and maybe even more Important what I will no longer see). Here are some examples comparing the list and the system experience. I’m accessing the system via the classical SapGui-functions (using Business Client 6.0), and see if I get my processes running that way. (Exploring the new Fiori UI is left to a later stage). System – Status says:

   

Product-Version: SAP S/4HANA ON-PREMISE 1511 SAP_BASIS 750 0000 – SAP Basis Component S4CORE 100 0000 – S4CORE (there’s no SAP_APPL!)

2.1.1.1 Business Partner Approach – BP replacing vendor master and customer master Calling VD01 leads me directly to BP, with the message “Redirection to transaction BP, as transaction VD01 is obsolete”. Same is true for XK01, MK01… VD02 and VD03 let me select the customer before redirecting me to BP. So this is what was announced in 2.1.1.1 Business Partner Approach -> all is done via BP. I didn’t expect getting redirected if you try to use some of the old transactions (e.g. VK01) but consider it a nice service for people transitioning from ECC. Interesting: KNA1 and LFA1 are still filled, when creating the corresponding BusinessPartner. 2.1.2.1 SD Simplified Data Models: From 2.1.2.1 SD Simplified Data Models: “Field length extension of SD document category: Data element VBTYP (Char1) has been replaced by data element VBTYPL (Char4)” -> true, VBAK-VBTYP now has Data-Element VBTYPL, an it is 4 characters long. “Elimination of Status Tables VBUK, VBUP: “ 

Well: VBUK, VBUP: they seem to still be there, but are not filled!

“Status fields have been moved to the corresponding header and item tables – VBAK and VBAP for sales documents, LIKP, and LIPS for deliveries, VBRK for billing documents” 

true: VBAK now has the status fields (.INCLUDE (.INCLUDE VBAP_STATUS)

VBAK_STATUS), same for VBAP

“Elimination of redundancies – Document Index Tables VAKPA , VAPMA, VLKPA, VLPMA, VRKPA, VRPMA” 

well: they seem to still be there, and they are filled!

2.1.9.1 Data model in inventory management (MM-IM) There now is a table MATDOC, and it’s filled. MSEG and MKPF seem to still be there, and seem to be filled. They appear as Transparent Tables. 2.1.9.2 Availability of Transactions in MM-IM “The following transactions for entering and displaying goods movements (material documents) – called “MB transactions” (below) are not available with SAP S/4HANA. […]MB01, MB02, MB03, MB04, MB05, MB0A, MB11, MB1A, MB1B, MB1C, MB31, MBNL, MBRL, MBSF,MBSL, MBST and MBSU” 

True! MB03 redirects to MIGO, MB01, MB31, MBSF gives a message that it cannot be used: “Transaction MB01 is obsolete (see note 2210569 )”. -> ok.

2.1.4.11 Classic MM-PUR GUI Transactions replacement OK, here’s the first time, that the Simplification List clearly seems to be lying: “Transaction not available in SAP S/4HANA on-premise edition 1511:” ME21 ME22 ME23 ME24 ME25 ME26 ME27 ME28 [and some more] Well, I can use ME21 just fine, I successfully created a PO with it! I also used ME22 and ME23. 1.6 Elimination of tables – general Using a SapGui point of view (SE11, SE16, SE16n) the tables that should have been eliminated seem to still be there. I cannot tell a difference between VBUK (should have been eliminated) and VBAK (should still be there). I see two possible explanations for that:  

The compatibility views (aka equally named views) are abstracting so well that I cannot tell them apart from “real” transparent tables. Despite the simplification list saying so, they have NOT been eliminated.

[Edit: the first explanation now seems more likely to me, as I have tried writing into one of those Tables (MKPF) and it didn’t work (update set is giving an RC = 4). ] Another thing to note: some of the tables are still filled while executing business processes (like MKPF), others are not (like VBUK). [Edit 2: now I know how to look behind the scenes here! I share it with you in my new blog! ] 1.7 Elimination of Transactions / dead code Some transaction (ME21) have not been eliminated at all. The others are either re-directing to a new Transaction (VK01 -> BP; MB03 -> MIGO), or giving error messages, that they can no longer be used (MB01). But: The codebase is still there, it has not been eliminated. (I checked it on the example of MBSF -> SAPMM07M). So I have unused (dead) code in my system, which does not seem to be a good idea in regards to maintenance. 1.8 Outlook Maybe you can give me some tips, to help evaluate my experiences? E.g. – what would be a good way to really look at tables (probably down on HANA DB-level?) an tell if the really have been eliminated or not. – has maybe the 1511 cloud edition been more consequent in really elimination stuff, like promised (or threatened?) in the Simplification List? E.g. what happens, when you try ME21 in Cloud Edition? – (how) will we get rid of the obsolete codebase in future releases? I hope you enjoyed my blog, which in fact is my first one ever, so your feedback is very welcome!

Major transitions in SAP S4HANA 1511 in Sales/Logistics module Vs ECC 6.x May 6, 2016   

2,289 views 38 Likes 2 Comments

  

Share on LinkedIn Share on Facebook Share on Twitter As SAP has delivered a simplification list outlining all the changes in their newest product called S4HANA 1511 (On Premise Edition) in all the line of businesses. I am summarizing the changes in SD/LE area here to help get crisp idea of what's in store for Logistics Consultants.



Customers who want to convert from existing Business Suite of ECC 6.x to S4HANA 1511; need to adapt mandatory steps in Pre-Checks shipped as SAP notes to customers.



Business Partner approach is mandatory in SAP S4H On Premise Edition 1511.



As part of pre-check it is planned to check customer-vendor Integration and if it is not in place in current system will be declined for transition.The user interface for SAP S/4H, on-premise edition 1511 is transaction BP. There is no specific user interface for customer/vendor like known from SAP Business Suite (the appropriate specific transaction like XD01, XD02, XD03 or VD01, VD02, VD03 / XK01, XK02, XK03 or MK01, MK02, MK03 etc. are not available in SAP S/4H, on-premise edition 1511).



With SAP S/4H, on-premise edition 1511, the maximum field length of the material number (MATNR) is extended from 18 to 40 characters; all the associated fields on other SAP tables have also been updated with 40 characters.



The Foreign Trade functionality as part of Sales & Distribution is not available within SAP S/4H, onpremise edition 1511. The functional equivalent in SAP S/4H is SAP Global Trade Services (GTS). Material type "SERV" for services is introduced for Product Master in S/4H for simplification purposes.



The business partner related iDoc message types - DEBMAS and CREMAS are not available with SAP S/4H, on-premise edition 1511. They are planned to be available in a future release of SAP S/4H, onpremise edition.



Elimination of Status Tables VBUK, VBUP: Status fields have been moved to the corresponding header and item tables - VBAK and VBAP for sales documents, LIKP, and LIPS for deliveries, VBRK for billing documents.



Business documents within the SAP Business Suite such as the sales order or the purchase order used to store the pricing result in the database table KONV. In SAP S/4H, table KONV was replaced in its data persistency role by the new table PRCD_ELEMENTS. However, KONV is and can still be used for data declaration purposes.



Elimination of redundancies – Document Index Tables VAKPA , VAPMA, VLKPA, VLPMA, VRKPA, VRPMA.



The FI-AR-CR Credit Management is not available with SAP S/4H, on-premise edition 1511. The functional equivalent in SAP S/4H is SAP Credit Management (FIN-FSCM-CR).



The" ERP SD Revenue Recognition" is not available within SAP S/4H. The newly available "SAP Revenue Accounting and Reporting" functionality should be used instead. The new functionality supports the new revenue accounting standard as lined out in IFRS15 and adapted by local GAAP's.



With SAP S/4H a new Output Management approach is in place. The new BRF+ configuration differs from the configuration that is used when output management is based on NAST. For the form determination rules BRF+ functionality is used which has the target architecture based on Adobe Document Server and Adobe Forms only. In application Billing it is recommended to use Adobe Forms but due to compatibility the form technologies known from Business Suite (like SmartForms, SapScript) are supported as well.



SD Rebate Processing is not available within SAP S/4H. The functional equivalent in SAP S/4H is SD Rebate Processing is Settlement Management



In business suite system (ECC 6.x) the database table VBBS contained pre-aggregated sales requirements. The requested (OMENG) and confirmed (VMENG) quantities have been aggregated on a daily basis. With the new HANA ATP we do not need pre-aggregation anymore and therefore this table is obsolete. Instead of the VBBS S4H uses VBBE where each ATP-relevant requirement is explicitly stored. The old ERPATP-check coding is redirected to use VBBE, too.



In line with SAP’s strategy to simplify solution portfolio, e-commerce functionality in SAP S/4HANA Enterprise Management will be provided by the SAP Hybris Commerce solution. SAP intends to offer native integration with SAP Hybris Commerce in a future release.



To reduce the IT footprint and increase response time, SAP intends to provide functionality similar to logistics and sales information systems in SAP S/4HANA with database analytics provided through OData and CDS views. This will facilitate enhanced query performance by reducing select statements and by simplifying joins for headers and items, such as status and business data.



In S/4HANA the business role "Internal Sales Representative" (ISR) is not available within SAP S/4HANA, on-premise edition 1511. This also includes the POWLs (Personal Object Work Lists). Instead a set of new FIORI roles, e.g. SAP_BR_INTERNAL_SALES_REP are offered as successor.

S/4 HANA and its differences with ECC May 16, 2016 | 1,062 Views |

Mrinal Kanti Roy more by this author SAP S/4HANA     

share 0 share 0 tweet share 0 like0

Follow Most of us are following the innovations & simplifications in S/4 HANA and wondering about the functionalities & business benefits of implementing S/4 HANA (S4H).Find lot of questions on differences in ECC with S/4 HANA (S4H). Trying to highlight the major(not a full list) differences in digital core of S4H as planned by SAP w.r.t ECC Hana database S4H can only be run on Hana database unlike ECC which can be run on Oracle , IBM DB2 etc. Back bone of S4H’s design is with HANA’s in memory capability and below design principles





 

In-memory database means that data is read from memory i.e data always reside in main memory RAM (though Write happens in hard disk) and hence in-memory database reads data much faster w.r.t traditional databases (fetching the data from hard disk) Hana’s column based tables provide faster access (as only affected columns need to be read in a query), better compression (due to few distinct values compared to rows), parallel processing (different columns can be easily processed parallely) OLTP and OLAP capability in same system with real time reporting and predictive analysis There will be no aggregate (total), index and history tables in S4H. Aggregates are created dynamically based on line item table instantaneously (on the fly).

Single source of truth S4H combines the data structures of different components (for FI , AA , CO , CO-PA and ML) into a single line item table ACDOCA, called as Universal journal . It eliminates several aggregate and index tables. Now, data needs to be inserted only a single table instead of several tables thus reducing the data foot print drastically. MATDOC is also a new line item table for inventory management and it eliminates 26+ tables. Material documents will be stored in MATDOC but not in MKPF or MSEG tables. Merger of CO and FI In ECC , FI GL accounts are mapped to CO primary cost elements . In S4H, only one field of universal journal is used to store both GL account and cost element. Cost elements (both primary and secondary) are now GL accounts and hence created / maintained (in FS00) with relevant Cost element category. Reconcilation (as in case of CO to FI) is not needed now. Period end closing also will be faster. New GL S4H is technically very similar to new GL of ECC due to its data structure. Customers using classic GL need not use Document split or parallel ledger. However, new GL’s functionality (Parallel ledger) is a pre-requisite for new Asset accounting . CO-PA Account based CO-PA is now the default option with Costing based CO-PA as optional. Both options can be run simultaneously. Refer URL http://scn.sap.com/docs/DOC-65828 for more details. Custom code Read operations in custom code will be redirected to compatibility views (like V_COEP for CO line item table COEP) via a special setting at database interface level (i.e invisible to source code) so that the custom reports can work without any disruption. Business partner All customer and vendor master need to integrated / migrated as Business partner . Probably, SAP is trying to align the concept of business partner as in other SCM applications like APO , EWM , TM etc as these SCM applications also will be natively integrated with core of S4H in future releases. Customervendor integration (CVI) is a mandatory step. Refer URL https://websmp201.sapag.de/~sapidp/012002523100007374172016E.pdf for more details. Extension of Material number field : Material number can now be 40 characters from existing 18. It is a optional feature. Impact of this extension on custom coding, interfaces, other SAP applications need to be evaluated before switching on 40 characters. Refer note 2267140 for more details. Credit management

ECC’s FI-AR-CR is replaced by credit management of FSCM (Financial supply chain management) . FSCM-CR is based on a distributed architecture which allows interfaces with external credit rating agencies. Traditional FI-AR-CR credit control setting requires high degree of manual work. However, FSCM-CR has advanced features like   

Credit rule engine for automatic risk scoring & credit limit calculations Automatic update to master data on approval of credit limit etc. Work flow for credit events etc

ATP ECC provides the option of availability check at the individual or summarized requirements (aggregated at daily or weekly level) , however S4H uses only individual requirements (with no VBBS table) and probably the rationale is that S4H does not have any aggregate table with its simplified data model. SAP also has plans to integrate APO’s GATP (Global ATP) functionality in S4 core. Not sure whether all functionalities of GATP will be integrated in S4 core. Rule based ATP (For substitution of location (plant) or material), Multi-level ATP check, advanced check for product allocation with ATP, advanced BOP (Back order processing) etc are some of the unique features of GATP w.r.t ATP in ECC. Location substitution allows to check the material availability at plant B (as set in master data or business rule) if the material is not available at sales order plant A. If material is available in plant B, then a stock transfer order from plant B to A is created automatically. This rule can be extended to a network of plants also. SD pricing There are some changes in data model in pricing and condition techniques like existing table KONV replaced by new table PRCD_ELEMENTS with extended fields etc. Refer note 2267308 for more details. MRP 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. In ECC , Storage location can either be excluded from MRP or planned separately . 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. SAP has plans to integrate the functionality of APO’s PPDS in core of S4H in future releases and hence probably aligning the APO features like BOM to be selected through production version for in-house , unified source of supply (no source list , only info record ) for external procurements with S4H core. Foreign trade Foreign trade functionality has been replaced by GTS (Global trade services). Advanced features in GTS w.r.t foreign trade are SPL (Sanctioned party list) screening, automated embargo check (Manual in ECC), automatic & simplified license check (manual and complex in ECC) , Automatic import / export declaration etc. Material ledger Activation of material ledger (ML) is mandatory. ML valuates inventory in multiple currencies.Traditionally inventory is mainly valuated with a single currency in SAP ERP. ML allows valuation in two additional currencies. Today’s global organizations operating in different countries desire to valuate inventory in multiple currencies. Like for example, a company in Norway dealing with oil needs to maintain their books in Norwegian currency (NOK), they will also like to evaluate their

inventory in USD as oil is traded in international market in USD. This functionality is available in Release 1511 of S/4 HANA. Refer the blog in URL http://scn.sap.com/community/s4hana/blog/2016/02/22/material-ledger-embeddedin-s4-hana–benefits-and-challenges for more details on ML and its benefits & challenges. Revenue recognition ECC SD revenue recognition is being replaced by SAP Revenue Accounting and Reporting (RAR) due to new accounting standard released jointly by the Financial Accounting Standards Board (FASB) and the International Accounting Standards Board (IASB). New guide line is also in IFRS 15 issued in 2014. Existing SD revenue recognition of ECC is based on Generally Accepted Accounting Principles (USGAAP), International Accounting Standards (IAS) / Financial Reporting Standards (FRS) and it provides the option of recognizing the revenue based on an event (like Goods issue, proof of delivery ) or over a period of time (based on specific set of dates) apart from standard way of realizing revenue on billing. New standard introduces the 5 step model (Identify the contract, separate performance obligations, determine transaction price, allocate transaction price and recognize revenue). SAP’s new Revenue Accounting and Reporting (RAR) solution is in S4H. for fundamental changes with IFRS 15 and also to meet the requirement of parallel accounting and cost recognition . Rebate Customer rebates through existing SD rebate processing has been replaced by settlement management through Condition contracts. Some details on condition contracts are in URL Condition Contract – Compensation Management – SAP Library Output management ECC message determination through table NAST is replaced by Business rule framework plus (BRF +) and target architecture is based on Adobe document server and Adobe forms only. Refer OSS note 2228611 for more details. Warehouse management Existing WM module will be replaced by SAP’s new application for warehouse management EWM . There will be 2 options  

Native integration i.e inbuilt in S4H Side car approach for decentralized deployment

There are several advantages in EWM w.r.t WM like complex warehouse processing through Process oriented storage control (POSC) , improved (easily customisable) RF functionality , Value added service like kitting , enhanced wave & replenishment processes, labour management etc. Native integration of SCM applications Other SCM applications like TM etc will be natively integrated with digital core of S4H. Refer URLhttps://scn.sap.com/community/s4hana/blog/2015/11/19/sap-s-road-map-for-supply-chain-solutionwith-s4-hana-and-its-expected-benefits for more details. User interface Fiori is a new user interface . Refer URL https://experience.sap.com/files/SAP_Fiori_UX_Overview.pdf for more details. Activate implementation methodology

There is no concept of Blueprinting in S4H implementation. S4H has introduced new ‘Activate’ methodology. SAP offers pre-built demo system with SAP’s best practices for specific business processes. Business users can now test in demo system whether it meets their business requirement or not . Fit-gap analysis can be done after initial trial period . Refer URL http://www.akili.com/wpcontent/uploads/2016/01/SAP-Activate_Customer_v03.pdf for more details. Note : All the above information are based on several sources like SAP Documents , Open SAP courses , SCN blogs etc and hence subject to change. Also the features stated above are target functionalities i.e may not be available in present edition of S4H (Like tables for material ledger have not yet been merged to ACDOCA in 1511). Will appreciate if you can highlight other important/fundamental differences or if anything is misinterpreted.