Difference between certification and integration programs

Hi
I am trying to understand the difference in SAP certification programs. We are looking for a 3rd party solution and want to know what we should we ask for with respect to fully integrated with SAP. Does anyone know the difference between "Powered by Netweaver, certified for Netweaver, Endorced solutions, extensions etc.?
Any information is appreciated!

Similar Messages

Differences between trigger and Integrity Constraints

waht are the differences between trigger and Integrity Constraints

waht are the differences between trigger and Integrity ConstraintsConstraints are to be preferred:
"Declarative Ease
Define integrity constraints using SQL statements. When you define or alter a table, no additional programming is required. The SQL statements are easy to write and eliminate programming errors. Oracle controls their functionality. For these reasons, declarative integrity constraints are preferable to application code and database triggers. The declarative approach is also better than using stored procedures, because the stored procedure solution to data integrity controls data access, but integrity constraints do not eliminate the flexibility of ad hoc data access.
Centralized Rules
Integrity constraints are defined for tables (not an application) and are stored in the data dictionary. Any data entered by any application must adhere to the same integrity constraints associated with the table. By moving business rules from application code to centralized integrity constraints, the tables of a database are guaranteed to contain valid data, no matter which database application manipulates the information. Stored procedures cannot provide the same advantage of centralized rules stored with a table. Database triggers can provide this benefit, but the complexity of implementation is far greater than the declarative approach used for integrity constraints."
More:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/data_int.htm#sthref2976

Difference between IntegrationServer and Integration Engine

Hi,
Could you please provide me difference between IntegrationServer and Integration Engine.
functionality of both and what are the runtime environments exits in XI Server.
Could you please show me digaram how message flow from
XI server i.e., through which engines.. what is the input and output of each engine.
Thanks,
RamuV

Hello Ramu,
Go through this link..
http://help.sap.com/saphelp_nw04/helpdata/en/e1/0c733cb7d61952e10000000a11405a/frameset.htm
Use
Two SAP XI 3.0 Integration Servers are used to exchange messages between the system landscapes of two business partners.
Description
An SAP XI Integration Server of a business partner is connected to the SAP XI Integration Server of another business partner. Both use SAP XI message protocol to send or receive messages.
When an SAP XI Integration Server receives a message from another Integration Server it understands the message format and so processes the message.
Example
A business partner that uses SAP XI wants to send a message to another business partner who also uses SAP XI .
·        The message is sent between the Integration Servers in SAP XI message format
·        The Integration Server of the second business partner then sends the message to the relevant business system
Integration Engine
Purpose
The Integration Engine enables you to process XML messages exchanged between applications in heterogeneous system landscapes. Both applications of SAP components and external applications can communicate with the Integration Engine.
Using adapters, the Integration Engine can also process IDocs (Intermediate Documents) and RFCs (Remote Function Calls). This option is available for applications that have already defined IDocs or RFCs, as well as for applications of SAP components that do not yet have access to the proxy generation functions.
Integration
The Integration Engine is the runtime environment of the SAP Exchange Infrastructure. The following are examples of other important parts of this infrastructure:
·        Proxy Generation
·        Integration Repository
·        Integration Directory
The integration processes involved can take place between heterogeneous system components within a company, as well as between business partners outside company boundaries.
Features
The Integration Engine, as a runtime component of SAP Exchange Infrastructure, has the task of receiving, processing, and forwarding XML messages. During message processing, collaboration agreements are evaluated, the receivers are determined, and mapping activities are executed.
The individual processing steps are called pipeline services and are defined in pipelines. It is the task of the Integration Engine to process these pipelines correctly and consistently. To guarantee this, you must configure the Integration Engine accordingly and monitor the message processing. Both event-driven message processing and prioritized message processing are possible.
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on Apr 22, 2008 3:34 PM

Difference between exit and leave program

Hi,
what is the difference between exit and leave program.
I want to come to sap screen which one have to use.?
Thanks,
srii.

Hi,
EXIT is used to end the Further processing after The EXIT Statement if the condition does not meet.
The output before EXIT is then Displayed.
But LEAVE PROGRAM is used to Leave the defined program just after the the Statement.
Generally if to Coming Back to Calling Program after the Processing of Called Program it is used.Or After a Certain Statement if you want to Leave the program.
Follow the link-
http://help.sap.com/saphelp_nw2004s/helpdata/en/71/9f893f17493c17e10000000a114084/content.htm
http://www.sapbrainsonline.com/ARTICLES/TECHNICAL/ABAP/CALL%20ANOTHER%20PROGRAM%20FROM%20LIST.html
http://help.sap.com/saphelp_nw70/helpdata/en/9f/dba50035c111d1829f0000e829fbfe/content.htm
Regards,
Sujit

Difference between Workflow and Integration Process

Hi Experts,
Can someone please explain, what is the difference between the workflow and integration process(BPM).
Thanks
Sree

Hi Sree,
Integration Processes are :-
--Message based
--Interface focused
--Cross component
--Have no support for human interaction
--Enabled with SAP XI
Workflows are:-
--Object based
--Human focused
--Intra-application
--Have no support for mapping, routing or message transformations
--Enabled with the SAP Web AS
However, most automated business processes involve a combination of the two.
I hope this clear your doubt.
Regards.
Praveen

CS5 - Color difference between Photoshop and other programs

I'm running CS5.5 student edition on a brand new Asus Q500A laptop running Windows 8. i7 processor and a UMA graphics card.
I do not have calibration software; I'm using Calibrize for the moment and colors appear fairly true when browsing after calibration.
My problem is that overall colors in Photoshop appear more saturated than those in regular browser windows, particularly reds. I set up my computer to run the Win8 photos app and my desktop with Photoshop simultaneously and the color difference was immediately noticeable. I did a quick screen grab to show the difference; the inset photo is the one viewed in Win8's photos app, and the background is the exact same photo open in Photoshop.
This is the second install of this program. I originally installed it on a Dell Inspiron with a DuoCore processor (way out of spec, I know - that's why I upgraded!) and I seem to remember having this issue then, too. I found a way to correct it, but I don't remember how I fixed it and Photoshop is no longer on that machine so I can't look over my settings.
I have not changed the color profile in Photoshop. When installed it chose North America General Purpose 2 as default and I've left it there. I experimented with the other color profiles and while the color tone in Photoshop changes, there is still a difference when the image is viewed in another program.
Any help is much appreciated - I can't trust the program to handle color properly right now and until I can, I'm dead in the water.

I'm sorry, but I have to disagree. When I view the image on another computer or my iPhone, the image views properly. It's my photography, from a tree in my back yard. I know how the image is supposed to look, and right now it doesn't look right in Photoshop.
On my previous machine, I am almost positive that it was saving as sRGB by default as well. I don't remember what color profile I was working in, but I know that I did not have a color profile/space error pop up on opening new images, nor do I have that problem on other images saved on that machine that I'm opening on the laptop.

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

What is the programming (ABAP) difference between Unicode and non Unicode?

What is the programming(ABAP) difference between Unicode and non Unicode?
Edited by: NIV on Apr 12, 2010 1:29 PM

Hi
The difference between programming in Unicode or not Unicode is that you should consider some adjustments to make on the Program "Z" to comply with the judgments Unicode Standard.
In the past, developments in SAP using multiple systems to encode the characters of different alphabets. For example: ASCII, EBCDI, or double-byte code pages.
These coding systems mostly use 1 byte per character, which can encode up to 256 characters. However, other alphabets such as Japanese or Chinese use a larger number of characters in their alphabets. That's why the system using double-byte code page, which uses 2 bytes per character.
In order to unify the different alphabets, it was decided to implement a single coding system that uses 2 bytes per character regardless of what language is concerned. That system is called Unicode.
Unicode is also the official way to implement ISO/IEC 10646 and is supported in many operating systems and all modern browsers.
The way of verifying whether a program was adjusted or not, is through the execution of the UCCHECK transaction. Additionally, you can check by controlling syntax (making sure that this asset verification check Unicode).
The main decisions to adjust / replace are (examples):
ASSIGN H-SY-INDEX TEXT TO ASSIGN <F1> by
H-SY-INDEX TEXT (*) TO <F1>.
DATA INIT (50) VALUE '/'. by
DATA INIT (1) VALUE '/'.
DESCRIBE FIELD text LENGTH lengh2 by
DESCRIBE FIELD text LENGTH lengh2 in character mode.
T_ZSMY_DEMREG_V1 = record_tab by
record_tab TO MOVE-Corresponding t_zsmy_demreg_v1.
escape_trick = hot3. by
escape_trick-x1 = hot3.
itab_txt TYPE wt by
ITAB_TXT TYPE TABLE OF TEXTPOOL
DATA: string3 (3) TYPE X VALUE B2023 '3 'by
DATA: string3 (6) B2023 TYPE c VALUE '3 '.
OPEN DATASET file_name IN TEXT MODE by
OPEN DATASET file_name FOR INPUT IN TEXT MODE ENCODING NON-UNICODE.
or
OPEN DATASET file_name FOR INPUT IN TEXT MODE ENCODING DEFAULT.
CODE FROM PAGE TRANSLATE a_codepage record by
record TRANSLATE USING a_codepage.
CALL FUNCTION 'DOWNLOAD' by
CALL METHOD cl_gui_frontend_services => gui_download
CALL FUNCTION 'WS_DOWNLOAD' by
CALL METHOD cl_gui_frontend_services => gui_download
CALL FUNCTION 'UPLOAD' by
CALL METHOD cl_gui_frontend_services => gui_upload
CALL FUNCTION 'WS_UPLOAD' by
CALL METHOD cl_gui_frontend_services => gui_upload
PERFORM USING HEAD APPEND_XFEBRE +2. by
PERFORM USING HEAD APPEND_XFEBRE +2 (98).
Best Regars
Fabio Rodriguez

Difference Between BAPI And RFC in ABAP

Hi,
i want to know difference between BAPI and RFC in SAP,
can we call SAP GUI screen from NON SAP System Using BAPI.
Reg,
Hariharan

Hi Ravishankar,
The difference is not importat while you understand the concept.
I think, RFC is the protocol for calling functions from external systems in R/3.
I understand like BAPI a series of complet functions that SAP offers you for use and model a business use.
But if I need program a function that can be called for external system i would call it RFC_NAME, because is a unique function that makes a single task.
In other words, the difference i think is about work idea more than another thing.
RFC
A remote function call is a call to a function module running in a system different from the caller's. The remote function can also be called from within the same system (as a remote call).
RFC consists of two interfaces : A calling interface for ABAP Programs and a calling interface for Non-SAP programs.
The RFC Interface takes care of :-
- Converting all parameter data to the representation needed in the remote system
Calling the communication routines needed to talk to the remote system.
Handling communications errors, and notifying the caller, if desired ( using EXCEPTIONS paramater of the CALL FUNCTION).
BAPI
BAPIs are standardized programming interfaces (methods) enabling external applications to access business processes and data in the R/3 System.
BAPIs provide stable and standardized methods to achieve seamless integration between the R/3 System and external applications, legacy systems and add-ons.
BAPIs are defined in the BOR(Business object repository) as methods of SAP business object types that carry out specific business functions.
BAPIs are implemented as RFC-enabled function modules and are created in the Function Builder of the ABAP Workbench.
The most critical difference btwn BAPI and FM is that BAPI can be wrapped in Business objects whereas RFC cant.
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Check these Links out
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
Refer following SDN threads:
Diff. Between BAPI and RFC
Re: BAPI and RFC
Hope this resolves your query.
Reward all the helpful answers.
Regards

Difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports

Could someone explain in simple way what is the difference between BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports? I have read the differences in standard documentation but it is a little confusing.
Thanks!
Regards,
Madhur

Hi
CLEAN_REQREQ_UP (Cleaner Job)
You can use this function for document types Shopping cart, (Local) Purchase Order, Confirmation, and Invoice to trigger a synchronization with the associated documents in the back-end system. The system checks whether and how the (follow-on) documents were posted in the back end, and updates the object link and references, as well as the document status.
A job (background processing) is generated for the program CLEAN_REQREQ_UP. When this is run, the system queries a database table containing the transfer information of the documents to the back end. The entries are checked with the data of the respective back-end systems. If the back-end transfer is successful, the respective entries are deleted and the prerequisites for further processing are created.
BBP_GET_STATUS2 (Status Job)
The status job was created by SAP to update the EBP system with data such as purchase requisition number, purchase order number, goods received or invoices recorded manually in R/3, etc. The report should not be run on a frequent basis at short intervals unless the order count from EBP to R/3 is not that high. Otherwise, a recommended interval for running the report is approximately every hour. Basically the schedule times depend on your business requirements.
Until this job runs, the user will not see the number of the backend document created in R/3 for a particular shopping cart in the history tab of the check status transaction.
Some more information :
Go to:
SPRO->IMG->Integration with Other SAP components->Advanced Planning and
Optimization->basic Settings for the Data Transfer->Change Transfer->
change Transfer for Transaction Data->Active Online Transfer using BTE
Here you should maintain the application 'SRMNTY' with active flag.
Once this customizing is enabled, whenever a follow-on document
(either confirmation or invoice) for an extended classic PO is created
in the backend R/3 system, the R/3 system communicates to the SRM system
by creating an entry in the table BBP_DOCUMENT_TAB for this PO.
The item level of the SRM PO has fields to store the actual quantity
and values entered for the corresponding confirmations and invoices.
After that, run the reports CLEAN_REQREQ_UP and BBP_GET_STATUS_2.
When the report CLEAN_REQREQ_UP runs this will update the
PO with statistical information. With the latest information in
BBP_PDIGP table (statistical information) the query should work fine.
Summer

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

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

What is the difference between ABAP and HR-ABAP?

Hi people,
Could u just tel me abt what is the difference between ABAP and HR-ABAP?
Thanks in advance,
Sanjeev K.V

Hi Sir ,
Please have a look below .Hope it is suitable and simpler solution for your question.
Please do reward if useful.
Thankx.
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
Also,
HR:
HR deals with the INFOTYPES which are similar to Tables in General ABAP.
There are different ways of fetching data from these infotypes.
There are different areas in HR LIKE Personal Admn, Orgn Management, Benefits, Time amangement, Event Management, Payroll etc
Infotypes for these areas are different from one another area.
storing of records data in each type of area is different
LDBS like PNP are used in HR programing.
Instead of Select.. we use some ROUTINES and PROVIDE..ENDPROVIDE.. etc
and in the case of Pay roll we use Clusters and we Import and Export them for data fetching.
On the whole Normal ABAP is different from HR abap.
For Personal Admn the Infotypes start with PA0000 to PA1999
Time Related Infotypes start with PA2000 to PA2999.
Orgn related Infotypes start with HRP1000 to HRP1999.
All custom developed infotypes stsrat with PA9000 onwards.
In payroll processing we use Clusters like PCL1,2,3 and 4.
Instead of Select query we use PROVIDE and ENDPROVIDE..
You have to assign a Logical Database in the attributes PNP.
Go through the SAp doc for HR programming and start doing.
http://www.sapdevelopment.co.uk/hr/hrhome.htm
See:
http://help.sap.com/saphelp_46c/helpdata/en/4f/d5268a575e11d189270000e8322f96/content.htm
sites regarding hr-abap:
http://www.sapdevelopment.co.uk/hr/hrhome.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPA/PAPA.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PAPD/PAPD.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PYINT/PYINT_BASICS.pdf
http://www.atomhr.com/training/Technical_Topics_in_HR.htm
http://www.planetsap.com/hr_abap_main_page.htm
You can see some Standard Program examples in this one ...
http://www.sapdevelopment.co.uk/programs/programshr.htm
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci1030179,00.html?Offer=SAlgwn12604#Certification
http://www.erpgenie.com/faq/hr.htm.
http://www.planetsap.com/hr_abap_main_page.htm
http://www.sapbrain.com/TUTORIALS/FUNCTIONAL/HR_tutorial.html
These are the FAQ's that might helps you as well.
http://www.sap-img.com/human/hr-faq.htm
http://www.sapgenie.com/faq/hr.htm
http://www.planetsap.com/hr_abap_main_page.htm
http://www.atomhr.com/library_full.htm
HR Long texts Upload
Look at the below link
And finally,
Few notes are below:
InfoSets in the HR Application
You can use SAP Query in HR to report on HR data. Queries are maintained as described in Creating Queries. The special features of queries created for HR are described in Maintaining Queries in the Human Resources Application. The maintenance procedure for HR InfoSets differs from the described procedure inasmuch as HR data fields are grouped together in infotypes.
InfoSet management in SAP Query is also used for InfoSet Query. For further information, see Functions for Managing InfoSets.
If you want to create InfoSets for HR, you can use logical databases PNP, PNPCE, PAP, and PCH (see HR Logical Databases). The database you must use to create your InfoSet depends on the component in which the data you want to report on is stored.
The reports you can execute using InfoSets based on logical databases PNP (or PNPCE) or PCH are similar, but differ in that they can select different objects. The following table describes the connection between the logical database, and the infotypes you can include in an InfoSet. It also provides you with one or two examples of reports that you can execute using the appropriate InfoSets.
Logical database PNP/PNPCE* PCH PAP
Selection of Persons Objects from Personnel Planning Applicants
Infotypes that can be included in the InfoSet Infotypes for· Personnel Administration (0000-0999) · Time Management (2000-2999) · Payroll infotypes · Infotypes for Personnel Planning objects that can be related to persons If the object type is specified:· Infotypes for the object type · Infotypes for objects that can be related to the specified object typeIf the object type is not specified:· All infotypes · Infotypes for Recruitment (4000-4999)· Some infotypes for Personnel Administration (such as 0001 and 0002)
· Customer infotypes
Reporting examples · Selection of all persons who participated in a specific business event, output of prices for reserved business events · Selection of all persons assigned to a specific personnel area, output of qualifications held by these persons · Selection of all business events held in London in March, output of all persons who participated in these business events · Selection of all positions assigned to a specific organizational unit, output of all persons assigned to the positions · Selection of all applicants hired last year to work on special projects, output of addresses for the applicants selected
Logical database PNPCE (PNP Concurrent Employment) functions just like logical database PNP. The procedure for creating InfoSets is also the same. It only becomes significant if you work with Concurrent Employment.
Creating InfoSets
The maintenance procedure for HR InfoSets differs from the procedure described so far in this section inasmuch as HR data fields are grouped together in infotypes. To set up an InfoSet for the HR application, proceed as follows:
1. On the initial screen for maintaining InfoSets, enter a name for the InfoSet and choose Create.
2. On the next screen, enter a name for the InfoSet and select one of the HR logical databases in accordance with your reporting requirements.
Customer infotypes can be created on all HR logical databases. In each individual case, therefore, you must decide which database to select so that you can report on customer infotypes.
This screen enables you to enter an authorization group. All of the queries that are subsequently created using this InfoSet can only be executed by persons who have this authorization group.
3. Choose .
This takes you to the Infotype Selection for InfoSet screen. You now have the option of creating field groups and assigning fields as required for non-HR InfoSets. Field groups that correspond to infotypes and already contain fields, however, are always created for HR InfoSets. The field groups are displayed in an overview tree in the top right section of the screen.
The infotypes that you included in the InfoSet are displayed in an overview tree on the left of the screen. The infotype fields that are already included in field groups are displayed in a different color, and the corresponding field group ID is displayed.
In the standard system, a field group is created automatically for each infotype that you included in the InfoSet (a field group corresponds to an infotype).
In the standard system, each field group contains the infotype-specific fields. To ensure that working with the InfoSet is as easy as possible, you are advised to restrict your use of fields in each field group to those you really require. This means you should remove fields that are not required.
An infotype's fields must only be assigned to the pertinent field group. Make sure this assignment is correct. If the assignment is incorrect, the InfoSet could be rendered unusable.
When an InfoSet is created, the following fields are transferred automatically to the first field group:
§ Logical database PNPCE or PNP Personnel number
§ Logical database PAP Applicant number
§ Logical database PCH Object ID, plan version, and object type
6. Determine the fields that must be included in the field groups of your InfoSet. If you require further information, see Assigning Fields to a Field Group.
If you want, you can change the default sequence of field groups and fields as required using Drag&Drop.
7. To save the InfoSet, choose .
8. To generate the InfoSet, choose .
On the Change InfoSet (InfoSet name) screen, you can choose Edit ® Change infotype selection to add more infotypes to the InfoSet, or to remove infotypes from the InfoSet. Remember to regenerate the InfoSet afterwards.
This screen also enables you to update InfoSets if, for example, the system contains new additional fields for specific key values. To do so, choose InfoSet ® Additional functions ® Update additional HR fields.
9. Go back to the initial screen for InfoSet maintenance.
10. Choose User group assignment.
11. Select a user group, and save your entry.
sample code
START-OF-SELECTION.
GET pernr.
rp_provide_from_frst p0000 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0001 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0001-plans. " earliest.
endif.
endif.
rp_provide_from_last p0014 space pn-begda pn-endda.
if pnp-sw-found EQ '1'.
READ TABLE p0014 WITH KEY pernr = p0000-pernr.
if sy-subrc = 0.
write : p0014-LGART. .
endif.
endif.

Difference Between SCA and SDA

Hi,
I am preaparing for the SAP Certification exam , my exam is on 20 of this month . Can anyone explain me the difference between SCA and SDA .How are they different from each other and the benefits of using them.
appreciate quick responses.

Hello,
Here u go ...
The Software Deployment Archive (SDA) is the delivery format for SAP applications in programming languages other than ABAP, for example applications of the J2EE Engine. It is an archive format that is compatible with ZIP and that can be used as a container for other archives. The SDA contains the manifest information, that is package-related data of the contained archive (e.g. jar, war) and an SAP manifest containing additional information about the software logistics. Larger entities can be created in SCA format in the second step from the different SDAs. A Software Component Archive (SCA) is the physical representation of a version of a software component. It contains a selection of SDAs that describe a precise version. Updating an SCA always results in a new version of the software component.
I hope this solves your question
Thanks
Pankaj

Difference between validation and susbstittution with tcodes

hi all can any body tell me about difference between validation and susbstittution with tcodes
regars
sravya

Hi,
Settting up the FI Validations
You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.
For e.g. to allow postings from company code 0001 to business area AA only.
GGB0 - To maintain the validations
Validation - Enter a validation name e.g. VBUS
Applicaion Area - SAP module e.g. FI
Calling Point - Dependent upon the application area that is selected.
0001 - Document Header - validate enteries at document header, e.g BKPF table
0002 - Line Items - check line item entris within a document, e.g. BSEG table
0003 - Complete Document - check settings for the whole documents.
e.g. Validation step 001
Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.
If checks failed, the error message number 14 is displayed to stop the transaction.
Prerequisite
<BSEG> $BUKRS = '0001' AND
<BKPF> $GLVOR = 'FI00'
Check
<BSEG> $GSBER = 'AA'
Message
Type E No. 14 - Business Area not allowed for company 0001
Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS
3 - 4
OB28 - Define Validations for Posting
CC CallPnt Validation Description Activtn Level
0001 2 VBUS Business Area Validation 1
Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input
GGB4 - Manage the activation of all validations in the SAP system.
Validations, Substitutions, and Rules
Purpose
With the validations and substitutions software, you can validate and/or substitute data at the time of entry in the FI-SL System and other SAP Systems.
Implementation Considerations
You do not need to change the standard system to customize your validations and substitutions. For each installation, you can define exactly which validations and substitutions are necessary to ensure the integrity of your data.
Features
Validation
In the SAP System, almost all input values are validated by a program or against tables or master files. Since some types of validations cannot be standardized, you can use FI-SL's validations program to create validations for your system.
With validations, you can check values and combinations of values as they are being entered in the SAP environment. Validation rules are stored in the Rule Manager; as data is entered, the Integration Manager validates the data against the validation rules stored in the Rule Manager. Because data is validated before it is posted, only valid information enters the FI-SL System.
You define validation rules using Boolean logic. When you define a validation rule, the system checks the validation rule to ensure that it is syntactically correct.
You can also define the result of breaking the validation rule. For instance, you can specify that a message is issued but the user can continue processing. You can also force the user to correct the error before processing can continue.
For more information, see Validation or What Are Validations?. For more information on using validations, see Creating a Validation. For more information on Boolean Logic, see Introduction to Boolean Logic.
Substitution
Substitution rules are stored in the Rule Manager. When data is entered in the system, it is substituted by the Integration Manager. The Integration Manager calls the Rule Manager. Substitution occurs before the data is posted to the FI-SL databases.
You define substitution rules using Boolean logic. When you define a substitution rule, the system checks the substitution rule to ensure that it is syntactically correct.
For more information, see Substitution or What Are Substitutions?. For more information on using substitutions, see Creating a Substitution. For more information on Boolean Logic, see Introduction to Boolean Logic.
Rules
A rule is a Boolean expression that you can use as a condition, as a check, or in another rule. Rules enable you to refer to frequently used Boolean statements simply by specifying the rule name.
The FI-SL Integration Manager uses Boolean logic. When you use Boolean logic and syntax, you can:
Validate data
Substitute data
Select ledgers for posting
Transfer substitution data to a rollup ledger
Select report data
The Rule Manager stores the Boolean rules used to analyze data. The Integration Manager calls the Rule Manager and determines whether entered data should be used. If a Boolean statement is true, an action is taken; if a statement is false, no action is taken.
Boolean logic is used in the following FI-SL modules:
Validation
Substitution
Ledger selection
Report Writer
Rollups
To use Boolean Logic in one of the functions listed, you create statements that are used as formulas in the FI-SL System. For more information on using Boolean Logic, see Introduction to Boolean Logic or Boolean Logic Statements and Rules.

Difference between certification and integration programs

Similar Messages

Maybe you are looking for