My Oracle Support Banner

Errors Returned By UPDATE_OPERATION_RESOURCES API Not Recorded Correctly In Log File (Doc ID 2519892.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Process Manufacturing Product Development - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

When an error is returned by the GMD_OPERATION_RESOURCES_PUB.UPDATE_OPERATION_RESOURCES API it is not recorded correctly in the log file. Instead of the message text, only the message name is present in the log, and that too not completely; some special character / value is returned causing it not to log all the messages - though 100s of records error, only 5 - 7 errors are reported in the log, the rest are all missing.

Steps to Reproduce
Run the API wrapper with writing error in log file using FND_FILE as below

  IF x_return_status='S' THEN
  fnd_file.put_line (fnd_file.LOG, 'Success : '||x_message_list);
  -- dbms_output.put_line('Success : '||x_message_list );
  COMMIT;
  ELSE
  --dbms_output.put_line('Error : '||x_message_list );
  fnd_file.put_line (fnd_file.LOG, 'Error : '||x_message_list);
  END IF;

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.