Pay_cost_allocation_api.Create_cost_allocation Loads Invalid Data

Last updated on JANUARY 05, 2017

Applies to:

Symptoms

Problem Statement:

Creating Cost Allocations utilizing the PAY_COST_ALLOCATION_API' using segments not in the value sets does not perform any validation and does not raise any errors.

It creates a Cost Allocation for the passed cost code segments, irrespective of the value set contents.



Steps to Reproduce:

The issue can be reproduced at will with the following steps.

1. Create wrapper script to call PAY_COST_ALLOCATION_API.CREATE_COST_ALLOCATION passing known invalid data to any of the p_segment parameters

Example:

PAY_COST_ALLOCATION_API.CREATE_COST_ALLOCATION
(p_validate => FALSE
,p_effective_date => SYSDATE
,p_assignment_id => 371
,p_proportion => 1.0
,p_business_group_id => 626
,p_segment2 => 'ANY RUBBISH'
,p_concat_segments => l_concat_segments
,p_combination_name => l_combination_name
,p_cost_allocation_id => l_cost_allocation_id
,p_effective_start_date => l_effective_start_date
,p_effective_end_date => l_effective_end_date
,p_cost_allocation_keyflex_id => l_cost_allocation_keyflex_id
,p_object_version_number => l_object_version_number

Cause