Yes, user can create background job scheduling in two ways.
1. By calling the executable program RSBDCSUB 2. Transaction Code SM37
While to transfer the data from the through if any errors occurs until the errors are the complete the data is not transfer to the SAP system. the system compulsory shows the errors. that errors are stored into the error logs (Transaction is SM35). so the session method should not return any value. In call transaction method data is directly pass to the SAP system. So its compulsory return the value. Because of the call transaction is the function. A function should return the value mandatory.
Recording Function With recording, user can avoid manual search for fields and tables required in a program including screen numbers. SHDB is the transaction code.
BDC vs Direct Loads( have you used direct loads on SAP tables ) Direct loads is 5 times faster than uploading by normal BDC method. but some times while updating the database referential integrity is violated.
KCD_EXCEL_OLE_TO_INT_CONVERT even takes care of blank cells and is available in older versions of SAP
* Add values to internal table SORT t_cells BY row col. LOOP AT t_cells INTO wa_cells. MOVE : wa_cells-col TO l_index. ASSIGN COMPONENT l_index OF STRUCTURE itab TO <f_value>. MOVE : wa_cells-value TO <f_value>. AT END OF row. APPEND itab CLEAR itab. ENDAT. ENDLOOP.
Session method: The records are not added to the database until the session is processed. sy-subrc is not returned. Error logs are created for error records. Updation in database table is always Synchronous.
Call Transaction method: The records are immediately added to the database table. sy-subrc is returned to 0 if successful. Error logs are not created and hence the errors need to be handled explicitly. Updation in database table is either Synchronous or Asynchronous.
A Great Tutorials Portal
Aquarian Infotech System
Copyright © 2008 interviewmaterial.com. All rights reserved.