Hello all

I am in a situation here where the client is sort of keen to migrate balances using the balance adjustment API as opposed to the balance batch/Initial Balance Upload approach. Personally I favour the latter, but I would appreciate some pros and cons from those who have done both.

The obvious ones I can think of off the top of my head is the potential for doing a partial load (IBU won't load any balances for an assignment where one or more lines are invalid), element entry level balances (API simply won't do it, end of) and the ability to back the balances out easily (doing IBU in 'UNDO' mode) as opposed to a completely new API call (delete_balance_adjustment)

Cons for me would be the insistance by IBU on there being no pre-existing assignment actions.

Any other contributions on this matter gratefully received, and shamelessly plagiarised as all my own work; you know how it works...

Hi Clive,

Think you have covered most of it

You say the client wants to do Bal Adj....why have they gone down that route, they must have some reason

Its a while since I have done one but cannot you see both/either on the Bal Adj form off the assignment ?...if not then that is the only benefit I can see

Could allow them to make manual corrections for those that are wrong

You need to be careful with IBU and BEE if you use that for the elements as it now creates an Assignment action where it did not use to ..so always balances first (usually used to be anyway)

Cheers Gus

I'll be having a meeting with them soon about their thinking on the approach, and the whys and wherefores and do-you-mind-if-we-don'ts of it, but I just wanted to be able to go in and set out some known issues either way which maybe they didn't appreciate.

Any other thoughts, comments?