D3-FPCOMM Attempts To Create A To Do Without A To Do Type (Doc ID 2946412.1)

Last updated on MAY 02, 2023

Applies to:

Symptoms

D3-FPCOMM attempts to create a To Do without a To Do Type

A customer using the L+G Adapter found an error in ToDo creation during an error case. When sending a Demand Reset, if the initial communication is successful, but discarded prior to the arrival of the asynchronous reply, the Inbound Communication will attempt to log a ToDo item. However, due to a script error, the transaction rolls back and leaves the Inbound Communication in the pending state

Step-
The issue can be reproduced at will with the following steps:
1.Create a Demand Reset Command FA with a Child Schedule Demand Reset Outbound Communication.
2. Discard the Outbound Communication prior to completing the inbound communication:
3. Create a Schedule Demand Response Inbound Communication where the parent outbound communication has been discarded.
4. Attempt to validate the Inbound Communication:
a. This inbound communication will stay stuck in PENDING with the following error in the log:
Transition from status Pending to status Validate failed by Enter plug in (D3-FPCOMM) - 20

Changes

Cause

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