Other Innowera Products
Select one of the above options to request Innowera's advanced business, enterprise and integration product to take SAP usability to the next level.
Data Extractor allows you to extract table or view data from SAP in an Excel File. The graphical filtering interface gets the most relevant data quickly, easily, and in a repeatable fashion, and includes the ability to filter the extract with existing Excel data.
Data Extractor is an extension/replacement of SE16, SE17, SQVI, SQ01 (SAP Quickview or Query) and is designed to work with large datasets in the fastest and most responsive manner possible.
Download data from SAP tables and views to various file types, such as Excel and MS-Access or to a text file.
Optionally, use Process Runner DB to download from SAP tables and views to other databases including Oracle, Sybase, My SQL, MS-SQL Server, and DB2, or use the built-in XML table to work even when you are not connected to a database.
Innowera provides a custom data extraction remote function that further extends Data Extractor with other useful business needs. Process Runner software is already designed to work with this custom function module.
|Max characters per record||Limited to 512 characters||Up to 4000 characters|
|Field exits||Does not execute field/conversion exits.||Can perform field/conversion exit (GLL is returned as GAL etc.)|
|Field overflow||Packed number may overflow and be truncated with *. unless OSS note is applied||Correctly delivers the output without any truncation or Overflow and without needing to apply OSS note.|
|Line level or record level authorization within table||Does not support line level Authorization or extraction. User will be able to extract all or none based on standard Table level authorization.||Supports line level authorization.
Customization available to control which tables and organizational level should be controlled on the Record (line) level. Very useful for global companies where table level data needs to be restricted by various company codes/organizational level.
|Dynamic table joins||You can use single table or table joins if defined by SAP as views. You cannot dynamically perform table join. Alternative to dynamic table join in standard system is to use process connection (chain) feature or use BAPI where available.||Dynamic Table joins are allowed. For example, you can request EKKO and EKPO together and specify join conditions between then. Process Runner proposes automatic join based on common primary keys but you can change this if required. Left Outer join is also supported. (Please note that SAP does not allow joining cluster, pool and most views)|
|*More features…||May not be available||Available|
Process Runner offers Pre-run and Post-run execution of other programs or scripts. Process Runner offers many advanced SAP automation capabilities, however if you want to further extend these capabilities with an external processes, you can do so with the Pre-run and Post-run integration that Process Runner offers.
With the Pre/Post-Run integration feature, any external .Exe (standard Executable), .Bat (Batch file), .VBS (VB script), or .JS (Java Script) file can be executed before or after each run.
An externally-called process can also receive important parameters from Process Runner that can be utilized to execute its own logic, and the called processes can also communicate back to Process Runner at the conclusion to provide end to end integration.
Some of the examples Pre/Post run external processes:
Custom tables and views are supported. A special mechanism ensures that downloads are faster and that the application is always responsive.
Using the inbuilt scheduler, one can schedule data extracts which do not require any manual/personal intervention whatsoever.
Process Runner has several uses during an SAP Upgrade, including during the Unicode conversion process. One of the challenges of non-Unicode to Unicode migration is the data quality check and validation following the migration. This challenge is magnified if a multiple code page (MDMP) system is being used. Download this case study to learn how Data Extractor can be used to quickly and easily validate the data migration processes.
Process Runner's easy graphical interface makes your data extract a breeze. Most novice users will be up and running in no time. The Data Dictionary Explorer allows business users to find the correct table/view by simply typing in the English description (no need to remember SAP-style table names anymore!).
This feature provides custom filtering for your data extract with the inbuilt Data Filter Builder, custom ABAP code, or by using existing Excel data.
You can also use Process Runner DB to extract data to XML or other databases.
Process Runner supports large data extracts up to the capacities of target platforms such as Excel/MS-Access 2003/2007/2010 or text output.
Using Process Runner the extract processes generally will not time out and will put less of a burden on your SAP system when compared to other methods. Use this method when you want to download data from SAP tables or views.
Process Runner works out of the box. It builds upon what SAP has already delivered, and no ABAP or Transports are required to be implemented for Process Runner to function.
If SAP-delivered standard extraction does not serve your purposes, an enhanced solution is available and Process Runner is already designed to use this customized solution once you decide to implement it. This approach will provide quick deployment capabilities to suit your exact requirements.
Process Runner implementation will be as SOX compliant as your SAP implementation is, and your auditor (apart from BASIS) will love that there is not a custom ABAP program involved.
With Process Runner, you are using the standard SOX compliant sets and features delivered by SAP.
In addition to the above, Process Runner DE supports many other features. Learn more.