sobiratul
22nd February 2018, 12:27
Hi,

I used exchange scheme to upload the data for tables tfgld213, tfgld214 and tfgld215. Successfully upload to system.

During to Post Imported Journal Transaction (session : tfgld2215m000), I got this error

Transaction Date 15192720 Error: Bad date
146 Error: The Reporting Period field has
an invalid value in Financial Batch.
Error: Period must be Correction
period Transaction Date is not
entered.

bdittmar
22nd February 2018, 15:01
Hello,

the Transaction date is wrong.
In table tfgld213 it's a string of 8 characters, in tfgld214 also.

The date Format has to correspond with your System date Definition.
In german date Format :
15192720
means : 15th day of 19th month in year 2720
In YYYYMMDD :
15192720
means : 20th day in 27th month in 1519

So correct your imported date, please.

If 15192720 is UTC then convert to value shown in attachment.

Regards

sobiratul
23rd February 2018, 08:35
Hi,

I've change the date. But still got the same error.
Attached herewith the sample exchange scheme and template.

Tom de Valk
26th February 2018, 10:57
The 'Post Imported Journal Transactions' session (tfgld2215m000) is looking at the 'Date Format (Transaction Import)' of the transaction type (tfgld011.dfmt).

So, updating this field in the 'Transaction Types' session (tfgld0511m000) will most probably solve your problem.

sobiratul
27th February 2018, 08:23
Hi,

Yes, I'm changed the format date from " Not Applicable" to "DDMMYYYY" in tfgld0511m000 session. Problem solved.

Thanks for the advise and support given.

Pestor
18th July 2023, 16:04
Hi Gurus,

for me it is very similar, only that I get a different error message that I unfortunately do not understand.

exchange scheme to upload data,
tables tfgld213, tfgld214, tfgld215
successfully upload to system.

During Imported Journal Transaction (tfgld2215m000), I got this error


Tools error in session tfgld2215m000: internal error in DAL Engine ('unreachable' failed).

File: ittstpdalutl0 (line 292).

Description:
Transaction is on, cannot continue.

StackTrace:
019: dal.before.retry.point() in ottstpamdll
018: validate.and.convert.document.header.data(i.financial.company=2000,i.import.journal=0) in otfgld2215
017: start.import.process(i.exchange.id.f="L20230401 ",i.exchange.id.t="L20230401 ") in otfgld2215
016: on.choice.cont.process() in otfgld2215
015: g_call_section() in ottstpstandard
014: exec.cont.process() in ottstpstandard
013: frmcmd.executefunction() in ottstpstandard
012: frmcmd.execute() in ottstpstandard
011: frmcmd.handleexecution() in ottstpstandard
010: frmcmd.start() in ottstpstandard
009: cmdhnd.handleformcommand(command=65) in ottstpstandard
008: cmdhnd.handlecommand(command=65) in ottstpstandard
007: tc.handleformcommand(commandnode=2147458390) in ottstpstandard
006: tc.dispatch.message(event=^00000000033B0010(12)((18,3,844684,1000002,0,0,0,0,0,0,0,0))) in ottstpstandard
005: g.execute.bms() in ottstpstandard
004: evthnd.handlebucketmessage(event=^00000000033B8C10(12)((18,3,844684,1000002,0,0,0,0,0,0,0,0))) in ottstpstandard
003: evthnd.handleevents() in ottstpstandard
002: std_main() in ottstpstandard
001: main() in otfgld2215


thanks in advance for your help

with kind regards
Pestor

Pestor
16th August 2023, 12:48
Moin Moin,
i could find the error even if the error message was absolutely not helpful.

The problem was, in the old Baan5 system the country code was two digits and in the Cloud Edition it is three digits (see Countries (tcmcs0510m000)).
The country codes imported through the Exchange Scheme were two digits for the old system but must be three digits for the new system. The country codes to be imported must therefore now be mapped.