Difference between batch input method and direct input method in LSMW.

Hi all,
what is difference between batch input method and direct input method in LSMW. are they same?if differences are there tell me with details?

Hi,
Here are few differences bw Batch Input and Direct Inputs methods.
Batch Input: Uses classical BDC approach, but doesn't required an ABAP program to be written to format the BDC DATA. The user has to format the data using predefined structures and store it in a flat file. Yet it is a slower updation method.
Direct Input: Works similar to Batch Input programs. The difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. Much faster and suits for large volume of data.
Thanks.
DhanaLakshmi M S

Similar Messages

Difference between Realtime Data Acqisition and Direct Data Access ?

Hi experts,
What is RDA and DDA and whrere these two are used ?
What is the Difference between Realtime Data Acqisition and Direct Data Access?
Please explain me in a detail manner, i will assign points for ur valuable answers..............

Hi,
Eventhough the aim of the two methods are to report on the latest data, there is a difference in both.
In Realtime Data Acqisition you are loading the data into BW and then reporting on that data from BW Infoproviders.
http://help.sap.com/saphelp_nw04s/helpdata/en/52/777e403566c65de10000000a155106/content.htm
I think you are refering to Virtual providers by the term Direct Data Access. In Direct Data Access you are not loading data into BW. Data is residing in R/3 itself. Your reports will fetch data from R/3 directly. The data is called during execution of a query in the source system.
http://help.sap.com/saphelp_nw04s/helpdata/en/23/c0234239f75733e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/13/3e34429692b76be10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/da/5909392a430303e10000000a114084/frameset.htm
Hope this helps.
Thanks,
JituK

Can anyone Explain me the difference between Batch Input, Direct input met

Can anyone Explain me the difference between Batch Input Method and Direct Input Method.

hi
good
Direct input method                     Batch Input Method
1) We cannot send the fields   | 1) We can send fields as per
   according to our requirement|    requirement.
2) validations are done based
2) validations are done based
   on pre-defined function
on applications.
   modules
Batch Input Session:
- It is a sequence of transactions, which is generated when user run a particular program.
- It contains the accounting documents that are to be created. The SAP system stores these transactions until you decide to process them online.
- It does not update transaction figures until the session has been processed. Using this technique, you can transfer large amounts of data to the SAP system in a short time.
Three processing modes of executing Batch Input Session :-
(1) Run Visibly : You can correct faulty transactions online & work step-by-step through the transactions not yet executed.
(2) Display Errors only : You can correct faulty transactions online.   Transactions not yet executed, but without error, run in the background.
(3) Run in Background : Recommended by SAP.
thanks
mrutyun^

Difference between Batch input and Direct Input

Hi please tell me the difference between Batch Input and Direct Input in BDC?

hi aparna,
DIRECT INPUT
TO ENTER THE DATA INTO THE CORRESPONDING DATABASE TABLES DIRECTLY, THE SYSTEM CALLS A NUMBER OF FUNCTION MODULES THAT EXECUTE ANY NECESSARY CHECKS. IN CASE OF ERRORS, THE DIRECT INPUT TECHNIQUE PROVIDES A RESTART MECHANISM. HOWEVER, TO BE ABLE TO ACTIVATE THE RESTART MECHANISM, DIRECT INPUT PROGRAMS MUST BE EXECUTED IN THE BACKGROUND ONLY. DIRECT INPUT CHECKS THE DATA THOROUGHLY AND THEN UPDATES THE DATABASE DIRECTLY.
TO MAINTAIN AND STRAT THESE PROGRAMS, USE PGM RBMVSHOW OR THE TRANSACTION BMVO.
BATCH INPUT
TYPES SESSION METHOD, CALL TRANSACTION, DIRECT INPUT.
TO SAVE DATA IN THE BDCTAB, USE THE FIELDNAME BDC_OKCODE AND FIELD VALUE OF /11.
BDCDATA
THIS IS A STRUCTURE WHICH CONTAINS THE FOLLOWING FIELDS.
PROGRAM NAME OF TH MOD PROG ASSOCIATED WITH THE SCREEN. SET ONLY FOR THE FIRST RECORD OF THE SCREEN.
DYNPRO SCREEN NUMBER. ALSO SET ONLY FOR FIRST RECORD.
DYNBEGIN INDICATES THE FIRST RECORD OF THE SCREEN. SET X FOR FIRST RECORD OTHERWISE .
FNAM FIELD NAME.
FVAL VALUE FOR THE FIELD NAMED IN FNAM.
THE FIRST STEP IN BDC IS TO UPLOAD DATA FROM THE FLAT FILE OR SEQUENTIAL FILE TO THIS BDCTABLE.
SESSION METHOD
WE USE 3 FUNCTION MODULES IN THIS SESSION METHOD.
1) BDC_OPEN_GROUP
 USER NAME: USER NAME
 GROUP: NAME OF THE SESSION
 LOCK DATE: THE DATE ON WHICH YOU WANT TO PROCESS THE SESSION.
 KEEP: THIS PARAMETER IS PASSED AS X WHEN YOU WANT TO RETAIN SESSION AFTER PROCESSING IT OR TO DELETE IT AFTER PROCESSING.
THIS CREATES A SESSION
2) BDC_INSERT
 TCODE: TRANSACTION NAME
 DYNPROTAB: BDC DATA
THIS CREATES A SEESION AND DATA IS TRANSFERRED O SESSION.
3) BDC_CLOSE_GROUP THIS CLOSES THE BDC GROUP.
ONLY ONE SESSION CAN BE CREATED USING BDC_OPEN_GROUP. BUT MULTIPLE TRANSACTIONS CAN BE PROCESSED USING BDC_INSERT.
CALL TRANSACTION
CALL TRANSACTION <TCODE> USING <BDCTAB>
 MODE <A/N/E>
 UPDATE <S/A>
 MESSAGES INTO <MSGTAB>.
A ALL SCREEN MODE. ALL THE SCREEN OF THE TRANSACTION ARE DISPLAYED.
N NO SCREEN MODE. NO SCREEN IS DISPLAYED WHEN YOU EXECUTE THE TRANSACTION.
E ERROR SCREEN. IF THE SCREEN HAS ERROR RECORD, THEN THAT SCREEN WILL BE DISPLAYED.
S - IF YOU CHANGE DATA OF ONE TABLE THEN ALL THE RELATED TABLES GETS UPDATED. AND SY-SUBRC IS RETURNED I.E., SY-SUBRC IS RETURNED FOR ONCE AND ALL.
A - WHEN YOU CHANGE DATA OF ONE TABLE, THE SY-SUBRC IS RETURNED. AND THEN UPDATING OF OTHER AFFECTED TABLES TAKES PLACE. SO IF SYSTEM FAILS TO UPDATE OTHER TABLES, STILL SY-SUBRC RETURNED IS 0 (I.E., WHEN FIRST TABLE GETS UPDATED
WHEN YOU UPDATE DATABASE TABLE, OPERATION IS EITHER SUCCESSFUL OR UNSUCCESSFUL OR OPERATION IS SUCCESSFUL WITH SOME WARNING. THESE MESSAGES ARE STORED IN INTERNAL TABLE, WHICH YOU SPECIFY ALONG WITH MESSAGE STATEMENT. THIS INTERNAL TABLE SHOULD BE DECLARED LIKE BDCMSGCOLL, A STRUCTURE AVAILABLE IN ABAP/4. IT CONTAINS THE FOLLOWING FIELDS: TCODE, DYNAME, DYNUMB, MSGTYP, MSGID.
DIFFERENCE BETWEEN SESSION AND CALL TRANSACTION
 SESSION METHOD CALL TRANSACTION
1. DATA IS NOT UPDATED IN DATABASE TABLE UNLESS SESSION IS PROCESSED. IMMEDIATE UPDATION IN DATABASE TABLE.
2. NO SY-SUBRC IS RETURNED. SY-SUBRC IS RETURNED.
3. ERROR LOG IS CREATED FOR ERROR RECORDS. ERRORS NEED TO BE HANDLED EXPLICITLY
4. UPDATION IN DATABASE TABLE IS ALWAYS SYNCHRONOUS
 UPDATION IN DATABASE TABLE CAN BE SYNCHRONOUS OR ASYNCHRONOUS.
5. ASYNCHRONOUS PROCESSING SYNCHRONOUS PROCESSING
6. TRANSFERS DATA FOR SINGLE TRANSACTIONS TRANSFERS DATA FOR MULTIPLE TRANSACTIONS
ERROR HANDLING IN CALL TRANSACTION
1) CREATE AN INTERNAL TABLE SIMILAR TO THE STRUCTURE OF YOUR LOCAL FILE.
2) CREATE BDCTAB LIKE BDCDATA.
3) CREATE BDCMSG LIKE BDCMSGCOLL.
4) CREATE AN INTERNAL TABLE SIMILAR TO THE 1ST INTERNAL TABLE.
5) UPLOAD FN UPLOADS DATA FROM THE LOCAL FILE TO THE ITAB.
6) LOOP AT ITAB.
POPULATE BDCTAB TABLE.
CALL TRANSACTION STATEMENT.
PERFORM CHECK.
REFRESH BDCTAB.
ENDLOOP.
7) FORM CHECK.
IF SY_SUBRC <> 0.
CALL FUNCTION FORMAT_MESSAGE.
APPEND ITAB2.
ENDFORM.
TRANSACTION FOR RECORDING SHDB.
MAX TIME ALLOWED FOR ONLINE EXECUTION 300 SECONDS.

Pls reward if helpful.

Difference between batch input method and batch input recording in LSMW?

hi,
plz tell me the difference between batch input method and batch input recording in LSMW?
thanks & regards
Ruban

Hi Ruban,
The main difference between the two is in lsmw we can view the code status at any time just by coming to prvious steps, but whereas in batch input method unless the recording is finished we cant view the code.
second diff is tht we need to do lot of coding in batch inptu whereas here in lsmw we need not do much coding and mapping to data.
third diff is that batch input is both inbound and outbound where as lsmw is only inbound.
hope u got the differences.....
Regards,
sana M...

Difference between module on request and module on input

hi,
what is the Difference between module on request and module on input
can any one explain with some examples
Thanks in advance
Ganesh

HI
module on request is triggered when you press F4
module on input is triggered when you enter any value to certain field or change it.
refer this for more details
http://www.jt77.com/development1/programming-19561.html
reward if helpful
thanks
vivekanand
Message was edited by:
vivekanand meghmala

Difference between Session method and Call transaction method

Hi,
Difference between Session method and Call transaction method in BDC

Hi,
SESSION method:
Is a standard procedure for transferring large amount of data into the R/3 system.
Data consistency is ensured because batch input uses all thje checks conducted on the normal screen.
It is a two step procedure:
1. Progarm: creates batch input session. This session is the data file that includes everything to begin the transaction.
2. Process session: Which then actually transfers the data to database table.
In this method an ABAP/4 program reads the external data that is to be entered in the SAP system and stores the data in a session.
A session stores the actions that are required to enter your data using normal SAP transactions i.e. data is transferred to session which inturn transfers data to database table. Session is an intermediate step between internal table and database table.
Data along with it's actions are stored in session. i.e. data for screen fields, to which screen it is passed, the program name behind it and how next screen is processed.
When the program has finished generating the session, u can run the session to execute the SAP transactions in it.
BDC_OPEN_GROUP
 You create the session through program by BDC_OPEN_GROUP function.
1) User Name: User Name.
2) Group : Name of the session
3) Lock Date : The date when you want to process the session.
4) Keep : This parameter is passed as 'X' when you want to retain session even after processing it.
BDC_INSERT
 Data is transferred to session by BDC_INSERT.
BDC_CLOSE_GROUP.
 With this function the session will be closed.
CALL TRANSACTION method.
Syntax: call transaction <tr code> using <bdctab>
 mode <A/N/E>
 update <S/A>
 messages into <internal table>.
<tr code> : transaction code
<bdctab> : Name of the BDC table
mode: mode in which you execute the transaction.
A : all screen mode ( all the screens of the transaction are displayed )
N : no screen mode ( no screen will be displayed when you execute the transaction )
E : error screen ( only those screens are displayed where in you have error record )
Update type:
S: synchronous update in which if you change data of one table then all the related tables gets updated and SY_SUBRC is returned for once and all.
A: asynchronous update in which if you change data of one table, the sy-subrc is returned and then updation of other affected tables takes place. So if system fails to update other tables still sy-subrc returned is zero.(that is when first table gets updated ).
messages: if you update database table, operation is either successful or unsuccessful. These messages are stored in internal table. This internal table structure is like BDCMSGCOLL.
 TCODE: transaction code.
 DYNAME: batch input module name.
 DYNNUMB: batch input dyn no.
 MSGTYP: batch input message type.
 MSGSPRA: batch input language id of message.
 MSGID: message id.
 MSGV1.MSGV5: message variables
For each entry which is updated in the database table message is available in BDCMSGCOLL.
Reward if useful
Regards
Srinu

Difference between center,edge mmcm and edge direct allignments

What is the difference between center, edge mmcm and edge direct allignments.

Both of these terms are used most often used (but not exclusively) when describing source synchronous interfaces.
Edge Aligned vs. Center Aligned
When a device uses source synchronous communication, be it a device that sends data to an FPGA (an input to the FPGA) or a an FPGA sending data to an external device (an output of the FPGA), the device needs to define and describe the timing relationship between the clock and the data that it is forwarding to the other device. The receiving data needs to know this timing relationship in order to devise a mechanism to capture the data.
The timing relationship can really be just about anything, but two types are common:
Edge Aligned:
This is the simplest for the transmitting device. The device simply generates the forwarded clock and data using the same mechanism. If the sending device is an FPGA, then it uses an internal clock to drive an ODDR that drives the forwarded clock, and uses the same clock to send the forwarded data, either using an IOB flip-flop (SDR) or an ODDR flip-flop (DDR).
Using this mechanism, the timing relationship is often (but not always) described as a skew; i.e. the data will change +/-200ps around the edge/edges of the clock.
Of course, this clock/data timing relationship can rarely be used "as is" by the recieving device, so the receiving device will be responsible for adding some delay or other mechanism to use the forwarded clock to capture the forwarded data (i.e. an MMCM shift or an IDELAY).
Center Aligned:
This is supposed to be the simplest mechanism for the receiver. The transmitter uses some internal structure to place the edges of the forwarded clock in the middle of the forwarded data valid window. In an FPGA (as a transmitter), an internal clock would drive an ODDR for the forwarded clock, but the forwarded data would be driven from either an IOB FF using an inverted clock (SDR) or an ODDR using a clock that is 90 degrees out of phase (DDR). (Or it could be vice versa - the data uses the normal clock, and the forwarded clock uses the inverted or 90 degree clock).
Using this mechanism, the clock/data relationship is often (but not always) defined as a provided setup/hold relationship around the forwarded clock; i.e. the data will be valid 1.5ns before the edge of the clock and remain valid for 1.5ns after the edge of the clock.
The idea is that using this timing relationship, the receiver should be able to use the forwarded clock as is to capture the forwarded data. In general, though, this is rarely true, since most devices don't have an equal required setup and hold time; so the receiver still needs to modify the clock/data relationship to center its required window in the provided window.
MMCM vs. Direct Capture
This is a different concept. Regardless of which alignment is used (edge, center or something in between), the receiver (now we are assuming it is the FPGA doing the reception) needs to implement some clocking mechanism to use the forwarded clock to capture the forwarded data. There are really two styles:
Direct Capture:
The forwarded clock is brought in and goes directly to a clock buffer (either BUFG/BUFH or BUFR/BUFIO), which is used to capture the incoming data. Generally (as I said above), the clock/data timing relationship needs to be changed, and when using this capture mechanism, this can only be accomplished using an IDELAY on the clock or data (or both). When done this way, the clock has a propagation delay through the delay element (the IDELAY)
MMCM Capture:
Here, the forwarded clock is brought in on a clock capable I/O, then through an MMCM and from there to a BUFG or BUFH (with feedback to the MMCM). When done this way, the "common" way of modifying the clock/data timing relationship is by adjusting the phase delay of the MMCM output clock.
There is a subtle but extremely important difference in Vivado (and SDC/XDC) between a propagation delay and a phase delay (or phase shift). It has to do with how the tool determines which clock edge will capture data that is generated by a particular clock edge.
When we use a set_input_delay, we describe to Vivado a data window associated with a particular clock edge. By default, that data window will be captured by the next edge of the clock. The definition of the next edge is different when using these two mechanisms.
When a clock edge is propagated through a delay element, the resulting clock is the same edge. Lets take the example of a 10ns clock (rising at 0ns, falling at 5ns) with a 2ns delay (using an IDELAY) capturing an SDR data. The rising edge at time 0ns will generate a data window. By default, it will be captured by the next clock edge, which is at 10ns. After the 2ns of propagation delay, the internal clock at 12ns will be used to capture the window.
When a clock is phase shifted, a new clock is generated. Using the same example using an MMCM, the output clock of the MMCM rises at 2ns and falls at 7ns (and rises again at 12ns). So, the data window defined by the first rising edge of the input clock (at time 0), will be captured by the next rising edge of the phase shifted clock, which is at 2ns (this 2ns rising edge of the phase shifted clock is the "next" edge after the 0ns edge that generated the data window). This is different than the previous example, where the internal edge at 12ns (not 2ns) would capture the first window.
As a result, the constraints you use to describe the timing relationship (the set_input_delay) needs to be different between these two styles. Its also a bit messy, since the constraints that are correct for an MMCM with 2ns (or even 0.01ns) of phase delay are not correct for an MMCM with 0ns of phase delay (which is a bit icky).
I hope that clears things up!
Avrum

Difference between jsp:forward sendRedirect and jsp include directive

Am very much confused, please explain me the difference between
jsp:forward sendRedirect and jsp include directive with a suitable example.
I'll be very gratefull. Its very urgent.

One basic difference. The include executes in the .jsp servelet created. The redirect transfers "control" by redirecting the client request to another destination. In other words, the current .jsp is no longer in charge or in the calling chain in any way.

What's the difference between batch class type 022 and 023?

Hi Guys,
I find that some of my SAP client only have class 022 and some have 023, but no client has them all. I don't know why it happed.
So what's the difference between batch class type 022 and 023? Which setting decide which class to be used ?
Thanks.

Hi nitin,
Read http://www.sapfans.com/forums/viewtopic.php?t=212819&highlight=022 you will know the difference between 022 and 023 .
Use tcode OMCT you can switch batch level .

The difference between batch class type 022 and 023

what's difference between batch class type 022 and 023? 023 is described as standard batch class type, but there is only 022 type exists in my system. can i use 022?

Hi,
both classes mean the same, but which class is used is decieded by batch level. In case of material level or client level the system use automatically only class 023. If you define batch level to plant the system use automatically class 022.
Regards,
Abhee.

What is the difference between organisation payment method and Assignment payment method?

What is the difference between organisation payment method and Assignment payment method?
As i am a new bie, i am curious to know this though it might sound a silly question.
Thank you,
Kuton

You can create an Organization payment method of any Payment type(Cash, Check, BACS, NACHA etc) under the same country.
All these will be valid payment methods on the payroll description form.
And you can even attach these to a person.
In which case you will have a Base currency (say USD) and payment currency (say GBP).
These cases are not normal and only used by people who use a single BG for paying employees in 3-4 countries.
So, unless you need to pay in different currencies, do not use it.
Cheers,
Vignesh

Difference between batch and lot size

What is the difference between batch size and lot size. How do these quantities relate to production planning & machine capacity planning.
Regards

Hi,
Lot size: Some times specific materials are not referred individually but are represented in groups or lots.
When we maintian BOM/production version/routing it is sometime convinenit to maintain compoenent qty / operaion times ect.. for speciifc lots .. we also call them base qty.
we can create different master data for different lot sizes and it is consider in auto selection of this master data in production orders.
MRP can also intiate procurement / production in speciifc lots and this lot size in size is maintained in material master ans lot sizing procedure is maintianed in MRP customiziation.
Batch Size: some times batch size and lot size can be interheprited same in busienss langauge but they have fundamental
difference from SAP point of view. .
In SAP Batch is homoginious non reproducible Unit of material. The batch zise depends on GR qty of the specific batch.

What is the difference between Batch determination and Batch derivation?

Please explain the difference between batch determination and batch derivation.

Hello Kishore,,
Please refer below thread for your issue
Batch derivation
Batch Derivation Overview with exampl
SAP Batch Derivation - SAPs'WORD - We SAP For Your Cause
Batch Determination
SAP Batch Determination - SAPs'WORD - We SAP For Your Cause
I hope this document provide you enough knowledge of batch derivation and Determination
I hope this information help to you
Regards
Umesh Mali

What is the difference between on new focus and do prepare out put methods

Hi,
what is the difference between on new focus and do prepare out put methods.

Hi Divya,
DO_PREPARE_OUTPUT method is triggered each time the view is prepared after each event. Normally we redefine this method in order default the initial values based upon the parameter iv_first_time = 'X'. There can be certain other scenarios like putting data validations where this method can be helpful.
For details on ON_NEW_FOCUS, refer to this [thread|on_new_focus event;
Thanks
Vishal

Difference between batch input method and direct input method in LSMW.

Similar Messages

Maybe you are looking for