cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC FIDCCP02 Issue

Former Member
0 Kudos

I'm currently using idoc FIDCCP02 to create parked documents via FBV1. However, when I use FBV0 to attempt to post any of the created parked documents I get 1 of 2 errors.

When trying to post a payables document it says "Field RF05A-XIMKO. does not exist in the screen SAPMF05A 0302"

When trying to post a receivables document it says "Field BSEG-MADAT. does not exist in the screen SAPMF05A 0301"

The idoc isn't utilizing either of those two fields, nor do I want it to. I've already made sure that none of the posting keys I'm using require either of the fields in transaction OB41. Any suggestions would be greatly appreciated.

Thanks,

Nate

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

This thread is quite old, but as I just found the answer and will probably forget it in a year or two and don't want to start debugging again, here my findings.

I just had the same problem. Some error mentioning RF05A-XIMKO in dynpro 0302 when trying to post a parked document. After investigating through half of the function modules involved in posting, i discovered that the FM responsible for processing the idoc isn't very fond of empty DATS fields. For instance, if you leave field E1FISEG-DABRZ empty instead of filling it with '00000000', you will get the error mentioning RF05A-XIMKO in dynpro 302.

If you want to investigate this a little further: FORM fuellen-imkey in include LF040Z01 inserts 'BSEG-DABRZ' into internal table FIELD_INP, which much later leads to adding RF05A-XIMKO to the batch input table in function module POSTING_INTERFACE_DOCUMENT. There is a test for VBSEG-DABRZ IS INITIAL in FORM fuellen-imkey, but the initial value for date fields is '00000000' and the field at that point is empty, therefore not initial.

So the workaround is: initialize all date fields in the idoc with either a real date or the string representation of an initial DATS field, '00000000'.

0 Kudos

This thread is old indeed, but your answer saved me tons of time, thanks a lot. I've been parking FIDCCP02 IDocs through BizTalk and this error was appearing (in screen 0303), when I was posting parked documents through fbv0. It was not that obvious, because IDoc schema does not contain XIMKO element.

For any BizTalk developer, who has the same trouble - as Dirk said, you need to fill with '00000000' value the following fields for every E2FISEG006GRP element in your IDoc:

E2FISEG006/BZDAT

E2FISEG006/DABRZ

E2FINBU006/VRSDT

E2FINBU006/MADAT

Once again, thanks for your valuable comment.

sridevi_p
Active Contributor
0 Kudos

For MADAT issue -

Check the structure - E1FINBU.  Hope none of the dunning fields(MSCHL, MANSP,MABER, MADAT,MANST) are filled in. 

Also try parking the document directly in FBV1 and check for exact messages.

Regards,

Sridevi

Former Member
0 Kudos

I've already done both of those things. No dunning fields are mapped. If I manually
enter all of the same data into FVB1, it parks and posts with no problem.

Thanks,

Nate