A Big Thank You

Hi every one,

It is your abap blogger Suresh.

This SAP ABAP COMPLETE blog is having 400 posts now and this blog has came across a long journey.

At least some of 5oo+ readers know the journey completely.

It is started around March 2007 and every day i tried my best to make it better in terms of subject as well as look.

Your support through out this journey is incredible and i shall say A BIG THANKS
to all of you.

To day is another mile stone in the life of this blog.

It has got a very fresh look and you can feel the difference.

At least i believe that the new design is more user friendly and gives better experience .


Until yesterday the blog look like this.

And the new look is like this.

How do you feel the difference ?

Your comments are most welcome and gives me some thoughts and insights.

Are you happy with this blog ?

What topics of the blog are boring and inconsistent ?

What topics of sap abap it has not covered ?

What makes this blog better?

Let me know from your side.
Any way thank you once agian.

Update June 2013

Well.The journey is in continuation.There is now all most thousand posts in sap  abap blog and the
discussion is well extended now to other topics like FICO,CRM AND BW.
 
Let me add the new look picture here.Your comments are very much welcome.



No comments :

Privacy policy

This website/blog uses third-party advertising companies to serve ads when visiting this site. These third parties may collect and use information (but not your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, you can visit Google's Advertising and Privacy page.

If you wish to opt out of Advertising companies tracking and tailoring advertisements to your surfing patterns you may do so at Network Advertising Initiative.

Google uses the Doubleclick DART cookie to serve ads across it's Adsense network and you can get further information regarding the DART cookie at Doubleclick as well as opt out options at Google's Privacy Center.

Privacy:
I respect your privacy and I am committed to safeguarding your privacy while online at this site www.abapprogramming.net. The following discloses how I gather and disseminate information for this Blog.

RSS Feeds and Email Updates

If a user wishes to subscribe to my RSS Feeds or Email Updates (powered by Feedburner), I ask for contact information such as name and email address. Users may opt-out of these communications at any time. Your personal information will never be sold or given to a third party. (You will never be spammed by me - ever)

Log Files and Stats

Like most blogging platforms I use log files, in this case Statcounter. This stores information such as internet protocol (IP) addresses, browser type, internet service provider (ISP), referring, exit and visited pages, platform used, date/time stamp, track user’s movement in the whole, and gather broad demographic information for aggregate use. IP addresses etc. are not linked to personally identifiable information.

Cookies

A cookie is a piece of data stored on the user’s computer tied to information about the user. This blog doesn't use cookies. However, some of my business partners use cookies on this site (for example - advertisers). I can't access or control these cookies once the advertisers have set them.

Links

This Blog contains links to other sites. Please be aware that I am not responsible for the privacy practices of these other sites. I suggest my users to be aware of this when they leave this blog and to read the privacy statements of each and every site that collects personally identifiable information. This privacy statement applies solely to information collected by this Blog.

Advertisers

I use outside ad companies to display ads on this blog. These ads may contain cookies and are collected by the advertising companies and I do not have access to this information. I work with Google Adsense. Please check the advertisers websites for respective privacy policies.

Contact Information

If you have any questions or concerns please contact me at d_vsuesh[at the rate of]yahoo[dot]co[dot]in.


@ 2007 Abapprogramming - The articles are copyrighted to D V Suresh and can only be reproduced given the author's permission.

All product names are trademarks of their respective companies.Every effort is made to ensure content integrity. Use information on this site at your own risk. Information furnished in the blog is collected from various sites. This blog does not host any files on its server. Please report any broken links in comment.

The Blog www.abapprogramming.net no way affiliated with SAP AG.

No comments :

SAP ABAP Dictionary Complete

SAP stores all data in the form of tables in abap dictionary.This is a vital ,individual and dedicated data base for SAP.

Here you can learn every thing regarding ABAP DICTIONARY.

All your comments are welcome.


ABAP DICTIONARY OVER VIEW

TABLE TYPES IN ABAP

CHANGES TO DATA BASE TABLES

VIEWS IN ABAP

TYPES OF VIEWS IN ABAP

DATA BASE DIALOG

ABAP DATA BASE UPDATE

ORGANIZING DATA BASE UPDATES

SAP LOCK CONCEPT

SEARCH HELP

DEPENDENCIES OF DICTIONARY OBJECTS

PERFORMANCE DURING TABLE ACCESS

ENHANCEMENTS TO DICTIONARY ELEMENTS

If you are interested in SAP ABAP syntax for format check here.

ABAP TOPIC WISE COMPLETE COURSE

BDC
OOPS ABAPALE
IDOC'S
BADI
BAPI
Syntax Check
Interview Questions
ALV Reports with sample code
ABAP complete course
ABAP Dictionary
SAP Scripts
 Script Controls
Smart Forms
Work Flow
Work Flow MM
Work Flow SD
Communication Interface
No comments :
Labels: ABAP DICTIONARY

Programming ABAP Syntax for Format part three

This post is in continuation with sap abap syntax for format part two.

Addition 4

... HOTSPOT [ON] or ... HOTSPOT OFF

Effect

Affects the display format of the mouse pointer and the effect of the mouse single click:

If you drage the mouse pointer over list areas which are output with the format ...HOTSPOT (lines or fields), the mouse pointer switches from its standard display format (usually an arrow) to the format of a hand with an outstretched index finger. If you then click once, the effect is like double-clicking or pressing the function key F2 (AT LINE-SELECTION ).

Note

The addition ...HOTSPOT has no effect on input fields.

Addition 5

... INPUT [ON] or ... INPUT OFF

Effect

Determines whether the user can enter data. You can change the contents of list lines output with the format ... INPUT on the screen. You can also print out the change or process it further by using READ LINE in interactive events.

... INPUT OFF reverses the ready for input status.

Note

Every time a new event ( START-OF-SELECTION , TOP-OF-PAGE , ...) is started, the system setting reverts to ... INPUT .

The additions ... COLOR , ... INVERSE and ... HOTSPOT have no effect on input fields.The addition ... INTENSIFIED affects the background color (color palette "input field" or "output field intensified").

The attribute ... INPUT causes lines to be displayed characterby- character and ready for input ( | or - ).

Addition 6

... RESET

Effect

Resets all formats (color, intensified, inverse, hotspot and input). This corresponds to the command:

FORMAT COLOR OFF INTENSIFIED OFF INVERSE OFF HOTSPOT OFF INPUT OFF.

Example

FORMAT INTENSIFIED INPUT.

WRITE 5 'JOHN'.

FORMAT INPUT OFF.

WRITE 40 'CARL'COLOR COL_GROUP.

produces the following output:

....+....10...+....20...+....30...+....40...+
JOHN CARL
ready for input: <------->
intensified: <------------------------------------------>
color: <--->

From the beginning of the line to the last character of 'JOHN' , the list is ready to accept input and is thus displayed in intensified form.

From column 9 (i.e. after the 'N' of of 'JOHN' ), the list line is also intensified but no longer ready for input.

'CARL' is output from line 40, together with a colored bar (color COL_GROUP = 7 from the palette "color intensified"). The script color is the color "output field intensified" (ProtInt). The intensified line display ends with the last character of 'CARL' .

Note

If the formats apply only to the output of a single field, you can set the same (and other) parameters as additions to the WRITE statement. If you want to display different formats on the screen, there are no reserved characters, i.e. you may output 2 fields with different formats one directly after the other (without gaps). You can also set the static additions ON , OFF and n (for COLOR ) dynamically with = var which always interprets the contents of var as a number. Values other than zero are used as ON or color number, zero works like OFF .

For color numbers less than zero or greater than 7, the result is not defined. Recommended data type: I(nteger)

Example

DATA C TYPE I VALUE 5.
FORMAT INTENSIFIED ON COLOR = C.


CRM Middle ware System Architecture
CRM Middle ware Enhancement
CRM Middle ware Data Flow
 CRM Middle ware Modelling 
CRM Adapter Overview 
CRM Software Logistics and support
No comments :
Labels: SYNTAX CHECK

ERP SAP ABAP Syntax for Format part two

This is in continuation with SAP ABAP SYNTAX For format part one.

Addition 2

... INTENSIFIED [ON] or ... INTENSIFIED OFF

Intensified - affects the background color.

Each color exists in a normal (desaturated) and in an intensified (saturated) form... ITENSIFIED takes the current background color from the "intensified" palette, while the ... INTENSIFIED Off uses the "normal" palette.

Note

Every time a new event ( START-OF-SELECTION , TOP-OFPAGE , ...) is started, the system setting reverts to ... INTENSIFIED .

On a standard background ( COLOR COL_BACKGROUND ), the foreground color may be affected in certain cases.

If, for example, you use the addition ... INVERSE with the color palette "output field intense" (IntNorm), the addition ... INTENSIFIED has no effect; the only exception to this rule is COLOR COL_BACKGROUND .

The attribute ...COLOR does not work for lines .

Addition 3

... INVERSE [ON] or ... INVERSE OFF

Inverse - affects the background and foreground colors. Each color exists in an inverse form. ... INVERSE takes the current color from the "inverse" palette and uses it as the foreground (script) color. The background ( COL_BACKGROUND ) then has no color. ... INVERSE OFF
switches off the inverse display.

Note

Every time a new event ( START-OF-SELECTION , TOP-OFPAGE , ...) is started, the system setting reverts to ... INVERSE .

If the use of ... INVERSE results in the same background and foreground colors ( COLOR OFF INVERSE ), the background color and the foreground color are merely reversed.

When you are using the inverse display, the addition ... INTENSIFIED has no effect. (As mentioned above, COLOR OFF INVERSE is an exception to this rule.)

The attribute ...COLOR does not work for lines .
66.5

The previous post of this blog deals with the next generation sap product SAP XI adapter.

SAP CRM Technology Overview
CRM Data Exchange with SAP R/3
CRM Data Exchange via Adapter
CRM E commerce Introduction
CRM Interaction Center System  Architecture
CRM Field Sales
People Centric SAP CRM
Analytical SAP CRm Overview
SAP CRM Solution Monitoring
CRM Backup Restoring System
No comments :
Labels: SYNTAX CHECK

ERP SAP XI ADAPTER

“One that adapts, such as a device used to effect operative compatibility between different parts of one or more pieces of apparatus.” (Dictionary definition).

An XI Adapter enables compatibility between the XI Integration Server and an application system As such, the use of the XI Integration Server in conjunction with selected adapters enables the compatibility between heterogeneous business systems Adapters are essential in the vast majority of today’s customer scenarios.

Adapters are at the core of any integration scenario. Any customer scenario where external applications are present is a use-case for adapters.

Adapters converts messages from the XI Protocol (SOAP with attachments over HTTP) to the respective protocol “spoken” by the application system, and vice-versa.

The XI Integration Server itself would have very little purpose if the surrounding adapters were not present (unless all application systems are based on SAP WebAS 6.20 or above, and use proxy interfaces to communicate – which is not yet a reality in customer landscapes).

The key premise of XI is its very nature to integrate heterogeneous systems, and the adapters are the enabling technology to do this.


related post

SAP XI CONNECTIVITY

MySAP CRM Marketing Introduction
Marketing and Advertizing in CRM
MySAP CRM Marketing Calender
No comments :
Labels: XI BASICS

SAP XI CONNECTIVIY

The choice of adapters vs proxies comes into play when connecting SAP applications Before WebAS 6.20 the only connectivity option in/out of the 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) At the present time, the vast majority of SAP applications still fall in the first category (IDoc or RFC/BAPI based) This is true for all applications based on 4.6C and below. Since RFC/IDoc is the only technology available for interfaces.

This is still true for most applications based on WebAS 6.20 or above. Indeed most applications still use RFC/BAPIs and IDocs.Newer applications are starting to emerge, which are based on the ‘outside-in’ methodology (proxies, native connectivity, no adapters).

At this point in time this is only a small set of SAP applications .As this is the long-term development strategy (towards ESA approach), this form of connectivity will gain importance in the future and ultimately this will be the only form of interfaces in/out of SAP applications.

SAP Business Packages for Industry Standards

Provides Solution Kits for specific industries and delivers mappings for RosettaNet, CIDX Application adoption .

Enhance business applications like mySAP CRM or mySAP SCM to support SAP® Business Packages for high.

MApping

Including message sets for the industries according their priority Support mappings: versions, upgrade, maintenance Process Integration .

SAP® Business Packages’ message protocol implementation (such as RNIF 2.0 and RNIF 1.1 for CIDX)

Provision of Collaboration Agreements

In the case of Industry standards support, the adapters play a key role in the SAP Business Packages, but they are only part of the picture.

The idea of an SAP Business Package is to provide all levels of support for a given Industry Standards Semantic level (mappings, interfaces).

Process level (BPM)

Application level (R/3, CRM, SCM,...)

Connectivity (adapters)

Adapter mappings and adapter metadata are stored in the Integration Repository Centralized Integration Repository contains all relevant information for collaborative processes All content adheres to open standards Adapters provide technical connectivity The PCK will be detailed in one of the following units.

As already established the PCK is also based on the adapter framework. PCK does not inherit central configuration data from the Integration Directory PCK has its own user interface (which is a subset of the Integration Directory) for configuration of individual adapters.

SAP Partner Connectivity Kit (PCK) is based on Adapter Framework :

SAP PCK‘s objective is to enable XML document exchange between SAP XI and business partner not using SAP XI SAP PCK also provides an extensible platform for developing and running individual JCA Resource adapters Communication between SAP XI and SAP PCK is via SAP XI messaging protocol SAP PCK Includes the following adapters: File/FTP, JDBC, JMS, SOAP, RFC, IDoc (once available for SAP PCK) Optionally SAP PCK can host further adapters that are available from SAP or 3rd party adapter providers.


Adapter Framework runs on J2EE Stack of SAP Web AS :

Adapter Framework is platform for Adapter Engine and SAP PCK Adapter Framework provides an extensible platform for developing and running adapters in SAP XI environment Adapter Engine utilizes central configuration, monitoring, administration .


READ MORE ABOUT SAP XI HERE AT WEKIPEDIA

RELATED POST

sap xi adapters local and central
Customer Relationship Management and mysap an introduction
CRM Management and sales and service strategy of mysap crm
MySAP CRM and customer as business partner
No comments :
Labels: XI BASICS

SAP XI Adapters Cental and Local

Central AE is installed by default.Any number of local AEs can be installed. The local AE needs its own instance of the J2EE engine. The local AE can reside on any remote hosts, and several local AEs can even coexist on the same host (even on the Integration Server host).

Many factors come into play when making a decision to use the central or local AE The primary reason for using a local AE is the proximity to the business system. This may be by choice (in order to optimize the performance) or because of miscellaneous technical / networking issues (e.g. Operating system dependencies or Firewalls).Even when the AE is deployed locally, the configuration and monitoring is done centrally via the Integration Directory and Runtime Workbench, respectively. (as explained in one of the previous slides).

Technical benefits of using one or several local adapter engines:

mitigate the risks of having a single point of failure (SPOF). Indeed if the central AE is used exclusively, it becomes a SPOF (so is the Integration Server – J2EE stack).

Distribute the load of the adapters

All R/3 systems 4.6C 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 6.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 systemThe 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 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.

It is important to understand that proxies and adapters are the 2 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 (cf next slide) .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:

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.

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.


RELATED POST


XI ADAPTER ENGINE
XI INTRODUCITON
sap abap SYNTAX FOR FORMAT
Marketing and erp mysap crm options
Organizational Challenges with crm and mysap crm solutions
My sap crm and marketing planning
No comments :
Labels: XI BASICS

SAP ABAP Syntax for FORMAT

Basic form

FORMAT.

Additions

1. ... COLOR n [ON] or ... COLOR OFF

2. ... INTENSIFIED [ON] or ... INTENSIFIED OFF

3. ... INVERSE [ON] or ... INVERSE OFF

4. ... HOTSPOT [ON] or ... HOTSPOT OFF

5. ... INPUT [ON] or ... INPUT OFF

6. ... RESET

Effect

Sets or modifies the valid output format.

The formats set by FORMAT work from the next output in the list, i.e. from the next WRITE command or from the next new line.

The addition ... ON for switching on the relevant output format is optional.

Addition 1


... COLOR n [ON] or ...COLOR OFF Color of line background .

Note

Every time a new event ( START-OF-SELECTION , TOP-OFPAGE , ... ) is started, the system setting reverts to COLOR 0 .

The additions .. INTENSIFIED and ... INVERSE both affect the color display (see below).

The attribute ...COLOR does not work for lines .

Addition 2

... INTENSIFIED [ON] or ... INTENSIFIED OFF Intensified - affects the background color.

Each color exists in a normal (desaturated) and in an intensified (saturated) form. ... INTENSIFIED takes the current background color from the "intensified" palette, while
the ... INTENSIFIED OFF uses the "normal" palette.

Note

Every time a new event ( START-OF-SELECTION , TOP-OFPAGE , ...) is started, the system setting reverts to ... INTENSIFIED .

On a standard background ( COLOR COL_BACKGROUND ), the foreground color may be affected in certain cases.

If, for example, you use the addition ... INVERSE with the color palette "output field intense" (IntNorm), the addition ... INTENSIFIED has no effect; the only exception to this rule is
COLOR COL_BACKGROUND .

The attribute ...COLOR does not work for lines .



RELATED POST

ABAP SYNTAX CHECK COMPLETE LIST OF KEY WORDS
MySAP CRM System architecture and design
MySAP CRM architecture and E procurement introduction
No comments :
Labels: SYNTAX CHECK

SAP ABAP SYNTAX CHECK COMPLETE

Syntax of any programming language is a vital part and has to be used in the correct manner by a programmer and it is really difficult to remember every syntax of key words.

This list shall come to the rescue of every ABAPER and help in writing the code.

Here is the syntax for key words and some times because of its size ,divided into number of parts.

Happy coding.

ADD CORRESPONDING

ASSIGN PART ONE

ASSIGN PART TWO

CONTROL BREAK

EVENTS IN LISTS

EVENTS IN LISTS PART TWO

EVENTS ON SELECTION SCREEN PART ONE

EVENTS ON SELECTION SCREEN PART TWO

AUTHORITY CHECK

BACK

BREAK POINT

CALL FUNCTION PART ONE

CALL FUNCTION PART TWO

CALL FUNCTION PART THREE

CALL FUNCTION PART FOUR

CALL FUNCTION PART FIVE

CALL METHOD

CALL SCREEN

CALL TRANSACTION

CHECK

CHECK WITH IN LOOP

CLEAR

CLOSE AND CNT

COLLECT

COMMIT

COMMUNICATION PART ONE

COMMUNICATION PART TWO

COMMUNICATION PART THREE

COMMUNICATION PART FOUR

COMMUNICATION PART FIVE

COMPUTE PART ONE

COMPUTE PART TWO

COMPUTE PART THREE

CONCATENATE

CONDENSE

CONSTANTS

TABLE CONTROL

CONVERT

CREATE

DATA PART ONE

DATA PART TWO

DATA PART THREE

DATA PART FOUR

DATA PART FIVE

DATA PART SIX

DEFINE

DELETE PART ONE

DELETE PART TWO

DELETE PART THREE

DELETE PART FOUR

DELETE PART FIVE

DELETE FROM DATA

DELETE PROGRAM

DESCRIBE PART ONE

DESCRIBE PART TWO

DESCRIBE PART THREE

DESCRIBE PART FOUR

DESCRIBE PART FIVE

DESCRIBE PART SIX

DESCRIBE PART SEVEN

DETAIL

DIVIDE

DO

EDITOR CALL PART ONE

EDITOR CALL PART TWO

ELSE AND ELSE-IF

EXEC

EXPORT PART ONE

EXPORT PART TWO

FETCH

FIELD SYMBOLS

FORM

FORM PART TWO

FORMAT

FORMAT PART TWO

FORMAT PART THREE

FREE

GENERATE

GET PART ONE AND TWO THREE

GET CURSOR PART ONE TWO

GET CURSOR PART ONE AND TWO

IF KEYWORD

IMPORT PART ONE AND TWO

INCLUDE

INFOTYPES

RELATED POST

ABAP 51 Days Complete Course
ABAP Dictionary
OOPS in ABAP
BDC
SAP Scripts
SAP Scripts Controls
SAP Smart Forms
Real Time ABAP Programming Reports
SAP Interview Questions
Syntax for ABAP Programming
ABAP Interface Programming
Financial and Controlling Sample Reports 
No comments :
Labels: SYNTAX CHECK

SAP ABAP INTERVIEW QUESTIONS

Here is the list of interview questions for a sap abap interview and you can find topic wise.

SAP ABAP FAQ'S ON INTERACTIVE REPORT

SAP ABAP INTERVIEW QUESTIONS ON SCRIPTS PART ONE

SAP ABAP INTERVIEW QUESTIONS ON SCRIPTS PART TWO

SAP ABAP INTERVIEW QUESTIONS ON SCRIPTS PART THREE

SAP ABAP INTERVIEW ROUND ONE FAQ'S PART ONE

SAP ABAP INTERVIEW ROUND ONE FAQ'S PART TWO

SAP ABAP INTERVIEW ROUND ONE FAQ'S PART THREE

SAP ABAP INTERVIEW ROUND ONE FAQ'S PART FOUR

SAP ABAP INTERVIEW QUESTIONS ON INTERNAL TABLE

SAP ABAP INTERVIEW QUESTIONS ON REPORT FORMATION AND EVENTS

SAP ABAP INTERVIEW QUESTIONS ON MODULARIZATION

SAP ABAP INTERVIEW QUESTIONS ON BASIS LAYER

SAP ABAP FAQ'S ON RFC

SAP ABAP OPTIMIZATION

SAP ABAP CROSS APPLICATIONS

ABAP ASSIGNMENT

ABAP REAL TIME INTERVIEW QUESTIONS PART ONE

ABAP REAL TIME INTERVIEW QUESTIONS PART TWO

ABAP REAL TIME INTERVIEW QUESTIONS PART THREE

RELATED POST

ABAP 51 Days Complete Course
ABAP Dictionary
OOPS in ABAP
BDC
SAP Scripts
SAP Scripts Controls
SAP Smart Forms
Real Time ABAP Programming Reports
SAP Interview Questions
Syntax for ABAP Programming
ABAP Interface Programming
Financial and Controlling Sample Reports 

No comments :
Labels: SAP ABAP INTERVIEW QUESTIONS

SAP XI ADAPTER ENGINE

The J2EE-based Adapter Engine provides you with various adapters that you can use to connect external systems to your Integration Engine. You can use these adapters to convert XI Protocol based messages (SOAP /attachments over HTTP) to the specific protocols and formats of the respective external systems and the other way around.

Besides the J2EE-based Adapter Engine, you can also use the plain J2SE-based Adapter Engine.

Most XI adapters reside on the J2EE adapter engine. The only 2 exceptions are the plain HTTP adapter and IDoc adapter, which both reside within the Integration Server (ABAP) The AE is fully integrated with the XI landscape.

All adapters (including IDoc and HTTP) are configured centrally in the Integration Directory. There you can specify whether an adapter is to be located at the inbound channel (sender adapter) or at the outbound channel (receiver adapter) of an Integration Engine Reuse of Integration Directory’s existing versioning and Transport capabilities Central administration and monitoring over adapters, Integration Server, Integration Engine through Runtime Workbench Adapters can be hosted separately, possible on another host The J2EE adapter engine is based on the open JCA architecture. This is part of the J2EE standard.

As such, each individual adapter is referred to as a ‘resource adapter’. The JCA architecture allows to ‘plug in’ resource adapters, written by third-party vendors, SAP partners or customers.

Adapter framework is the main building block of the adapter engine.

The Adapter Engine is based on the adapter framework. The adapter framework is based on the SAP J2EE Engine (as part of the SAP Web Application Server) and the J2EE Connector Architecture (JCA). The adapter framework provides interfaces for configuration, management, and monitoring of adapters.

Adapter Framework provides common functionality for Adapter Engine and SAP Partner Connectivity Kit Adapter Framework inherits properties and features such as scalability, clustering, high availability, thread management, etc.

Adapter Framework provides its own queuing and logging services Temporary stand-alone operation without connection to an Integration Server is possible, while still providing e. g. guaranteed exactly once messaging to and from connected application system The Adapter framework is at the core of the adapter engine. It provides the core services which are common to all adapters: messaging, queuing and security handling. This is really the runtime of all adapters.

This slide also explains the benefits of having an adapter framework which is based on the open JCA standard. Te goal is to enable customers and partners to provide their own adapters through a consistent architecture and certification process.

Adapter Framework supports J2EE Connector Architecture (JCA).

JCA is standard architecture for connecting the J2EE platform to Enterprise Information Systems (EIS), e. g. ERP, DBMS, etc.

A Resource Adapter plugs into an application server, providing connectivity between the EIS and a Java application JCA enabled Adapter Framework provides defined interfaces to which both our adapters and 3rd party adapters can conform JCA is a widely accepted standard that 3rd party adapter providers are familiar with Adapter Software Development Kit (ASDK) based SAP XI Adapter Framework (as SAP PCK) and includes Adapter Framework Interface Specification, JCA sample adapter (incl. source code), Java Docs, xsd file .

The adapter engine can be deployed centrally or locally.

When the Integration Server is installed, the central AE is automatically installed as well.

Optionally the customer can deploy any number of local adapter engines. This can be done for several reasons (see next slide) The PCK is based on adapter framework and is intended for business partners who do not have a full XI system. The PCK will be detailed later on.

Note that the IDoc adapter is not part of the J2EE adapter engine and resides directly on the Integration Server host (ABAP stack). Same for the plain HTTP adapter which is not pictured here.

The J2SE adapter engine was the main solution for XI 2.0. It is still provided with XI 3.0 mainly for those customers who have already invested into it in the context of their XI 2.0 project. The J2SE adapter engine provides a limited set of technical adapters (File, JDBC, JMS, SOAP).



RELATED POST

ADAPTORS INTRODUCTION
SAP CRM Business Transactions
 SAP CRM marketing Management Campaign
No comments :
Labels: XI BASICS

Adapters in SAP XI Introduction

“One that adapts, such as a device used to effect operative compatibility between different parts of one or more pieces of apparatus.” An XI Adapter enables compatibility between the XI Integration Server and an application system As such, the use of the XI Integration Server in conjunction with selected adapters enables the compatibility between heterogeneous business systems Adapters are essential in the vast majority of today’s customer scenarios.

Adapters are at the core of any integration scenario. Any customer scenario where external applications are present is a use-case for adapters.

Adapters converts messages from the XI Protocol (SOAP with attachments over HTTP) to the
respective protocol “spoken” by the application system, and vice-versa.

The XI Integration Server itself would have very little purpose if the surrounding adapters were
not present (unless all application systems are based on SAP WebAS 6.20 or above, and use proxy interfaces to communicate – which is not yet a reality in customer landscapes).

The key premise of XI is its very nature to integrate heterogeneous systems, and the adapters are the enabling technology to do this.

RELATED POST

COMMUNICATION INTERFACE IN SAP ABAP COMPLETE SERIES

SAP Solution Manager Overview
People Centric SAP CRM Introduction
CRM Technical Infrastructure
No comments :
Labels: XI BASICS

COMMUNICATION INTERFACE IN ABAP COMPLETE

No comments :
Labels: Interface Programming , programming report

WORK FLOW FOR SD COMPLETE

Learn about work flow in sap abap sales and distribution module below.

SAP WORK flow in sales and distribution 1
SAP WORK flow in sales and distribution 2
SAP WORK flowin sales and distribution 3
SAP WORK flow in sales and distribution 4
SAP WORK flowin sales and distribution 5
SAP WORK flowin sales and distribution 6
SAP WORK flow in sales and distribution 7


related info

ABAP 51 Days Complete Course
ABAP Dictionary
OOPS in ABAP
BDC
SAP Scripts
SAP Scripts Controls
SAP Smart Forms
Real Time ABAP Programming Reports
SAP Interview Questions
Syntax for ABAP Programming
ABAP Interface Programming
Financial and Controlling Sample Reports  Work Flow
Work Flow MM
Work Flow SD
Communication Interface
MySAP CRM Customer Relationship Management
MySAP Best ERP
No comments :
Labels: ABAP WORK FLOW COMPLETE , ABAP WORK FLOW SCENARIOS IN MM , ABAP WORK FLOW SCENARIOS IN SD , Business Work flow

SAP ABAP WORK FLOW FOR MM

No comments :
Labels: ABAP WORK FLOW COMPLETE , ABAP WORK FLOW SCENARIOS IN MM , ABAP WORK FLOW SCENARIOS IN SD , Business Work flow

SAP ABAP WORK FLOW COMPLETE

No comments :
Labels: ABAP WORK FLOW COMPLETE , ABAP WORK FLOW SCENARIOS IN SD

BADI COMPLETE SERIES

Learn the most advanced technique of enhancements of sap abap i.e BADI here in a systematic manner with series of lessons as shown here.


IMPORTANCE OF BADI IN SAP ABAP

COMPARISON OF ENHANCEMENTS IN ABAP

BADI DEFINITION WITH SCREEN SHOTS

BADI IMPELEMTATION

BADI IMPLEMENTATION PART TWO

MENU ENHANCEMENTS USING SAP BADI

SCREEN ENHANCEMENTS USING SAP BADI

IMPLEMENTATION OF SCREEN ENHANCEMENTS USING BADI

BADI IMPLEMENTATION WITH FORMULA BAR

FILTER DEPENDENT BADI IMPLEMENTATION PART ONE

FILTER DEPENDENT BADI IMPLEMENTATION PART TWO

SAP ABAP FILTER DEPENDENT BADI IMPLEMENTATION

BADI AND OTHER ENHANCEMENTS COMPARISON

SAP ABAP BADI PART ONE

ABAP BADI PART TWO

ABAP BADI PART THREE

ABAP BADI PART FOUR

BADI PART FIVE

ABAP BADI PART SIX CALLING BADI AND ITS USES

BADI INTRODUCTION

RELATED POST

ABAP 51 Days Complete Course
ABAP Dictionary
OOPS in ABAP
BDC
SAP Scripts
SAP Scripts Controls
SAP Smart Forms
Real Time ABAP Programming Reports
SAP Interview Questions
Syntax for ABAP Programming
ABAP Interface Programming
Financial and Controlling Sample Reports 
No comments :
Labels: BADI'S IN ABAP

BAPI COMPLETE COUSE

No comments :
Labels: BAPI'S IN ABAP
Subscribe to: Posts ( Atom )