mySAP Technical

How to add Custom Subscreen and Field to VL02N using BAdI

2018-10-06T03:22:00.000-07:00

In order to implement a BAdI,we have to create a function group.
Create a function group using SE37.

Open the Function group in SE80. Activate it.

After activation check the status

Select Function group and right click on it.
Right click -> Create -> Screen

Program name will be come like SAPL Followed by Function Group.
Give the screen number example 9000,9001..etc.

Give the screen decription and select screen type as Subscreen.

Go to Layout as shown below

Create or Design the screen as required and provide field parameters.
In this case Data Base table field is referred as new field,which is already
appended in LIPS using SE11.
Save and activate it.

Now goto SE18 and open the Badi name (LE_SHP_TAB_CUST_ITEM).

Select Implementatio -> Create in Menu path

Give some name to it.

Provide short text and click on Method ACTIATE_TAB_PAGE.

Write code to activate extra subscreen in VL02N.

Activate the implementation.

Go to VL02N and check at Item level for newly added Subscreen and field.

Overview of OOP's in ABAP/4

2012-06-26T04:45:00.000-07:00

OBJECT ORIENTED PROGRAMMING IN ABAP/4

Class : A Class is a user defined data type with attributes,method types and events for a particular entity or business scenario or business application.
Class creation is of 2 step process :
1) class definition 2) class implementation

Object : Objects are instances of classes
Each object has unique identity i.e, memory and its own attributes.
Once an object is created,we have an instance of class with separate memory

Object creation is also of 2 step process.
1) Object/Instance declaration 2) Object creation

Components of a Class :

Attributes : Any data,variables,constants declared within a class are called as attributes of a class
Methods : Methods contain a block of code,providing some functionality for a class. These are similar to function modules in ABAP. Methods can access all the attributes of a class.
Events : Event is a mechanism by which method of one class can raise method of another class, without the hazard of instantiating that class.
Interfaces : Interfaces are similar to classes which contain methods. These are mainly used to extend the scope or functionality of the class.
Interfaces contains methods without any implementation.
where as a class contains methods with implementation.
Interface can be used by 'n' no of classes to extend the functionality of the class.
All the interface methods will be automatically copied to the classes in a particular class without effecting the other classes.

Instance and Static Components :

Instance Component : These components exists separately in each instance(Object) of the class and are referred using instance components selector using '->'.

Static Component: These components exists globally for a class and are referred to using static component selector '=>'.

Visibility components :

Each class component has a visibility
In ABAP Objects,the whole class definition is separated into three visibility section.
PUBLIC : Data declared in public section can be accessed by the class itself, by its subclasses as well as by other users outside the class.
PROTECTED : Data declared in the protected section can be accessed by the class itself, and also by its subclasses but not by external users outside the class.
PRIVATE : Data declared in the private section can be accessed by the class only, but not by its subclasses and by external users outside the class.

Global Class and Local Class :

Classes in ABAP Objects can be declared either globally or locally.

Global Class : Global classes and Interfaces are defined in class builder using SE24 in ABAP workbench.
All ABAP programs in an R/3 system can access the global classes.

Local Class : Local classes are defined in an ABAP program (SE38) and can only be used in the program in which they are defined.

Constructors :

These are special type of methods.
Constructor method is executed automatically whenever a object is created or instantiated.
These methods are mainly used to set default values in a class.
constructor method is called for each instance is created.

Instance Constructor : The name of the instance constructor method is 'constructor'.
These methods have only importing parameters.
There are no exporting parameters.

Static Constructor : this method is executed automatically whenever a first call to the class is made.
The static constructors will not have any importing or exporting parameters.
Name of the static constructor is 'class_constructor'.

FINAL and FRIENDS:

FINAL: It is a keyword which specifies whether inheritance is possible or not.
If FINAL option is selected, we cannot create inheritance (or) the class cannot be inherited.
If ‘FINAL’ option is not selected, we can create inheritance.

FRIENDS: By default , the child class cannot access the private variables of a SUPER class.
It can access only PUBLIC&PROTECTED variables.
FRIEND’ is a concept which is used to access the PRIVATE variables of a SUPER class.
So, To access the PRIVATE variables of a super class, the SUPER class has to treat the child as a friend.

OOP's Concepts :

There are 4 OOP's concepts.

1)Inheritance : In OO ABAP we use an existing class to derive a new class (child class). The new class contains the attributes of the parent class (derives according to the visibility of attributes and methods) in addition to new attributes and methods added to it. The child class derives all the attributes and methods declared in parent class as public visibility. The child class can not inherit private members. The protected members in parent class are derived in child class but their visibility changes to private.

2)Abstraction : It is a class which contains methods with implementation as well as methods without implementation.

we cannot create an object to the abstract class instead create an object to the child class and call the methods(Hiding the main class).

3)Encapsulation : Through encapsulation we restrict the visibility of attributes and methods in the object.

4) Polymorphism : It is a concept by which the same method names will behave differently in different classes i.e each method will have its own implementation in different different classes but with the same name.

Transaction code for a Maintainance Table

2010-10-24T11:15:00.000-07:00

How to Create T Code for a Maintainance Table
Create T Code using SE93

Provide short text and select Transaction with Parameters(parameters transaction)

Provide Transaction as SM30 and select Skip initial screen check box.
In Default values section,Provide Table name and other details as below.

Finally Save the Application

How to down load Spool into PDF file in Local system

2010-10-06T09:01:00.000-07:00

Down Load Spool into PDF file in Local system.

Pick the spool number from SP01,which you want to down into PDF.

Execute RSTXPDFT4 Report in SE38.

Provide Spool number,which you picked from SP01 and file path,where to download.
Execute the report.

Spool will be now downloaded into PDF in local system.

Append SAP standard table

2010-08-10T02:54:00.000-07:00

It is a standard procedure to add new custom fields to the standard tables.
Append structure name should begin with ZZ or YY. This prevents name conflicts with fields inserted in the table by SAP.

Open LIPS table and click on Append structure.

Click on Create button as below

Provide structure name starts with ZZ or YY.

Give the Field name and data element and save and activate.

Usually it takes time ans its depends on data in the table.

Warehouse Management(WM) Interface

2010-08-03T06:37:00.001-07:00

Warehouse Management Involves in below modules.

Implementing Enhancement Point

2010-04-01T04:18:00.000-07:00

Implementing Enhancement :

Take an example like Inbound IDoc : IDOC_INPUT_INVOIC_MM
Go To SE37 and give Function module name as IDOC_INPUT_INVOIC_MM
Click on Display.

Click on Enhancement Source Code Button on Application tool bar

Now the Editor will be changed as below

Now put cursor on ENHANCEMENT-POINT and Right click
Go to Enhancement Implementation -> Create

Click on Creat Button

Give Enhancement Name and Description and press enter

Select your Enhancement and press enter

Now the Enhancement will be ready to Implement

Enhance the Logic between ENHANCEMENT - ENDENHANCEMENT as below

Save the code,Check the syntax and Activate the Code.

How to Debug the Outbound IDoc Programs/Function modules.

2010-03-23T22:58:00.000-07:00

Take Sales order Outbound IDoc Process as an example.
Put the Break points in outbound programs, where ever you want.
Enter T Code VA02 for changing the order.

Provide the Order number and Press enter.

In Menu Path: Extras -> Output -> Header -> Edit.

Select the Output type and Click on Repeat output button.

Now Select the Output type again and click on further data button.

Select Send with periodically scheduled job.

Click on Back.

Now click on Save. An entry will be created in NAST table, once order is saved.

Go to SE11 and Check the entry in NAST table by providing Application and Date.

Copy the Object Key.

Now Go to WE15 to process Outbound IDoc.
Provide Application, Object Key and Output Type. And Execute.

ABAP Debugger will be on.

SAP SD Flow with TCodes and Tables

2010-03-17T04:51:00.001-07:00

RFC Programming/Functionality in ABAP

2010-03-16T02:37:00.000-07:00

RFC Programming in ABAP

A remote function call is a call to a function module running in a system different from the caller's.

In the SAP System, the ability to call remote functions is provided by the Remote Function Call interface system (RFC).

RFC allows for remote calls between two SAP Systems (R/3 or R/2), or between an SAP System and a non-SAP System.

RFC functions running in an SAP System must be actual function modules, and must be registered in the SAP System as "remote".

When both caller and called program are ABAP programs, the RFC interface provides both partners to the communication.

The caller may be any ABAP program, while the called program must be a function module registered as remote.

REMOTE FUNCTION CALL (RFC) is an extension of CALL FUNCTION in a distributed environment.
Existing function modules can be executed from within a remote system (R/2 or R/3) via an RFC call.
This is done by adding a DESTINATION clause to the CALL FUNCTION statement.

RFC frees the ABAP programmer from having to program his own communications routines.

Parameters declared as type REFERENCE cannot be used in remote function calls.

TYPES OF Remote Function Calls :

Synchronous Remote Function Call.
Asynchronous Remote Function Call.
Transactional Remote Function Call.
Queue Remote Function Call.
Web Remote Function Call(Not Covered)

Synchronous Remote Function Calls :

Synchronous remote function calls (RFCs) are those where the user have to wait for their completion before continuing the calling dialog.

In simple terms , “ calling program must wait for the return values to perform further processing”.

Asynchronous Remote Function Calls :
Asynchronous remote function calls (aRFCs) are those where the user does not have to wait for their completion before continuing the calling dialog.
There are three characteristics of asynchronous RFCs :
When the caller starts an asynchronous RFC, the called server must be available to accept the request.
The calling program can receive results from the asynchronous RFC.

In simple terms , “ calling program need not wait for the return values to perform further processing”.

You must not use IMPORTING when calling aRFCs.

Transactional Remote Function Calls :

From Release 3.0 onwards, data can be transferred between two R/3 Systems reliably and safely via transactional RFC (tRFC).

The called function module is executed exactly once in the RFC server system.
The remote system need not be available at the time when the RFC client program is executing a tRFC.

If a call is sent, and the receiving system is down, the call remains in the local queue until a later time.
The calling dialog program can proceed without waiting to see whether or not the remote call was successful.

If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.

Transactional RFCs use the suffix IN BACKGROUND TASK.

Queue RFC :

qRFC With Send Queue
To guarantee an LUW sequence dictated by the application, the tRFC is serialized using queues.
It is therefore called queued RFC (qRFC). Due to the serialization, in R/3 a send queue for tRFC is created. This results in the general term qRFC with send queue.

ALE IDoc Creation steps with T Codes

2010-03-10T23:15:00.000-08:00

INBOUND IDOC

Segment : Create Segements Using WE31
IDoc Type : Create IDoc Type and Assign Segment to IDoc Type Using WE30
Release : Release Segements and IDoc Type using WE31 and WE30 Respectively
Message Type : Create Message Type Using WE81
And Assign IDoc Type to the Message Type Using WE82
Function Modules : Create Function Module Using SE37
Process Code : Create Process Code Using WE42
Characteristics : Maintain characteristics of Inbound Function Modules Using BD51
Relate FM,Msg Type : Assign Function Module to Message type Using WE57
Partner Profile : Create Partner Profile Using WE20
And Assing Message type under Inbound parameters

OUTBOUND IDOC

Segment : Create Segements Using WE31
IDoc Type : Create IDoc Type and Assign Segment to IDoc Type Using WE30
Release : Release Segements and IDoc Type using WE31 and WE30 Respectively
Message Type : Create Message Type Using WE81
And Assign IDoc Type to the Message Type Using WE82
Function Modules : Create Function Module Using SE37
Relate FM,Msg Type : Assign Function Module to Message type Using WE57
Partner Profile : Create Partner Profile Using WE20
And Assing Message type under Outbound parameters
Port : Create/Use Existing Port Using WE21

SAP R/3 Architecture

2010-03-10T23:07:00.001-08:00

SAP R/3 - Systems Applications and Products in 3 Tier Architecture.

Typical structure of an R/3 system is as below

Presentation Layer
Application Layer
Database Layer

Presentation Layer is nothing but the system/pc we/end user accesses to perform the activity

Application layer will receives the request from user(i.e, presentation layer) and performs the activity based on the request.

Database Layer is nothing but Database. when an activity is running in application layer and that particular activity needs some data than a request will come to Database layer,Database layer sends back the data.

Creating Custom BAPI - step by step

2010-03-09T02:39:00.000-08:00

Step 1: Create Structure/Structures for parameters, which we need in SE11

Use Data elements while creating structure fields

Step 2 : Create Function Module using SE37

Select Radio Button “Remote-Enabled Module”

Provide Import Parameters as below and select Pass by Value.

Provide Tables for output and Return table to handle Errors

Write the code to retrieve the data.

Save Check and Activate the function module. And go back
In Menu, Go to Function Module -> Release -> Release

Step 3 : Create Object type for Function Module
Create Object type in SWO1

Provide Object name,Name,Description,Program and Application

Open Node of Method and Select Method.
Now in Menu, Goto Utilities -> API Methods -> Add Method.

Provide Function Module,Which was created in Step 2 and Hit enter.

Check on Next.

Check all the parameters and click on Next

Click on Save.

Now Click on Save and Select Object Type.
In Menu, Goto Edit -> Change Release Status -> Object Type -> To Modeled

Click on Save

In Menu, Goto Edit -> Change Release Status -> Object Type -> To Implemented

In Menu, Goto Edit -> Change Release Status -> Object Type -> To Released

Now Select Function Module in Method.
In Menu, Goto Edit -> Change Release Status -> Object Type Component -> To Modeled

In Menu, Goto Edit -> Change Release Status -> Object Type Component -> To Implemented

In Menu, Goto Edit -> Change Release Status -> Object Type Component -> To Released

Finally Click On Generate.

Step 4 : Check it in BAPI Repository