Difference between sapscripts and BDCs

what is the difference between sapscripts and BDCs

BDC for data communication between sap to non sap(vice-versa)
where scripts is a business layout(we create)
bdc help
They are the only 3 methods mostly we use in BDC.
Call _Dialog is outdated. it is there in the intial stages of SAP.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
These are the Function modules used for the Session Method.
BDC_OPEN_GROUP
BDC_INSERT
BDC_CLOSE_GROUP
BDC_DELETE_SESSION to create a session
You can schedule the execution of BDC session using the program RSBDCSUB.
another one call transaction
open dataset
close dataset
reward if it helps u
vijay pawar

Similar Messages

Differences between LSMW and BDC

Hi All
Please can you give me the few points about the differences between LSMW and BDC?
Awaiting for your Responce
Praveen

Hai Check with the following document
GOOD
THERE IS THREE TYPE OF METHOD IN BDC
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
· BDC_OPEN_GROUP : Opens a session group
· BDC_CLOSE_GROUP : Closes a session
· BDC_INSERT : Insert a BDC scenario in the session
· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purpose
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
LSMW vs DX Workbench
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.
SAP provides this tool along with documentation to customers and partners free of charge.
Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).
Releases:
Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.
Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.
Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !
Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

Difference between SAPScript and Smartforms

Hi all,
Can any body tell me, which of these SAPScript and Smartforms are client independent or client dependent and why?
Thanks in advance....
Sri.

Hi Sri,
SAPScript is client dependent and Smartform is client independent.
So you need to transport the SAPScript from the development client to test client if both are in the same system.
Because Smartform is client independent it will behave like report program.
Thanks
Vinod

Difference between interface and bdc

Hi All,
Can anybody please explain interface and BDC.
Thanks in advance

Hi
Interface is the one which is used to transfer data from SAP to Non SAP system or NON SAP to SAP system.
BAPI, IDOC are some of the interfaces.
BDC is used to upload data from Legacy to SAP system.
Reward points if useful
Regards
Anji

Difference between Sapscripts and Smartforms

Hi
I need to create a form for print it in some predefined furmulary for the user signs it , something like a payment receipt.
Wich tool should i use, a Sapscript or Smartform, wath's the diffrerence between these two tools ?
Thanks
Frank

Hi,
SAP Scripts is the old tool and SMART Form is comparatively new tool to develop and print business documents.
SMART Forms are more GUI oreiented and you can do lot of things just by dragging and dropping. SAP Scripts are more code oreiented.Practically smartforms is easier to develop when compared with SAPscript.
Differences :
1. Sapscript is Client dependent Smartform is Client independent.
2. Multiple page formats are possible in smartforms which is not the case in SAPScripts.
3. It is possible to a smartform without MAIN Window.
4. Labels cannot be created in smartforms.
5. It is possible to have a smartform without a main window .
6. In sapscript we cannot write our own logic for printing where as in smartform, we can write our own logic for pritning
7. Sapscript requires a driver program (se38 program) and layout (se71 layout) where as Smartforms can be run independently without a driver program.
8. In sapscript we cannot design matrix like tables,having grid lines, but in smartforms, it is much possible to design tables, having grid lines, color etc. just like excel table.
9.Smartforms generates a function module when activated.
Regards,
V Joshi.

Differnce between SapScript And Smartform

hi All,
Can anyone tell me the difference between sapscript and smartforms.Which we have to use
Points rewarded for answer
Harpreet

Hi harpreet,
1. Can anyone tell me the difference between sapscript and smartforms
some practical differences are :
*----
One main difference which is
visibility in the report is TABLES
(in sapscript we cannot design MATRIX like tables,
having grid lines,
but in smartforms, it is much possible to
design tables, having grid lines, color just
like excel table)
a) sapscript requires
 - driver program (se38 program)
 - layout (se71 layout)
 smartforms just require
 smartform,
(and a program is just required for
 selection screen purpose)
b) the logic of printing (ie. sequence, flow)
 is CONTROLLED BY drier program,
 in case of sapscript.
where as in smartform, it is inbuilt using TABLES element.
c) In sapscript we cannot write our own logic for printing.
 where as in smartform,
we can write our own logic for pritning.
(we can even write SELECT Statements, DATA statements,
 and many program lines + logic to suit our requirements)
2 Which we have to use
If we are copying some standard sapscript,
then we have to go for sapscript only.
We can use both. but practically smartforms is easier to
develop.
regards,
amit m.

Key Configuration differences between SAP and ORACLE Financials

Hello,
After spending good 7 years in SAP related projects recently I started working in ORACLE Applications. I used to be an ORACLE programmer years back. To my surprise the same ORACLE Forms are still very much the heart of the ORACLE UI.
Then I thought what will be the key differences between ORACLE and SAP in terms of configuration elements. While I know a bunch of configuraion items in SAP , I am not sure about the same in ORACLE world. I am not even sure some of the configuration items that are available in SAP exists in ORACLE.
Does anyone know both sides of the coin ? The terminology and design ?
SAP has
Client,Company code, Business area, Functional Area, GL, Posting Key, Document Type.
I am trying to get the details of the equivalents of these in ORACLE.
Does anyone know it ?
For e.g , when you post to AP or AR in SAP , GL is updated automatically. In ORACLE you post to a AP Book or AR Book then Run a batch to move them to GL Book.
ORACLE uses SQLLoader to load data . You can write a PL SQL and update the tables directly, which is not the case in SAP. For dataloads and conversions, SAP uses BDC's ( though XI can be used but its slow).For ORACLE its the good old SQL and PlSQL combo.
What are the equivalents of the configuration elements in ORACLE world ?
Also what are the major differences between these two in terms of designing a financial system.
Does any one know ?

Genie,
I agree that a case is made on how well these two ERPs solve the day to day tasks before a company chooses one of these two. But my question is aimed at finance to begin with. You are going to need a general ledger for any company or government regardless of ERP. And how well you can drive the ledger to map your business is the key here.
The way ledger is built is around a business area ,company or country and is very tighly designed in SAP. I would like to know if there is any equivalent of the configuration items in ORACLE. I am more interested in terminology of ORACLE.
For example ,
SAP ====> ORACLE
GL ==> Book In ORACLE
Document Number ===> Invoice Number
Posting Period in SAP ==> Posting period In ORACLE
Most of the terms are finance terms , so they are common ( eg. an account number is an account number in ORACLE and SAP ) between two systems. I am interested in any specific thing that is available in ORACLE but not in SAP and vice verse.
thanks for the link you have provided.
Its very useful.

Difference between poh and pov in module pool programming

hi all,
                   pls tell me difference between poh and pov and how i check validation in screen

Hi,
POV gives you F4 help.
like:
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD f MODULE mod.
After the PROCESS ON VALUE-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F4 for a field f, the system calls the module mod belonging to the FIELD statement. If there is more than one FIELD statement for the same field f, only the first is executed. The module mod is defined in the ABAP program like a normal PAI module. However, the contents of the screen field f are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These alll have the prefix F4IF_. The most important are:
·        F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
·        F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The self-programmed value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT demo_dynpro_f4_help_module.
TYPES: BEGIN OF values,
         carrid TYPE spfli-carrid,
         connid TYPE spfli-connid,
       END OF values.
DATA: carrier(3) TYPE c,
      connection(4) TYPE c.
DATA: progname TYPE sy-repid,
      dynnum   TYPE sy-dynnr,
      dynpro_values TYPE TABLE OF dynpread,
      field_value LIKE LINE OF dynpro_values,
      values_tab TYPE TABLE OF values.
CALL SCREEN 100.
MODULE init OUTPUT.
progname = sy-repid.
dynnum   = sy-dynnr.
CLEAR: field_value, dynpro_values.
field_value-fieldname = 'CARRIER'.
APPEND field_value TO dynpro_values.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE value_carrier INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
       EXPORTING
            tabname     = 'DEMOF4HELP'
            fieldname   = 'CARRIER1'
            dynpprog    = progname
            dynpnr      = dynnum
            dynprofield = 'CARRIER'.
ENDMODULE.
MODULE value_connection INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
       EXPORTING
            dyname             = progname
            dynumb             = dynnum
            translate_to_upper = 'X'
       TABLES
            dynpfields         = dynpro_values.
READ TABLE dynpro_values INDEX 1 INTO field_value.
SELECT carrid connid
    FROM spfli
    INTO CORRESPONDING FIELDS OF TABLE values_tab
    WHERE carrid = field_value-fieldvalue.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
       EXPORTING
            retfield    = 'CONNID'
            dynpprog    = progname
            dynpnr      = dynnum
            dynprofield = 'CONNECTION'
            value_org   = 'S'
       TABLES
            value_tab   = values_tab.
ENDMODULE.
*POH gives you F1 documentation:*
like:
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
       VAR(4),
       INT TYPE I,
       LINKS TYPE TABLE OF TLINE,
       FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
    WHEN 1.
    VAR = '0100'.
    WHEN 2.
    VAR = '0200'.
    INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
       EXPORTING
            DOKLANGU                      = SY-LANGU
            DOKTITLE                      = TEXT-002
            CALLED_FOR_TAB                = 'DEMOF1HELP'
            CALLED_FOR_FIELD              = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
       EXPORTING
            DOKCLASS                      = 'TX'
            DOKLANGU                      = SY-LANGU
            DOKNAME                       = 'DEMO_FOR_F1_HELP'
            DOKTITLE                      = TEXT-003
       TABLES
            LINKS                         = LINKS.
ENDMODULE.
Regards,
Renjith Michael

Difference between Distribution and Assessment cycle

Hi,
Can any one help me regarding the above(Difference between Distribution and Assessment cycle)
Thanks in advance
Rajani

HI,
Assessment:
Assessment was created to transfer primary and secondary costs from a sender cost center to receiving controlling objects. During assessment, cost centers or business processes can be used as senders .n The receivers for an assessment can be a cost center, WBS element, internal order, cost object, or a
business process. You can restrict the number of receiver categories in customizing. n Primary and secondary postings are allocated at the end of the period by means of the user-defined
key.
n During assessment, the original cost elements are summarized into assessment cost elements
(secondary cost element category = 42). As the system writes fewer totals records, the assessment
has a better performance than periodic reposting and distribution.
n Line items are posted for the sender as well as for the receiver, enabling the allocation to be recorded
exactly. The system does not display the original cost elements in the receivers. Therefore,
assessment is useful if the cost drilldown for the receiver is not important, for example, as in the case
of the allocation for the "cafeteria" cost center.
n Similar to distribution, the partner is updated in the totals record during distribution.
n You can reverse assessments as often as required.
n You use the Cycle -Segment method to define sender-receiver relationships.
Distribution:
Differences between periodic reposting and distribution are due to information content and
performance.
n For periodic reposting, no separate credit record is written on the sender for the cost element in the
summary report. Instead, the totals record for the cost element is reduced on the debit side, which
means that the original debit amount can no longer be checked there ("unclean credit"). However,
during distribution, the system writes a totals record for the credit ("clean credit"). The information
on the receiver is the same for periodic reposting and distribution ("clean debit").
n Compared with periodic reposting, during distribution, the system also updates the partner in the
totals record for the sender. This means that the partner can be displayed in the information system
on the totals record level.
n As fewer totals records are written during periodic reposting, performance is better than during
distribution. See customizing for an example with figures that illustrates this aspect. Under utilities,
make settings for the SAPscript text display, then call up the text by choosing Periodic reposting,
Distribution, or Assessment from the menu.
Regards,
Meenakshi

Difference Between BADI and User Exits

Hi..
generally BADIs & User Exis are used exensively in SAP SD...
Can anybody throw some light waht is difference between them ...
Kindly please reply......
Regards
Nisha

Hi
ifference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Difference between Userexits and BADI

Pls give me the Difference between Userexits and BADI.

Hi,
hope this is helpful
Difference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Difference between Smartforms and Sapscrits.

Hi Experts,
I have a interview coming up next week and I was just wondering: difference between Smartforms and SAPscripts..
So experts, can anyone please let me know what are the main differences between Smartforms and SAPScripts??
I will really appreciate your answers.. guys..
Regards,
-Ashok Patel.

Hi,
Difference with SMARTFORMS vs. SapScript(SE71)
The Following are the differences :-
a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
b) It is possible to have a smartform without a main window .
c) Labels cannot be created in smartforms.
d) Routines can be written in smartforms tool.
e) Smartforms generates a function module when activated.
f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format. In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment.
In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
Check the link,
http://www.sap-img.com/smartforms/sap-smart-forms.htm
Conversion of SAPSCRIPT to SMARTFORMS
SAP provides a conversion for SAPscript documents to SMARTforms.
This is basically a function module, called FB_MIGRATE_FORM. You can start this function module by hand (via SE37), or create a small ABAP which migrates all SAPscript forms automatically.
You can also do this one-by-one in transaction SMARTFORMS, under
Utilities -> Migrate SAPscript form.
You could also write a small batch program calling transaction SMARTFORMS and running the migration tool.
Hope it helps u.
Thanks&Regards,
Ruthra.R

Difference between LSMW and CATT

Hi all,
Can anybody tell me the difference between LSMW and CATT?

CATT
SAP users use CATT frequently to upload master data or to
make changes to master data records. SAP Consultants and
Abapers tend to use it for creating test data. The
transactions run without user interaction. You can check
system messages and test database changes. All tests are
logged. The CATT records your keystrokes while performing
the actual transaction. You then identify the fields that
you wish to change in that view. Then export this data to a
spreadsheet to populate with the data required. This is
uploaded and executed saving you keying in the data
manually.
To perform CATT, it has to be enabled in your production
environment (your systems administrator should be able to
do this - SCC4). You will also need access to your
development system to create the CATT script.
The process of uploading data with a CATT:
Activate CATT in your client
In transaction code SCC4 - click the change button
Double click on the client number
In the Restriction section, tick Allows CATT processes to
be started.
Upload data using CATT
1. Create Import variant for the fields you need
Transaction SCAT
Goto Parameters
Create Import Variant
Goto Variant -> Edit
Goto Variant -> Fast entry or F9
Duplicate 01
2. To change the MRP Group for a list of Material
Assuming that I want to change the MRP Group for a list of
Material.
My text files should look something like this:
[Variant ID] [Variant Text] &ZDISGR &ZMATNR
--> Parameter texts MRP group Material
--> Default Values M1 A001
Changes to the default values displayed above not
effective
#01 M1 A001
#02 ''     A002
#03 M1 A003
Note : '' denotes a blank in the field. e.g. Material A002
MRP group will be replaced by a blank.
3. Configure the recorded entry fields to read from the
imported text file data
In the CATT : Maintain functions test case Screen
Double click on the Object Name
Double click on the screen number with your desired fields
Park the cursor on the fields
Click Edit -> Details
Fill in the Parameters Name and Field Contents
Finish Save it.
Assign your text file data.
In the CATT : Execute test case Screen
Click External from file and choose your text file
CATT will now read from your text file and update whatever
data you have specified.
LSMW
Using LSMW you can update any kind of data but no changes to database are allowed, where as CATT tool can update only master data, which also allows changes to the master data and also a significant testing of data is possible. LSMW is a tool that offers you 4 ways to import data into SAP, they are BDC, Direct Input, BAPI(BO), IDOC.It is used for migrating the data b/w the Non-SAP and SAP application to do for that we can take the Non-SAP application data and Converts the data into the Legacy data. After the Legacy data creation convert the data in to the "Flat file". That flat file is in the form of text file or excel format.If the file is in the form of text format
we can create the ".txt" file ("ABC.txt")and in the form of
excel ".xls" file is created. flat file for dos and .xls
file for IBM. The converted file (.txt/.xls)is either upload or download. The Upload functionality if used for .txt file to SAP and where as Downloading is the concept while SAP to .txt/.xls file.
Execute the transaction LSMW to start transfer of data,Before using the LSMW we should have good knowledge about the business object and the fields that will be transferred.
There are 14 steps that are normally used and these are :
1)   Maintain Object Attributes.
2)   Maintain Source Structures.
3)   Maintain Source Fields.
4)   Maintain Structure Relations
5)   Maintain Field Mapping and conversion rules .
6)   Maintain Fixed Values,translations ,user defined routines.
7)   Specify Files .
8)   Assign Files .
9)   Read DATA.
10) Display Read Data.
11) Convert Data.
12) Display Converted Data.
13) Create Batch Input Session.
14) Run Batch Input Sesion.

Difference between Null and null?

What is the difference between null and NULL?
When is each used?
Thanks,

veryConfused wrote:
There is a null in java, but no NULL. null means no value. However, when assigning value, the following is different:Although the empty String has no special role. Null means, the referential type is not assigned (doesn't refer) to a specific object. The empty String is just another object though, so seeing it or pointing it out as something special when it actually isn't at all (no more special than new Integer(0) or new Object[0]) just adds to the confusion.

Difference between GUI_UPLOAD and WS_UPLOAD

Hi,
Please make me clear about the difference between GUI_UPLOAD and WS_UPLOAD. In which cases we need to use these modules...??
Thanks,
Satish

I would suggest to always use the GUI_UPLOAD. I say this because this is the function module which is used in the GUI_UPLOAD method of the class CL_GUI_FRONTEND_SERVICES.   Really, you should probably use the class/method instead of the function module.
data: filename type string.
filename = p_file.
call method cl_gui_frontend_services=>gui_upload
         exporting
              filename                = filename
              filetype                = 'ASC'
         changing
              data_tab                = iflatf
         exceptions
              file_open_error         = 1
              file_read_error         = 2
              no_batch                = 3
              gui_refuse_filetransfer = 4
              no_authority            = 6
              unknown_error           = 7
              bad_data_format         = 8
              unknown_dp_error        = 12
              access_denied           = 13
              others                  = 17.
Regards,
Rich Heilman

Difference between sapscripts and BDCs

Similar Messages

Maybe you are looking for