Analysis from 11.07.2022 Untit 17.07 2022 Report: R40, Productive Installation: 0020312597 Session: 0010000008198, EarlyWatch Alert - R40 1 Service Summary ‘This EarlyWatch Alert session detected issues that could potenti Please evaluate the recommendations. Alert Overview ly affect your system. [eg sssave Server Access Conical Ust nat effedive, Sysiem not prieded avainst access byioaue lanplication servers a a [Ealusers with critical authorizations, which allow to do anything in other clent(@) than 000 [EalUsers with critical authorizations, which should not be used in graduction in client 000 [Mle found more than 30 ABAP dumps in your system, (Mi) Readiness of your system for SAP Rem¢ jice has not been verified by running report RICCTOOL IMJ|SAP Software on this system is about to be outdated, Support with SAP Securily Notes is endangered, [M|System-internal communication not protected. [Ml The trend analysis on response time and applications shows a critical trend. [Ml[Based on response times in your ABAP system performance problems may occur Based on worsened response times in your ABAP system in at least ane time window a bottleneck wi | i vs I cetected, Note: If you send SAP EarlywWatch Alert data to SAP, this report can also be viewed in the SAP ONE Suonort Launchnad in an interactive ‘SAP Fiori application SAP Note 2520319. The link to the latest reports for this system: SAP Earlywatch Alert Reports Link to the analytical dashboard for this system: SAP EarlyWaten Alert Dashboard jons in this report Specific links to analytical detall pages In SAP EarlWalch Alert Workspace are included in the respective sect Check Overview Fropie [subtopic Rating [Tome Rating _|Subteple SAP Sater WD [contourat P Apalication Raleasa~ Malatanance Ph [Security Risk Due to Outdated Suaport Packages Database - Maintenance Phases [Operating System(s)_- Maintenance Phases [SAP Kernel Release [Performance Evaluation Bottleneck Analysis Th __|Sae System Operating lavallabiity based on Collector Pratocals [program Errors (ABAP Oumps) S/S) eee] |<<) es) [update Errorscheck Overview fropie Rating [subtopic Rating v v [Topic |Subtopic [fable Reorganization ritcal Number Ranges [Hardware Capacity [Database Administration v v Database version [cache Hit Ratios Database Growth Tao [Link] [Database and Los Backup Frequency, G_|Secunty [System Recommendations (ABAP) |Age of Support Packages Default Passwords of Standard Users trol ofthe Automatic Login User SAB® [Protection of Passwords in Database Connections: [aBAP Password Policy REC Gateway Securit Message Server Security [critical authorizations, which allow to do anything [Ceitical authonzations, which should not be used in production [critical auth In produ DS GIG| Hardware Capacity [Max. CPU Utilization on DB Server 68 % z [Max. CPU Utllzation on Appl. Server lan 9 z Database Performance JAvg. DB Request Time in Dialog Task lszams_| JAvg. DB Request Time for RFC issms|_a [avg_ DB Request Time in Update Task [53 ms z [Database Space Management [DB Size lss06 ca | JOB Growth Last Month iases | # 2 Landscape 2.1 Products and Components in current Landscape Product [system [SAP Product Product Version Inao~aBAP [SAP ERP ENHANCE PACKAGE [6.08 Main Instances [Related System [Main instance Inao~aBar [SAP ECC Server Databases [Retated System [Database System Database Version| [DB ID IRao~ABAP MaxDB 1.9.10 a0. 2.2 Servers in current Landscape ‘SAP Application Servers [system Host [instance Name [Logical Host [ABAP AVA |R40~ABAP ho3se4cus [20301091_R40_41 lao301093 v IReo~neap _[n0s9acus _[ooaoi09i_Rao_42 jaoaox09% v IReo~aBAP__[r.24acus _[o0701091_Ra0_46 jao7ai091 ¥ IReo~asaP —_.2a5cus _[a0801091_Ra0_47 jao80109% ¥ |R40~ABAP hoaticus [ro001091_R40_40 jrooo1091 v [R40~ABAP noss7cus [a0901091_R40_48 Jao901093, v |R40~ABAP hoa 3cus [20501091_R40_44 Jaoso1091 v IReo~AsAP _[no4i3cus _[eos01091_Ra0_45 jao6ox091 v DB Servers [Related system Host [Logical Host (SAPDBHOST) fRe0~ABAP 041 es rooos051, components [Related system [component [Host [instance Name Logical Host IReowABAP [apa scs fhosiieus [roooa091_Rao_a2 rooo1091 2.3 Hardware Configuration Host Overview Hardware CPU [vireuatization|°P&*t°9 epys|cores|Memory| Host [tardvrare, er|todet |cPU Typelmnts [Virtuatization|oPS"=ti"9 lcpus|cores| Meme integrity itaniom HP-UX 11iv3 hosoacus|HPE lvituat |9s00.” |2sa0|Hevm (21.31) on far s6s016 Parton (Poulson) eaniumHost Overview Hardware lceu [operating [Memory] Host [Marae eer(Modet |cPU Tyne|iiys|Virtuatization|oPe'2t"9 |cpus|cores| ("ne integrity |itaniom HP-UX inva lho3e7cus|HPE lviruat [9500 |2530]Hpvm (21.31) on a 1131704 partion [Poulson] tanium integrity [itanium hoa1 tcus|HPE lviruat [9500 |230|Hpvm (12.31) on fis ero16 Partition _|fPoulson] integrity [Itanium hot3cus}He Must” foso0. fasaofupum p 708 Pariion_|outsont Witwer Ieaon Gols Emerprae l2¢ccus [vmware tne. [Vital 2s00}mware bp fa |assys Must lei30 Server 13 5.54) liner Ieaon Gots Encerprise l124scus [vmware tne. |Vivat s00}mwane b fp |assys Miruat e130 Server 15 564) 3 Service Data Quality and Service Readiness Service data of only minor importance Is missing for this report: This does not impact the report rating. ‘The SAP ERP ENHANCE PACKAGE system R40 is not fully prepared for delivery of future remote services, Rating [Check Performed ‘7 __|Sending EarlyWatch Alert of R40 to SAP Backbone 7 [Configuring R40 for SAP Note Assistant ‘> _ [Service Data Quality _ [Service Preparation of R40 3.1 Sending EarlyWatch Alert of R40 to SAP Backbone [oog]S¥ster R40 is prepared for SAP Support Backbone vadate sending EWA data on HTTPS through Solution Manager 7.2 PSM All connections to SAP Support Backbone use https protocol only. For a how to, refer to Connectivity to SAP. ‘The following table shows the latest data transmissions for system R40: Latest Service Data for System R40 Sent to SAP Ready [bat sande Sr ls occa [pate cast Joos (cotectea)|5¥**2™ eas Kernel |Kermelfpy py |Destination|Userfor oer Pet nate Sater a rane] y fol y|imes> [s secraozaltenances (EAE gr [ely lames fo | yy lrnonaiaa] w 3.2 Service Data Quality The service data Is collected by the Service Data Control Center (SDCCN) or read from the Solution Manager's BW or Configuration and Change Database (CCDB) Recommendation: To resolve Issues with the service data quality, follow the hints and SAP Notes provided below.2,1 Quality of Data in Service Data Control Genter (SDCC) Quality Of Service Data In ST-A/PI [Report Area IsaP prio, |Report A Details and Related ST-A/PI Module ear [application Peele on of (Content is only avaliable if you allow online collectors. Run report ° RTCCTOOL, ST-A/PI function: SAP_BACKBONE_UPDATE in project NOL [2927330] JABAP System | used in section ‘Service Data Quality and Service Readiness’ Rao. Legend for ‘Priority’ Column Above rio. [Explanation: Impact of Missing or Erroneous Data ‘© _[Only checks of minor importance are affected 3.3 Service Preparation of R40 [Rating [check Performed wo [Service Preparation Check (RICCTOOL) v [Service Data Control Center of R40. v Hardware Utilization Data 1n preparation for SAP services, ensure that connections, collectors, and service tools are up to ate, These functionalities are explained in SAP Notes 91488 and 1172939. 3.3.1 Service Preparation Check (RTCCTOOL) Report RTCCTOOL was last run on 18.07.2022, During the check, the tool éetected issues for which @ YELLOW rating was set, foveral Status [SAP Note [Tit [root status [Manual Status {59455|Addon STAVPI O1V_731 {59455 [Allow Online data collectors 1359977 |ST-PI 740 Support Package 19 {69855]Proe. after addon Impl. ‘69455|Switch on digital content verification 1539977 Addon ST-PI 740 12103|Collectors and TCOLL S| S| S| Ses ei 2}<|<\< B68) so lololololo [Recommendatios lAddon ST-A/PLO1V_731 "Servicetools for Applications Plug-In" for NetWeaver as of 7.31 [your current version is one or two levels lower than the latest lavaiiabie) From htta://[Link],com/supporttoals ->ST-A/PI-> Installations&Upgrades download the installation ST-A/PI O1V_731. Upload to tx SAINT and instal as per note 69455. Then restart report RTCCTOand choose 'List->Refresh from SAPN: laliow Online data collectors lallow Online collectors for data collection Fram the menu choose "Gato->Online Collectors” and chase a setting. Recommendation is to choose (but also "Disable" decision sets this recommendation to green). low Online collectors" IST-P1 740 Support Package 19 (Addon supportpackage level 19 for ST-PI 740 for basis as of 7.40 [your current patch is one to four levels lower than the latest lavailabie} lOpen ntto://[Link]/suaperttoals ->ST-PI Supportpck.-> ST-PI 740. Add patch SAPK-74019INSTPI (and predecessors if not yet implemented) t download basket, Release basket via Maintenance optimizer. Upload from frontend into transaction SPAM, Jdefine a queue anc import the queue, 4 Software Configuration for R40 We have listed recommendations concerning the current software configuration on your system.Your system's software versions are checked, If known issues with the software versions installed are identified, they are highlighted. 4.1 SAP Application Release - Maintenance Phases [SAP Product Version [End of Mainstream Maintenance [Status IEHPS FOR SAP ERP 6.0 31122027] [SAP NetWeaver Version im Maintenance: Status [SAP NETWEAVER 7.5 3ii22027| Ww 4.2 Security Risk Due to Outdated Support Packages “The chapter Security provides the following ratings regarding the maintenance status of implemented Support Packages: [Rating [check [System 1D a [Age of Support Packages: a0. ‘The Support Package level of key software components on your system threatens to run out of security maintenance. For more information, see chapter Secunty, 4.3 Support Package Maintenance - ABAP The following table shows an overview of currently installed software components. ‘Support Packages Latest lsoftware lpatch|avail. Component [Version [Peter lp sery [Support Package |component Description Level lair [702 ‘| __9|SaPK-702090N1 lairGen [700 q laiex [702 5|__5|SAPK-7O205INATEX [Application Interface Framework Extension 702 : [SAPK- integration Component: Ariba Integration with JARBERPII [600 22| 23 /gao221NARBERPI2_|ERP Backend Systems 600 600 [SAPK- integration Component: Foundation for Ariba [ARBFNOIE [00 21] 24 /fooztNARBFNOIL [Integration with NW 700 100 [SAPK- integration Component: Foundation for Ariba [ARBFNDI2 [200 7] 7|zooo7iNaRBFNDI2 [integration with NW 701 100 [SAPK- lacont —frs7 20] 31/SAPK econt [BE CONT SAP NW 7.40 ADDON 7.57 leas laz0_702_| 2-113 [SAPK-22216INCGS [SAPK- lccsco —faz0_vo2 | 2.213] SAK cesco : [SAPK- Icasce l2z0_702 2.1111 SAP Ncesce : ISAPK- lease l220_702 | 2.113] SAK vcesce [SAPK- lcosos—faz0_7o2 J [Link] SAP ceSoB [SAPK- lcesoo—faz0_vo2 | 2.113] SAK cesop‘Support Packages atest lsoftware lpatch|avai leomponent [Yersion raver pacer [SUPPEFt Package [Component Description Level ISAK lccsot —faz0_vo2_} 2.113] SARK ccsor ISAPK- Icoserp —fa20_702 | 2.113] SAK NCGSERP [SAPK- lcasks —faz0_vo2_} 2.113] SARK casks ISAPK- lcasky —fa20_v02 J 2.1111 SAP cesKy [SAPK- les-orps Jose to] 16|SPK capers [EA-Defense Forces & Public Security 618 lea-rinserv fox 16] sftp [SAP R/3 Enterprise Financial Services 618 Stes SINEAFINSRV nterprise Financial Services = [SAPK- lea-currave [exe 1618 et veaccTaan {SAP R/3 Enterprise Global Trade 618 7 7 ISAP R/S Enterprise Human Resource & Travel leanne feos. 90] 108|SaPK-6ossorNEAHR|SAP R/3 Enter 5 [SAPK- [SAP Integrated Product and Process Engineering [eatere [ese S| lereosineairre [61a EAS: ene 76] __18|SAPK-61616INEAPS [SAP R/S Enterprise Public Services 618 [SAPK- lea-reran fore 16] 16) SR vemreran [SAP R/3 Enterprise Retail 618 lecc-omp exe 16) 8S IECC Discrete Industries Mill Products 618 1 SARK ECCDIMP screte Industries Mil Products ISAPK- lece-se Joos. 20] 21/SAPK cccse [ESA FAST TRACK (ECC-SE) 605 - [SAPK- i lerecrurr |ex7 20] 22|SAPK ecaurr [HEM E-Recruiting 617 7 7 IFI-CA, Contract Accounts Receivable and Payable pce ers (virtell) 618 7 [SAPK- lri-cax exe 18 [SAK ercax. _|FICAX: Extended FI-CA 618 lrineasis fra 16) 19S FFINBASIS 748, [74816INFINBASIS [SAPK- lrscm_cep Jose to] 158K eccmeco |Fsem Cee 618 ISAPK- Jarcerere |v1o00_700] 22] 26| SAM sree» [SAP GRC 10.0 Plug-in ERP 7.00 ‘ [sAPK- larceinw fv1oo0_731) 15] 20/SAP [SAP GRC 10.0 PLUGIN NW 7.31, HEX IHEX_600 i [SAPK-BOOOTINHEX, 4 [SAPK- linsurance Jose 10 [SAP nsuranc [INSURANCE 618 7 [SAPK- cat * hs-cwm — exe 18 SRP wascwm _|IS-CWM Caten Weight Management 618 lis-H ie |___30|SAPK-61806INISH _|IS-Hospital 618 hsm ue. @|__18|/saPK-e180ainisM [Media 618 7” [SAPK- ison — exe 13 [SAP som {SAP for Oil & Gas ISAPK- lis-pra fox. to] 16|SAPK vispra _|IS-PRAGIB 7 [saPK- is-ps-ca eae 18 |SAPK ispsca _|1S-Publie Sector Contract Accounting 618 sur eae 76|SAPK-61804INISUT [1S-UT 618 > [SAPK- Process Gateway enables exposition of processes Ewrcw [00 8] *rooosimiwecw _|as a resource [SAPK- sore fex7 19] 21 A core [tearing Solution - Front Ene 617 IMoc_aret |ox9 a7] 198A [MOG Applications 619 [6191 7INMOGAPPL,‘Support Packages lsoftware lpatch| ee eere ne [version [Petey ISupport Package |component Description ISAPK IMoc_rno rao v7 SAK moGeND (MOG Foundation 749 ISAPK- IMoc_moc foo 17 SAP MoGMDc (Master Data Consolidation 1.0 [SAPK- IMoc_ux exo v7 SAK moGux MOG Additional User tnterface 619 lPasANAPL _|ooi_6i7 q ISAPK- lpescco—Jooi_si7 4| SAP Ks npBscco lpasccora _|ooiei7 q [SAP lpasccu —_oos_ei7 1 SAR wwasccu lpascoarr |o02_617 a lpesces _|ooi_6i7 d lpascrt __|oo2_617 q lpascum _ |oo2_6i7 q ISAPK- lpescur —|ooi_ei7 4] SAK eBscMT lpasceca _|ooi_6i7 q lpascep __|oo3_617 q ISAPK lpascso— |oor_si7 1 Sa NPBSCSD lpascst__|ooi_ei7 ql lpascwm _|ooi_6i7 q ISAPK- pesto [pot_617 y [Do1oxINPASIDK lpasnsP__|o0i_6i7 C [sAPK- lpasorver |oo2_617 | SAK NPBSORDER. lpasuTm —_|oos.ei7 q ISAK leumwur fae. 16 SAK npuwur [PUM WUT 748 \sapKe Fist Integration Component for Revenue Ireveecso fio a Recognition 100 (Revenue Accounting and tootzinrevrecso [Recosnition 1 [sAPK- lsar_asa [750 20] ‘SAK: saeasa _|SAP Anwendungsbasis 7.50 7 [SAPK- _ lsap_ap 750 14 Sark saeap [SAP Anplication Platform 750 [SAPK- 7 lsap_ape. jose 16 SARK: samp. [SAP APPL 6.18 [SAPK- lsap_easis [750 20) 24 ae capansis. [SA? Basis Component 7.50 [SAPK- lsaP_es_rnp|7ae 19 SSAPK: sapasenp (SAP Business Suite Foundation 748 ISAPK- lsap_ew — [750 20] 24 ac sogw [SAP Business Warehouse 7.50 [SAPK- lsap_rin jose. 16 SAK: saein (Financials Isap_cweno [750 zi] 24/SAPK |SAP NetWeaver Gateway Foundation 7.50 x: SAK vSAPGWEND| feaver Gateway Foundation [SaP_HR [608 30] [SAPKE6DB90 [SAP HR 6.08) s [SAPK- S lsap_ur— fsa 7} 10/58 caput [User Interface Technology 7.54 IseeAGeP _|eas_700 q lsem-ew rae. 16) 18)SAPK sap Sem 748 74816INSEMBW‘Support Packages atest lsoftware lpatch|avai leomponent [Yers'on raver pacer [SUPPEFt Package [Component Description Level 7 [SAPK- Isrom_asar |xoo afSAPKcromapap |SFOM On ABAP 1.0 Israrpr __loiu_73t 2|__ 3|SAPKITABCI [STAPI O1U_734 [Solution Tools Plugin 740 Further information's stp 720. 1s 19]/saPk-72015insTPI land responsibles: [nttns://wiki wd [Link]/viii/display/STPL/Home| i [SAP luxorcar foo 6] GfK oxoncar [Ul for Cross Applications 1.0 7 [SAPK- lwrcrooos [520 ISzo04iNvEcPoao1 lvexpoo02 [230 a lvexPo006 [140 C [SAPK- lvFxeo007 [450 2] {1S0021NVFXxP0007 lvexroooe [100 q lwescur rae. 16] 19S ISAP Web UIF 748, 74816INWEBCUIF eb [SAPK- lweco !700_700 4| SARK: wEco ISAPK- Jwecoc {700-700 y [7a0011NWECOC ISAPK- lwecow — |7a0_700 | SARK: wEcow 4.4 Database - Maintenance Phases [Database Version [End of Standard Vendor Support™ [Comment [status [SAP Note: [SAP MaxDB 7.9 INot Yet Defined by Vendor| w _| 1178367) * Maintenance phases and duration for the OB version are defined by the vendor. Naming of the phases and required additional support contracts differ depending on the vendor. Support can be restricted to specific patch levels by the vendor or by SAP. Check in the referenced SAP Note(s) whether your SAP system requires a specific patch release to guarantee support for your database version, 4.5 Operating System(s) - Maintenance Phases End of Standard End of Extended sae nest operaung system [pedghtanderd [end oT EA=Nd64 — |eommentltaual eee, Ream 31.12.2023 w[essaa suse Unor eerie Tinted fema|sever a bos 2) aa.07 0a sovaoalirasy | [assay * Maintenance phases and duration for the operating system version are defined by the vendor. Naming of the phases and required adcitional support contracts eiffer depending on the vendor. Support can be restrcted to specific patch levels by the vendor or by SAP. Check in the referenced SAP Note(s) whether Your SAP system requires @ specific patch release to guarantee support for your operating system version. 4.6 SAP Kernel Release ‘Your system is running an SAP kernel that is up to date. This means that you have the latest available improvements and error corrections offered by SAP to its customers, finstance(s) [SAP Kernel Release [Patch Level [Age in Months [0S Family lSinstances [753 [p21 6 HP-UX on Keanium I2instances [753 lsat 6 Linux (86.64) 4.6.1 Additional RemarksSAP releases Support Package stacks (including SAP kernel patches) on a regular bas's for most products (generally 2-4 times a veer), We recommenc that you base your software maintenance strategy on these stacks. You should only consider using a more recent SAP kernel patch than that shipped with the latest Support Package Stack for your procuct if specific errors occur For more Information, see SAP Service Marketplace at httas://sunpor,sa9,com/software/gatches/stacks. html (SAP Support Package Stack information) and httas://[Link]/+#/softwarecenles/sugpart/index (Support Packages & patch information). For each patch there is an SAP Note in which all known regressions for this level are lsted. Find it using the keyword KRNL7539.921 in the SAP Note search. For detailed information, see SAP Note 1802333 - Finding information about regressions in the SAP kernel. 4.7 ERP Applications ‘Scenario Overview [Scenario lused]betails Y_ [Transactions MIRé, WIRS, MIRE or MIRO were lused in your system IMadule SD is used but ane time accounts (COP- IThe number of one time addresses present in the lcustomer) at most occassionally lsystem is in the range of 0-999, [According to the workload monitor module MM is Processing of Parked Invoices |Module Materials Management (MM) v 5 Hardware Capacity checked your system for potential CPU or memory bottlenecks and found that the hardware of your servers is sufficient for the current workload. Note: Hardware capacity evaluation is based on hosts for which data is at least partially available. Besides the "Overview System” check that focuses on dally average values during main business hours, the "Capacity Analysis section is available. For every host that is related to an SAP workload bottleneck, a resource shortage evaluation has been performed, 5.1 Overview System R40 General! ‘This analysis focuses on the workload during the peak working hours (9-14, 13) and is based on the hourly averages collected by SAPOSCOL. For information about the definition of peak working hours, see SAP Note 1251231. cpu If the average CPU load exceeds 75%, temporary CPU bottlenecks are likely to occur: An average CPU load of more than 90% Is @ strong Incieator of a CPU bottleneck, Memory If your haréware cannot handle the maximum memory consumption, this causes a memory bottleneck in your SAP system that can Impair performance. The paging rating depends on the rato of paging activity to physical memory. A ratio exceeding 25% indicates high memory usage (if Java has been detected O%) and values above 50% ava 10%) demonstrate a main memory bottleneck. server [Max tory [Pate |Rating! any |taecsranmy [Date|Ratinglanaiys's [Analysis lizascus 7]17.07.2022| P| 15.975 a A_|11.07-2022] 17.07.2022, lnzaacus 3)11.07.2022| _~ | 15.975 A _|11.07,2022]17,07,2022, Ihoai cus 41)13.07.2022| #7 _|131.704 ol ¢_|11.07.2022]37.07.2022) Ihoai cus 68|15.07.2022|_¥ [161.036] ol ‘| 11.07.2022]37.07.2022| ho397eus 23/13.07.2022| wy [131.704] Ql ¢_|11.07.2022]17.07.2022 Ihoz94cus 31]11.07.2022)_¥ [161.016] a #_|11.07.2022]27.07.2022, Note: For virtualization or 1aaS scenarios (for example, IBM PowerVM, VMware, Amazon AWS, ..)Itis possible that the CPU rating for some hosts is YELLOW or RED, even though the utilization value is quite low. In this case, the relevant host could not use maximum Usable eapacty due to a resource shortage within the virtualized infrastructure (for example, IBM PowerVM: Shared Pool CPU. utiization).5.2 Capacity Analysis h0411cus [Atleast one CPU (> 75%) bottleneck has been found, The graphical 24-hour profile for every day of the analyzed time frame is shown below. CPU Utilisation (%) 100 ry sianznee * vzoraee "13072002 ame" weorz0e "16072002 sTo72022 Paging In Activi sono nan: simzoz " w2ora2 ' rgnrzz ' ssoram2 ' isarzz * ooram2 ' 17072002 Paging Out Activity (KB) sconco: ono. ° a. L Sharan * saoraee " isoracee " qapvanea " qeorsome ' Wearam2 ” ivar2ize6 Workload Overview R40 6.1 Workload By Users ser activity is measured in the workload monitor, Only users of at least medium activity are counted as ‘active users Users Low Activity [Medium Activity [High Activity [Total Users eiiog steps per week [1 to 399 [a00 to 4799 [4800 or more [measurea in system [225 72 bas: i 6.2 Workload By Task Types ‘This chart displays the main task types and indicates how their workload is cistributed inthe system. Task Type Overview scomr0 4001.00 Ce wee) CICA Ties) [Link] El Cher Tne) [rask Type [Response Timef=] DB Time[s] __[ePUTime[s] [GUI Time ins faaten fss34939 [2057707 676984 o Rec fsx04017 (557242, lesa7as 7576 biatos o72509 1350931 767781 fri6721 lotners aso96e 179015 79459 039 “The chart below lists the top task types in terms of total response time in s. Hourly Workload Profile Total Werks inet 8 8 é e Cash REC CogCPU Load by Application Deca Derescw-ow Duninonn scccu ern Bee Bs Blaters DB Load by Application TecaaLa Di urtrew acccman Docanrwru Bacsressr Dec so Davee 6.3 Top Applications ‘This table lists the top applications of the Dialog task type, The unit of measure is milliseconds [ms] for average time and seconds [s] for total time. ‘Transaction Profile fransaction _|eeponeelrora!22!°9 erp. _forcc. Avs. CPU [ava. DB iva So" (Ava, GU fimetet to fimetms [rimetmsy fimetms RAUoTA———aseaea a7 feeasslisis oe? ows woe ee sez sssee0 [3.1 lar Joia7as_[soaa roo [soisei_[020 ea. Pct fsa5i8 20 [p20 —|ys0e04 ase pocraz —seases loss [ei fas_Awvro——|r7siae—|i.8[eoooo soe lo aoe [rs08 as? eso anz 1790 [0 |as4667[767 Jo [isos ise fact 107809 Jos[sosb7 [1190 Jo Jas9 Joao ara 6 fars_BESTEL —io1ss0—Jas [10s eau? 2 psa [ous Joao as iaceRer ss7es — Joa [sseee [oove [1 fiast_—|sos [uss _—oas pauccz 2686 |o.7[perae_|io79 Jo ps ass soso SESSTON_MANACER|706=2 lose [rzealeea ——o tor ba pot ee ‘This table lists the top applications of the RFC task type. The unit of measure is milliseconds [ms] for average time and seconds [s] for total time,RFC Profile 6.4 RFC Load by Initiating Action The load In task type RFC is shown. In the workload monitor, system can be an application server of the system itself or any © intia! system [intial Action Jotaifstens |nesp. prec, ave. cru lava 8 fewal""”* lrimetres|rietoey aaranoioai naa a0 [SAPD e002 aa eases [99 [neo [7 fso7e0s01091_aA0_ 44 ]os APPLICATION fa775 [ud ]46e27 109 ews Jan Irs fs0/a040105%_ 40-47 [OS_APPLICATION 0547509 [55734 [5107 ps8 feo ro shvro0023#7_Psw_20]ABAr CALL MONITOR, COLLECT ——[aasiz Joe [aera _[osa7i piso [oso 3237 fe0r0001051_Reo 40 [s0_600 9999 econ! poc_nisToRr|ss4s6 [oe [pvse7ilase 109 fir Report Response Tinta] [eof otal Land [Steps [EPO Tinete] 8 Tinea] FON. PROCESS BUFFER [52997 es ia ]aeaso7 [i789 aso wait_pRocaan_[373707 32 soap 9 RSWWERRE i547 Ba 58 [e533 penta NALA RswaSi_SPEGIALosoo7a a 0433 67482 fase one paeas8 is 36 eases ——poerae this Information Is shown as Load from External Systems’, The calling nal system using the RFC interface. The ‘Initial Action’ is the calling program initiating the RFC, The total response time for each intial action is shown as an absolute value and as a percentage compared to the total RFC load considered in this table. The average times (per dialog step) are shown in milliseconds [ms] Calls trom external systems are shown If they account for at least &h or 5% of the total RFC load. Local calls are shown if they account for at least 24h or 20% of the total RFC load. Load Overview [initial System koad f= Load % [Local system RAO 2.288.463] 84,36) [Sum of external systems 411.921 35,19) n/a (not available) 12.224 0.45] IRFC toad (sum of above) 2.712.608] 100,09 IRFC toad in Performance Overview 3.409.460] 125,69 Load of all task types in Performance Overview 11,672,441] 430,30Load Distribution From External Systems ‘Top 20 RFC Calls From External Systems - Average Times [ms] sw Bren Biscrove Brn Bese rca Dots Total lon of [aw Jave eta Jontat Action Resp. Jrec:|Responselcpu {Av8. 08 frme in na (rime rime sit [RW RESOURCE MANAGER Toner] 375) wearer] samplers _o.2 sm [apa CALL WONTTOR: COLLECT 93.168| 349] 36.167,8| 2.91,9[39.986.3| 0.1 yore [VASA GET_WH_ALLOG.ITEWS w7s43] 140] —_969,5| 164] _«a2.9| od sc —erWi RESOURCE MANAGER 35.69o{ 1.32] —ote0.s| 2327.0 2334.4] 02 scrooe|cet 29.729[ ao] aera] 30a] «596,7[ 0 sm —|sw_ccLniveRs_ aaa 23.309{ oe] 22,5 aoa] 24.4] oa sceone put to.s04[ 0.4 —92,0{ 205.6] 272.5] 0.1 favors _[YASACSP_UIST_SALESORDER DOCS | 10.99| 0,40) 3.103,7| 1769.4] 17,0] 0. a Sa 5.539] 020] sas 93.a| 219.4) 02 r70JaiREQU_oxvAMaLFAMOWKUAIOBRSISRBW| 5s 394] 0,20) —2.a03.7| 37.0] —160,7| 0. p70 |o1_process_toapine 463] oel—eo3.o{ 30.71 eo] 02 lyons asa. csp_save_sates_DoC 2.35| oo] —4.854.a] 2523.2) 600.9] 0. lyons [YASA_CSP_NEW_SALES_Doc 2.634)_0.1o] 1.4314] 954.7| i,t acc [2ac_UaN REP OB).P_SyNC-FLWEEK | 2.620] 0,10] 69.890.3| 5370.5|58.976.0 0. lace —|zac_uaw_Aee_o01_p-sync_ra_wetx | —[Link]]_o,0o 56.7622] 5.003,]32.294,6[ 0.1 sceoDe [post La7sloo7| 7481] asa] —s0sa} oa lace zac. aN_pS8_uSeR_Syne_ioUR 1.e36|_o,06] 7.629] —sa3.i] Geae,a|_oa] firs Wash. cSP_OELETE. ALL ITEMS 1533] 006] 3.001, L7a6a]_7o1,1] oa p70 Jainequ_sinoceriovsaisxearxesa7ac | —[Link]]_o,0q] a2.st14] 3.0029] @254] 5 p70 [BIREQU_20GNMDSzXGALISeXFORTUSLUK| 994] 0,0) 39.130,9]10.952,7|36.798 9] 3. ‘Top 20 RFC Calls From Local System - Average Times [ms] [rotator of |avs Ave Enitaiat acion Resp. |aec: Response jeru |A¥9. 08 Fie inetd frime [rime feao [05 APRLICATION smoaai|aeai] —a05n2] —aa.0] aoa] _o.2 fio [sap 454.670] 36,76] 1.2965] —@7.3| —93.6| 02 ji4o__/SDF/MON_ SCHEDULER 259.256) s6]4.802.006,7/8.593.2[23;574.4|255.4 ao [sawe toe eo] 393] 15.1760) 128.5] 188.3] 0. sao [so_600_s999_econ_boc_wsTowr | 6.042] <7] 251,3[ a7] sia] oa aso [swo_ async 6.020] 2.46] 26.1630] i02,s] —235,e| 0.3 fano[saP_COLLECTOR_PERFNON_SHINCCOU | s0.268| 2.15] — s.ss2.s[z709.8] D1ai.7| 5.2 fi40_/ORBIS/ALMA_ INTERFACE, FINALE 55.063] 2,03] —aaa0,7| 35.4] 75] 0. faso/VFORGE/FULLSCAN [Link]) 197] 1296[ 202) «.q] oa fo [vane 25.077 169] 29520] 321 77a oa‘Top 20 RFC Calls From Local System - Average Times [ms] Fetal Eta tit action Resp. |nre_ |Response feru. |Avo.08 ime in icea frie [rime faaa—sa_cens_MOW ATOR DP woasil 125] Tose a|aoo oeae js4o_[50_600_9999_csi_EAWTURN_CALC 38.806] 1.43] —s0.060,]2-767.2]38.498.4 fsa0__/s0F/MON_warcHOOS 25043] 143)a315.960,14.660, 9.0582 fsso[avee001 36995] asf 2.77741 92,5] 75.3 sao [saP_COLLECTOR_PERFWVON_ASDOOS_HSC| 22.573] 1.20] —2e.238.7| 555,0]39;600< sao eaco 22 rif oa 1392430, «209 fsao|[s0_00_b900_VERTEX TAX WRIS_UPO | 22.068] o6i] 22,81 5.6 34 sao [coos 16.749] 069] 4983.9] 40,5] 73 sao [saowsava 77.621] 0.65] 254. 39. 473 sso [vane 76.299] 0.60] 2748.9] 22.6] 05.3 7 Performance Overview R40 ‘The performance of your system was analyzed with respect to average response time and total workload, ‘Some problems that may impair system performance were detected To ensure adequate performance in your core business transactions, you should take corrective action as s00n as possible. For more information, contact SAP Support. Rating [check an Performance Evaluation a Bottleneck Analysis 7.1 Performance Evaluation “The following table shows the average response times of task types running in dialog work processes. Data is BW, Dialog WP related task types [Task [eteps |Ava-Resp. Avg. CPU Avg. Walt [Avg. DB —_JAvg. GUT Itype lrimefms} [Timefms}___|Time(ms}__|timefms}_|Timefms} larc__[are2aia|7a6 87 lo ise 3 [Diatog _[2367512|1298 324 lo 572 303 HTTPS) [612416 [236 18 lo 3 o ‘The measured times are compared against reference times to provide a rating = Ifthe task type Is not Isted in the "Task Type Overview" table In the “Workload Overview R40” section, the In the evaluation = DIALOG, RFC, and HTTP(S) are considered to be related to the end user's dialog activity, The table below indicates that performance problems are anticipated for tasks rated YELLOW or RED. Ratings [rask [Steps [Application Server Performance [Database Server Performance [Dialog 2367512 a laFc___[anez3r v v Time Profile Rating ing| ask [rime [steps [AV®- Response Java. EPU [avg. Database [Rating}Task |Time [Steps |rimetms] [Timetms) lrimetms] B piatos|>>” {30.502 3.615] 1.126 1.644) is fram Soktion Manager task type is not includedTime Profile Rating atinglraak [rime otone [Avs Response lave. CPU lava. Database |Rating} Task | iStePs lrimetms] [Time[ms] [Timetms] B [oad aa 3774 78d os | B Jpiatoo|95" |11.420 1.267 305 622] BB ovars)9% | 6.034 aasad see 23.403 Reference Times Ref. for Ava. Response Ref for Avg. DB [Ref for Ava. DB jrask [rimetmsy ~vellow [Ret for Ava: Response meme] Yellow jumetms]~ Red Rating i ‘9 |Rating [Rating bic 209 300] a9 7809 arc 2.09 3.509 i209 1,809 ‘The chart below displays the time profile for the Dialog task type. Dialog se z 2 4150000 ‘sooo Bt th el | avg Wet Tncns] (Avg. CPUTreIns) Ava D8 Tweins) GlAva GUITiwene) El Oersine) “The chart below displays the time profile for the RFC task type. RFC am. 2 iso = a0 ge eg fa ag a gag ag aa Pees ee ee ge eee eg Ca Wot Trea] EA CPU Trees Clg OB rane onal 7.2 Bottleneck Analysis‘The workload profile of the system has been analyzed to detect periods with increased average response times. If such situations occurred at the same time as hardware bottlenecks, the time periods as well as the affected servers are listed below, For details about hardware bottlenecks, see the ‘Hardware Capacity’ Section. 7.2.4 Bottleneck 13.07.2022 14:00:00 ‘A hardware-related bottleneck was detected during time period 13.07.2022 14:00:00~13.07.2022 22:00:00. The related servers are listed in the table above, [Related Server poatteus 7.2.2 Bottleneck 15.07.2022 10:01 ‘A hardware-related bottleneck was d listed in the table above, [Related Server hositeus 8 Trend Analysis for R40 ected during time period 15.07.2022 10:00:00~16.07.2022 04:00:00, The related servers are The performance of your system was analyzed with respect to the trend of response times per system and e@ per application, We found some problems that may impair system performance. To ensure adequate system performance, take corrective action as soon as possible. For more information, contact SAP Support. Rating table Rating[Check Description 7] [History of response time of |The long-term or short-term analysis of the response time shows @ R40 critical trend ‘7 [Application profile of R40__ |The long-term analysis of applications does not show a critical trend In the following, we analyzed the trend within the following time frames: Short term: From calendar week 25/2022 to 28/2022 Long term: From calendar week 02/2022 to 28/2022 8.1 History of Response Time of R40Workload Profile of Top 3 Task Types Total Ret, Tvain 100s Bf 8 8 3 Cesich Gare odes Bote ‘The graphs below show the time profiles of the following task types: Dialog, RFC. Dialog ge PURGE U PEGG TUT PG acacia RFC 8 ‘Ayatega Reap. Time inme oe y Tag Wet Tire Gave CPUTre ElAig D8Tne Bahers In the following, we analyzed the trend within the following time frames: ‘Short term: From calendar week 25/2022 to 28/2022 Long term: From calendar week 02/2022 to 28/2022 ‘The table below shows the long-term and short-term growth in average response time extrapolated to a year.Growth Extrapolated To A Year peg pao Tove morro co [Type oe/yesr) [Trend|Rating (%e/year) [Trend|Rating| [AL -9,7| Ww Hi 88,7| fey Dialog 28|_ > | Bt 358,3| |B lRFC -18,8] © | Bb -168,5| ¢ | Fees [Schacag Sn Preeltalirwcniy omen [ALL -0,2| > 17, > fi] [Dialog oi, > 69] a [RFC 0.4] > -3,2| > ao Ba [The trend is only for information Bh _ [The trend is critical _[The trend is very critical 8.2 Application profile In the following, we analyzed the trend within the following Short term: From calendar week 25/2022 to 28/2022 Long term: Fram calendar week 02/2022 to 28/2022 ‘Top Applications by Response Time time frames: ‘The table below shows the time profile of the top applications by total workload curing the analyzed period i ase ots ow onan, ons feucre [aah leva hrype |APptication [Rese [Fotallrime [Growth |crowth [rime |T™e| ime in 5)k024 lin ms |(%/year)|(%/ year) in ms in [ialog|YaLMLOLA iiiases63|9 [1980 ~9,3| __-39,7]1049 |sox ‘The graph below shows how the average response time of the top five applications varies over time. Data is normalized to 100% equaling the average value.Trend in Response Times of Top 5 Applications (%) ‘Average Resp Time = yAwioLa “e puangeoto8t_uo_4405 APPLICATION a RéneoOmION AAO AOISAPAIITT® ——-B-RanMsNDINET_AAO_45\05_APPLICATION -2VAsAMYTO 9 SAP System Operating R40 The daily ope operation jon of your system was analyzed, We detected some problems that may impair system lity. Rating [check [avallebiity based on Collector Protocols Program Errors (ABAP Dumps) lUpeate Errors [rable Reorganization S| %| See < [critical Number Ranges 9.1 Availal ty based on Collector ProtocolsCollector availability 0 #100. Fe mata, Date ‘Avalus of 100% means that the collector was avallable all day. "Available" in the context of this repart means that at least one SAP Instance was running. Ifthe SAP collector was not running correctly, the values in the table and grephics may be incorrect. ‘Te check these logs, call transaction STO3N (expert mode) and choose "Collector and Performance DB -> Performance Monitor Collector -> Log This check is based on the logs for job COLLECTOR_FOR_PERFORMANCEMONITOR that runs every hour, ‘The job does NOT check availability; it carries out only general system tasks such as collecting and aggregating SAP performance data {or all servers/instances. The log does nat contain any direct infarmation about availability; it contains only information about the status of the hourly statistical date collection. {As of SAP Basis 6.40, system avallabllty information is available in the CCMS (Computing Center Management System) of an SAP System, in Service Level Reporting of SAP Solution Manager. ‘This function is provides by the relevant Solution Manager Support Packages as an advanced development. For more information, refer to SAP Note 944496, which also ists the prerequisites that must be fulfiled before implementation ean take place 9.2 Update Errors In a system running under normal conditions, only @ small number of update errors should occur. To set the rating for this check, number of active users is also taken into consideration, The following table contains the number of update errors detected. Update Errors by Day We did not detect any problems. 9.3 Table Reorganization When analyzing your database, we detected large or rapiely growing tables or indexes, Recommendation: implement the SAP Notes listed below to reduce the size of some of these tables or indexes, Background: For more information about SAP Data Volume Management, see SAP DVM wid[Fable / index Name [Size of Table / Index [MByte] [Recommended SAP Note leoiaa 4408, /40088 [rstos 9.157,0]48400, 130978, 16083 9.4 Program Errors (ABAP Dumps) 228 ABAP dumps have been recorded in your system in the period 11.07.2022 to 18.07.2022. ABAP dumps are generally deleted after 7 days by default. To view the ABAP dumps In your system, cal transaction S22 and choose Selection, Then select a timeframe. [pate [Number of Dumps 11.07.2022] 36 12.07.2022 54) 13.07.2022 35 34.07.2022] 46 15.07.2022| 50) 16.07.2022] 4 17.07.2022 2 18.07.2022 1 [Name of Runtime Error [bumps [Server (e-9.) Date (es.) [Time (eo) [SAPSQL_PARSE_ERROR aeosoi0s1 Rad_a4 | 13.07.2023] 08:55:08 [COnvT_OVERFLOW. [a0601091_R40_45 | 11.07.2022] 19:25:42 [CREATE_DATA_UNKNOWN_TYPE frovon091-Rao_40 | 12.07.2022] 16:48:46 [UNCAUGHT_EXCEPTION afaoso1091_Rs0_45 | 13.07.2022] 19:51:59 [TABLE_INVALID_INDEX 3]eoso1091_e40_42 | 16.07.2022] 09:29:08 lDYNPRO_FIELD_CONVERSION 3leosoi091_ea0_45 | 14.07.2022) 17:06:32 [CONNE_iMPORT_WRONG_COMP_TYPE ‘Jaos01091_Re0_45 | 14.07.2022] 37:27:49 [CONVT_NO_NUMBER 1[a0301091_Ra0_41 | 15.07.2022] 17:40:36 JOBECTS_OBREF_NOT_ASSIGNED sleo601091_e40_45 | 15.07.2022] 18:39:31] JbBSQL_DUPLICATE_KEY_ERROR 2]rooo.091_Ra0_40_| 15.07.2022] 19:16:04] [GETWA_NOT_ASSIGNED 1fa0s01091_Re0_4¢_| 15.07.2022] 20:36:30 [TSv_TNEW_PAGE_ALLOC_FATLED 3aja0s01091 Reo 48 | _15.07.2022| 22:51:53 [SQL_CAUGHT_RABAX 21f20s01091_R40_48_| 15.07.2022] 22:51:56) IRFC_NO_AUTHORITY 35[20401091_R40_42 | 16.07.2022] 00:38:24 lmessaGe_TYPE_x 18[r0001091_Ra0_20| 16.07.2022] 07:01:47 [rime_our 34)-o002091_kao_40 | 17.07.2022| 16:42:52 [RaISE_eXCEPTION Goja0z01091_Ra0_41_| 18.07.2022] 02:20:28 It is important that you meniter ABAP dumps using transaction ST22 on a regular basis. If ABAP dumps occur, you should determine the cause as soon as possible. jased on our analysis, we found several ABAP dumps that need your attention. Evaluate and resolve the above dumps. If ‘you cannot find a solution, send a customer message to SAP to request support. 9.5 Critical Number Ranges We have checked the usage of ABAP number ranges and found no issues. 10 Security Critical security Issues were found in your system. See the information in the following sectionsRating [Check [System Recommendations (ABAP) [Age of Support Packages [Default Passwords of Standard Users [Control of the Automatic Login User SAP Protection of Passwords in Database Connections [ABAP Password Policy IRFC Gateway Secur Message Server Security [critical authorizations, which allow to do anything [critical authorizations, which should not be used in production [ritical authorizations, which should only see very limited use in production Sio\olo|<|<|<| "SAP Security Patch Day’. [Recommendation: Run support package updates at least once a year. In addition, evaluate SAP Security Notes once a month at ithe time of the monthly SAP Security Patch Day, SAP strongly recommends always performing support package updates for the complete support package stack and not just for the software components listed above. See [Link] |suoport/software-downloads/support-package-stacks, html for further information, 10.1.2 ABAP Password Policy If password login is allowed for specifi instances only, the password policy 's checked only for these instances: 10.1.3 Secure System Internal Communication Parameter: system/secure_communication Rating [Instance [current Value [Recommended Value WW [alinstances [OFF [ON Profile parameter system/secure_communication is not set to ON. System-internal communication js not protected end may allow intruders to access your system. IRecommendation: Activate authentication and encryption of system internal communication by setting profile parameter systemy/secure_communication to ON,ISAP recommends activating secure system internal communication on pure ABAP-based systems. For more information, see SAP Notes 2040644, 2362078, 2624688, and 2778533. 0.1.4 Message Server Security Message Server Access Control List Parameter: ms/acl_info Rating instance [Error Condition v all instances ms/ecl_Info is defined Message Server Access Control List Rating [Error Condition a IHOST=* Recommendation: System- internal communication should be protected by setting profile parameter lsystem/secure_communication to ON, (see corresponding alert) lf this is nat the case, at least the profile parameter ms/acl_info should be set to point to an ms_acl_info fle with the message lserver’s access control list. This list controls which application servers are allowed to log on to the message server, The file referenced by profile parameter ms/ac\_Info should exist and should not contain trivial entries. For more information, see SAP Note 821875. 10.1.5 Users with Critical Authorizations For more information about the following check results, see SAP Note 863362. Note that 12 firefighter accounts have been identified in your system, These firefighter accounts are not considered in the subsequent ‘checks for critical authorizations Recommendation: Depending on your environment, review your authorization concept and use the Profile Generator (transaction PFC) to correct roles and authorizations, YoU can use the User Information System (trensaction SUIM) to check the results, For leach check, you can review the rales or profiles that include the authorization objects listed in the corresponding section [Link] 6 -al authorizations, which allow to do anything 4041 4 Super User Accounts Users with authorization profile SAP_ALL have full access te the system. There should be a minimum of such users. The number of users with this authorization profile Is stated for each client. [client _|No. of Users Having This Authorization. INo. of Valid Users [Rating [ooo 77| 109] 2 loon a |_ a loss: a | a [s00 2 14a] 2 ‘Authorization profil SAP_ALL 40. 2 Users Authorized to Debug / Replace ‘This authorization provides access to data and functions, since any authorization check that is builtin ABAP can be bypassed. In addition, you can change data during processing, which may lead to inconsistent results. The specified number of users for each Glient have the checked autharization. [client _|No. of Users Having This Authorization INo. of valld Users [Rating [ovo @| 105] foo @ | a ose: a | a [500 2| i422) Authorization objects: Object 1: S_DEVELOP with ACTVT=02 (change) and OBJTYPE=DEBUG Note: If you do not want to disable development in your system, you have to exclude the authorization for OBITYPE=DEBUG with ACTVT=02 from roles and only allow any other object type for S_DEVELOP, This means that development and debugging with Visualization is still possibleYou can achieve this by adding two authorizations to the object $_DEVELOP: one with al object types except for "DEBUG" and all activities, ané another for the object type DEBUG only and all activities except for 02, 10,4.5.2 6 al authorizations, which should not be used production 40. 41 Users Authorized to Change or Di y all Tables Unauthorized access to sensitive data is possible If too many users have this authorization. The specified number of users for each client have the checked authorization, [client _[No. of Users Having This Authorization INo, of Valid Users [Rating [ovo 34] 103] foo a |v lose. 3 |v [é00. 4] 14a] v ‘Authorization objects: Object 1: S_TCODE witn TCD=SE16, TCD=SEI6N, TCI Object 2: S“TABU_DIS with ACTVT [Link] © .al authorizations, which shoul E17, TCD=SM3O, or TCI (3 or 02 and DICBERCLS = * only see very I production 10. 1 Users Authorized to Start Reports ‘This authorization allows eritical functions and reports that do not contain their own authorization checks to be executed. The specified number of users for each cient have the checked authorization, [Client _[No. of Users Having This Authorization INo. of valid Users [Rating ooo. 30] 19] foo 3 |v loss. 5 |v [soo 128 1.442) AUTHORIZATION OBJECTS: Object 1: S_TCODE with TCD=SA38 Object 2: S_PROGRAM with P_ACTION=SUBMIT P_GROU Object 1: §_TCODE with TCD=SE3e Object 2: S_DEVELOP with OBITYPE=PROG OBINAME=* ACTVT=16 [Link].2 Users Authorized to Administer RFC Connections If too many users have this authorization, two problems can occur: = Unautharized access to other systems * Malfunction of interfaces if invalid connection data is entered The specified number of users for each client have the checked authorization. [Client _[No. of Users Having This Authorization INo. of valid Users [Rating [oa 73| 709] loon A |_v loss. a | Vv [s00 22 14a) W ‘Authorization objects: Object 1: 5_TCODE witn TCD=SMS9 Object 2: S_RFC_ADM with ACTVT NE 03 10.1 3 Users Authorized to Reset/Chan: ‘The following users are allowed to change and reset the passwords of users. This Is very risky because any of these users could change the password and log on themselves with anather user, The only consequence is that the "real ser" would no longer be able to log on because the password would have been changed. However, this normally results in the password being reset, because there is a chance that the "real user" might have fargotten the correct password. [client _|No. of Users Having This Authorization INo. of Valid Users [Rating [ovo @| 15] foo ql |v[Client_[No. of Users Having This Authorization IN. of Valid Users [Rating oss: a lv [s00 37| 14a] v7 Authorization objects: Object 1: §_TODE with TCD=Su02 or TCL Object 2: S_USER_GRP with ACTVT=05 188 or TCD=OOUS or TCI 11 Software Change and Transport Management of R40 No critical software change management issues were found In your system. 11.1 SAP Netweaver Application Server ABAP of R40 [Rating [check Performed v INumber of Changes v [Emergency Changes v [Failed Changes 11.1.4 Number of Changes Performing changes is an important cost driver for the IT department. It is only acceptable to make a large number of software and Configuration changes in exceptional situations, such as during go-live for an implementation project The following dlagram shows the number of changes per day that were performed in the SAP system in the last week. The data Is ‘extracted from the Change Diagnostics application in SAP Solution Manager. The changes are grouped into "Software Maintenance’ (such as support or enhancement packages), "Parameter" (instance, database, operating system), "Transport Requests", "SAP Notes", and "Miscellaneous" (such as security settings). Pe : = Clee : oo {| no [ip opDate [security|sorware Parameter| \rewuree Rates [Miscellaneous| ia.07.2022] 2 q 7 q q ql [12.07.2022] 3] q d q q q [23.07.2022] 2| q q q q q 14.07.2022] 3 a H 2 G A 15,07,2022] 2| Ql 2 o A 17.07.2022] dl o d 27| d d 11.1.2 Number of Transport Requests The following diagram contains information about the number of transport requests per day that were imported into the SAP system inthe last week, ie g 2. L = lwerteren aa pebeston Remuere AG 1] |Giowiomary Peace é ranspon a copes Z L Date [Date [Workbench and Relocation Requests [Customizing Requests [Transport of Copies 14,07,2023| ql 2 Ql 15.07.2022] d 2 d 17.07.2022| 23] q 4 11.1.3 Number of Transported Objects The following diagram contains information about the rumber of objects per day that was imported into the SAP system in the last He nWeriberch 9d Pebedten omueta Doves n cusionara Pesueete Dlovecten Tanssor et copes To "aao7, "aaa" aso7, "as0r. aeor, "arr Datepate [objects in Workbench and Jobjects in Customizing [Objects in Transport lRelocation Requests Requests lof Copies 4.07.2022| al 7 ql 15.07.2022] | 3 d 17.07.2022] 237] Ql a 41.1.4 Emergency Changes We analyzed the number of emergency changes in system 240 in the last week. [Ratinglitem lVatuelexplanation [Trensport requests creates Infotacuction | _9|Number of transport requests; created or released In production. [Transport requests "The duration between the export from the development system lwitn short transition lane the import into the production system was shorter than one time \day. [Total number of transport requests ° 331| Total number of transport requests in production. 11.1.5 Failed Changes In this check, we analyzed the number of failed changes in system R40 during the last week. Ratnglitem value[explanation nee INumber of transport requests with Import errors that were not resolved requests with ith one hour lOverakers ard | Iran old object version overwrites a newer one we count this a8 @ ve Oftransport sequence error. We count both the overtaker transport and the renspor bypassed transport. Each transport is only counted once > Fezanumber oT] roa numberof anspor equests that were imported or leased in renspor production within the last week. Financial Data Quality 11.2 Financial Data Integrity Our “quick” chacks identified no inconsistencies in the area of Financial Data Integrity that require your attention, 11.3 Financial Data Management (ur “quick” checks identified no inconsistencies in the area of Financial Data Management that require your attention. 11.4 Reconciliation of ECC Systems (prior to S/4HANA) ‘This section cisplays data from the reconciliation checks in the ares of Finance, For ECC customers we provide checks in the area of General Ledger and Asset Accounting 11.4.1 Reconciliation for Asset Accounting ‘The data displayed in this chapter is a result of execution of the FIN_AA_CORR_RECON transaction, It contains various consistency checks of the Asset Accounting application. Identified inconsistencies might have a negative Impact on your daily business and cigital tvansformation projects. It's especialy crucial to analyze and resolve listed issues in detail prior to SAP S/4HANA conversion. Please rote that, when estimating the resolution effort of the Identified inconsistencies, you should refer to the number of different error types, but not the total number of errorsIn your case, this transaction had not been executed or not fully executed. Please make sure to fully scan your system for possible further inconsistencies In your financial data, For more information, refer to SAP Note 3038014, Prerequisites [Note [Description [2896400] Reconciliation of Asset Accounting Inconsistencies In ECC prior ta S/4HANA Conversion [3026403] FIN_AA_CORR_DISPLAY: false positive error message FIN_AA_RECON 764 DDDIC objects for note 2896400 - Reconciliation of Asset Accounting Incons| 3075335) S/aHANA Conversion [3002026] Recon. of AA in ECC prior to S/4HANA conv. asset numbers In multiple company code encles In EGG prior 11.4.2 Reconciliation for General Ledger ‘The data displayed in this chapter is a result of execution of the FIN_CORR_RECONCILE transaction, This reconciliation check is the main source of the financial data quality analysis. It contains various consistency checks of the General Ledger application. Identified inconsistencies might have a negetive impact on your daily business and digital transformation projects. It is especially crucial to analyze and resolve listed issues in detail prior to SAP S/4NANA conversion. Please note that, when estimating the resolution effort of the identified inconsistencies, you should refer to the number of different error types, but not the total number of errors. In your case, this transaction had not been executed. Please install and execute the FIN_CORR_RECONCILE transaction, in order to fully scan your system for possible Inconsistencies in your financial data. For more information, refer to SAP Note 2755360. Note Description [2755360 [Reconciliation prior to S/4HANA Conversion [2906603 Financial Data Quality: Central Preparation Note Please note that the displayed results in the following tables concern the Run IDs mentioned above, 12 Data Volume Management (DVM) ‘The database size and database growth of your system R40 indicate that no immediate action is required in the area of Data Volume Management. ‘This report does not have @ Data Volume Management (OVM) section focusing on Deletion and Data Archiving because the collection of DVM-relevant data has nat been activated for your system RéO, See SAP Note 2036242 for more Information about how to activate the DVM content for service reports. Once the DVM content has been activated, information about the current state of your system R40 regarding Data Volume Management is provided, along with proposals about how to reduce the database size of this system. [AS a workaround, the database size and growth per year for your system R40 were checked. Here, we found a database size of 8.906,00 GB and a database growth of 10,04% per year, The database growth per year was calculated/extrapolated by comparing the current database size 8.906,00 GB with database size 8012 GB from 05.07.2021. ‘These figures indicate that, from a Deletion and Data Archiving perspective, no immediate activities are required for your system Raa, 13 Database Administration In the checks performed, no problems regarding the administration of your database were found.Rating [check [Database version [Cache Hit Ratios [Database Growth [Top growing Tables S/SISISIS) [Database and Log Backup Frequency 13.1 Database Version We have not detected any severe problems during the SAP DB / MaxDB version check. Obtain the latest available build for your database version from the SAP Marketplace Downloac Center at [Link]/swde Downloads --> Support Packages and Patches --> Entry by Application Group --> Additional Components ~-> SAP DB / MAXDB, and so lintroduction: lUsing a recent kernel version helps to ensure that the database management system functions properly, In addition, most new releases have been optimized with respect ta performance. We have determined that you are using the following SAPOB / MexDB: se: 7.9.10 bulld 005-123-267-563. 13.2 Cache Hit Ratios Cache Hit Ratios [Data cache [catalog Cache 39] 33) ‘According to our check, the sizes of the data cache, the catalog cache, and the converter cache are set correctly 13.3 Database Growth No problems with database free space have been found. Database Growth (93) 8 21062003 5062023 062003 1062003 nor 272 ve? 2003 a3 zane oar 2003 ?13.4 Top growing Tables Top Growing Tables [ovseraname| [Fablesi® [Sum leaf pages [Sum ahort longs [rable Growth lenddate lsorrconti_[x] 892.967.608] 3.703.632| _889,263,976]11682552 ra.07.2022| lcocts |x) 207.639.240] 34.183.560] 113.455.680|2104344 18.07.2022] Jractetexa | [90,487,392] 90,487,392] ofeos7ise 18,07,2022| lEDIs0 x|_45.473.529] 3.804.216| “41, 669,304]1779184 18.07.2022] [conDR 88,620,560] 8.620.560] ofiss7e32 18.07.2022] [cexe60o 152,972,708] 152.972.704| ofis20136 18.07.2022] lneivvaues | |122.633.072| _122.633.072 ofiz9sz32, 28.07.2022] lausP 174,309,056] _174.309.056| ofiaz2a40 18.07.2022] esis 38,392,272] 38,392,272| ofgoa7i2 18.07.2022] frsTos x] _9.376.472| 101.624] 9,274,848)825224 18.07.2022] 13.5 Database and Log Backup Frequency [According to our check, your data and log backup strategy is sufficient. ‘The backup cycle defines the period for which backup media is stored before reusing it. SAP recommends a backup cycle of 28 days ‘his is a compromise between the amount of backup media required and the ablity to successfully respond to possible error sit A sulfcient backup strategy will ensure that the database can be restored in due time after a database crash. The time needed to recover the database depends on how often backups are performed, |Recommendation: SA? recommends the following backup strategy: Jat least one complete and one incremental data backup should be performed per week. lat least one log backup every day should be performed or the autolog option should be enabled, [all backup operations should be monitored regularly and backup errors (return code <> 0) should be analyzed. [The usability of the backup tapes should be tested ance in each backup cycle (by restaring them to a test system, for example) 13.6 EWM Workload Weekly Workload [Transaction [steps Avg. Repsonse Time [ms] [avg. DB Tine [ma] IRSPPFEROCESS Zz 72 04 14 SAP NetWeaver Gateway No major problems were found with the gateway configuration or administration of your SAP ERP ENHANCE PACKAGE system R40. Rating [check IMetaData Cache Activation lKegaing Configuration NetWeaver Gateway Error Logs [Cache Cleanup 30b SSISIS) 14.1 Gateway Configuration 14.1.1 MetaData Cache Activation[cache [Activated [Metadata Cache es. ‘The metadata cache is activated in your system as recommended. 14.1.2 Logging Configuration [Logging Use Case Log Leve [Recommended Log Level [Regular processing [Eror, Security, Warning Error, Secunty, Warning The gateway logging configuration is set correctly on your system. 14.2 Gateway Administration 14.2.1 Cache Cleanup Job Pobname: [Status [/IWEND/R_SM_CLEANUP [Scheduled ‘The gateway cache cleanup job is scheduled on your system, Gateway Processing Performance ‘The following tables show the load and performance of OData gateway cals forthe previous week, These tables show the top 10 Obata cals, sorted by the fllowing enter ‘Total Calls Total Call Time In Milsecones Average Data Received In Bytes Note: The OData Request sttistics can be viewed and further analyzed by visiting the SAP EariyWatch Alert Workspace, 15 Trend Analysis ‘This section contains the trend analysis for key performance indicators (KPIS). Diagrams are bullt weekly once the EarlyWatch Alert service is activate. In this section, a "Week" is from Monday to Sunday. The date displayed is the Sunday of the week 15.1 System Activity ‘The following eiagrams show the system activity overtime. ‘The “Transaction Activity” diagram below depiets transaction activity in the system over time, |- Total Activity: Transaction steps performed each week (in thousands) “ransaction steps performed in dialog task each week (in thousands) ansaction steps (in thousands) during the peak hour; this peak hour is calculated as the hour with the maximum eiiog ectivity n the ST03 time profile divided by 5 working days per week, (Peak Activity is absent if "Activity Data" Is token from STO3 deta direct).Transaction Activity (oopusdes) Amey Wook [oT Acnvty -@-Dalog Acs Users who performed more than 400 transaction steps in one week Total Users: Total users that logged on in one week. < ‘The "User Activity” diagram below shows the user activity on the system over time. User Activity = agasee"se° Tex f t 3 t i i 4 2 eeeaee 6 [2 Leased on -e-actve 15.2 System Operation ‘The following ciagram or table shows important KPIs for system operation.System Operation 0. Eieao pend eae cea ee cee ete cea a cee cee * “ ~ “ Wook ~ 7 " feaviakty CO) Program Evora (BAP) -#-Upse Evers 15.3 Hardware Capacity Hardware Capacity 4) F oso] “© Database Sever CPU Mas Load) -S-Ape Sever CPU Wax. Losd () Report time frame: Service data was collectes starting at 18.07.2022 04:25:51, This took 21 minut You can see sample SAP EarlyWatch Alert reports on SAP Support Portal at SAP EarlyWatch Alert -> Sample Reports. For general information about SAP EarlyWatch Alert, see SAP Note 1257308. ‘About System And Solution Manager [System No. Of Target System aiooni5a6 [Solution Manager System PSM [Solution Manager Version| ISOLUTION MANAGER 7.2 [Service Tool [720 sP14 [Service Content Update On 2.07. 2022