hi igor,
i presume this is your test env. being in test area, i think you can try
this.
Create a MG.BALANCES.SAVE record by copying the respective MG.BALANCES of
the problematic records DOING THIS the MG.BALANCES can not roll
back to wat it was , before your amendment. but this a
Hi Igor,
i presume the problem is
you are not able to use 'S' function for the 2 problematic MG contracts.
but when you execute the LIST command from jbase level , 2 mg contracts
are listed under exception
.
now you need to REVERSE the Mgs listing..
is this the problem?
and i dont think
Hi,
never use JOURNAL.UPDATE inside a VERSION-level routines. It will
commit the transaction which is expected to be committed later by core
T24.
On Oct 22, 8:45 pm, Igor Micev igormi...@gmail.com wrote:
Hi All,
I try to resolve the following problem:
I made one subroutine which aim was
Hi Sarvanan,
Yes I cannot see ( 'S' ) and input ( 'I' ) them.
We had a problem with two other similar MG records, but weren't able
to detect the reasons why the COB didn't passed (if it was because of
them, still not sure). Because we're on a test environment, since we
made quite volume
Hi All,
I try to resolve the following problem:
I made one subroutine which aim was previously to create records in
one local application. I used UPDATE.JOURNAL() function to authorize
the records. Then I decided to extend its usage, i.e to use it from
version's authorization routine. I made a
