Syntax Check for Leave

LEAVE TO LIST-PROCESSING

LEAVE TO LIST-PROCESSING.

Addition

... AND RETURN TO SCREEN scr.

Effect

Switches from "dialog processing" (module pool, screens) of the current transaction to "list processing". You can then use all the usual list layout commands ( WRITE , SKIP , ...).

After leaving the current screen, the list formatted in this way is displayed implicitly or explicitly by LEAVE SCREEN . Here, all list programming options are possible, e.g. line selection, F keys ,windows.

LEAVE LIST-PROCESSING continues with "Processing Before Output" ( PBO ) of the screen which controls the list processing.

After switching to list processing mode with SET PF-STATUS ... ,you are recommended to define a GUI (Graphical User Interface) of type List or List in dialog box .

Addition

... AND RETURN TO SCREEN scr.

Effect

LEAVE LIST-PROCESSING continues with "Processing Before Output" ( PBO ) of the screen scr.

Using LEAVE LIST-PROCESSING to leave list processing explicitly is only necessary in exceptional cases; normally, the standard F keys (F3 Back and F15 Exit ) are sufficient.

LEAVE TO SCREEN

LEAVE TO SCREEN scr.

Effect

Leaves the current screen and processes the screen scr . If scr = 0, processing in CALL mode continues after the CALL SCREEN statement. Otherwise, you branch to the transaction selection screen.

LEAVE TO TRANSACTION

LEAVE TO TRANSACTION tcod.

Addition

... AND SKIP FIRST SCREEN

Effect

Terminates the current processing and starts the (new) transaction tcod .

Examples

Start Transaction SM02 :

LEAVE TO TRANSACTION 'SM02'.

Restart current transaction:

LEAVE TO TRANSACTION SY-TCODE.

Addition

... AND SKIP FIRST SCREEN

Effect

Processes the first screen of the transaction in the background. If possible, the fields on this screen are filled with values from the SAP memory . Therefore, you should set the desired values with SET PARAMETER . If an error occurs when processing the initial screen (due to incorrect or imcomplete parameter values), this is reported and you must correct or complete the input manually on this screen.(86.5).

Related Post

Syntax for Insert data into Table and Insert part two

ABAP BADI PART FOUR

BADI PART FIVE

ABAP BADI PART SIX CALLING BADI AND ITS USES

BADI INTRODUCTION

Syntax for Insert Continued

Previously we have discussed regarding syntax for Insert data into table part one and part two.We have also learned regarding inserting data into a internal table. Here is the continuation for that.

Insert a program

Basic form

INSERT REPORT prog FROM itab.

Effect

Inserts the program prog from the internal table itab into the library. The internal table itab contains the source code; the lines of the table cannot be more than 72 characters long. The program attributes (type, date, ...) are set by the system, but you can change them manually or in the program (table TRDIR ).

Runtime errors

1 · INSERT_PROGRAM_INTERNAL_NAME : he program name prog is reserve internally; it begins with '%_T' .

2· INSERT_PROGRAM_NAME_BLANK : The program name prog must not contain any blanks
characters.

3· INSERT_PROGRAM_NAME_TOO_LONG : The program name prog is too long; it cannot be more than 8 characters long.

4· INSERT_REPORT_LINE_TOO_LONG : One of the source code lines is longer than 72 characters.

INSERT - Insert text elements

Basic form

INSERT TEXTPOOL prog ...FROM itab ...LANGUAGE lg.

Effect

Assigns the text elements in the internal table itab to the program prog and the language lg and inserts them in the library. The line structure of the table itab is described in the section Text elements .

Example

The following program uses the internal table TAB to set the text elements of the program PROGNAME .

DATA: PROGRAM(8) VALUE 'PROGNAME',
TAB LIKE TEXTPOOL OCCURS 50 WITH HEADER
LINE.
TAB-ID = 'T'. TAB-KEY = SPACE. TAB-ENTRY =
'Sales'.
APPEND TAB.
TAB-ID = 'I'. TAB-KEY = '200'. TAB-ENTRY = 'Tax'.
APPEND TAB.
TAB-ID = 'H'. TAB-KEY = '001'. TAB-ENTRY = 'Name
Age'.
APPEND TAB.
TAB-ID = 'S'. TAB-KEY = 'CUST'. TAB-ENTRY =
'Customer'.
APPEND TAB.
TAB-ID = 'R'. TAB-KEY = SPACE. TAB-ENTRY = 'Test
program'.
APPEND TAB.
SORT TAB BY ID KEY.
INSERT TEXTPOOL PROGRAM FROM TAB LANGUAGE
SY-LANGU.

The internal table should be sorted by the components ID and KEY to enable faster access to the text elements at runtime. However, this is not obligatory. The component LENGTH (see text elements ) for the length of a text element does not have to be set explicitly. In this case - as in the example - the actual length of the text element is used.

The value of LENGTH cannot be smaller than the text to which it applies. If your length specification is too short, it is ignored by INSERT and the actual length is used instead. On the other hand, larger values are allowed and can be used to reserve space for texts that may be longer when translated into other languages.

Related Post

Syntax for Insert data into Table

LESSON 1 DATA PORTS IN IDOC

LESSON 2 DEFINING PARTNER PROFILE FOR IDOC

LESSON 3 PARTNE RPROFILES AND PORTS IN IDOC

LESSON 4 CONVERTING DATA INTO IDOC SEGMENTS

Syntax for Insert into a Internal Table

Variant 1

INSERT [wa INTO|INITIAL LINE INTO] itab [INDEX idx].

Effect

Inserts a new line into an internal table.

If you specify wa INTO , the new line is taken from the contents of the explicitly specified work area wa .

When using INITIAL LINE INTO , a line containing the appropriate initial value for its type is inserted into the table.

If you omit the specification before itab , the new line is taken from the header line of the internal table itab .

INDEX idx specifies the table index before which the line is inserted into the table itab . If the table has exactly idx - 1 entries, the line is appended to the table.

Within a LOOP , on an internal table, you do not have to specify the insertion point with INDEX idx . The source table is then inserted before the current LOOP line in the target table.

The return code value is set as follows:

When specifying the insertion point with INDEX idx :

SY-SUBRC = 0 The entry was inserted.
SY_SUBRC = 4 Index specification too large.

The entry was not inserted because the table has fewer than idx - 1 entries.

Return code value If the insertion point is not specified, the is set to 0.

Inserting lines within a LOOP ... ENDLOOP structure affects subsequent loop passes.

Invalid index specifications (for example, idx <= 0), result in a runtime error. Example

Insert values into a table of whole numbers:

DATA: VALUE TYPE I,
ITAB TYPE I OCCURS 100 WITH HEADER LINE.
ITAB = 5.
VALUE = 36.
INSERT ITAB INDEX 1.
INSERT VALUE INTO ITAB INDEX 2.
INSERT INITIAL LINE INTO ITAB INDEX 2.

The table ITAB now contains three lines with the values 5, 0 and 36.

Variant 2

INSERT LINES OF itab1 [FROM idx1] [TO idx2] INTO itab2 [INDEX idx3.

Effect

Inserts the internal table itab1 or a section of itab1 into the internal table itab2 .

As with variant 1, INDEX idx3 is to specifies the table index before which you want to insert in the target table itab2 .

Within a LOOP , on an internal table, you do not have to specify the insertion point with INDEX idx3 . The source table is then inserted before the current LOOP line in the target table.

By specifying FROM idx1 or TO idx2 , you can restrict the line area from which the source table itab1 is taken. If there is no FROM specification, the line area begins with the first line of itab1 . If there is no TO specification, the line area ends with the last line of itab1 . This means that the whole table is inserted, if neither a FROM nor a TO is specified.

Return code value

The is set as for variant 1.

You can use DESCRIBE TABLE itab1 LINES ... to determine the size of the table itab1 before or after the INSERT statement and thus establish how many lines were actually inserted into the
table.

Inserting lines within a LOOP ... ENDLOOP structure affects subsequent loop passes. Invalid index specifications (for example, idx <= 0), result in a runtime error. Performance

Inserting a line into an internal table incurs index maintenance costs which depend on the insertion point.

For example, inserting a line in the middle of a 100-byte wide internal table with 200 entries requires about 90 msn (standardized microseconds). If you want to insert the contents of one internal table into another internal table, you incur index maintenance costs only once with the variant INSERT LINES OF ... . Compared with a LOOP which inserts the lines of the source table oneby- one into the target table, this represents a distinct improvement in performance.
Inserting a table of 500 lines with a 100-byte line width in the middle of a similar size table can thus be amde up to 20 times faster.(84.4)

Related Post

Syntax for Insert data into Table
LESSON 5 DEVELOPING OUTBOUND IDOC FUNCTION

LESSON 6 CREATION OF IDOC DATA

Insert Data into Table Syntax Part two

This Insert data into table is in continuation with previous post .

Variant 2

INSERT dbtab. or
INSERT *dbtab. or
INSERT (dbtabname) ...

Additions

1. ... FROM wa
2. ... CLIENT SPECIFIED

Effect

These are the SAP -specific short forms for the statements explained under variant 1.

1. · INSERT INTO dbtab VALUES dbtab. or
2. · INSERT INTO dbtab VALUES *dbtab. or
3. · INSERT INTO (dbtabname) VALUES wa.

When the command has been executed, the system field SYDBCNT contains the number of inserted lines (0 or 1).

The return code value is set as follows:

SY-SUBRC = 0 Line successfully inserted.
SY_SUBRC = 4 Line could not be inserted, since a line with the same key already exists.

Example

Add a line to a database table:

TABLES SAIRPORT.
SAIRPORT-ID = 'NEW'.
SAIRPORT-NAME = 'NEWPORT APT'.
INSERT SAIRPORT.

Addition 1

... FROM wa

Effect

The values for the line to be inserted are not taken from the table work area dbtab , but from the explicitly specified work area wa . The work area wa must also satisfy the conditions described in variant 1. As with this variant, the addition allows you to specify the name of the database table directly or indirectly.

If a work area is not explicitly specified, the values for the line to be inserted are taken from the table work area dbtab if the statement is in a FORM or FUNCTION where the table work area is stored in a formal parameter or local variable of the same name.

Addition 2

... CLIENT SPECIFIED

Effect

As for variant 1.

Variant 3

INSERT dbtab FROM TABLE itab. or
INSERT (dbtabname) FROM TABLE itab.

Additions

... CLIENT SPECIFIED
... ACCEPTING DUPLICATE KEYS

Effect

Mass insert: Inserzts all lines of the internal table itab in a single operation. The lines of itab must satisfy the same conditions as the work area wa in variant 1.

When the command has been executed, the system field SYDBCNT contains the number of inserted lines.

If the internal table itab is empty, SY-SUBRC and SY-DBCNT are set to 0 after the call.

Addition 1

... CLIENT SPECIFIED

Effect

As for variant 1.

Addition 2

... ACCEPTING DUPLICATE KEYS

Effect

If a line cannot be inserted, the processing does not terminate with a runtime error, but the return code value of SY-SUBRC is merely set to 4. All the remaining lines are inserted when the
command is executed.

The return code value is set as follows:

SY-SUBRC = 0 All lines successfully inserted. Any other result causes a runtime error .(82.6)

Related Post

LESSON 10 SENDING IDOC VIA STANDARD R3 SYSTEM

LESSON 11 IDOC OUTBOUND TEIGGER PART TWO

Syntax for Insert in data base table

Variants

1. INSERT INTO dbtab VALUES wa. or INSERT INTO (dbtabname) VALUES wa.

2. INSERT dbtab. or INSERT *dbtab. or INSERT (dbtabname) ...

3. INSERT dbtab FROM TABLE itab. or INSERT (dbtabname) FROM TABLE itab.

Effect

Inserts new lines in a database table .

You can specify the name of the database table either in the program itself in the form dbtab or at runtime as the contents of the field dbtabname . In both cases, the database table must be defined in the ABAP/4 Dictionary . If the program contains the name of the database table, it must also include a corresponding TABLES statement.

Normally, lines are inserted only in the current client. Data can only be inserted using a view if the view refers to a single table and was defined in the ABAP/4 Dictionary with the maintenance status "No restriction".

INSERT belongs to the Open SQL command set.

You cannot insert a line if a line with the same primary key already exists or if a UNIQUE index already has a line with identical key field values.

When inserting lines using a view , all fields of the database table that are not in the view are set to their initial value - if they were defined with NOT NULL in the ABAP/4 Dictionary . Otherwise they are set to NULL .

Since the INSERT statement does not perform authorization checks , you must program these yourself.

Lines specified in the INSERT command are not actually added to the database table until after the next ROLLBACK WORK .Lines added within a transaction remain locked until the transaction has finished. The end of a transaction is either a COMMIT WORK , where all database changes performed within the transaction are made irrevocable, or a ROLLBACK WORK , which cancels all database changes performed within the transaction.

Variant 1

INSERT INTO dbtab VALUES wa. or INSERT INTO (dbtabname) VALUES wa.

Addition

... CLIENT SPECIFIED

Effect

Inserts one line into a database table.

The line to be inserted is taken from the work area wa and the data read from left to right according to the structure of the table work area dbtab . Here, the structure of wa is not taken into account. For this reason, the work area wa must be at least as wide (see DATA ) as the table
work area dbtab and the alignment of the work area wa must correspond to the alignment of the table work area.

Otherwise, a runtime error occurs. When the command has been executed, the system field SYDBCNT contains the number of inserted lines (0 or 1).

The return code value is set as follows:

SY-SUBRC = 0 Line was successfully inserted.

SY_SUBRC = 4 Line could not be inserted since a line with the same key already exists.

Example

Insert the customer Robinson in the current client:

TABLES SCUSTOM.
SCUSTOM-ID = '12400177'.
SCUSTOM-NAME = 'Robinson'.
SCUSTOM-POSTCODE = '69542'.
SCUSTOM-CITY = 'Heidelberg'.
SCUSTOM-CUSTTYPE = 'P'.
SCUSTOM-DISCOUNT = '003'.
SCUSTOM-TELEPHONE = '06201/44889'.
INSERT INTO SCUSTOM VALUES SCUSTOM.

Addition

... CLIENT SPECIFIED

Effect

Switches off automatic client handling. This allows you to insert data across all clients even when dealing with clientspecific tables. The client field is then treated like a normal table field which you can program to accept values in the work area wa that contains the line to be inserted.

The addition CLIENT SPECIFIED must be specified immediately after the name of the database table.

Example

Insert the customer Robinson in client 2:

TABLES SCUSTOM.
SCUSTOM-MANDT = '002'.
SCUSTOM-ID = '12400177'.
SCUSTOM-NAME = 'Robinson'.
SCUSTOM-POSTCODE = '69542'.
SCUSTOM-CITY = 'Heidelberg'.
SCUSTOM-CUSTTYPE = 'P'.
SCUSTOM-DISCOUNT = '003'.
SCUSTOM-TELEPHONE = '06201/44889'.
INSERT INTO SCUSTOM CLIENT SPECIFIED VALUES
SCUSTOM.

Initialization Syntax Check

Basic form

INITIALIZATION.

Effect

Processing event.

Executed before the selection screen is displayed.The parameters (PARAMETERS ) and selection criteria (SELECT OPTIONS ) defined in the program already contain default values (if specified). You can assign different values here and also change the database-specific selections.

In contrast to R/2 , this event is also executed during background processing.

Example

Define the last day of the previous month as the key date:

PARAMETERS QUAL_DAY TYPE D DEFAULT SYDATUM.

INITIALIZATION.

QUAL_DAY+6(2) = '01'.

QUAL_DAY = QUAL_DAY - 1.

INITIALIZATION is executed in the following steps:

Specify default values for the selections. Execute the event INITIALIZATION. Import variant (if used to start the report).

On SUBMIT , the values specified for each WHERE clause are also transferred, if necessary. Execute the event AT SELECTION-SCREEN OUTPUT , if it occurs in the report (unlike INITIALIZATION , this event is always executed for PBO of a selection screen). Display selection screen.

Transport the screen fields containing user input to the report fields. Continue with START-OF-SELECTION .

Since INITIALIZATION is only executed once when you start the report, it is not suitable for screen modifications such as suppressing individual parameters (LOOP AT SCREEN , MODIFY SCREEN ) because these changes would disappear again when the user pressed ENTER. The correct event for screen modifications is AT SELECTION-SCREEN OUTPUT .(80.5)


SAP WORK flow in sales and distribution 1
SAP WORK flow in sales and distribution 2
SAP WORK flowin sales and distribution 3

Syntax for Infotypes

Basic form

INFOTYPES nnnn.

nnnn between 0000 and 0999: HR master data info types
nnnn between 1000 and 1999: HR planning data info types
nnnn between 2000 and 2999: HR time data info types
nnnn between 3000 and 8999: Not yet used
nnnn between 9000 and 9999: Customer-specific info types

Additions

1. ... NAME c
2. ... OCCURS occ
3. ... MODE N
4. ... VALID FROM begin TO end

Effect

Declares the HR info type nnnn . Creates an internal table as follows:

DATA BEGIN OF Pnnnn OCCURS 10.

INCLUDE STRUCTURE Pnnnn.

DATA END OF Pnnnn VALID BETWEEN BEGDA AND

ENDDA.

Example

INFOTYPES: 0000, 0001, 0002.

Addition 1

... NAME c

Effect

c is a name

c is a name up to 20 characters long. Creates an internal table as follows:

DATA BEGIN OF c OCCURS 10.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN BEGDA AND ENDDA.

Example

INFOTYPES: 0005 NAME VACATION, 0006 NAME ADDRESS.

Addition 2

... OCCURS occ

Effect

occ is a number for the OCCURS value. Creates an internal table as follows:

DATA BEGIN OF c OCCURS m.
INCLUDE STRUCTURE Pnnnn.
DATA END OF c VALID BETWEEN BEGDA AND ENDDA.

Example

INFOTYPES 0003 OCCURS 1.

Addition 3

... MODE N

Applies only to the HR logical databases PNP and PCH .

Effect

The info type tables are not filled by GET PERNR (logical database PNP ) or GET OBJEC (logical database PCH ). The effect of the INFOTYPES statement is then the same as the data declaration of an internal table .

Example

INFOTYPES: 2001 MODE N, 2002 MODE N, 2003 MODE N.

Addition 4

... VALID FROM begin TO end.

... VALID FROM begin TO end.

Effect

This addition should only be used with the logical database PNP .

GET PERNR retrieves only those info type records which are valid within the time range ( begin and end ) specified. begin and end are dates with the format YYYYMMDD.

Example

INFOTYPES: 0007 VALID FROM 19910101 TO 19911231.

Note

Each info type has a formal description in the ABAP/4 Dictionary as table Pnnnn .

If you enter SHOW INFOTYPES nnnn in the editor command line, the system displays information about the info type nnnn .

If you enter SHOW INFOTYPES * , you see a list of all info types.


Work flow for MM PART 5

Syntax for Include

INCLUDE prog

Basic form

INCLUDE prog.

Effect

Includes the program prog in the main program for syntax check and generation purposes. Include programs are used to divide very large programs into smaller more manageable units. They also allow you to create common program components.

Example

INCLUDE LSPRITOP.

The whole of an INCLUDE statement must appear on one line where it is the only statement allowed. The include program must consist of complete statements (and comments). You can use the service report RSINCL00 to generate reference lists for include programs.

INCLUDE STRUCTURE

Basic form

INCLUDE STRUCTURE rec.

Effect

When you define a structure rec (with DATA or TYPES ), this statement copies the components of the structured data type subRec to the structure rec . Since you can define nested data structures (i.e. structures with sub-structures) starting from Release 3.0, you should use INCLUDE STRUCTURE only if you want to introduce types in a program first and nested structures in a later step.


A data definition DATA: BEGIN OF rec.
INCLUDE STRUCTURE subRec.
DATA: END OF rec.

is equivalent to

DATA rec LIKE subRec.

You are recommended to use the second formulation. Even if the structure rec to be defined contains additional components, instead of

DATA: BEGIN OF rec,
...
INCLUDE STRUCTURE subRec.
DATA: ...
END OF rec.

you should use

DATA: BEGIN OF rec,
...
rec LIKE subRec,
...
END OF rec.

so that subRec can be referenced as a sub-structure of rec .

Although " INCLUDE STRUCTURE subRec. " breaks up the substructure subRec into its components, the alignment of subRec is retained. This means that padding fields may be inserted before the first and/or before the last component of subRec in rec .

INCLUDE TYPE

Basic form

INCLUDE TYPE subRec.

Effect

When you define a structure rec (with DATA or TYPES ), this statement copies the components of the structured data type subRec to the structure rec .

Since you can define nested data structures (i.e. structures with sub-structures) starting from Release 3.0, you should use INCLUDE TYPE only if you want to introduce types in a program first and nested structures in a later step.(78.8).


Work flow for MM PART 6
Work flow for MM PART 7

Syntax Check for IMPORT part two

We have all ready discussed regarding syntax of IMPORT key word and this post is the continuation of it .

Variant 2

IMPORT f itab FROM DATABASE dbtab(ar) ID key.

Additions

1. ... TO g (for each field f to be imported)
2. ... MAJOR-ID maid (instead of ID key )
3. ... MINOR-ID miid (together with MAJOR-ID maid )
4. ... CLIENT h (after dbtab(ar) )
5. ... USING form

Effect

Imports data objects (fields, field strings or internal tables) with the ID key from the area ar of the database dbtab

The return code value is set as follows:

SY-SUBRC = 0 The data objects were successfully imported.

SY_SUBRC = 4 The data objects could not be imported, probably because an incorrect ID was used.
The contents of all objects remain unchanged.


Example

Import two fields and an internal table:

TABLES INDX.

DATA: INDXKEY LIKE INDX-SRTFD,F1(4),
F2 TYPE P,BEGIN OF TAB3 OCCURS 10, CONT(4),
END OF TAB3.

INDXKEY = 'INDXKEY'.

IMPORT F1 F2 TAB3 FROM DATABASE INDX(ST) ID

INDXKEY.

The structure of fields, field strings and internal tables to be imported must match the structure of the objects exported to the dataset. In addition, the objects must be imported under the same name used to export them. If this is not the case, either a runtime error occurs or no import takes place.

Exception: You can lengthen or shorten the last field if it is of type CHAR , or add/omit CHAR fields at the end of the structure.

Addition 1

... TO g (for each field f to be imported)

Effect

Takes the field contents stored under the name f from the database and places them in g .

Addition 2

... MAJOR-ID maid (instead of ID key )

Addition 3

... MINOR-ID miid (together with MAJOR-ID maid )

Effect

Searches for a record with an ID that matches maid in the first part (length of maid ) and - if MINOR-ID miid is also specified - is greater than or equal to miid in the second part.

Addition 4

... CLIENT h (after dbtab(ar) )

Effect

Takes the data from the client h (only with client-specific import/export databases).

Example

TABLES INDX.
DATA F1.
IMPORT F1 FROM DATABASE INDX(AR) CLIENT '002'
ID 'TEST'.

Addition 5

... USING form

Effect

Does not read the data from the database. Instead, calls the FORM routine form for each record read from the database without this addition. This routine can take the data key of the data to be retrieved from the database table work area and write the retrieved data to this work area schreiben; it therefore has no parameters.(76)

The previous post of the blog deals with SAP XI ADAPTER CONCEPT.


ERP implementation process and advantages
ERP advantages and erp project launch

XI Adapters verses Proxies

It is important to understand that proxies and adapters are the two alternatives for connecting XI to an application system.

Typically for an existing system (any external system or even ‘traditional’ SAP systems that only communicate via RFC and IDoc), the interface semantics cannot be changed. Also in many cases a specific, proprietary wire protocol must be used. This is exactly the scope of adapters.

This is also the premise of ‘outside-in’ integration or ‘a posteriori’ integration . In the case of new SAP applications (ABAP or Java) the interface development process has changed. The interface is designed centrally in the Integration Repository.]

From the interface definition a proxy is generated in ABAP or Java. The proxy is deployed on the application system, and the business application is built around it. This is the premise of inside-out integration (integration by design).

A proxy is a fragment of code in ABAP or Java which serves 2 purposes:

1 . Convert the data structures (ABAP or Java) into XML messages and vice-versa Establish connectivity with the XI Integration Server A proxy hides such technical details from the application developer.

2 . It is important to note that for proxy communication, no specific adapter configuration is required.

However from the technical aspect, the proxy runtime itself resides on the adapter framework. The point is that there is no protocol conversion necessary for communicating with XI using proxies.

Connectivity with SAP applications :

The choice of adapters vs proxies comes into play when connecting SAP applications .

Before WebAS 6.20 the only connectivity option in/out of SAP system is RFC/BAPI/IDoc.

Starting with the WebAS 6.10 the native HTTP connectivity has been added to the basis layer .

Starting with the WebAS 6.20, each application system has its own local integration engine and is
therefore able to connect to XI via proxies over HTTP / SOAP with attachments (XI protocol).

Where is the adapter in SAP ?

The following diagram illustrates the position of adapters of sap.

Related posts :

SAP XI connectivity
SAP XI Adapter introduction

XI Adapters hosted on J2EE

All R/3 systems and under can communicate using RFC and IDoc only. Therefore the RFC/IDoc adapter is necessary to integrate these systems with XI Even SAP systems based on WebAS .20 and above, still rely heavily on RFC/IDoc interfaces and therefore the adapter is necessary The RFC adapter enables you to use the functions of the Integration Engine in existing SAP system landscapes. It is used by SAP systems to connect to the Integration Engine by using the RFC interface. It supports SAP systems as of version 3.1x.

Many Mainframe applications interface via flat files over FTP or at the OS level. Some rely on a messaging tool such as IBM MQSeries (WebSphereMQ), based on JMS.

The file/FTP adapter enables you to exchange data with the Integration Server by means of a file interface or an FTP server.

The JDBC adapter enables you to connect database systems to the Integration Server. The adapter converts database content to XML messages and the other way around.

Database content can be read with any SQL statement. A special XML format is defined for content coming from the Integration Engine. This format enables SQL INSERT, UPDATE, SELECT, DELETE, or stored procedure statements to be processed. A message is always processed in exactly one database transaction.

The JDBC adapter connects to databases directly by handling SQL statements or procedures. Therefore it is not appropriate let’s say to connect to the database underlying an R/3 system The JMS adapter enables you to connect messaging systems to the Integration Engine.

JMS adapter is typically used to connect to a JMS provider such as IBM WebSphere MQ (MQSeries) or Sonic MQ.

The SOAP adapter enables you to exchange SOAP messages between remote clients or Web service servers and the Integration Server Any interface which is exposed as a web service can be accessed via the SOAP adapter You use the marketplace adapter to connect the Integration Server to marketplaces. It enables messages to be exchanged by converting the XI message format to the marketplace format MarketSet Markup Language (MML) and the other way around.

The RNIF (RosettaNet Implementation Framework) Adapter supports RosettaNet, a standard used for data communication in the High-Tech industry.

The RNIF Adapter is based on the RosettaNet Implementation Framework (RNIF) version 2.0.
SMTP (simple mail transfer protocol) is used to interface with most mail servers by sending and receiving emails.

The SAPBC adapter enables the coexistence of the SAP Business Connector and SAP XI .

Adapters not hosted in the J2EE Adapter Engine :

The adapters are implemented in ABAP and reside directly on the Integration Server (ABAP stack) are of this category. They are two types as given below.

The IDoc adapter comprises two parts, namely an adapter at the Integration Server inbound channel, and an adapter at the Integration Server outbound channel.

The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data using a plain HTTP connection. Depending on the receiver system, outbound messages can be enhanced with certain information.

Their configuration is done centrally in the ID (as for all adapters) but the monitoring does not go through the RWB. There are specific ABAP transactions to monitor these adapters.

Regarding the connectivity to SAP systems please note that the RFC adapter is hosted by the J2EE adapter engine, while the IDoc adapter is hosted by the ABAP stack of the Integration Server.

Related Posts :

What is xi adapter ?
How do xi fetch data ?
Central and Local adapters

The previous post of the blog deals with Syntax check for ABAP IMPORT .

SAP definition,full form,over veiw and introduction

Syntax Check for IMPORT

This syntax check of ABAP is in continuation of our series and previous discussion is about IF key word.

Variants

1. IMPORT f itab FROM MEMORY.
2. IMPORT f itab FROM DATABASE dbtab(ar) ID key.
3. IMPORT DIRECTORY INTO itab FROM DATABASE dbtab(ar) ID key.
4. IMPORT f itab FROM DATASET dsn(ar) ID key.

Variant 1

IMPORT f itab FROM MEMORY.

Additions

1. ... TO g (for each field f to be imported)
2. ... ID key

Effect

Imports data objects (fields or tables) from the ABAP/4 memory . Reads in all data without an ID that was exported to memory with "EXPORT ... TO MEMORY." . In contrast to the variant IMPORT FROM DATABASE , it does not check that the structure matches in EXPORT and IMPORT .

The return code value is set as follows:

SY-SUBRC = 0 The data objects were successfully imported.

SY_SUBRC = 4 The data objects could not be imported,probably because the ABAP/4 memory was empty.

The contents of all objects remain unchanged.

Addition 1

... TO g (for each field f to be imported)

Effect

Takes the field contents stored under f from the global ABAP/4 memory and places them in the field g .

Addition 2

... ID key

Effect

Imports only data stored in ABAP/4 memory under the ID key .

The return code value is set as follows:

SY-SUBRC = 0 The data objects were successfully imported.

SY_SUBRC = 4 The data objects could not be imported, probably because an incorrect ID was used. The contents of all objects remain unchanged.

SAP Full form and introduction part two
SAP architecture,its full form of working and enjoy sap products
SAP journey from R/3 towards MySAP.com

Syntax Check for IF keyword

Basic form

IF logexp.

Effect

Used for case distinction.

Depending on whether the logical expression logexp is true or not, this statement triggers the execution of various sections of code enclosed by IF and ENDIF .

There are three different types:

IF logexp.

processing1

ENDIF.

If the logical expression is true, processing1 is executed.

Otherwise, the program resumes immediately after ENDIF .

IF logexp.

processing1

ELSE.

processing2

ENDIF.

If the logical expression is true, processing1 is executed.

Otherwise, processing2 is executed (see ELSE ).

IF logexp1.

processing1

ELSEIF logexp2.

processing2

ELSEIF ...
...
ELSE.

processingN

ENDIF.

If the logexp1 is false, logexp2 is evaluated and so on. You can use any number of ELSEIF statements. If an ELSE statement exists, it always appears after all the ELSEIF statements.

Notes

All IF statements must be concluded in the same processing block by ENDIF .

IF statements can be nested as mayn times as you like. The IF statement does not directly affect the selection. For this purpose, you should use the CHECK statement.

What is SAP and Why do we are in need of It
What is SAP Full form and its definition part one

SAP BW InfoObject Catalogs Creation

In the previous post of SAP BW series we have dealt with creation of SAP INFO AREA for business ware housing. Here in continuation with that we are going to discuss regarding info object catalog creation.

Before we can create an Info Cube, we must have Info Objects. Before we can create Info Objects, however, we must have Info Object Catalogs. Because characteristics and key figures are different types of objects, we organize them within their own separate folders, which are called Info Object Catalogs. Like Info Cubes, Info Object Catalogs are listed under Info Areas.

InfoObject Catalogs hold characteristics and key figures of info area.

Here is the step by step process.

1 . Click InfoObjects under Modelling in the left panel. In the right panel, right-click InfoArea – demo, and select Create InfoObject catalog….


2 . Enter a name and a description for the InfoObject Catalog, select the option Char., and then click the symbol shown in the diagram below to create the InfoObject Catalog.

3 . In the new window, click the check symbol to check the Info Object Catalog. If it is valid, click activate symbol as shown to activate the InfoObject Catalog. Once the activation process is finished, the status message InfoObject catalog IOC_DEMO_CH activated appears at the bottom of the screen.

You can check the result as Click the back symbol to return to the previous screen. The newly created InfoObject Catalog will be displayed.

Following the same procedure, we create an InfoObject Catalog to hold key figures. This time, make sure that the option Key figure is selected as shown below.

Related Posts :

SAP BW architecture
Introduction to SAP BW
sap internet transaction architecture
SAP internet transaction application components