BDC

[Former Member]

Hi,

In BDC in 'CALL TRANSACTION USING' method The system executes a database commit immediately before and after the CALL TRANSACTION USING statement. What does this mean?

[Former Member]

hi

just refer to the link below

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

<b>step by step procedure with screen shots</b>

regards

ravish

<b>plz dont forget to reward points if helpful</b>

[Former Member]

Executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ) (see also Transaction processing ). This means that

• all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and

• all database locks are released.

COMMIT WORK also

• calls the subroutines specified by PERFORM ... ON COMMIT ,

• executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK ) specified in these subroutines or started just before,

• processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK ,

• cancels all existing locks (see SAP locking concept ) if no update requests exist,

• closes all open database cursors (see OPEN CURSOR ) and

• resets the time slice counter to 0.

Regards,

Santosh

[Former Member]

bdc:

two method

call transcation

session

call transcation: when user upload 10 records.

5 record is error record. remaining record is upload.

in call transcation record bu record insert.

[Former Member]

Notes

All subroutines called with PERFORM ... ON COMMIT are processed in the LUW concluded by the COMMIT WORK command. All V1 update requests specified in CALL FUNCTION ... IN UPDATE TASK are also executed in one LUW . When all V1 update requests have been successfully concluded, the V2 update requests ("update with start delayed") are processed, each in one LUW . Parallel to this, the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK are each executed in one LUW per destination.

COMMIT WORK commands processed within CALL DIALOG processing

- execute a database commit (see above),

- close all open database cursors,

- reset the time slice counter and

- call the function modules specified by CALL FUNCTION IN

BACKGROUND TASK in the CALL DIALOG processing.

However, subroutines and function modules called with PERFORM ... ON COMMIT or CALL FUNCTION ... IN UPDATE TASK in the CALL DIALOG processing are not executed in the calling transaction until a COMMIT WORK occurs.

Since COMMIT WORK closes all open database cursors, any attempt to continue a SELECT loop after a COMMIT WORK results in a runtime error. For the same reason, a FETCH after a COMMIT WORK on the now closed cursors also produces a runtime error. You must therefore ensure that any open cursors are no longer used after the COMMIT WORK .

<b>With batch input and CALL TRANSACTION ... USING , COMMIT WORK successfully concludes the processing. </b>

Refer this link for additional notes...

http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/call_tra.htm

Regards,

Pavan