HCM Processes & Forms: FPM forms? Let there be light…er uhm….PRINT!!!!

I have not blogged in a good while and figured if I came back, I better drop a banger (that’s what the “kids” call it, right?). Well, I guarantee you, this one is quite a doozy! (that’s what the “old folks” call it, right?). I will worry about which crowd I most appeal to later. For now…..let’s do this! I am about to rock your world and show you a “new” way to make printing your FPM forms for HCM P&F a whole lot easier….like super simple easy! Don’t believe me? Read on!

Background

Way back when SAP announced and released the FPM options for HCM Processes & Forms which effectively replaced Adobe Interactive Forms, the world rejoiced. When SAP said “nuh uh uh…not so fast” and let it be known that the only way to “print” FPM forms was to develop and Adobe form/layout in parallel and assign it in the configuration, the world let out a collective sigh. That just did not sit right with us HCM P&F folks. In fact, I can say that in all of my projects implementing FPM HCM P&F processes, not a single one ever implemented the “Adobe print form option”. Not ONE! In most cases, the customers would tell their users either:

Order to Invoice Sales Cycle using FM/BAPI’s

We keep getting requirements from businesses to create a Z Process to perform Order , Delivery and Invoicing in the background.

Although there are other option like BDC’s, here I am making attempt to do the same using FM/BAPI’s, this might be useful specially for Consultant who have just started working on Developments.

The Usage is typically for any Development where there is requirement for Mass Automaton of Order to Invoice generation or for a requirement where we need to perform the whole Order to Invoice process in background.

Expose SAP GUI Transaction in Fiori Launchpad

In this blog post, we will learn how to expose Standard SAP GUI Transaction in FIORI Launchpad.

1. Here we want to create Tile for standard SAP GUI Transaction i.e. ME42 in Fiori Launchpad

2. First check, if standard Fiori App is available for Transaction ME42, in this case, no standard Fiori app is available, so follow below steps to expose backend transaction to Fiori Launchpad

3. First Verify that the standard Transaction Me42 is SAP GUI for HTML.

Extending SAP FIORI App : My Inbox – Approve Purchase Order (F0402A)

Overview

This blog shares on how SAP FIORI App – My Inbox can be enhanced. FIORI extension is done on My Inbox – Approve Purchase Order (F0402A) enhancing custom field in PO Line Item data.    Custom screen enhancement is done on PO Line Item to add field ‘Last Price’. To display the field on FIORI screen, no enhancement is needed either in Odata, Workflow or UI. Appropriate CDS views related to My Inbox – Purchase Order app to be identified and enhanced to modify the UI output display.

Workflow Configuration

SAP Business Workflow configuration entries maintained for Workflow Task of Purchase Order

Transaction Code – SPRO

IDOC data extraction method for multiple segments using an RFC Function Module

Title

IDOC data extraction method for multiple segments using an RFC Function Module.

Introduction

In this document, we will discuss the process of extracting the IDOC data from multiple segments and sending it to a target system using an RFC function module.

Enabling the CFL custom fields with F4 help using SCFD_EUI transaction from SAP GUI

Custom fields can be enabled at GUI or FIORI launchpad either using CFL (Custom Fields Logic) or transaction code SCFD_EUI. In this blog I will be demonstrating the prominence of SCFD_EUI in enabling the custom fields with F4 help at the backend (SAP GUI).

Why to use SCFD_EUI instead of CFL?

There are few advantages for preferring SCFD_EUI over CFL

In CFL, customization of field suffix is not allowed as the suffix is predefined and cannot be changed. However, in SCFD_EUI we can change the suffix of the field as per the requirement.

ABAP Restful Application Programming : Real Time validation on field input in transactional Fiori Application

Introduction:

Main aim of any application is to keep the transactional document error free. That says how important is error handling and validations in the application process.

In this blogpost, I will explain how we can implement real time validations on field input in a transactional fiori application with ABAP RAP framework. Instead of executing the validations at the save in the end.

Interactable split-screen ALV (using CL_SALV_TABLE)

One ALV with headers and a second with details of selected row – quite a common use-case. And won’t it be practical to have all this in one screen, so users can check details quickly without constant back and forth between screens? This was indeed what users wanted and what I implemented for them.

In this post, I will describe how to make such a screen with two ALVs, utilizing CL_SALV_TABLE, displaying dependent information.

Finished split-screen

ABAP Restful Application Programming: Custom actions => Merge Draft entities into Active and switch to display mode

Introduction:

In this blog post, I will explain about “Custom actions” that can merge draft entities into Active and switch to display mode. An action in RAP is a non-standard modifying operation that is part of the business logic. The standard use case of an action is to change specific fields of a business object entity.

Problem statement:

In General, MODIFY ENTITIES can be used to change the required fields in an entity. That means, Active instance remains as active and Draft instance remains as Draft. But some business requirements expect us to convert those draft instances into active instances.

About ADS Font Trace

With the activation of ADS Font Trace by referring to Note 1717189, we can get the font processing log following the steps provided by 2216427 – How to generate a PDF with Additional Information – ABAP Scenario.

Simple Report by calling function module SE16N_EXTERNAL_CALL

Purpose 

I have been asked to make simple reports just for retrieving data from tables with all nice functions which you can use at SE16N, SE16H sort of SE transactions .

Well, there are many fancy UI report tools that you can create a fancy report, which are something like POWL or Fiori List, FPM, and WebUI. Of course, if you are good at using conventional SAP report tools like Report Painter, SAP QUERY, QuickView, and so on .. Wouldn’t be any problem considering that SAP has been providing  lots of report tools for user to avoid building SAP reports from scratch.

Editable CL_SALV_TABLE after release 756

Ever since the CL_SALV_TABLE class was released, one question was ever present – how to make it editable? For years the answer lied in taking advantage of the inheritance of the CL_SALV_TABLE, as presented in this post: http://zevolving.com/2008/12/salv-table-10-editable-salv-model-overcome-the-restriction-of-salv-model/.

I was among those using this method. But then the Release 756 came. And suddenly, all ALVs using it suddenly started reported error after error. I dived in and investigated the issue. To my surprise, I discovered that the very basis of this “edit-hack” was gone. The CL_SALV_TABLE class was no longer in the inheritance tree which enabled it to work!

Custom Print Preview In MIGO Transaction

Introduction:

In this blog I am going to explain how to add additional tab and print preview button in MIGO Transaction.

Normally in MIGO Transaction there is no standard print preview button available to preview the forms. Only way to preview the Form layout is by using another transaction MB90 only, But there is an way to achieve the print preview using a BADI by adding a custom tab and a print preview button to view the form layout.