on 07-22-2016 3:12 PM
Not sure this is the correct thread. We are on ecc6.0 ehp7. We upgraded to this ehp at the end of May and my edi messages have changed.
I now get an error 51 'This delivery (nnnnnnnn) is currently being processed by another user'. It lists the name of the user we process EDI with. What does this mean - my system is too slow? I had about 20 of these this weekend. I had more this morning.
I now also get error 64. When I try using program RBDAPP01 in background to reprocess, I get dumped into another almost blank screen. In st22 it shows I have a runtime error of Message_Type_X to program sapmssy0 and rk2aosi1_post.
Any insight on where I should look to minimize these errors or handle them differently? I appreciate any assistance.
Susan
Hi Susan,
Can you please update what is the OS/DB of your ECC system and what is the IDOC type for which status is getting changed to 51.
Also please check below areas:
. SM21 logs : If there are logs related to IDOC/USER for status 51.
. SM12 lock entries: Any pending lock entries.
. SM13 : Pending update records
Please try to attach ABAP dump also which you are getting when manually processing IDOCs through RBDAPP01.
Thanks,
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Manish,
My system admin is out. I know we have a windows12 environment using SQL. The idoc type is DELVRY03. We are in a batch managed environment, so our data is more detailed than in an non-batch environment. I did not have a 64 error today. I had some error 51 'this delivery is currently being processed' errors this morning. I do not see anything in the trxn's you noted.
The next error 64 I will do screen shots.
Susan
Hi Susan,
Can you please try adding second step in batch job with program RBDMANIN to process these locked idocs.
Referred from below SCN discussions:
https://scn.sap.com/thread/3563198
Thanks,
Manish
Manish,
Sorry to be so slow to respond. It looks like everything that goes into error 64 has inventory problems. We are a batch managed environment with COPA reporting. I just ran one through the RBDAPP01 program and this is the error log. so one of the batches is not being found and cannot do profitability segment. I just wish it went to 51 versus 64 so it is easier to correct.
08/04/2016 14:00:35 Job started 00 516 S
08/04/2016 14:00:35 Step 001 started (program RBDAPP01, variant &0000000000105, user ID SDELANEY) 00 550 S
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Batch 04-4009-28 0070 0004 6195203445 does not exist M7 042 E
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:37 Profitability segment being derived again KI 350 W
08/04/2016 14:00:40 Internal session terminated with a runtime error MESSAGE_TYPE_X (see ST22) 00 671 A
08/04/2016 14:00:40 Job cancelled 00 518 A
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.