cancel
Showing results for 
Search instead for 
Did you mean: 

material document issue

former_member221039
Active Participant
0 Kudos

hi  we are facing typical problem/issue, we are move transport request to prd client and same time, user has done some transaction in prd client, due to which the material document created but stocks tallied, etc,, but because of transport request is related to structural changes, the said material document, whenever we run thru mb52, mb59,etc we are getting dump.  we are facing only with 3 material document numbers on particular day.

Attached dump file for your ready reference.

please let us know is there any solution.  thanks & regards/ srihari

Accepted Solutions (1)

Accepted Solutions (1)

JL23
Active Contributor
0 Kudos

I dont share the opinion of a typical problem, maybe typical in your company, but certainly not in mine. if you do structural changes then you have to make sure that you transport when no movements are posted.

there are not many options you have,  Best is to get in contact with SAP,

I think you did a conversion of old movements into new strucures. And those movements were no converted since they got created while the conversion ran, so the data is still like it was in the past, but not like it is expected in the new structures. So you would need to do an extra convertion for these movements before you can access them with the updated programs.

former_member210560
Active Contributor
0 Kudos

Dear Ediga,

I think you have problem with the Oracle 10g parameter.

Please check and implement the following oracle parameters by refer

to SAP Recommendations Note 830576.

_INDEX_JOIN_ENABLED               FALSE

_OPTIM_PEEK_USER_BINDS           FALSE

_OPTIMIZER_MJC_ENABLED           FALSE

Please check with your Basis colleague to see the recommendation from note.

Regards,

ian Wong Loke Foong

Answers (1)

Answers (1)

Former Member
0 Kudos

whats exact issue? is it related to data or MB52 dump?

If its related to data do you see any discrepancies in data? if it's related to MB52 dump, MB52 might go to dump for various reasons.. inappropriate data, wide range of input.. also check this oss notes which helps to improve the performance of MB52.. which version of SAP you use?

Note 531604 - MB52: Performance improvement