‹
Raising & Handling Non-class based exceptions - I
›
OO Design Pattern Decorator - Why do we need to use helper variable?
  • View
  • Comments
  • Leave a comment

Finding Hidden Function Group Includes

By | December 13, 2011 | Function Module | 509 views

When we generate Remote Enabled Function (RFC) or Update FM, system would generate some includes. These includes wont be displayed when see all the includes of the Function Group. So, lets see how to easily find them out.

RFC

Long time ago, I wrote about RFC Calls: Function Module Parameter Passing. In this post, I figured out the hidden include by using the naming standard.

System has generated the Include LZTEST_NPV03 (L+fgname+V+fmnumber) with subroutine ZTEST_NP_RFC (same name as the FM) which call the FM. This include is part of the RFC framework.

Update Module

Similarly to RFC include, generated include for Update Module follows the same naming standards. System will generate the include with name e.g. LZTEST_NPV04 (L+fgname+V+fmnumber).

Interface Include

Every FM, generates one interface include. This include follows naming std as LZTEST_NP$04 (L+fgname+$+fmnumber). I still need to figure out the purpose of this include, though.

Std option

We can also check display these generated includes in SE37. To find that out:

Advertisement
  1. Enter FM in SE37 & Display
  2. From the menu Goto > Further Options > Generated RFC/Update Include

Give it a try and check out FM’s hidden includes.

Share It!

Don't miss an Update

  • Related Post
    RFC Calls: Function Module Parameter Passing

    Parameter Passing in the RFC Function Module Calls Today we will discuss how system take care of the obligatory parameter passing in the RFC function module. Generally, when we call the FM without passing the obligatory parameter, system would raise the exception CALL_FUNCTION_PARM_MISSING and would lead to run time error. Now, when we call the…

    Read Post »
  • Related Post
    Function Module Exception Handling

    Exception handling is the integral part of the designing the application. By raising the exception, we are providing the oppertunity to the Caller program to handle the exception in its own way. Visit Raising & Handling Non-class based exceptions to learn more on exception handling and flow control with flow-chart. Checkout all post related to…

    Read Post »
Load comments

1 Comment

  • Abhishek | January 23rd, 2012 at 7:34 pm

    awesome blog

Comments on this Post are now closed. If you have something important to share, you can always contact me.

‹
Raising & Handling Non-class based exceptions - I
›
OO Design Pattern Decorator - Why do we need to use helper variable?
I'm SAP ABAP Consultant for more than a decade. I like to experiment with ABAP especially OO. I have been SDN Top Contributor.
Follow :
Author List Write A Post