BDC's

[Former Member]

Hi friends,

I have a very small question for you. If there are 100 records 50 records are updated suddenly from 51 st record what will you do. Whether they will be uploaded or not . How can we upload the remaining records. Can we upload the remaining records by same session.

How can I know these type of questions and answers. I have not come across this type of questions any where. can any one send me this type of questions and answers . I will definetely revert the points more.

[Former Member]

Hi friends,

I have a very small question for you. If there are 100 records 50 records are updated suddenly from 51 st record what will you do. Whether they will be uploaded or not . How can we upload the remaining records. Can we upload the remaining records by same session.

How can I know these type of questions and answers. I have not come across this type of questions any where. can any one send me this type of questions and answers . I will definetely revert the points more.

[Former Member]

In the above question sudden if there is a power off at the 51 st record .what will you do . how will you update .

[Former Member]

Hi..,

When the session is not processed successfully it will be stored in Incorrect tab of the<b> Transaction SM35</b>... showing how many records are updated successfully and how many records are not processed successfully...

<b>Now u can process the same session for the remaining 50 records from the same transaction.. but u cannot process the successfully processed records again for the second time !!!</b>

These are some commands to give in BDC_OKCODE bar to stop a particular transaction .. and the result of each command is also given below... !!

<b>IT will be very helpful for u...</b>

In the BDC_OKCODE,

give <b>/n</b> to stop that particular transaction...

give <b>/bend</b> to quit the entire Session....

You can interrupt the interactive execution of a session by entering the <b>/bend </b>OK code on any screen. <b>/bend</b> terminates the transaction currently being executed in the session and marks the transaction with the status Incorrect. The session is kept in the queue and is displayed in the Errors section of the list. Changes made by the interrupted transaction are rolled back as long as the transaction uses only the R/3 update facility. Direct database changes made by the transaction are not rolled back.

You can use <b>/bend</b> when testing sessions. For example, you may wish to run the first transactions of a large session in display-all mode to make sure that the session has been generated correctly.

You can restart processing of a transaction by entering the <b>/bbeg </b>OK code on any screen. <b>/bbeg</b> terminates the transaction that is currently being processed and then restarts the transaction fresh, as it is recorded in the batch input session. Any changes made by the transaction are rolled back, as long as they were made only by way of the R/3 update facility. Changes made directly to the database are not rolled back.

You can delete a transaction from a session during interactive execution by entering the <b>/bdel</b> OK code. The transaction is removed from the session. The deleted transaction cannot be run even if you restart the session, and you cannot take back the deletion.

reward points if it helps u..

sai ramesh

[Former Member]

Hi Satish,

Then way of answering is like this:

"Then i will check how many records getting update and then restart the process".

Hope this helps you, reply for queries, Shall post you the updates.

Regards.

Kumar

[Former Member]

Hi

You can chech in SM35 and also u can use the help of log files that is creating after the process.By seeing that u can easily identyfy how many records get updated...If u want to study more use the following links..Reward all helpfull answers...

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sap-img.com/abap/learning-bdc-

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

[Former Member]

Hi ,

From the information provided , it is known that the session is unprocessed. So we can go for the <b>SM35</b> transaction, and remove the session and again reprocess from the beginning, so that successful processing and updation of Data takes place.

Otherwise, if user manually wants to abort the session abnormally, better to go for the <b>/bend</b> in the OK_CODE bar to quit the session abnormally, here also the same procedure as above needs to be followed to remove and reprocess the session.

But be careful to remember that the data once updated in the database cannot be rolled back through any of these processes as said above.

You can also use <b>/bdel</b> to delete a transaction from the session.

Hope this resolves your query.

Reward all the helpful answers.

Regards

[Former Member]

Answered