07-03-2010 6:21 AM
I'm using BAPI_CATIMESHEETMGR_INSERT (for the first time) and it is successfully inserting new CATS records - with the exception of the short text field (ltxa1). I've run the program in debug mode and the SHORTTEXT field within my internal table for the import BAPICATS1 table (named tbl_catsdata_in) has the SHORTTEXT value populated, but after the BAPI call, the field is not updated in the corresponding BAPICATS2 export table (named tbl_catsdata_out in my program).
Is there something special I need to know about getting values to store in the CATSDB LTXA1 field? All other fields are storing just fine. I am explicitly moving a value to the field. I'm baffled.
Here are excerpts from the program:
tbl_inserts-abs_att_type = tbl_zlct_to-awart.
tbl_inserts-bonustype = tbl_zlct_to-prakn.
tbl_inserts-employeenumber = tbl_zlct_from-empl.
tbl_inserts-rec_cctr = tbl_zlct_to-rkostl.
tbl_inserts-rec_order = tbl_zlct_to-raufnr.
Storing the LCT-ID in the new records short text field.
tbl_inserts-shorttext = tbl_zlct_to-lct_id.
.
.
.
loop at tbl_inserts where lct_id = v_hold_lct_id.
move-corresponding tbl_inserts to tbl_catsdata_in.
append tbl_catsdata_in.
endloop.
.
.
.
loop at tbl_cust_fields where lct_id = v_hold_lct_id.
tbl_extensionin-structure = 'BAPI_TE_CATSDB'.
bapi_te_catsdb-row = tbl_cust_fields-recno.
bapi_te_catsdb-zoan = tbl_cust_fields-zoan.
bapi_te_catsdb-zzminclss = tbl_cust_fields-zzminclss.
bapi_te_catsdb-zzcostcntr = tbl_cust_fields-zzcostcntr.
bapi_te_catsdb-ztaskid = tbl_cust_fields-ztaskid.
tbl_extensionin+30 = bapi_te_catsdb.
append tbl_extensionin.
endloop.
call function 'BAPI_CATIMESHEETMGR_INSERT'
exporting
profile = 'AUTOAPP2' "Profile
testrun = v_no_upd "Test
release_data = p_releas "Release Data
AGENT =
TEXT_FORMAT_IMP = 'ITF'
tables
catsrecords_in = tbl_catsdata_in
extensionin = tbl_extensionin
catsrecords_out = tbl_catsdata_out
extensionout = tbl_extensionout
WORKFLOW_TEXT =
return = tbl_return
LONGTEXT =
Thanks in advance for your help.
09-09-2010 5:11 PM
Marking this question as answered. We found another alternative..did not use the SHORTETEXT field.