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

SITUATION IDENTIFIED IN:

Print Financial Stock and WIP Transactions (tdinv8410m000).

SITUATION DESCRIPTION:

The session 'Print Financial Stock and WIP Transactions' (tdinv8410m000) prints debit and credit lines, that result in totals

and Grand totals of zero.

SOLUTION DESCRIPTION:

This solution solves defect DF10535-1.

td

VERSIONS:

3.1_a1, 3.1_a2,

3.1_b, 3.1_b2, 3.1_b3, 3.1_b4, 3.1_b5, 3.1_b6,

B40_a, B40_a1,

B40_b1, B40_b2, B40_b3,

3.1L_b_jit0, 3.1L_b2_jit0, 3.1L_b3_jit0,

3.1L_b4_jit0, 3.1L_b5_jit0, 3.1L_b6_jit0,

B40L_a_sch0, B40L_a1_sch0,

B40L_b1_gls0, B40L_b1_glo0, B40L_b1_sch0,

B40L_b2_gls0, B40L_b2_glo0, B40L_b2_sch0,

B40L_b3_gls0, B40L_b3_glo0, B40L_b3_sch0

SESSION ERROR IDENTIFIED IN:

tdilc1122s000 - Maintain Stock Transfers by Lot and Location

PROBLEM TEXT:

Inventory transfer is allowing inventory to go out of balance.

Procedure for duplication of Error:

1. Enter a item with Inventory Unit = pcs and Storage Unit = Meter with a conversion factor of 2 (1 piece = 1/2 meter)

2. Adjus stock for the item so that stock report reads 20 pcs / 10 m

3. Transfer 40 pcs to another location or warehouse. When the user activates session tdilc1122s000, the Storage Unit/Qty

defaults in as 20 m and the Inv. Unit/Qty defaults in as 40 pcs. When the user tries to enter past this field, he/she gets

the message "No inventory or insufficient inventory" (msg tdilc00029). The user now changes the Inv. Unit/Qty to 20 pcs

and the system accepts the transaction without recalculating the storage units. The system now shows 20 psc and 20 m in the

new location.

SOLUTION DESCRIPTION:

This is not an error. The system uses stock in terms of inventory unit for maintaining checks and balances in the system. The

stock in terms of storage unit is maintained only for informational use. If the user has storage unit of pallet, and the

conversion factor is 1 pallet = 100 pieces, the pallet being recieved / transferred on the warehouse floor may not contain 100

pieces, and so then the system accepts the user input of 1 pallet and say 95 pieces. All stock checks would be done on the

basis of inventory unit.

An additional stock check is now being done, when user enters stock in terms of storage unit. A message is given if there is

not enough stock for the resultant quantity in terms of inventory unit. Also the check for stock availability has been

improved. This solution is provided under DF 353-1.

td

VERSIONS:

B40_b,

B40L_b1_gls0, B40L_b1_glo0,

B40L_b2_gls0, B40L_b2_glo0,

B40L_b3_gls0, B40L_b3_glo0

SESSION ERROR IDENTIFIED IN:

tdsls4223m000 - Process Delivered Sales Orders

tdsls4224s000 - Process Delivered Sales Orders

PROBLEM TEXT:

If there are two delivery records for the same sales orderline, and both are on the same invoice with an order status of " Ready

for Process Delivered", only the first record will get updated to the status "Deleting Line", even though financial transactions

have been registered for both deliveries of the sales orderline.

To duplicate error:

1. Enter a sales order for 10 pcs

2. Maintain Outbound for 8 pcs

3. Release the Outbound

4. Confirm and deliver the backorder

5. Print invoice for the order

6. The 1st time tdsls4223m000 is run, sequence 0 moves to deleting line, sequence 1 stays at process delivered. Integration is

updated with the full amount but sales order history is only updated for the first line. Second time tdsls4223m000 is run it

tries to wirte invoice integration there are errors because the record already exists.

SOLUTION DESCRIPTION:

The error did not occur when process delivered sales order was run from the sales invoice program. Upon investigation, there

was a slight change in the code between the function which is called from "Print Invoices" versus the function which is

called from "Process Delivered Sales Orders". However this difference did not cause the error. The difference in the code

has been resolved by DF 491-1.

Upon correcting this code, it was found that the sales order delivery line was getting updated with the correct mask and

status, but the tables tdsls049 and the history line table tdsls051 were not getting updated. Also when "Process Delivered

Sales Order" was run the second time, the tables tdsls049 and tdsls051 would get processed, but there would be a secondary

financial transaction for the same invoice. The problem was traced to an erroneous table definition in B40 b2 glo0 and B40

b2 gls0. The table definition has been corrected by ID 10242522. The table definition can be picked up from the solution

links specified below.

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.

td3.1a, 3.1b, tdB40b, td3.1Lacms0/glo0/cms0, 3.1Lbcms0/glo0/jit0[/nl10], B40Lbgls0/glo0/sch0.

SESSION ERROR IDENTIFIED IN:

tdilc4204m000 - Release Inbound Advice.

tdilc4204b000 - Release Inbound Advice ( with DDC ).

PROBLEM TEXT:

Not all lines of an Inbound Advice are always being released. The lines were generated for an item that has lot control set to

"By Unit". The ordered quantity was 600 pcs. The advice generated by "Generate Inbound" generated 600 lines of advice but only

499 lines were released. The only way one could release the rest of the lines was to delete the incomplete advice and regenerate

an advice for the rest of the lines. Only then could the rest of the items required be released.

SOLUTION DESCRIPTION:

The limit within the program was set to process only 999 lines for each order/position no. This has been corrected so that it

selects all the advised lines for an order/position no. combination. The correction was done with DF 599-1.

PLEASE REFER TO SOLUTION 11279 AND IMPORT IT, BEFORE IMPORTING THE SOLUTION GIVEN BELOW (You can use

the link in the header of this Solution).

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

tdB40_a, tdB40_a1, tdB40_a2

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

SITUATION IDENTIFIED IN: Display Receipts (tdilc4515s000)

SITUATION DESCRIPTION:

When inserting a new record in Maintain Inbound Data, the sub-session Display Reciepts does not default to the production

order that is being modified.

SOLUTION DESCRIPTION:

When inserting a receipt for a production order, the system properly displays the order being worked on.

This solution solves defect 594

tdB40_a, tdB40_a1, tdB40_a2

tdB40L_a_glo0, tdB40L_a1_glo0, tdB40L_a2_glo0

tdB40L_a_gls0, tdB40L_a1_gls0, tdB40L_a2_gls0

tdB40L_a_sch0, tdB40L_a1_sch0, tdB40L_a2_sch0

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

SITUATION IDENTIFIED IN: Maintain Approvals (tdilc4123s000)

SITUATION DESCRIPTION:

The QMS quantities seen in "Maintain Standard Inspections by Origin (tcqms1120m000)" were not being updated with the

values entered in "Maintain Approvals (tdilc4123s000)". Also, even when "Only Recommended" was set to "No", it was

possible to enter an actual rejected quantity that was less than the recommended rejected quantity.

SOLUTION DESCRIPTION:

QMS quantities seen in "Maintain Standard Inspections by Origin" (tcqms1120m000) are now updated with the values entered

in "Maintain Approvals" (tdilc4123s000). When "Only Recommended" is set to "No", it is not possible to enter an actual

rejected quantity that is less than the recommended rejected quantity.

This solution solves defect Defect Number 533.

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: Enter Inquiry Results (tdpur1103m000)

SITUATION DESCRIPTION:

Status of "Returned" is supposed to occur if at least one line has been returned.

SOLUTION DESCRIPTION:

The purchase inquiry status is returned if any of the lines has be returned.

This solution solves defect 671

tdB40_a, tdB40_a1, tdB40_a2

tdB40L_a_gls0, tdB40L_a1_gls0, tdB40L_a2_gls0

tdB40L_a_sch0, tdB40L_a1_sch0, tdB40L_a2_sch0

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: Maintain Outbound Data (tdilc4102s000)

SITUATION DESCRIPTION:

System errors stating deliveries not equal to recommended qty when confirming deliveries.

SOLUTION DESCRIPTION:

Rounding of recommended values and delivery values have been corrected to more accurately represent values.

This solution solves defect 672

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

SITUATION IDENTIFIED IN: Enter Stock Transfers by Lot and Location via DDC (tdilc1122b000)

SITUATION DESCRIPTION:

DDC function server is missing some of the standard Baan session functionality that handles inventory dates. It is not

possible to transfer dated inventory using the ddc function server tdilc1122b000. You always get the message "No inventory

or insufficient inventory" for dated inventory.

SOLUTION DESCRIPTION:

A new input field has been added to the function server which allows the user to input the inventory date. When transferring

dated inventory, the user must enter the inventory date, or the system with give the error "No inventory or insufficient

inventory".

This solution solves defect 570.

td

VERSIONS:

3.1_b, 3.1_b2, 3.1_b3, 3.1_b4, 3.1_b5, 3.1_b6, 3.1_b7,

B40_b1, B40_b2, B40_b3,

B40L_b1_gls0, B40L_b1_glo0, B40L_b1_sch0,

B40L_b2_gls0, B40L_b2_glo0, B40L_b2_sch0,

B40L_b3_gls0, B40L_b3_glo0, B40L_b3_sch0,

SESSION ERROR IDENTIFIED IN:

tdilc4203m000 - Generate Inbound Advice

PROBLEM TEXT:

Generate Inbound Advice gives error 206, when run for an RPL order

SOLUTION DESCRIPTION:

This error was caused by incorrect clause which was added to the select statement. The problem has been

corrected by DF 614-1

tdB40_b, tdB40_b1, tdB40_b2, tdB40_b3

tdB40L_b_glo0, tdB40L_b1_glo0, tdB40L_b2_glo0, tdB40L_b3_glo0

SITUATION IDENTIFIED IN: Generate Inbound Advice via DDC (tdilc4203b000)

SITUATION DESCRIPTION:

Unable to generate inbound advice through the generate inbound function server (tdilc4203b000) for Manufactured Items.

Generation of inbound advice for normal purchase order and collect purchase order types which do not have a receipt number,

is not a problem, but with DDC functionality, you cannot generate inbound advice for the items posted to stock using

production orders (SFC).

For the receipts through SFC there is no receipt number, but while generating inbound advice via DDC, the system expects the

receipt number to be filled. If the value zero is given for the receipt number and the production order number is entered,

the system does not give any inbound advice. It seems that the system assumes the order type as a full range, and there is no

way to specify the order type to be "Production Order" as there is in the standard "Generate Inbound Advice" (tdilc4203m000)

session. There needs to be a way to allow the user to specify the order type in the function server (tdilc4203b000) in order

to allow the user to generate inbound advice for the goods posted to inventory using SFC.

SOLUTION DESCRIPTION:

A input field has been added to the function server to allow the user to enter the order type. This will allow inbound advice

to be generated correctly for items which were posted to inventory using SFC.

This solution solves defect 451.

B40a, B40b, B40Lasch0, B40Lbgls0/glo0/sch0.

SESSION ERROR IDENTIFIED IN:

tdilc4201m000 "Generate Outbound Advice".

tdilc4201b000 "Generate Outbound Advice".

SITUATION DESCRIPTION:

When there was not enough stock for a certain material for a production batch, the number of times that the shortage was

printed equaled the number of operations in the batch. ID 10242239 was created to solve this problem, but the problem still

exists.

Example at customer:

PSPMG020 PSPMG010

orno opno pono orno pono opno

==== ==== -------- ==== ==== --------

1 10 0 1 10 20

1 20 0 1 20 20

1 30 0 1 30 20

1 40 0 1 40 50

1 50 5 1 50 60

1 60 10

The shortage-components were printed 6 times (Number of operations in pspmg020). The ID 10242239 reduced the multiple

printing of the shortage-components to 3 times (Number of different positions in pspmg020: 0, 5 and 10) for the given

example.

SOLUTION DESCRIPTION:

This problem (the multiple processing of all the operations for a given batch) was due to a programming error. This error

has now been corrected with DF 10507-1.

td

VERSIONS:

3.1_b, 3.1_b2, 3.1_b3, 3.1_b4, 3.1_b5, 3.1_b6, 3.1_b7,

B40_b1, B40_b2, B40_b3,

B40L_b1_gls0, B40L_b1_glo0, B40L_b1_sch0,

B40L_b2_gls0, B40L_b2_glo0, B40L_b2_sch0,

B40L_b3_gls0, B40L_b3_glo0, B40L_b3_sch0

SESSION ERROR IDENTIFIED IN:

tdilc5210m000 - Generate Stocktaking Orders

PROBLEM TEXT:

If this session is run for full range it gives oracle error 1555:snapshot too old. They have large rollback segments.

SOLUTION DESCRIPTION:

The solution is provided by adding the clause "as prepared set" to the main select statements in the program. The solution

is provided by DF 647-1.

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.

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

tdB40_a, tdB40_a1, tdB40_a2

tdB40L_a_gls0, tdB40L_a1_gls0, tdB40L_a2_gls0

tdB40L_a_sch0, tdB40L_a1_sch0, tdB40L_a2_sch0

tdB40_b, tdB40_b1, tdB40_b2, tdB40_b3

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: Print Storage Lists (tdpur4421m000)

SITUATION DESCRIPTION:

The location is not printed on the report when printing 'List by Order', whereas it is printed when printing 'List by Item' or

'List by Warehouse'. This situation occurs while ILC is implemented.

SOLUTION DESCRIPTION:

The print condition on the report field was modified to allow location to be printed when printing 'List by Order'.

This solution solves defect 783.

tdB40_a, tdB40_a1, tdB40_a2

tdB40L_a_glo0, tdB40L_a1_glo0, tdB40L_a2_glo0

tdB40L_a_gls0, tdB40L_a1_gls0, tdB40L_a2_gls0

tdB40L_a_sch0, tdB40L_a1_sch0, tdB40L_a2_sch0

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:

Maintain Quotation Lines (tdsls1102s000).

SITUATION DESCRIPTION:

When inserting lines in a quotation referencing a budget, the following error message appears: "Discount Method Not

Allowed". The quotation line cannot be inserted.

SOLUTION DESCRIPTION:

A change has been made in 'an include' so that discount method will not be empty. This solution solves defect 719.

td

VERSIONS:

B40_b1, B40_b2, B40_b3,

B40L_b1_gls0, B40L_b1_glo0,

B40L_b2_gls0, B40L_b2_glo0,

B40L_b3_gls0, B40L_b3_glo0

SESSION ERROR IDENTIFIED IN:

tdilc4211m000 - Delete Outbound Data

PROBLEM TEXT:

The user is able to delete outbound for part of the order that is shipped complete.

SOLUTION DESCRIPTION:

The sales order header table was being read after the check for ship complete. This problem has been corrected by DF 787-1.

tdB40_b, tdB40_b1, tdB40_b2, tdB40_b3

SITUATION IDENTIFIED IN: Copy Ranges of Lots (tdltc0103s000)

SITUATION DESCRIPTION:

Lot codes are switched to Left align (Modify code allignment). Lot codes maintained manually has no problems.Attempt is

made to copy ranges of lots tdltc0103s000, session will not run and gives the message "Last position must be numeric"

SOLUTION DESCRIPTION:

Have changed the code to check the alignment of the domain. If it is left aligned, the last positon filled in is checked if it is

numeric else if it is right aligned, the last character of the field is checked.

This solution solves defect 775

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_c3

SITUATION IDENTIFIED IN:

Maintain Quotation Lines (tdsls1102s000)

SITUATION DESCRIPTION:

The item category is not being updated into Sales Quotation Lines History,

so it is not copied when copying sales quotations from history.

Also applies to planned receipt date.

SOLUTION DESCRIPTION:

Added line to Log Sales Quotation History function that will transfer the item

category and planned receipt date with other values already being transferred.

This solution solves defect 821-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_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: Maintain Sales Budgets (tdsst0150m000)

SITUATION DESCRIPTION:

When the fields Commis. and Rebate are maintained at less than 1.00 (for any period)

and the session is left and then returned to, the amount less than 1.00 is no longer displayed - unless you put your cursor on

that field.

SOLUTION DESCRIPTION:

Changed the script to allow the displaying of these fields if they are less than 1 and still greater than 0.

This solution solves defect 845

td3.1b, tdB40a, tdB40b, tdB40Lbmcr0.

SESSION ERROR IDENTIFIED IN:

tdilc4113m000s000 "Maintain Receipts (ILC)".

PROBLEM TEXT:

The customized lot controlled items are not received by stock correctly. When attempting to assign a receipt to a lot, via

session tdilc4113s000, the following fatal error occurs:

"Fatal Error 606 (reference does not exist on tdltc004xxx in SELECT

Fatal Error: Cannot continue in tdilc4113s000 in DLL: otdltcdll0001

Error: tdilc4113s000: A not terminated transaction is aborted."

SOLUTION DESCRIPTION:

Lot pricing does not apply to customized items. The lot price, in the case of a customized item, should not be updated.

Originally the system tried to update the lot price as it is done for standard items. That was the reason, why the reference

between table tiitm001 and tdltc001 didn't exist. The modifications in the software components have been marked with

DF10984-1.

td3.1b, td3.1Lbglo0, tdB40a, tdB40Laglo0/gls0, tdB40b, tdB40Lbglo0/gls0/mcr0.

SESSION ERROR IDENTIFIED IN:

tdpur4401m000 ("Print Purchase Orders").

PROBLEM TEXT:

The item description (from titim0101m000) is still printed, even though the field 'Standard Description' is set to 'No' in

"Maintain Purchase Order Lines" (tdpur4102s000).

SOLUTION DESCRIPTION:

Now only the order line text is printed, when the field Standard Description is set to "No" in Maintain Purchase Order

Lines. The modifications in the software components have been marked with DF11136-1.

SITUATION IDENTIFIED IN: Display Sales Statistics (ASCII) (tdsst0501m000)

Display Purchase Statistics (ASCII) (tdpst0501m000)

SITUATION DESCRIPTION:

P-for previous does not work.

This problem is reproducable. You have to go to the sales statistics menu (Processing) and choose 'display sales statistics

(ASCII). After entering the display code, you can go for the next records by presssing 'N' for next, but if you press 'P' for

previous, it does not work.

SOLUTION DESCRIPTION:

Now P for previous and N for next work correctly.

Modifications in software components have been marked with : DF10095-1.

tdB40_b4, tdB40_c.

SITUATION IDENTIFIED IN:

Session 'Maintain Stock Transactions by Lot and Location' (tdilc1121s000).

SITUATION DESCRIPTION:

A "storage condition for warehouse and location" (tdilc0151m000) or "storage condition for item or item group" was defined

with the field mandatory set to 'No'. An inventory transaction (any type) was created and the item with the storage

condition was put intentionally into a warehouse/location without a storage condition. The system should then give a prompt

as an error message. It should let user continue with the transaction. However, the message "Ask enum tdilc40079 not found"

appeared and the transaction was aborted.

SOLUTION DESCRIPTION:

The error is solved in object tdilc40079. The message "Ask enum tdilc40079" does not appear anymore. The message

"Continue?" does appear.

SITUATION IDENTIFIED IN: Maintain Purchase Contracts (tdpur3101m000)

Maintain Purchase Contract Lines (tdpur3102s000)

Copy Purchase Contracts (tdpur3801m000)

Copy Purchase Contracts (tdpur3801s000)

Maintain Purchase Contract Status (tdpur3110m000)

Maintain Purchase Contract Status (tdpur3110s000)

Maintain Sales Contracts (tdsls3101m000)

Maintain Sales Contract Lines (tdsls3102s000)

Copy Sales Contracts (tdsls3801m000)

Copy Sales Contracts (tdsls3801s000)

Maintain Sales Contract Status (tdsls3110m000)

Maintain Sales Contract Status (tdsls3110s000)

SITUATION DESCRIPTION:

Problems are experienced in Copy Purchase Contracts and Maintain Purcase Contracts. It is not possible to make a copy of a

normal contract to a contract with overlapping periods. The same holds for inserting a line in Maintain Purchase Contracts

having a combination of supplier / item already present in another normal contract (free or active) within the same period.

If ID 10227384 is present then it was possible to create two active normal contracts within the same period and having

matching lines with same supplier / item.

SOLUTION DESCRIPTION:

It is now possible to have multiple normal contracts of status free by inserting a new purchase contract or copying an

existing purchase contract to a new one having matching lines of the same combination of supplier / item and within the same

period. However it is not possible to have multiple normal contracts having status active.

If ID 10227384 is available in the programobjects then you should check on multiple active normal contracts. The easiest way to

correct from this situation is to set all normal contracts to status free or closed and then activate those you want to be active.

SITUATION IDENTIFIED IN : Print Packing Slip (tdsls4403m000)

SITUATION DESCRIPTION : In case the field 'Print Summary Packing Slip' was BLANKED, then the

packing slip(s) received the number zero.

SOLUTION DESCRIPTION : The field cannot be blanked anymore, and the packing slips do not

receive the number zero.

There was a programming error that has been corrected by : DF 11126-1.

SITUATION IDENTIFIED IN:

Maintain Marketing Projects by Relation(tdsmi1103m000)

SITUATION DESCRIPTION:

The User expects that ALL Contacts by Marketing Project will be deleted if the corresponding combination of "Trade

Relation/Marketing Project" is deleted in the above mentioned session.

SOLUTION DESCRIPTION:

This situation caused by inconsistent attributes definition in table tdsmi122.

So far as I am not allowed to make any changes to the tables, the Deletion is now built in the Program Script.

The modifications have been marked with : DF11067-1.

PROBLEM IDENTIFIED IN:

Session: Print Pickinglist tdsls440201000

SITUATION DESCRIPTION:

a) "Original" is printed on top of report even if it is a copy.

b) Page number is not shown on report - pagenumber is set in the

layout.

c) There s a mismach in report headlines, "Quantity" and the amount

doesn t fit.

SOLUTION DESCRIPTION:

There are 2 different layouts that contain "Quantity" one for ILC on and 1 for ILC off. The layout has been changed,

changes have been marked with 11411.

SITUATION IDENTIFIED IN:

Enter Quotation Results(tdsls1108m000)

SITUATION DESCRIPTION:

If the Quotation consists of two or more lines and the User changes the Status of one of them, then the expected Update of

History file does not happen.

SOLUTION DESCRIPTION:

The User is allowed to change the Status of Quotation Line without marking this line. In this case the Previous Status was

wrongly defined and as a result the corresponding Update of History file was not triggered. The Script is now adjusted to avoid

this situation.

The modifications have been marked with : DF11277-1

tdB40b.

SITUATION IDENTIFIED IN:

tdsls4102s000 (Maintain Sales order lines).

SITUATION DESCRIPTION:

This problem only occurs under the following conditions:

- when special contracts are being used.

- and when the sales price unit in the contract differs from the price unit in the item file.

The wrong prices are calculated when you are not using a sales contract number in the header of the sales order. When you

maintain a sales order line, and the line has been linked to the contract manually, the prices are calculated incorrectly. If the

contract number is filled in the sales order header, the sales order lines are automatically linked to the contract. Then the

prices are calculated correctly.

SOLUTION DESCRIPTION:

The calculated sales prices are now correct when the sales contract number is not filled in in the sales order header and the

sales order line has been linked to a sales contract manually. ID 10020709 caused the programming error. It has been

corrected with DF 11701-1.

tdB40b, tdB40Lbglo0/gls0/mcr0.

SESSION ERROR IDENTIFIED IN:

tdsls4105s000 "maintain sales orderlines (Wholesale) ".

tdpur4105s000 "maintain purchase orderlines (Wholesale)".

SITUATION DESCRIPTION:

An "OK" button and a "Cancel" button appear on the sales order lines, when you are working with Wholesale.

Furthermore, when there is more than one discount level present for an order line and when the order line has not been saved,

the first discount percentage is shown on the form.

SOLUTION DESCRIPTION:

The "OK" button and the "Cancel" button are no longer appearing on the sales order lines when you are working with

Wholesale.

Furthermore, when there is more than one discount level present for an order line and when the order line has not been

saved, no discount percentage will be shown on the form. The problem has been solved with DF 11031.

tdB40b, tdB40Lb4glo0/gls0/mcr0.

SESSION ERROR IDENTIFIED IN:

tdpur4102s000 "Maintain purchase order lines".

SITUATION DESCRIPTION:

It is not possible to enter an account number for costs items, in the session "Purchase Order Lines" (tdpur4102s000), when

the parameter 'Project implemented' (tppdm0100m000 "Maintain General Parameters") is set to 'YES' and the project is NOT

a TP project.

SOLUTION DESCRIPTION:

In the session "Purchase Order Lines" it is now possible to enter an account number for PCS-project cost items. The

modifications in the source have been marked with DF11952-1.

td3.1b, tdB40b, tdB40c, tdB40csys9.

SITUATION IDENTIFIED IN:

Update Sales Statistics (tdsst0201m000).

SITUATION DESCRIPTION:

Sometimes, whilst running this session a float exception occurs.

SOLUTION DESCRIPTION:

There was a field in the history with the value 0. This field was used in a division. This caused the float exception. The

field is now checked before the division. This is marked with ID 12126-1.

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.

td3.1_b, td3.1L_b_cms0, td3.1L_b_glo0,

tdB40_b, tdB40L_b_glo0, tdB40L_b_gls0,tdB40L_b_mcr0.

SESSION ERROR IDENTIFIED IN: tdsls4102s000 "maintain sales orderlines "

SITUATION DESCRIPTION:

When the project number is changed, after a line with project and generic item has been saved, the project information wasn't

read again so the prices were not reinitialised.

SOLUTION DESCRIPTION:

There was a bad fix in the source ID 10241260. According to this description it was not possible to insert more than one

order line for the same generic item and to link it to the same project. After removing the fix the problem did not occur

again.The changes have been marked by : DF 12060-1.

SITUATION IDENTIFIED IN: Maintain Sales Orders Lines (tdsls4102s000)

Maintain Deliveries (tdsls4120m000)

Maintain and Confirm Back Orders (tdsls4125m000)

Process Delivered Sales Orders (tdsls4223m000)

SITUATION DESCRIPTION:

The costprice of an item having components and status issue components is saved incorrectly in the sales order line history

after using

the following sessions:

Maintain Sales Order Lines - Maintain Deliveries - Maintain and Confirm Back Orders - Print Sales Invoices - Process

Delivered Sales Orders.

SOLUTION DESCRIPTION:

A salesorder with a sales orderline containing an item having components and status issue components results in recording the

costprice in the sales history equal to the sum of the costprices of the components. This is not necessarily the same as the

costprice of the item on the sales orderline.

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

B40L_b1_gls0 - B40L_b3_gls0, B40L_b1_mcr0 - B40L_b3_mcr0.

SITUATION IDENTIFIED IN: tdsls4102s000 ("Maintain Sales Order Lines").

SITUATION DESCRIPTION: When using a customized Phantom item, linked to a project, then

the messages "Item is not a customized item" and "Item is a phantom

item" appeared, or message "no valid components found".

SOLUTION DESCRIPTION: The messages will no longer appear. Also the message "No valid

components found" will no longer wrongly appear. Modifications in

software components have been marked with : DF12072-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.

tdB40_a, tdB40_a1, tdB40_a2

tdB40L_a_glo0, tdB40L_a1_glo0, tdB40L_a2_glo0

tdB40L_a_gls0, tdB40L_a1_gls0, tdB40L_a2_gls0

tdB40L_a_sch0, tdB40L_a1_sch0, tdB40L_a2_sch0

tdB40_b1 - tdB40_b3

tdB40L_b1_glo0 - tdB40L_b3_glo0

tdB40L_b1_gls0 - tdB40L_b3_gls0

tdB40L_b1_mcr0 - tdB40L_b3_mcr0

SITUATION IDENTIFIED IN: tdsls4102m000, tdpur4102m000 ("Maintain Sales/Purchase Order lines").

SITUATION DESCRIPTION: Poor performance of the sessions tdsls4102m000 and tdpur4102m000, on

an Oracle level 2 driver.

SOLUTION DESCRIPTION: Improved the sql query that caused the problem. Performance is much

better now. Modifications in software components have been marked

with : DF12231-1

tdB40L_b_mcr0, tdB40L_b_sch0.

SITUATION IDENTIFIED IN: tdilc4113sm000 "Maintain Receipts (ILC)"

SITUATION DESCRIPTION:

In the case of replenishing a Triton Project project with a lot-controlled item the inventory on hand of the lot

(tdltc001.stoc) should decrease with the quantity to replenish because it is an issue of inventory out of a warehouse. The

replenishing quantity was added to the inventory on hand of the lot involved.

SOLUTION DESCRIPTION:

Program script has been changed. Now lot-data is updated correctly.

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

tdB40b, tdB40b1, tdB40b2, tdB40b3

tdB40Lb1_mcr0, B40Lb2_mcr0, B40Lb3_mcr0

SITUATION IDENTIFIED IN: Maintain Receipts (tdpur4120m000)

SITUATION DESCRIPTION:

After maintaining receipts of a pcs item the table field tfgld410.cuno is not filled with the project customer-code.

SOLUTION DESCRIPTION:

The field tfgld410.cuno is now being filled for the integration booking "Material Cost" when doing Maintain Receipts for a

PCS item.

The modifications in the source have been marked with : DF10995-1.

tdB40_b, tdB40_b1, tdB40_b2, tdB40_b3,

tdB40L_b_mcr0, tdB40L_b1_mcr0, tdB40L_b2_mcr0, tdB40L_b3_mcr0,

tdB40L_b_sch0, tdB40L_b1_sch0, tdB40_b2_sch0, tdB40L_b3_sch0.

tdB40L_b_glo0, tdB40L_b1_glo0, tdB40_b2_glo0, tdB40L_b3_glo0.

SESSION ERROR IDENTIFIED IN: tdilc4113s000 "maintain receipts (ILC) "

tdilc4114s000 "maintain receipts (ILC) (SCH version)"

tdilc4113b000 "maintain receipts (ILC) via DDC"

.

SITUATION DESCRIPTION: The received quantity is calculated incorrect in "maintain receipts ILC".

SOLUTION DESCRIPTION: The received quantity is calculated after all receipt lines are typed in.

This is solved by : DF 12238-1.

SITUATION IDENTIFIED IN: Maintain Sales Order Lines (tdsls4102s000)

SITUATION DESCRIPTION:

A new currency has been introduced. Prices and discounts should be recorded in 4 decimals for this currency. this works fine.

It causes a problem in the following situation:

3 Discount levels are used. On the order line, after entering the price, the system zooms to the session where the discounts

can be entered, only one level of discount is entered, as an amount in 4 decimals. At the order line entry screen, only 2

decimals are shown.

When an attempt is made to type 4 decimals, the system gives a message 'Discount amount not allowed' and the discount

amount is shown on the order line in the field Disc. Amount.

SOLUTION DESCRIPTION:

The discount amount was not shown in the currency format. Now the form is changed, so that the

discount amount is shown in the currency format. When the currency format specifies 4 decimals,

then now 4 decimals will be seen.

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

tdB40a, tdB40Laglo0/gls0/sch0,

tdB40b, tdB40Lbglo0/gls0/mcr0/sch0.

SITUATION IDENTIFIED IN:

"Rebuild Planned Inventory transactions" (tdinv0250m000).

SITUATION DESCRIPTION:

Wrong items were reported by tdinv025001000 when running tdinv0250m000.

SOLUTION DESCRIPTION:

The variables were not correctly filled. This has now been corrected. Now the right items are reported. Modifications have

been marked with DF 12061-1.

td3.1b, td3.1Lbglo0/cms0, tdB40b1, tdB40Lbglo0/gls0/mcr0.

SITUATION IDENTIFIED IN:

tdsls4102s000 "maintain sales order lines".

tdsls4225m000 "unblock sales orders".

SITUATION DESCRIPTION:

Margin control, in combination with sales order blocking, does not work.

SOLUTION DESCRIPTION:

The mechanism of margin control, in combination with sales order blocking, has been changed. The modifications have

been marked with DF 10804-1.

tdB40b, tdB40Lbmcr0.

SITUATION IDENTIFIED IN:

Updating Sales Statistics (tdsst0201m000).

SITUATION DESCRIPTION:

When running the session "Update Sales Statistics" it works well, for most of the Sales Orders that have been processed.

However, when processing an order for which a rebate has been calculated, the sales statistics update crashed.

SOLUTION DESCRIPTION:

An incorrect parameter was used in the calculation. The source has been modified and now the statistics update runs as

required when a rebate has been calculated for an order. The modifications to software components have been marked with

DF 629-1.

SITUATION IDENTIFIED IN: tdpur1102s000

SITUATION DESCRIPTION: When inserting a new inquiry line, the field for alternative item

code is skipped.

SOLUTION DESCRIPTION: Field alternative item code can be accessed again. Modifications in software components

have been marked with DF12406-1

td3.1b, td3.1Lbjit0, tdB40b, tdB40Lbmcr0/sch0.

tdB40a

SESSION ERROR IDENTIFIED IN:

tdilc4102s000 "maintain outbound data"

tdilc4201m000 "generate outbound advice"

tdilc4203m000 "generate inbound advice"

tdilc4204m000 "release inbound data"

tdilc4104m000 "maintain inbound data"

tdilc4213m000 "delete inbound data"

tdilc4403m000 "print inbound data"

tdilc4512m000 "display inbound data"

SITUATION DESCRIPTION:

It is not possible to generate an outbound from a receipt location anymore. When it was possible the purchase and production

orders got stuck in their procedures, because of the 'outbounded' inventory from the receipt location.

SOLUTION DESCRIPTION:

It is now possible to generate an outbound advice from a receipt location without the purchase and production orders getting

stuck in their procedures, because the outbound movement is from the receipt location.

The modifications have been marked with DF 12228-1.

SITUATION IDENTIFIED IN: tdrpl0111s000

SITUATION DESCRIPTION: There was no check when the field position number becomes greater then 1000.

SOLUTION DESCRIPTION: The length of the position is checked now. Printing an order acknowledgement

shows "###" on the report. Modifications in software components have been

marked with DF12405-1

SITUATION IDENTIFIED IN: Display Planned INV Purchase Orders (tdinv3520m000)

Display Planned INV Purchase Orders (tdinv3520s000)

SITUATION DESCRIPTION:

Labels on top of the form do not match the column contents.

SOLUTION DESCRIPTION:

The forms now display the correct labels.

SITUATION IDENTIFIED IN: tdilc5411m000 (Print Cycle Counting Check Report)

SITUATION DESCRIPTION:

By ID 10230816 a performance problem is introduced into this program.

SOLUTION DESCRIPTION:

Original bug (by containerized items information was not shown right) solved.

Also the performance problem is solved.

Changes are marked by DF 12039-1.

td3.1_b, td3.1L_b_cms0, td3.1L_b_glo0, td3.1L_b_jit0, tdB40_b, tdB40L_b_mcr0.

SESSION ERROR IDENTIFIED IN: tdrpl0110m000 "maintain replenishment orders "

SITUATION DESCRIPTION:

In the session "Maintain Replenishment Orders' (tdrpl0110m000) it is possible to insert replenishment orders for projects with

status 'finished'.

SOLUTION DESCRIPTION:

An earlier solution under ID 10229249 (If replenishment-orders are maintained and linked to a replenishment project with

status 'Closed' the system logs cost-mutations for a project with status 'Closed) was not completely accurate and correct

programmed. This problem has now been fixed and the changes have been marked with : DF 12459-1.

td3.1b, td3.1Lbjit0, tdB40b, tdB40Lbmcr0/sch0.

SITUATION IDENTIFIED IN:

Maintain Receipts (tdpur4120m000).

SITUATION DESCRIPTION:

Due to cycle counting an item is blocked. When we receive goods line by line, in "Maintain Receipts" (using the option <C>),

the system does not accept the receipt. Due to cycle counting, the inventory transactions for the item are blocked. However,

the system accepts the item when <ctrl>G is used.

SOLUTION DESCRIPTION:

After pressing <ctrl>G, when the user tried to save the record, the system disallowed the receipt.

This was due to a programming error, which has now been corrected with DF 12208-1.

tdB40a, tdB40b.

SESSION ERROR IDENTIFIED IN:

tdpur3405m000 "Purchase Contract Confirmation".

SITUATION DESCRIPTION:

If in the session tdsls3102s000 the field standard description is "yes", then the system prints both the item description and

the purchase text on the Purchase Contract Acknowledgment. This is against the standard of TRITON/BAAN IV. Firstly, the

system should print the "Item Description by Supplier". Secondly, the "purchase text" of itm001. It prints the item

description (tiitm001.dsca), only if the aforementioned are both empty.

SOLUTION DESCRIPTION:

Now the item description is printed, once only and never on the first detail line. Modifications in the software (report)

have been marked with DF 12267-1 (in Technical Documentation).

td3.1b, td3.1Lbjit0/glo0, tdB40b, tdB40Lbsch0/mcr0/glo0/gls0.

SESSION ERROR IDENTIFIED IN:

tdilc4104s000 "maintain inbound data".

SITUATION DESCRIPTION:

Generating an inbound advice to a receipt location via the session "maintain inbound data" is possible. This may lead to

stock differences between ILC/ITM/INV.

SOLUTION DESCRIPTION:

Generating an inbound advice to a receipt location via the session "maintain inbound data" is now impossible. The

modifications have been marked with DF 12363-1.

tdB40L_b1_glo0 - tdB40L_b3_glo0,

tdB40L_b1_gls0 - tdB40L_b3_gls0,

tdB40L_b1_mcr0 - tdB40L_b3_mcr0,

tdB40L_b1_sch0 - tdB40L_b3_sch0.

SITUATION IDENTIFIED IN: tdinv0250m000 (Rebuild Planned Inventory transactions)

SITUATION DESCRIPTION: When using the session Rebuild Planned Inventory Transactions the program did not

consider the quantities that were already included in a salesorder. Therefore the contract quantities were not always

correct. Also, the session could abort with an error on reference check (error 606).

SOLUTION DESCRIPTION: The correct quantities are calculated now. Also no abort will take

place. Modifications in software components have been marked with : DF 12631-1.

VERSION(S): td3.1_b, tdB40_b, td3.1L_b_jit0, td3.1L_b_cms0, tdB40L_b_mcr0, tdB40L_b_gls0, tdB40L_b_sch0

SITUATION IDENTIFIED IN: Maintain Replenishment Order Receipt (tdrpl0122m000)

SITUATION DESCRIPTION:

In the following situation it was possible to change a receipt-line of a RPL-order when the session tdrpl2126m000,

"Process/Delete Delivered RPL Orders" was already executed:

RPL receipts are maintained, and the session tdrpl0122m000 "Maitain Replenishement Order Receipt" stays open (active)

on the screen.

The session tdrpl2126m000 "Process /Delete Delivered RPL Orders" has already been executed.

Now, receipt-line could be changed by means of the session that was still active.

SOLUTION DESCRIPTION:

Program scripts have been changed to avoid the problem of re-executing the session tdrpl0122m000 when it isn't allowed.

SITUATION IDENTIFIED IN: Maintain Replenhisment Orders (tdrpl0110m000)

SITUATION DESCRIPTION:

The customer makes use of the module Project and has a single

logistic / multi finance company situation.

There is a warehouse in logistic / finance company 100 and a project in finance

company 200.

Delivering goods from the warehouse to the project is done by using Replenishment

Orders.

The financial transaction are of the type "Issue to Project" and for the way back

"Receipt from Project".

In this situation the bookings are not always made in the right

financial company.

SOLUTION DESCRIPTION:

In the use of the Baan system you do have to setup your system

as follows.

When using Triton Project in combination with a Warehouse,

you need a 'Transit Account'.

When using a Warehouse in Company 100 and a Project in Company 200 and

transfer Goods between Warehouse and a Project,

with a Replenishment Order, the 'Transit Account' has to be in Company 100.

By 'Issue to Project', there will be the following bookings:

Transit Account company 100

to Stock company 100

Project Cost company 200

to Transit Account company 100

* this booking will also generate an intercompany booking in finance

By 'Receipt from Project', there will be the following bookings:

Transit Account company 100

to Project Cost company 200

* this booking will also generate an intercompany booking in finance

Stock company 100

to Transit Account company 100

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

SITUATION IDENTIFIED IN: tdilc1121s000

SITUATION DESCRIPTION:

Inventory blocked for inspection present in a not inspection location is allowed to be removed via inventory adjustment. This

is not correct. This inventory should remain blocked.

SOLUTION DESCRIPTION:

Now the blocked inventory for inspection present in a not inspection location is not allowed to be removed via inventory

adjustments.

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

tdB3.1b. tdB40b.

SITUATION IDENTIFIED IN:

Maintain Replenishment Order Deliveries (tdrpl0114m000).

SITUATION DESCRIPTION:

It is not possible to delete a delivery line of a RPL order when using the Baan GUI. This only occurs in objects where the ID

10222049 is present.

SOLUTION DESCRIPTION:

It is now possible to delete a delivery in the Baan GUI. This has been marked with ID 12415-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.

tdB40_b1 - tdB40_b3.

SESSION ERROR IDENTIFIED IN:

RPL0110 ("Maintain Replenishment Order Header")

RPL0111("Maintain Replenishment Orders")

RPL0114("Maintain Replenishment Order Deliveries").

SITUATION DESCRIPTION:

Due to a bad fix ID 10231215 statements in tfgld410 and tfgld416 concerning RPL orders are false.

SOLUTION DESCRIPTION:

A correction program was made that does the following:

In tabel tfgld410 and tfgld416 all records of combination replenishmentorder and Materialcosts are deleted

In table tfgld410 all records of combination replenishmentorder and issue are changed :

- the transfer status from "not for finance" to "not posted".

- the right ledger account is inserted.

- the right financial periods are inserted.

tdB40_b

SESSION ERROR IDENTIFIED IN: tdsls4102s000 "maintain sales orderlines "

SITUATION DESCRIPTION:

When a discount amount was entered the program did not take the conversion between the units into account.

SOLUTION DESCRIPTION:

The library that handles the discounts has been modified.

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

td3.1a, td3.1b, tdB40a, tdB40Lasch0, tdB40b, tdB40Lbmcr0/sch0.

SESSION ERROR IDENTIFIED IN:

tdpur4121m000 "Maintain approvals".

tdilc4123s000 "Maintain approvals (ILC)".

SITUATION DESCRIPTION:

If when you receive more than the ordered quantity you approve the total received quantity, then the approved quantity will

equal the ordered quantity. This is incorrect.

SOLUTION DESCRIPTION:

The approved quantity is now equal to the received quantity. The problem has now been solved with DF 12565-1.

SITUATION IDENTIFIED IN: Maintain Replenisment Order Deliveries (tdrpl0114m000)

SITUATION DESCRIPTION:

When you make a replenishment order for a Triton Project and you use a transit warehouse,

then the first financial transaction gets type "issue to Project", what has to be type "issue".

SOLUTION DESCRIPTION:

The first transaction between replenisment Warehouse and Transit Warehouse is now of

type 'Issue'.

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

td3.1b, tdB40b, tdB40L_b_mcr0.

SITUATION IDENTIFIED IN:

"Maintain Receipts" (tdpur4120m000).

SITUATION DESCRIPTION:

After updating multiple receipt lines, by means of the sub-session "Global Update of Receipts" (zoom to tdpur4220s000),

the screen of session tdpur4120m000 remains empty. This also occurs when the option "Fast Approval" (Cntr+Shft+O) is

used. The problem occurs both in GUI and in ASCII.

SOLUTION DESCRIPTION:

The problem has been solved, by changing the conditions for reading and displaying the main table (script tdpur4120).

Modifications in the script have been marked with DF 12507-1.

tdB40_b1 - tdB40_b3

SITUATION IDENTIFIED IN: tdpur1502m000 (Display Inquiry Lines)

tdpur1202m000 (Copy Inquiry Lines to Purchase Order)

SITUATION DESCRIPTION:

When displaying standard items that are linked to a project, the item description was not shown.

SOLUTION DESCRIPTION:

When displaying standard items that are linked to a project, the item description is now shown. There was a programming

error, which has been corrected.

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

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

SITUATION IDENTIFIED IN:

tdilc4113m000 "Maintain Receipts" (ILC).

SITUATION DESCRIPTION:

Calendar error: the calendar references a non-existing date in the year 1998.

After the goods were received they were booked to the warehouse with the date 29th August. The shelf life (in the item data -

tiitm0101m000) was set to six months. But, the date given in the system was the 29th February 1998. Since this date does not

exist, no data is shown against that stock. This prevents any transaction from taking place.

SOLUTION DESCRIPTION:

If a non-existing date is generated, then the program goes back and checks the dates until a correct date is found.

Modifications in the software components have been marked with DF12683-1.

SITUATION IDENTIFIED IN:

Maintain Receipts (tdpur4120m000, tdilc4113s000)

Approve Purchase Invoices (tfacp1140m000)

SITUATION DESCRIPTION:

The financial transaction date in table tfgld410 stays empty at the moment a transaction of type "Purchase Result" is

inserted. The consequence is, that the system can't determine the right financial period that should be used.This problem

occurs both at maintain receipts and during approving of purchase invoices.

SOLUTION DESCRIPTION:

Due to modifications in the session "Maintain Receipts" (tdpur4120m000) the DLL used to insert the financial transactions of

type "Purchase Result" (tdpurdll0020) isn't compatible anymore. To solve the problem the latest object of this DLL should be

installed. This object is available. Also a few new objects which make use of the dll should be re-installed.

You can download the solution 11900 to correct the already existing records in tfgld410. The field Transaction Date will be

update with the log date.

tdB40a, tdB40b, tdB40bmcr0.

SITUATION IDENTIFIED IN:

tdilc4201m000 (Generate Outbound Advice).

SITUATION DESCRIPTION:

Where a demand for a phantom item has components with units and rounding codes that are different from those of the main

item, it can result in the delivery of too few components. This happens when the inventory on hand for one of the components

is insufficient to meet the demand and when the rounding factor for the main item is less precise than the rounding factor

for a particular component e.g. 1.00 instead of 0.001. The final amount delivered will be determined by this rounding to

whole numbers, instead of on the creation of an outbound based on a rounding factor of 0.001.

SOLUTION DESCRIPTION:

A bad Fix code (ID 10229554) has been removed. The changes have been marked with DF 11997-1 and DF 12300-1.

tdB40a, tdB40b.

SESSION ERROR IDENTIFIED IN:

tdpur3108s000 "Maintain Discount Parameters by Contract Line".

PROBLEM TEXT:

The error message "enum constant was not found" appears.

SOLUTION DESCRIPTION:

The problem has already been solved in the B40_a2 and B40_b4 versions of the form belonging to this session.

SITUATION IDENTIFIED IN:

Maintain replenishment orders (tdrpl0110m000)

SITUATION DESCRIPTION:

It is possible to create RPL orders between projects were the company applying to these project differs without making use of

a transit warehouse. This functionality is not correct handled and should not be possible.

SOLUTION DESCRIPTION:

Now the user is not abled anymore to insert a RPL order between projects with different companies without making use of a

transit warehouse.

tdB40b.

SITUATION IDENTIFIED IN:

"Recalculate Purchase Prices and Discounts" (tdpur4810s000).

SITUATION DESCRIPTION:

A Fatal error occurs, when running the session tdpur4810s000:

"Fatal error: Arg error

tdpur.dll3005.search.price.and.discount.in.contract[271]:[STRING|FIXED|DD_NAME|BASED,expected:LONG]"

SOLUTION DESCRIPTION:

The number of arguments for tdpur.dll3005 has been extended to the point that DLL isn't compatible anymore. To solve this

problem the most recent objects of tdpur4810s000 and of DLL should be installed, to ensure that the number of arguments

matches.

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.