What Is The Use Of Direct Input Method

Explain what is the use of direct input method over call transaction / session method.

Data is transferred from an external system into the SAP R/3 System. You use data transfer when you:

Transfer data from an external system into an R/3 System as it is installed. 

Transfer data regularly from an external system into an R/3 System. 

There are three basic methods for Data Transfer:

Direct Input (DINP)

With direct input, the SAP function modules execute the consistency checks. However with batch input, these consistency checks are executed with help of the screens. This means that direct input has considerable performance advantages. But there are a few programs for direct input, you can use them if it accomplishes your goal. Direct Input programs work like that they update database tables directly. As you know that it is forbidden to update SAP database tables directly, since consistency and security should be considered. Exceptions are these direct input programs. So you are not able to write custom ABAP direct input programs. But of course you can write ABAP programs to update custom database tables (Z tables), if you are sure all about consistency.

So why SAP has created direct input programs? Because SAP wanted to enhance the batch input procedure, since batch input is slower. SAP offers the direct input technique, especially for transferring large amount of data. In contrast to batch input, this technique does not create sessions, but stores, updates, inserts data directly. 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 able to activate the restart mechanism, direct input programs must be executed in the background only. To maintain and start these programs, use program RBMVSHOW or transaction BMV0. 

Examples for direct input programs are:

RFBIBL00 - FI

RMDATIND - MM

RVAFSS00 - SD

RAALTD11 - AM

RKEVEXTO - CO-PA 

CALL TRANSACTION

It seems like batch input method. Data consistency check with help of screen logic. 

Batch Input with batch input sessions.

Data consistency check with help of screen logic. Batch Input is a standard technique for transferring large sets of data into the SAP System. The transaction flow is transferred as if it were entered online. The advantage of this is that all relevant check for the transaction are executed, thereby ensuring that the data is consistent. 
 

How to Schedule Direct Input?

1> Go to SM36, Give a job name.

2> Go to Menu option EDIT -> STEPS. 

3> Give the program name and variant and press the save button on the window.

4> Now you will be in STEP LIST OVERVIEW screen.

5> Goto menu option Step -> Creation, to create another step.

6> Come back to the SM36 screen and define the start condition.

7> Come back to the SM36 screen and save the job.

You can define multiple steps in one job, they execute in a sequence.

In the case for direct input, you have to edit the start condition of the job BMV0.

First create job (Say generate_file ) to execute the customer program which generates the file. 

Go to the job BMV0 in edit mode and change the start condition -> after job. 

Key the job name (generate_file).

Get help for your ABAP problems
Do you have a ABAP Question?

ABAP Books
ABAP Certification, BAPI, Java, Web Programming, Smart Forms, Sapscripts Reference Books

More ABAP Tips

Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.erpgreat.com

All the site contents are Copyright © www.erpgreat.com and the content authors. All rights reserved.
All product names are trademarks of their respective companies.  The site www.erpgreat.com is in no way affiliated with SAP AG. 
Every effort is made to ensure the content integrity.  Information used on this site is at your own risk. 
 The content on this site may not be reproduced or redistributed without the express written permission of 
www.erpgreat.com or the content authors.