Академический Документы
Профессиональный Документы
Культура Документы
BAPI BADI
BAPI is an interface which helps BADI is used to enhance R/3 For customer
the extenal world to communicate Needs.
with R/3 via OOPS Programming.
BADI Customer-exit
No batch input processing log Detailed Log will be generated for all the
sessions
While execution it starts from the While executing it wont start from the first. It
first. will start from the place where it ends with
error.
IDOC BAPI
IDocs are text encoded documents BAPIs are a subset of the RFC-enabled
with a rigid structure that are used function modules, especially designed as
to exchange data between R/3 and Application Programming Interface (API) to
a foreign system the SAP business object, or in other words:
are function modules officially released by
SAP to be called from external programs.
Idocs are processed asynchronously BAPIs are called synchronously and (usually)
and no information whatsoever is return information
returned to the client,
Idocs – by using tRFC – support whereas for BAPIs the client code needs to
guaranteed delivery do the appropriate error handling.
With asynchronous links the sub- Problems with synchronous links occur if the
process on the client can be finished communication line or the server is
even if the communication line or temporarily not available. If this happens,
the server is not available. In this the sub-process on the client can not be
case the message is stored in the finished (otherwise there would be data
database and the communication inconsistencies).
can be done later
The disadvantage of asynchronous Synchronous links have the advantage that
links is that the sub-process on the the sub-process on the server can return
server can not return information to values to the sub-process on the client that
the calling sub-process on the has started the link.
client. A special way for sending
information back to the client is
required. In addition, a special error
handling mechanism is required to
handle errors on the receiving side.
ALE EDI
SAP has provided ALE (Application EDI is described as the interchange of
Link Enabling) to distribute structured data according to agreed
applications across several SAP message standards between computer
systems and also between SAP and systems, by electronic means. (Electronic
external systems. Data Interchange) EDI in other words is a
set of computer interchange standards for
business documents such as invoices, bills,
and purchase orders. EDI(electronic data
interchange) is used send data to an
external partner.
For eg : if we send the purchase For eg :If we send the purchase order to a
order via ALE to another R/3 system, supplier then the supplier will store the
then the receiving system will store purchase order as a sales order.
the purchase order also as a
purchase order.
User-exits(modifications) Customer-exits(enhancements)
USER EXITS are FORMS and are CUSTOMER EXITS are FUNCTIONS so they
called by SAP standard programs are called using CALL FUNCTION (or more
using PERFORM. exactly CALL CUSTOMER FUNCTION).
Inside the form (user exit) you can Inside a function (customer exit) you can
read and change almost any global only acces your
data from host program. import/export/changing/tables parameters.
User exits are more flexible because Customer exits are more restrictive but you
you have more information to use in are sure any change you can make to any
your code but on the other hand , it parameters will never lead to inconsistency
is very easy to manipulate
erroneously global data and lead the
standard program to a dump or even
to make database inconsistent.
User-exit doesn’t have any In customer-exit we have function-module
classification. exit , screen exit , menu exit
With user-exits the code , the Customer-exits are not wiped during
developer has written will not be upgradation
there for next version unless
modification assistance tool is used
Alv-grid and Alv-list
Alv-grid Alv-list
When the report is run in When the report is run in background only
background you cannot see the grid the list comes out in the spool
in the spool
to have an editable grid you have to you can make the list editable easily just
create it using objects flagging the field edit in fieldcat table
Multiple page formats are not possible Multiple page formats are possible in
in SAPScripts smartforms
LSMW BDC
lsmw is basically for standard sap BDC is basically for customized
application applications
in lsmw mapping is take care by sap in bdc we have to give mapping concept
exlicitly