The SAP add-on (PAT) file contains ignio’s ABAP programs for use cases execution. They are written in its own namespace. For more details, refer https://digitate.atlassian.net/wiki/spaces/ID/pages/3776649057
The SAP add-on (PAT) file contains ignio’s ABAP programs for use cases execution. They are written in its own namespace. For more details, refer https://digitate.atlassian.net/wiki/spaces/ID/pages/3776649057
The general recommendation is to always install custom ignio™ SAP add-on during off-peak hours.
The process to uninstall SAR file is like PAT file. Basically .SAR is compressed form of .PAT file only.
Refer to Eagle | AI.ERPOps 5.0 | SAP Add-on Release and Installation Process
There is no impact. Refer to Eagle | AI.ERPOps 5.0 | SAP Add-on Release and Installation Process
JCO connector is SAP AG certified. It has already passed the GxP, a regulatory security compliance for pharma customers. It is plug and play type utility present out-of-the-box.
JCO is capable of handling large number of use cases used by ignio in ERP SAP Manufacturing applications.
Error handling also becomes easier in the JCO/RFC scenario.
Also, by “wrapping” JCO/RFC/BAPI logic in MII (Mfg intelligence and Integration and Analytics) BLS (BAPIs) transactions, it creates a reusable, simplified (reduced no of inputs/outputs) services for ignio to invoke in ERP SAP application.
JCO is tightly coupled integration which probably is the best in using technical integration where ignio understands all the stable end points.
The main reason why it can’t work is because a PAT file contains more than 600 SAP programs. We have used many programs which are common between the 2 PAT versions and we do not make changes to all the programs. Therefore, we cannot use both old and new at the same time.
Also, in SAP when we upgrade the newer version it goes and overwrites the older PAT (all programs). Technically, we cannot store SAP PAT file programs in the database which have 2 “active” versions.
In order to install ignio custom add-on in the SAP system, one needs minimum authorizations. This is a standard SAP requirement and holds true not only for ignio add-on, but for any SAP patch that needs to be installed. The Basis BD team must be able to identify any suitable user with relevant authorization per their organization’s policies. There are many SAP standard links available on this ask. One that I came across is https://help.sap.com/saphelp_ssb/helpdata/en/49/3e896a28ab2222e10000000a42189d/frameset.htm
No.
The average size is around 3 to 4 MB.
You need to provide SAP component version and SAP product version. The details are available in SAP at SYSTEM > STATUS.
It is in the product roadmap.
Yes, that’s correct. It can be used to monitor both SAP ABAP (Webdynpro) and Java web-based applications.
No, the SHC dashboard gives live monitoring and HC view of critical admin level checks on a single or multiple systems
The addition of custom transaction in SHC completely depends on individual business process requirements. It can be easily developed per the solution design and with the customer’s technical team.
Cumulatively added new self-heal in System Health Check capability such as SAP system traces, SAP Logon group configurations, SAP RFC Server group configurations checks. Currently, there are more than 28 catalog items across various capabilities. Refer to Eagle | AI.ERPOps 5.0 | Catalogs for more information.
You can add multiple email IDs but not separately for each TCode at single node.
In case of ignio, SM13 TCode signifies whether all the update process are active or not. The values mentioned are of SAP standard RC(VBRC)- return codes for SM13 updates. Refer SAP standard documentation for the same.
Govern dashboard for real-time monitoring of SAP. The system health check includes trend analysis, latest work items viewing features. The dashboard is also available for IDoc management.
Yes, ignio AI.ERPOps provides self-heal actions for System Health Check capability.
Yes, SAP system health check can be implemented for multiple systems in one go.
The KPI metrices that are configured in Solution Manager are considered for the profile vital and threshold.
Solution Manager provides graphs. However some of the functionalities such as insights, risks, predictions, integration with problem tickets are currently not available.
Yes.
Solution Manager capabilities are:
Solution Manager Alert Integration -Alert aggregation, suppression to find true alerts in the alert flood
Analytics – Profiling, Correlation and Predictive data Analytics on Solution Manager KPIs
As of now it’s SM 7.2. The integration works in the same way as ERP and S/4 HANA.
ignio™ AI.ERPOps based product offerings can supplement Solution Manager functionalities to deliver customers a win-win proposition. Ignio™ AI.ERPOps possesses capabilities over and above the Solution Manager and provides you with out-of-box use cases to resolve the issues with the technical monitoring data, provides you with insightful analytics on it, and handles problems with ChaRM. ignio™ supports the latest version of SAP Solution Manager (SAP Solution Manager 7.2). Please refer the following link for the more details:-
https://digitate.com/ignio-ai-erpops-complementing-sap-solution-manager/
Service based approval can be configured through SR policy. Refer for Eagle | AI.ERPOps | Service Request Configuration Manual 5.0
With ignio™ AI.ERPOps, you can not only automate onboarding but also automate all routine user/role/password management requests such as :
Create User, User Modifications/Changes, Password Reset, Lock/Unlock Users etc.
Note: It depends upon the user onboarding process for enterprise.
One user entity represents one user in SAP. It’s the design of ignio to have such entities which will allow AI/ML operations to be performed for user management use case.
EWA is very static in nature. It is based on cloud-SMP logic to validate SAP systems against set or pre-configured parameters. PCM on the other hand can adapt based on the SM KPI metrics that that you feed.
PCM KPIs complement Solution Manager. With PCM, you can also ingest data manually in SAP landscapes.
Refer to row no 48 of https://digitate.atlassian.net/wiki/spaces/ID/pages/3776644118
There is no limitation. There is also the chunking logic added to keep the update of records to minimum in each call to SAP.
There are internal SAP adapter programs written to update SAP master data records based on approval and necessary validations. Missing master data generally is updated by business teams based on their knowledge. For example, vendor payment terms, material or article prices are all governed by the business teams.
For self healing, ignio suggests some recommendations.
Yes, AI.ERPOps makes use of artificial intelligence which is implemented via programming for each KPI.
Master Data Sanity check capability checks inconsistency within the systems only. For example, Inconsistency of Production system
In AI.ERPOps 5.0 release, Master Data Sanity Check Self-heal feature is introduced which rectifies the
Master Data Inconsistencies as well. Refer to Eagle | AI.ERPOps 5.0 | Master Data Sanity Check (MDSC) – Check Master Data User Guide
ignio™ MDSC does inconsistency and missing master data checks post the implementation phase.
Yes. However, ABAP and Java coding is required to implement this type of customization in sanity check.
The missing delivery plant KPI is maintained in Customer Master.
Material Price – Material
Storage Location – Storage Location
Payment Term, Bank Details – Vendor
Shipping Condition, Delivering Plant – Customer
You can customize your own custom master and custom KPIs.
Yes. ignio™ can predict it. Conflict, missing transports, version mismatch of the objects is included in this check.
ignio AI.ERPOps Impact Assessment supports ABAP Transports only.
ignio stores the new data again.
ignio AI.ERPOps sends IDoc dashboard link via email. User needs to have ignio authentication to access the dashboard link.
No. ignio™ AI.ERPOps only sends the link.
It is generic for certain standard SAP message types and error codes. User can configure customer specific self heal using customization.
You need to first run the work item API to find the latest IDoc ticket and then run IDoc API by using the IDoc ticket to get the IDoc data.
Yes. The segment level report is available in AI.ERPOps 4.1 and later.
Financial impact is in critical IDocs and error code detail report.
ignio AI.ERPOps provides Failed IDoc Financial impact summary and Business process wise summary from Dragon and above.
Yes, the HANA DB use cases are available in 4.1. Please refer our version wise catalog for details at https://digitate.atlassian.net/wiki/spaces/ID/pages/3776644850 . It is supported for both SUSE and Red Hat (RHEL) Linux flavors. However, the supported version would depend on what AIOps support as OOB.
The use cases are for SAP S/4HANA database. That means, a use case works for HANA DB users. Foe example, users who connect to HANA DB for modelling usage, admin users or business/functional users who execute views based programming.
No. The product currently does not have any capability that directly helps in migration. But the existing capabilities are supported on S/4 HANA and thus can be utilized during migration as well.
Yes, HANA DB monitoring is supported in ignio™ AI.ERPOps Dragon releases and later.
Yes. It is possible to create an ITSM ticket.
Not at the moment. You can download in .csv format and can do the modification.
ignio™ is providing consolidated list of Open PO including financial impact of open PO which has impact on regular MRP run. ignio is providing open PO and self heal to close the open POs based on different selection.
Yes, based on use case feasibility, customization can be done in ignio™ AI.ERPOps.
It can be developed in Studio only.
Yes, ignio™ AI.ERPOps have compliance capability to cover SAP Basis key parameters, Operating System and Database controls.
Refer to Compliance Configuration Manual : Eagle | AI.ERPOps 5.0 | Compliance Configuration Guide
Refer to Compliance User Manual : Eagle | AI.ERPOps 5.0 | Compliance BASIS DB OS Functional User Guide
Yes. For each plant, sales organization, production organization and so on, you need to create a separate node for one time task.
You can use data sources in case of large numbers.
Yes.
SAP user entity discovery is supported.
Blueprint ingestion for SAP instances can be done through file.
For more information, see Eagle | Blueprint Configuration Manual 5.0 – ignio Docs – Confluence (atlassian.net)
SAP business processes are not supported in blueprint.
ignio™ provides an intuitive dashboard that provides a detailed ABAP dump analysis with categorization and SAP best practice recommendations for exceptions and errors.
It summarizes all the work items which are being executed based on configurations, for example, every 5 minutes.
Approval is through email. ‘Approved’ or ‘Rejected’ must be written in email subject while replying.
ignio AI.ERPOps supports auto refresh in System Health Check and IDoc Management as a part of Govern dashboard.
SAP Ariba is in a roadmap.
No. ignio™ AI.ERPOps does not have any reference use cases.
You can find the ignio™ AI.ERPOps catalogue at Eagle | AI.ERPOps 5.0 | Catalogs:
Download the excel file to read in detail. In case you do not have access to the attached link, connect with your Digitate Alliance representative.