topic Re: sm35 in Application Development and Automation Discussions

sm35

Former Member — Tue, 17 Apr 2007 06:48:53 GMT

in sm35 what can we do

Re: sm35

Former Member — Tue, 17 Apr 2007 06:50:12 GMT

Hi babu,

1. SM35 is for batch input session.

2. We can create a recording here

We can analyse and process BDC sessions from here.

regards,

amit m.

Re: sm35

Former Member — Tue, 17 Apr 2007 06:55:03 GMT

Hi Babu,

In SM35, we release the session which has been created, and then processed by releasing the specific name, irrespective fo the number of sessions for the particular program. Here we can to release the session.

SM35 is related only for Session method.

We can also check the error log , and also modify the errors and then reprocess the session.

Hope this resolves your query.

Reward all the helpful answers.

Regards

Message was edited by:

Nagaraj

Re: sm35

Former Member — Tue, 17 Apr 2007 06:59:46 GMT

hi,

SM35 is exclusively for Session method only.

In SM35 we can process a Session

we can process it Back ground as well as foreground

we can check errors in error log.(un processed records)

we can release the session which has been created.

Re: sm35

amit_khare — Tue, 17 Apr 2007 07:13:49 GMT

As from SAP -

Batch Input Administrator

Technical name: SAP_BC_BDC_ADMIN

Tasks

The Batch Input administrator transfers data to the SAP System based on the 'batch input' transfer technology. The data transfer process comprises two steps:

The administrator uses a data transfer program to import the external data into the SAP System and store it there as a batch input session.

The administrator runs the batch input session to distribute the data to the relevant database tables of the application.

To do this, the administrator needs authorization to call up the following transactions:

SM35 Batch Input Monitoring

SM35P Batch Input: Log Monitoring

SHDB Transaction Recorder (Record Batch Input)

The tasks of an administrator are as follows:

Running (starting) batch input sessions in the background. This requires the authorization to define and schedule batch jobs (see Basis: Batch Administrator role).

Monitoring data transfer and handling errors

Evaluating batch input logs

Analysing batch input sessions

Running sessions with errors online and correcting the transactions that contain errors. This requires the relevant transaction authorization in each application.

Releasing terminated sessions

Managing data transfer

Locking batch input sessions

Reorganising batch input sessions and logs

Archiving batch input logs

Archiving batch input sessions and logs no longer needed

Creating/testing data transfer programs using the Transaction Recorder

Creating batch input programs

Creating batch input sessions

Creating test data

Regards,

Amit

Reward all helpful replies.

Re: sm35

Former Member — Tue, 17 Apr 2007 07:22:52 GMT

HI babu,

IF ur using bdc session method and exucute the session method it not possible to update the tables.

for this we have go for the t.code sm35 there we can release the session and process the session and if any error is there it will store it in sm35.

rewords somw points.

Rgds,

P.nag