td3.1_b, td3.1_b1, td3.1_b2

td3.1L_b_glo0, td3.1L_b1_glo0, td3.1L_b2_glo0

td3.1L_b_jit0, td3.1L_b1_jit0, td3.1L_b2_jit0

td3.1L_b_nl10, td3.1L_b1_nl10, td3.1L_b2_nl10

tdB40_b, tdB40_b1, tdB40_b2, tdB40_b3

tdB40L_b_glo0, tdB40L_b1_glo0, tdB40L_b2_glo0, tdB40L_b3_glo0

tdB40L_b_gls0, tdB40L_b1_gls0, tdB40L_b2_gls0, tdB40L_b3_gls0

tdB40L_b_nl10, tdB40L_b1_nl10, tdB40L_b2_nl10, tdB40L_b3_nl10

tdB40L_b_sch0, tdB40L_b1_sch0, tdB40L_b2_sch0, tdB40L_b3_sch0

ti3.1_b, ti3.1_b1, ti3.1_b2

ti3.1L_b_glo0, ti3.1L_b1_glo0, ti3.1L_b2_glo0

ti3.1L_b_jit0, ti3.1L_b1_jit0, ti3.1L_b2_jit0

ti3.1L_b_nl10, ti3.1L_b1_nl10, ti3.1L_b2_nl10

tiB40_b, tiB40_b1, tiB40_b2, tiB40_b3

tiB40L_b_glo0, tiB40L_b1_glo0, tiB40L_b2_glo0, tiB40L_b3_glo0

tiB40L_b_gls0, tiB40L_b1_gls0, tiB40L_b2_gls0, tiB40L_b3_gls0

tiB40L_b_nl10, tiB40L_b1_nl10, tiB40L_b2_nl10, tiB40L_b3_nl10

tiB40L_b_sch0, tiB40L_b1_sch0, tiB40L_b2_sch0, tiB40L_b3_sch0

SITUATION IDENTIFIED IN: Maintain Sales Order Lines (tdsls4102s000)

SITUATION DESCRIPTION:

If a product variant (already configured) is reconfigured using the session "Generate Product Variant Structure for Project"

from the menu, and if the sales price as per generic option changes, it was not reflected in the sales order line. This is done

by zooming from the choice field of sales order lines.

SOLUTION DESCRIPTION:

If a zoom is performed from the choice to run re-configure, the correct sales price and amount will be displayed in the sales

order line.

This solution solves defect 417

cpB40_b, cpB40_b1, cpB40_b2, cpB40_b3

cpB40L_b_glo0, cpB40L_b1_glo0, cpB40L_b2_glo0, cpB40L_b3_glo0

cpB40L_b_gls0, cpB40L_b1_gls0, cpB40L_b2_gls0, cpB40L_b3_gls0

cpB40L_b_nl10, cpB40L_b1_nl10, cpB40L_b2_nl10, cpB40L_b3_nl10

cpB40L_b_sch0, cpB40L_b1_sch0, cpB40L_b2_sch0, cpB40L_b3_sch0

tiB40_b, tiB40_b1, tiB40_b2, tiB40_b3

tiB40L_b_glo0, tiB40L_b1_glo0, tiB40L_b2_glo0, tiB40L_b3_glo0

tiB40L_b_gls0, tiB40L_b1_gls0, tiB40L_b2_gls0, tiB40L_b3_gls0

tiB40L_b_nl10, tiB40L_b1_nl10, tiB40L_b2_nl10, tiB40L_b3_nl10

tiB40L_b_sch0, tiB40L_b1_sch0, tiB40L_b2_sch0, tiB40L_b3_sch0

SITUATION IDENTIFIED IN: Display Item Planning (cprmp2501s000)

SITUATION DESCRIPTION:

When zooming from sales order lines to the session 'Display MPS' (in the case of stock shortage), timps3501 starts up an

IRP session (cprmp2501s000) when IRP is implemented. When zooming to this session item/container data is not set

correctly when looking up MPS data. The item for which an MPS is displayed is not the same item as recorded in the sales

order lines. After returning to the order lines, the message 'Actual MPS for item <x> not defined in company <xxx>'. This is

not correct in this case, as the MPS is present.

SOLUTION DESCRIPTION:

The Item planning will now be displayed for the appropriate plan item/container. This will be done for the Actual MPS plan

code set in IRP parameters. If no item planning exists for the actual plan code/plan item, then no data will be displayed in

the item planning session.

The message "Actual MPS for item <x> not defined in company <xxx>" will appear if no MPS exists for the actual plan code

and the plan item in consideration. The most important thing to know is the actual plan code is used to display all the

schedules and the planning.

This solution solves defect 514.

tiB40_a, tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Calculate Cost Prices (ticpr2210m000)

SITUATION DESCRIPTION:

If a manufactured item does not contain any cost price data, the zero cost price is not updated in all tables (ticpr200) and

therefore causes problems in finance integrations.

SOLUTION DESCRIPTION:

The appropriate tables (ticpr200) will now be updated even if no cost price data exists for the manufactured item.

This solution solves defect 542

tiB40_a, tiB40_a1, tiB40_a2

tiB40L_a_glo0, tiB40L_a1_glo0, tiB40L_a2_glo0

tiB40L_a_gls0, tiB40L_a1_gls0, tiB40L_a2_gls0

tiB40L_a_sch0, tiB40L_a1_sch0, tiB40L_a2_sch0

tiB40_b, tiB40_b1, tiB40_b2, tiB40_b3

tiB40L_b_glo0, tiB40L_b1_glo0, tiB40L_b2_glo0, tiB40L_b3_glo0

tiB40L_b_gls0, tiB40L_b1_gls0, tiB40L_b2_gls0, tiB40L_b3_gls0

tiB40L_b_nl10, tiB40L_b1_nl10, tiB40L_b2_nl10, tiB40L_b3_nl10

tiB40L_b_sch0, tiB40L_b1_sch0, tiB40L_b2_sch0, tiB40L_b3_sch0

SITUATION IDENTIFIED IN: Transfer Planned MRP Production Orders (timrp1250m000)

SITUATION DESCRIPTION:

When transferring multiple planned MRP production orders with an item group the same as the immediately previous one,

the default production data specified in "Maintain Production Data by Item Group" (tisfc1100m000) was not used.

SOLUTION DESCRIPTION:

For every transferred planned MRP production order, the default production data specified in "Maintain Production Data

by Item Group" (tisfc1100m000) is now used.

This solution solves defect 553.

tiB40.

SITUATION IDENTIFIED IN:

Maintain Production Orders (tisfc0101m000).

SITUATION DESCRIPTION:

When SFC Parameter "Automatic Update of Production Order Dates" is set to "yes" and a production order is rescheduled-in,

then the uncompleted operations are rescheduled and the order delivery date is set to match the operation with the latest

finish date - even if it has already completed.

SOLUTION DESCRIPTION:

When production orders are rescheduled-in, only uncompleted operations are considered for the recalculation of the new

delivery date. This solution solves defect 554.

tiB40_b, ti B40_c

SITUATION IDENTIFIED IN: Maintain ECOs (tiedm3110m000)

SITUATION DESCRIPTION:

With E-Items by ECO not deleted while setting the status of the ECO to free, it is not allowed to release the ECO again when

the check is done to verify if the E-items by ECO are eligible as per the current ECO lines.

The situation identified for Automatic EBOM generation, Applicable to all lines, Include and Delete Items.

SOLUTION DESCRIPTION:

It will be possible to release an ECO (with existing E-items by ECO) provided all the ECO lines fulfill the condition that

each component (set to be deleted in ECO lines) be present in the EBOM.

This solution solves defect 527.

ti3.1_b, ti3.1_b1, ti3.1_b2

ti3.1L_b_glo0, ti3.1L_b1_glo0, ti3.1L_b2_glo0

ti3.1L_b_jit0, ti3.1L_b1_jit0, ti3.1L_b2_jit0

ti3.1L_b_nl10, ti3.1L_b1_nl10, ti3.1L_b2_nl10

tiB40_a, tiB40_a1, tiB40_a2

tiB40L_a_glo0, tiB40L_a1_glo0, tiB40L_a2_glo0

tiB40L_a_gls0, tiB40L_a1_gls0, tiB40L_a2_gls0

tiB40L_a_sch0, tiB40L_a1_sch0, tiB40L_a2_sch0

tiB40_b, tiB40_b1, tiB40_b2, tiB40_b3

tiB40L_b_glo0, tiB40L_b1_glo0, tiB40L_b2_glo0, tiB40L_b3_glo0

tiB40L_b_gls0, tiB40L_b1_gls0, tiB40L_b2_gls0, tiB40L_b3_gls0

tiB40L_b_nl10, tiB40L_b1_nl10, tiB40L_b2_nl10, tiB40L_b3_nl10

tiB40L_b_sch0, tiB40L_b1_sch0, tiB40L_b2_sch0, tiB40L_b3_sch0

SITUATION IDENTIFIED IN: Maintain Production Orders (tisfc0101m000)

SITUATION DESCRIPTION:

Calculating the delivery date or production date by pressing Ctrl-R (or Ctrl-Shift-R, depending on the user interface)

while maintaining a production order in "Maintain Production Orders" (tisfc0101m000) when there was no routing did not

work. This was observed by incorrect dates which did not consider the order lead time of the item.

SOLUTION DESCRIPTION:

When maintaining a production order with no routing, the system now uses the item's order lead time (but not the safety

time) when calculating the delivery date (when forward planning) or production date (when backward planning) after the user

presses Ctrl-R (or Ctrl-Shift-R, depending on the user interface).

This solution solves defect 12107.

tiB40_a, tiB40_a1, tiB40_a2

tiB40_b, tiB40_b1, tiB40_b2, tiB40_b3

SITUATION IDENTIFIED IN: Calculate Cost Prices (ticpr2210m000)

SITUATION DESCRIPTION:

Costs were not always being computed correctly when surcharges based on item groups were modified.

SOLUTION DESCRIPTION:

Costs are now correctly computed when surcharges based on item groups are modified.

This solution solves defect 654

tiB40_b, tiB40_c,

tsB40_b,tsB40_c

tpB40_b, tpB40_c

tcB40_b,tcB40_c

psB40_b, psB40_c

SITUATION IDENTIFIED IN: Maintain Engineering Item Revisions (tiedm1101m000)

SITUATION DESCRIPTION:

(Reported for NT Backoffice build 15.8)

When using the session "maintain engineering item revisions" ( tiedm1101m000), and trying to launch a drawing, it gives

the following message:

" ttstpvtemul.

Shell functionality not supported by Windows NT"

SOLUTION DESCRIPTION:

It will now be possible to display the drawing attached to an engineering item revision by clicking the button "Drawing" or

using <Shift><Ctrl><D>.

The drawing file name will be read from the above session (tiedm1101m000) in form 3.

This file should exist in the directory as mentioned in the session "Maintain EDM Parameters" (tiedm0100m000) in the

field 'Directory Name for Drawing". Furthermore, the field "Display Drawing" indicates which application program should

be used to display the drawing.

In BW mode, this application must exist on the client. The name of the application should be the executable name and

should be in the PATH.

Note:

1.) It is required to have a /temp directory on the client since the application puts the file in this temporary directory for

reading and keeps it there.

2.) For this solution, it is required to have the DLL "ottdllbw" in the $BSE/tools/{...} directory. Please check if this

exists on your system and if not, contact the the support center.

This solution solves defect 365

tiB40_c

SITUATION IDENTIFIED IN: Maintain Production BOM's (tibom1110m000)

SITUATION DESCRIPTION:

The help text for the 'lead time offset' field in "Maintain Production BOM's" is in French for the English version of session

in Baan IV c.

SOLUTION DESCRIPTION:

The help text for the 'lead time offset' field in "Maintain Production Orders (tibom1110m000)" has been correctly translated

for Baan IV c1. Pick up the solution patch listed below for the correct help text.

This solution solves defect 16670

SITUATION IDENTIFIED IN: Maintain Item Data (GRT) ( tigrt1180s000).

SITUATION DESCRIPTION:

When classifying an item and creating the help text for that item, the search keys are not filled in the session "Print Texts"

(tttxt1400s000).

SOLUTION DESCRIPTION:

The search keys are now properly filled when the item help text will be created.

Modifications in software components are marked with DF 11624-1.

SESSION ERROR IDENTIFIED IN: tihra1210m000.

PROBLEM TEXT:

The help about the PCS/Operation Costs combination doesn't say that customer can be used as a dimension.

Therefore ID 10023257 should be canceled.

SOLUTION DESCRIPTION:

The ID 10023257 has been removed.

Modifications in software components are marked with DF 11670-1.

SESSION ERROR IDENTIFIED IN: "Maintain Production Bill of Material " ( tibom1110m000 ).

PROBLEM TEXT:

When copying a BOM-item ( using select and then "Ctrl-Shift-C" ) and inserting it on a position that already exists, the

program places the item at a new position but copies the last occurence

instead of the selected one.

SOLUTION DESCRIPTION:

The ID 10221738 has been removed, because this is solved by the Standard program.

Modifications in software components are marked with DF 11678-1.

SESSION ERROR IDENTIFIED IN: tipcs5250m000.

OTHER SESSIONS: tipcs5210m000, tipcs5220m000, tipcs5230m000, tipcs5270m000.

PROBLEM TEXT:

Selection by planner gives also error messages for other planners (transfer prp).

When selecting a plannercode while transferring prp orders thy system gives errormessages for items that have a different

plannercodes.

(The solution of ID 10224656 is not satisfying enough, because all the limit checks should be done first and after that status

checks etc.

Furthermore, after that the complete solution must also be build in into the other PCS scripts if applicable

(PCS5210/52**).)

SOLUTION DESCRIPTION:

As item type in customised item data was being checked before planner therefore the error message was displayed.

(The ID 10224656 has been removed)

Modifications in software components are marked with DF 11686-1.

SITUATION IDENTIFIED IN: Update Order Lead Times (tirou2212m000)

SITUATION DESCRIPTION:

When Update Order Lead Times session is run it is not including the wait time of the last operation in the process route

(regardless of any operation overlap on the operation).

SOLUTION DESCRIPTION:

When there is no overlap on the final operation of the process route then the wait time at the work centre will included in

the calculation of the overall order lead time. This solution solves Badfix of ID 10016501.

All modifications are been marked with DF139

tiB40_b4, tiB40_c1

SITUATION IDENTIFIED IN:

tipcs3462m000 "Print Actual Costs By Project"

SITUATION DESCRIPTION:

"Print Actual Costs By Project" report (tipcs3462m000) shows a wrong 'Grand Total Of Project Costs For Project' when a

Service Order with order lines is linked to a (active) project.

If materials recorded for a service order in session "Maintain Actual Service Order Costs and Revenues" (tssma3110s000) have

been recorded in the order lines, but not issued (or generated and released when ILC = 'ON'), they appear on the "Actual Cost

Price by Project" report (tipcs3462m000) as line-item values, but not in the Grand Total value (=0,00). At this point, the

Grand Total is correct, but the line-item values shouldn't appear because those materials haven't been issued (or released in

case of ILC) yet.

After issuing (or releasing (in case of ILC)) the materials on the service order, the line-item values are correct and the

Grand Total is not correct anymore on the report of session (tipcs3462m000) "Print Actual Costs By Projects.

SOLUTION DESCRIPTION:

The function "Determine.service.order.status()" is improved. Now the lines don't appear on the report when they are not issued

(or released) while the Grand Total is still correct. But after issueing (or releasing) the service order lines will appear on

the report "Print Actual Costs by Project" (tipcs3462m000) and the Grand Total will be calculated and displayed correctly.

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

SESSION ERROR IDENTIFIED IN: tisfc0101m000.

OTHER SESSIONS:

PROBLEM TEXT:

ID 10228366 must be removed, because the user should decide whether the effective date should be overwritten with the

E-item revision's effective date. Therefore a question must be added which asks the user whether or not to overwrite.

SOLUTION DESCRIPTION:

The ID 10228366 has been removed.

Question added.

Modifications in software components are marked with DF 11758-1.

SESSION ERROR IDENTIFIED IN: tibom1413m000 Print Where-Used PBOM Components (Multi-Level)

PROBLEM TEXT:

If there are more than 9 level items in the PBOM, the level number disappears in the "WHERE USED OF PBOM

COMPONENTS (MULTI-LEVEL)" report.

SOLUTION DESCRIPTION:

Domain of report field 'slevel' changed from tcmcs.str8m to tcmcs.str20m. Now user can see upto 20 level Items.

All modifications has been marked with DF11582-1

SESSION ERROR IDENTIFIED IN: tirou1101m000 Maintain Routing Codes by Item(Incl. RPT Data)

PROBLEM TEXT:

Using a standard routing for RPT part. In session tirou1101m00, the system does not allow anything to be entered under the

field Scheduling Area when using a standard routing, because it has been defined when the standard routing was defined. But

it does not update the Scheduling Area field with the value defined in the standard routing.

Solution will be available in the next patch (B40_b4) / release (B40_c)

SOLUTION DESCRIPTION:

Scheduling area has been read for a RPT Item with Standard Routing and displayed.

This solution solves defect 344

For version B40_a see solution 11825.

tp3.1_b, tp3.1_b1, tp3.1_b2, tpB40_b, tpB40_b1, tpB40_b2, tpB40_b3, ti3.1_b, ti3.1_b1, ti3.1_b2, tiB40_b, tiB40_b1,

tiB40_b2, tiB40_b3

SITUATION IDENTIFIED IN: Maintain Planning Board for Project Plan ( tppss2100m000 )

Maintain Planning Board for Execution Plan ( tppss4100m000)

Maintain Activities Using Graphical Planning Board ( tipcs4170m000)

Maintain Production Planning by Graphical Planning Booard ( tisfc1120m000)

SITUATION DESCRIPTION:

When the projectplan has been set to the plan time unit "Day" in tppss0110m000 the header in the planningboard in

tppss2100m000 is not displayed right.

In tppss0130m000 weeks have been defined as follows:

... week 52 1996, week 1 1997, week 2 1997, ...

However, in the planboard in tppss2100m000 the system displays week 53 of 1996 followed by week 2 of 1997 which is

not conform the company calender.

SOLUTION DESCRIPTION:

Determining of the weeknumber has been adjusted. Now, it works fine for the last and first week of the year.

Modifications in software components have been marked with DF 11038.

SESSION ERROR IDENTIFIED IN: ticst0105s000 "Post Purchase Receipts to Work-in-Process"

OTHER SESSIONS:

PROBLEM TEXT:

The field Quantity Remaining in session ticst0105s000 is not calculated correctly. Besides, the calculation of the default value

of the field Issue is not really user friendly.

SOLUTION DESCRIPTION:

Now the calculation of the field Remaining Quantity is done immediately after a change is made which affects the value of

the Remaining Quantity. The calculation of the default value of the field Issue has been improved.

Some QMS functionality was copied from cst0101.

SITUATION IDENTIFIED IN: "Display Planned Production Orders/Batches", (ticrp0501m000).

SITUATION DESCRIPTION:

Independent of your choice at the field Order Type, the zoom on Order always shows the zoom to MRP Production Orders.

SOLUTION DESCRIPTION:

The values of the kind of order are now restricted to MRP and MPS Production Orders. Based on the kind

of order selected, the zoom displays MRP/MPS Production Orders.

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

SITUATION IDENTIFIED IN: "Print Order Documents", (tisfc0408m000)

SITUATION DESCRIPTION:

There are no labels present in Header 2 of report tisfc040804000. In Baan 4b they are still present.

SOLUTION DESCRIPTION:

The labels have now been included in report tisfc040804000.

SITUATION IDENTIFIED IN: Calculate Cost Prices by Project (tipcs3250m000)

SITUATION DESCRIPTION:

This defect is related to ID 10242867 (Olympus). Rounding of amounts is still not correct.

SOLUTION DESCRIPTION:

Now rounding of variables is done as early as possible.

This solution solves defect 11941

SITUATION IDENTIFIED IN: Cancel Production Orders ( tisfc0203m000)

SITUATION DESCRIPTION:

In DLL tisfcdll0220 of B40_a2 the variable cancel.order is declared as external (done with ID 10224222).

This is not allowed in an DLL.

In VRCs B40_b4 and B40_c1 ID 10224222 is canceled by ID 10229841.

ID 10229841 should also be built in into tisfcdll0220 of B40_a2 to cancel ID 10224222.

Also remove the declaration of the external variable "cancel.order" in tisfcdll0220 of B40_a2, B40_b4 and B40_c1,

because this variable is not used anymore in those DLLs.

SOLUTION DESCRIPTION:

The solution has been built into the tiB40_a2 version and the declaration of the external variable in the tiB40_b4 and ti

B40_c1 has been removed. All modifications are marked with DF11831-1.

SITUATION IDENTIFIED IN: many sessions

SITUATION DESCRIPTION:

Field ticpr010.cref on reports and forms was not long enough because of multi-byte versions. Extension of call 10230259.

SOLUTION DESCRIPTION:

Field ticpr010.cref on reports and forms adjusted to length 4.

This solution solves defect 12000

SITUATION IDENTIFIED IN: Close Projects (tipcs2250m000)

SITUATION DESCRIPTION:

It is possible to close a project when the status of the salesorder is "print sales invoices"

SOLUTION DESCRIPTION:

The sales order lines were not being checked before closing a report.

SITUATION IDENTIFIED IN : Maintain Item Data (tiitm0101m000)

SITUATION DESCRIPTION :

Session tiitm0110m000 & tiitm0101m000. Item group defaults, commission and rebate groups, do not carry over onto the

items.

SOLUTION DESCRIPTION :

Modification made to the include itiitm0002. Commission and Rebate Groups are now copied to tiitm001 from

tiitm002. Solution will come available in the nearest patch B40_b4. Modifications are marked wilt DF 506

SITUATION IDENTIFIED IN: Print Order Documents (Direct) (tisfc0408s000)

SITUATION DESCRIPTION:

The solution of ID 10242026 (Olympus) was superfluous, so it has to be removed.

SOLUTION DESCRIPTION:

Solution of 10242026 removed.

This solution solves defect 12031.

SITUATION IDENTIFIED IN: Report Production Orders Completed. ( tisfc0202m000)

SITUATION DESCRIPTION:

If the quantity reported complete is higher then the planned quantity of the production order, the quantity in the current

planning is raised to the quantity reported complete. In common situations this is ok, but it also happens when you make a

typing error. This can be corrected, but a decrease of the quantity reported complete does not trigger a decrease of the

quantity in the current planning. This is ok to in most situations, but if you have long lasting production orders with

expensive components you cannot correct the allocations.

SOLUTION DESCRIPTION:

A warning message would appear if the customer enters a value for Quantity to deliver higher than the Ordered

Quantity and is given an option to correct the input value.The solution is with DF ID 11991-1.

SITUATION IDENTIFIED IN : Maintain Reference Designators (tibom0120m000)

SITUATION DESCRIPTION :

The selectdo with 'break' is redundant in tibom0120. Same for 'selectempty' since a reference

always exist to itm001 for BOM-Items.

SOLUTION DESCRIPTION :

SQL improved.

This solution solves defect 12052.

SITUATION IDENTIFIED IN : Maintain Plan Items (timps2101m000)

SITUATION DESCRIPTION:

Cannot search by search key. The same problem exists in session timps2502s000. In both of these sessions, the search key is

defined.

Cannot search for items in master production scheduling sessions by anything other than item code.

SOLUTION DESCRIPTION:

In the forms of the sessions, the Standard Option "Change Order" was not set. It has now been set.

tiB40_b, tiB40_c1

SITUATION IDENTIFIED IN: Calculate Cost Price (ticpr2210m000)

SITUATION DESCRIPTION:

- When updating the costprice by using session calculate cost price (ticpr2210m000), the surchage for a item will not be

deleted if you recalculate. This situation occurs when you recalculate a item with surcharges which have been removed

before recalculating.

- It is possible to calculate a costprice of zero for a manufactured item, this is not correct.

SOLUTION DESCRIPTION:

- When recalculating the costprice within session ticpr2210m000 "Calculate Cost Price" and a surcharge have been removed,

the system will delete this surcharge before recalculating.

- When calculating a costprice of zero for a manufactured item then the system will not update the costprice and will present

a warning.

solution solves defect 12080.

SITUATION IDENTIFIED IN: Transfer Planned MRP Production Orders (timrp1250m000)

SITUATION DESCRIPTION:

Caused by ID 10242405. No need to do another db.eq on timrp020 in timrpdll0002.

For version B40_a use solution 12631

SOLUTION DESCRIPTION:

Solution of 10242405 removed.

This solution solves defect 12119

tiB40a, tiB40b.

SITUATION IDENTIFIED IN:

Transfer Planned PRP purchase Orders (tipcs5260m000).

SITUATION DESCRIPTION:

Text added to a planned PRP purchase order became footer text after the order had been transferred.

SOLUTION DESCRIPTION:

Text added to a planned PRP purchases order now becomes line text, when the order is transferred.

SITUATION IDENTIFIED IN: Maintain Customized Items (tipcs2121m000)

Calculate Cost Prices by Project (tipcs3250m000)

SITUATION DESCRIPTION:

Price may never be rounded according to extra rounding of valuta.

SOLUTION DESCRIPTION:

Program scripts tipcs2121 and tipcs3250 modified.

This solution solves defect DF 12137.

VERSIONS: tiB40_c_sys9, tiB40_c1

SITUATION IDENTIFIED IN: Maintain Estimated Materials by Production Order (tisfc0110m000)

Enter Material Issue for Production Orders (ticst0101m000)

SITUATION DESCRIPTION:

The functionality of QMS in combination with backflushing has to be removed.

It has been decided to forbid the combination of backflushing and inspection orders because it is not logical to backflush if

items have to be inspected first.

SOLUTION DESCRIPTION:

All checks on QMS in tisfcdll.0225 have been removed.

It is now not possible to create an inspection order if the line is a backflushing line.

The backflushing flag is not allowed to be changed from "no to "yes"

SITUATION IDENTIFIED IN: Generate Network Planning (tipcs4210m000)

SITUATION DESCRIPTION:

The generation of network planning for multiple projects was going wrong sometimes. With the last activity in the project

being planned at the start of the project and not the end.

SOLUTION DESCRIPTION:

Because an internal table was not being cleared properly in session " Generate Network Planning" (tipcs4210m000) an error

could occur when the number of activities in the current project (being planned) was less than the number of the activities in

the previously planned project in the range. This resulted in the last activies of the current project being planning

incorrectly. The internal table is now cleared properly. In B40_a2 it is backported because of the performance

improvement.

This solution solves defect 12035-1.

ti3.1_b, tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Report Production Order Completed(tisfc0202m000)

SITUATION DESCRIPTION:

It is possible to put a production order on completed in session Report Production Order Completed "tisfc0202m000" when

total quantity completed is bigger then quantity completed on last operation.

The original problem only occurred in case the field tisfc001.rpsd (Partial Deliveries) was on Yes.

SOLUTION DESCRIPTION:

It is not possible to put a production order on completed in session Report Production Order Completed "tisfc0202m000"

when total quantity completed is bigger then quantity completed on last operation.

This solution solves defect 12188-1 and 12188-2

tiB40_c1

SITUATION IDENTIFIED IN: Maintain Activity Relationship (tipcs4110m000)

SITUATION DESCRIPTION:

In session "Maintain Activity Relationship" (tipcs4110m000) the Popup Help of the Relation Type (tipcs.korl) is not

correct.

The explanation in this Popup Help of the Relation Type EE (End-End) is not correct. It says: "The next activity and the

preceding activity must end simultaneously".

But the program works not like that, so the description must be: "The successor cannot finish unless the predecessor has

finished"

AND the same for Relation Type SS (Start-Start). It now says: "The next activity and the preceding activity must start

simultaneously" and it has

to be : "The successor cannot start unless the predecessor has started".

SOLUTION DESCRIPTION:

The Form Field help (FFpcs4110m0001tipcs410.korl) has been modified. The explanation in this Popup Help of the

Relation Type EE (End-End) is changed from:

"The next activity and the preceding activity must end simultaneously" to: "The next activity cannot finish unless the

predecessor has finished"

AND for Relation Type SS (Start-Start) changed the Pop up help from: "The next activity and the preceding activity must

start simultaneously" to:

"The next activity cannot start unless the predecessor has started".

This solution solves defect 12215

Modifications in the help text have been marked with DF 12215-1

SESSION ERROR IDENTIFIED IN: Print Order Documents (tisfc0408m000)

PROBLEM DESCRIPTION:

DF 11802-1 tackles the problem with Operation Notes printed till a certain date, filled in the session (tisfc0408m000)

'Print Order Documents'. A solution was made. This solution works fine. However:

The same problem as with the Operation Notes occurs with the Material Issue Notes. The same change has to be made for the

material issue note.

For production orders bridging the " to Production Date " not all the Material Issue Notes are printed. This is incorrect

because once any of the Material Issue Notes have been printed the " originals printed " flag on the production order header is

set to true.

The same problem occurs with the Subcontracting Notes also, so this must be corrected the same way as the Material Issue

Notes.

SOLUTION DESCRIPTION:

For each production order with a planned start date before or equal to the " to Production Date " all the Material

Issue Notes AND SUBCONTRACTING NOTES will be printed.

Modifications in software components are identified with DF 12156-1

SITUATION IDENTIFIED IN: Generate Project Structure for Sales Orders(tipcs2240m000)

SITUATION DESCRIPTION:

When generating a projectstructure (tipcs2240m000) for a salesorder the actual revision is not shown.

When copying a revision controlled item, then when a relationship is created in table tiedm101 the field item copied must be

set to yes. Also if it is a manufactured item the field Ebom copied must be set to Yes.

When fields are set to yes, also the date fields must be set.

SOLUTION DESCRIPTION:

When copying a revision controlled item, then while inserting a relation in table tiedm101, the field item copied set to Yes,

also if it is a manufactured item e-bom copied set to Yes. Because the field Item copied is set to Yes, date fields are set to

current date. E-bom copied date set to current date only when e-bom copied field set to Yes.

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

SITUATION IDENTIFIED IN: timps3101m000 "Maintain Master Production Schedule"

SITUATION DESCRIPTION:

When there is actual receipt within the Planned Receipt Consumption region which is not jet consumed. Then when

generating MPS, Planned Receipts are calculated with actual inventory which results in to low planned receipts.

SOLUTION DESCRIPTION:

Software changed so correct Planned Receipts are generated.

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

tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Print Machine Utilization by Day (ticrp0407m000)

SITUATION DESCRIPTION:

The number of options for 'Order Type' was limited to 2 options and needed to be extended with 2 batch-options as

requested.

SOLUTION DESCRIPTION:

This solution solves defect 12282 with MPS- and MRP-Batch Orders.

the new modifications are marked with 12282-2.

SITUATION IDENTIFIED IN: timps3201m000 "Generate Master Production Schedule"

SITUATION DESCRIPTION:

While running a total MPS run the system gives error index 1001 out of dimensions (1) 1000. This error does not come

every time when running this session.

SOLUTION DESCRIPTION:

An internal array was not being extended when all its allocated memory had been consumed. The array is now dynamic and

when all allocated memory has been used the array will be allocated more memory.

This solution solves defect 12024

SITUATION IDENTIFIED IN: Print Sales Price Structure by Product Variant ( tipcf5430m000 )

SITUATION DESCRIPTION:

In the session tipcf4101m000 (Maintain Generic Price Lists) a number of lines have been given input. Each line has it's own

textline, entered via Text manager. When in session tipcf5430m000 (Print Sales Price Structure by Product Variant) the price

structure is printed, all the lines of this report have the same text. This text is the text of the last line in the report.

SOLUTION DESCRIPTION:

Session "Calculate Product Variant Selling Price Structure" (tipcf5230m000 ) is changed and is now correctly

(re-)initializing the Text number for subsequent lines. This means that now the correct Text numbers are copied to the Sales

price structure lines. Also a warning message is now given when the user has no default Text group defined.

Also fixed potential problem with "ERR 2" ( = No such file or directory ) when calculating Sales price structure (

tipcf5230m000 ).

Modifications in tipcf5230m000 and function tipcf0500.h are marked with DF 12245-1.

SITUATION IDENTIFIED IN : Close Projects Session ( tipcs2250m000 )

SITUATION DESCRIPTION:

It is possible to close a project when the status of the salesorder is "print sales invoices"

Problem not solved, solution 10973 is a bad fix. See defect 11970

SOLUTION DESCRIPTION:

An extra select has been added and the situation has been corrected and it does not repeat.

SITUATION IDENTIFIED IN: Process Hours Accounting (tihra1210m000)

SITUATION DESCRIPTION:

When ILC is on and tisfc000.isgo=NO donot start the ILC sessions. This takes unnecessary time. (Could happen in more

sessions which start backflushing)

SOLUTION DESCRIPTION:

Use of ILC sessions made conditioned on Backflush Goods on Outbound Priority when using ILC (tisfc000.isgo).

Also OK button removed from form tisfc0202s0001.

This solution solves defect DF 12219.

SITUATION IDENTIFIED IN: Data Selection for Planning Board (tipcs4171m000)

SITUATION DESCRIPTION:

When you close the Graphical Planning Board by using the cross in the upper right corner, the system returns to

tipcs4171m000. You can make any changes here, but the Planning Board will not start again.

SOLUTION DESCRIPTION:

When you close the graphical planning board by using the cross in the upper right corner (ALT-F4), tipcs4171m000 will

also closed.

It is possible to display modified data in tipcs4171m000 as long as both processes are active.

SITUATION IDENTIFIED IN: timps3201m000 "Generate Master Production Schedule"

SITUATION DESCRIPTION:

Generate Master Production Schedule fails if it is still processing after midnight.

SOLUTION DESCRIPTION:

Software changed so Generate Master Production Schedule continues processing after midnight.

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

SITUATION IDENTIFIED IN: Maintain Customized Item Data (tipcs2121m000)

SITUATION DESCRIPTION:

When the fields Commodity Code and/or Country Of Origin have been changed in the standard item data (tiitm0101m000 form

4-5) they can not be updated in the session tipcs2121m000 (form 4-4) by using the option <Ctrl>[G] in the choice field.

Furthermore: this option is only available in form 1-4 while the two fields are in form 4-4.

SOLUTION DESCRIPTION:

The usage of option <Ctrl>[G] has been moved from form 1 to form 4. When this option is used the fields 'Comodity Code'

and 'Country of Origin' of the current record will be updated with the values from tiitm001. Remark that when customized

items are copied from the standard item table (tipcs2230s000), the earlier mentioned fields are automatically updated. The

option <Ctrl>[G] can be used if the standard item table has been modified.

This solution solves defect DF 12346.

Solution will be available in the next release 3.1_b7, B40_b4, B40_b4_mcr0, B40_c1

SITUATION IDENTIFIED IN: tipcf5120s000 (Product Configurator).

SITUATION DESCRIPTION:

In a sales order, when you are configuring a generic item, the description of each option for a feature (when zooming to

these options) are not displayed in the customer's language. After the zoom, when you come back with one option then the

description is in the customer's language.

SOLUTION DESCRIPTION:

The problem is basicly that not only the Standard description for each option belonging to the Feature should be shown,

but also the Description in the language as defined for the Customer ( Customer language should be defined in "Maintain

customers" ie. tccom1101m000, and "Customer language specific" descriptions should be defined in session tipcf1101m000,

by zooming to "Maintain option descriptions , tipcf1111s000 ) . The form has now been changed such that both Standard

option descriptions (in Standard language), AND Customer language descriptions are shown on the same Form.

Modified components are marked by DF 12289-1.

SITUATION IDENTIFIED IN: Enter Material Issue for Production Orders (ticst0101m000)

SITUATION DESCRIPTION:

Field subsequent deliveries is not always updated correctly.

SOLUTION DESCRIPTION:

Program script ticst0101 has been modified. Now, always a default for the subsequent deliveries will be calculated if the

field issue has been changed.

This solution solves defect DF 12054.

SITUATION IDENTIFIED IN: Display Standard Cost Price by CostType (ticpr3502s000)

SITUATION DESCRIPTION:

The total standard costprice consists of: material costs, operation costs, surcharge on material costs, surcharge on

operation costs and general costs. When zooming from "Display Standard Costprices by Item" (ticpr3501m000) the general

costs are not displayed.

SOLUTION DESCRIPTION:

The general costs are added to the form and will be calculated correctly.

This solution solves defect 12449-1

PROBLEM IDENTIFIED IN : tirpt1201m000 (Report Production Schedules Complete )

SITUATION DESCRIPTION:

When "Always Create a New Lot" = "Yes", then if the Quantity Reported Complete is greater than the possible quantity which

can be assigned to the existing Lot ( the order quantity being the maximum the Lot can be assigned with this parameter set ),

a fatal error 606 : Reference does not exist was observed.

SOLUTION DESCRIPTION:

The parameter "Always Create a New Lot" determines the assignment of quantities to Lots.

If it is "Yes", then if the quantity reported complete is assigned to a new lot through the session tirpt1201m000, but this

quantiy is greater than the order quantity of the Production Order, another new Lot is created for the remaining quantity (

= Reported Complete quantity - Order Quantity of the Production Order).

If the quantity reported complete is assigned to an existing Lot through the session tirpt1201m000, and this quantity is

greater than the quantity which can be accomodated in the existing Lot, a new Lot code is created for the remaining

quantity ( = Quantity Reported Complete - { Qrder Quantity - Existing Quantity on Existing Lot })

If it is "No", then the total quantity reported complete is assigned to the existing Lot, even if the quantity is greater than

the order quantity of the Production Order.

The new Lot Code now always gets a correct value. Error 606 no longer exists.

This solution solves defect 605.

SITUATION IDENTIFIED IN : Maintain Reference Designators (tibom0120m000)

SITUATION DESCRIPTION :

The Quantity on BOM Line is not given correct (0 instead of right value) during the first view after starting up. Hence the

Difference in Quantities isn't correct either, causing troubles while leaving the session.

SOLUTION DESCRIPTION :

Now the quantity is displayed correctly at all times.

This solution solves defect 12496.

SITUATION IDENTIFIED IN: Report Production Schedules Completed by RPT Item (tirpt1201m000)

Report Prod. Schedules Compl. by Sched. Area and RPT Item (tirpt1203m000)

SITUATION DESCRIPTION:

When an previous operation has been completed it's not possible to reject quantities in folowing operations.

As a result of this, the order can not be completed. The system keeps asking what to do with the remaining quantities,

although there aren't any remaining quantities.

SOLUTION DESCRIPTION:

Reporting schedules with rejected quantities works correctly now.

This solution solves defect DF 10084.

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: Print Estimated Cost Price by Project (tipcs3461m000)

Print Actual Cost Price by Project (tipcs3462m000)

SITUATION DESCRIPTION:

No surcharges are printed in the sessions "Print Estimated Cost Price by Project" (tipcs3461m000) and "Print Actual Cost

Price by Project" (tipcs3462m000) when we calculate costs for a sub-project which is connected to a main-project where the

surcharges are being maintained for the main project but not for the subproject.

SOLUTION DESCRIPTION:

When the costs are calculated for a subproject where it is connected to a main project and the surcharges are being maintained

for the main project but not for the subproject, the system should check for the surcharges for the subproject in the table

tipcs320 (Costprice Surcharges by Project). And if they are maintain for the subproject. It should calculate the surcharges else

if the surcharges are not present in tipcs320 table.It should check for the surcharges for the main project in the table tipcs320

and calculate it.

This solution solves defect 12381

SITUATION IDENTIFIED IN: Generate Planned PRP Orders (tipcs5201m000)

SITUATION DESCRIPTION:

Wrong item code is displayed on error report for standard phantom items without a production BOM.

SOLUTION DESCRIPTION:

The include (itipcs5000) has been modified in such a way that the correct (phantom) item code will be displayed on the error

report.

This solution solves defect DF 12595.

PROBLEM IDENTIFIED IN: Generate Sales Quotation for Budget (tipcs0240m000)

SITUATION DESCRIPTION:

The session "Generate Sales Quotation for Budget" (tipcs0240m000) doesn't roll up the quotation ammount for the budget

parts which are linked to a multilevel generice item.

SOLUTION DESCRIPTION:

The quotation ammount in (tipcs0240m000) "Generate Sales Quotation Ammount for Budget" will now be rolled up for

budget parts which are linked to multilevel generic items.

Softwarecompents marked with DF 12064-1

ti3.1b, tiB40b, tiB40c.

SITUATION IDENTIFIED IN:

"Transfer Planned PRP Warehouse Orders" (tipcs5270m000).

SITUATION DESCRIPTION:

A negative stock is generated, although the Parameter 'Negative stock allowed' (in tdinv0100m000 "INV Parameters") is set to

'NO'. This occurs when PRP orders are generated or maintained and the total quantity exceeds the actual stock. A negative

stock value could result after transferring these orders.

SOLUTION DESCRIPTION:

Now session tipcs5270m000 will transfer PRP warehouse orders for as long as enough stock is available. For all the orders

that go wrong, the message 'insufficient stock' will appear on the error report. All the modifications have been marked with

defect ID 12612-1.

SITUATION IDENTIFIED IN: timps3101m000 "Maintain Master Production Schedule"

SITUATION DESCRIPTION:

When there is demand within a holidays period, planned receipt was generated within the holidays period and after then

scheduled receipt was generated on the first workable day after the holidays period. Which results in unconsumed planned

receipts.

SOLUTION DESCRIPTION:

Software changed so Planned Receipts are generated in the period just before the holidays period which results in scheduled

receipts in the same period as planned receipt.

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

ti3.1_b, tiB40_b, tiB40_c,tiB40_c_mcr

SITUATION IDENTIFIED IN:

Generate planned PRP orders ( tipcs5201m000 )

SITUATION DESCRIPTION:

1. When generating orders for items with a scrap of 20 % you need 1 x 1.20 = 1.20 pieces (when you have a need for 1

piece). The roundingfactor is 1.00000.

But it is not possible to produce 1.2 pieces so the system should create an order advise for 2 pieces. In practice it creates an

order for 1 piece.

When you create a need of 3 pieces, you need 3 x 1.2 = 3.6. When you now run prp/mrp you will get an advise quantity of 4

pieces which is correct.

2. When selecting all projects for a PRP-run the session hangs, when single projects are selected the session works fine.

SOLUTION DESCRIPTION:

1. Now the session "generate planned PRP Orders ( tipcs5201m000 ) will round upwards when quantities are having unit =

piece and roundingsfactor = 1,000000 ( as defined in session tcmcs0101m000 ).

Modifications in function tipcs5000 ( called by tipcs5201m000 ) are marked with DF 12353-1

2. Selecting all projects for a PRP-run is possible without risk of hanging of session 'Generate planned PRP orders' (

tipcs5201m000 )

SITUATION IDENTIFIED IN: Maintain Production Orders(tisfc0101m000)

SITUATION DESCRIPTION:

Inventory unit is not displayed completely. Also the label for Unit is missing.

SOLUTION DESCRIPTION:

Forms changed, to show the unit completely. These forms are from session tisfc0505m000 and tisfc0505s000, which are the

upper part of the session tisfc0101m000.

TECHNICAL MODIFICATIONS:

Label (tigen.unit)added for Unit and extended field inventory unit to three positions.

SITUATION IDENTIFIED IN: Maintain Item Data (tiitm0101m000)

SITUATION DESCRIPTION:

In the german version of tiitm0101m000, on form 3 session states "Artikelcode" (up on the left side) and on form 1, 2, 4 and

5 session states "Artikel".

In the english version, all forms state "item".

SOLUTION DESCRIPTION:

Item Label field, tiitm001.item, has length changed to 9 <= 11, from 11 <= 13. Hence, table fields 'tiitm001.item' and

'tiitm001.dsca' moved two positions to the left.

Changes have been made in the forms in English, and Runtime has been created for this form in all four languages.

This solution solves defect 12833.

ti3.1_b, tiB40_b, tiB40_c

SITUATION IDENTIFIED IN:

Maintain Activity Relationships (tipcs4110m000)

SITUATION DESCRIPTION:

The Maximum negative float was restricted to two digit negative numbers

Form is changed for negative float from 2 to 3 digits

SOLUTION DESCRIPTION:

In the Form:

The display format has now been changed for the field 'tipcs410.arfl'

The changed form field attributes are:

1) Link/Max. Display Length: from "Yes 3" to "No 4"

2) Link/Dec. Field Length: from "Yes 1" to "No 1"

3) Link Display Form: from "Yes ZZ9VD9" to "No ZZZ9VD9"

In the Report:

The display format has now been changed for the field 'tipcs410.arfl'.

The changed report field attributes are:

1) Link with Domain: from " Yes to No "

2) Print Format: from " ZZ9VD9 to ZZZ9VD9 "

Changes are marked with DF12814

tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Maintain Planned PRP Purchase Orders (tipcs5120m000)

SITUATION DESCRIPTION:

In session 'Maintain Planned PRP Purchase Orders' (tipcs5120m000) on form 2 in ASCII the field 'Purchase Price'

(tipcs520.pric) wasn't refreshed proparly.

This situation occurred when the field is manually changed and (after that) you change another field in the same form.

Workaround was to switch between the two forms (the field(s) are refreshed then).

SOLUTION DESCRIPTION:

After zooming or changing of the field 'Purchase Price' the field 'tipcs520.pric' will be refreshed now

This solution solves defect 12354

VERSION(S):

tiB40_b4, tiB40L_b4_sch0, tiB40_c1

SITUATION IDENTIFIED IN: tiitm0101m000 (Maintain Item data)

SITUATION DESCRIPTION:

If an item (MRP/MPS) is copied to a new item and its status is to be changed it should be allowed to do so after

checking for MRP, MPS Transactions and any possible Active Puchase Contract lines in case of Supply Chain

Localization irrespective of Net Change MRP being true (YES).

SOLUTION DESCRIPTION:

A check is made to identify the above situation. ( One more check for live purchase contracts lines was made in a newly

created script in Supply Chain ).

tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: tiitm0101m000 (Maintain Item Data)

SITUATION DESCRIPTION:

If the previous Order System is MRP or MPS and no MRP/MPS transactions are linked then it should be possible to change

the order system irrespective of the Net Change MRP being 'Yes'.

For Supply Chain Localization there should also be a check for possible live contracts being present for the current item.

SOLUTION DESCRIPTION:

The check is made to see if previous order system is MRP/MPS and changing is allowed if no transactions are present for

that item.

For Supply Chain an additional check for possible 'live' Purchase Contracts is introduced after creating a new script

ptiitm0201 in that localization.

SITUATION IDENTIFIED IN : Confirm Planned PRP Purchase Orders (tipcs5220m000)

SITUATION DESCRIPTION :

PRP purchase orders are not getting confirmed via the session " Confirm PRP Purchase Orders" whereas manual confirmation

of PRP purchase orders is possible if the purchase price is zero but when the purchase amount is not zero.

A PRP purchase order cannot be confirmed only when the purchase price and the purchase amount are zero but if the

purchase amount is not zero and the purchase price is zero the PRP purchase order can be confirmed.

SOLUTION DESCRIPTION :

It is now able to confirm the PRP purchase orders through the session " Confirm PRP Purchase orders" when the purchase

price is zero.

This solves the defect DF14106