Skip to Content
0

Problem with EDATEXMON01

Mar 18, 2017 at 06:12 PM

99

avatar image
Former Member

Hello,

I used the sap IS-U and consulted t-code BD87 and had 2 idocs in error as was supposed. But when I access the transaction EDATEXMON01 the same 2 idocs have created about 2000 records each and continues to generate more.

Has anyone had this problem that can help me?

Thank you.

10 |10000 characters needed characters left characters exceeded

Check the IDOC status history, if it is being processed there should be logs to review.

0
Former Member
Daniel McCollum
The IDOC status will toggle between status 51 and 55 consecutively.
0

try setting the status to 68 in RC1_IDOC_SET_STATUS

Thats a work around for the processing loop.

sounds like you have some custom workflow or program active.

0
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Harald Lesche-Holzbecher
Mar 23, 2017 at 06:26 PM
0

Well, each processing of the IDOC will create entries within EDATEXMON01. In case it's some kind of "aggregated" idoc a single processing might already create a whole bunch of entries in EDATEXMON01. So you should check whether you can solve the issue which causes the IDOCs to run into error.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Apr 20, 2017 at 11:01 AM
0

I've been parsing better and the error was supposed to have occurred because the linetype does not exist, but the idoc is toggling between states 51 and 55. What can cause an idoc to skip between state 51 and 55? And why is the idoc in the EDIDC table in state 51 and in the EDIQI table in status 75?

Share
10 |10000 characters needed characters left characters exceeded