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.