Question:
status 39 to 41 are status of idoc in receiving system. they are set by aleaud idocs. to change the status you have to process the idoc in receceiving system and send another aleaud back to the sendung system. but it's better to monitor idoc in receiving system anyway there i woudn't pay much attention to status 39 ++
_________________
joko
Answer:
Joko,
We are also show a fair number of status 51 records, which I believe are as a result of some kind of locking as a result of processing status 64 records via RBDAPP01. The trouble is I can't identify what's causing this lock or what table is actually being locked.
Any idea ?
_________________
"In the middle of difficulty lies opportunity" - Albert Einstein
"Money isn't everything in life, unless you don't have it". David King
"Fail to plan, plan to fail"
"Success is a journey, not a destination."
Answer:
Lock identified. Our Z program that creates the IDOC's seems to be the culprit. We need to revisit the locking methods used by this code.
_________________
"In the middle of difficulty lies opportunity" - Albert Einstein
"Money isn't everything in life, unless you don't have it". David King
"Fail to plan, plan to fail"
"Success is a journey, not a destination."