topic Re: Why we r not using direct input method ? in Application Development and Automation Discussions

Why we r not using direct input method ?

Former Member — Sat, 28 Jul 2007 04:21:27 GMT

Hi Guys,

Why we r not using irect input method for uploading data to r/3.

Rewards as per answers

Regards

Kiran.

Re: Why we r not using direct input method ?

Former Member — Sat, 28 Jul 2007 04:27:44 GMT

DIRECT INPUT

About Direct Input

In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. 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.

You can start a Direct Input program in two ways;

Start the program directly

This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.

Starting the program via the DI administration transaction

This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).

Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.

First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:

- Create variant

- Define job

- Start job

- Restart job

Common batch input errors

- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.

- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.

- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.

- The BDCDATA structure contains fields, which are longer than the actual definition.

- Authorization problems.

Regards,

Santosh

Re: Why we r not using direct input method ?

Former Member — Sat, 28 Jul 2007 04:54:43 GMT

Direct input method only applicable to master data like material master,customer master,vendor master,work center and so on.

if suppose material master has some custom enhancement then we should not use direct input method,we need to write new program to upload the data.

In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.

other than this there is no drawbacks.

Thanks

Seshu

Re: Why we r not using direct input method ?

Former Member — Mon, 30 Jul 2007 05:53:50 GMT

d irect input method for uploading data to r/3 at a time single record.

just testing field validtasion.

Re: Why we r not using direct input method ?

Former Member — Mon, 30 Jul 2007 06:14:00 GMT

hi,

by using direct input menthod we can upload data directly into database,

we can't do validations.

Using the Standard Programs the data will upload from the Legacy to SAP.

These standard Program will accept the Data file in a specific structural format.

we don't need transactions,screen flow so there is no change for validation

Re: Why we r not using direct input method ?

Former Member — Mon, 30 Jul 2007 06:16:31 GMT

Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.

Check the BMVO,SXDB Transaction

Regards