OPR Stock update issue

[Former Member]

Hi Experts,

I need some advice or help in an issue with OPR.

We have implemented Customs management for a country which Standard SAP doesn't support.

In the current scenario of OPR Export document, we could see in some cases of OPR Exports, the Release date doesn't get updated in the Header level Transportation tab and in turn the OPR Stock is not built.

We have used all standard logics for this country. We have logic in place to update the Acceptance date in the document as soon as we receive Acceptance message and same case for Release message.

This issue doesn't occur for all cases. Only in some cases of OPR Exports, Release date doesn't update even after processing Release message and in turn OPR Stock is not building up.

I don' t think this could be an issue with the custom code because in some cases we find it working.

We believe, there could be some conditions in the standard code which is clearing the release date.. Have anyone come across this scenario. Could you please help me in identifying those conditions.

Thanks in advance

Dhilipan

[former_member215181 · Accepted solution]

Hi Dhilipan,

I can't think of any reason for that behaviour - there should not be anything casuing OPR stock (which is derived at the Item level) to affect the Release Date in the header.  As an experiment, you could try configuring so that Release is immediate, and then see if you still have problems.

By the way, how are you setting the Release Date from the inbound message =- standard Function Module, or own code?

Regards,

Dave

[Former Member · Accepted solution]

Hi Dave,

Thanks for your response and suggestions. I was able to identify the issue.

Basically, it was a mistake done by us while implementing the Release message processing code logic.

We had a logic verifying if there are any differences with the Cumulative gross weight in the document and the gross weight sent by the customs in release message idoc. I believe this is even available in some standard logic.

If at all, there were any differences we had used /sapsll/cuhd_maintain_object to update the gross weight in the Inbound release idoc to the customs document.So, this is where the issue had happened.

The Release date(DSPTS) and OPR stock posting status(IVMST_OP) was cleared inside this function module. So, in turn the OPR stock wasn't built.

It was not the problem with the function module. But the area where we used this call. When this is being called to update the gross weight. We send the complete cs-obj(which doesn't hold the release date etc.).

So, in turn there is a point in standard code where it removes the release date,etc from GT_CUHD.

And this was happening only in cases, where the Gross weight was different between the Document and the Inbound idoc.

We are in progress of correcting it..

Finally, mystery resolved .  Thanks for your help in this case.

Regards

Dhilipan

[former_member215181 · Accepted solution]

Glad to hear that you resolved the problem.  Don't forget to mark the thread as "answered"

Regards,

Dave