06-16-2009 2:24 PM
Hello Forums,
I am using BAPI_ACC_GL_POSTING_POST and I am getting the error:
"FI/CO interface: Inconsistent FI/CO document header data for updating"
Anyone had to deal with this error before?
Thanks
06-16-2009 2:28 PM
Hi keith
you must be passing the structure of type BAPIACHE08 as an import parameter for the BAPI [export parameter from program].
check what data u are passing. i guess the problem lies just there
06-16-2009 2:32 PM
hi,
Might be your are not passing mandatory fields in the structure( BAPIACHE08).
for example transaction Fb60 or Fb70 in the header at least you have to fill the posting date ,document date,currency key ,posting key,company code.These are the mandatory fields to fill the header,So you need to fill BAPIACHE08 structure with mandatory fields.
thanks & regards,
rakesh
06-16-2009 2:40 PM
Thanks Gents,
here is what I am passing:
DATA: gv_doc_header LIKE bapiache08,
SELECT SINGLE WAERS FROM BKPF
INTO gv_comp_curr
where BUKRS = gv_bukrs.
gv_doc_header-doc_date = gv_Posting_Date.
gv_doc_header-comp_code = gv_bukrs.
gv_doc_header-username = sy-uname.
gv_doc_header-doc_type = DocType. "'YP'.
CONCATENATE '2009' '/' pcard_post_rec-ZLGPSPD
INTO ls_ref.
gv_doc_header-REF_DOC_NO = ls_ref.
CONCATENATE 'PCARD ' gv_hdrtxt gv_Posting_Date
INTO gv_doc_header-header_txt
SEPARATED BY space.
if cb_test = 'X'.
gv_doc_header-pstng_date = sy-datum.
else.
gv_doc_header-pstng_date = gv_Posting_date.
endif.
Edited by: keith warnock on Jun 16, 2009 3:40 PM
06-16-2009 3:01 PM
06-16-2009 3:02 PM
keith,
thanks for posting the code...
we are checking it...
can u please keep a break point on the BAPI call and see the values in that gv_doc_header, whether all values are coming accordingly to the struc.
06-16-2009 3:10 PM
06-16-2009 3:14 PM
On the return of my BAPI Call the Document header is like this:
BKPFF$ ECDCLNT200WARNOCKE PCARD actual 20090427 1000 20092009042720090616000000
06-16-2009 3:16 PM
hi...
BEFORE the BAPI CALL, out a break point and match the corresponding fields of that structure to the value u have passed.
are they looking correct?
06-16-2009 3:23 PM
Hello,
Yes, the values for the header b\4 the BAPI call are not changed and look correct to me: here they are:
SELECT SINGLE WAERS FROM BKPF
INTO gv_comp_curr
where BUKRS = gv_bukrs.
gv_doc_header-doc_date = 20090427
gv_doc_header-comp_code = 1000
gv_doc_header-username = warnocke
gv_doc_header-doc_type = YP.
gv_doc_header-REF_DOC_NO = 2009/ 4.
gv_doc_header-header_txt = PCARD actual 20090427
gv_doc_header-pstng_date = sy-datum.
gv_doc_header-FISC_YEAR = '2009'.
gv_doc_header-FIS_PERIOD = '004'.
06-16-2009 3:25 PM
I am also getting this error:
Error in document: BKPFF $ ECDCLNT200
06-16-2009 3:28 PM
06-16-2009 3:29 PM
06-16-2009 3:36 PM
You have an error message in the return table:
"FI/CO interface: Inconsistent FI/CO document header data for updating"
Along with that, there should be a message ID and a number in the return table. There may be a long text that gives more information. Can you provide that ID and number?
Rob
06-16-2009 3:44 PM
Hi Rob,
Here are the details from the BAPI gt_return
Line = 1
Id = RW
Number = 609
Message = Error in document: BKPFF $ ECDCLNT200
Line = 2
ID = RW
number = 015
message = FI/CO interface: Inconsistent FI/CO document header data for updating
06-16-2009 3:47 PM
06-16-2009 3:55 PM
Soumya,
i am not sure what you are referring to with the note numbers?
06-16-2009 3:55 PM
Well, the message says that the description is "self explanatory", so I guess you need to look at the data. Are you sure fiscal period 4 is open in your system for 2009?
Rob
06-16-2009 4:08 PM
Hi Rob,
I have tried many different periods and still the same result.
06-16-2009 4:13 PM
06-16-2009 4:49 PM
Gents,
I have made some progress, the issue was with the comp_code and the accounts were under different compaines...
I have fixed that and am having issues with this now:
Document type De not defined = I have put 'Debit' Here... I orignally had 'D' What should it be?
06-16-2009 4:54 PM
This appears to be a separate problem. Since this thread is quite long, I think you should close it and start a new thread with the new question.
Rob
06-17-2016 1:52 PM