mPower™ Blog Series

Customize SAP Mobile Apps with SIMPLE SAP CONFIGURATIONS – No Code Changes Required

Empowering IT Teams to Customize SAP Mobile Apps with SIMPLE SAP Configurations using our Proprietary “Customization & Extensions” Cockpit

The demand for mobilizing key business processes is on the rise. Enterprise IT customers across line of businesses such as Sales, Finance, Supply Chain, Operations and Field Services have empowered themselves in their personal lives with smartphones and tablets, creating a trend to have information ubiquitously available anywhere, anytime. This trend of processing and consuming information ubiquitously, anywhere and anytime has created enormous expectations from their enterprise IT teams to provide on On-Demand mobile solutions to conduct business. However, meeting this demand is next to impossible for IT, if a mix of Pre-packaged mobile apps and custom mobile app development is not considered within their long term strategy.

The Challenge of embracing pre-packaged mobile applications

With the current demand for enterprise mobile apps exponentially rising, IT is continuously evaluating pre-packaged mobile applications to meet this demand. However, most of the commercially available pre-packaged apps don’t meet most of their business requirements, creating a need for a platform/SDK that gives them to ability to quickly fine tune the pre-packaged app to meet business requirements such as:

  • Adding, Removing or Re-Sequencing Fields
  • Activating and Deactivating Specific Modules
  • BADI Implementations to Add Custom Business Rules
  • Applying Security Authorizations at the Field Level to Meet Security & SOD Requirements
  • Applying Custom Validations Logic

Despite the above IT Needs, most commercially available pre-packaged apps provide none to minimal customization options, making these pre-packaged mobile apps a non-viable option.

Change is here and it’s here to Stay

The Solution: A Customization and Extensions Cockpit for the Entire mPower™ Apps Suite

Innovapptive’s entire mPower Apps Suite now comes with a “Customization and Extension Cockpit” that provides our customers IT teams the flexibility and agility to achieve all the above customizations with simple CONFIGURATIONS. Yes, simple configurations, NO CODE CHANGE is needed.

How does the Customization and Extensions Cockpit Work?

Activating and Deactivating Modules and Transactions based on your business process scope

The mPower™ Apps Suite Customization and Extensions cockpit can be used to define the scope of transactions for your mobile business scenarios. Using the cockpit you can activate or deactivate the required modules and transactions based on your current business scope. For example, the Innovapptive mInventory mobile solution UI can be customized by activating and deactivating modules and/or transactions using the below cockpit. The scope change configuration can also be done at a Role level by using the Role column in the table.

Screen Shot 2014-07-01 at 1.19.46 PM

Example 1 – Module Scoping: Stock Overview is not in scope of your mobile business scenarios. Stock Overview module can be deactivated in the table for all the users. To restrict the usage of this module for a group of users this can be controlled by the security role(s) already defined in your SAP ERP. The Stock Overview module is deactivated in the custom table as shown in the screenshot below.

Screen Shot 2014-07-01 at 1.20.54 PM

Screen Shot 2014-07-01 at 1.22.15 PM

 Adding custom fields based on your business requirements

The “Customization and extensions cockpit” is available as a standard offering for the entire portfolio of the mPower™ Apps Suite. The “Customization and extensions cockpit” can be used to activate custom fields that are in scope of your specific business processes. The fields which are most commonly used in the back-end system are made available in the standard module of all our available mobile solutions.   You may require certain additional fields in SAP to be included in the UI of various transactions or certain fields from the standard UI may not be in use for your business scenarios. You can activate/deactivate these fields as long as they are not critical and mandatory for processing these transactions.

Screen Shot 2014-07-01 at 1.23.29 PM

Example 2 – Activating an SAP field that is not standard on the Mobile App: Shelf Life Expiration Date (SLED) and Manufactured Date (MFGD) are needed to be visible for the Receiver while performing a Goods Receipt. You can activate these fields on the Line Item Detail screen so they appear on the App UI for the receiver to review while performing the Goods Receipt.

Screen Shot 2014-07-01 at 1.24.29 PM

Deactivating fields based on your business requirements

Certain fields from the standard UI may not be in use for your business scenarios, you can deactivate these fields as long as they are not critical and mandatory for processing these transactions. You may also add custom fields beyond the standard fields available in SAP using the mInventory Extensions Cockpit.

BADI implementations to add custom business rules based on your business requirements

Business Add-Ins (BADI) implementation helps adding new functionality without disturbing the existing functionality. It also helps to add enhancements to the existing fields.

Applying Security Authorizations at the field level based on your security and SOD requirements

New fields added should have authorization from admin. Applying security authorization at the field level can be done by ensuring securing corporate data of the new fields added.  SOD helps to define strategy for doing Segregation of Duties effectively in an organizations that is spread across various systems and various geographical locations.

To learn more about this solution or to request a quote for your enterprise, please email us at sales@innovapptive.com or you can simply click here and complete this contact form and an Innovapptive sales associate will be in touch with you within 24-48 hours.

Share this post

Leave a comment

Your email address will not be published.