12-11-2018 8:44 AM
Hello Friends,
Required your help/answer ASAP...
One job is scheduled with the program RBDMIDOC and selected Message type as 'MATMAS'.
Sometimes the job is taking less time even there are many records in BDCP2...sometimes it is taking more time even there are fewer records.
Now the main problem is 'Job is not getting completed'...It is keep on running.. We are not sure about the reason?
Please suggest the solution to faster the job and the reason for not completion.
Awaiting your response!!!
Thanks in Advance...
12-11-2018 9:18 AM
Could you provide more information, did you look for OSS notes - a must do for standard program - did you recently change of version, did you execute SM50/SM51, etc.
12-11-2018 3:51 PM
Thanks for your reply..
Didn't find any suitable notes. Please suggest some notes.
we didn't change any version recently..we are in SAPKA73120 Support pack.
We checked in SM50, Work process in the application servers are also free/Available.
The Sequential Read, Direct Read, Insert, Update, Delete statements are also accessing fine when viewing in SM50. It is not getting stuck at any point when viewing it manually.
There are nearly 7.5 lakh entries in BDCP2 table. Because of this Job is not completing?? It is taking more days to create the IDOC?
12-12-2018 5:41 AM
Hello Divya
In SM50 you should be able to see the instance of this report running. You can choose the line and from menu debug it. In debugging you will come to know the reason for running so long might be running for all entries and all.
Thanks
Nabheet
12-12-2018 6:44 AM
In SM50/51 you may also notice some other tasks running, or some RFC parallel process that may cause exhaustion of system ressources...
12-11-2018 9:23 AM
If it is PRD, kindly take the help of Basis team to get some info on what actually is holding the job.
12-12-2018 12:56 AM
did you look at spool log to check out which IDOC got stuck? also check your printer setting ( cause its calling fm GET_PRINT_PARAMETERS) with MATMAS message, it process a block with size 50000 you can read and debug that program, source code quite short and easy to understand.
12-12-2018 12:38 PM
Thanks for your reply...
Spool is not getting generated..as the job is not getting completed...There are 8 Lakh record in table BDCP2..it is because of that??
12-12-2018 11:59 PM
800k records is not that much, i dont think its the problem. you may have only chose to debug it, analysis through SM50 (chose your process and debug program). maybe you should start analysis with the case there are few records but taking more time.
12-12-2018 8:49 AM
Hi Divya,
here is something you could try to see where the process gets stuck:
There is obviously no guarantee to find anything but it might at least help to narrow down where a problem might exist. For example, if a process gets executed millions of times in just a few seconds you might be looking at an endless-loop situation. I had something like that recently:
Even if you cannot resolve the issue yourself, you'll have some more information to pass on to either your basis-team or to SAP via an OSS-message.
Hope this helps!
Bärbel
12-12-2018 12:36 PM
12-15-2018 7:36 AM
When the following situation occurs
then how much IDOC MATMAS are created ?
When the following situation occurs,
then how much IDOC MATMAS are created ?
There is may be a problem in the distribution model (BD64) for message type MATMAS.
12-15-2018 7:38 AM
Did you use SAT transaction as proposed by Bärbel Winkler ?
If yes, can you share a screen shot of the result like she did ?
12-17-2018 4:16 AM
Chaouki,
Can you share the info on the possible bottlenecks, a distribution model can cause.
Thanks,
K.Kiran.