Jak zrobić FND Debug

Jak zrobić FND Debug:

(na przykładzie tworzenia Case Folder w OCM i przesyłania do zatwierdzenia do AME).

How To Tell If Case Folder Has Made It To The Approval Management Engine(AME)? [ID 1190983.1]

——–
Run FND Debug and obtain FND Debug Message log which will show what happens when the case folder enters the AME process.

1. Run the following query:

select max(log_sequence) from fnd_log_messages; MAKE A NOTE OF THIS NUMBER

2. Set the following profile options using System Administrator responsibility:

FND: Debug Log Enabled -> Yes <user or site level>
FND: Debug Log Level -> Statement <user or site level>
FND: Debug Log Module -> %
Null out other FND: Debug% profile options.

3. Reproduce the issue

4. Run the following query after you reproduce the issue:

select max(log_sequence) from fnd_log_messages; MAKE A NOTE OF THIS NUMBER

5. Exit the application

6. Get the FND message file. Provide results in Excel Format with column headings. You can use Toad or SQL*Developer to do this easily.

select module, message_text from fnd_log_messages where log_sequence between <value from step 1> and <value from step 4>

7. Disable the FND profile options you set in step 2:

You will notice in the results of the FND Debug Message Log something like this:
ame_engine.fetchItemClassData which indicates the case folder has gone to the AME process. If you keep reading the log you should find the problem.

If you see that the case folder has indeed gone to the AME process and it is not finding an approver, please open a SR with the AME Support Team, product id 1168. Also, please check for any custom attributes you may have created in your AME set up as they could be causing the approvers not to be found.

Ten wpis został opublikowany w kategorii _EBS - ogólnie i oznaczony tagami , , . Dodaj zakładkę do bezpośredniego odnośnika.

Dodaj komentarz