Skip to Content

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              VBAK_STATUS), same for VBAP (.INCLUDE VBAP_STATUS)

“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!

To report this post you need to login first.

22 Comments

You must be Logged on to comment or reply to a post.

  1. Frank Wagner

    Hello Joachim,

    first – thanks for providing these details related to the Simplificatin List. Some remarks:

    • I wrote to the development –  I will give you an update regarding the ME21 topic
    • The S/4 cloud editions the user interfaces are FIORI based. The SAPGui based transaction codes are not availablel in the cloud editions.
    • The removal of the (not longer used) coding is on the roadmap and might take a while.

    Kind Rehards,

    Frank

    (0) 
    1. Joachim Rees Post author

      Hello Frank,

      thank you very much, that allready answers most of my questions!

      Now what is left is just: how can I have a closer look at the eliminated tables?.

      Regards

      Joachim

      (0) 
      1. Frank Wagner

        Hi Joachim,

        I would take two central SAP Notes as staring point:

        1. The MM SAP Note 2206980 – Material Inventory Management: change of data model in S/4HANA (see aswell Vasilios reply)

        2. FIN SAP Note 1976487 (see additionally the Simplification Item Data Model Changes in FIN)

        Kind Regards,

        Frank

        (0) 
    2. Sven Kotting

      Hello Frank,

      did you get a response as to Ta ME21 and others?

      Or do you have any pointers?

      We have the same ans I wasnt able to find an answer as to why those Transactions are still available.

      thank you and regards

      Sven

      (0) 
  2. Gregory Misiorek

    Hi Joachim,

    good stuff. wasn’t the idea behind S/4 to leave most, but not all, of the tables in but stop populating them (esp since they would then be turned into structures) to reduce the data footprint? not sure what’s behind leaving the ‘old’ code in other than making the transition from ECC a little smoother.

    thanks and congrats on your first blog,

    greg

    (0) 
    1. Monika Patel

      My understanding — “the full transition” will take time (a couple of versions)…

      (a) 1511 – primarily “identifies” the OLD & OBSOLETE, while introducing the NEW DATA-MODEL and optimizations in various area.

      (b) unless and until – challenged by technical reasons and architecture, “existing code & functionality” will remain in package (at least for sometime) 

      (b) Note that many “optimizations” are yet to be released & expected in quarterly feature packs (1602, 1605….)  …

      (c) By 1611, the new data-model would be “time-tested” and errors/bugs fixed & various correction Notes incorporated in the SP/EhP/Version release (as the case may be) 

       

      The removal of old & obsolete would happen in piecemeal…

      Well these are my thoughts and I welcome any other views

      (0) 
  3. Monika Patel

    Thanks for sharing your experience. Interesting to read the observations. Look forward to your next blog.

    One Q : Is your system a new installation ?

    I am working on “System Conversion” & it’s interesting to see that “Pre-Migration” activities are more than actual “Migration” I eagerly await to see how it actually works 🙂

    I also observed that — there is an UPDATE to Conversion Guide as well as Simplification-Listing – which means that the documentation is still being updated and enhanced to incorporate various details.

    Thx..

    (0) 
  4. Karwacki Tomasz

    Interesting blog, thanks for that Joachim. As a Finance person i’m especially interested in this BP feature replacing customer/vendor as i have also read Simplification list. I’m wondering whether for new customers we would need to have customers vendors at all then ? Especially if create transactions are not available anymore ? And if the answer is ‘we do not need them’ how daily processes like reviewing accounts (previously FBL1N or FBL1H for vendor line item display) or executing payment run or dunning will work, are they redesigned for BP usage ?

    Somehow i do not get it, currently we have S/4HANA Finance 1503 with patch 1511 (SPS03) and we are wondering will FI simplifications informed for S/4HANA 1511 will come sooner or later also for S/4HANA Finance, next release is 1602…

    (0) 
    1. Joachim Rees Post author

      Hi Tomasz, sorry for the late reply.

      As far as I see it, customer and vandor are still used at least in a technical sense. Here’s what happens: When you create a Business-Partner in BP, the customer / verdor ist automatically created as well. (Tables KNA1 / LFA1).

       

      When creating a sales order (VA01), not the BP-Number but the customer number is used.

       

      As far as I know you could use this feature (using BP and having it linked to customer/vendor) in the past (e.g. ECC 6) allready. New with 1511 is, that now it’s the only way to go.

       

      I tried the transactions FBL1H and FBL1N you mentioned, and they seem to work fine(-> at least they produce some output – I’m not a Finance person…)

       

      best

      Joachim

      (0) 
    1. Srikanth Palla

      Hi Joachim,

      Can you please advise how to get access to this system? I have an AWS account but this S/4 HANA on premise 1511 system is not avaible as a free trial system on SAP cloud hosted by AWS.

      There are NW 7.5 ABAP systems but they don’t have  S4Basis & S4Core components.

      Regards

      Srikanth

      (0) 
  5. Amit Nanda

    Thanks everyone for sharing these details.

    Need some help from Data Load perspective if anyone did in their project?

    Like earlier we were loading master data through XK01 or XD01 transactions for customer and Vendor and as per 1511 edition now everything will goes through BP transaction.

    Can you please let me know how we gonna load master data now as we have single transaction available as BP.

    (0) 
    1. Vijayalakshmi Chandrashekar

      Hello Amit,

      In S/4 Hana BP’s will be segregated with BP roles.

      To replicate FI/Logistics Customers/Vendors to BP, you have to map customer/vendor groups with BP roles. You have option for both way synchronization.

      After mapping of Customer grp/Vendor grp to BP roles you have to execute T code MDS_LOAD_COCKPIT to replicate all customers/vendors to BP.

      (Please note system will not synchronize blocked vendors/customers to BP).

      Then after whenever you create BP system automatically updates data into KNA1/LFA1….tables.

      Regards,

      Ashok

      (0) 
    1. Joachim Rees Post author

      I don’t know, it might not be possible (I think a faintly remember  something about CPD customers not working).

      Sorry I can’t help you more here.
      Joachim

      (1) 
      1. Susana Messias

        Hi Joachim,

        I searched a little bit more and it appears its possible.

        You have to create an account group for CPD Customer (there is a standard one called CPD), and create a BP grouping for CPD. Then you assign that grouping to that CPD account group.

        When create a sales document and you assign a business partner created on that Grouping, the system prompts a pop up asking for the details (name, address, …) for that CPD customer and these informations will be saved on VBPA table for the document, in a specific ADRNR. With that ADRNR you check table ADRC (name and address) /ADR6 (e-mail) /VBPA3 (tax numbers).

        Regards.

        (1) 

Leave a Reply