Mass Allocation runnin no error but a never ending process id is generated (Doc ID 2560036.1)

Last updated on AUGUST 15, 2023

Applies to:

Goal

On : 11.13.19.04.0 version, Performance
We have an accounting flex-field with 11 segments
The need is to create a journal which represent provision of rebates . For that we setup a Mass Allocation which multiply the turnover by a rate entered on a specific account with statistical currency . we've done this setup with looping on several segments on the point of view

1/ the first result is that the Mass Allocation produced no result . After investigation we found that is was due  to the looping we used . Indeed  on a specific segment the turnover was entered with the value B whereas the rate was entered on the value A
The result was : segment A  turn over =0  X  existing rate =0
                       segment B  turn over existing  X no rate =0

2/ To solve that we update the formula of the Mass Allocation. On this specific segment  we keep the looping on the point of view  but on the formula we precise to take into account the rate only with the value A
The result was  : segment A  turn over =0  X  existing rate =0
                        segment B  turn over existing  X rate of the segment  A  = result

The result was correct and allow us to have turn over on as many value as we want on this specific segment


3/ To be sure not to  faced the issue describe on the point 1 on another segment we decide to implement the solution describe on point 2 on all the segment of the accounting flex-field . I mean we continue to put a looping on the Point of view but on the formula turn over X rate we precise a specific value on each segment of the accounting flex-field

The result was a never ending request .


4/ the workaround we implemented was to record the rate in statistical currency  on the value B  for the specific segment i talked on point 1
The result was  : segment A   turn over =0  X  no  rate =0  
                        segment B   existing turn over  X  existing   rate  = correct result

We have been able to implement this workaround because by chance all the turn over is on the value B on this specific segment . When it will no more be the case  our workaround will no more be efficient . That's why we wish to solve the root cause

Why do we success on point 2 and not on point 3 whereas the solution is the same? 

The main key point is on the fact that there's no error but a never ending request.

Solution

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