Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Hi Readers,

Here is my blog post on S4 HANA upgrade.

A brief Background:

Often time we go for System conversion from ERP to S4 HANA upgrade on HANA DB1.0 or 2.0 as Business desires to have for advance business processes transformation in the light of digital age.

Primarily we get into this upgrade in two ways... Either your ERP system is updated HANA DB upgrade from previous database (ORACLE/DB2 etc...) first then brownfield implementation with S4 upgrade OR straight with S4 upgrade with HANA DB upgrade in parallel.

Successful S4 upgrade beings lot of new functionalities and leaves many existing standard objects as obsolete and or deprecated (replacement with available fiori apps from the library). it also makes custom applicable and associated objects unstable to the extent of the usage of standard functionalities inside.

So we need to take care of the custom objects with seamless responsibility as for the standard objects in order keep the entire system up and running for the business as it was before and now in much better with higher expectations.


So with the above business goal to achieve proactively ,here are bunch of helpful tips from my view in this blog that will keep the system consistent and operational POST S4 HANA upgrade from ERP in better way than it was before to the least.

1.There will no longer be separate transaction codes for vendor master (XK0*) and customer master (XD0*). It’s all in BP transaction as business partner must be created first before customer or vendor.

2.The CVI configuration governs the internal/external number range assignments along with BP role and account group (vendor/customer) mapping.

3.Material number will have the new length 40, however many already existing BAPIs FMs or OO objects like BADIs may carry the old material number length as 18 so appropriate conversion to be taken care.

4.ABAP custom RICEFW objects including DDIC to be altered/modified to ensure material number/product code consistency.

5.Many standard FMs will become obsolete, especially related to time/time zone conversion, BAPI RETURN table types, structures.

6.Many data elements, domains, tables, structures will become obsolete and to be replaced with S4 HANA support pack provided DDIC objects.

7.During migration phase, the SPAU and SPDD changes to be done with greatest care, especially no already implemented OSS NOTES to be reset unless turn out to be obsolete in S4 HANA system. In that case, suitable and applicable OSS notes to be considered.

8.Remediation of RICEF objects will be necessary specially to make them Unicode compatible in case the system was not converted previously.

9.For good movement, stock transfer only MIGO must be considered. There will no longer MB1A/MB1B and MB1C available.

10.Functional usage of FBL3N/FBL5N will be limited and instead FAGLL03 to be used.

11.Many standard BADIs will become obsolete (example – time sheet, commodity usage, house bank configuration). Those will be replaced with equivalent FIORI apps with even enhanced functionality as based on sap recommendation.

12.The transports move from the old stack during service pack upgrade to be validated with care such that pieces of codes in custom enhancements should not be lost. Otherwise this can cause lot of system inconsistency.

13.It may be required to deactivate few custom enhancements as sap may provide the same or similar enhanced functionality in their standard codes of applications.

14.Often S4 HANA default output management flag remains active for application like purchase orders/invoices. this can cause issues in sending outbound idoc messages, in this case the old and original output types to be reactivated again.

15.Keep an eye on active S4 HANA credit management in SD application as this can create problem for custom exits.

16.In many applications/transaction codes, S4 HANA alters the screens with new tabs/screen elements so in this case pre-existing BDCs will not work so they may need to be replaced accordingly.

17.Blacklisted objects (runtime error – SYSTEM ABAP ACCESS DENIED) to be tracked closely and to be made white and active if necessary.

18.Oftentimes, you may notice that certain important screen elements are not working as they used to in ERP version (for example – services for objects or entry pop up screen in service entry sheet), then the fix to be done accordingly.

19.Existing SAP QUERIES, FI reports, reports groups to be regenerated to avoid short dumps.

20.You may need to regenerate the TMG for custom tables.

21.Single exit multiply active short dump fix to be taken care as S4 HANA often inserts standard implementation.

22.Many program variants to be recovered again in S4 HANA system to make the program works.

23.GL account conversion to take judiciously if required.

24.Preexisting UI5/FIORI apps may be noticed as deprecated in the new S4 system. In this case proper fix to be incorporated or the app to be replaced with any new standard FIORI app.

25.The SELECT will be preferred using the optimized SQL view in the program as all the tables will be replaced by CDS view in underlying DB query.

26.DB tables (Classic DDIC object) will mostly be on column orientation rather row orientation.

27.Background jobs performances to be checked on HANA DB if they get slower than expected in the execution.

28.ABAP CDS views to be incorporated from eclips to S4 HANA system.

29.For DB procedure access and debug, AMDP method to be used.

30.For gateway development, SADL framework to be considered with Ui5/Fiori application.

31.BOPF framework deactivation, transaction state related dump (short dump Exception /BOBF/CX_FRW_FATAL) to be resolved technically with supplied oss note.

32.DBSQL_SQL_ERROR (error code – 10807) to be resolved with the help of basis.Set the parameter idle_cursor_lifetime  to 1440 for above.

33.BP related short dumps: PHONETIC, NO_ACTIVE_TAB, illegal operations, etc. to be investigated.



The above sneaky pointers are quite powerful, once understood in context, will provide the required arsenal to be better prepared to tackle the S4 upgrade and later the system remediation with more confidence and good planning.

I thank you all the readers for helpful comments and feedbacks here, I appreciate....

Please reach out to me for any question that you may have. You can follow the tag here for the comments.