tf3.1_b, tf3.1_b1, tf3.1_b2

tfB40_a, tfB40_a1, tfB40_a2

tfB40L_a_glo0, tfB40L_a1_glo0, tfB40L_a2_glo0

tfB40L_a_gls0, tfB40L_a1_gls0, tfB40L_a2_gls0

tfB40L_a_sch0, tfB40L_a1_sch0, tfB40L_a2_sch0

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

tfB40L_b_glo0, tfB40L_b1_glo0, tfB40L_b2_glo0, tfB40L_b3_glo0

tfB40L_b_gls0, tfB40L_b1_gls0, tfB40L_b2_gls0, tfB40L_b3_gls0

tfB40L_b_sch0, tfB40L_b1_sch0, tfB40L_b2_sch0, tfB40L_b3_sch0

SITUATION IDENTIFIED IN: Direct Network Communication (tcedi7205m000)

SITUATION DESCRIPTION:

Getting fatal error index 501 out of dims.

SOLUTION DESCRIPTION:

Expanded the dimension limit.

This solution solves defect 395.

tf3.1_b, tf3.1L_b_glo, tfB40_b, tfB40L_b_mcr, tfB40L_b_glo, tfB40L_b_gls, tfB40_c1

SITUATION IDENTIFIED IN: Print Trial Balance - With Dimensions (tfgld3405m000)

SITUATION DESCRIPTION:

Printing trial balance with budget variances (ledger account/ dimension) results in all children and parent accounts being

totaled on report even though range for "sub-level" was set to " 0 to 0".

SOLUTION DESCRIPTION:

The total line was summing up amounts even when the sub-level of the ledger account was more than zero. This is incorrect

as bottom-up budgets get automatically accumulated in zero level accounts while in top-down budgets it does not make a

difference as no accumulations are done. Thus budget totals are now only for zero sub-level accounts. Also, the sub-level

for the accounts was added to the report layout. The input form accepted sub-level range as 2 digits when it was meant for

dimensions. This has been changed to 1 digit to avoid confusion between ledger sub-level and dimension sub-level.

This solution solves defect 314.

tf3.1_b, tf3.1_b1, tf3.1_b2, tf3.1_b4, tf3.1_b5, tf3.1_b6

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

SITUATION IDENTIFIED IN: Select Financial Statement Values (tffst1205m000)

SITUATION DESCRIPTION:

Masking on dimensions will not work in session tffst1205m000 when the performance ID 10241823 is applied.

SOLUTION DESCRIPTION:

Values were not calculated correctly if dimension masks were specified, due to the fact that the dimension mask can be

specified at the dimension level. This has been fixed, and the session should now run correctly.

This solution solves defect 413.

tf3.1_b, tf3.1_b1, tf3.1_b2

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

tfB40L_b_mcr0, tfB40L_b1_mcr0, tfB40L_b2_mcr0, tfB40_b3_mcr0

tfB40_c1

SITUATION IDENTIFIED IN: Print Aging Analysis by Supplier (tfacp2420m000)

SITUATION DESCRIPTION:

The below problem was orginally logged under defect 88. This fix works correctly in acr however acp does not work. Now

with this fix the acp aging shows all transactions even invoices that have been paid and reconciled. This has been

duplicated on our system.

I have an invoice that has been paid with a check but it has not been reconciled yet therefore it is still at the anticipated

status. When I print the aging to include anticipated payments (in calculations) as yes - it still prints on the aging.

This problem is duplicated on our system in Tigger for supplier 1001 see invoice ACP 96000080 which has been paid with

ANP 97000008. Both of these documents show up on the aging when the aging is printed to include anticipated payments.

SOLUTION DESCRIPTION:

The changes done by defect ID 88 have been reversed.

When include anticipated payments is set to 'Y' any anticipated payments expected for the invoice should be considered as

normal payments. Hence only if there is an outstanding balance against the invoice, after considering anticipated payments,

should the invoice be printed. If the flag is set to 'N' by the user, then anticipated payments for that invoice are not to be

considered as payments, and therefore, the invoice should get printed.

This solution solves defect 367-1

tfB40_b4

tfB40L_b4_glo0, tfB40L_b4_gls0, tfB40L_b4_sch0, tfB40L_b4_mcr0

tdB40_b4

tfB40_c1

tdB40_c1

SITUATION IDENTIFIED IN: Integration Transactions to Financial Transactions (tfgld4200m000)

SITUATION DESCRIPTION:

In Maintain inventory and WIP (tdinv850) a specific setup is defined for an item for purchase receipt and purchase result.The

item is a purchased item. A generic setup is also defined for the purchase receipt and purchase result. When this specific item

is purchased, the system uses the generic setup instead of the specific setup for the item

SOLUTION DESCRIPTION:

The function itdinv001 has been changed and now it allows a specific setup (if it exists) to be used for purchase receipt and

purchase result instead of a generic setup. This solution solves defect Defect Number 94-1.

B40_b2

SITUATION IDENTIFIED IN: Display Sales Invoice (tfacr2521m000)

SITUATION DESCRIPTION:

The field "balance amount incl. all child customers" on form 2 was not producing the correct result. This was

because it was taking its amounts from table tccom010 instead of from table tccom011.

SOLUTION DESCRIPTION:

The program was changed so that the invoice amounts for both the customer and its children were read from

table tccom011 instead of table tccom010. This change was made in the field section of total.buin and in the

function read.buin.children. This solution solves defect 476

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

tfB40L_b_glo0, tfB40L_b1_glo0, tfB40L_b2_glo0, tfB40L_b3_glo0

tfB40L_b_gls0, tfB40L_b1_gls0, tfB40L_b2_gls0, tfB40L_b3_gls0

tfB40L_b_sch0, tfB40L_b1_sch0, tfB40L_b2_sch0, tfB40L_b3_sch0

tfB40_c

SITUATION IDENTIFIED IN: Maintain Posting Data of Standing Orders/Standalone Payments (tfcmg1113m000)

SITUATION DESCRIPTION:

When a payment for standing order is made the posting data created did not have balanced entries. The debit entry was

missing.

SOLUTION DESCRIPTION:

In the solution for defect 195, the company number field was properly populated in the table tfcmg102 (Posting data for

Payments without Invoice). This led to a problem because many other programs including the one which this problem is

related to read the table tfcmg102 expecting the company number to be zero. Hence the posting data was not found at

payment time and unbalanced entries were created. Now the changes made by defect 195 have been partially reversed and all

data created for standing orders in table tfcmg102 is with company number field set to zero.

This solution solves defect 394.

SITUATION IDENTIFIED IN: Print Statements of Account (tfacr3440m000)

SITUATION DESCRIPTION:

The problem was that the header would not align correctly when you printed the statement account. In customer

statements (accounts receivable), Maintain Statement of Account Letters, a header was entered that looked like it

was aligned. However, in Print Statements of Account, the header would not be aligned when it printed.

SOLUTION DESCRIPTION:

The problem cannot be totally eliminated. This is because the alignment is in the hands of the user and it also depends on the

size of the field defined in the header and footer. The comment attached to this defect gives the sizes of all possible fields.

Hence if layout of the fields is done using these sizes the result will be aligned. This solution solves defect 329.

tf3.1_a, tf3.1_a1,

tf3.1_b, tf3.1_b1, tf3.1_b2,

tfB40_a, tfB40_a1, tfB40_a2,

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3.

SITUATION IDENTIFIED IN:

Remove Fully Paid Sales Invoices (tfacr2260m000).

SITUATION DESCRIPTION:

Error on reading text with number 0 in language 1.

SOLUTION DESCRIPTION:

There had been a problem (logged on Olympus with ID 10242347) in which customers received error 606 when archiving. This

problem was fixed, but not entirely it seems. Because of this, some customers received the error "Error on reading text with

number 0 in language 1." The original problem has now been solved in its entirety. The customer should no longer get this

error.

This solution solves defect 11586.

tfB40_b4

tfB40L_b4_glo0

tfB40L_b4_gls0

tfB40L_b4_mcr0

tfB40_c1

SITUATION IDENTIFIED IN: Maintain Matched Purchase Invoice Transactions (tfacp1133s000)

SITUATION DESCRIPTION:

During approval invoices in acp1133 a default reference comes up which is name of supplier. When you tab through this field

for a second time the reference disappears. Also when you 'save' the reference disappears.

SOLUTION DESCRIPTION:

The form and the program script were changed for this defect. The form was changed so that the default for

the field 'tfacp101.refr' was tfacp200.refr instead of tccom020.nama. The script was changed in the field

'tfacp101.refr' so that the user can maually enter a reference without it disappearing. This solution solves

defect 12063-1.

tf3.1_b, tf3.1_b1, tf3.1_b2

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

tfB40L_b_glo0, tfB40L_b1_glo0, tfB40L_b2_glo0, tfB40L_b3_glo0

tfB40L_b_gls0, tfB40L_b1_gls0, tfB40L_b2_gls0, tfB40L_b3_gls0

SITUATION IDENTIFIED IN:

Background Process for Real-time Document Level Update (tfgld1201s000)

Background Process for End of Session Update (tfgld1203s000)

Termination Mode Updations (Background) (tfgld1213s000)

Print Non-finalized Transactions (tfgld1401m000)

SITUATION DESCRIPTION:

When a transaction of type opening balance is entered and there are rounding differences, these get posted to the p&l

account (defined in the company parameters) in the history tables of opening balance. This shows up as an error when

running the session Automatic Balancing of Profit and Loss Accounts (tfgld6202m000), because a p&l accounts

cannot/should not have an opening balance.

SOLUTION DESCRIPTION:

In case a rounding difference is generated during the entry of a transaction of type opening balance it will now be

automatically added to the transaction itself using the account code of the last transaction line and not to the rounding

difference account defined in the company parameters. This solution solves defect 477

SITUATION IDENTIFIED IN: Restart Finalization Run (otfcor0203)

SITUATION DESCRIPTION:

In some situation, after Finalization run is broken, it is not possible to restart Finalization run.

SOLUTION DESCRIPTION:

It is now possible to restart the Finalization run in case the Finalization run is broken

3.1_b, B40_b.

SESSION ERROR IDENTIFIED IN:

Select Financial Statement Values - tffst1205m000.

SITUATION DESCRIPTION:

The incorrect calculation of data.

SOLUTION DESCRIPTION:

The incorrect calculation of data was due to performance enhancements (i.e. improvements to the ofst1205 object). The

problem has been corrected with ID398-1. Several ID's from 3.1a have been built forward to the 3.1b... & B40_b... versions.

VERSION(S):

tf3.1_a, tf3.1_a1

tf3.1_b, tf3.1_b1, tf3.1_b2

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

SITUATION IDENTIFIED IN: Creating Recurring Transactions (tfgld1202m000)

SITUATION DESCRIPTION:

For ID 10230450 a new field 'Tax Year' has been added to the table with recurring/reversing instructions (tfgld103). However

this new field is not used in tfgld1202m000, so that transactions are still created with the fiscal year and not with the tax

year.

Another problem in tfgld1202m000 is the check if the reporting year/period is open: this check is done with the fiscal year

instead of the tax year, with the fiscal period instead of the tax period, but also a flag is sent to the include itfgld0007 to read

the fiscal periods instead of the tax periods.

Last problem is that the new field has been added to tfgld103, so a customer who upgrades from Baan IVb to Baan IVc has

all records in tfgld103 with tfgld103.tyer = 0 . How can you avoid wrong transactions being created with tax year 0 ????

tf3.1a2

tf3.1b7

tfB40_b4

tfB40_c1

SITUATION IDENTIFIED IN:

Close Year (tfgld6203m000)

SITUATION DESCRIPTION:

When you execute the session tfgld6203m000 the system will generate opening balances for the next year. Before generating

these opening balances the system will check if (only) the accounts have closing balances. It¦s a problem because you can

have accounts with zeros in the closing balances, and in other hand, you can have closing balances for the combination

Ledger Account/Dimension, and the system doesn¦t check it.

SOLUTION DESCRIPTION:

The zero balance check for ledger accounts is removed, hence even if the ledger account balance is zero, transactions will

be created now. The same change is done for tfgld6202m00 (Automatic Balancing of Profit and Loss Accounts). Transactions

will now be created if a non-zero ledger/dimension combination is found. This solution solves defect 690.

tf3.1_a, tf3.1_a1

tf3.1_b, tf3.1_b1, tf3.1_b2

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

SITUATION IDENTIFIED IN: Assign Credit Note to Invoices (tfacr2121s000)

SITUATION DESCRIPTION:

If you create an invoice for a CAD customer in CAD currency then create a credit for the same customer in USD currency, the

balance in tfacr2522s000 Display Sales Invoices changes after you link the two together. The ending balance is not even

correct. This was originally addressed with solution #849 and ID 10242895. The solution appeared to fix the problem but

it is happening again.

SOLUTION DESCRIPTION:

These are corrections to earlier fixes 10240386 and 10242895. These fixes updated the customer balances when a credit note

is linked to a customer invoice. Actually customer balances are not to be updated here unless there is a currency difference

between invoice and credit note exchange rate. When a customer invoice is entered the customer balance increases to show

the new balance. When a credit note is entered the customer balance decreases according to the amount of the credit note. If

the invoice and credit note having different exchange rates are linked, and a currency difference is noted between the

invoice and credit note then only this difference figure is now added to the customer balances. The same changes were done

to reflect supplier balances in Accounts Payable.

This solution solves defect 350.

tf3.1_b, tf3.1_b1, tf3.1_b2,

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3.

SITUATION IDENTIFIED IN:

Maintain Integration Relations by Ranges (tfgld4122s000).

SITUATION DESCRIPTION:

Connecting integration option "series" with relations is not possible, because the zoom session does not work in session

"Maintain integration relations by range" (tfgld4122s000) or in session "Maintain integration relations by element"

(tfgld4123s000).

SOLUTION DESCRIPTION:

When connecting an integration option with option "series", the zoom will now work in both tfgld4122s000 and

tfgld4123s000.

This solution solves defect 12656.

tf3.1_b, tf3.1_b1, tf3.1_b2

tf3.1L_b_glo0, tf3.1L_b1_glo0, tf3.1L_b2_glo0

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

tfB40L_b_glo0, tfB40L_b1_glo0, tfB40L_b2_glo0, tfB40L_b3_glo0

tfB40L_b_gls0, tfB40L_b1_gls0, tfB40L_b2_gls0, tfB40L_b3_gls0

SITUATION IDENTIFIED IN: Register Purchase Invoices (tfacp1110s000)

SITUATION DESCRIPTION:

The annual turnover is not updated in the table tccom021/011 even if invoices are registered (the invoice balance is

appearing normally in the supplier/customer open-entries).

SOLUTION DESCRIPTION:

After some discussion with development, it was decided that turnover should NOT be updated in finance, but rather, all

updates to turnover should take place in distribution. Therefore, the functionality to update turnover in finance has been

removed.

This solution solves defect 11407.

tf3.1_b, tf3.1_b1, tf3.1_b2

tfB40_b, tfB40_b1, tfB40_b2, tfB40_b3

SITUATION IDENTIFIED IN: Maintain Dimensions (tfgld0110m000)

SITUATION DESCRIPTION:

I chose an existing dimension code(001) under dtyp 2 and created an identical dimension code(001) under dtyp 3. The

dimension code(001) under dtyp 2 has had transactions processed and history exists. The dimension code (001) under dtyp 3

has no history, but I still receive the dimension in use. Cannot delete error (tfgld9078). I ran this in debug with Ajith and

he determined that the check in the code for tfgld206 has a bug. It does not recognize the dtyp associated with the

dimension code when checking history. Therefore it will not let me delete the code under dtyp 3 because history exists for

the same code under dtyp 2.

SOLUTION DESCRIPTION:

Users will now be able to delete a dimension code that exists in two dimension types, as long as it does not have any

transactions in the dimension type that the user is trying to delete it from.

This solution solves defect 797.

SESSION ERROR IDENTIFIED IN: tfacr2415m000 'Print Control Account Checklist'

PROBLEM TEXT:

Control Account Checklist - When a Debtor Invoice is paid - The original Invoice transaction and the Receipt Transaction

are both posted in the Finalised and Closing Balance Columns and not in the Open Item Balance giving an equal plus and

minus balance. These transactions should not appear on the list.

SOLUTION DESCRIPTION:

The link between two documents for advance/unallocated receipts was not established, because in tfgld102 (and tfgld106),

namely .ctyp and .cdoc, were not filled with the right values. The latter tables are used in session tfacr2416m000; now the

document as in the the example above does not appear anymore in the list.

B40_b, B40_c

SESSION ERROR INDENTIFIED IN: tfgld1406m000 / tfgld1407m000

PROBLEM TEXT:

There is no print session (finalized transactions) which includes a selection on reporting period. It would be a lot easier for

a customer to have a standard report in which he could see the result for a reporting period, than to make a report everytime

he needs reporting information on a selected ledger account.

SOLUTION DESCRIPTION:

Session, Form and program scripts have been adapted for tfgld1406m000 and tfgld1407m000, in order to be able

to print the reports based on as well a fiscal as a reporting period

VERSIONS: tfB40_b4, tf B40L_b4_mcr0, tfB40_c

SITUATION IDENTIFIED IN: Display Ledger History ( tfgld3501m000)

Display Dimension History (tfgld3520m000)

SITUATION DESCRIPTION:

The default value for the field "Display final transactions" in the session "Change default value (tfgld3503s000)" is 'no',

instead of 'yes' because normally a customer is always interested in seeing his final transactions.

SOLUTION DESCRIPTION:

The default value for the field "Display final transactions" has now been set to 'Yes' from the existing 'No'. Programming

Error has been corrected by DF 11431-1

SITUATION IDENTIFIED IN: Maintain Payment Advices ( tfcmg1120m000 )

SITUATION DESCRIPTION:

In tfcmg1120m000 when the payment method of a supplier (having an alternate payment method) is changed then at the time

of selecting

the invoices for payment (tfcmg1220m000), within the SAME BATCH, the payment method of the supplier is changed back

to the

original payment method (can be seen in tfcmg1120m000).

SOLUTION DESCRIPTION:

A message is flashed to the user when he tries to change the payment method (from alternate to the parent having maximum

amount less than

the invoice amount) in the Maintain Payment Advice session.

VERSIONS: tp3.1_b, tp3.1_b2, tp3.1_b5, tp3.1_b6, tpB40_b1, tpB40_b2, tpB40_b3

SITUATION IDENTIFIED IN: tfacp1140s000 "Approve Purchase Invoices "

SITUATION DESCRIPTION:

Currency gain/loss after approval.

In the session tfacp1140s000 "Approve Purchase Invoices " the projectcost amount of an orderline

with a projectcode is calculated based on the rate-factor of the orderheader. When the currency-rate

is changed after the moment of inserting the order-line, the projectcost amount is wrong. The projectcost amount

must be calculated with the currency rate of the invoice.

SOLUTION DESCRIPTION:

The contra posting of the commitments is still done with the currency-rate of the purchase order.

But the projectcost amount is calculated based on the currency rate of the invoice header (tfacp1110s000).

The projectcost amount in the invoice currency is maintained via session tfacp1131s000 "Match Receipts" or

in session tfacp1132s000 "Maintain Matched Receipts".

Modifications in software components have been marked with DF 11458-1.

SITUATION IDENTIFIED IN: tfacr2420m000 Print Aging analysis by customer

SITUATION DESCRIPTION:

The Label was printed as FC instead of HC - and the values were printed for columns greater than the number of periods

SOLUTION DESCRIPTION:

The Labe has been corrected to HC and the colomn error has been corrected by DF 11517

tf3.1_b7, tfB40_b4, tfB40_c1.

SITUATION IDENTIFIED IN:

tfacr3410m000 "Maintain reminding advice".

SITUATION DESCRIPTION:

When reminders were printed for transactions of type cash (unallocated receipt), the interest was calculated with the due

date 0.

SOLUTION DESCRIPTION:

Don't calculate the interest when the due date is 0.

tfB40_b4, tfB40L_b4_mcr0, tfB40_c1, tfB40_c_mcr0

SITUATION IDENTIFIED IN : Transfer Payments ( tfcmg1260s000 )

SITUATION DESCRIPTION:

When the Check used is the German Layout the checks were being printed for the entire amount owed to the Supplier. The

parameters of the Payment Method were not considered. The Checks should be printed for each line in the Composed

Payments Table.

SOLUTION DESCRIPTION:

The layout of the reports were changed so as to allow the checks to be printed per line in the composed payment table. This

basically meant that the layouts were changed from being with respect to tfcmg103.suno to being with respect to

tfcmg103.srno.

3.1_a2, 3.1_b7, 3.1L_b7_glo0, 3.1L_b7_jit0, 3.1L_b7_nl10, B40_b4, B40_c1

SESSION ERROR INDENTIFIED IN:

tfgld0107m000 "Maintain Period Status".

PROBLEM TEXT:

Cannot close tax period 01 if transactions exist in next year see attached pages.

It is not possible to close tax period 01 of a year if transactions exist in tax period 1 of the following year. This happens when

the fiscal & tax year differ. The program checks for transactions in the tax period of the fiscal year, not the tax period of the

tax year.

a PMG-employee has seen this problem at the customers site and has provided the following description :

"The error is easy to reproduce. Looking in the source I found that the function "check.period.tfgld100" does not take into

account the tfgld100.vyer. So the situation is now that there are batches in 1996 with the status < finalized found that have

tfgld100.vprd = 1 . So the errormessage tfgld0478 is given ("Unposted transactions present, closing period not allowed") So

the test "if tfgld100.yprd = tfgld007.prno then"

in function "check.period.tfgld100" in program 1206/0107 is not enough.

Please build in a test that also checks tfgld100.vyer = tfgld007.year."

SOLUTION DESCRIPTION:

The check if closing is allowed in tfgld0107 is different from tfgld1206. Checking for batches in tfgld100 is done by index_4

(fiscal year, tax period), this should be (tax year, tax period). Although there is no index on these fields, i changed the

query as mentioned.

SESSION ERROR IDENTIFIED IN: Maintain Payment Advice (tfcmg1120m000)

PROBLEM TEXT:

Case: you enter the payment selection. Press a C in the choice field and enter all the fields. Nothing is changed. Press P

(previous) and N (next) and press again a C and change the payment amount. Confirm with a W. After that press C and enter

all the fields. Strange thing is now that the default discount will be set on 0.00 instead of the amount which was already in

the field. This error can lead to unwished paymentdifferences.

SOLUTION DESCRIPTION:

For each record it is necessary that the default discount, payment surcharge and payment difference appear when the payment

amount is changed. Therefore you have to initialize the booleans, which triggers the calculation of de defaults, every time

you want to modify a record.

SESSION ERROR INDENTIFIED IN:

Maintain Cash Management Transactions (Anticipated payments) (tfcmg2140s000)

Maintain Anticipated Receipts (tfcmg2117s000)

PROBLEM TEXT:

tfcmg2117s000, error message, "Unknown symbol 'compnr' in expression: value 0 assumed", appears on the screen.

SOLUTION DESCRIPTION:

Forms have been modified and the error does not appear anymore.

SITUATION IDENTIFIED IN: Print Column Balance (tfgld3409m000)

SITUATION DESCRIPTION:

In this session, the balance is displayed only for the period entered in the form , whereas it should actually print the balances

till the entered period

SOLUTION DESCRIPTION:

Now the coloumn balance is printed from the first period of the fiscal year till the entered period

tf3.1_b1, tf3.1_b2, tf3.1_b5, tf3.1_b6, B40_b1, B40_b2, B40_b3, B40_c.

SITUATION INDENTIFIED IN:

Compose Payments - tfcmg1240m000.

SITUATION DESCRIPTION:

When payments are processed using the payment method with the fields "Report group" and "Report group report" on 14 and 0

respectively (i.e. using BTL91 format), it is observed that the description of the country is not written in the output file.

SOLUTION DESCRIPTION:

The BTL91 format report has been modified and the description is now written in the output file.

SESSION ERROR IDENTIFIED IN:

"Print Specifications Delivered, not yet invoiced" (tfacr1432m000)

SITUATION DESCRIPTION:

Wrong zooming is performed. When zooming on the order from/to field it zoomed to a session with purchase orders. This

should be a zoom session with sales orders.

SOLUTION DESCRIPTION:

Changed form, so that the correct zooming sessions are enabled.

3.1_a, 3.1_b, B40_b.

SITUATION INDENTIFIED IN:

tffst1100m000 - Maintain Financial Statements.

SITUATION DESCRIPTION:

When the customer prints several reports he gets the error message "Cannot continue in tffst1214s000". Error 111 on

tffst199100 (no retry point specified).

SOLUTION DESCRIPTION:

Retry points specified.

SESSION ERROR INDENTIFIED IN:

tfacp1140s000 Approve Purchase Invoices

tfacp1230s000 Automatic Matching of Purchase Orders

tfacp1250s000 Receive Purchase Invoices (EDI)

PROBLEM TEXT:

When an invoice with an amount of 0.01 Australian dollar's (currency rate 1.8) is approved then

the currency rate displayed in the approval document is 2.0.

SOLUTION DESCRIPTION:

Function called in the approval program was not taking care of the small amounts. Modified the

the function and the currency rate is now correctly displayed.

B40_b, B40_c

SESSION ERROR INDENTIFIED IN: tfcmg1260m000

PROBLEM TEXT:

For Clieop files a line is created with transaction type and documentnumber for payment (line 0150). This information is

internal Baan system information. The problem is however that this information is also communicated to suppliers of our

customers. Next to the suppliers invoice number also the Baan document number will be showed.

SOLUTION DESCRIPTION:

Detail Field 2 has been deleted. For payments there is no need to

write a transaction type and document number.

3.1_b, B40_b

SESSION ERROR INDENTIFIED IN:

tfacp1110s000

PROBLEM TEXT:

'transaction is on, cann't continue'

SOLUTION DESCRIPTION:

Solved "Transaction is on " Error.

This error was caused due to a forgotten commit.transaction in the after choice.cont.process section.

3.1_b, B40_b

SESSION ERROR INDENTIFIED IN:

tffst1205m000

PROBLEM TEXT:

The session "Select Financial Statement Values" (tffst1205m000) is not working correct after installing ID 10230963.

SOLUTION DESCRIPTION:

Several ID's from 3.1a are buildt forward to the 3.1b... & B40_b... versions.

tfB40_b, tfB40_b_glo0, tfB40_b_gls0, tfB40_b_mcr0, tfB40_c.

SESSION ERROR IDENTIFIED IN:

tfacp1140s000 Approve Purchase Invoices.

OTHER SESSIONS:

tfacp1110s000 Register Purchase Invoices.

tfacp1130s000 Match Purchase Invoices with Orders.

tfacp1131s000 Match Purchase Receipts.

SITUATION DESCRIPTION:

If you change the order in tfacp1140s000 it has no effect on the 'FIND'-command.

SOLUTION DESCRIPTION:

The option 'Change Order' is now available on the form of session tfacp1140s000. It is now possible to use index 1 and

index 2. A small change was made to the script of the session because some of the fields were not always displayed

correctly.

A small change was made to the script of session tfacp1110s000 because some of the fields were displayed incorrectly when

returning from a zoom session.

A small change was made to the script of session tfacp1130s000 because some of the fields were displayed incorrectly when

returning form a zoom session.

The forms of session tfacp1131s000 were modified. It is not longer possible to zoom on the fields supplier and order, on

both forms (tfacp1131s0001/tfacp1131s0002).

3.1_b, B40_b , B40_c

SITUATION IDENTIFIED IN:

Print Reconciliation of Work-in-Process - tfgld5400m000.

SITUATION DESCRIPTION:

Session tfgld5400m000 prints all the projects, irrespective of whether the project has a value or not. When the customer

prints a report from session tfgld5400m000, he or she is faced with a large number of pages, including the pages from the

projects with a zero value.

Also, the total sum of the variances is not printed as expected at the bottom of the last page, and as a consequence it has to

be calculated manually. An extra field for the total value of the variance would be convenient.

SOLUTION DESCRIPTION:

The reports now have the choice as to whether to print the zero values or not. With report tfgld54001100 and tfgld54003100 a

grand total field is included.

For all the PVRCs a new label is generated for the question on form: "Suppress zero values".

For B40_b4 some labels need to be added.

3.1_a, 3.1_b, B40_b

SESSION ERROR INDENTIFIED IN:

tfgld3203m000

PROBLEM TEXT:

The session tffst1205m000 is not selecting the right values.

SOLUTION DESCRIPTION:

Tffst1205s000 is not selecting the right values the values in the history tables are wrong due to a bug in tfgld3203m000. This

bug is fixed now. To fix the history tables, do the following (in order):

1. Install ID 11009

2. Run session tfgld3203m000 "Rebuild opening balance/history from transacitons"

(3) If ID 10230963 is present in tffst1205m000 then install also Defect 11999

4 Run session tffst1205m000 "Select Financial statement values"

tf3.1b, tfB40_b4, tfB40L_b4_mcr0, tfB40_c1.

SITUATION IDENTIFIED IN:

Recalculate Open Entries - tfacp200 (tfcor0260).

Recalculate Open Entries - tfacr200 (tfcor0261).

SITUATION DESCRIPTION

These correction programs were written to take care of a fixed number of positions for the Customer Code and Supplier Code.

If the customer used Codes with the number of positions is different from the standard length (which is 6), then each of the

customers will require a separate program.

SOLUTION DESCRIPTION:

Now the length of the domains, tccuno and tcsuno, are read at runtime. The Input of the Customer/Supplier Number, on the

form, is independent of the length of these codes.

B40_b

SESSION ERROR INDENTIFIED IN:

tfgld3405m000

PROBLEM TEXT:

After upgrading from triton 3.1 to Baan 4.0b, cannot supress the Zero Balance in Print Trial Balance - with Dimension

report (tfgld3405m000). The report selection fields screen does not have Print Zero Balances Yes/No option as in Triton 3.1

screen.

SOLUTION DESCRIPTION:

Zero balanced are always supressed now.

3.1_b, B40_b

SESSION ERROR INDENTIFIED IN:

tfacp1110m000, tfacp1120s000

PROBLEM TEXT:

When in tfacp1110s000 a tax country code is used without any value (i.e. the code with the "blank"),

the message "Buchungsdaten pro UST-code nicht vorhanden" appears.

But for a tax code without any value, no ledger account should be required.

Mind: when inserting any transaction in acp1110s000, the tax country code always appears default.

SOLUTION DESCRIPTION:

The check for the tax accounts for deduction should be according to the parameter in ACP for level of tax calculation. If

this parameter = transaction header the check should be in tfacp1110m000 ("Maintain purchase invoices") and if the

parameter = transaction line then it should be in tfacp1120s000 ("Maintain purchase invoice transactions")

B40_b4, B40_c1.

SESSION ERROR IDENTIFIED IN:

tfacp2420m000 "Print Aging Analysis by Supplier".

tfacr2420m000 "Print Aging Analysis by Customer".

SITUATION DESCRIPTION:

We cannot access the field "last invoice date / period" by tabbing through the screen. We can only access this field by

using the arrow keys.

SOLUTION DESCRIPTION:

The field "last invoice date / period" was initialized twice. First it is initialized by the current date and later by the

current fiscal period (tfgld005.prno). Input is then disallowed once. The second initialization and disallowance has been

removed.

tf B40_b4, tf B40_c1

SITUATION IDENTIFIED IN:

tfcmg1246s000 ( Compose Payments )

SITUATION DESCRIPTION:

The last Invoice was added to the existing set of invoices again and again when the upward and downward arrow keys were

pressed. Also , it was reported that it calculated wrong values for

documents of type " Sales Invoice "

SOLUTION DESCRIPTION:

Error rectified now . The form shows the correct number of invoices for the payment batch and supplier. The second error

was automatically solved when the first was rectified

tfB40_b4, tfB40L_b4_glo0, tfB40L_b4_gls0, tfB40L_b4_mcr0, tfB40L_b4_sch0,

tfB40_c1

SITUATION IDENTIFIED IN:

Maintain Integration Relations By Range ( tfgld4122s000 )

Maintain Integration Relations By Elememt ( tfgld4123s000 )

Maintain Integration Relations By Range ( tfgld4124s000 )

Maintain Integration Relations By Element ( tfgld4125s000 )

SITUATION DESCRIPTION:

When inserting in tfgld4122s000 data,zooming on Main item's warehouse wrong session arises. The normal session which

should arise is the warehouse's one and not

tcmcs0506s000:Display unit set.

SOLUTION DESCRIPTION:

The correct zoom session has been added to the include which determines the sessions zooomed to.

3.1_b, B40_b, B40_c.

SESSION ERROR IDENTIFIED IN:

tfacp1120s000 "Maintain Transaction Purchase Invoices".

tfacr1111s000 "Maintain Transaction Sales Invoices".

SITUATION DESCRIPTION:

The situation can be duplicated as follows:

1. Book a purchase invoice directly on a ledger account by using acp1110s000 and 1120s000.

2. Make a purchase invoice correction with session acp2110s000. Press Y - you will get session acp1120s000 for entering a

ledger account.

3. Instead of filling in this account, press E.

4. You will get the message 'still transactions to be entered'. After first pressing enter and then E you will be returned to

session gld 1101m000.

5. You will see that the document does not balance.

6. Go to the transaction type session acp 2110s000 again and press Y on the invoice that you have changed (step 2) - you

will NOT get session acp 1120s000 again.

It is not possible to make an adjustment in a batch after you have left it.

SOLUTION DESCRIPTION:

Processing the invoice correction to maintain the transaction must not be finished until the transaction is balanced. It has

to be done in this way because you cannot make an adjustment for this transaction type after leaving tfacp2110s000.

(Technical note: There is no record to operate on).

When you want to leave tfacp1120s000/tfacr1111s000, after you have made invoice corrections, the whole correction must

be posted.

tfB40_a, tfB40L_a2_glo0, tfB40L_a2_gls0, tfB40_b, tfB40L_b4_mcr0, tfB40L_b4_glo0 , tfB40_b4_gls0, tfB40_c

SITUATION IDENTIFIED IN:

tfgld1103s000 ( Maintain Journal vouchers)

SITUATION DESCRIPTION:

In BW windows, the desription for dimensions was not displayed. However, in ASCII, the description is displayed

SOLUTION DESCRIPTION:

This solution solves defect number 17028 (in tfB40_a) and defect number 10500 (in tfB40_b and tfB40_c).

Error rectified. The descripton for the dimensions is displayed now in BW interface too

3.1_b7, B40_b4, B40L_b4_mcr0, B40_c1, B40L_c_mcr1

SESSION ERROR IDENTIFIED IN:

tfacr4410m000 "Print Sales Invoices.

PROBLEM TEXT:

Sales creditnotes made in the ACR module did not show up with a negative amount. Sales creditnotes made via Distribution

did. Sometimes it is confusing. when a creditnote does not show up with negative amounts.

SOLUTION DESCRIPTION:

Sales credit notes should look the same in distribution as in finance. The best way is showing negative amounts on them,

because it is more clear that it are creditnotes, so that making faults in handling the creditnote can be prevented.

When the transaction type of the sales invoice is "Sales credit note" the shown amounts are now multiplied by -1.

3.1_b, B40_a, B40_b

SESSION ERROR INDENTIFIED IN:

tfcmg6230m000

PROBLEM TEXT:

The last amount is shown on the

PROFORMA INVOICE( Print Only Overdue Invoice=NO)

I test the Proforma invoice data as the

follow. 1. Run the Maintain Sales Order(tdsls4101m000) and zooming , the Maintain

Advance Payment Schedules(tfcmg6110s000) should be maintained. In this session, I

give this 100 percent. 2.Print Proforma Invoices(tdsls4435m000). 3. Run the Maintain Transactions(tfgld1101m000) and it

is registered as an Advance Receipt in the Maintain Bank Transaction(tfcmg2100s000), and finalized. 4. Run the Link

Advance Receipts to Proforma

invoices(tfcmg6200mn000). 5. Run the Process Proforma Invoice(tfcmg6230m000)

8. I run Maintain Sales Order (No.1).This amount is 1226.-. I receive the amount of- from a customer and run No.3 and

No.4. And then I receive the amount of 500.-

9. from the customer again and run No3 and No4. I receive the amount of 200.-

10. from the customer and run No3 and No4. And then run the Process Proforma

Invoice (tfcmg6230m000). But the Proforma Invoices is shown that the Amount

is 1226.-, the Amount Paid is 200.-, and the Remark is Partial receipt.

In the TABLE (tfcmg601), 226.-, 500.- and 200 can be find by each Seq. No.

I think these amounts, 226.- 500.- and 200.- should be shown on the

Proforma Invoice(tfcmg6230m000).

SOLUTION DESCRIPTION:

The program should know it is possible to have : One payment to a document, one payment for more docs,

more payments for one doc and more payments for more documents.

SESSION ERROR IDENTIFIED IN: tfacr2121s000 "Assigning credit notes to invoices"

PROBLEM TEXT:

Assing credit-invoices with a currency rate factor of 100 to an invoices with currency rate factor of 1, the system

calculates a wrong amount which still must be assigned to an normal invoices. This calculated assigning amount by the

system isn't correct.

SOLUTION DESCRIPTION:

Now, the linked amount is calculated correctly, also when the currency of the invoice or the credit note has a rate factor

unequal to 1.

SITUATION IDENTIFIED IN: Maintain Posting Data of Standing Orders/Stand Alone Paym ( tfcmg1113m000 )

SITUATION DESCRIPTION:

In the session tfcmg1113m000, at the choice prompt when we zoom it does not zoom to session tfcmg3105s000 Maintain

Expense Tax Accounts - Standing Order.

SOLUTION DESCRIPTION:

This Solution solves defect 12237.

The zoom to session tfcmg3105s000 Maintain Expense Tax Accounts - Standing Order is attached to session

tfcmg1113m000.

3.1_b, B40_b, B40L_b_glo0, B40L_b_gls0, B40L_b_mcr0, B40_c.

SITUATION IDENTIFIED IN:

tfacp1132s000 Maintain Matched Receipts.

SITUATION DESCRIPTION:

Different status detected when matching via tfacp1132s000 or tfacp1131s000.

SOLUTION DESCRIPTION:

The receipt status was set to free when the invoice was not completely matched (i.e. when receipt-amount = invoice-amount

and receipt-quantity = invoice-quantity) and the invoice-amount was zero (This was regardless of what the invoice-quantity

was). It has now been set to match, when a quantity or an amount is matched. It is only set to free when the invoice-amount

and the invoice-quantity are zero.

3.1_b, B40_b

SESSION ERROR INDENTIFIED IN:

tfcmg1240m000

PROBLEM TEXT:

Supplier : 1001

Invoices: ACP 94000174 - 94000176 with amount - 100,-

ACP 94000177 - 94000180 with amount +100,-

All reference strings filled with fifteen characters.

Composing option "characters", limit "50" , action "more"

Result:

1st payment ACP 94000179

ACP 94000178

2nd payment ACP 94000177

ACP 94000176

ACP 94000175

3rd payment ACP 94000174

ACP 94000180

This should be :

1st payment 3 invoices (179 - 177)

2nd payment 3 invoices (176 - 174)

3rd payment 1 invoice (180)

SOLUTION DESCRIPTION:

In case of composing option characters, number was increased two times for the first invoice.

That resulted in wrong composing

tf 3.1_b7, tf B40_b4, tf B40L_b4_mcr0, tf B40_c1

SITUATION IDENTIFIED IN:

tfacp2421m000 (Print Purchase Invoices)

SITUATION DESCRIPTION:

The Session Printed the invoices with status " Transactions entered " as well though it was specified at the form level to

print

only "Registered" Invoices

SOLUTION DESCRIPTION:

Now The session prints only invoices with the status specified in the form . Invoices with status " Transactions entered" are

printed only

if the field " Invoices to be Printed " is set as " All "

tf3.1b, tfB40b.

SESSION ERROR IDENTIFIED IN:

tccom2501m000 "Display Suppliers".

PROBLEM TEXT:

When a part of the invoice amount is written to a cost ledger account (in session tfacp1133s000) the supplier's turnover is

not updated for that amount. This is not correct.

SOLUTION DESCRIPTION:

When an invoice is approved, the part of the invoice amount that is booked on a cost ledger account (in session

tfacp1133s000) is now added to the supplier's turnover.

Order amount: 100 (Supplier's turnover is updated with 100)

Invoice amount: 120

Matched with order: 110

Price difference: 10 (Supplier's turnover is updated with 10)

Written to cost account: 10 (Supplier's turnover is now updated with 10)

3.1_b, B40_a, B40_b

SESSION ERROR IDENTIFIED IN:

tfcmg2100s000

PROBLEM TEXT:

The problem is that a currency difference occurs.

This may not occur because only amounts for discounts, late payment surcharges and price differences

were changed.

SOLUTION DESCRIPTION:

Currency difference amount was created because discount,late payment surcharge and price difference

were handled as amounts in HC.

3.1_b, B40_b

SESSION ERROR IDENTIFIED IN:

tfcmg1240m000

PROBLEM TEXT:

Tested on daytona, company 902, 3.1_b7.

Supplier : 1001

Invoices: ACP 94000174 - 94000176 with amount - 100,-

ACP 94000177 - 94000180 with amount +100,-

All reference strings filled with fifteen characters.

Composing option "characters", limit "50" , action "more"

Result:

1st payment ACP 94000179

ACP 94000178

2nd payment ACP 94000177

ACP 94000176

ACP 94000175

3rd payment ACP 94000174

ACP 94000180

This should be :

1st payment 3 invoices (179 - 177)

2nd payment 3 invoices (176 - 174)

3rd payment 1 invoice (180)

SOLUTION DESCRIPTION:

If it is the first record, the program should not add the number of characters from the reference twice

SESSION ERROR IDENTIFIED IN: tdsls4102s000 "maintain sales orderlines"

SITUATION DESCRIPTION:

On inserting a process item on a orderline with issue type is components (form 2) error 606 occurs,

(reference does not exist) in session "maintain sales order lines" (tdsls4102s000).

This error comes from process. After inserting a formula in "maintain formulas" (tpfrm0110m000) automatically

material is linked to this formula in session "maintain materials" (psfrm0111s000). This process item is non stockable and

therefore has no warehouse. Leaving the warehouse empty will lead finally to an error 606 in salesorders.

SOLUTION DESCRIPTION:

When issue on components is used for a containerized process item the formula is always exploded to 1 level deeper than set

in the sales order parameters. Therefore the level that contains the actual non stockable process item is always exploded.

The changes have been marked by : DF 11016-1.

3.1_b,B40_b

SESSION ERROR IDENTIFIED IN:

tfcmg1120m000, tfcmg4120m000

PROBLEM TEXT:

The parameters of the used payment method are:

- Document received : Yes

- Document accepted/sent : No

When using this kind of payment method, it is possible to select invoices for payment again after process payments has

executed.

After Status Balance = Anticipated Balance Select possible

Select invoices for payment selected No No

Process payments empty No Yes

Reconciliation empty Yes No

SOLUTION DESCRIPTION:

A message will be displayed if for this document already an anticipated document is generated

3.1_a2, 3.1_b7, B40_b4, B40L_b4_glo0, B40L_b4_gls0, B40L_b4_mcr0, B40_c1, B40_c_mcr1.

SESSION ERROR IDENTIFIED IN:

tfacp1132s000 "Maintain matched receipts"

PROBLEM TEXT:

When an invoice is matched via session tfacp1132s000 "Maintain Matched Receipts" the price difference is not calculated

right.

Also the calculating of the default amount is based on the currency-rate of the purchase order in contrast with the session

tfacp1131s000 "Match Receipts". In the last named session the currency-rate, found via the systemdate, is used and not the

currency rate of the purchase order.

SOLUTION DESCRIPTION:

Two problems are mentioned in the problem text.

Wrong calculation of price difference and using different currency rates in tfacp1131s000 and tfacp1132s000. Both problems

are solved. The price difference is calculated right now and tfacp1132s000 now uses the same currency rate as tfacp1131s000.

This is the currency rate belonging to the transaction date.

3.1_a, 3.1_b, B40_a, B40_b

SESSION ERROR INDENTIFIED IN:

tfgld3203m000

PROBLEM TEXT:

Some of the records updated by this program, were updated more then once.

After analysis of the program, we discovered that the statement "WITH RETRY" was not present in the select. So whenever a

lock is detected, the system goes back to his retry point and starts to reexecute the COMPLETE select.

SOLUTION DESCRIPTION:

Added "With Retry" to avoid double countings

SESSION ERROR INDENTIFIED IN: Maintain Posting Data Standing Orders/Stand Alone Payment (tfcmg1113m000)

PROBLEM TEXT:

In the session tfcmg1113m000, the description of the ledger account is not displayed.

SOLUTION DESCRIPTION:

Source has been fixed and now the ledger account description is getting displayed.

B40_a, B40_b

SESSION ERROR IDENTIFIED IN:

tfacr3410m000

PROBLEM TEXT:

When you have more invoices to remind for one customer and each particular

invoice has a different reminder number, in session tfacr3410m000 and

tfacr3420m000 the wrong reminder number is printed.

SOLUTION DESCRIPTION:

The session "print reminder selection" now prints the correct letter number

3.1_b, B40_b

SESSION ERROR INDENTIFIED IN: tfcal2403m000 "Print activity and cost object results"

PROBLEM TEXT:

On report "Detailed results by activity/dimension" the field "amnt/quantity" was not always calculated correctly.

SOLUTION DESCRIPTION:

The fiels total.amount and total.quantity were not always inittialized. This caused wrong values on the report. The error has

been corrected. Also now it is possible to zoom on the formfields year and period.

tfB40_b4, tfB40_c1, tfB40_b4_mcr0

SITUATION IDENTIFIED IN:

tfacp2420m000 ( Print aging analysis by supplier )

SITUATION DESCRIPTION:

The amount for correction documents was being displayed in the Amount paid colom.

SOLUTION DESCRIPTION:

Error Rectified. Now the amount for correction document is being shown in the invoice amount colom only.

tfB40_b4, tfB40_b4_mcr0, tfB40_c1.

SITUATION IDENTIFIED IN:

tfacp2535s000 (Display supplier invoices in a company).

SITUATION DESCRIPTION:

The Session takes a long time to be activated.

SOLUTION DESCRIPTION:

Performance improvements done.

3.1_b, B40_b.

SITUATION IDENTIFIED IN:

Reconciliation of Receipts/Payments - tfcmg2103s000.

PROBLEM TEXT:

When in cmg2103s000 when setting the status of a completely reconciled document back to <open>, the status of the fields

<scrn> in cmg204 and srcn cmg111 remain as "processed". Also, the field <ramt> in cmg111 has a value.

This is most likely the reason why the system generates an error message (cmg2123), when trying to delete a de-reconciled

document.

SOLUTION DESCRIPTION:

Status now correctly updated within function itfcmg2000, for tables tfcmg204/tfcmg111.

tfB40_a2,tfB40_b4, tfB40L_b4_mcr0, tfB40_c1

SITUATION IDENTIFIED IN:

tfgld1114s000 (Maintain Journal vouchers)

SITUATION DESCRIPTION:

Dimension description not displayed in BW version

SOLUTION DESCRIPTION:

Form size adjusted accordingly to display dimensions

SITUATION IDENTIFIED IN :

Print Company Parameters ( tfgld0404m000 )

SITUATION DESCRIPTION :

The display and report show different information for company parameters.

Specifically, the 'Ledger Accounts by Currency field' for company parameters is affected. If it is set to 'YES' in

tfgld0103m000, it prints on the report (tfgld0404m000) as 'NO'.

SOLUTION DESCRIPTION :

The error occurred because the particular table field was not addded as an Input field in the report. The field has now been

added as an Input field.

tfB40a1,tfB40_b1, tfB40_b2, tfB40_b3

SESSION ERROR INDENTIFIED IN:

tfgld0113s000

OTHER SESSIONS:

tfgld0112m000

PROBLEM TEXT:

Performance is very poor when accessing the session 'Maintain Payment Schedules'

SOLUTION DESCRIPTION:

Performance improved

3.1_a, 3.1_b, B40_a, B40_b

SESSION ERROR INDENTIFIED IN:

"Print Payment Advice List(tfcmg1401m000)"

PROBLEM TEXT:

The field original company is not always printed on the report.

SOLUTION DESCRIPTION:

The field 'orignal company' was only printed when a new supplier was printed. However, a supplier can have

invoices/standing orders with different original companies. So now, the original company is printed every time it changes.

SITUATION IDENTIFIED IN: Maintain Purchase Invoice ( tfacp1110s000 )

SITUATION DESCRIPTION:

In tfacp1110s000 when entering a Purchase Invoice, if a wrong supplier bank is entered, a wrong message " Bank Relation

not found " is displayed.

SOLUTION DESCRIPTION:

This solution solves the defect 639.

The message was changed from " Bank Relation not found " to " Supplier / Customer Bank not found ".

tf3.1_b, tfB40_a, tfB40_b, tfB40_b_glo0, tfB40_b_gls0, tfB40_b_sch0, tfB40_b_mcr0, tfB40_c

SITUATION IDENTIFIED IN:

Maintain Transaction Types ( tfgld0111m000).

Maintain Last Used Document Nos by Transaction Type Series ( tfgld0114s000 ).

SITUATION DESCRIPTION:

It was possible to enter a lesser number of digits for the default series ( in tfgld0111m000 ) than was specified in the

number of digits for series. The same was possible in tfgld0114s000 when maintaining the actual series.

SOLUTION DESCRIPTION:

This solves the defect #12544. A check has been added to ensure that the user must enter the exact number of digits that are

mentioned in the field "Number of Digits for Series" when entering a Transaction type or when modifying an existing record.

A new message has been created to give information to the user about the lower limit of the range of acceptable data.

SESSION ERROR IDENTIFIED IN:

tfacp1433m000 "Print Registered Invoices"

PROBLEM TEXT:

The session tfacp1433m000 produces a report that includes registered purchase invoices with the statuses "Registered",

"Matched" and "Approved". "Approved" invoices should not be included, and were not in previous versions.

SOLUTION DESCRIPTION:

In previous versions invoices could be printed until a fiscal year/period. Functionality was added by adding a from fiscal

year/period parameter. Although the program was rewritten, the form was not changed. Besides that a change was made

because of a bug when creditnotes were assigned to invoices. After fixing this bug all invoices were printed, which was not

correct.

Now on the form de field "fiscal year/period from" is added and the program is changed so that all transactions that influence

the amount of the interim account within the interval of periods are printed. These are:

1. All registered and NOT matched/approved invoices within the interval of periods.

2. All matched/approved invoices which are not registered within the interval of periods (with negative amounts).

3.1_a, 3.1_b, B40_a, B40_b

SESSION ERROR INDENTIFIED IN:

""Post Integration Transactions to Finance(tfgld4201m000)"

PROBLEM TEXT:

Some integration transactions cannot be posted to finance. The system gives the message <<Cannot define ledger account

(tdinv850)>>, but there is a ledger account defined in session tdinv8150m000.

SOLUTION DESCRIPTION:

There was an technical error in the program which posted the integration actions to finance. As a result of this, some

integration transactions could not be posted to finance and a message was generated in the logfile : <<Cannot define ledger

account (tdinv850)>>, although this was not the case. The error has been corrected.

tf3.1_b, tf3.1_b1, tf3.1_b2, tfB40_b, tfB40_b1

SITUATION IDENTIFIED IN:

Maintain Bank Transactions ( tfcmg2120s000 )

SITUATION DESCRIPTION:

In Bank transactions when the category of the transaction is a Journal and a ledger account which had an integration with

Project Sales was given as the input the system would not accept the ledger account. If a Ledger account with integration to

Project costs was used the system would accept it.

SOLUTION DESCRIPTION:

This solves Defect 11322.An unnecessary check was being done on the Ledger Account which has now been removed.

SESSION ERROR IDENTIFIED IN:

Compose payments (tfcmg1246s000)

PROBLEM TEXT:

If in the Payment method-parameters the composing option is set to 'invoices' and the number is '1', it is impossible to

manually compose more than one.

SOLUTION DESCRIPTION:

It now is possible to compose manually more payments than defined in the composing options per payment method.

tf3.1_b7, tf3.1L_b7_glo0, tf3.1L_b7_jit0, tf3.1L_b7_nl10, tfB40_b4 , tfB40L_b4_gls0, tfB40L_b4_glo0,

tfB40_b4_mcr0,tfB40_c1.

SITUATION IDENTIFIED IN:

tfgld1420m000 (Print Tax analysis).

tfgld1401m000 (Print non-finalized transactions).

SITUATION DESCRIPTION:

The VAT lines are shown twice on the above mentioned reports.

SOLUTION DESCRIPTION:

Error rectified. Under some circumstances records were added twice, so they were printed twice.

3.1_b, B40_a, B40_b

SESSION ERROR IDENTIFIED IN:

tfacr4220m000 Post Sales Invoices

PROBLEM TEXT:

When entering a manual Sales Invoice via sessions tfacr4100m000 and tfacr4101s000 and using quantities. These quantities

cannot be seen in session tfgld3508s000 'Display Transactions not Finalized and tfgld3509s000 'Display Transactions

Finalized'.

SOLUTION DESCRIPTION:

The session tfacr4220m000 Post Sales Invoices is not writing the quantities in the table of Non Finalized Transactions

(tfgld102).

SITUATION IDENTIFIED IN:

Display registered sales invoices (tfacr2532m000).

SITUATION DESCRIPTION:

Baan goes directly into session acr2525s000 'display sales invoices details', when you press the left mouse button ONCE

only on a document in session acr2532m000 'display registered sales invoices'.

You can leave session acr2525s000 and go back into session acr2532m000 again by clicking on the 'OK' screen button (using

the left mouse button). However, the hour glass remains on the screen!

SOLUTION DESCRIPTION:

Zooming from "Display Registered Sales Invoices (tfacr2532m000)" to "Display Sales Invoice Details (tfacr2525s000)"

now works correctly again. The same kind of solution was made for zooming from "Display Registered Purchase Invoices

(tfacp2532m000)" to "Display Purchase Invoice data (tfacr2532m000)".

3.1_b, B40_b

SESSION ERROR IDENTIFIED IN:

tfacr3440m000 "Print statements of Account"

PROBLEM TEXT:

Session tfacr3440m000, Print Statements of Account, does not reflect sales corrections at all; however, session

tfacr2420m000, Print Aging Analysis by Customer, does print the sales corrections accurately.

SOLUTION DESCRIPTION:

The sales corrections will be taken into account now.

3.1_b, B40_b, B40L_b_mcr0

SITUATION IDENTIFIED IN:

Assign Unallocated/Advance Receipts to Invoices - tfcmg2105s000.

SITUATION DESCRIPTION:

When the invoice currency and the bank transaction currency are the same, the program is still trying to convert the

unallocated amount into the invoice currency through the home currency. When the currency rate is changed, the new amount

in the bank currency may be different from the amount in the invoice currency. Thus, the batch remains unbalanced and the

status is not changed to "ready".

SOLUTION DESCRIPTION:

If the bank currency is the same as the invoice currency, then the related invoice amount is calculated directly from the

unallocated amount without having to translate it into the home currency.

SITUATION IDENTIFIED IN: Maintain chart of accounts (tfgld0108m000)

SITUATION DESCRIPTION:

When inserting new records in the financial company (not used as logistic) the field logistical company is filled default

with the financial company.

SOLUTION DESCRIPTION:

The field is now filled with the logistic company

SESSION ERROR IDENTIFIED IN:

tdedi0070 "Field formating".

PROBLEM TEXT:

The input field of this function does not work with the standard maximum of 18 positions that a fieldname can have.

SOLUTION DESCRIPTION:

The input field of this function was changed so that a maximum of 18 characters is possible.

(The improvements have been marked in the source with DF 12860-1).

tfB40L_b_mcr0, tfB40_c1

SESSION ERROR INDENTIFIED IN: Maintain Bank Transactions (tfcmg2100s000)

PROBLEM TEXT:

When entering bank transactions, it is possible to leave the field <transaction type> empty. Program does not give an error

message.

SOLUTION DESCRIPTION:

Source has been fixed and now the message "Transaction type not filled" gets displayed when the field is left blank.

SITUATION IDENTIFIED IN:

tfgld1430m000 ("Print Tax Analysis (suppliers))

SITUATION DESCRIPTION:

In column amount in HC is the invoice-total per invoice-line repeated. This repeated invoice-total is taken into the grand

total.

SOLUTION DESCRIPTION:

Now, the total amount is printed correctly. The invoice amount of each invoice is counted only once.

SITUATION IDENTIFIED IN:

tfgld4200s000 Post Integration Transactions to Finance Transactions

SITUATION DESCRIPTION:

Error message 'No additions present in tfgld415' is given when the integration records are posted to Finance.

SOLUTION DESCRIPTION:

Newest DLL tfgld4010 made aviable.

SITUATION IDENTIFIED IN:

tfgld4510m000 Display Integration Transaction by Project / Order

SITUATION DESCRIPTION:

Cost component not vissible on form tfgld4510m000.

SOLUTION DESCRIPTION:

The field cost components should be displayed from table Logistic Data (tfgld419) instead of Integration Transactions

(tfgld410).