My Oracle Support Banner

Promise To Pay 4th Installment Action Status Is Set To 6 Instead Of 2. (Doc ID 3059980.1)

Last updated on NOVEMBER 26, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version 12.0.0.8.0 and later
Information in this document applies to any platform.

Symptoms

Promise To Pay (p2p) 4th installment action status is set to 6 instead of 2.

Scenario 1:

1. Move the account to collections.
2. Invoke Promise To Pay with 4 milestones.
3. Post payment before each milestones due date.
4. Run pin_collections process after 4th milestone due date.

Expectation: 4th Milestone collection action status should be 2 and account should move out of collection.

Actual: Account is moving out of collection but 4th P2P Milestone collection action status is set to 2.


Scenario 2:

1. Move the account to collections.
2. Invoke Promise To Pay with 4 milestones.
3. Post full payment before 3rd milestones due date.
4. Run pin_collections process after 3rd milestone due date.

Expectation:3rd and 4th Milestone collection action status should be 2 and account should move out of collection.

Actual: Account is moving out of collection and status of both 3rd and 4th are set to 2.


Action status is set correctly in Scenario 2 but in scenario 1 even after making payment before milestone due date, status is set to 2 for 4th milestone action.

Possible Action Statuses :

typedef enum pin_action_status {
  PIN_ACTION_PENDING = 0,
  PIN_ACTION_CANCELED = 1,
  PIN_ACTION_COMPLETED = 2,
  PIN_ACTION_ERROR = 3,
  PIN_ACTION_NO_EXECUTE = 4,
  PIN_ACTION_WAITING_FOR_DEPENDENT = 5,
  PIN_ACTION_BROKEN = 6
} pin_action_status_t;
#endif

#define PIN_COLL_ACTION_STATUSES_COUNT 7

/* collections overall P2P status */
typedef enum pin_coll_overall_p2p_status {
  PIN_COLL_P2P_PENDING = 0,
  PIN_COLL_P2P_CANCELLED = 1,
  PIN_COLL_P2P_COMPLETED = 2,
  PIN_COLL_P2P_KEPT = 3,
  PIN_COLL_P2P_BROKEN = 4
} pin_coll_overall_p2p_status_t;

When Full payment is done after 3rd installment and pin_collections_process is run, ACTION_STATUS should be PIN_COLL_P2P_COMPLETED but it is updating PIN_ACTION_BROKEN in Scenario 1.

Changes

 

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
Changes
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.