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.

ti3.1_b7,tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Report Orders Completed Globally (tisfc0206m000)

SITUATION DESCRIPTION:

The session hangs if run in job mode. This happens with backflushing set to Yes.

With defect 13391 registerred that job is terminated with message "Job interrupted because of question".

This happens by changes in program under DF454-1. Program modified with markings DF454-2 that this couldn't happen

anymore.

SOLUTION DESCRIPTION:

It will be possible to run the session in job mode. While inserting the session in the job (pressing "G" in ASCII mode), the

user will be asked to select a device to send the output.

This solution solves defect 454 and defect 13391.

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.

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.

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

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

tuB40_b, tuB40_b1, tuB40_b2, tuB40_b3

SITUATION IDENTIFIED IN: Maintain Receipts via DDC (tdpur4120b000)

SITUATION DESCRIPTION:

Receipts through DDC not complete.

The following tables are not being updated from Maintaining Receipts through the DDC Function Server:

tdilc101

tdpur045

tiitm001

tdilc402

tdinv001

As a result, the receipts are not complete, and approvals can not be maintained.

SOLUTION DESCRIPTION:

All of the necessary tables will now be updated properly when running the function server "Maintain Receipts via DDC"

(tdpur4120b000).

This solution solves defect 587.

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_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: Display Item List (tiitm0502s000)

SITUATION DESCRIPTION:

Navigation through the item records is extremely slow when many containerized items exist. This solution should only be

applied if many containerized items exist and performance is not ideal.

SOLUTION DESCRIPTION:

This solution relies on a few STANDARD changes to program scripts and a few easy CUSTOMIZATION changes for several sessions

to the start index of each (the sort used by default when starting a particular session). If both are done, navigation will

be quick for containerized items (although if a user of one of the changed sessions overrides the start index and thus

changes the sort by selecting one of the choices in the "Order" drop down menu in the GUI version or by pressing "K" in

the ASCII version, navigation performance may again be non-ideal).

It is important to understand the relationship between the sort used (such as the start index, which is ) and the query

functionality. The fields used in the index are the fields used to specify query values. Thus, as a result of the

customizations described in this solution, the startindex index will be changed to a sort that includes the containerization

field, but the item, search key, order system, and other fields that may be desirable to query by will not be included. If a

user wants to do a query, s/he will need to change the sort by selecting one of the choices in the "Order" drop down menu in

the GUI version or by pressing "K" in the ASCII version.

The CUSTOMIZATION changes are to use session "Maintain Sessions (ttadv2100m000)" to select the sessions that currently provide slow navigation, and use the "Change Key" option to change index 11 to be the start index (i.e., "Allowed" is set to "Yes" and "Sort" is "1" for index 11). If index 11 is not currently set as such, you will need to add 1 to the Sort for the other indices that have "Allowed" set to "Yes" (e.g., "Sort" for index 1 becomes "2", "Sort" for index 2 becomes "5", etc.) The sessions you may need to change (different VRC's will have

different requirements) are: tiitm0101m000, tiitm0101s000, tiitm0501m000, tiitm0501s000, tiitm0502m000, tiitm0502s000. It is

important to note that these changes to the start index are not "standard", and if a patch is installed that modifies one of the

sessions (the session itself, not, for example, a program script used by the session), the start index will need to be changed

back to index 11 (or some index that has the containerization field) because navigation performance will likely become

non-ideal again.

This solution solves defect 337.

tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Generate Planned PRP Orders (tipcs5201m000)

SITUATION DESCRIPTION:

In PCS, when running "Generate Planned PRP Orders", PRP may create orders with incorrect amounts when a sales order

containing several lines, all for the same item needed on different dates, is being processed.

SOLUTION DESCRIPTION:

The session "Generate Planned PRP Orders" now calculates correct order quantities and generates orders for them.

This solution solves defect 708

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 MPS/MRP Production Batches (timrp1270m000)

SITUATION DESCRIPTION:

When zooming from the "To" column for "MPS/MRP Prod. Batch" in "Transfer Planned MPS/MRP Production Batches"

(timrp1270m000), the wrong subsession was accessed.

SOLUTION DESCRIPTION:

"Display Planned MPS/MRP Production Batches" (timrp1522s000) is now accessed from the zoom instead of "Display

Planned MRP Production Orders" (timrp1520s000).

This solution solves defect 12515.

SESSION ERROR IDENTIFIED IN: tigrt0282s000 " Search for (Project) Items "

PROBLEM TEXT:

Items were found as matching the 'master item' when there were differences in some of answers to the search questions.

This problem was fixed in Triton 2.2c by ID 31965.

For higher versions ID 10272 is used

SOLUTION DESCRIPTION:

A small change has been made so that each item and feature is checked against the master item an it's corresponding feature.

SESSION ERROR IDENTIFIED IN: tisfc0101m000 "Maintain Production Orders"

PROBLEM TEXT:

When a stock for phantom items exist and a production order for an item which contains this particular phantom item in its

BOM structure, the system uses the actual stock instead of the economic stock.

SOLUTION DESCRIPTION:

Function / DLL "Process Production Order" (sfc0220) has been modified in such a way that the economic stock is used instead

of the actual stock.

Modifications in software components are marked with ID 10656-1.

tf3.1_b, tf3.1_b1, tf3.1_b2, tf3.1_b4, tfB40_b1, tfB40_b2, tfB40_b3

SESSION ERROR INDENTIFIED IN:

tfcmg1120m000 Maintain Payment Advice

PROBLEM TEXT:

When you select data of the type 'Sales Credit Note' of a supplier with no customer linked to it. You get the wrong message :

No customer linked to this supplier. Type of advice Sales Credit Note not possible.

SOLUTION DESCRIPTION:

Error message changed to 'No customer linked to this supplier'.

SESSION ERROR IDENTIFIED IN:

tipcf2201m000 "Compile Constraints by Generic Item

OTHER SESSIONS:

none

PROBLEM TEXT:

The '.e' file (file with the error messages and warnings) in session (tipcf2201m000) "Compile Constraints by Generic Item"

is not removed after compiling when you ask for deleting the sources and when there are ONLY warnings in this file. This

can be very confusing.

SOLUTION DESCRIPTION:

The '.e' files, generated in session (tipcf2201m000) "Compile Constraints by Generic Item", with WARNINGS ONLY will be

removed after compilation when you set the field "Deleting Constraint Source" in this session to "YES". Mention that '.e'

files containing at least one ERROR-message will NOT be deleted. When the field "Deleting Constraint Source" is put on

"NO" the warning and error files with extention '.e' will be saved. Modifications in the software components have been

marked with ID 10811-1.

SESSION ERROR IDENTIFIED IN: tiedm3240m000 "Finalize Engineering Data"

OTHER SESSIONS: tiedm1220m000 "Maintain EBOM copy Data"

PROBLEM TEXT:

When there no BOM changes are in the new revision, NETCHANGE is not set to Yes, so the revision on production orders is

not changed after PRP run.

SOLUTION DESCRIPTION:

NETCHANGE is now always set to Yes, even when there no BOM changes are.

All changes have been marked with DF11033-1.

tiB40b, tiB40c.

SESSION ERROR IDENTIFIED IN:

tipcs5420m000 "Print Planned PRP Purchase Orders".

OTHER SESSIONS:

tipcs5410m000 "Print Planned PRP Production Orders".

SITUATION DESCRIPTION:

The planners' name and code are not printed correctly on the reports produced by "Print Planned PRP Purchase Orders". The

planners' code is also not printed correctly on some of the reports produced by "Print Planned PRP Production Orders".

Furthermore, the session "PRP Planned Purchase Orders by Buyer" produces a report sorted by planner instead of by buyer.

SOLUTION DESCRIPTION:

The sorting order and the fields for the planner name, planner code, buyer code and buyer name have been changed on the

reports generated by the above mentioned sessions. The reports will now be produced correctly.

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.

SITUATION IDENTIFIED IN : Maintain Routing Sheets (tipcs1120m000)

Maintained Customized Routing (tipcs2170m000)

Maintain Genric Routing (tipcf3120m000)

SITUATION DESCRIPTION :

ID 10228873 must be build in into tipcs1120, tipcs2170 and tipcf3120 also.

SOLUTION DESCRIPTION:

ID backported to above mentioned program sources.

This solution solves defect DF 11795-1

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: 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.

tiB40_b, tiB40_b, tiB40_c

SITUATION IDENTIFIED IN: Process Hours Accounting (tihra1210m000)

SITUATION DESCRIPTION:

The company number is not selected correctly in multi company situation. If you try to book hours on a employee and this

employee doesn't belong to the current financial company then there are certain rules how to determine on which company

the hours should be booked. These rules were not take into account, the system determines the wrong company number.

SOLUTION DESCRIPTION:

When posting hours for a employee the hours are being booked on the financial company, dependent on the production order,

work center, project etc.

This solution solves defect 12032

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.

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.

SESSION ERROR IDENTIFIED IN: tiitm0101m000 "Maintain standard Item Data"

PROBLEM TEXT:

After ID 10242779 customers could have problems when they use EDM without coping EBOMs.

All modifications has been marked with DF12135-1

SOLUTION DESCRIPTION:

Program is changed so when a manufactured E-item which does not have any E-bom line with physical item, Copy Bom lines

is not necessary.

ti3.1a, ti3.1b, ti3.1bjit0, tiB40a, tiB40asch0, tiB40b, tiB40bsch0, tiB40bmcr0, tiB40Sbcon, tiB40c.

SITUATION IDENTIFIED IN:

Maintain Estimated Materials (tisfc0110m000).

SITUATION DESCRIPTION:

Negative backflushing was no longer possible after modifications were made by ID 10242224 and DF 11094-1.

SOLUTION DESCRIPTION:

Backflushing of negative quantities has been made possible again in all cases (i.e. with ILC 'on' or 'off'). In addition

some other smaller problems have been solved. Modifications made by ID 10242224 and DF 11094-1 that prohibited the

backflushing of negative quantities have been removed or changed. This solution solves defect DF 12157-1.

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.

SOLUTION VERIFIED IN: Maintain Planned MRP Production Orders (timrp1120m000)

SITUATION DESCRIPTION:

When adding new orders in " Maintain Planned MRP Production Orders " (timrp1120m000) the fixed start and finish dates are

calculated incorrectly or not filled at all.

If the planning method is backwards then the fixed start date is not calculated, giving an error message when trying to write

the new order to the table (timrp020).

If the planning method is forwards then the fixed finish date is always calculated by using the lead-time found in the item

master.

SOLUTION DESCRIPTION:

The fixed start and finish dates are now calculated correctly.

When adding new orders the lead-time will always be calculated based on routing data, or, when no routing data is specified,

it is based on the lead-time stored in the item master.

This solution solves defect 12209.

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:

Generate Planned MRP/MPS Order/Batches (timrp1210m000)

Maintain Sales Orders (tdsls4101m000)

and more.

SITUATION DESCRIPTION:

ATP Check is going wrong in the following situation:

For a Process Item:

planning is done based on the main item, a sales order is entered for an end item.

SOLUTION DESCRIPTION:

Problem is solved. Problem solution is marked with DF 11897-1

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: 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: 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: 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

SITUATION IDENTIFIED IN : Print Planned Inventory Movements by Item and Period (timrp1412m000)

SITUATION DESCRIPTION:

A fatal error - Float Exception - has been observed while trying to print Planned Stock movements by item and period.

SOLUTION DESCRIPTION:

Float exception does not occur any more. There was a programming error which has been corrected.

Modifications in software component is marked with DF 12467-1.

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: Print Pull Notes by Order (tisfc3402m000)

SITUATION DESCRIPTION:

According to the helptext of tisfc3101m000 "Maintain Pull Note Layouts", it should be possible to print the delivery and

production date on inter-operational pull notes.

SOLUTION DESCRIPTION:

Above mentioned dates will now be printed on Inter-operational pull notes (if you are using variable #dldt and #prdt in the

"Maintain Pull Note Layout" text ).

VERSION(S): tiB40_b3, tiB40L_b3_sch0, tiB40_c

SITUATION IDENTIFIED IN: "Generate Master Production Schedule" (timps3201m000)

SITUATION DESCRIPTION:

Fatal error: Detected database server termination. During MPS run "Generate Master Production Schedule" (timps3201m000)

the system comes up with errors and you can't continue.

Software delivery for ID10240934 was incomplete. This Solution includes all modified components for ID 10240934.

SOLUTION DESCRIPTION:

Table TIMPS420 changed for the VRCs B40_bx_dev and B40_c_sys. Field timps420.plct added (as fieldnumber 4). Also this

field added in the cmba field.

Additionally index 1 and 2 are added with this field. Customers with this problem must do the following:

1. Import the new table definition of table TIMPS420 by Importing the solution 11374 and make sure it is installed well

(defect number 12580 must be listed in the session info (ttstpsessinfo) of the sessions listed

under modified components.

2. Be sure that all other users are logged out, and no jobs are running, and then start session ttadv5210m000 (Tools,

Application Development, Runtime Data Dictionary, Create Runtime Data Dictionary )

and give the following input :

Package combination: from à to zzz

Domains: Yes

Tables: Yes

Reconfigure tables: Yes

Sessions: No

Print Errors: No

Package: from ti to ti

Table: from TIMPS420 to TIMPS420

Sessions: from à to zzzz

Also create runtime Help: no

3. Run session TIMPS3201M000 (regenerative), with only the field "Generate Rough Capacity Requirements" on [yes], for all

the relevant plan codes, plan levels and plan items. (This step isn't however

mandatory, the building of the table will succeed with the first next (fully regenerative) MPS run. Modifications in

software components are marked with ID 10240934.

ti3.1_b, tiB40_b, tiB40_mcr0.

SITUATION IDENTIFIED IN:

Generate Product Variant Structure for Budget (tipcf5270s0000).

SITUATION DESCRIPTION:

Fatal error 206 (record is not locked) occurs with tipcs002301 in db_update when changing a product variant for a budget

with the session "maintain budget parts" (tipcs0150m000).

SITUATION SOLUTION:

The error was due to the incorrect implementation of retry points. The defect DF 12598-1 is solved by this Solution.

Modifications in Software components are marked with DF 12598-1.

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.

tiB40_b, tiB40_b1, tiB40_b2, tiB40_b3

SITUATION IDENTIFIED IN: Maintain Item Data (tiitm0101m000)

SITUATION DESCRIPTION:

2 field descriptions are missing in session tiitm0101m000 on form 5 in German language.

The third and fourth field under process data are unlabeled but must have the following labels:

- Default Cont. MPS/MRP

- Use Formula Ratio

SOLUTION DESCRIPTION:

2 Labels added in German language:

- tiitm001.dcnt length 17

- tiitm.ufra length 28

This solution solves defect 12329

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.1_b, tiB40_b

SITUATION IDENTIFIED IN: Enter Hours Accounting (Daily) (tihra1101m000)

SITUATION DESCRIPTION:

Machines which code has alphanumeric characters in it, cannot be inserted in "Enter Hours Accounting (Daily)"

(tihra1101m000)

SOLUTION DESCRIPTION:

All machines (numbers/codes) can be inserted for hours accounting, The option "Link/Dis. Form" on the form field was "No"

and filled with "ZZZZZ", but the link is now put on "Yes", which is necessary.

This solution solves defect 757 which is a backport of ID10243265

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: Generate Product Variant Structure for Sales Order (tipcf5260m000)

SITUATION DESCRIPTION:

When making use of constraints which update tables (in our case tdsls041), a error 107 occurs when inserting two sales order

lines for the same generic item and project. After inserting and generate the product variant structure for sales

(tipcf5260m000) and running this session the error 107 (record is locked) will come up.

SOLUTION DESCRIPTION:

It is possible to insert two salesorderlines for the same generic item and project, while the constraints update the table.

Modifications are marked with DF 10865-1

SITUATION IDENTIFIED IN: Generate Planned PRP Orders (tipcs5201m000)

SITUATION DESCRIPTION:

Calculated production startdate and production finishdate for planned production orders is incorrect when last operation does

not end last. This might be the case if overlap percentages are used and planning is done backwards.

SOLUTION DESCRIPTION:

If in the above situation backwards planning is used, the correct start date will be calculated. From that date forwards planning

is used to plan the order correctly.

This solution solves defect 11207 (and is marked in the modified components as DF 11207-2).

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.

SITUATION IDENTIFIED IN:

Maintain Planned MRP Production Orders (timrp1120m000).

SITUATION DESCRIPTION:

On form 1 of session Maintain Planned MRP Production Orders (timrp1120m000) the sequence of the input fields is not

correct.

SOLUTION DESCRIPTION:

Field sequence corrected.

This solution solves defect 10967.

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: Maintain Product Variants ( tipcf5101m000 )

SITUATION DESCRIPTION:

When you enter the configurator for instance through the session tipcf5101m000 (Maintain Product Variants) and change a

variant, in the configurator a field is shown which says whether there is text or not.

All the flags are all default set to "NO" when the configurator screen is started. After changing or just entering through the

options, all lines having Text are suddenly changed with text flags being "Yes".

SOLUTION DESCRIPTION:

Session "Product Configurator" ( tipcf5120s000 ) is changed such that now the Text flag's are showing the correct status.

Badfix ID 10230069 is now removed by this fix.

Modifications in tipcf5120 session are marked with DF 12629-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: Generate product variant structure for Project ( tipcf5280m000 )

SITUATION DESCRIPTION:

The session "Generate product variant structure for Project ( tipcf5280m000 )" is hanging after you answered "Yes" to the

question "Generate product variant structure ?".

This happens only in ASCII mode.

SOLUTION DESCRIPTION:

This problem was caused by the fact that the report was not closed correctly ; Now the session "Generate product variant

structure for Project ( tipcf5280m000 )" is modified such that (Error)

report get's closed and printed correctly. Modifications in software are marked with DF 13139-1.