Getting an error with message text 'Program errors'

[Former Member]

Hello All,

We are trying to find out the root cause of ans error we keep getting during a batch job run :

The message class is VHU01 and message number 073 with type E.

The batch jobs are running successfully but this messages keep appearing in the job log.

Any help in resolving would be appreciated.

Regards.

[FredericGirod]

Hi,

do you have some information about the steps of your job?   what did you try to do ? 

(did you check SM13)

regards

Fred

[Former Member]

Hi Fred,

I do not have authorization to run SM13. The job has three steps an the ' program error '

messages are all in the first step.

It is a Z program with user defined variants.

This program does the month end revaluation of stock with the new price,

Finds the new price that should be used for the next period.This new price is based on the valid ZIIP conditions, Vendor Scheduling Agreements (VSA) or Contracts (which ever has the lowest price). The program then update the future price field in the material

master.

Regards,

Ankita

[nabheetscn]

Please check your Z program you must be having some information message or write etc

[FredericGirod]

I try to check the use-case, but it doesn't give something in my system, did you check it ?   maybe the error is used in your Z program.

In the french translatation of the error, it speak about  "database update"

regards

Fred

[Former Member]

Hi Nabheet,

No the message is not getting triggered from the Z Program. I checked.

Regards,

Ankita

[Former Member]

Yes, no hits are there for use-case, as you and Klaus suggested, seems to be some database update error, maybe some lock issues with parallel running batch jobs. Will keep you all updated.

Regards,

Ankita

[nabheetscn]

Hi Ankita

You can simulate the same. Select the processed job checkbox and then in command box do a JDBG. It will simulate what it has done you see if some message is coming. Do an F7 3-4 times to go into your program.

If you run your pogram in forground what do you get?

Nabheet

[FredericGirod]

Ok,

for lock issues, you could add a test with a function ENQUEUE_... just before your update.

I never find another method to check lock entry

regards

Fred

[Former Member]

Hi Nabheet,

Thanks for your response, but the problem is this issue is in production. Debugging the batch job is really frowned upon as table updates are involved.

Its not replicated in Quality, the issue seems to happen randomly so was checking if anybody else came across this error.

Regards,

Ankita

[former_member339717]

Anikita,

Try to run the Standard tcode and enter the same values in the standard programe and watch what is going on if the same message appear before the saving the data then the message has to be catered by the funcitonal  if not then you have to find out wht is going on. But before R&D check at least once the standard transaction.

regards,

[former_member195402]

Hi,

the retranslation from the German VHU01 073 message is like

Program error (Object is still being created and still missing in database).

I hope this will help you anyway.

Regards,

Klaus

[Former Member]

Thanks Klaus,

I am working in 4.6C, the complete error description is not there.

Regards,

Ankita