Question:
Hi,
I Have been getting same problem agian and agian in the master data load
1. I have 20 data pockets(OBPARTNER)
2. Always giving error in the same data pocket
3. whenever it is trying to load new records in the same data pocket, it is giving message like missing messages.
Is there any one can solve this problem.
Lot Thanks
Kevin singapore
Answer:
While the update is in process, the system shows 'Missing messages' as it waits for the process to complete and go to the next step.
Keep refreshing (F once in a while and the messages will change.
This could be that the system is waiting for IDOCs for the source. 'Step-by-step analysis' may give you more clues.
_________________
Keep smiling
Answer:
Thx for your help.
But I have been trying to find out problem, I have checked many times step by step analysis and can't see any clue. That is the reason I am wondering why it is giving like this type of problem.
If any one suggestion great input for me
Thanks
Answer:
I don't know if there is any help for 'Missing messges' since it means that the system is waiting for som kind of message from the process.
Please check system logs in SM21 for the specific time period. Check in SM50 if any processes are still running. I presume you checked job overview in the source system when you went through the step-by-step...
If any process is running, check how long it's run, and kill it (w/o core dump). Change status in the monitor (if it has not changed after you killed the process) as described below and restart the update job.
In case no process is running, and the status does not change, set the QM flag to red from the 'Status' tabstrip, delete any yellow/red flagged request(s) from the cube/ODS and re-start the update job. This time closely watch the process/job, preferably with basis help.
_________________
Keep smiling
Answer:
Thx,
I am not getting you. Are you trying to say if any other jobs were running, we will get like missing messages, am i right, can you correct me.
I have checked just now SM21 I cant see any thing wrong.
Is there any chances short dump error.
One more thing I said out of 20 data pockets one of the data pocket getting new records, only that time I am getting error.If there is no new records I am not getting error
Thanks
Answer:
Hi Belgio,
I am getting same error many times. I cudn't able to see any specific reason. I posted before also same, but I didn't get proper answer, if is there any one can help me out
Thanks
Answer:
"Missing messages' is a wait state, which means the system is waiting for a process to finish, for its success or failure.
If the update is partially done, then you would see yellow flags in the InfoProvider. Delete that request and run it again. If there is any data error, the system would recognize it and the error (or sometimes, warning) message will tell you of what the error is.
With the status 'Missing messages' there is one of 2 things you can do. Wait for the job to time out, or delete, as I said before, and restart the job.
_________________
Keep smiling
Answer:
Thx for your reply.
But this problem is in the process chain. I can not restart the job daily. That is the reason I would like to fix permanemt solution.
Thanks
Answer:
The restart is only a temporary, manual workaround. Probably the chain will work ok from the next day.
You can always kick off a job manually, w/o affecting it's automatic scheduling run, even if the sceduling is done by a 3rd party tool, as is done in cour case (of course with a a little jugglery)
Recently, we had a production down situation, and the R/3 prod. system had to be retored from a previous day's backup. Lucliky it was the easter hoildays and there was negligible transactions in the system, and no delta change pointers were lost. However, some deltas failed with the funny message that it cannot run deltas w/o initialization. I went ahead and scheduled the delta manually, and it worked like a song, and after that the automatic schedule has run (onyl 2 days so, far since the problem) w/o any errors, BEx users didn't miss any data.
I am sorry, I can't help you any more than that. Probably El Belgio/CHC/SBob will step in, now that I have stepped aside.
Good luck!
_________________
Keep smiling
Answer:
Anyway Thx a lot for your help. What you said that is right it works 1 week and another week is giving problem, ok, will see how it will go things. I wait for theire reply.
Thanks
Answer:
One of my friend said, if we delete whole data in the OBPARTNER and do schdule next time, we will not get any error like this, is there any one has idea about this.
Thanks