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

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_sch0, tdB40L_b1_sch0, tdB40L_b2_sch0, tdB40L_b3_sch0

tdB40_c1

SITUATION IDENTIFIED IN:

Maintain Quotations (tdsls1101m000)

Maintain Quotation Lines (tdsls1102s000)

SITUATION DESCRIPTION:

Text manager key word descriptions are misleading or wrong. In the case of Quotation headers, there is no clear distinction

between footer text and header text. In Quotation Lines, key word 1 seems to suggest that the associated line text is related

to sales orders and not to Quotations.

SOLUTION DESCRIPTION:

A condition was added to the Maintain Quotations script to determine whether the text was for footer or header and then

assign the correct value to key word 2. For Quotation lines, the text value was changed from Sales to Quotation Line. This

solution solves defect 415-1.

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

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_sch0, tdB40L_b1_sch0, tdB40L_b2_sch0, tdB40L_b3_sch0

tdB40_c1

SITUATION IDENTIFIED IN:

Display Deliveries (tdsls4531m000)

SITUATION DESCRIPTION:

When using index on form, the key field associated with that index is not the field that is entered when using CTRL-F.

SOLUTION DESCRIPTION:

The sequence of the form fields was changed to coordinate with the index being used.

This solution solves defect 524-1.

tdB40_b, tdB40_b1, tdB40_b2, tdB40_b3

tdB40_c1

SITUATION IDENTIFIED IN:

Print and/or Delete Inquiry History (tdpur1204m000)

SITUATION DESCRIPTION:

The text is not being printed on the report for inquiries containing text. This only occurs if the order is the last one on the

report.

SOLUTION DESCRIPTION:

The report layout that handled text printing for the order was modified so that if the order is the last on the report, its

accompanying text will be printed.

This solution solves defect 525-1.

tdB40a, tdB40b, tdB40Lbglo0/gls0/sch0.

SITUATION IDENTIFIED IN:

Generate Cycle Counting Orders (tdilc5210m000).

SITUATION DESCRIPTION:

When a range of item groups are specified, those items that are not within the item group range and those items that are

associated with the specified warehouses (that are not location controlled) are incorrectly included in the generation.

SOLUTION DESCRIPTION:

The range checking was modified to check the item group range separately from the location characteristics. This solution

solves defect 745.

SESSION ERROR IDENTIFIED IN:

tdsls4102s000 - Maintain Sales Order.

tdpur4102s000 - Maintain Purchase Order.

SITUATION DESCRIPTION:

The system picks the wrong item, when the user chooses an alternative item code for the sales order entry. This only occurs

when you have a quotation for that item.

EXAMPLE:

This defect can be duplicated as follows:

1. Enter a quotation for two items.

2. Enter a new sales order using the same two items that appear in the quotation.

3. Use an alternative item code system (Set this up beforehand in tcmcs0127m000, for a specific customer and enter an

alternative item code for that system in tiitm0112m000). Complete the first line of the sales order. Everything is still OK at

this point.

4. On the second line of the sales order, enter the alternative item code system and the regular item number. The alternative

item code will be automatically filled in. Add quantity - everything is still OK.

5. Save the record. The second line of the sales order now changes, to whatever was in the first line.

6. You can not zoom or pick the second item. The system always returns the same field data as that from the first item/order

line.

SOLUTION DESCRIPTION:

The error was caused by a bad fix, ID 10241504. DF 700-1 has now corrected this. The ID 10241504 has been removed. The

complete solution: import solution #1247, provided by DF 700-1.

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_sch0, tdB40L_b1_sch0, tdB40L_b2_sch0, tdB40L_b3_sch0

SITUATION IDENTIFIED IN: Check Inventory Data (tdinv0252m000)

SITUATION DESCRIPTION:

Duplicate records were being displayed on the report.

SOLUTION DESCRIPTION:

Changed the script to only print once per record.

This solution solves defect 800

tdB40_c

SITUATION IDENTIFIED IN: Maintain Purchase Order Lines (tdilc1122s000)

SITUATION DESCRIPTION:

When doing inventory adjustments for a process item in a warehouse without location gives error messsage

tdilc00037?????????????????

SOLUTION DESCRIPTION:

Created export dump of the message that is missing on customer system

This solution solves defect 1954

td3.1b, tdB40a, tdB40b.

SESSION ERROR IDENTIFIED IN:

tdinv1220m000 "Generate Warehouse Stocktaking Orders".

SITUATION DESCRIPTION:

If a cycle counting order for a warehouse/item combination has been generated in the INV Module (which has not yet been

processed) and another cycle order is subsequently generated for the same warehouse/item combination then the message

"can not continue" appears (Error 206 (="Record is not locked")).

ANALYSE:

In the past, error 100 (maximum retries exceeded) occurred when trying to read table tdinv120, when a specific cycle

counting order was generated more than once and when the INV parameter 'Block during Warehouse Cycle counting' was set to

'No'. The error was the result of an alternate index in table tdinv120. It was introduced to prevent a cycle counting order

for a warehouse/item combination from being generated more than once. However, this solution did not deal with the duplicate

record error '100'. This has been solved with ID 10224428. Only now when the parameter in question is set to 'Yes' does the

error 206 occur on tdinv120. It only occurs when the first order is generated with the parameter set to 'No' and when the

second order is generated with the parameter set to 'Yes'

SOLUTION DESCRIPTION:

Locking/Duplicate errors were occurring, because a cycle count order was being generated for the same Warehouse/Item

combination. If a Warehouse/Item combination already exists on a cycle count order, then it should not be considered. It

should be skipped.

tdB40c1: Also, a provision has been made in the ILC Module (in version BaaN IV release c1) that no more than 1 cycle

counting order per Warehouse/Item/Location combination will be generated. This uses the same mechanism as in the INV

Module. This is realized by using an extra index on table tdilc501, in which the fields 'Warehouse', 'Item', 'Container', 'Lot'

and 'Location' have been included.

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

tdB40_b - tdB40_b3,

tdB40L_b1_glo0 - tdB40L_b3_glo0,

tdB40L_b1_gls0 - tdB40L_b3_gls0

SESSION ERROR IDENTIFIED IN: tdpur4102s000 Maintain purchase order lines

PROBLEM TEXT:

- Parameter "Several Special contracts allowed by purchase order" has the value "yes".

- When changing the quantity in the purchase order line you zoom to a contract line.

- Select a contract and return to the purchase order line.

- The special contract has now been selected and a message appears.

- Now press (enter) to clear the message. You zoom to the special contract menu AGAIN ----> This is wrong.

SOLUTION DESCRIPTION:

When changing the quantity in the purchase order line, you only zoom to the special contract menu once. There was a

programming error which was corrected by DF10810-1

SITUATION IDENTIFIED IN : Maintain Receipts (tdpur4120m000)

SITUATION DESCRIPTION:

When searching on ordernumber the message 'order received / no backorder' was wrongly displayed in case of reserved

receipts (= receipt reserved for future use with all quantities set to zero).

SOLUTION DESCRIPTION:

A new message was created to be used in case of reserved-receipts, so there can be no more

misunderstandings. In case of a reserved receipt receipt the message "order already connected to another receipt" will

be displayed. Changes have been marked by DF 11349-1.

SITUATION IDENTIFIED IN : Maintain Replenishment Order Receipts (tdrpl0122m000)

SITUATION DESCRIPTION :

It is nowhere to see in the help of tdrpl0122m000 (maintain replenishment receipts) that a receipt of ZERO is impossible. This

has to be in the help in this session, because a lot of clients do not know this.

SOLUTION DESCRIPTION :

Help Text has been written and attached to the existing Maintain Replenishment Receipts Session.

Modifications have been marked with DF 10706-1.

tdB40b1, tdB40b2, tdB40b3,

tdB40_c1

SITUATION IDENTIFIED IN : Enter Warehouse Cycle Counting data (tdinv1120m000)

SITUATION DESCRIPTION :

See the session tdinv1120m000 and helptext

POPUP HELP: Cycle Counting Processed (tdinv120.csts)

This field shows if the counting results have been processed.

Yes

The inventory on hand in the system has been processed using the session

"Process Cycle Counting Data (tdinv1221m000)". The field "Counted

Inventory" can no longer be modified.

No

The inventory on hand in the system has not yet been processed using the

abovementioned session, so the field "Counted Inventory" may still be

modified.

The help text is not right because:

1) when the field is set to 'yes' it IS possible to modify 'counted inventory'

2) once the the inventory has been processed (tdinv1221m000) the line counted inventory is not visible any more. Printing

the Cycle Counting Check Report (tdinv1421m000) is also not possible.

SOLUTION DESCRIPTION :

The field Cycle Counting Processed will change to "Yes" once the field "Counted Inventory" is entered. This indicates that

the inventory on hand is ready for processing. The Help Text has been appropriately corrected.

The check report compares the quantity recorded in the system and the counted inventory, while processing involves

adjusting the system inventory with the counted inventory.So the session "Print Cycle Counting Check Report" must be

run BEFORE processing the cycle counting data and not after. Processing can be invoked through the session "Process

Cycle Counting Data" (tdinv1221m000) or while exiting from the session "Enter Warehouse Cycle Counting Data".

Modifications have been marked with DF 11251-1.

tdB40b, tdB40c, tdB40_a.

SITUATION IDENTIFIED IN:

"Print Where-Used Lots by Item" (tdltc1410m000).

"Print Origin of Orders by Item/Lot" (tdsls1430m000).

SITUATION DESRIPTION:

Not all the levels are displayed when printing 'Origin by lot all levels'.

Double lines appear when printing 'Where_Used Lots'. This makes the analysis of this Report difficult.

SOLUTION DESCRIPTION:

The additional checks are implemented to avoid this situation. The modifications have been marked with DF 11630-1.

tdB40L_c_sch0

SITUATION IDENTIFIED IN: Maintain deliveries (tdsls4120m000)

Maintain receipts (tdpur4120m000)

SITUATION DESCRIPTION:

If you change the delivered quantity followed by pressing the SAVE button, the displayed values of the delivered and

backorder quantity are not the same as the one's stored in the database.

SOLUTION DESCRIPTION:

When the delivered quantity is changed followed by pressing the SAVE button, the backorder quantity is adjusted accordingly

to meet the values stored in the database.

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

td3.1a, td3.1b, tdB40b.

SITUATION IDENTIFIED IN:

"Display Integration Transactions by Project/Order" (tfgld4510m000).

"Change Prices/Discounts after Maintain Receipts" (tdpur4122m000).

"Release Outbound Data" (tdilc4205s000).

SITUATION DESCRIPTION:

For ID 10229542, the standard software has been modified regarding the number of units recorded in the financial

integration table.

If a lot result was applicable, then the number of units in the financial integration table (tfgld410.nuni) were recorded twice:

- First, in the receipt transaction from 'maintain receipts'.

- Second, in the receipt transaction from 'approve purchase invoice'.

The second RECEIPT transaction had the quantity 0 (zero). The quantity is recorded in the LOT RESULT transaction(s)

instead.

However, the same financial integration transactions are applicable in the case of session "Change Prices / Discounts after

Maintain Receipts" (tdpur4122m000) and in the case of the Lot (part) in question. They will be sold by means of a direct

delivery Order Type, in which case the Outbound Release will take place in sub-session tdilc4205s000. At this moment, the

(additional) purchase/receipt transactions in these 2 sessions have a number of units NOT equal to 0 (zero). The lot result

transaction has a number of units EQUAL to 0 (zero). These situations have been overlooked in the original solution.

SOLUTION DESCRIPTION:

In addition to the original solution a provision has been made to deal with this situation, in session "Change Prices /

Discounts after Maintain Receipts" (tdpur4122m000) and in the case of a direct delivery Sales Order related to the original

Lot.

Additional modifications in the sources have been marked with DF 10182-1.

tgB40b2, tgB40b3.

SITUATION DESCRIPTION:

In report pur440101000 the length of the text field has been changed to 90 positions.

SITUATION SOLUTION:

The length has been changed back to 80 positions in accordance with the normal standards.

If you want to change it back to more than 80 positions then it must be customized.

Modifications have been marked with DF11955-1.

SITUATION IDENTIFIED IN: Maintain Lots (tdltc0101s000)

SITUATION DESCRIPTION:

After the fix of DF 11978 it was possible to change the lot-type after saving a lot-code.

SOLUTION DESCRIPTION:

Now it is not possible anymore to change the lot-type after the lot-code is generated and

saved.

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

tdB40_b - tdB40_b3

SITUATION IDENTIFIED IN: tdinv0520m000 (Display Warehouse Inventory by Production BOM)

tdilc1517m000 (Display Component Inventories by Manufactured Item)

SITUATION DESCRIPTION:

For manufactured item these sessions show the inventory by component.

- When going to the last components of a manufactured item (through 'B' in ASCII or through the appropriate

button in GUI) the last component would disappear from the screen.

- When going to the first components of a manufactured item (through 'T' in ASCII or through the appropriate

button in GUI) the first component would disappear from the screen.

- When there was only one component, this record would disappear from the screen and only by going to 'Next set'

and 'Previous set' consecutively you could get the component back on screen.

- When going to the last components of a manufactured item (through 'B' in ASCII or through the appropriate

button in GUI) the wrong records could be shown.

SOLUTION DESCRIPTION:

When going to the first or last components of a manufactured item the session displays all rows correctly now.

There was a programming error caused by ID 47692, which was corrected by DF 12249-1. All modifications in the

source have been marked with DF 12249-1.

SESSION ERROR IDENTIFIED IN: tdsls4102s000 "maintain sales orderlines"

SITUATION DESCRIPTION:

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

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

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

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

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

SOLUTION DESCRIPTION:

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

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

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

VERSIONS: tdB40_c1

SITUTATION IDENTIFIED IN: Generate Outbound Advice (tdilc4201m000)

SITUATION DESCRIPTION:

If a phantom item is entered in sales order lines and the outbound advice is generated it could happen that in case of

shortages too much was issued. E.g. stock available is 3 for component A and requirement from sold phantom item is 4.5.

(say A is 1.5 items present in phantom)

If now the rounding factor for the sales unit = 1.0000 (so the phantom item) and for comp A it is 0.001 now it will happen

that requirement for A is rounded up to 5 which could cause a incorrect calculation for recommended quantity of phantom

item.

SOLUTION DESCRIPTION:

If a phantom is outbounded its components are now rounded according the inventory unit's rounding factor instead of the sales

order unit's factor.

Error was reported with ID 10229554 which caused a bad fix and is partly solved with DF 11997.

B40_a1,

B40_b1, B40_b2, B40_b3,

B40L_a1_gls0, B40L_a1_glo0, B40L_a1_sch0,

B40L_b1_gls0, B40L_b1_glo0, B40L_b1_mcr0,

B40L_b2_gls0, B40L_b2_glo0, B40L_b2_mcr0,

B40L_b3_gls0, B40L_b3_glo0, B40L_b3_mcr0.

SESSION ERROR IDENTIFIED IN:

tdpur4102s000 - Maintain Purchase Order lines.

PROBLEM TEXT :

Purchase order lines not selecting correct item if an alternative item is being used.

SOLUTION DESCRIPTION:

There was an error caused by a bad fix of DF 529-1 (System picks the wrong item when user chooses alternative item code

for sales order entry) . Changes have been marked with : DF 607-1

SITUATION IDENTIFIED IN: tdrpl0122m000 "Maintain Replenishment Order Receipts"

SITUATION DESCRIPTION:

When the receipt of a RPL order is processed (tdrpl0122m000) the delivery date instead of the receipt date of the order is

transferred to Project.

In Distribution the correct dates are used.

When delivery and receipt are in different months or years, processing of the order causes problems.

SOLUTION DESCRIPTION:

Now the date of receipt of the RPL order is transferred to Project.

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

td3.1a,td3.1b, tdB40b, tdB40c.

SITUATION IDENTIFIED IN:

Maintain Replenishment Order Deliveries ( tdrpl0114m000 ).

Confirm Back Orders ( tdrpl0120m000 ).

SITUATION DESCRIPTION:

The user has created an RPL order. While maintaining RPL order deliveries there wasn't enough stock to fulfill the order.

Therefore, the remaining quantity will be in the back order. When this backorder was confirmed for delivery and when the

user deleted the record from the session "Maintain Replenishment Order Deliveries", the change was not correctly

reflected in the session "Display Planned Inventory Movements By Order".

SOLUTION DESCRIPTION:

The session "Display Planned Inventory Movements By Order" is now updated correctly, when a backorder is first

maintained and then subsequently deleted from the session " Maintain Replenishment Order Deliveries". The programming

error was corrected with DF 11987-1.

SITUATION IDENTIFIED IN : Print Inventory Transactions by Item( tdinv7410m000)

SITUATION DESCRIPTION:

The session 'Inventory Transaction by Item' prints the 'Total' correctly. But ithe session 'Inventory Transaction by

warehouse' was cumulating the 'Total' across warehouses. This was causing mis-information.

SOLUTION DESCRIPTION:

Earlier the total of Inventory Transactions by Warehouse by Item was cumulative. Now it is modified to display a Total

separately for each item. The programming error was corrected by the Defect 12154-1. This defect is not applicable in

version td3.1_b.

tdB40_c

SESSION ERROR IDENTIFIED IN: tdsls4102s000 "maintain sales orderlines "

SITUATION DESCRIPTION:

When modifying or deleting an orderline you are prompted on pressing SAVE or SAVE&EXIT for filling in the

acknowledgement code. This depends on SLS history parameter "Prompt for Change Codes". After this the session hung with

"Transaction is on, can't continue"

SOLUTION DESCRIPTION:

There was a bad fix ID 10243189 : the acknowledgement codes where updated at the wrong place in the script which causes the

transaction to be still active during a later update. Furthermore the check on the update.status was useless because on that spot

in the script this update.status value is already resetted.

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

SITUATION IDENTIFIED IN: tdpur4201s000

SITUATION DESCRIPTION: In session tdpur4201s000 the tabel "Bis" should be "In"

SOLUTION DESCRIPTION: Label has been changed into "In" Modifications in software components have been marked

with DF12372-1

B40_b1, B40_b2, B40_b3,

B40L_b1_gls0, B40L_b1_glo0, B40L_b1_sch0, B40L_b1_mcr0,

B40L_b2_gls0, B40L_b2_glo0, B40L_b2_sch0, B40L_b2_mcr0,

B40L_b3_gls0, B40L_b3_glo0, B40L_b3_sch0, B40L_b3_mcr0.

B40_c1

SESSION ERROR IDENTIFIED IN:

tdsls1102s000 - Maintain Quotation lines.

PROBLEM TEXT :

When you change the warehouse in session tdsls1102s000 the description of the warehouse is not updated immediatly.

SOLUTION DESCRIPTION:

Display of form was modified. The problem did not occur on 3.1 b7.

Changes have been marked with 12657-1.

SITUATION IDENTIFIED IN: Copy Sales Orders (tdsls4201s000)

SITUATION DESCRIPTION:

When copying a salesorder to a new salesorder, system overrides all kinds of avaliabilitychecks, that is, no check what so ever, is

done. Not even when salesorderpositions is edited manually.

SOLUTION DESCRIPTION:

When now a sales order is copied all the normal availability checks are being done.

The modifications have been marked with : DF12694-1.

tdB40L_b1_mcr0 - tdB40L_b4_mcr0

SITUATION IDENTIFIED IN:

Display Inventories by Item and Warehouse (tdilc1512m000)

SITUATION DESCRIPTION:

When displaying the inventory for containerized items, the total stock displayed was always zero. For non-containerized

items the total stock was displayed correctly.

SOLUTION DESCRIPTION:

When displaying the inventory for containerized items, the total stock is now displayed correctly. There was a programming

error that has been corrected by DF 12085.

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

td3.1L_b1_cms0 - td3.1L_b6_cms0

td3.1L_b1_glo0 - td3.1L_b6_glo0

tdB40_b - tdB40_b3

tdB40L_b1_glo0 - tdB40L_b3_glo0

tdB40L_b1_gls0 - tdB40L_b3_gls0

tdB40L_b1_mcr0 - tdB40L_b3_mcr0

SITUATION IDENTIFIED IN: Maintain Sales Order Lines (tdsls4102s000)

SITUATION DESCRIPTION:

When the parameter 'Baan Project Implemented' was on 'Yes' and zooming from the item field in Maintain Sales Order Lines

(tdsls4102s000),

the session would erraneously zoom to the purchase menu 'Display Cost Objects (tdpur00009050)', instead of zooming to

sales menu 'Item Data (tdsls00009014).

SOLUTION DESCRIPTION:

When you zoom from the item field, zoom menu 'Item Data (tdsls00009014)' is now always zoomed to. There was a

programming error, which has now been corrected.

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

SITUATION IDENTIFIED IN: Process Commission/Rebate (tdcms2201m000)

SITUATION DESCRIPTION:

Very poor performance in the program "Process Commission/Rebate".

SOLUTION DESCRIPTION:

The performance of the session has been improved by using indexes. The modifications have been marked with : DF

10138-1.

SESSION ERROR IDENTIFIED IN: tdsls4120m000 "maintain delivery"

SITUATION DESCRIPTION:

When you want to maintain a delivery and you are not working with transportation, the message "missing parameter of

TRTOC" comes up.

SOLUTION DESCRIPTION:

A check on the Transportation parameters was always done when updating a delivery so this was changed.

The changes have been marked with 12369-1.

SESSION ERROR IDENTIFIED IN:

tdedi0070 "Field formating".

PROBLEM TEXT:

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

SOLUTION DESCRIPTION:

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

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

tdB40_b4, tdB40_c1

SITUATION IDENTIFIED IN:

Enter Quotation Results (tdsls1108m000)

SITUATION DESCRIPTION:

When zooming from tdsls1108m000 at the delivery date field, session (tdinv1550s000) "Display Planned Inventory

Transaction by Item" was being displayed with the first item in the item master and not the item that is zoomed.

For Triton 3.1b the problem is solved with solution 12680.

SOLUTION DESCRIPTION:

Imported the item and assigned it to the correct select field.

tdB40_b - tdB40_b3

tdB40L_b1_mcr0 - tdB40L_b4_mcr0

SITUATION IDENTIFIED IN: Display Inventories by Item and Warehouse (tdilc1512m000)

SITUATION DESCRIPTION:

When displaying the inventory for containerized items, the total stock displayed was always zero. For non-containerized

items the total stock was displayed correctly.

SOLUTION DESCRIPTION:

When displaying the inventory for containerized items, the total stock is now displayed correctly. There was a programming

error that has been corrected by DF 12085.

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

tdB40b, tdB40c.

SITUATION IDENTIFIED IN:

Select Receipts (tdpur4131s000).

SITUATION DESCRIPTION:

The session returns the wrong value, when the quantity has already been marked, when zooming to this session from

"Maintain Receipts" (tdpur4120m000). Subsequently, the session "Maintain Receipts" is not able to find the purchase order

that the user was trying to get.

SOLUTION DESCRIPTION:

Some logic has been added to program to enable this session to handle this situation correctly. This change has been marked

with defect 631, in the source.

SITUATION IDENTIFIED IN: Maintain Priority Simulation Codes (tdsls4124m000)

SITUATION DESCRIPTION:

The zoom from the field "Sort Sequence" in the sesion "Maintain Priority Simulation Codes" is not working properly. When

a record is chosen, nothing is returned.

SOLUTION DESCRIPTION:

The zoom from the field "Sort Sequence" now returns proper value. The solves the Defect DF15261-1