B40_b2, B40_b3.

SESSION ERROR IDENTIFIED IN:

tppdm7260m000 "Read in and/or Print Supplier Diskettes".

OTHER SESSIONS:

None.

PROBLEM TEXT:

When reading a supplier disk and the "Automatic Item Generation" reads "Yes", the system gives error 606 when a new item

is added.

SOLUTION DESCRIPTION:

The origin of the error message has now been established. There was no record inserted in tiitm100.

Modifications in the software components have been marked with DF 10109.

SESSION ERROR IDENTIFIED IN: tppss2100m000 "Maintain planning board for project plan"

PROBLEM TEXT:

When an estimate is transferred to a budget via sesion tpptc0205m000 and the start- and finishdate in that estimation have

already been filled:

1. The start- and finishdates of the activities were equal to the startdate of the estimate. Because of this, the duration of an

activity was changed to 1 when

it was clicked in the planning board (session tppss2100m000).

2. The startdate for an activity was not rounded to the plan time unit.

3. Activities were always positioned at the start date, even when the default planning method was "Backward".

Also :

4. When the company calendar and trade group (or employee ) calendar are different, the finishdate of an activity could

change. This happened only for activities for which

the trade group (or employee ) calendar should be used, when the user stepped through the start- and finishdate fields in

session tppss2120m000 (maintain activities).

SOLUTION DESCRIPTION:

When an estimate is transferred to a budget, the start - and finishdate of the activities are now calculated based on:

1 the standard planning method

2 the start- or finish date of the estimate

3 the duration based on the budget lines

4 the appropriate calendars

Also in session tppss2120m000 (Maintain activities) the correct calendars are used for determining the dates.

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

tp3.1_b, tp3.1_b2, tp3.1_b5, tp3.1_b6, tpB40_a1, tpB40_b1, tpB40_b2, tpB40_b3.

SESSION ERROR IDENTIFIED IN:

tpppc2111m000 "Maintain Material Costs".

tpppc2151m000 "Maintain Equipment Cost".

tpppc2171m000 "Maintain Subcontracting Costs".

tpppc2191m000 "Maintain Sundry Costs".

PROBLEM TEXT:

You can change the document number for costs registered in Finance and split to Project. By default, the system will give the

invoice number. If you change this number (which should be possible), then the table is filled in differently (field cdoc) to the

way that it is for the default value. This causes problems with reports/queries.

SOLUTION DESCRIPTION:

The document number is by default aligned to the left. If the field is maintained manually then it is aligned to the right.

The leading zeros have no purpose. So, the field is now always aligned to the right. It has a length of 10 and the leading

zeros have been removed. The modifications to the software components have been marked with DF10803

SESSION ERROR IDENTIFIED IN: tppin4165m000 "Maintain Pro Froma Invoice"

tppin4167s000 "Maintain Advance invoice lines"

tppin4168s000 "Maintain Instalment invoice lines"

PROBLEM TEXT:

If the choice is made that for the project customer the tax has to be taken for the transactions that are made for this customer,

it is also mandatory to take the tax for advance invoices. At the moment this isn't the case. The field 'tax' of the advance is

set on YES but the tax code is not filled in the invoice (table tppin120).

SOLUTION DESCRIPTION:

In Finance it is possible in the session tfcmg0100m000 to decide whether the advance invoice should be calculated with or

without taxes. These settings overrule the standard tax method.

Modifications are made in sessions where a tax code could be filled or changed. It is now dependent of the integration with

finance and the settings for advance invoices.

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

SESSION ERROR IDENTIFIED IN: tpbop2140s000 "Configure Estimate"

PROBLEM TEXT:

Window doesn't close it self.

SOLUTION DESCRIPTION:

The process off tpbop3245 was placed in a group, The proces was killed but not the group, all the windows belonging to that

group will be activated until the group is deleted. The delete action is now used and problem is solved.

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

SITUATION IDENTIFIED IN: tppss6110m000 "Maintain Material Recommendations"

tppss6111m000 "Maintain Equipment Recommendations"

tppss6112m000 "Maintain Subcontracting Recommendations"

tppss6113m000 "Maintain Planned Warehouse Orders (Manufacturing)"

tppss6115m000 "Maintain Planned Warehouse Orders"

tppss6120m000 "Maintain Material Recommendations"

tppss6121m000 "Maintain Equipment Recommendations"

tppss6122m000 "Maintain Subcontracting Recommendations"

tppss6123m000 "Maintain Planned Warehouse Orders (Manufacturing)"

tppss6125m000 "Maintain Planned Warehouse Orders"

SITUATION DESCRIPTION:

When two users add a record the keys will be the same.

When the first user saves before the second user the second user gets a message that the record already exist.

After this the second user changes his ordernumber but he losts his data one the single fields below on the form.

So he has to enter his order again.

SOLUTION DESCRIPTION:

New sessions are made and replace the existing sessions. The sessions are sessions with single occurence forms.

The ordernumber is generated by the system during the save action. The ordernumber is the last used number increased with

one.

You sould change your menu's to be able to start these sessions.

Replace the next sessionnames:

tppss6810m000 --> tppss6812m000

tppss6113m000 --> tppss6123m000

tppss6115m000 --> tppss6125m000

Modifications in software components have been marked with DF10023

tp3.1_b, tp3.1_b2, tp3.1_b5, tp3.1_b6, tpB40_a1, tpB40_b1, tpB40_b2, tpB40_b3.

SITUATION IDENTIFIED IN: tpppc3101m000 "Maintain Revenues"

SITUATION DESCRIPTION:

When you are using a ledger account with an integration parameter, the field "Project sales" is not filled in at all.

In session tpppc3101m000 the field "Document" (tpppc301.cdoc) was also aligned right when it should have been aligned

left, as in Finance "Correction Document Number" (tfgld102.docn).

SOLUTION DESCRIPTION:

The same document number as in tfgld102.docn is also used in tpprc3400m000. All the cdoc-fields for the commitments have

been aligned left.

This problem had been previously solved, for Costs in DF10803.

Where modifications have been made in the software components, they have been marked with DF11076.

SITUATION IDENTIFIED IN: tpptc0410m000 "Print Extensions"

SITUATION DESCRIPTION:

It is not possible to print the extension data for the one customer as given in session Print Extensions. The system always

prints all extensions (of different customers) that meet the other criteria given in.

SOLUTION DESCRIPTION:

Before printing the extensions also the customercode is checked if it complies with the customercode chosen in the session

Print Extensions (tpptc0410m000).

Modifications in software components have been marked with DF11185-1.

tp3.1_b, tp3.1_b1, tp3.1_b2, tpB40_b, tpB40_b1, tpB40_b2, tpB40_b3

SITUATION IDENTIFIED IN: Delete Actual Budget Structure (tpptc1210m000)

SITUATION DESCRIPTION:

Deleting the top-element in element-structure results in error112.

SOLUTION DESCRIPTION:

The functionality of this session is as follows:

1. It should delete the given element from the structure. First it should delete its relationships

with its children then if the given element is the only parent of the child elements then it should delete the child

elements

(including the budget lines).

2. After that it should delete the given element.

There was a bug in the program ( It was not deleting the relationships of the given element with its parents) because of

which it was deleting

only the children of the given element leaving the given element in the structure.

Regarding the error112

This problem occured when we enter the top element and press 'Y' at the choice prompt twice.

The reason for this is that, when we press "Y" for the first time itself system deletes the top element including it's child

elements.

And when we press "Y" for the second time, because there was no check on the input data it was giving an error.

All the above mentioned bugs are fixed and commented with DF 11466.

SITUATION IDENTIFIED IN: tpppc4411m000 "Print Cost Control"

SITUATION DESCRIPTION:

If a selection is given for the activities the system prints more than the selected activities. Also the subtotals for activities that

are not in the selection are printed.

SOLUTION DESCRIPTION:

Modified the report so that only selected activities are printed.

During generating of control data the selection is now used.

Modifications in software components have been marked with DF11573-1

tp3.1_b, tp3.1_b1, tp3.1_b2,tpB40_b, tpB40_b1, tpB40_b2, tpB40_b3

SITUATION IDENTIFIED IN: Print Planned Purchase Orders (tppss6410m000)

SITUATION DESCRIPTION:

System was displaying " " as the default value of the field 'Project to' when no defaults are saved. This should be

ZZZZZZZ

SOLUTION DESCRIPTION:

Now the system displays ZZZZZZ as a default when defaults are not saved.

Modifications in software components have been marked with DF 11920

SITUATION IDENTIFIED IN: tpptc4120m000 "Maintain Purchase Budget Detail Lines"

SITUATION DESCRIPTION:

In session " Maintain Purchase Budget Lines" tpptc4120m000 the cost component is not defaulting from the cost object

table.

SOLUTION DESCRIPTION:

The default cost component is now read from the standard cost object table or project cost object table dependant on the type

the object.

Modifications in software components have been marked with DF434-1

SITUATION IDENTIFIED IN: tphrs1100m000 "Maintain Hours Accounting Transactions"

SITUATION DESCRIPTION:

If the maintain hours accounting (tphrs1100m000), it is possible to change the single fields at the lower part of the form

after changing the status to final or/and after processing transactions (tpppc4802m000) .

In some cases you get the message 'Activity not allowed according to status'. This is not always correct.

SOLUTION DESCRIPTION:

When the status in tphrs1100m000 isn't 'free' it is not possible to change the fields at the lower part of the form. (Project,

Element, Activity . . . )

Test on activity, element and extension status corrected.

Modifications in software components have been marked with DF12028-1

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

SITUATION IDENTIFIED IN: tpbop3150m000 "Maintain quantity sheet"

SITUATION DESCRIPTION:

Out of dims error in the tpbop3150m000.

SOLUTION DESCRIPTION:

The message out of dims is a failure in the allocated memory. Problem solved by a regular update of the database during

deleting.

After deleting of 10 rows the database is updated

Modifications in software components have been marked with DF 11843

SITUATION IDENTIFIED IN: Maintain Plans (tppss0110m000).

SITUATION DESCRIPTION:

The Finish Date ( Planning Board ) which by default should be filled by the Finish Date of the Project for which the plan is

defined is instead being filled by the Project Start Date.

SOLUTION DESCRIPTION:

The Finish Date ( Planning Board ) is now by default being filled by the Finish Date of the Project for which the plan is

defined.

There was a programming eror which has been corrected by DF 11935.

SITUATION IDENTIFIED IN: tpptc3100m000 "Maintain Budget Cost Analysis Codes by Project"

SITUATION DESCRIPTION:

When deleting a Cost Analysis Code, the entire corresponding budget data is not deleted. The budget data marked with Totals

Indicator "project" is deleted, but the budget data marked with Totals Indicator "total m" still exists.

SOLUTION DESCRIPTION:

When a Cost Analysis Code is deleted of a project also the data with indicator "Total m" is deleted for that specific

project. This indicator of the mainproject-total occurs in session tpptc3540m000 "Display Budgetted Project Costs" and

in session tpptc3541m000 "Display Budgetted Cost Component Costs".

Also the session tpptc3200m000 "Budget Cost Analysis" is changed for the recalculation of the mainproject-total. Because

after deleting of a Cost Analysis Code of a subproject the total amount of the related mainproject (with another projectcode)

helds the amount of the subproject still.

Modifications in software components have been marked with DF11403

SITUATION IDENTIFIED IN: tpppc2131m000 "Maintain Labor Costs"

SITUATION DESCRIPTION:

Cost rates of labor costs are calculated incorrect when using hourly wage types, where the surcharge field is not equal to 0%.

For example:

Employee with a cost rate of 20,-, surcharge hourly wage type is 100%, so the cost rate in form 1 in tpppc2131m000 has to

be 40,- (100% plus 100% of the hourly wage type).

The first time using this particular employee and hourly wage type the cost rate was calculated correct (40,-). The second and

third time the cost rate was 80,-.

After testing several hourly wage types, this problem always occurs using it the second and following times. In the example

the multiplying factor was 400%, in other tests I got

a factor 484%.

SOLUTION DESCRIPTION:

The new cost rate was only calculated the first time you entered a Labor Line. But for every line it should be calculated

according to the Hourly Wage Type.

Modifications in software components have been marked with DF12226

SITUATION IDENTIFIED IN: tpptc1230m000 "Generate Control Data"

SITUATION DESCRIPTION:

In case one activity is linked to budget lines of different elements, and the status of the activity is "actual" and the budget

status of one of the element is free(and the other is actual) the budget status is reset to free in case of running

tpptc1230m000. In this enviroment the leading budget for budgeting is the element budget and the leading budget for cost

control is the activity budget. The status of the activity should not be reset because the budget lines with status free will not

be taken in account for the control budget.

SOLUTION DESCRIPTION:

The budget status of the activity is not set to a lower value anymore, but a message is printed

"Of some budget lines the status is to low in activity ......'

Also a message is added for the situation that budget lines are skipped because of the status of the budget line, the status of

the element relation or the status of a surcharge.

Modifications in software components have been marked with DF10544

SITUATION IDENTIFIED IN: tppss6110m000 "Maintain Material Recommendations"

tppss6111m000 "Maintain Equipment Recommendations"

tppss6112m000 "Maintain Subcontracting Recommendations"

tppss6113m000 "Maintain Planned Warehouse Orders (Manufacturing)"

tppss6115m000 "Maintain Planned Warehouse Orders"

tppss6120m000 "Maintain Material Recommendations"

tppss6121m000 "Maintain Equipment Recommendations"

tppss6122m000 "Maintain Subcontracting Recommendations"

tppss6123m000 "Maintain Planned Warehouse Orders (Manufacturing)"

tppss6125m000 "Maintain Planned Warehouse Orders"

SITUATION DESCRIPTION:

Cost Component is not always accessible in the right way.

When adding text to an orderline you get an overflow error.

SOLUTION DESCRIPTION:

The field Cost Component is now accessible, dependent on the cost control levels of the project.

The overflow error solved.

Modifications in software components have been marked with DF12301-1

SITUATION IDENTIFIED IN: Copy Element Budget Data ( tpptc1245m000)

SITUATION DESCRIPTION:

It isn't allowed to copy a budget structure within the same project, whereas it should be possible according to the help

information.

SOLUTION DESCRIPTION:

Now system allows to copy the budget structure within the same project.

Modifications in software components have been marked with DF 12139

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

SITUATION IDENTIFIED IN:

tppss2106m000 "Maintain Planning Board for Resource Plan".

SITUATION DESCRIPTION:

The menu option "Total Labor Capacity by Capacity Type" will start session tppss7700m000 "Utilization chart", when a resource

plan has been selected for teams or employees. However, this chart will always be for the resource level (trade group, team or

employee) of the last plan in the selection, irrespective of the resource level that was chosen for the planboard.

SOLUTION DESCRIPTION:

The chart will now show the resource level of the selected project, when clicking "Total Labor Capacity by Capacity Type".

However, these projects can have different resource levels, when more than one project is selected. So, the chart defaults to

the level "Trade group".

The modifications in the software components have been marked with DF 11418.

SITUATION IDENTIFIED IN: tpbop3150m000 "Maintain quantity sheet"

SITUATION DESCRIPTION:

System hangs after marking for a relation to the calculation

SOLUTION DESCRIPTION:

Modified the zoom type of the session.

Modifications in software components have been marked with DF11862

SITUATION IDENTIFIED IN: tpbop3101m000 "Maintain estimate"

SITUATION DESCRIPTION:

In tp bop3101m000 it is possible to fill the standard costprice/purchase price (see the setting of field "Price policy")

default. If this price is changed to 0 and at the colom "Subcontracting" and you zoom to the session tppdm0513s000 and select

the same subcontracting code as you defined before the system will not change the price back to the standard price. For the

other costtypes the system does!!

SOLUTION DESCRIPTION:

The inernal code for activating zoomsession (Ctrl-Z) or find option (Ctrl-F) where the same. Made difference between two

options. Now difference between selecting a code and finding the right price .

Modifications in software components have been marked with DF12364-1

SITUATION IDENTIFIED IN: tppdm0410m000 "Print Standard items"

SITUATION DESCRIPTION:

If you give a selection less than the maximum selection the system also prints the data with ordersystems that is not in the

selection.

SOLUTION DESCRIPTION:

In the Prgram source the wrong tablefields where use to check the start and end ordersystem. Change the check to the right

tablefields.

Modifications in software components have been marked with DF12387

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

SITUATION IDENTIFIED IN: tpptc1113m000 "Maintain Element Budget (Subcontracting)"

SITUATION DESCRIPTION:

If the field "Cost determination" has the value "Time quantity" for a subcontracting code and this code will be used in the

session tpptc1113m000 the system will not take the right costprice if a pricelist is available for this subcontracting code in

tdpur0101m000.

SOLUTION DESCRIPTION:

The price searching was done too early with quantity = 0. Now the reading of the price is done at a later moment. After

entering or changing of the subcontractingcode only the price is read when the quantity is filled. The price searching is done

only when the quantity is entered for the first time on a new line. So when the quantity is changed from 0 to another value

the price searching is done but not when i.e. quantity 3 is changed into 5. The reason for this construction is that a

manually entered (or changed) price may not been changed by the price searching mechanism.

This modification is done for the budgetting of material, equipment and subcontracting.

Also a modification is done for the budgetting of items that the field Quantity is only filled by the fields Length / With and

Number of Units when the field Quantity has no value. In the case that Quantity is already filled, no recalculation is done.

Modifications in software components have been marked with DF12343.

SITUATION IDENTIFIED IN: Archive Projects ( tppdm7820m000 )

SITUATION DESCRIPTION:

If a project had to be archived and this project happened to have activities, it was not possible to archive this project as the

system was giving the following error message:

Fatal error: Error 606 (Reference does not exist) on tppss010812 in db_insert.

Fatal error: Can not continue in tppdm7820m000

Error: tppdm7820m000: A not terminated transaction is aborted

SOLUTION DESCRIPTION:

It is now possible to archive Projects having activities, because the planningboard groups are archived before archiving the

projectdata. The error 606 occured for the reference of tppss010 'Project Plans' to table tccom500 'Planning Board Groups'.

Modifications in software components have been marked with : DF 11923.

SITUATION IDENTIFIED IN: tpbop3430m000 "Print estimate by code"

SITUATION DESCRIPTION:

When printing estimate by code (tpbop3430m000) a strange thing happens.

A message occurs : Uncoded elements: 1 elem.grp

10 .....

20......

etc.

The strange thing is that not all uncoded elements are shown.

This is not right, every uncoded element should be printed.

SOLUTION DESCRIPTION:

A part of program is reprogrammed with a newer technique.

After modifications the output of testresults was correct.

Modifications in software components have been marked with DF 12499

SITUATION IDENTIFIED IN: Maintain Standard Equipments (tppdm0112m000)

SITUATION DESCRIPTION:

When entering a new record in session Maintain Standard Equipment (tppdm0112m000) the system does not require a tax code

to be entered at the moment the fields are being inserted.

In case there is no definition in tcmcs037 for a blank code and a description (no VAT), when the record is saved no warning

message such as "Tax Code not allowed" is displayed and the following error occurs:

"Fatal error 606 (reference does not exist on tiitm001901 in select cannot continue in..... DLL-otiitmdll0004]. Fatal error

cannot continue in tppdm0112m000 in DLL otiitmdll0004."

SOLUTION DESCRIPTION:

Several tables are modified namely tiitm001[Items], tiitm002 [Item Default Data], tipcs002 [Calculation Parts] and

tipcs021[Customized Items].

The reference mode of field 'cvat' has been changed from "Mandatory" to "Mandatory unless empty", so while copying

tppdm025 [Standard Equipment] to tiitm001 [Items] no fatal error will occur anymore when the VAT code is blank.

This solution solves defect 438.

SITUATION IDENTIFIED IN: tppdm0201m000 "Global Update of Prices and Rates"

SITUATION DESCRIPTION:

If session " Global Update of Prices and Rates" (tppdm0201m000) is used to update Subcontracts and Eguipments. The prices

in table " Maintain Items" (ttiitm001) are not be updated and therefor the prices of subcontracts and Equipments are not

correct after using session " Global Update of Prices and Rates" (tppdm0201m000).

SITUATION IDENTIFIED IN: tpbop3416m000 "Print Estimate Recapitulation"

SITUATION DESCRIPTION:

If you choose for part of estimate in the tpbop3416m000, all codes of total the estimate is given.

SOLUTION DESCRIPTION:

When chosen for a part of an estimate the selected elementgroup wasn't used in the selection of the printed lines.

Now the selected part of an estimate will only be printed.

Modifications in software components have been marked with DF12626-1

SITUATION IDENTIFIED IN: tpppc3101m000 "Maintain Revenues"

SITUATION DESCRIPTION:

Problem with delivering company in multi site situation.

When you create two projects, TEST1 (company 812) and TEST2 (company 813).

In session tpppc3101m000 I inserted three lines in the following order. The company number is automaticaly filled in.

line 1: project TEST2 -> delivering company 813

line 2: project TEST1 -> delivering company 812

line 3: project TEST2 -> delivering company 812

Line 3 is wrong. The companynumber of the previous line was taken as a default company number.

SOLUTION DESCRIPTION:

Now the correct company number is taken for each line.

Modifications in software components have been marked with DF12513-1

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

SITUATION IDENTIFIED IN:

tpbop3431m000 "Print estimate detail lines per code".

tpbop3430m000 "Print estimate by code".

SITUATION DESCRIPTION:

The selection is not transferred to the tpbop3431m000, when zooming on own code.

SOLUTION DESCRIPTION:

The length of the field for the selected items is now checked with the standard format of the coding system.

The 'from' and 'up to' coded, also checked the length of the field of the format from the coding system.

The modifications in the software components have been marked with DF 12624.

tp3.1_b, tpB40_b

SITUATION IDENTIFIED IN: Maintain Material Transactions to be Invoiced (tppin4157m000)

Maintain Labor Transactions to be Invoiced (tppin4158m000)

Maintain Equipment Transactions to be Invoiced (tppin4159m000)

Maintain Subcontracting Transactions to be Invoiced (tppin4160m000)

Maintain Sundry Cost Transactions to be Invoiced (tppin4161m000)

SITUATION DESCRIPTION:

When entering the records by Activity system is not generating the serial numbers correctly.

SOLUTION DESCRIPTION:

Now the serial numbers are generated correctly. Order of the form fields has been modified to correct the problem.

Modifications in software components have been marked with DF 11415.

SITUATION IDENTIFIED IN: Maintain Material Transactions to be Invoiced ( tppin4157m000)

SITUATION DESCRIPTION:

Description of the Element is not displayed in the second form.

SOLUTION DESCRIPTION:

Now the system displays the Element descritpion correctly.

Modifications in software components have been marked with 12630

SITUATION IDENTIFIED IN: tpbop3411m000 "Print Estimate"

SITUATION DESCRIPTION:

The system gives the possibility to choose between different kind of reports for the alternative elements but it prints not the

correct information. If you choose for the option "Nothing" the system also prints the alternative elements. If you choose for

the option "Marked" the system also prints elements that are not marked.

SOLUTION DESCRIPTION:

The decision wether an elementgroup or detaillines should be printed was not correct. The new situation is as follows:

When chosen for elements and or alternatives only the data and detaillines belonging to these groups are printed.

If no selection is made for elements and or alternatives and chosen only for detaillines the estimate index will not be printed

and only the detaillines will be printed.

Modifications in software components have been marked with DF12661

SITUATION IDENTIFIED IN: tpbop3430m000 "Print Estimate by Code"

SITUATION DESCRIPTION:

When printing tpbop3430m000 and choosing for a part of the calculation you get a lock if you start it for the second time.

SOLUTION DESCRIPTION:

Locking of session doesn't occur anymore.

Modifications in software components have been marked with DF12723-1

SITUATION IDENTIFIED IN: tppin4474m000 "Print Invoices"

SITUATION DESCRIPTION:

If the invoicemethod has the aggregation level not equal to "No" the system takes not the right amount for the transport total of

the extension and cost plus invoices. The system shows 0 as the transport total instead of the total of the first invoice page.

The total amount of the invoice is correct.

The system also prints the label "Transporteren" instead of "Transport" as the first line of the second page!!

SOLUTION DESCRIPTION:

The transport totals are correct now when the invoice method has an aggregation level.

The label "Transporteren" on the second page can be changed by the custumer himself and not by BAAN because of

compatibility reasons.

Change the invoice report layout with expression "transport head". Change the length of label code "tppins4474.07" into 9.

Modifications in software components have been marked with DF12636-1

SITUATION IDENTIFIED IN: tppin4264m000 "Create Invoices"

SITUATION DESCRIPTION:

System shows invoicenumber "1" in Display Labor Cost History when creating a final invoice and then printing that final

invoice directly (without using Pro Forma). The invoice header gets a correct invoice number in Display Invoices, but the

detail line in the Display Labor Cost History shows a "1."

If Pro Forma is created first and then finalized the correct invoice number is seen in both the Display Invoices and Display

Labor Cost History. We see this same situation for ALL cost types.

SOLUTION DESCRIPTION:

In session tppin4264m000 "Create Invoices" the final invoices are created in two steps. Step 1 creates invoice numbers for the

temporary invoice type 'Make final'. This temporary invoicenumber is updated in the cost history. After all temporary invoices

are created, then step 2 is done for creating the final invoices. During step 2 the final invoice numbers were not updated. This

is changed, now the final invoice numbers are updated in the cost history of the five costtypes.

NOTE: During the updating of the cost history, transactions with an old and wrong 'final invoicenumber' are updated with a

final invoicenumber of the last creation run. Because the temporary invoice numbers are use more then one time. For example,

all old transactions with a 'final invoicenumber' "1" are updated with the final invoicenumbers of the last invoice run.

Modifications in software components have been marked with DF531-1

SITUATION IDENTIFIED IN: tppin4264m000 "Create Invoices"

SITUATION DESCRIPTION:

The system gives the error message "Not allowed to mix up debit and credit lines" if an invoiceline is filled manually in an

invoice that is generated by the system with the session tppin4264m000.

In session tpprc0100m000. When debit- and credit transactiontype are not equal and the credit transactiontype contains more

then one serie it's not possible to select a serie.

In session tppin4264m000. When creating invoices and the status is "final" the series of the PRC parameters are selected and

not the series mentioned on the form.

SOLUTION DESCRIPTION:

When an invoice was created, the field Debit/Credit invoice (tppin100.dbcr) was not correctly filled. This results in the

errormessage during maintainance of invoice lines.

Selecting of series in tpprc0100m000 are correted.

When creating a final invoice the specified series on the form tppin4262m0001 are used.

Modifications in software components have been marked with DF12638-1

SITUATION IDENTIFIED IN: tppss6115m000 "Maintain Planned Warehouse Orders"

SITUATION DESCRIPTION:

If planned inventory is insufficient, the system gives an errormessage in dutch at the moment you filled the delivery data .

At the moment you give [E] of [W] to save this record the system gives almost the same message again but now in English.

SOLUTION DESCRIPTION:

Second message cannot be removed, but is translated into the correct languages now.

Modifications in software components have been marked with DF 12791

SITUATION IDENTIFIED IN: tppin4264m000 "Create Invoices"

SITUATION DESCRIPTION:

In some cases the system generate for each line to be invoiced a new invoice with one line. This has to do with vat code yes

or no.

In the case that the project customer has 'Tax' = 'No' and in the CMG parameters 'Calculate Tax on Advance

Payments/Receipts' = 'Yes',

every extension transaction causes a new invoice header.

SOLUTION DESCRIPTION:

The invoice lines for extensions are now collected on one invoice.

Modifications in software components have been marked with DF12729-1

SITUATION IDENTIFIED IN: tpbop3101m000 "Maintain estimate"

SITUATION DESCRIPTION:

After modifications of the standard program for the Baan Windows environment, the deleting of elementgroups will hang the

process if you use the delete options "CTRL V" a second time.

SOLUTION DESCRIPTION:

The handling of processes in the standard will be different. Now the activated process is killed after returning to the main

session.

Modifications in software components have been marked with DF 11399

SITUATION IDENTIFIED IN: tppdm7840m000 ( "Copy Project" )

SITUATION DESCRIPTION:

When a Project with an Actual Cost Calculation Code was copied to another Project this calculation was not linked to the

new Project any more.

SOLUTION DESCRIPTION:

The Actual Cost Calculation Code is now being linked to the new Project also.

Modifications in software components have been marked with DF 11928

SITUATION IDENTIFIED IN: tpppc2111m000 "Maintain Material Costs"

SITUATION DESCRIPTION:

When you approve an invoice in Finance you get to session tfacp1133s000 (Maintain Matched Purchase Invoice Transactions).

When you use a ledger account with integration to Project Costs you get to session tpppc2111m000 (Maintain Material Costs).

You can enter project and item. The system gives default a serial number. When you enter 3 lines or more with the same project

and item, the default value is not correctly given by the system. For line 3 the default serial number will be 2 instead of 3.

At the end an error message is given 'Record already exists', and the record gets erased. This problem can be avoided by

saving after each two lines, or manually adapting the serial number.

SOLUTION DESCRIPTION:

The procedure for checking and determining the serial number was changed for the different cost types. Now the system

generates the correct serial number.

Modifications in software components have been marked with DF12537

SITUATION IDENTIFIED IN: tpbop3155m000 "Maintain Summary Sheets"

SITUATION DESCRIPTION:

It is not possible to enter alphanumeric elementcodes .

SOLUTION DESCRIPTION:

In the form tpbop3155m0001, the displayformat is now linked to the domain and it is now possible to enter alphanumeric

elementcodes .

Modifications in software components have been marked with DF12886

SITUATION IDENTIFIED IN: tpppc4412m000 "Print Principal's Project Control Report"

tpppc4421m000 "Print Surveyor's Report"

SITUATION DESCRIPTION:

After installeing the solution 10981 this session will only give the message no data in within selection and there is no data

generated.

SOLUTION DESCRIPTION:

A selection was made with invalid conditions. This conditions are corrected.

Modifications in software components have been marked with DF12825-1

SITUATION IDENTIFIED IN: tpbop3416m000 "Print estimate recapitulation"

SITUATION DESCRIPTION:

In the column 'labor' the quantities are shown instead of amounts.

SOLUTION DESCRIPTION:

The labor column is now filled with labor-amounts instead of labor-hours

Modifications in software components have been marked with DF12859-1

SITUATION IDENTIFIED IN: tpppc4411m000 "Print Cost Control"

tpppc4421m000 "Print Surveyor's Report"

SITUATION DESCRIPTION:

When the page break coincides with a skip in the sort sequence , the system calculates the totals of the previous page into the

totals of the first record of the current page.

Because of this, the subtotals of the first records are too high (it is the total of the current record + the total of the last record

of the last page).

SOLUTION DESCRIPTION:

The first totals on the second or next pages are now calculated correctly.

Modifications in software components have been marked with DF12845-1

SITUATION IDENTIFIED IN: tpbop3101m000 "Maintain estimate"

SITUATION DESCRIPTION:

In form 5 of session tpbop3101m000; there are some detaillines.

Execute the following steps :

- esc (tpbop99m01)

- select block (tpbop99m02)

- select buffermenu (tpbop99m10)

- select Estimate

- Maintain Estimate Sequence No (tpbop3121s000) to select an estimate.

- Display Estimate Structure (tpbop3110) to select elements with the mouse

Now it is not possible to select elements with the mouse, to copy that element to the original estimate.

SOLUTION DESCRIPTION:

Selecting elements with the mouse for copying to the original estimate is now possible.

Modifications in software components have been marked with DF12786

SITUATION IDENTIFIED IN: tppin4155m000 "Maintain advances to be invoiced"

SITUATION DESCRIPTION:

If the field "Invoice" in the session tppin4155m000 is set to "Yes" for an advance, the system deletes the link with the

installment. This happens only if the advance is confirmed by the session tppin4155m000. If you use the session tppin4150m000

for this, the system doesn't delete the link.

SOLUTION DESCRIPTION:

The link tbetween advance and installment is now updated correctly.

Modifications in software components have been marked with DF12810-1

SITUATION IDENTIFIED IN: tpptc1230m000 "Generate Control Data"

SITUATION DESCRIPTION:

If you choose for a project the value "Activity budget" at the field " Budget Type Project control" it is possible to give "No"

at the field "Cost Control" for all the linked elements (also for the TOP element). In that case it is possible to generate

planned purchase orders for the budgetlines that are linked to an element with the field "Cost control" on "No" (the system

gives no message if you run tpptc1230m000 because the setting of the field "Budget Type Project Control" is "Activity

budget").

If you confirm this planned order manually the system gives an errormessage but if you do this by the session tppss6225m000

the system accepts this planned order. This is inconsistent!!

It is also possible to link revenues for extensions to the TOP element (with the indicator "Cost control" on "No"). That means

you will not see this data in the cost control anymore at the level of element. This leads to differences in the costcontrol by

activities and elements.

So it works not correct if the field "Budget Type Project Costs" is filled with "Activity" and the field "Cost control" for the

Top element has the value "No".

SOLUTION DESCRIPTION:

The indicator Cost Control of the top element is always set to Yes now, because the top element was always shown in the

Project Monitoring.

For example: the top element is always printed in the print session tpppc4411m000 "Print Cost Control".

Modifications in software components have been marked with DF12698.

SITUATION IDENTIFIED IN: tpbop3150s000 "Maintain calculation sheet"

SITUATION DESCRIPTION:

Wrong calculation of formula's.

SOLUTION DESCRIPTION:

The compilation of formula's is made depended on counter of used fields in formula.

Modifications in software components have been marked with DF12965-1

SITUATION IDENTIFIED IN: Maintain Item Data (tiitm0101m000)

Maintain Item Data (tppdm0110m000)

SITUATION DESCRIPTION:

The message "Fixed ord qty and order qty multiple of do not correspond" (tiitms0018) was displayed incorrectly .

SOLUTION DESCRIPTION:

The appearance of the message "Fixed ord qty and 'order qty multiple of' do not match" (tiitms0018) had to do with the

wrong rounding of the doubles. This problem is solved now.

Modifications in software components are marked by DF 12800-1.

SITUATION IDENTIFIED IN: tpbop3155m000 "Maintain Summary Sheet"

SITUATION DESCRIPTION:

"Unkown symbol 'OUND' in expression: value 0 assumed".

SOLUTION DESCRIPTION:

During inserting or deleting of a column in a spreadsheet all formulas are checked again. The system took the 'R' of round for

the indication of 'row'.

Modifications in software components have been marked with DF12976-1

SITUATION IDENTIFIED IN: tpbop3150s000 "Maintain Spreadsheet"

SITUATION DESCRIPTION:

In the summary sheet you can give input on code. If selected code is 200 (items, Material) you can zoom to select an

itemcode.

But then always the error message "Item must be purchased or manufactured" appears. This is not correct.

SOLUTION DESCRIPTION:

Errormessage now only appears when applicable.

Modifications in software components have been marked with DF13014-1

SITUATION IDENTIFIED IN: tpbop3521m000 "Mark Estimate Structure"

SITUATION DESCRIPTION:

Session tpbop3521s000 starts su-sessions twice in the asci-mode

SOLUTION DESCRIPTION:

Problem is now solved by correcting the soultion of ID 10243104. The source was marked as old, but was not removed by

Pipe-sign's.

Modifications in software components have been marked with ID 10243104

SITUATION IDENTIFIED IN: tpptc1111m000 "Maintain element budget"

tpptc2111m000 "Maintain activity budget"

SITUATION DESCRIPTION:

When the unit code for labor time in session tppdm0100m000 (Maintain general parameters) is on "day" instead of "Hrs" ,

transferring an estimate to a budget can result in incorrect values for quantities in the budget.

This happens for detail lines with a unit code of type "time" .

In this case the conversion of the different time units and the norm entered for the labor code is wrong and it results in a

wrong value for the quantity in the budget.

SOLUTION DESCRIPTION:

There was already a defect for this problem (DF10673). In addition to the modifications marked with 10673-1 there are now

modifications made to solve the same problem but for the activities. The modifications are marked with 10673-2. The

solution 10429 is now obsolete and the solution 12049 is the replacement.

Modifications in software components have been marked with DF 10673-1

DF 10673-2