Hi, I provide training in SAP UI5. Also feel free to checkout my new web page https://saptechblog.com
Adobe forms

ABAP Dictionary Based Interface

 

If we create interface to be used in ABAP print programs then we should go for ABAP based dictionary interface. The same can be done using the smart form based interface also but it is not recommended due to the following reasons.

1. Get the wrong parameters and XSF/ XDF parameters are not allowed

2. If the spool request contains several PDF documents ,only one PDF document will be returned back

3. Only ABAP dictionary based allow you to determine the settings from BCS(Business Communication service)

Note: If several forms are going to use the same interface, then think about optional parameters to provide flexibility to the form.

Components of Form:

Form Interface: Form interface consist of import, Export and Exceptions.

Import:

The import parameter defined for the interface is used to pass application data to form at run time.

clip_image002

Export:

Export parameters cannot be created for ABAP Dictionary based form. It can only be created with those interfaces that are of type Smart form based.

clip_image004

Exceptions:

Exceptions can be raised in the ABAP dictionary based interface. These are traditional exception concepts that can be raised by

Raise exception

Or

Message E001(ZCSK) raising <exception >.

If the exception is raised in the interface it will be actually raised in the generated interface. Hence by querying the SY-SUBRC of the generated interface exceptions can be handled.

There are also parts to an interface that are actually invisible from outside, i.e., they cannot be accessed from the application program. Among them are the global definitions, initialization coding, and currency/unit fields.

clip_image006

Global definitions:

Coming to the global definitions of the interface, it consists of global data, types and field symbols.

Global types: Types and table types required for the data declaration can be declared here.

clip_image008

Global Data: Variables, work area and internal table required for the code initialization of the interface can be declared here. Type declared using global types can be referred here.

clip_image010

Field symbols: Field symbols can be declared in the field symbols tab to be used in the interface coding.

clip_image012

Initialization:

In initialization the data coming inside the interface can be changed before it is sent to the form.

In the code initialization we can make use of the global definition and interface parameters by entering the field names in importing or exporting parameters as per their needs. Fill those you read under input parameters and those you write under output parameters.

Additionally data can also be declared using the data statement. These data’s are local and cannot be used in the form.

clip_image014

In the Code initialization, we can call the subroutines written in the Form Routines.

Currency and Quantity fields:

It is used to distinguish between internal and external format of currencies and quantities. The type of external format (Whether or not it should contain decimal points) depends on the reference field. In case if you want to provide the reference field to a component of structure or internal table then specify the field name as struct-fieldname or itab-fieldname.

About Arun

0 Comments:

Post a Comment

Powered by Blogger.