Solution: 126106
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
In the current BaanERP software, especially in the area of Inventory, PCS and Service, it is difficult to reconcile Financial
and Logistical figures.
SOLUTION DESCRIPTION:
To be able to reconcile the following new session are created:
- tfgld4418m100: Print PCS Project Transaction Specification
With this session specific transaction information can be retrieved from the system for PCS projects.
- tfgld4418m200: Print Inventory Transaction Specification
With this session specific transaction information can be retrieved from the system for Inventory transactions.
- tfgld4418m300: Print difference between Logist. and Finan. integr. tables
With this session all differences between records in Financial Integration tables and Logistical tables will be printed.
These new sessions can be found in the mtfgld2010m000: Financial Reconciliation.
The following sessions are adjusted:
- tipcs3480m000: Print Project Work in Process
Within this session it is now possible to select on Ledger Account for printing the WIP.
- ticst0450m000: Print Work in Process
Within this session it is now possible to select on Ledger Account for printing the WIP.
- tcfin3400m000: Print BaanService Finance Reconciliation.
Within this session it is now possible to print detailed service integration transactions.
SOLUTION CONTAINS NEW FUNCTIONALITY.
Solution: 126272
SITUATION IDENTIFIED IN:
"Connect Components to PMC Solution" (ttpmc1221m000)
SITUATION DESCRIPTION:
To add components to a PMC solution can be a lot of typing work. This typing work can be automated when all
components or ranges of components of a VRC should be connected to a PMC solution. Also a set of components can be
known already somewhere in the system, like Customization Administration, another solution, etc.
SOLUTION DESCRIPTION:
The session "Connect Components to PMC Solution" (ttpmc1221m000) offers new functionality for distributors of PMC
solutions. This session builds a new PMC solution from a list of components somewhere present in the system.
There are 5 possible sources of components:
1. Components, which exist in the Export VRC.
2. Components, which belong to another solution.
3. Components, which belong to a patch.
4. Components, which are listed in a sequential file.
5. Components, which belong to a customization project.
Various options are present to control the processing:
- Maximum number of components to be connected to one solution.
- What to do when this number is exceeded.
- Which components types.
- etc.

Solution: 127516
SITUATION IDENTIFIED IN:
"Write Off Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
Revaluation of unallocated receipt that created an unrealized gain/loss not reversed when assigned.
SOLUTION DESCRIPTION:
During the write-off of the Unallocated/Advanced Receipts/Payments, Realized currency difference accounts are used
instead of the unrealized currency difference accounts, which are mentioned in the Ledger Accounts by Business Partner
Group.
This correction program is to replace the Unrealized accounts for Unallocated/Advanced with Realized accounts.

Solution: 128865
SITUATION IDENTIFIED IN:
"Shipment lines by warehousing order" (whinh4535m000)
SITUATION DESCRIPTION:
In cross docking when 2 Inbound advices exist for a Sales order line and if only the first inbound advice had been put
away and shipment lines also would have been confirmed, then no shipping line would be created for the second inbound
advice when putting away.
SOLUTION DESCRIPTION:
Now even the second inbound advice line can also be confirmed even after the shipment lines of the first line is done.

Solution: 128922
SITUATION IDENTIFIED IN:
"Correct Sales Installment Lines History" (tdcor1008m000)
SITUATION DESCRIPTION:
This correction program checks per invoice number if processed settlements are correct counter booked in the Sales Order
Line History (table tdsls451). Before delivery of solution 127879 this could happen.
SOLUTION DESCRIPTION:
When a range of orders is entered, the correction program checks for each invoiced and processed settlement if the Sales
Order History is correct. If not, the missing records are added to Sales Order Line History (table tdsls451)

Solution: 128925
SITUATION IDENTIFIED IN:
"Print Specifications Delivered not yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
The report of session tfacr1432m000 will compare the Sales Invoice amounts with the Sales Issue amounts. For closed
Sales Orders no difference should exist while in practice in some situations an unexpected difference may occur.
SOLUTION DESCRIPTION:
A correction program has been developed to correct differences between the Sales Invoice amounts and the Sales Issue
amounts. By inserting financial integration transactions this difference is cleared.
Furthermore the COGS amounts stored on the Sales Order Line, Sales Order History Line and the Sales Order Invoice
Line are updated.
An option is available to execute this correction program in test mode. In test mode no actual table updates will be
performed. Before the correction program is executed in update mode the output reported in test mode should be
carefully analyzed.
Financial integration origins (TROR) and financial integrations types (FITR) considered by this correction program are:
- Sales / General Cost
- Sales / Direct Delivery
- Sales / Issue
- Sales / Issue (Invoiced)
- Warehousing Consignment / Issue
- Warehousing Consignment / Issue (Invoiced)
- Service / Approved for Invoicing
- Sales Invoicing (Sales) / COGS (material)
- Sales Invoicing (Sales) / COGS (operation)
- Sales Invoicing (Sales) / COGS (surcharge)
- Sales Invoicing (Sales) / COGS (general)
- Sales Invoicing (Service) / COGS (material)
- Sales Invoicing (Service) / COGS (operation)
- Sales Invoicing (Service) / COGS (surcharge)
- Sales Invoicing (Service) / COGS (general)
Several options are available when executing the correction program:
Fiscal Year/Period:
When left empty the fiscal year and period is determined based on the original transaction date of the corrected
transaction. In case the fiscal year and period are closed the transaction will be booked into the next open period based
on the parameter "Posting to next open period allowed" (tfgld4150s000) The user can overrule the automatic determination
of the fiscal year and period by filling this field on the form. Only an open fiscal year and period can be chosen.
Reporting Year/Period:
Logic identical to fiscal year/period field
Tolerance:
The allowed tolerance for the difference between the issue and COGS amounts
Correct only when difference on Specification Delivered not yet invoiced:
When this option is set no financial integration transactions will be inserted when there is no difference reported by
tfacr1432m000 on a certain interim account even though there might be a difference between the issue/COGS amount
stored in logistics and finance.
Consider Delivered:
When this option is not selected a possible difference between the issue amount in finance and logistics is not corrected.
Consider Invoiced:
When this option is not selected a possible difference between the COGS amount in finance and logistics is not corrected
Update mode:
Determines whether this correction program is executed in test or update mode
Currency:
The currency in which the found differences should be reported. In an Dependent or Single currency system this will
always be the reference currency. The "rotate currency" button is only enabled in an Independent currency system, which
will allow the user to rotate between the different defined home currencies.
Some things have to be taken care of when executing this correction program:
1) Execution in Job mode
When executing the correction program in Job mode care has to be taken when selecting a device of type 'file' (when
selecting an actual printer device the issue described below is not applicable). This is because the correction program will
report the corrected data in two separate reports, while when running in Job mode only one output file can be specified. To
prevent both reports do overwrite each other a device of type 'append to file' has to be chosen. The second report output
will then be appended to the first report output in the same output file.
2) Archiving
Once the sales order history is archived this program is not able to correct the financial transactions anymore. Archived
Sales Order history lines will just not be considered.
The inventory transactions stored in Warehousing are also needed by this correction program and can be archived as well. In
case an issue/receipt is selected (as it still exists in the sales order history) for correction while the transaction date Is
before the last archiving date a message will be displayed and the correction is skipped.
Furthermore the financial integration transactions can have been archived which are needed to be able to correct as well.
Since its not possible to determine whether a certain financial integration transaction is just missing or archived care has
to be taken with this scenario as the correction program is not capable of preventing unnecessary insertion of archived
transactions. So incase the correction program inserts integration transactions before the last archive action those orders
should be skipped manually.
Solution: 129187
SITUATION IDENTIFIED IN:
"Projects" (tppdm6100s000)
SITUATION DESCRIPTION:
When inserting a project and the parameter "Use Project Archive" in session tppdm0100m000 ("General Parameters") is
switched on, the wrong logistic company was filled in table tppdm790 "Archived Projects". This caused reference-error
206 when deleting the project. This only occurred in a multi-finance setup.
SOLUTION DESCRIPTION:
The correct company is now being used to fill table "Archived Projects".

Solution: 129416
SITUATION IDENTIFIED IN:
"Archive Projects" (tppdm7820m000)
SITUATION DESCRIPTION:
When new standard items and new surcharges on these standard items are added, the next run of session "Archive
Projects" (tppdm7820m000) gives a reference error (Error 606) if the option "General Data" is checked.
SOLUTION DESCRIPTION:
The order in which the different tables were archived was wrong.
Now the Item Project Data is archived before the Standard Surcharges by Material, and therefore references are OK now.

Solution: 129433
SITUATION IDENTIFIED IN:
"Shipment lines by warehousing order" (whinh4535m000)
SITUATION DESCRIPTION:
In cross docking when 2 Inbound advices exist for a Sales order line and if only the first inbound advice had been put
away and shipment lines also would have been confirmed, then no shipping line would be created for the second inbound
advice when putting away.
SOLUTION DESCRIPTION:
Now even the second inbound advice line can also be confirmed even after the shipment lines of the first line is done.

Solution: 129588
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A sales order is maintained with some lines. Now, if the user wants to modify the header field shipping constraint from
none to order complete, then the system gives the message "shipping constraint not allowed" and the system will not
allow, to change the field even when lines attached are not been released.
SOLUTION DESCRIPTION:
The system will allow the user to change the header field 'shipping constraint' from 'none' to 'order complete', when lines
attached are not been released.

Solution: 129735
SITUATION IDENTIFIED IN:
"Correct Incorrect Contract Data" (tdcor0013m000)
SITUATION DESCRIPTION:
The Linked Order Data (tdsls402) table was updated with wrong contracts, before Solution 127633. This in turn corrupted
the Sales Order History (tdsls451), Contract (tdsls301), and Contract History (tdsls301) tables, when Back Order was
maintained, and shipments confirmed.
Correction program required for correction of incorrect contract data in Sales Order History (tdsls451), Contract
(tdsls301), and Contract History (tdsls301) tables.
SOLUTION DESCRIPTION:
Correction program available for correction of incorrect contract data in Sales Order History (tdsls451), Contract
(tdsls301), and Contract History (tdsls301) tables.
The Correction program has been provided with the option to run in 'Test Run' mode, and 'Update' mode. The user could use
the 'Test Run' mode to check the correctness of the data, and use the 'Update Run' to run the Update the tables.
Introduction
==========
There are more than one Sales Order Lines in an Order, and one or more of them have a contract attached to them. In such
cases, the consecutive lines of the Sales Order, which do not have a contract attached to them, are also attached to the
contract of the recent Sales Order Line, which has a Contract attached to it.
The Defect is solved under Solution 127633.
Table (field) s involved
==================
Called Quantity (tdsls301)
Called Amount (tdsls301)
Invoiced Quantity (tdsls301)
Invoiced Amount (tdsls301)
Full Record (tdsls351)
Contract (tdsls451)
Position Number (tdsls451)
Ranges and options
================
The correction program provides following selection ranges and options:
Range Sales Order From/To
Range Sales Order Position From/To
Option to select if Test Run of Definite Run should be performed
Option to select if the link for Contracts with Price Group should be removed
Reporting
========
Three reports are generated.
1. For printing the Corrected Order History records.
- All the Sales Order History lines that have a wrong contract attached to them, in the selected range, are printed. The
wrong contract number and the position are also printed in this report.
2. For printing the Deleted Contract History records.
- The incorrect Contract history records for the Order Number in the selected range are printed in this report.
3. For printing the Corrected Sales Contract records.
- The contract lines which are attached to the Sales Orders in the selected range, and that are updated with the wrong
Called Quantity, Called Amount, Invoiced Quantity and Invoiced Amount are printed in this report.
Limitations
========
The correction program will remove all the links of the contracts that have been wrongly linked. The conditions that are
checked are the Supplier, Item, and Start and End Dates of the Contract. If any of these do not match, then the link is
removed.
One limitation, however, is the check on whether the contract is activated or not. This has not been checked, as every link
in the Linked Order Data table (tdsls402), that has a contract attached might be activated and de-activated several times.
Checking this requires the History records to be read several times. Reading history tables affects the performance to a
large extent, and
more so when the History has to be read several times. Moreover, this does not have a major impact on the wrongly
linked Order data.
If the Contract is for a Price Group, instead of an item, the Price Group of the Item is selected. Check on the validity of
the contract for the Sales Order Line is checked for the Price Group instead of the item. There is a
chance that the Price Group of the Item is changed, and the Price Group in the contract no more holds good for the Item
Group chosen earlier. In this case, the Contract with the Price Group would be corrected incorrectly. A
check box has been provided to give the option to the user (Check Contracts for Price Groups), to avoid deletion of such
incorrect links.
In such cases, it would not be possible to delete the contracts that have an Item for which the Price Group is changed.

Solution: 129767
SITUATION IDENTIFIED IN:
"Inventory Transaction By Item and Warehouse" (whinr1510m000)
SITUATION DESCRIPTION:
In the session "Initiate Inventory Issue" if the 'Issue date' is set to be in the past, 'Transaction date' in session
whinr1510m000 is recorded not as specified in 'Issue date', but as the date of running session "Initiate Inventory Issue"
(that is current date).
SOLUTION DESCRIPTION:
Now the Transaction date date is the one which we specify while Initiating Inventory issue , (i.e) actual delivery date

Solution: 129880
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
The Negative Production/Issue transactions could be written to the wrong Finance Company in case the quantity received
exceeded the quantity issued and the cost price had been recalculated after the issue.
Correction program whcor0119m000:
The integration transactions Production / Issue could be incorrectly generated in the following situation:
1. Issue materials for a production order.
The valuation method for the issues item for the issuing warehouse is FTP.
2. Create a negative issue (a Receipt thus) that exceeds the preceding material issue.
3. Recalculate the cost price of the item issued.
4. The receipt transactions created for the receipt quantity calculated as "total received quantity - issued quantity", were
booked with:
Transaction Origin: Warehouse (Valuation) instead of Production
Financial Transaction:
Revaluation instead of Issue
Warehouse Surcharge(Issue)
Item Surcharge(Issue)
SOLUTION DESCRIPTION:
The Production/Issue Transactions will be booked to the right Finance Company.
Correction Program whcor0119m000
IMPORTANT NOTE:
The program must be executed by Logistic Company.
The correction program whcor0119m000 will correct these transactions according to the following procedure:
1. Warehouse (Valuation) / Revaluation Transactions:
These transactions should have been booked as Production / Issue transactions.
The correction program will thus create negative bookings for the incorrect warehouse revaluation (so that these
transactions can be reversed).
New Production / Issue Transactions will be created based on the erroneous Warehouse (Valuation) / Revaluation
bookings.
2. Warehouse (Valuation) / Warehouse Surcharge(Issue) Transactions:
Warehouse (Valuation) / Item Surcharge(Issue) Transactions:
This is not an allowed combination. These transactions will thus be deleted from the Integration transaction tables
(tfgld418/417/415/416/410).
Creation of the integration transactions:
Warehouse (Valuation) / Revaluation Transactions:
The debit and credit line are booked with:
- the finance company linked to the warehouse for which the transaction is processed
- the project number defined in the item code
Production / Issue Transactions:
The Debit line is booked with:
- the finance company linked to the calculation office filled in the production order for which the transaction is processed
- the project number defined in the production order
The Credit line is booked with:
- the finance company linked to the warehouse for which the transaction is processed
- the project number defined in the item code
Example:
Manufactured Item 98800040/0700
Components:
98800040/023 (Purchase PCS Item)
023 (Standard Item)
Both items are issue from the warehouse 004 linked to the finance company 100.
The calculation office of the production order is linked to the finance company 300.
When processing the a Production Issue of both material, the bookings Production/ Issue would be created that way:
Item 023
Debit Line:
Project = 98800040
Finance Company = 300
Credit Line:
Project = empty
Finance Company = 100
Item 98800040/023
Debit Line:
Project = 98800040
Finance Company = 300
Credit Line:
Project = 98800040
Finance Company = 100
When processing the a Revaluation of both material, the bookings Warehouse (Valuation) / Revaluation Transactions
would be created that way:
Item 023
Debit Line:
Project = empty
Finance Company = 100
Credit Line:
Project = empty
Finance Company = 100
Item 98800040/023
Debit Line:
Project = 98800040
Finance Company = 100
Credit Line:
Project = 98800040
Finance Company = 100
Options:
FORM1:
Selection Based on Fiscal Year/Period:
The Integration transactions will only be selected based on the fiscal year and period filled in the form2.
If this option is set to No, the Integration Transactions can then be selected based on:
- the production order numbers and
- the project numbers.
These options are available on the form3.
Specify Project:
This option has been added for performance reasons.
When processing a Warehouse (Valuation) / Revaluation Transaction, the project number is only filled in if the item for
which the transaction is created is a customized item (project segment filled in).
Filling in the project field would only make sense if:
- the erroneous integrations relates to a production order created for a customized item
- the negative production issue has been created for a customized component.
If this kind of transaction does not need to be corrected, set the field Specify Project to No (the project field will then be
blank when selecting the Integration Transactions).
Options on Form2 and Form3:
Test Run:
If this option is set to Yes, the report will print the incorrect Integration Transactions that need to be corrected.
If the field is set to No, the Integration Transactions will be corrected. Note that the correction executed will not appear on
the report.
The report will only show the corrected Integration Transactions.
Perform Corrections with original transaction date:
If this option is set to Yes, the correction bookings will be created with the transaction date of the corrected record as
transaction date.
If this option is set to No, the correction bookings will be created with actual date as transaction date.

Solution: 129886
SITUATION IDENTIFIED IN:
"Process Cycle-Counting/Adjustment Orders" (whinh5201m000)
SITUATION DESCRIPTION:
When a stock point exists in a storage unit (with or without package definition) different from the inventory unit and a
cycle-counting order is processed with no variance for that stock point, no cycle-counting data is recorded for that stock
point, hence no "last counting date" exists in session "Cycle counting data" (whinh5540m000).
SOLUTION DESCRIPTION:
Cycle counting data will only be deleted after processing an adjustment/cycle counting order when there is no inventory in
any unit left for the counted stock point.

Solution: 129938
SITUATION IDENTIFIED IN:
"Outbound advice" (whinh2125s100)
SITUATION DESCRIPTION:
Once the over delivery functionality was introduced, the following old data were not updated.
- The sales order line history was not updated in case of over deliveries and split shipments.
- The called quantity was not properly updated in case of over deliveries took place.
SOLUTION DESCRIPTION:
A correction program has been created. In the session there are two flags, which determines whether the user wants to correct
the sales order line history or the contract called quantity. Based on these flags, the sales order line history will be
corrected. First the sales order line table (tdsls401) will be read only for sales order for which the ordered quantity
exceeds zero. This is because no over deliveries are allowed for return orders. In case the backorder is different than zero
the ordered quantity used for updating the history will be the delivered quantity, otherwise it will be the ordered quantity.
The last history record booked for this sales order will be selected.
If the program detects that over deliveries took place for a particular sales order, the history record will be
counter booked, by using the original ordered quantity, and then booked by using the new ordered quantity which includes
the over delivered quantity.
The sales order history will also be corrected in case the shipment got split. The problem was that the total line was not
counter booked from the history and the detail lines were not booked in the history table. This situation will be also
corrected through this program. The program will counter book the total line and afterwards it will book all detail lines,
which are the split shipments. Appropriate messages are printed in the report to indicate the user which action was
performed by the program. The data will be committed in case the test run flag is not checked.
If the user has selected the flag for correcting the called quantity, the system will search all contracts specified in the
selection range. The called quantity will be calculated based on orders, which are not processed yet. If this quantity and
amount differs from the called quantity and amount in the sales contract, then the data will be updated.
The data will be committed in case the test run flag is not checked.

Solution: 130030
SITUATION IDENTIFIED IN:
"Generate Inbound Advice" (whinh3201m000)
SITUATION DESCRIPTION:
When an inbound line is registered with a package definition with certain dimensions (width, depth, height) and a second
line exists for another item without any package definitions, the system keeps the dimensions of the package definition
when generating the inbound advice for the second line. As a result, wrong dimensions are taken into account and the second
line is advised to irrelevant locations, depending on the available location capacities.
SOLUTION DESCRIPTION:
Values of Package Definition have been initialized. This will make sure that the correct dimensions are used when
choosing a location.

Solution: 130044
SITUATION IDENTIFIED IN:
"Maintain Projects" (tppdm6100m000)
SITUATION DESCRIPTION:
The following functional enhancement was requested:
When linking a sub-project to a main-project a question should come up asking if the customer data should be copied
from the main project.
SOLUTION DESCRIPTION:
The requested functionality is built in. When a sub-project is linked to a main-project the question comes up. When
answered with "Yes" the customer-data from the main-project is copied.

Solution: 130047
SITUATION IDENTIFIED IN:
"Easy Warehousing Order Entry" (whinh2202m000)
SITUATION DESCRIPTION:
Locking problem when re-using run number.
SOLUTION DESCRIPTION:
Removed setting of application lock when re-using run nmber.

Solution: 130063
SITUATION IDENTIFIED IN:
"Planned Material Transactions" (tppss6500m000)
SITUATION DESCRIPTION:
Processing of a Request For Quotation (RFQ) into a purchase order, doesn't cancel the 'planned receipt' within the project
requirements. Therefore, the PRP is taking both the quantity ordered through RFQ and the purchase order into account.
This is incorrect.
SOLUTION DESCRIPTION:
When we create a RFQ through a project and convert it to a purchase order in order management, the RFQ line is deleted
from the planned material transactions session as soon as the purchase order is created.

Solution: 130166
SITUATION IDENTIFIED IN:
"Sales Contracts" (tdsls3100s000)
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
It is not possible to enter a Consignment Invoicing order type on a Sales Contract (session tdsls3100s000).
SOLUTION DESCRIPTION:
A Consignment Invoicing order type can be entered on a Sales Contract.
When a not Consignment Invoicing order type on the sales order header gets overwritten with the Consignment Invoicing
order type from a Sales Contract, the warehouse is changed to the Consignment Warehouse.

Solution: 130172
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
The capacity use of Planned Orders is not consistent with the capacity use of SFC-Orders.
When using Calendars with long intervals (year), and a scenario, which ends 'early' in the year, fatal errors can occur
during the update of planned orders.
SOLUTION DESCRIPTION:
Capacity use of Planned Orders is consistent with capacity use of SFC-Orders.
(Capacity is only available/used between the scenario start- and finish date.)

Solution: 130182
SITUATION IDENTIFIED IN:
"Generate Progress from Planning" (tpppc1240m000)
SITUATION DESCRIPTION:
1.If "Child charge element" is above the "Parent charge element" in the in the alphabetical sequence, then progress of child
is overwritten with that of parent.
If the child is below the parent in alphabetical sequence, then child gets it's own progress.
The first situation is not correct as the "Child" can have it's own progress independent of the parent.
2. The process of updating progress in itself is also inefficient, as it requires about 6 hrs for the customer to update
progress.
SOLUTION DESCRIPTION:
The above problems have now been corrected and now the child will get it's own progress independent of it's alphabetical
order with respect to it's parent.
Also, this solution will take care of performance problems.

Solution: 130185
SITUATION IDENTIFIED IN:
"Process Quotation to Contract" (tsctm2200m000)
SITUATION DESCRIPTION:
Processing a quotation to a contract, for which a maintenance planning exists gives the following error message "Planned
Activity should start during Contract Period". However, all planned activities fall within the contract period.
SOLUTION DESCRIPTION:
The error message was displayed when there are planned activities within the contract period, which are not yet set to status
final.
Therefore we changed the error message to indicate the exact error.
The error message has been changed to "The planned activities for Configuration are not final".

Solution: 130204
SITUATION IDENTIFIED IN:
"GRNI Sessions" (GRNI Sessions)
SITUATION DESCRIPTION:
Several problems were logged:
All Versions:
- Amounts of session tfacp1432m000 "Print receivable Invoice Specifications" were incorrectly calculated due to PUR
rate type and INT rate type.
- Because the option "Based on values in ACP in session tfacp1438m000 "Print Receivable Invoice Checklist" is the same
functionality as the session tfacp1432m000 "Print receivable Invoice Specifications", the scripts should be moved to a
DLL.
- Session tfacp1438m000, tfacp1432m000 and session tfacp1439m000 read the rate tables in order to get the correct internal
rates. However rates can be anti dated and therefore the internal rate should be stored in the logistic tables.
SOLUTION DESCRIPTION:
- Rates are stored now in the logistic tables as soon as a receipt is done
- Old transactions read the currency rate from the currency rate tables, new transactions read the rate in the logistic tables
for receipts
- The functionality of tfacp1432m000 is moved to a DLL because the checklist tfacp1438m000 uses the same
functionality.
- Improved the calculation of logistic receipt and approval amounts.
- Table changes of table tfacp245 were delivered via solution 132323. The field business partner is added to the table.
This solution delivers a correction program (tfcor2245m000) to fill the business partner.
Solution: 130206
SITUATION IDENTIFIED IN:
"Close Production Order" (ticst0201m000)
SITUATION DESCRIPTION:
When closing a production order, a float exception message due to a division by zero is given.
SOLUTION DESCRIPTION:
When the subcontracting factor is determined the calculation is corrected.

Solution: 130216
SITUATION IDENTIFIED IN:
"Print Customer's Total Balance by Company" (tfacr2434m000)
SITUATION DESCRIPTION:
Customer name does not appear on report when "totals after groups" = "Yes". The problem occurs only when the customer
name is similar for consecutive customers.
SOLUTION DESCRIPTION:
Customer name appears on report

Solution: 130220
SITUATION IDENTIFIED IN:
"Payments on Purchase Invoices" (tfacp2523m000)
SITUATION DESCRIPTION:
The problem only occurs in a multi site environment.
The check number is not printed when tfacp2523m000 (Payments on Purchase Invoices) is used in the company (group
company) where a payment is created and finalized.
(The payment should contain invoices of companies.)
However, when tfacp2523m000 is used in another company with invoices that are paid in the group company, the check
number is printed.
SOLUTION DESCRIPTION:
After installing this solution the check number is printed when printing invoices of the group company with session
tfacp2523m000 (Payments on Purchase Invoices).

Solution: 130221
SITUATION IDENTIFIED IN:
"Print Purchase Receipts" (tfacp1430m000)
SITUATION DESCRIPTION:
A new option to filter "Receipt Date" required in report "Print Purchase Receipts".
SOLUTION DESCRIPTION:
A new filter on "Latest Receipt Date" has been added on the session.
It will only be triggered on the LAST receipt-date of the order-line.

Solution: 130225
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
Fatal Error 206 "Record is not locked" when changing run number inside outbound advice.
SOLUTION DESCRIPTION:
Record lock is re-done and a fatal error is prevented.

Solution: 130232
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When running session "Register Purchase Invoices - tfacp1110s000" and it is mandatory to fill reason to payment (foreign
pay-to address involved) the message "Reason for Payment not filled" is not stated.
SOLUTION DESCRIPTION:
When running session "Register Purchase Invoices - tfacp1110s000" and it is mandatory to fill reason to payment (foreign
pay-to address involved) the message "Reason for Payment not filled" is stated.

Solution: 130235
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2121s000)
SITUATION DESCRIPTION:
Material lines that have delivery type "To Warehouse" or "To Warehouse by Transport" are excluded from contract,
warranty, and quotation coverage when these lines have been entered manually.
However, when a line with one of these delivery types is created automatically, it can be included in coverage because the
financial handling of this line is done on the related line with the delivery type "From Warehouse" or "By Purchase
Order".
SOLUTION DESCRIPTION:
If applicable, the coverage flag for contract, warranty, or quotation will be enabled also for delivery types "To
Warehouse"and "To Warehouse by Transport". It will not be defaulted to "Yes" (like it is done for other delivery types).
Logic is so as not to change functionality for customers who appear to be satisfied with the current functionality, i.e.
repairables and scraps do not influence any coverage.
Note:
If, for non-consumed items, the return is done in another order, there is no automated method that will make sure things
match exactly as in the original order. Therefore it is better to use the 'automated' method.
Properties to be matched manually are at least:
- Coverage date/time
- Cost Component
- Rate Determiner
- possible exchange rate differences

Solution: 130237
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When changing sales orders via the order change message, and the delivery date field (tdsls400.dddat, tdsls401.ddta) was
not filled, the check if receipt date is before delivery date was not executed. Hence, sales orders got wrong dates.
SOLUTION DESCRIPTION:
The program script has been corrected. Even if the delivery dates are empty in the incoming ASCII file, the check if
receipt date is before delivery date is executed and the appropriate error message is generated.

Solution: 130240
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1. Error message "EU tax code not defined" comes up even when it is not appropriate.
2. Wrong tax code picked up. As soon as item code is entered, system picks up a tax code based on the address of the
purchase office. Later on the same vat code stays on, even though the delivery address of the warehouse is different.
3 There was no check done for the dimension fields when we use the EQUIPMENT item. It was possible to enter any
value in those dimension fields, as there was no check.
SOLUTION DESCRIPTION:
1. Now the error message does not come up, unnecessarily.
2. Now the correct vat code is picked up.
3 The check has been added for equipment item also.

Solution: 130241
SITUATION IDENTIFIED IN:
"Print work centers" (tirou0401m000)
SITUATION DESCRIPTION:
While printing the work centers using report "Work centers by work center type", the field critical in master planning is
always printed as 'NO' even though the work center is defined as critical in master planning.
SOLUTION DESCRIPTION:
System will print the critical in master planning field correctly, while printing the work centers with "Work centers by
work center type".

Solution: 130246
SITUATION IDENTIFIED IN:
"Copy Element-Budget Data" (tpptc1245m000)
SITUATION DESCRIPTION:
If a budget line (either Material/Equipment/Subcontracting) has a "Cost Object" that has some signal code, the user
expects that the information about the existence of such signal code be given to him when he copies budget data from one
element to another element.
If such information is not given while copying, then he will know it at much later stage (like when making a purchase
order for the item).
SOLUTION DESCRIPTION:
Now, if any cost object (Material/Equipment/Subcontracting) has signal code, a report will be printed indicating the
same while copying the element budget data to another element.

Solution: 130247
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
Several variances are processed at the same time. Some variances cannot be assigned to inventory so a value correction
is created. However in "Inventory Receipt Transactions" (whina1512m000) new records are inserted with the flag
variance assigned with an empty order number and an amount of 0 and a MAUC value of zero.
SOLUTION DESCRIPTION:
Whenever a new warehouse - item combination is encountered within the to be processed Inventory Variances range a new
entry in the "Inventory Receipts Transactions" is created. This is not correct it should only happen when there is still
inventory available.
Also the valuation corrections in finance should only be added if a correction is needed.
Modifications implemented to make sure new entries are created when it is needed.

Solution: 130249
SITUATION IDENTIFIED IN:
"Components by Solution" (ttpmc1120s000)
SITUATION DESCRIPTION:
PMC gives no warning or error message when you add a component to a solution with a component code that is too long.
PMC checks the presence of the component, but ignores the characters that are beyond the normal length of the code of
the particular component type.
Example: A message code is 12 characters long, e.g. "com123456789". When you enter "com1234567890" this is accepted,
although this message doesn't exist.
SOLUTION DESCRIPTION:
PMC checks now if you don't enter more characters than are allowed for the component type.

Solution: 130258
SITUATION IDENTIFIED IN:
"Maintain Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Fatal Error 205 comes up when confirming receipts for a return sales order in a triangular invoicing scenario.
SOLUTION DESCRIPTION:
Now the Fatal Error doesn't occur while confirming the receipts for return sales order .

Solution: 130263
SITUATION IDENTIFIED IN:
"Copy Software Components to Package VRC" (ttadv6265m000)
SITUATION DESCRIPTION:
Package 'From' field is not defaulted to the 'To' value when entering a range in session 'Copy Software Components'
SOLUTION DESCRIPTION:
Now when a user changes the value of the Package 'From' value, this new value is defaulted to the Package 'To' field.

Solution: 130267
SITUATION IDENTIFIED IN:
"Generate Purchase Order Advice for Sales Order" (tdsls4240m000).
SITUATION DESCRIPTION:
Position numbers of Order Lines are not defaulted in 'from - to' fields of session "Generate Purchase Order Advice for
Sales Order" (tdsls4240m000) when called from session "Sales Order Lines" (tdsls4501m000).
When selecting a range of Sales Order Lines, one has to enter the Position numbers manually.
SOLUTION DESCRIPTION:
The 'from - to' fields of session "Generate Purchase Order Advice for Sales Order" (tdsls4240m000) are filled with the
right Position numbers of the Order Lines that were selected in session "Sales Order Lines" (tdsls4501m000).

Solution: 130281
SITUATION IDENTIFIED IN:
"Object Relations" (tscfg2510m000)
SITUATION DESCRIPTION:
When using the 'zoom down' option in the specific menu of session "Object Relations" (tscfg2510m000), not always the first
line is displayed. The user has to scroll up to see the first line.
The same happens in session "Service BOMS" (tscfg1510m000)
SOLUTION DESCRIPTION:
When using the 'zoom down' option in the specific menu all lines are displayed, starting with the first line.

Solution: 130316
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2121m000)
SITUATION DESCRIPTION:
Excluding material cost term or a tooling cost term in a warranty or contract does not work properly in the following
case.
Define an include cost term for an item cost component combination and an excluding cost term for the same cost
component.
When using this cost component on a service order actual material line, no coverage should be granted.
SOLUTION DESCRIPTION:
No coverage will be granted for excluded material or tooling.

Solution: 130321
SITUATION IDENTIFIED IN:
"Print Payment Advice" (tfcmg1401m000)
SITUATION DESCRIPTION:
Original company is not being printed in the report "Print Payment Advice by Pay-to Business Partner".
SOLUTION DESCRIPTION:
Now Original company is getting printed in the report "Print Payment Advice by Pay-to Business Partner".

Solution: 130323
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
During a registration of a payment within session 'Bank Transaction' (tfcmg2100s000) or assigning of a payment to a
purchase invoice within session 'Assign Unallocated/Advance payment to invoices' (tfcmg2106s000/tfcmg2119s000 (B50
only)), no warning message is given when a blocking code is present on the purchase invoice. This is useful information
for the Administrator in case the purchase invoice is not paid through the payment procedure within Baan but collected by
the supplier.
SOLUTION DESCRIPTION:
Message 'Blocking code present for invoice' is given when:
- A supplier transaction is done for an invoice with a blocking code within session 'Bank Transactions';
- An (automatic) assignment is done for an invoice with a blocking code within session 'Assign Unallocated/Advance
payment to invoices';
- (B50 only) an assignment is done for an invoice with a blocking code within session 'Enter payment amounts for
assignments'.

Solution: 130324
SITUATION IDENTIFIED IN:
"Delete/Terminate Purchase Contracts" (tdpur3203m000)
SITUATION DESCRIPTION:
1. There is a purchase contract and a Purchase order Line is linked to this contract.
2. This Purchase Order Line is fully received and then processed fully, but not yet deleted with the status of the line being
"Deleting Lines'
3. The Purchase contract is Evaluated and Terminated.
4. The contract is now deleted from the session "Delete/Terminate Purchase Contracts" (tdpur3203m000). But, the contract
is not deleted and also no error message is displayed to the user.
SOLUTION DESCRIPTION:
The purchase order line that is linked to the contract is not yet deleted. This is the reason why the contract is not
deleted. The user is now displayed with the error message ""Current Orders for contract line still present"

Solution: 130336
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
1) When tabbing over the currency field without changing this field and a manually rate inputted the rate will change back
to the default rate.
2) When the fields: "Amount", "Currency" and "Rate" are filled, and enter the tab key the home currency amount is not
displayed. It remains zero.
3) After changing the Pay-To Business Partner, there is no message 'Reason for Payment not filled' when no reason filled.
SOLUTION DESCRIPTION:
1) When tabbing over the currency field without changing this field and a manually rate inputted the rate will remain the
inputted rate,
also after saving.
2) When the fields: "Amount", "Currency" and "Rate" are filled, the home currency amount will be always displayed.
3) After changing the Pay-To Business Partner also the correct country will be fetched.
So, afterwards also the field Reason for Payment will be checked against the correct country-code.

Solution: 130342
SITUATION IDENTIFIED IN:
"Generate Invoice by Self billing" (tfacp2290m000)
SITUATION DESCRIPTION:
When Terms of Payment is not specified for an order, while self billing this order, the terms of payment belonging to
previous order number was picked up.
SOLUTION DESCRIPTION:
This situation has been corrected. Now, the terms of payment is picked up from the current purchase order, and if not
specified, from the Business partner.

Solution: 130343
SITUATION IDENTIFIED IN:
"Generate Availability Planning" (titrp1213m000)
SITUATION DESCRIPTION:
After generating 'Tools Requirement Orders' from planned 'Recourse Requirement Orders' (EP package) the tool usage is
incorrect.
For every day the total tool usage of the order is used instead of the tool usage a day. Because of this issue, the
availability check will give a report with shortages for the tool.
SOLUTION DESCRIPTION:
The tool usage is calculated per day. For this calculation, the calendar from the work center is used to determine the
working hours.
With the production rate of the operation and working hours is the tool usage calculated.

Solution: 130355
SITUATION IDENTIFIED IN:
"Print Program Structure Diagram" (ttadv2430m000)
SITUATION DESCRIPTION:
While running session ttadv2430m000 (Print Program Structure Diagram), for some scripts the following error will be
displayed:
index 0 out of dims 1 [2000].
For example library td boidll0010 in Baan IV will result in this error message.
SOLUTION DESCRIPTION:
The problem was caused by the placing of opening brackets "(". When an opening bracket was placed immediately after a
keyword (for example "if" or "while"), the program did not recognize this keyword. This has been modified: the
keywords are now recognized.
Now the Program Structure Diagram is printed without the index out of dims-error.

Solution: 130359
SITUATION IDENTIFIED IN:
"Update Vendor Rating" (tdpur8850m000)
SITUATION DESCRIPTION:
1 Cost Performance calculation is incorrectly done if the Item-Purchase currency and Reference Currency are same, but
Purchase Order currency is different.
2 While running Vendor Rating, unwanted error report created for Average Purchase Price being 0 though Cost
Performance calculation is implemented in Vendor Rating Parameters.
SOLUTION DESCRIPTION:
1 Cost Performance Rating calculation is done correctly if Purchase Order currency and Reference currency are
different.
2 If Cost Performance parameters are not used in Vendor Rating parameters, then unwanted error messages are not
printed in report.

Solution: 130368
SITUATION IDENTIFIED IN:
"Print Registered and Matched Purchase Invoices " (tfacp1433m000)
SITUATION DESCRIPTION:
When an invoice is approved in period one and unapproved in the next period, when printing the report Print Registered
and Matched Purchase Invoices (tfacp1433m000) for the period one, the invoice is shown as not approved.
SOLUTION DESCRIPTION:
Now, if an invoice is approved in a specific period, the session Print Registered and Matched Purchase Invoices shows
those invoices approved in that period, even if they are unapproved later.
Please note that, this solution becomes active only when the new table definition has been created, and also the new table
has been created. After this the correction program tfcor1826m000 should be run to populate this table.
Solution: 130378
SITUATION IDENTIFIED IN:
"Process Financial Statement Values" (tffst1205m000)
SITUATION DESCRIPTION:
Records are not inserted in the table "Maintain Financial Statement Values" when a second Financial Statement is
selected for processing without closing the session "Process Financial Statement Values"
SOLUTION DESCRIPTION:
Now, records are properly inserted when another Financial Statement is selected for processing without closing the
session "Process Financial Statement Values"
Solution: 130379
SITUATION IDENTIFIED IN:
"Purchase Requisition lines" (tdpur2102s000)
SITUATION DESCRIPTION:
When the purchase requisition is created, by default warehouse is filled by taking from item purchase data the session
"Item Purchase Data" (tdpur0501m000) and while entering Project, an error message pops up that warehouse not
allowed.
SOLUTION DESCRIPTION:
Now, if the project is filled, then the warehouse field will be kept blank. If the project is removed then the normal
warehouse will be filled.

Solution: 130383
SITUATION IDENTIFIED IN:
"Print Consignment Inventory and Usage" (whinh2440m000)
SITUATION DESCRIPTION:
Entered range of business partners is ignored.
SOLUTION DESCRIPTION:
Check on business partner range implemented.

Solution: 130385
SITUATION IDENTIFIED IN:
"Service Order Activities" (tssoc2110s000),
Online Manual Topic (OM000051).
SITUATION DESCRIPTION:
Online manual help topic "OM000051" gives an unclear explanation of the usage of the 'Blank Availability" type in
iBaanERPService.
You can find this help for example by using the following steps:
1) On tab Times in session "Service Order Activities" (tssoc2110m000), view the help one of the times fields.
Click on topic Planned start/finish time for service order (activity) controlling.
2) Go the bottom of this text and click on topic "Calendars in Service, using ".
SOLUTION DESCRIPTION:
Online Manual topic "Calendars in Service, using" has been revised.

Solution: 130401
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Descriptions:
- Defect 210557 AFS bitsets are now handled by api/afs
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 130411
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
"Index 3 out of dims [1] 2" error when processing tax invoices in multi site environment. This happens only when
VERTEX is ON.
SOLUTION DESCRIPTION:
Now the error does not arise.

Solution: 130413
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
If the Invoice date in session Compose/Print/Post or the Transaction Entry date in the session Compose/Print/Post or in
session Post Invoices is made empty, then no posting takes place and wrong error report is displayed.
SOLUTION DESCRIPTION:
Now when the Transaction Entry date or the Invoice date is made empty a message that the Date should not be empty is
displayed. It is compulsory to have a date in these fields.

Solution: 130414
SITUATION IDENTIFIED IN:
"Compose/print/post invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Sales listing was not updated for triangular or bilateral invoice.
SOLUTION DESCRIPTION:
Sales listing are updated correctly in case of triangular or bilateral invoice

Solution: 130421
SITUATION IDENTIFIED IN:
"Copy Sales Contracts" (tdsls3801m000)
SITUATION DESCRIPTION:
When copying a contract only for the first line the new Effective and Expiration date are filled in correctly. For the other
new lines the dates are identical to the original contract.
SOLUTION DESCRIPTION:
For each line the Effective and Expiration dates are taken from the form. Also the Creation date was not always correct.
Now the date, when copying the contract, is filled in for the creation date of the new contract.

Solution: 130422
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
After installing solution 117155 there are now much more entries shown in the tree of the Dynamic Menu Browser.
SOLUTION DESCRIPTION:
There was a problem in the Dynamic Menu Browser (DMB), that when a role was linked excluded to a Business Process,
but in a sub Business Process that was changed for 1 activity, then that activity did not show up in the DMB.
This happened only, when the View menu option "Main Business Processes" was checked.
To fix this, a solution(117155) is build, to show every activity in a Business Process, which is a link to another Business
Process in the DMB.
That way the activities with changed authorization would not be missed anymore.
The result is more entries of type Business Processes in the tree of the DMB.
With this solution a new View menu option in the DMB is introduced.
The new view option is located below the option for "Main Business Processes" and is called "Show excluded sub
Business Processes".
When this option is checked, then the tree in the DMB will be as before the implementation of solution 117155.
When this option is unchecked, then sub Business Processes, to which a role is linked with the excluded property, will not
be shown in the
tree in the DMB.
The consequence will be, that activities in sub Business Processes of that excluded Business Processes, for which the
authorization was changed, will not be shown in the tree of the DMB anymore. And then the end-user cannot activate
them anymore from the DMB.

Solution: 130423
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When receiving a sales order containing addresses that have more than one geo code assigned to it (a valid geo code is
passed in the ASCII file), the system errors out with error "Invalid address information. Unable to assign GEO code to
address."
SOLUTION DESCRIPTION:
The system could not assign the values for geo code read from the ASCII file. The program script has been modified. The
values for geo code, read from the file, are now properly assigned to the addresses on the sales order.

Solution: 130436
SITUATION IDENTIFIED IN:
"ccboidllxmlfun" ()
"ccboidllowxlfn" ()
SITUATION DESCRIPTION:
When creating a BOI with long function names, the length of the name was limited to 100 characters.
SOLUTION DESCRIPTION:
The container.get.fields(..) function had the limitation of accepting only 100 characters for the data type string; this is
now changed to 2048 characters, so longer names are supported.

Solution: 130438
SITUATION IDENTIFIED IN:
"Enter Hours Accounting" (tihra1101s000)
SITUATION DESCRIPTION:
It is possible to enter and register hours for a budget in "Enter Hours Accounting"(tihra1101s000). A project having
'Project type' as budget can be entered in the 'Project' field and the record can be saved.
SOLUTION DESCRIPTION:
Registering hours for a budget, is not allowed. If user tries to enter a project having 'Project type' as 'Budget' in "Enter
hours Accounting" (tihra1101s000), then system throws an error message and user can not proceed further.

Solution: 130440
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
In production the Select Invoices for Payment, tfcmg1220m000, process is running until its bshell process reaches 134 MB.
The process then aborts with a sbrk error (max data segment kernel limit) in its bshell.pid file.
SOLUTION DESCRIPTION:
The problem is solved.

Solution: 130446
SITUATION IDENTIFIED IN:
"Global Update of Sales Quotations" (tdsls1205s000)
SITUATION DESCRIPTION:
When executing the function the reference date is compared with the expiration date of the quotations. In case the
expiration date passes the reference date the quotation is selected based on this condition.
There is no possibility to enter a period within which the quotation should be effective.
SOLUTION DESCRIPTION:
Several changes are made regarding this topic:
- There now is a possibility to enter a period in time within which a quotation should be effective before a status change
can be done.
- The entry location of the period range was incorrect on the form. It has been relocated to the "Selection Range".
- According to the help text of the reference date field the transaction date is based on the reference date. This is not
correct. Updating of the quotation history is done based on the current date. Back dating or forward dating is not possible.

Solution: 130452
SITUATION IDENTIFIED IN:
"Installments" (tppin4551m000)
SITUATION DESCRIPTION:
1. Start session Projects, activate session Business Partners by Project and via "special" the session Contract Amounts by
Business Partner is activated.
In this session new contracts with different currencies can be inserted.
Start session Installments and add new installment with different currencies for a project and Business Partner.
Press the Print button and choose the summarized report.
A list of installments registered for this project is printed; it summarizes the amount with no concern taken to which
currency the amount is in.
2. Start session Installments and create an installment.
Transfer a part of this installment to central invoicing.
Create a final invoice.
After this set the remaining part or a larger part of the installment to "to be invoiced".
The following message appears: "Instal. will be closed. Still additional work pending"
SOLUTION DESCRIPTION:
1. In the session tppin4451m000 "Print Installments" an option print the installments in another currency, than the currency
of the installments them self is introduced. Also the possibility to print the installments in their own currency is kept.
However the total of this last option is in currency of the Business Partner".
2. The message will only appear when there is additional work and the installment will be closed

Solution: 130464
SITUATION IDENTIFIED IN:
"Lots" (whltc1100s000)
SITUATION DESCRIPTION:
Lot size not correct in case of production rework order.
SOLUTION DESCRIPTION:
In case of issue for production order with type rework order lot size will be decreased.

Solution: 130471
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
Outbound order line status remains "Staged" after Confirm Advice Lines for a picking list generated with sort 'Advised
Quantity in Inventory Unit' (whinh225.astk)
SOLUTION DESCRIPTION:
Now all the shipment lines are getting confirmed and the status of the outbound order line is "Shipped"

Solution: 130474
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
In the Japanese Localization, the terms of payment on the sales order header is mandatory to fill if |Payment Method"
(Localization Parameters by Country; tccoml101m00l) and |Payment Method by Terms of Payment" (COM Parameters;
tccom0000m000) are checked. However, if the value for the terms of payment is empty in the incoming ASCII file, the
sales order is inserted without error.
SOLUTION DESCRIPTION:
The check on terms of payment was not executed. The program script has been corrected. Now the proper error is generated
(similar as in the manual order entry process) and printed on the |Errors in Received Messages" report when the field empty
in the file while it is mandatory to fill.

Solution: 130486
SITUATION IDENTIFIED IN:
"Transfer Payments " (tfcmg1260s000)
SITUATION DESCRIPTION:
When a windows printer was used, a check defined in portrait mode was printed in landscape mode. This happened when
the audit report (which gets before the check) was printed in landscape mode.
SOLUTION DESCRIPTION:
Even when the audit report is printed in landscape mode, the check report defined in portrait mode is printed only in
portrait mode and not in landscape.

Solution: 130489
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Correction program whcor0119m000:
The integration transactions Production / Issue could be incorrectly generated in the following situation:
1. Issue materials for a production order.
The valuation method for the issues item for the issuing warehouse is FTP.
2. Create a negative issue (a Receipt thus) that exceeds the preceding material issue.
3. Recalculate the cost price of the item issued.
4. The receipt transactions created for the receipt quantity calculated as "total received quantity - issued quantity", were
booked with:
Transaction Origin: Warehouse (Valuation) instead of Production
Financial Transaction:
Revaluation instead of Issue
Warehouse Surcharge (Issue)
Item Surcharge (Issue)
SOLUTION DESCRIPTION:
Correction Program whcor0119m000
IMPORTANT NOTE:
The program must be executed by Logistic Company.
The correction program whcor0119m000 will correct these transactions according to the following procedure:
1. Warehouse (Valuation) / Revaluation Transactions:
These transactions should have been booked as Production / Issue transactions.
The correction program will thus create negative bookings for the incorrect warehouse revaluation (so that these
transactions can be reversed).
New Production / Issue Transactions will be created based on the erroneous Warehouse (Valuation) / Revaluation
bookings.
2. Warehouse (Valuation) / Warehouse Surcharge (Issue) Transactions:
Warehouse (Valuation) / Item Surcharge (Issue) Transactions:
This is not an allowed combination. These transactions will thus be deleted from the Integration transaction tables
(tfgld418/417/415/416/410).
Creation of the integration transactions:
Warehouse (Valuation) / Revaluation Transactions:
The debit and credit line are booked with:
- the finance company linked to the warehouse for which the transaction is processed
- the project number defined in the item code
Production / Issue Transactions:
The Debit line is booked with:
- the finance company linked to the calculation office filled in the production order for which the transaction is processed
- the project number defined in the production order
The Credit line is booked with:
- the finance company linked to the warehouse for which the transaction is processed
- the project number defined in the item code
Example:
Manufactured Item 98800040/0700
Components:
98800040/023 (Purchase PCS Item)
023 (Standard Item)
Both items are issue from the warehouse 004 linked to the finance company 100.
The calculation office of the production order is linked to the finance company 300.
When processing the a Production Issue of both material, the bookings Production/ Issue would be created that way:
Item 023
Debit Line:
Project = 98800040
Finance Company = 300
Credit Line:
Project = empty
Finance Company = 100
Item 98800040/023
Debit Line:
Project = 98800040
Finance Company = 300
Credit Line:
Project = 98800040
Finance Company = 100
When processing the a Revaluation of both material, the bookings Warehouse (Valuation) / Revaluation Transactions
would be created that way:
Item 023
Debit Line:
Project = empty
Finance Company = 100
Credit Line:
Project = empty
Finance Company = 100
Item 98800040/023
Debit Line:
Project = 98800040
Finance Company = 100
Credit Line:
Project = 98800040
Finance Company = 100
Options:
FORM1:
Selection Based on Fiscal Year/Period:
The Integration transactions will only be selected based on the fiscal year and period filled in the form2.
If this option is set to No, the Integration Transactions can then be selected based on:
- the production order numbers and
- the project numbers.
These options are available on the form3.
Specify Project:
This option has been added for performance reasons.
When processing a Warehouse (Valuation) / Revaluation Transaction, the project number is only filled in if the item for
which the transaction is created is a customized item (project segment filled in).
Filling in the project field would only make sense if:
- the erroneous integrations relates to a production order created for a customized item
- the negative production issue has been created for a customized component.
If this kind of transaction does not need to be corrected, set the field Specify Project to No (the project field will then be
blank when selecting the Integration Transactions).
Options on Form2 and Form3:
Test Run:
If this option is set to Yes, the report will print the incorrect Integration Transactions that need to be corrected.
If the field is set to No, the Integration Transactions will be corrected. Note that the correction executed will not appear on
the report.
The report will only show the corrected Integration Transactions.
Perform Corrections with original transaction date:
If this option is set to Yes, the correction bookings will be created with the transaction date of the corrected record as
transaction date.
If this option is set to No, the correction bookings will be created with actual date as transaction date.

Solution: 130492
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Tax amount in home currency is made zero in the lines after the user composes the invoice.
SOLUTION DESCRIPTION:
Now the tax amounts in home currency does not become zero.

Solution: 130493
SITUATION IDENTIFIED IN:
"Process Financial Statement Values" (tffst1205m000)
SITUATION DESCRIPTION:
Records are not inserted in the table "Maintain Financial Statement Values" when the same Financial Statement is
selected for processing without closing the session "Process Financial Statement Values"
SOLUTION DESCRIPTION:
Now, records are properly inserted when the same Financial Statement is selected again for processing without closing
the session "Process Financial Statement Values"
Solution: 130497
SITUATION IDENTIFIED IN:
"Reorganize/Reconfigure tables" (ttadv5215m000)
SITUATION DESCRIPTION:
Bdbreconfig functionality is changed. In such way, that it does no longer stop when an error has appeared. It will
reconfigure as much tables as possible. And mention the errors at the end.
To handle this bdbreconfig correctly a change need to be made in the tools sessions calling bdbreconfig.
The tools sessions should however still work correctly with the old bdbreconfig.
SOLUTION DESCRIPTION:
When bdbreconfig exits with an error code then the tools session will no longer stop directly but it will process the
successfully reconfigured tables.
previous fix 130305 was not a full fix. This is now corrected.

Solution: 130506
SITUATION IDENTIFIED IN:
"Sales Order Lines, Purchase Order Lines" (tdsls4101s000, tdpur4101s000)
SITUATION DESCRIPTION:
When the Order Quantity is different from the Sales Price Unit, there exist some rounding differences that are reflected in
the Order
Acknowledgement, and Invoice.
The Reporting documents - Acknowledgement and Invoice report the price only in terms of the Sales Price Unit,
irrespective of the
Order Quantity Unit, and the Agreements maintained in the Price Book. This makes it difficult to check the agreement
prices also.
SOLUTION DESCRIPTION:
Pricing Parameter 'Price Based On' has been added, one for Sales and another for Purchase. This Parameter has two
options. The Options are
1. Item Sales Data 2. Price Structure - for Sales, and
1. Item Purchase Data 2. Price Structure - for Purchase.
The Default is Item Sales Data/Item Purchase Data. If this is chosen, then old functionality remains. There is no change,
and the price in the Sales Order Line/ Purchase Order Line/ Purchase Requisition or the Sales Quotation line would be the
Sales Price Unit / Purchase Price Unit.
If the 'Price Structure' were chosen, then, the Price Unit would be picked up based on the Price Unit available for the
order quantity in the Price Book.
This way, since, there is no conversion to other unit, there is no rounding problem encountered. Order Acknowledgements,
and the Invoices would be printed with this Unit. So, the Acknowledgement and the Invoice could be seen in the respective
units.

Solution: 130523
SITUATION IDENTIFIED IN:
"Generate Inbound Advice" (whinh3201m000)
SITUATION DESCRIPTION:
Generating and putting away inbound advice for an item with a conversion factor that cannot convert exactly between units
(therefore a rounding is needed) causes corruption in data.
SOLUTION DESCRIPTION:
An extra check for this kind of conversion factors has been included: if correction on original amount/figure results in a
new amount/figure with same deviation from desired quantity, then it is not needed to do any correction.

Solution: 130524
SITUATION IDENTIFIED IN:
"Update purchase statistics" (tdpst0201m000)
SITUATION DESCRIPTION:
Purchase statistics are not updated in case a purchase order is created for a business partner that apply for vendor rating.
This only occurs when making a partial updated.
SOLUTION DESCRIPTION:
There was a variable used in the query that selects all none processed purchase orders. This variable was wrong initialized.
This has been modified. This variable is now initialized so all purchase orders, that are not processed, are selected.

Solution: 130547
SITUATION IDENTIFIED IN:
"Maintain Transactions Purchase Invoices" (tfacp1120s000)
SITUATION DESCRIPTION:
When entering transactions with session "Maintain Transactions Purchase Invoices - tfacp1120s000" and the remaining
amount looks like 0, still the message "Still transactions to be entered' pops-up.
SOLUTION DESCRIPTION:
By using the double.compare functionality we will avoid differences in amounts on decimals which are not displayed.

Solution: 130550
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Payments/Receipts to Invoices" (tfcmg2105s000 and tfcmg2106s000 )
SITUATION DESCRIPTION:
When two unallocated receipts were processed in the same transaction by linking with several invoices, the system picked
up wrong assignments and then the balance of the first unallocated receipt is wrong
SOLUTION DESCRIPTION:
The system now picks the right records.

Solution: 130561
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
The standard program solutions didn't have dependencies.
Therefore it is possible that a new standard program already installed will be overwritten with an older standard program.
SOLUTION DESCRIPTION:
A new solution 130561 is created for the standard program contains a dependency to all previous standard programs.
To prevent customers from a long download time we created a special multilevel dump.
All previous standard program solutions in this multilevel dump will contain only a dummy message and not the whole
standard program.

Solution: 130599
SITUATION IDENTIFIED IN:
"Reprocess Production Orders" (tisfc1203m000)
SITUATION DESCRIPTION:
The Netchange-flag in Item Production Data should only be reset to "No" if ALL Prod. Orders for the EndItem are
reprocessed, which are not yet released.
So, if the netchange flag is set for a manufactured item,
and you run tisfc1203m000 "Reprocess Production Orders" with 'Type of SFC reprocess run' set to Netchange
and you there are yet Planned/Release/Active Production Orders OUTSIDE the selection, for the same EndItem, then the
Netchange-flag in Item Production data should not be reset to "No".
SOLUTION DESCRIPTION:
Now the netchange flag is only reset, if all production orders for the same EndItem that are not yet Released are
reprocessed.

Solution: 130601
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
Problems can occur when 2 transfer orders are processed simultaneously using "direct release".
The following situations are noticed at the end of the process:
1. The outbound lines of one order have status "shipped" while the outbound lines of the other order have status "staged".
This is wrong, because all lines should have status "shipped".
2. Sometimes a fatal error "g.itab index 11 out of dims [1] 10" is given. In this case outbound order lines have different
statuses as described under situation 1.
3. Sometimes the outbound lines of both orders have status "shipped" which is o.k.
SOLUTION DESCRIPTION:
The outbound lines of both orders are processed correctly. All lines get status "shipped" and no fatal error occurs.

Solution: 130602
SITUATION IDENTIFIED IN:
"Help Viewer" (ttstphelp)
SITUATION DESCRIPTION:
In the helptext for a session, it is possible to add links to other sessions (for example "%SEttaad2500m000").
In the Session Help, the link will show as "ttaad2500m000 not implemented".
Yet In session "Session Help" (ttadv2105m000), session helptext for session ttaad2500m000 is present.
SOLUTION DESCRIPTION:
Before displaying the Session Help, links to another session are processed to show the session description, instead of
simply the link like it is present in the helptext (for example "%SEttaad2500m000").
The session description could not be found, because the VRC-structure for finding a session description was not known at
this point.
This resulted in the " not implemented" in the Session Help.
Now the VRC-structure is read in, before trying to find the session description. Now the link is shown correctly in
Session Help.

Solution: 130606
SITUATION IDENTIFIED IN:
"Item Sales Data" (tdisa0101s000)
SITUATION DESCRIPTION:
Problems when updating Sales Item Data in session "Sales Item Data" (tdisa0101s000).
Min.Quantity to Commit (tdisa001.mnqa) and Sales Price (tdisa001.pris) can't be updated due to slow performance.
These problems occur when Sales Order Lines table (tdsls401) has a large number of records for the Item for which the
Sales Item Data should be updated.
SOLUTION DESCRIPTION:
Now Sales Item Data can be updated. The performance problem occurred because the system was checking all sales order
lines with the given item to check if the field "Commitment Policy" should be enabled or disabled. The
enabling/disabling for this field has been changed. This field can now be changed if there are no commitments present
in warehousing (table whinp200 "Inventory Commitments") for the specified item.

Solution: 130607
SITUATION IDENTIFIED IN:
"Print Return Notes" (tdpur4411m00)
SITUATION DESCRIPTION:
1.When status is Awaiting Receipts (partial qty received & still expecting some qty), even when Return Note printed is not
printed for this Purchase Order line earlier, Return Notes is getting printed if we check box "Include Printed Lines"
2. Return Note was getting printed for the rejected quantity
SOLUTION DESCRIPTION:
1.The return notes will not be printed, if the status of the purchase order line is not "Print Return note ".
2." Include Printed lines " prints records only if the Return note is printed already

Solution: 130613
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
A) In a purchase order, if a contact (including a title) is defined in the header and no title is defined for the business
partner, the print out of the purchase order does not even include the title of the contact.
B) In a purchase order, if a contact (including a title) is defined in the header and a title is defined for the business
partner, the print out of the purchase order includes the title of the contact but not his name. Even though we link a contact
name to a title.
C) In a purchase order, if no contact is defined in the header and a title is defined in the business partner, if print a batch,
all purchase orders will print out the title of the first BP defined in the first purchase order.
SOLUTION DESCRIPTION:
1) Not only the title but also the surname of the contact is printed on the purchase order.
2) Title of the BP is not printed on following orders when printed as batch for other suppliers.

Solution: 130614
SITUATION IDENTIFIED IN:
"Purchase Order lines, Purchase Contract lines" (tdpur4501m000, tdpur3511m000)
SITUATION DESCRIPTION:
The session type of Purchase Order lines (tdpur4501m000) is set as "Maintain" though it has to be "Display". The
Purchase Contract lines (tdpur3511m000) session has to be a main session.
SOLUTION DESCRIPTION:
The session type of Purchase Order lines (tdpur4501m000) is made as "Display". The Purchase Contract lines session
(tdpur3511m000) is made as a main session.

Solution: 130618
SITUATION IDENTIFIED IN:
"Service Order Actual Labor Costs" (tssoc2131m000)
SITUATION DESCRIPTION:
In the session "Service Order Actual Material Costs" (tssoc2131m000), it was not possible to review the surcharge cost and
sales rate associated with the hourly labor type.
SOLUTION DESCRIPTION:
It is now possible to view the surcharge cost as well as surcharge sales rate that is associated with an hourly labor type for
labor costs.

Solution: 130628
SITUATION IDENTIFIED IN:
"Print Invoice-from Business Partner Open Entries" (tfacp2421m000)
SITUATION DESCRIPTION:
Report "Open Entries by Invoices from Business Partner" (tfacp242111000) is sorted first on company and then on
business partner.
SOLUTION DESCRIPTION:
The report "Open Entries by Invoices from Business Partner" is sorted first on Business Partner and then company. Hence
all the invoices of a business partner across companies appear together.

Solution: 130633
SITUATION IDENTIFIED IN:
"Generate Invoices by Self billing" (tfacp2290m000)
SITUATION DESCRIPTION:
The following situations were noticed.
1. The order type was not a selection criteria for selecting the Purchase Orders / Receipts for self billing. This resulted in
the Mixing of orders from different sources, when the same number group series is used for different order types.
2. The document date in the Documents table ( tfgld018 ) was different from the document date in the Open Entry (
tfacp200 ).
3. In the Japanese localization for B50_b, the rate date was not document date, even when the "Fixed Rate" in the
purchase order header was "Document date".
4. The help text for Compression was not present.
SOLUTION DESCRIPTION:
1. Added Order type as one of the selection criteria for selfbilling.
2. The document date is consistent now between Documents table ( tfgld018 ) and Open Entry ( tfacp200 ).
3. In case Fixed Rate = Document date, then the rate is based on the document date.
4. Help text have been added for the field Compression. The help text can be accessed by pressing F1 when the field for
which help text sought is current.

Solution: 130647
SITUATION IDENTIFIED IN:
Process Delivered Purchase Order (tdpur4223m000)
SITUATION DESCRIPTION:
It is not possible to delete the processed purchase order even when the project is archived.
SOLUTION DESCRIPTION:
It is now possible to delete the processed purchase order when the project is archived.

Solution: 130648
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In case of an ICT Purchase situation, meaning that goods are transferred from EU country A to EU country B, ICT
Purchase VAT from the "ship-from country" was shown. This was incorrect.
SOLUTION DESCRIPTION:
In case of an ICT Purchase situation, wherein goods are transferred from EU country A to EU country B, the ICT
Purchase VAT of the "ship-to country" is applicable according EU Laws.

Solution: 130650
SITUATION IDENTIFIED IN:
"Default Text Groups by Text Field Template" (ttams1120m000)
SITUATION DESCRIPTION:
Zooming to find a text group from session "Default Text Groups by Text Field template" (ttams1120m000) does not
position correctly.
Session "Text Groups" (ttxt1110m00) always comes up with the first record.
SOLUTION DESCRIPTION:
Now the contents of field Text Group in session "Default Text Groups by Text Field template" (ttams1120m000) is taken
into consideration as start value when zooming to find a Text Group.

Solution: 130675
SITUATION IDENTIFIED IN:
"Sales Header" (cisli2140s000)
SITUATION DESCRIPTION:
In the Invoice headers in "Central Invoicing" the Pay-By BP is having a label "Pay-from". The label should be "Pay-by"
SOLUTION DESCRIPTION:
The label is changed now. And also the error message is displayed.

Solution: 130676
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2100s000)
SITUATION DESCRIPTION:
A new Transfer (Manual) warehousing order is created. In the first form of the session, the Transfer Price is filled. Then,
in the second form the 'Ship from' and 'Ship to' warehouses are filled. The Transfer Price that was filled manually filled
in the first form becomes zero even when there is Commercial Price type of Bilateral invoicing relationship exists
between the two warehouses.
SOLUTION DESCRIPTION:
The 'Transfer Price' field does not become zero when the relationship between the two Warehouses is Bilateral
Commercial price.

Solution: 130689
SITUATION IDENTIFIED IN:
Link Invoices to Credit Notes II (tfacr2121m000)
SITUATION DESCRIPTION:
When matching a credit note in foreign currency to an invoice in home currency the batch created is out of balance and
unable to finalize.
SOLUTION DESCRIPTION:
When matching a credit note in foreign currency to an invoice in home currency the batch is balanced and able to
finalize.

Solution: 130696
SITUATION IDENTIFIED IN:
"Selection of Open Items" (tfcmg2118s000)
SITUATION DESCRIPTION:
The selection of open items does not work properly in session "Selection of open items" if the "PAY-by-Business Partner"
is part of hierarchy with more than 1 level.
Open entries of a child customer are not displayed in the session when more than 1 level is set up in the Pay-by-Business
Partner hierarchy.
SOLUTION DESCRIPTION:
Now all Business Partners, which are in parent-child relations in all existed levels are shown.

Solution: 130699
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
There are several shipment lines for one sales order line. The discount percentage is filled on the Sales Order Line
(tdsls4101s000). When confirming the shipment (session whinh4275m000) a Total Sales Order Line is created with a detail
for each shipment line. The field "Total Discount Amount" on the Total Line is incorrect. It displays the "Total Discount
Amount" for the first detail line.
SOLUTION DESCRIPTION:
After confirming the shipment lines the Total Discount Amount on the Total Sales Order Line will be the same as was
entered when entering the Sales Order Line.

Solution: 130704
SITUATION IDENTIFIED IN:
"Check Solution to Install", "Check and Install Solutions" (ttpmc2203s000/ttpmc2204s000)
SITUATION DESCRIPTION:
PMC Solutions get the status 'To Install', although not all conditions for installing are satisfied. These conditions are:
- The solution must be present;
- The solution dump must be present;
- Pre-, co- and post-requisite solutions must be installed or also have the status 'To Install'.
It could happen that a pre-requisite solution still had the status 'Available' and the solution to check had the status
'To-install'.
Consider the following structure of solutions:
<#HTML>

     Standard Localization

     Co

     Sol 1 <--------> Sol 1

     /\

     | Pre

     |

     Sol 2

Standard Sol 2 has a pre-requisite solution Sol 1; this Sol 1 has a co-requisite solution Sol 1 for the Localization. When Sol
1 for the Localization has not been scanned, the 'Check Solution to Install' report shows the status 'Not available' for it,
Sol 1 for the Standard remains 'Available'. The problem is that Sol 2 gets the status 'To Install'.
The consequence of the wrong statuses is bad information only. Although the status is 'To Install', PMC will not install it,
because the other solutions still have status 'Available'.
SOLUTION DESCRIPTION:
The checking of solutions has been changed. When one of the pre-requisite solutions is still 'Available', also the
subsequent solutions will remain 'Available'.
When you are checking a range of solutions with session "Check and Install Solutions" (ttpmc2204s000), all newer
solutions will remain 'Available'.

Solution: 130709
SITUATION IDENTIFIED IN:
"Purchase Order lines" (tdpur4101s000)
SITUATION DESCRIPTION:
There was no check done for the Ledger accounts and dimensions when entered for an equipment item
SOLUTION DESCRIPTION:
The check has been coded and the equipment item also included.

Solution: 130721
SITUATION IDENTIFIED IN:
Change Prices and discounts after Delivery (tdsls4122m000)
SITUATION DESCRIPTION:
When the user is tabbing through the check boxes "update price in item file" and "update price date for other seq." in the
session "Change Prices and discounts after Delivery (tdsls4122m000)",
The system is giving the following messages, "this value is not allowed, change the update price in item file" and "this
value is not allowed, Change the Update Price Data for other Seq." even though this fields are not mandatory input fields.
SOLUTION DESCRIPTION:
Now the problem is solved, the system will not give the messages when the user tabs through the form fields.

Solution: 130722
SITUATION IDENTIFIED IN:
"Material to issue for production order" (ticst0101s000)
SITUATION DESCRIPTION:
When additional items are added/updated in the "Material to issue for production order" (ticst1501m000) session with
backflushing flag selected for a released production order with moments of freezing estimates as "Before First WIP
transaction" then, while backflushing for the production order, all the items are backflushed except for the additional
added items and no message is displayed stating the reason for not backflushing.
SOLUTION DESCRIPTION:
The newly added material lines via session "Material to issue for production order" (ticst1501m000) are rightly
backflushed. This solution introduces an additional functionality as explained below to fix the problem.
New material line can be added to a production order, if the estimates are not frozen. Addition of new material line can
be added through "Material to issue for production order" (ticst1501m000) or "Estimated Materials" (tisfc0510m000)
session. Let us take the scenario in which the item is to be backflushed so the flag backflushing is set to YES.
Backflushing process mainly takes net quantity into account for backflushing. Materials with zero net quantity will not be
backflushed. The new functionality calculates the net quantity and estimated quantity from the issue quantity and
subsequent delivery quantity. As a result backflushing is done for additional items also.

Solution: 130723
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
After entering a purchase invoice and matching it partially to
an order, the approval data tab on invoice header level doesn't
show the right values if the logistical company differs from the financial company.
SOLUTION DESCRIPTION:
Because now the right (logistical) company is taken in
account, the right values on the approval tab are shown.

Solution: 130753
SITUATION IDENTIFIED IN:
"Subcontracting costs" (tpppc2171m000)
SITUATION DESCRIPTION:
Sales amount is displayed for a fixed price project when the costs are booked from finance which is wrong.
SOLUTION DESCRIPTION:
Now a check on the type of project is built so that sales amount displayed for a fixed price project would be zero.

Solution: 130765
SITUATION IDENTIFIED IN:
Calls (tsclm1100s000)
SITUATION DESCRIPTION:
When transferring a Call to a Service Order where the Sold Business Partner has no default Invoice To Business Partner
linked, it is not possible to transfer the Call. It is not possible to create a Service Order without a default Invoice To
Business Partner.
SOLUTION DESCRIPTION:
It is now possible to create an External Service Order without an Invoice-to Business Partner or a Pay-by Business
Partner. This is possible until the Service Order or its Activity are being set to Costed. During the process of setting
one of them to Costed a check is made whether the Invoice-to Business Partner and Pay-by Business Partner are present on
the Service Order header. Also when creating an actual costline for an External Service Order, a Invoice-to Business
Partner and a Pay-by business partner have to be present. These changes make it possible to "transfer" or "emergency
transfer" a Call without having defined a default Invoice-to Business Partner.
When actual costlines are created, changes are limited. The following fields cannot be changed in that case, also when
they are derived from fields, which are allowed to change.
Fields:
Location Address (tssoc200.lcad)
Service Area (tssoc200.csar)
Currency (tssoc200.ccur)
Exchange rate type (tssoc200.rtyp)
Rate determiner (tssoc200.fcrt)
Country (tssoc200.ccty)
For example when the Invoice-to Business Partner changes, default values are retrieved, for example the currency. This
will be blocked when one or more actual costline exist.
Solution: 130766
SITUATION IDENTIFIED IN:
Change Prices/Discounts after Receipts (tdpur4122m000)
Integration Transactions by Project / Order (tfgld4510m000)
SITUATION DESCRIPTION:
When the user changes the prices of the PO line using the session "Change Prices/Discounts after Receipts
(tdpur4122m000)", after receipt of a subcontracting purchase order line. When we look at the generated integration
transactions, some order fields are empty.
When the subcontracting purchase order item is received using the purchase order receipt session, then the multiple
transactions have been posted.
SOLUTION DESCRIPTION:
Now the system will show all the relevant information in the generate integration transactions when the user changes the
prices, after receipt of a subcontracting PO lines are made.
Multiple transactions are not posted any more.

Solution: 130769
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Document Date in 'Maintain Documents' table (tfgld018) is always current date even when the batch date is not the
current date.
SOLUTION DESCRIPTION:
Document date within 'Maintain Documents' table is equal to the batch date (transaction entry date) instead of current
date for the assignment document. All dates of assignment documents are consistent.

Solution: 130785
SITUATION IDENTIFIED IN:
"Import Patch" (ttiex1280m000)
SITUATION DESCRIPTION:
When 1 component is delivered with a PMC solution then all the modules of that package are included in the dump
SOLUTION DESCRIPTION:
Only the modules of the components in the solution are included in the dump. Also a correction program is created. "Delete
not existing modules" ttcorrmmodule. This session has just a continue button and it will remove all modules where no
session, script, function, table, form, report, menu, chart belong to.

Solution: 130787
SITUATION IDENTIFIED IN:
"Billing Requests" (cisli2110s000)
SITUATION DESCRIPTION:
When the billing request is composed and printed by one user on a date and then posted by another user, the fields "Last
update" and "User last update" is not getting updated.
SOLUTION DESCRIPTION:
Now the fields are updated correctly.

Solution: 130789
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
Processing of inventory variances for items with valuation method "lot price" can result in wrong financial postings.
When processing inventory variances, these variances are assigned to inventory based on the wrong assumption that the
oldest lot is consumed first.
Example:
Item A; valuation method "lot price"
1. Purchase and receive 10 item A on 01-01; Lot "LOT01"; Price 10
Purchase and receive 10 item A on 02-01; Lot "LOT02"; Price 20
2. Sell and ship 10 item A on 04-01; lot "LOT02"
3. Now the purchase price for lot LOT02 is adjusted and an inventory variance is created.
When processing this variance, lot LOT02 is assumed to be still on hand because lot LOT01 is assumed being
consumed.
Hence wrong integration transactions are created.
SOLUTION DESCRIPTION:
Now the lot inventory is taken into account. Processing of the inventory variances is done based on the right quantities and
correct financial postings are created.

Solution: 130809
SITUATION IDENTIFIED IN:
"Integration Transactions by Order" (tfgld4510m000)
SITUATION DESCRIPTION:
During Item Transfer, with Valuation method being 'Lot price', the lot price of the "From Item" is not defaulted to the Lot
Price of the " To Item ". It is being calculated from the cost price of the item and the difference in the lot prices is booked
as valuation result.
SOLUTION DESCRIPTION:
Now the Lot price of the "To Item " is same as the lot price of the "From Item " and there are no Integration transactions
booked as valuation result.

Solution: 130813
SITUATION IDENTIFIED IN:
Purchase Order Lines (tdpur4101s000)
SITUATION DESCRIPTION:
When there is a contract line and if the price books are maintained for the items. And for a particular item a contract line
is maintained. Then if a purchase order line is inserted for this item this contract will be linked and the price will be
fetched from the maintained price books. But if for the next item is inserted, then also the same price is fetched which is
wrong.
SOLUTION DESCRIPTION:
When the option 'apply contract for all items in price group' is checked on the Purchase Contract Line then using the
correct item the price will be fetched.

Solution: 130816
SITUATION IDENTIFIED IN:
"Re-Print Sales Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
Performance is very bad when invoices are re-printed using the option "Select by Invoices".
SOLUTION DESCRIPTION:
Now the performance is improved.

Solution: 130827
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
The standard cost price of a manufacturing item is not getting updated, if the calculated cost price is zero. If the BOM
(Bills of material) and routing get expired for a manufacturing item, even though the system calculates the cost price, the
standard cost price sessions will not be updated.
SOLUTION DESCRIPTION:
When the calculated cost price of a manufacturing item is zero, the standard cost price sessions will be updated.

Solution: 130836
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4101s000)
SITUATION DESCRIPTION:
When the Business Partner on a blocked Sales Order Header (tdsls4100s000 is changed and the Header needs to be blocked
also, the Business Partner on the Blocking Record (session tdsls4120s000) is not changed.
SOLUTION DESCRIPTION:
In above situation the blocking record in session Order (Line) Blocking (tdsls4120s000) is adjusted. The correct
Business Partner and Hold Reason are displayed.

Solution: 130838
SITUATION IDENTIFIED IN:
Price Calculator (tdpcg0200m100)
SITUATION DESCRIPTION:
When the date in the session "Price Calculator" (tdpcg0200m100) is changed, and 'Recalculate' button is pressed, the
price applicable for that date is NOT picked up and calculations of other fields NOT done based on that price.
SOLUTION DESCRIPTION:
Now, whenever 'Price date' is changed, and 'Recalculate button' is pressed, 'Unit Price' applicable for that quantity and
date is picked correctly and other fields are calculated based on the new 'Unit Price'.

Solution: 130847
SITUATION IDENTIFIED IN:
Maintain and Confirm Back Orders (tdsls4125m000)
SITUATION DESCRIPTION:
For an Engineering Item a direct delivery sales order is inserted. But initially the Engineering Item is not activated in
Item Master data. The Purchase Order is generated. The Engineering Item is activated in Item Master data, and the goods
are received partially. On confirming the Back Order in Sales, the Back Order in Purchase is not created.
SOLUTION DESCRIPTION:
Now, the Back Order in Purchase is created for the Engineering Item if the Engineering Item value in Item Master data is
activated after the direct delivery Purchase Order is created and received partially.

Solution: 130849
SITUATION IDENTIFIED IN:
"Control Account Checklist" (tfacp2415m000)
SITUATION DESCRIPTION:
Printing the Control account checklist some Purchase documents are showing a difference related to the currency difference
that actually doesn't exist. If the open item table is checked all entries are properly made.
SOLUTION DESCRIPTION:
Only real differences are printed now.

Solution: 130851
SITUATION IDENTIFIED IN:
Print Purchase Orders (tdpur4401m000)
SITUATION DESCRIPTION:
User is able to print the Purchase Orders with "All Lines" option even when the purchase order has a manual approval
activity that has not been executed. Because of this, normal users are able to print and read the unapproved purchase
orders.
SOLUTION DESCRIPTION:
User is able to print the Purchase Orders with "All Lines" option even when the purchase order has a manual approval
activity that has not been executed. Because of this, normal users are able to print and read the unapproved purchase
orders.

Solution: 130853
SITUATION IDENTIFIED IN:
"Cancel Production Orders" (tisfc0203m000)
SITUATION DESCRIPTION:
It is not possible to cancel a production order in the following situation:
- (part of the) material is already issued to the shop floor
- the default receipt transaction type for production orders contains more steps then only confirm receipts
The default transaction type is found in session "Default Order Types by Origin" (whinh0520m000).
When canceling a production order, the already issued materials are returned to warehousing. A warehouse order inbound line
is created to return the issued quantity. This line is confirmed automatically. If the line is not put away, it is not
possible to remove the line and an error message comes up: "Warehouse order %s with order origin '%s' has not been deleted
because of line status." As a result, all transactions are undone, and the order is not cancelled.
Either all lines are removed or nothing happens.
SOLUTION DESCRIPTION:
Now it is allowed to cancel the production order in the SFC module. Not all warehousing order lines are deleted. Only
those lines for which no materials are issued, or for which the issued materials are returned and put away.
If inbound is not part of the inbound order steps, the inbound is completed automatically. If inbound is part of the
inbound order steps, the inbound must be done manually.
In the last situation there is a discrepancy between SFC and WH. The warehousing sessions contain an order that does
not exist any more in production. That is not a problem. The session "Remove Closed Warehousing Orders"
(whinh2250m000) even assumes this discrepancy and can be run to remove the warehousing order once it is completed.

Solution: 130857
SITUATION IDENTIFIED IN:
"Match Purchase Order Line" (tfacp2541s000)
SITUATION DESCRIPTION:
When the Order number and packing slip are not entered in the Purchase Invoice, and when the session Match Purchase
order line is started for matching the orders, the performance is bad.
SOLUTION DESCRIPTION:
Now, the session "Match Purchase order line " uses the correct Index when starting from the session Purchase Invoice.
The performance has been optimized.

Solution: 130863
SITUATION IDENTIFIED IN:
"Update sales statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
The sales statistics are booked to the wrong Business Partner 2 when running a full update by using the actual customer
data.
SOLUTION DESCRIPTION:
The problem was due to the roles were not correctly read. A function has been created where all roles are read based on the
parameter 'Business Partner 2 selection'. This tables are read by using the Sold-to business partner.

Solution: 130873
SITUATION IDENTIFIED IN:
"Global Update of Project Status" (tipcs2280m000)
SITUATION DESCRIPTION:
Changing the project status to "Finished" is not possible when purchase invoices related to the project have not been
approved.
SOLUTION DESCRIPTION:
Changing the project status to "Finished" is not blocked when purchase invoices related to the project have not been
approved.
Project status "Finished" basically means that all logistical activity has been finished, and should not be blocked by
financial activities that have not been done (these checks will be performed when closing projects)

Solution: 130887
SITUATION IDENTIFIED IN:
"Change VRC of Software Components by Customization Part" (ttadv1276m000)
SITUATION DESCRIPTION:
In session "Change VRC of Software Components by Customization Part", the user can enter a range of software
components for which the VRC must be changed, and the source VRC and the target VRC.
Error 100 (duplicate value) occurs if a component in this range is already present in the target VRC.
Problems found in B50_b and higher:
1: It is not possible to save the values (Save Defaults), and retrieve these values (Get Defaults).
The user needs to specify each field, every time the session is started.
2: Via session "Software Components by Customization Part" (ttadv1176m000), session ttadv1276m000 is started.
After returning to session ttadv1176m000, you need to Refresh the screen to see the new values for VRC.
SOLUTION DESCRIPTION:
While changing the VRC of the components, components that are already present in the target VRC are skipped.
These components will remain present in both the source and the target VRC.
1: The session now has buttons for Save Defaults and Get Defaults.
2: The new values are shown immediately after returning to session ttadv1176m000.

Solution: 130894
SITUATION IDENTIFIED IN:
"Project Status" (tppdm6107m000)
SITUATION DESCRIPTION:
When changing the project status from 'Free' to 'Active', the system will give an error 'Transaction is on, can't continue'.
This only happens when already installments or advances are created for this project.
SOLUTION DESCRIPTION:
The error occurred due to locking mechanisms. The check on whether the new status is allowed for the project or not, was
moved to the point of actually saving the record. This changed the point at which records are locked and removed the
error.

Solution: 130895
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
The 'total amount by BP' 'to' field is reset back to 9999.9999999999 (default), even if the value is changed for the Job.
SOLUTION DESCRIPTION:
When calling the session from Job the 'total amount by BP' 'to' field is not updated.

Solution: 130907
SITUATION IDENTIFIED IN:
"Import Data Dictionary" (ttiex1288m000)
SITUATION DESCRIPTION:
There is a problem when a dump is created on one system, and then transferred to another system using for example
ftp-client.
The filename of the dump should end with .Z, but after the file transfer the filename ends with .z.
Now the dump will not be handled during the import.
SOLUTION DESCRIPTION:
Filenames that end with .z. are renamed in filenames that end with .Z.
Now the import proceeds correctly.

Solution: 130912
SITUATION IDENTIFIED IN:
"Automatic Matching" (tfacp.dll2405)
SITUATION DESCRIPTION:
It is not possible to Match the Purchase Order with one packing slip with multiple lots.
SOLUTION DESCRIPTION:
Now it is possible to Match the Purchase Order with one packing slip with multiple lots.

Solution: 130921
SITUATION IDENTIFIED IN:
"Release to Invoicing (Batch)" (tdsls4247m000)
SITUATION DESCRIPTION:
An installment order for a sales order is closed, and both the sales order and the correction installment are released to
Invoicing. When composing the invoice, both the correction and the goods are invoiced. This means there is too much
invoiced for this Sales Order.
SOLUTION DESCRIPTION:
When the installment order is closed and the correction installment line does not have the status "Invoiced", it is not
possible to release the Sales Order to Invoicing. In this case the following error message is given (or printed on the error
report): "Installment closed: correction installment must be invoiced before goods can be released to invoicing".

Solution: 130951
SITUATION IDENTIFIED IN:
"Order-Specific Inspections" (qmptc0150s000)
SITUATION DESCRIPTION:
Help Text is not present for the field 'Order' in the session "Order-Specific Inspections".
SOLUTION DESCRIPTION:
The help text is added to the field 'Order' in the session "Order-Specific Inspections" and the system displays the help
text.

Solution: 130958
SITUATION IDENTIFIED IN:
"Generate Project Structure for Product Variant" (tipcs2220m000)
SITUATION DESCRIPTION:
When (re)generating a Product Variant, and EP-parameter 'Online Phase Number Update' is set to "yes", the Order
Phasenumber of the item from which the customized item is derived (derived from item) is not updated. After
(re)generating the Product Variant, both the customized item and its derived from item have Order Phase Number 0, while
the derived from item should have Order Phase Number 1 since it is treated as a material
SOLUTION DESCRIPTION:
When (re)generating a Product Variant, and EP-parameter 'Online Phase Number Update' is set to "yes", the Order
Phasenumber of the item from which the customized item is derived (derived from item) is updated. After (re)generating
the Product Variant, the customized item has Order Phase Number 0 and its derived from item has Order Phase Number
1.

Solution: 130971
SITUATION IDENTIFIED IN:
"Business partners " (tcccom4110s000)
SITUATION DESCRIPTION:
When a Business partner (BP) record is duplicated, then the texts of all the roles, namely Sold-to, Ship-from,
Invoice-from, Pay-by, Buy-from, Ship-from, Invoice-from and Pay-to Business partner are duplicated in the new Business
partner record. Now if user changes the texts of any of the roles of the original BP, then these changes are reflected in
the corresponding texts of the new BP as well.
SOLUTION DESCRIPTION:
If a Business partner (BP) record is duplicated, then the texts of all the roles of the Business partner are copied to the
new BP. If changes are made in the texts of any one of the roles of the original BP, then these changes are confines to that
BP role only. The changes are not reflected in the texts of the copied BP.

Solution: 130974
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Warehouse and Item" (whina1210m000)
SITUATION DESCRIPTION:
Under some cases the due to wrong rounding of the MAUC values the Inventory Value in the report of the session
based on MAUC is wrong.
SOLUTION DESCRIPTION:
The MAUC value is correctly calculated and rounded due to which the Inventory Value obtained is correctly shown in the
report of the session.

Solution: 130981
SITUATION IDENTIFIED IN:
"Generate Cycle Counting Orders" (whinh5200m000)
SITUATION DESCRIPTION:
In a location controlled warehouse for a location controlled item, a cycle counting order can be generated and processed
with an empty location. When there is inventory in the warehouse, the location is filled correctly during generation of
cycle counting order lines .The problem occurs only in the case of non- existing stock points and we force cycle counting
during generating of cycle counting orders.
SOLUTION DESCRIPTION:
The System will not generate cycle counting order lines for a location controlled item in a location controlled warehouse
with empty location for non existing stock points.

Solution: 130982
SITUATION IDENTIFIED IN:
"Delete WIP transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
When deleting wip (Work In Process) transactions for one or a range of production orders or PCS project
the transactions for closed and archived production orders / PCS projects are removed.
SOLUTION DESCRIPTION:
New functionality:
Add an extra option on the form tcfin1200m000 (Delete Wip transactions by Projects/ Production Order).
When ticking the option 'Only archived production orders / PCS projects' only the Work in Process transaction
for archived PCS Projects or Production Orders are removed.
When leaving this option unchecked the old functionality is used, as described in the situation description.

Solution: 130990
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Follow the following procedure:
- Insert a sales order line (session tdsls4101s000) for an item that is linked to an active contract. Unlink the contract by
using the button on the "Selling" tab and save the order line. Do not close the session.
- Generate a Purchase Order Advice for the Sales Order Line using the option from the Specific menu from the multi
occurrence session "Sales Order Lines" (tdsls4501m000)
- Go back to the Sales Order Line session (tdsls4101s000). Link the contract again to the Sales Order Line by using the
button on the "Selling" tab and save it.
- Now check session Linked Order Line Data (tdsls4102s200) by using the option from the Specific Menu in
tdsls4501m000. The Purchase Order Advice Number is gone, and the Contract Number is filled.
Now it is possible to generate a second purchase order advice and when confirming the two Purchase Order Advices, two
Purchase Order Lines for one Sales Order Line are present.
SOLUTION DESCRIPTION:
When following the procedure as described above, the "Linked Order Line Data" (session tdsls4102s200) shows both the
Purchase Order Advice Number and the Contract Number. Now it is not possible anymore to create a second Purchase
Order Advice for this order line.

Solution: 130999
SITUATION IDENTIFIED IN:
Project Structure (tipcs2115m000)
SITUATION DESCRIPTION:
Problem: 1
System allows to enter sub project in the main project field of session "Project Structure" (tipcs2115m000) and no warning
message is displayed. But a warning message "Project is not a main project" is displayed while entering and saving a sub
project which is inappropriate.
Problem: 2
The description of the sub project is changed in session "Projects" (tipcs2101m000), if the sub project is deleted from the
project structure in session "Project Structure" (tipcs2115m000).
SOLUTION DESCRIPTION:
Problem: 1
System displays a warning message "Project is not a main project" if a sub project is entered in the main project field of
session "Project Structure" (tipcs2115m000).
Problem: 2
The description of the sub project remains unchanged in session "Projects" (tipcs2101m000) even when the sub project is
deleted from project structure in session "Project Structure" (tipcs2115m000).

Solution: 131004
SITUATION IDENTIFIED IN:
"Item Data by Warehouse" (whwmd2510m000)
SITUATION DESCRIPTION:
In session whwmd2510m000 "Item Data by Warehouse" it is possible to delete an Item by Warehouse line when there are
still
- inventory transactions present
- or inventory variances present
SOLUTION DESCRIPTION:
Extra checks have been included: to be able to delete an item by warehouse line in session whwmd2510m000 it will be
consider now that this item warehouse combination does not contain any
- inventory transactions by item and warehouse
- or inventory variances
Two new messages have been created to be displayed in case inventory transactions or variances are present:
- Inventory transactions present in Warehouse for Item . Delete action cancelled.
- Inventory variances present in Warehouse for Item. Delete action cancelled.

Solution: 131009
SITUATION IDENTIFIED IN:
"Print Objects by Program Script\Library" (ttadv2439m000)
SITUATION DESCRIPTION:
It is not possible to zoom to pick up values for fields 'Version', 'Release' and 'Customer' in the session 'Print Objects by
Program Script/Library'
SOLUTION DESCRIPTION:
Now it is possible to zoom to session 'Package VRCs' and pick up values for the fields 'Version', 'Release' and 'Customer'.

Solution: 131012
SITUATION IDENTIFIED IN:
"Generate Invoices by Self billing" (tfacp2290m000)
SITUATION DESCRIPTION:
When a change price after receipt is done, during the self billing process, the changed price is not taken into account
during the invoice creation.
SOLUTION DESCRIPTION:
Now, the invoice is created with the changed price, when there is change price after discount, during the Invoice generation
by self billing.

Solution: 131024
SITUATION IDENTIFIED IN:
"Accept Values of GRNI Reconciliation" (tfacp1535m000)
SITUATION DESCRIPTION:
When an invoice is unapproved in session "Match/Approve Purchase Invoice" (tfacp2107s000), then the already accepted
GRNI approval transactions are deleted. This can be checked in session "Accept Values of GRNI Reconciliation"
(tfacp1535m000).
SOLUTION DESCRIPTION:
When an approval of an invoice is done, the already approved GRNI transactions are not deleted anymore.

Solution: 131033
SITUATION IDENTIFIED IN:
Project Status (tipcs2102s000)
SITUATION DESCRIPTION:
A Purchase Order is maintained with project item and a project.
In the lines "Split Delivery Lines" is checked, and detail lines are maintained.
All the lines are received, and invoices are also matched & approved in finance.
Now when trying to change the project status to "Finished" the system is giving the error message "Purchase Order not
closed". And hence the project status cannot be changed to "Finished".
SOLUTION DESCRIPTION:
The system will not give the error message when the user is trying to change the status of the project to "Finished" and
allow the status to change.

Solution: 131034
SITUATION IDENTIFIED IN:
"Confirm Shipments" (whinh4275m000)
SITUATION DESCRIPTION:
When Confirming Shipments (whinh4275m000) for more outbound lines including a backorder, the Planned Inventory
Transactions (whinp1500m000) are not updated with the correct sequence number when the Sales Parameter "Confirm
Backorders Automatically" is not checked. This error generates many records when running session "Rebuild Planned
Inventory Transactions" (whinp1200m000)
SOLUTION DESCRIPTION:
When confirming shipments for a situation as described above, the remaining Planned Inventory Transaction is for the
correct sequence number. This is the sequence number of the Sales Order Line for which the backorder exists.

Solution: 131039
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements/RMAs" (tdsls4401m100).
"Print Quotations" (tdsls1401m100).
SITUATION DESCRIPTION:
Order Amount and Quotation Amount are not being printed when printing Sales Order Acknowledgements
(tdsls4401m000) or Quotations (tdsls1401m000).
This situations applies when the value of the respective fields to be printed = '0' (zero).
SOLUTION DESCRIPTION:
Order Amount (tdsls401.oamt) and Quotation Amount (tdsls101.amta) are printed correctly, regardless the value to be
printed.

Solution: 131042
SITUATION IDENTIFIED IN:
"Sales Order Acknowledgment Code Assignments" (tdsls0155m000)
SITUATION DESCRIPTION:
In session |Sales Order Acknowledgment Code Assignments" (tdsls0155m000), the source for the changes was set to |EDI"
but the codes were added to the sales order lines for manual changes as well.
SOLUTION DESCRIPTION:
The system was checking the order origin (EDI or other) to determine if a code had to be assigned. This is not correct. The
process via which the changes are made (or lines are added) determines the code assignment. Now the functionality is in
line with the help text on the |Source" field.

Solution: 131044
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Orders" (tdsls4244m000)
SITUATION DESCRIPTION:
Problem comes in session 'Generate Project Structure for Sales Order (tdsls4244m000). In the process of customizing, for
a phantom item a BOM is created, but not a Routing. As a rule, both have go together. Enterprise Planning (EP) expects that
if one is created, the other is also done.
SOLUTION DESCRIPTION:
When for an item the BOM is created also the Routing is generated. In this way data remains consistent and Enterprise
Planning can handle the items in a correct way.

Solution: 131050
SITUATION IDENTIFIED IN:
"Inventory Transactions by stock point" (whinr1500m000)
SITUATION DESCRIPTION:
When a receipt correction is processed, the used transaction date for the inventory stock transactions (whinr1500m000) is the
current date instead of the actual transaction date of the initial receipt.
SOLUTION DESCRIPTION:
Now when a receipt correction is processed, the used transaction date for the inventory stock transactions (whinr1500m000)
is the actual transaction date of the initial receipt.

Solution: 131061
SITUATION IDENTIFIED IN:
Calculate Cost and Valuation Prices (ticpr2210m000)
SITUATION DESCRIPTION:
The standard cost price of a manufacturing item is not getting updated, if the calculated cost price is zero. If the BOM
(Bills of material) and routing get expired for a manufacturing item, even though the system calculates the cost price, the
standard cost price sessions will not be updated.
SOLUTION DESCRIPTION:
When the calculated cost price of a manufacturing item is zero, the standard cost price sessions will be updated.

Solution: 131064
SITUATION IDENTIFIED IN:
""Compose the payments" " (tfcmg1240m000)
SITUATION DESCRIPTION:
Compose of payments or direct debits was made on the financial business partner instead of the pay-to business partner
due to this problem even when the pay-to bp for both the child customers/suppliers are same it was printing more than one
cheque for the same pay-to bp. Amount equal to the total invoices amount of each child business partner.
SOLUTION DESCRIPTION:
Now compose of payments or direct debits is made on the pay-to business partner. Hence no additional cheques will be
printed when the pay-to business partner for the different suppliers/customers are the same and composed in one payment
batch.

Solution: 131065
SITUATION IDENTIFIED IN:
"Payments on Purchase Invoices" (tfacp2523m000)
SITUATION DESCRIPTION:
If the payment (check) is made through an advance payment, then the check number is not visible in session "Payments
on Purchase Invoices" (tfacp2523m000) and "Payment Details" (tfacp2524s000) for the "Assignment Document".
SOLUTION DESCRIPTION:
The check number is displayed if the payment is made on the "Advance Payment" document.

Solution: 131069
SITUATION IDENTIFIED IN:
"Print Planned Inventory Transactions by Order" (whinp1401m000).
SITUATION DESCRIPTION:
Wrong Business Partner is mentioned on Planned Inventory Transactions.
SOLUTION DESCRIPTION:
From now on Planned Inventory Transaction record will hold the right (Ship-to) Business Partner.

Solution: 131071
SITUATION IDENTIFIED IN:
"Display Business Process" (tgbrg5501m000)
SITUATION DESCRIPTION:
When from a Dynamic Menu Browser with 2 different Roles the session "Display Business Process" is open for 2 processes
from different roles at the same time, then we get after some time the message "no authorization for this activity".
However the modeled authorization is there for the activity and the session can be started from the Dynamic Menu
Browser.
SOLUTION DESCRIPTION:
When 2 processes where opened at the same time, then the roles got mixed up and resulted in finding none of the two valid
for the activity. This caused the error message.
The session is changed to handle the roles in the display process mode correct, so the message will not appear incorrect
anymore.

Solution: 131072
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000/tfacr2520m000), "Purchase Invoices by Business Partner" (tfacp2522m000), "Sales
Invoices" (tfacr2522m000), "Business Partners Invoices in a Company" (tfacp2535m000/tfacr2535m000)
SITUATION DESCRIPTION:
Because of rounding differences, fully paid invoices are displayed in session "Open Entries"
(tfacp2520m000/tfacr2520m000).
SOLUTION DESCRIPTION:
Fully paid invoices are no longer displayed in the session.

Solution: 131073
SITUATION IDENTIFIED IN:
"Banks by Pay-by Business Partner" (tccom4515m000)
"Banks by Pay-to Business Partner" (tccom4525m000)
SITUATION DESCRIPTION:
The values for the IBAN and Bank ID are not visible in the overview sessions "Banks by Pay-from Business Partner"
(tccom4515m000) and "Banks by Pay-to Business Partner" (tccom4525m000).
SOLUTION DESCRIPTION:
The form for both sessions, have been extended with the fields for IBAN and Bank ID. They are both display fields.

Solution: 131076
SITUATION IDENTIFIED IN:
"Create Ascii Files Fields and Relations" (tuxch0203m000)
SITUATION DESCRIPTION:
If batch name was changed from one existing variant to another existing one description was not updated properly
[remained the old one].
SOLUTION DESCRIPTION:
Modification was made so every time batch name is changed description is updated accordingly.

Solution: 131082
SITUATION IDENTIFIED IN:
Processed Delivered Purchase Order (tdpur4223m000)
SITUATION DESCRIPTION:
It was not possible to delete the normal processed purchase order. The check has been done only for the BaaN project.
SOLUTION DESCRIPTION:
It is now deleted for the normal processed purchase order.
Solution: 131096
SITUATION IDENTIFIED IN:
"Query Field Data" (ttadv3182m000)
SITUATION DESCRIPTION:
Using Easy-SQL to create a query:
in session 'Query Field Data' (ttadv3182m000), when applying a Filter (even an empty filter), the program aborts with
error messages:
Extern var 'save.cqur' not found (<610() in object ottstpstandard) >
Undefined table save used (<240>() in object ottstpstandard)
Undefined symbol save.cqur' (type1) used in query (<240>() in object ottstpstandard)
SOLUTION DESCRIPTION:
Problem was caused by a variable in session ttadv3182m000, that was not declared as extern variable.
Declaration is corrected. The Filter can now be applied without these error messages.

Solution: 131098
SITUATION IDENTIFIED IN:
"Print Commitments and Actual Costs " (tpppc2412m000)
SITUATION DESCRIPTION:
When we have an order with negative quantities and negative amounts, the subtotal per supplier of commitment lines is not
correct. It works fine for positive quantities and amounts
SOLUTION DESCRIPTION:
Now the above-mentioned problem is solved. Program prints the subtotals correctly for the negative quantities also.

Solution: 131099
SITUATION IDENTIFIED IN:
Purchase Requisition Lines (tdpur2502m000)
SITUATION DESCRIPTION:
A Purchase Requisition Line is maintained with the lines text.
The Requisition Lines is Submit, approved and converted to RFQ.
After converting to RFQ the lines text in the Requisition is deleted.
SOLUTION DESCRIPTION:
The system will not delete the Purchase Requisition lines text after converting the Requisition to
RFQ.

Solution: 131100
SITUATION IDENTIFIED IN:
"Release to Warehousing" (tdsls4246m000).
SITUATION DESCRIPTION:
Sales Order cannot be released to Warehousing due to a combination of Shipping Constraint and Commitment Policy when
the ordered quantity is not (fully) committed.
SOLUTION DESCRIPTION:
A Commitment Policy can be defined per Item in session "Item Sales Data" (tdisa0101s000). When a Commitment Policy
(tdisa001.acom) is applicable one can specify a minimum quantity to be committed; either by quantity (tdisa001.mnqa) or
percentage (tdisa001.mnra).
Sales Order (Lines) for Commitment items having a Shipping Constraint unlike "No", can only be Released to Warehousing
when the total ordered quantity is committed. This to ensure all ordered goods can be delivered in time according to the
shipping constraint.
.
According to the Help text of "Min. Qty to Commit" (tdisa001.mnqa) and "Min.Rate to Commit" (tdisa001.mnra) there are no
allocation restrictions if both fields are equal to zero.
Having defined a Commitment Policy not equal "No" in combination with both fields equal to zero, a Sales Order for that
kind of item cannot be released to Warehousing (as described above).
In cases as described above, for the given Item no Commitment Policy should be defined.
To be able to do this following modifications were done:
1. In order to be able to choose another Commitment Policy for a given Item, the check to enable / disable the
corresponding list box (tdisa001.acom) was modified. For a given Item it was checked if Warehousing Orders existed
for it that had not been delivered yet. As a result, the list box would be disabled nearly all the time, once the system
was in use. Now the check is done on actual Commitments. See session "Inventory Commitment "(whinp2500m000).
When no commitments are present for the specified item it is possible to change the commitment policy.
Therefore please install Solution 130606 first. This solution handles the enabling / disabling of the Commitment Policy
list box as described above.
2. The help text for fields "Min. Qty to Commit" (tdisa001.mnqa) and "Min.Rate to Commit" (tdisa001.mnra) was modified.
It does not state anymore that when leaving both fields equal to zero, no commitments take place. This way is clearer,

that when no commitment is preferred, this should be defined by means of the Commitment Policy listbox.

Solution: 131105
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
131940, 211226
Descriptions:
- Defect 131940 AFS stpapi.synchronize.dialog made case Insensitive
- Defect 211226 BafindObjectInProcess error when running job
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 131122
SITUATION IDENTIFIED IN:
"Copy Item Production Data" (tiipd0202m000)
SITUATION DESCRIPTION:
When a new item is created from Item Production Data, the search key is not filled correctly.
SOLUTION DESCRIPTION:
The search key value is filled correctly in the Item Production Data, by placing the new item's search key value from the
General Item Data.

Solution: 131125
SITUATION IDENTIFIED IN:
"Attached Files" (dmdoc4540m000)
SITUATION DESCRIPTION:
Problem1:
While viewing the attached file with the document status "Submitted for review", system gives the error message "There is
no appropriate mounted area for your file, or vault server is not running".
Problem 2:
When the host is declared in capital letter, then system is giving the error message "There is no appropriate BW local
host" while viewing the file.
SOLUTION DESCRIPTION:
Solution 1:
View file option works fine with all status of document revision. System will not give the error message saying "There is
no appropriate mounted area for your file, or vault server is not running".
Solution 2:
System will allow enter the host name with capital letter only. System will not give error message "There is no
appropriate BW local host" while viewing the file.

Solution: 131131
SITUATION IDENTIFIED IN:
"Remove Contracts Incorrectly Linked to Sales Orders" (tdcor0011m000)
SITUATION DESCRIPTION:
The correction program gives an error 206 "Record not Locked" when running in update mode for a sales order with an
incorrect link to a sales contract.
SOLUTION DESCRIPTION:
The correction program runs without giving the error 206. The linked order line data is corrected.

Solution: 131132
SITUATION IDENTIFIED IN:
"Clear Corrupted Inventory" (whcor0200m000)
SITUATION DESCRIPTION:
Due to inventory corruption there is need for a generic correction program to rebuild the inventory.
SOLUTION DESCRIPTION:
This correction program will correct inventory and the receipt/consumption tables:
When checking the check box 'Rebuild Inventory Transactions by Item Warehouse' on the first form the table whinr110
(Inventory transactions by Item/Warehouse) is checked. Also the inventory on hand on item/warehouse level
(whwmd215.stoc) will be balanced with the inventory transactions by Item/Warehouse (whinr110) when this check box is
set.
The following tables will be corrected when checking the check box 'Rebuild Receipt/Consumption transactions' on the
first form:
- whinr112 (Inventory receipt transactions)
- whinr114 (Inventory receipt transaction consumptions)
Correcting Inventory:
To be able to correct the corrupted inventory additional checks/updates are done like:
- detecting/inserting missing shipment lines
- detecting/correcting outbound line status.
The inventory can be checked/corrected by item and location type as defined on the 2nd form.
The inventory values that are corrected by this session in order of detail are:
Inventory on item level:
- Inventory on hand (tcibd100.stoc)
- Inventory on hold (tcibd100.bloc)
Inventory on item/warehouse level:
- Blocked inventory (whwmd215.blck)
- Location Allocated inventory (whwmd215.alpl)
* Note that the inventory on hand on item/warehouse level (whwmd215.stks) is normally not updated by this program.
Inventory on item/warehouse/lot level:
- Inventory allocated (whltc105.stka)
- Inventory on hold(whltc105.stkh)
* Note that the inventory on hand on item/warehouse/lot level (whltc105.stks) is normally not updated by this program.
Stock point level:
- Inventory on hand (whinr140.stks)
- Inventory on hold (whinr140.stkh)
- Inventory on order (whinr140.stko)
- Allocated inventory (whinr140.stka)
Inventory structure level
- Inventory on hand in inventory unit (whinr150.stks)
- Inventory on hand in storage unit (whinr150.strs)
- Inventory blocked in storage unit (whinr150.strb)
- Inventory allocated in inventory unit (whinr150.stka)
- Inventory allocated in storage unit (whinr150.stkr)
Form description:
On the 2nd form the following options are available:
- Rebuild Locations of type 'Receipt'
- Rebuild Locations of type 'Inspection'
- Rebuild Locations of type 'Pick/Bulk' or empty Locations
- Rebuild Location of type 'Staging'
Selecting one or more of these options will make the program correct the inventory on stock point (whinr140) and
inventory structure (whinr150) level on the selected location type.
- balance inventory
When this option is selected the inventory by item (tcibd100), inventory by item/warehouse (whwmd215) and inventory by
item/ warehouse and lot (whltc105) is corrected. A part of this correction is based on the inventory figures on stock point
level. Therefore always first the inventory should be rebuild by location before 'balance inventory' is set.
The inventory on hand figures in the several inventory tables are balanced based on the inventory on item/warehouse level.
This means when selecting this option it is possible that the inventory on hand on stock point level is changed. There are
two possibilities:
1) Inventory on hand on item/warehouse level > inventory on hand on stock point level.
The program will increase the inventory on hand on stock point level and inventory structure level. In case of a location
controlled warehouse/item combination the created inventory is put on the 'correction' location as defined on the session
form. In case of none location controlled item/warehouse combination the created inventory is put on the empty location.
2) Inventory on hand on item/warehouse level < Inventory on hand on stock point level.
The program will decrease the inventory on hand on stock point level and inventory structure level. This is done based on
the outbound priority after the program first tried to decrease the inventory on the 'correction' location.
- correction location
Not actual location. If the filled in location does not exist yet the program will automatically create it. When the program
did create this location it will be blocked for all transactions.
This location is used by the program in case the inventory on stock point level and inventory structure level needs to be
decreased in order to get the inventory tables balanced (see balance inventory)
- Allow automatic processing of Adjustment Orders
There are instances where the correction program is unable to decrease the inventory at location level
(whinr140/whinr150) or at lot level to balance the inventory with the inventory on hand registered at item/warehouse
level (whwmd215.stoc). In that case message code 0001 ("Stock Points in Warehouse ### can not be decreased by ###") or
message code 0002 ("Stock Points for lot ### in Warehouse ### can not be decreased by ###") is printed. This situation
can be corrected by processing an adjustment order to get additional inventory available. When setting the option 'Allow
automatic processing of Adjustment Orders' this adjustment orders is created and processed automatically and the
correction program will continue with correcting the situation.
On the third form the following options are available:
- Insert missing Shipment Lines
This option will detect/create missing shipment lines. This option will be automatically set when the options 'Rebuild
Locations of type 'Pick/Bulk' or empty Locations' or 'Rebuild Location of type 'Staging' is set. This because the inventory
on the pick/bulk/staging or empty locations are partially rebuild based on the shipment lines.
- Check Outbound Line Data
This option will perform checks on the outbound line quantities and check/correct the outbound line status. Also this
option is automatically set when the options 'Rebuild Locations of type 'Pick/Bulk' or empty Locations' /'Rebuild Location
of type 'Staging' or 'Insert Missing Shipment Lines' is set.
- Maximum execution time and unit.
In this field the maximum time the program is allowed to run can be filled in.
After correcting the inventory of each item the program will check whether the maximum execution time has been exceeded.
If so, the program will quit and the report will be printed. On the report also a message is printed that the program has
been quit due exceeding of the maximum execution time.

Solution: 131135
SITUATION IDENTIFIED IN:
"Print Sales Contract Reports" (tdsls3401m000)
"Print Sales Contracts by Item and Price group" (tdsls3410m000)
"Print Sales Contract Line Reports" (tdsls3411m000)
SITUATION DESCRIPTION:
1. When opening print sessions via the 'print'-button on session "Sales Contracts" (tdsls3500m000) the contract number is
not filled on the print-sessions.
2. When printing 'Sales Contracts by Item and Price group' (tdsls3410m000) and 'Sales Contract Line Reports'
(tdsls3411m000), the effective and expiry dates are taken from the Sales Contract Header and not from the Lines.
SOLUTION DESCRIPTION:
1. On the following sessions the contract number is now automatically filled when opened from "Sales Contracts"
(tdsls3500m000):
- Print Sales Contract Reports (tdsls3401m000)
- Print Sales Contracts by Item and Price group (tdsls3410m000)
- Print Sales Contract Line Reports (tdsls3411m000)
2. On the 'Sales Contracts by Item and Price group' (tdsls3410m000) and "Sales Contract Line Reports" (tdsls3411m000)
the effective and expiry dates are taken from the Sales Contract Lines now.

Solution: 131137
SITUATION IDENTIFIED IN:
"Enterprise Modeler Editor" (tgEME)
SITUATION DESCRIPTION:
When you work with your DEM models in two languages at the same time, then the descriptions of your annotation are lost
or only the last one entered is available
SOLUTION DESCRIPTION:
Each time a diagram was saved, a new text number was created for annotation text. As annotation texts are language
depended stored, only for the actual language a new text number was generated and the link to the other language texts
were lost at that moment.
Now depending on new or modified annotation text, a new text number is created or the old text number is used. So the
link to other language texts will not be broken anymore.

Solution: 131141
SITUATION IDENTIFIED IN:
Using Worktop.
SITUATION DESCRIPTION:
A modification is made in Worktop regarding problem of defect 131653. This modification is dependents on another
modification in ostpoledaemon.
Therefore, when using Worktop 2.2.25 or higher, take care to have updated ostpoledaemon with this version.

Solution: 131156
SITUATION IDENTIFIED IN:
"Generate Installments to be Invoiced" (tppin4251m000)
"Element Budget (Material)" (tpptc1110s000)
"Activity Budget (Material Lines)" (tpptc2110s000)
SITUATION DESCRIPTION:
The Dutch translation in the following three cases is wrong:
In session tppin4251m000 "Generate Installments to be Invoiced" for the enumerated field "Set invoicable" the
translation of "date" was "Bedrijfskalender". This should be "Datum".
In sessions tpptc1110s000 "Element Budget (Material)" and tpptc2110s000 "Activity Budget (Material Lines)" the button
"Make Customized" was translated as "Artikelcategorie", where it should be "Klantspecifiek maken".
SOLUTION DESCRIPTION:
The translation issues as described in the Situation Description are solved.

Solution: 131157
SITUATION IDENTIFIED IN:
"Dependencies" (ttpmc1140m000)
SITUATION DESCRIPTION:
When you want to create co-requisite dependencies from own developed PMC solutions to Baan standard solutions in
the session "Dependencies" (ttpmc1140m000), you cannot select the correct Base VRC and solution by zooming.
In the Recipient part of PMC, the Base VRC's need not to be filled. To be able to zoom to Base VRC's (session
ttpmc0110m000) and select the Base VRC to which a dependency must be defined, this Base VRC should be in this
table.
However, when you want to enter a standard Base VRC in session ttpmc0110m000, the system returns a message "Not
authorized for standard VRC".
SOLUTION DESCRIPTION:
The authorization check has been removed from the session "Base VRC's" (ttpmc0110m000). So now it is possible to enter
also the Baan standard Base VRC's in this session (e.g. B40 c or B52 a). When you zoom to this session from defining
dependencies, also the standard Base VRC's are shown and can be selected.
To prevent other parties than Baan creating solutions for standard Baan Base VRC's by accident, the authorization
check is added to the "Solutions" session (ttpmc1100m000/ttpmc1500m000).

Solution: 131161
SITUATION IDENTIFIED IN:
"Inventory Inspection Data" (whinh3122s000)
SITUATION DESCRIPTION:
Two users can approve the same inspection line, using the " Approve remaining " and "Save" buttons. After approvals, the
status of the outbound order line is still " To be Inspected " and the
quantities are doubled in the shipment lines.
SOLUTION DESCRIPTION:
Now a check is made whether the inspections are done and if its done already a message " Approval line is not saved,
Inspection is already done " is displayed, the same record cannot be saved two times. This check is made for both "
Approve remaining " and " Reject Remaining " buttons.

Solution: 131163
SITUATION IDENTIFIED IN:
BSS
SITUATION DESCRIPTION:
When assigning an activity to an engineer, no warning message is given when the engineer does not have the capacity for
executing the activity.
SOLUTION DESCRIPTION:
When assigning an activity to an engineer, a warning message is given when an engineer does not have a capacity for
executing the activity. The behavior of BSS client is now made equal to iBaan ERP where a warning message is given.

Solution: 131172
SITUATION IDENTIFIED IN:
Confirm Shipments/Loads (whinh4275m000)
SITUATION DESCRIPTION:
Unable to confirm shipment, when the following steps are followed:
1. A sales order header is created
2. Two sales order lines are created for the header with 'Shipping constraint' as 'Release complete'. The items do not
have enough inventory in the warehouse.
3. The sales order is released to warehousing. Both the lines will be linked to the same warehouse order set.
4. It would not be possible to generate outbound advice for the above lines.
5. Then, for the same sales order header, two more sales order lines are inserted for different items, which have enough
inventory in the warehouse.
6. The lines are released to warehousing.
7. A new warehouse order set will be created for these two sales order lines.
8. When 'Direct Release' is executed from the session "Outbound Order Lines" (whinh2520m000), they will be only put to
the status 'Staged'.
9. Now, when tried to confirm shipment from the session "Confirm Shipments/Loads" (whinh4275m000), message
"Minimum tolerance of warehouse order is not met" will be printed.
SOLUTION DESCRIPTION:
Now it is possible to confirm shipment for the second warehouse order set.

Solution: 131178
SITUATION IDENTIFIED IN:
"Copy Project" (tipcs2210m000)
SITUATION DESCRIPTION:
Default values overwrite the entered values while pressing the continue button in the session "Copy Project". If the
user deselects the value "Copy Bom Data" or "Copy Routing Data", the system defaults the value to YES and
overwrites BOM and Routing.
SOLUTION DESCRIPTION:
The user can copy the project based on the copy criteria (selection in the session).

Solution: 131183
SITUATION IDENTIFIED IN:
"Ledger History by Business Partner" (tfgldl531m00l)
SITUATION DESCRIPTION:
Japanese history tables were not updated correctly when manual purchase invoice transactions were deleted.
SOLUTION DESCRIPTION:
Japanese history tables are updated correctly when manual purchase invoice transactions are deleted.

Solution: 131190
SITUATION IDENTIFIED IN:
"Project" (tppdm6100s000)
SITUATION DESCRIPTION:
Problem 1: Whenever the value of enterprise unit is changed, a check is done on the user type & if the user is a "Normal
User", then a check is done to see if the Fin. company of first enterprise unit & second are different. If they are
different an error message is returned. But, next time when the same enterprise unit value is passed, no error message is
returned. The check on Authorizations is not consistent.
Problem 2: When a new project record is opened, keeping the old one open, the enterprise unit field of the new project has
the value of old project instead of it's own value.
SOLUTION DESCRIPTION:
Solution 1: Whenever the value of enterprise unit is changed, a check is done on the user type & if the user is a "Normal
User", then a check is done to see if the Fin. company of first enterprise unit & second are different. If they are
different an error message is returned. But, even when an error has occurred, the financial company gets the value of new
financial company. So, next time when the same enterprise unit value is passed, the check on financial company fails & no
error message is returned.
Now, the financial company will be assigned a new value only if there are no errors. So, the check will always be
consistent.
Solution 2: Now, always the enterprise unit of current project will be found & displayed.

Solution: 131192
SITUATION IDENTIFIED IN:
Match Electronic Bank Statements (tfcmg5212m000)
SITUATION DESCRIPTION:
When statement date = 0, wrong message 'Amount = 0, no automatic match' is shown while trying to match.
SOLUTION DESCRIPTION:
Now, A new message "Statement date = 0" is created to show the correct reason for not matching

Solution: 131196
SITUATION IDENTIFIED IN:
Hours Accounting by Project (tihra1502m000)
SITUATION DESCRIPTION:
While refreshing "Hours Accounting by Project", the total Man and Machine hours are not updated correctly if some
new project hours are added in "Enter Hours Accounting"(tihra1101s000). The Man and Machine hours are updated only
after closing and opening the session "Hours Accounting by Project"(tihra1502m000).
SOLUTION DESCRIPTION:
The total Man and Machine hours are updated correctly when refresh is done after a new record is added.

Solution: 131197
SITUATION IDENTIFIED IN:
Production planning (tisfc1101s000)
SITUATION DESCRIPTION:
For a Phantom Item operation, the 'Inventory unit' of 'Cycle Time' in "Production planning" (tisfc1101s000) is wrong. The
unit displayed is that of the main item but not that of the phantom item.
SOLUTION DESCRIPTION:
In "Production planning"(tisfc1101s000)", for a Phantom Item operation, the 'Inventory unit' of 'Cycle Time' displayed is
the unit of the phantom Item but not that of the end item.

Solution: 131198
SITUATION IDENTIFIED IN:
"Reports" (ttadv3530m000)
SITUATION DESCRIPTION:
Problem with SCM (Software Configuration Management).
The problem occurs when a new report script is created and checked-out for changing.
After the modified report script is checked-in, the added lines are not present anymore. Only the revision text is present in
the report script.
SOLUTION DESCRIPTION:
The copy of the modified report script from the SCM-directory to the regular directory for the report script failed for new
report scripts.
Solved by changing a check before the copying, so now also new report scripts are copied.

Solution: 131203
SITUATION IDENTIFIED IN:
"Uninstall Solution" (ttpmc2208s000)
SITUATION DESCRIPTION:
When a solution containing tools components was uninstalled, it could happen that the environment was corrupted and
users could not login anymore. This happened when PMC uninstalled a solution with components that are essential for
importing the uninstall-dump, like PMC-components, the standard program, etc. During the uninstall process these
components were deleted from the Baan environment and thus the components could not be activated anymore to import
the uninstall-dump.
SOLUTION DESCRIPTION:
During the uninstall process, tools components will not be deleted anymore before the uninstall-dump is imported. They
will be overwritten from the uninstall-dump. This is a generic change made for all tools components.
As a consequence, new tools components that were added to the system will remain there, although the solution has been
uninstalled. But because for existing components the old version is re-installed, the new tools components will not be
touched.

Solution: 131206
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
In session "Sales Order Lines" (tdsls4101s000) the field "Make Customized" is translated to Dutch with "Artikelcategorie"
which is incorrect.
SOLUTION DESCRIPTION:
The field 'Make Customized' is translated with 'Klantspecifiek maken' in Dutch. Also the German label is translated to
"Kundenspezifisch anpassen".

Solution: 131211
SITUATION IDENTIFIED IN:
"Check Control Account Write-off Currency Difference Bookings" (otfcorcont_ac05)
SITUATION DESCRIPTION:
The invoice line number was not displayed on the report of the correction program "Check Control Account Write-off
Currency Difference Bookings"(otfcorcont_ac05).
SOLUTION DESCRIPTION:
The invoice line number will be printed, but it will be the line number of the first document in case there is multiple
line numbers present for the same document.
Also in case there are different type of documents present (e.g. Unallocated, Advance payment) for the same document but
with different line numbers, then an error message is printed and no records are updated.

Solution: 131214
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
The bank file that is created after conversion in EBS is truncated, when the path name for the EBS archive directory is
very long.
SOLUTION DESCRIPTION:
The bank file name in the EBS archive directory is no longer truncated.

Solution: 131215
SITUATION IDENTIFIED IN:
Shipment lines by warehousing order (whinh4131s000)
SITUATION DESCRIPTION:
When a shipment lines are confirmed, it is not possible to confirm the shipment line, as there is error set in one function
mistakenly.
SOLUTION DESCRIPTION:
The shipment lines are now able to confirm without any error message pops up.

Solution: 131216
SITUATION IDENTIFIED IN:
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
When printing the actual cost price of a project, the system is not printing the Purchase Order receipts linked to a back
order.
SOLUTION DESCRIPTION:
The system prints all purchase orders including the backorders while printing the actual cost price of a project.

Solution: 131225
SITUATION IDENTIFIED IN:
Purchase Order lines (tdpur4101s000)
SITUATION DESCRIPTION:
For an Item, the Tax in Item Purchase Data is filled. A Purchase Order line is inserted for this Item. The country of the
Warehouse (Order line) has a blank Tax Code defined. Now, system is not picking up that code, it picks up the Tax code
mentioned in Item Purchase Data.
SOLUTION DESCRIPTION:
Now, if a blank Tax code is maintained for a country of Warehouse, then it is picked correctly when the Purchase Order
line is inserted.

Solution: 131230
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260m000)
SITUATION DESCRIPTION:
1.The Deletion date on the report is based on creation date of the file
2.The name of the last Buisines partner is shown on the report instead of the company that is paying.
SOLUTION DESCRIPTION:
Now the layout is correct.

Solution: 131232
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Currency difference calculated for receipt transaction of invoice with fixed hard.
SOLUTION DESCRIPTION:
Currency difference won't be calculated now for receipt transaction of invoice with fixed hard.

Solution: 131234
SITUATION IDENTIFIED IN:
"Print Costing History by Order" (ticst2401m000)
SITUATION DESCRIPTION:
When running session ticst2401m000 Print Costing History by Order the logfile is written with errors 'get_format_entry
pattern '0050.0' index 3 entry 0 not found'. On a windows based Baan server this error is written in the event viewer. This
error occurs because the system couldn't find the rounding factor.
SOLUTION DESCRIPTION:
The rounding factor is dependent of the currency used on the form. With this currency and the format code the rounding
is determined.

Solution: 131239
SITUATION IDENTIFIED IN:
"Remove Contracts Incorrectly Linked to Sales Orders" (tdcor0011m000)
"Correct Incorrect Contract Data" (tdcor0013m000)
SITUATION DESCRIPTION:
It is possible that the correction programs remove a correct link from a Sales Order Line to a Sales Contract in the
following situations:
- The "Price Date Type" parameter (tdpcg0100s000) is on system- or delivery date
- The order date of the Sales Order Lines is different from the header
SOLUTION DESCRIPTION:
First the value of the "Price Date Type" parameter is read
For every new orderline it is checked which is the correct date with which to check the effectivity period of the contract.
a. If the Price Date Type is on 'orderdate' the order date of the Sales Order line is used.
b. If the Price Date Type is on 'systemdate' the transaction date of the Sales Order line is read from the history, on that date
the orderline is entered.
c. If the Price Date Type is on 'delivery date' the delivery date of the Sales Order line is used.
In this way only linked orderline data or contract history of corrupted data is corrected.

Solution: 131241
SITUATION IDENTIFIED IN:
"Import Data Dictionary" (ttiex1285m000)
SITUATION DESCRIPTION:
<#HTML>

### Note1: This solution only applies to customers, which use a Windows or AS400 platform for their Baan
Server.
Note2: This solution also applies to customers, who did not yet install the solution 130907 or
129145, but have scanned this solution (individually or in a weekly collection) before December 18,
2002.

After you installed solution 130907 (solution 129145 for BaanERP 5.2 a customers),
you were not able to install import dumps anymore. This applies to all kinds of importing software into your Baan
Environment:
- Import a normal dump with session "Import Data Dictionary" (ttiex1285m000);
- Import a patch with session "Import Patch" (ttiex1284m000);
- Install PMC solution with session "Process Solutions" (ttpmc2101m000);
- Uninstall PMC solution with session "Process Solutions" (ttpmc2101m000); this is very critical, because components
will be deleted without being replaced by the components from the uninstall dump!
These sessions do not return an error message, so all software seems to be imported, but no components are really added or
updated in your system. PMC solutions get the status "Installed" and also the solution history has been modified, but the
components in the system are still the old ones.
SOLUTION DESCRIPTION:
The problem in the import session has been solved. All components, which are present in the solution dump(s) are added
or updated in the system.

Solution: 131244
SITUATION IDENTIFIED IN:
"Select Values for GRNI Reconciliation" (tfacp1235m000)
SITUATION DESCRIPTION:
The "Select Values for GRNI Reconciliation" (tfacp1235m000) creates manual orders when selecting price variance
transactions related to project.
SOLUTION DESCRIPTION:
The project price variance transactions are picked up correctly now with the correct order number.

Solution: 131247
SITUATION IDENTIFIED IN:
"Update Actual Calendar" (tcccp0230m000)
SITUATION DESCRIPTION:
When an actual calendar is updated, the derived (child) calendars are added.
In adding there is a check of the child calendar is already added or outside user selection range.
If there were actual calendar lines available for the child calendar an error would occur : "Fatal error : Use of NULL
pointer on"
SOLUTION DESCRIPTION:
When an actual calendar is updated with derived child's with lines, the update will not be aborted with : "Fatal error :
Use of NULL pointer on"

Solution: 131249
SITUATION IDENTIFIED IN:
Integration Transactions by Project / Order (tfgld4510m000)
SITUATION DESCRIPTION:
When the Receipt amount of the purchase order for a service subcontracting activity is zero, the financial transaction
Service/Subcontracting is not logged. Due to this, the 'Invoice accrual' accounts does not get balanced correctly.
SOLUTION DESCRIPTION:
For Service/Subcontracting finance transactions are logged even when the amount is zero, with the quantity not being
zero.

Solution: 131251
SITUATION IDENTIFIED IN:
"Purge Sales Invoice Data" (cisli3210m000)
SITUATION DESCRIPTION:
Sales Invoices, which are still "Open" in Finance, can be archived. But those Sales invoices, which are Fully Paid, cannot
be archived.
SOLUTION DESCRIPTION:
Now only those sales invoices, which are fully paid, can be archived.

Solution: 131256
SITUATION IDENTIFIED IN:
Production Planning (tisfc1101s000)
SITUATION DESCRIPTION:
Consider a manufactured item linked to an operation having yield less than 100%. A production order is raised for this
item. The production rate of the operation in production planning is calculated without taking the yield into consideration.
SOLUTION DESCRIPTION:
Earlier when a production order was created, the production rate value in production planning session was a copy of the
value from the routing session. This production rate at the routing level is calculated without taking the yield into account.
In the production order level, the production rate should be calculated taking the yield percentage into account during the
order creation itself. This is working fine with this solution.

Solution: 131261
SITUATION IDENTIFIED IN:
"Finalize Accepted GRNI Entries" (tfacp1239m000)
SITUATION DESCRIPTION:
Old coding statement (attr.input) is used in Baan ERP in session "Finalize Accepted GRNI Entries" (tfacp1239m000).
SOLUTION DESCRIPTION:
The statements have been removed.

Solution: 131270
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In session "Purchase Invoices" (tfacp1110s000), when a new invoice related to order is entered, and then after entering the
order number, the tax amount field is not getting filled up. Only when the cursor is on field tax amount, the amount is
displayed but later when the amount is changed, the tax amount is not getting recalculated automatically.
In session "Purchase-Invoice Transactions" (tfacp1120s000), if a shifted vat code is entered the tax amount is not
calculated by default.
SOLUTION DESCRIPTION:
The default tax amounts are calculated in both the sessions now.
In session ""Purchase Invoices" if the tax amount is changed manually, then the tax amount is not recalculated again if
the amount is changed.

Solution: 131271
SITUATION IDENTIFIED IN:
"Print rejects" (tisfc0403m000)
SITUATION DESCRIPTION:
Printing of production order rejects in sessions "Print rejects" (tisfc0403m000) and "Print rejects history" (ticst3403m000)
is not possible by selecting date/time range 'FROM' and 'TO'. User can select and print the rejects up to 'TO' date only.
SOLUTION DESCRIPTION:
User can print the production order rejects by selecting the 'FROM' to 'TO' range of the date/times in the sessions "Print
rejects" (tisfc0403m000) and "Print rejects history" (ticst3403m000).This will give user the option to select the rejects
based on 'FROM' and 'TO' dates of the order.

Solution: 131274
SITUATION IDENTIFIED IN:
"Export Language-Dependent Software Components" (ttadv6230m000)
SITUATION DESCRIPTION:
Session "Export Language-Dependent Software Components" (ttadv6230m000) is used to export Help Information of
tables/tablefields in a certain VRC. The option "Hypertext Info Lines" is marked.
For Help texts that are related to enum-domains, the Info lines in the created exportfile do not contain the correct
information, they show the text "Not implemented" instead.
The problem only occurs if a package VRC is selected in ttadv6230m000 that does not belong to the package combination
of the user.
SOLUTION DESCRIPTION:
When exporting Help texts for a VRC that does not belong to the user's package combination, the enum descriptions
were not found.
The Help texts should in that situation be found by using the development VRC structure. This has been solved.
Now the Help text Info lines show the correct information.

Solution: 131280
SITUATION IDENTIFIED IN:
Print and/or Delete Purchase Order History (tdpur5201m000)
SITUATION DESCRIPTION:
A Purchase Order is maintained and a line is inserted for an Item. The Purchase Order parameter "Prompt for Change
Codes" is set to YES. A change is made in the Purchase Order header and the user is asked to enter Change codes, which
is done by him. Now the Purchase Order is processed and deleted. While deleting the Purchase Order History, fatal error
605 (Reference exists) is given by system.
SOLUTION DESCRIPTION:
While deleting the Order history for a Purchase Order (A Change code was maintained for this Order), system doesn't give
Error 605 (Reference exists) and the records are deleted properly.

Solution: 131283
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
It is not possible to map on "Series" (tfgld415.grno) for a warehousing (valuation) order. For the financial integrations of
this origin, the field "Series" is not filled.
When posting in finance, an error occurs: "Error log: Dimension X for ledger account Y must be filled."
SOLUTION DESCRIPTION:
The "Series" is filled now, enabling the possibility to map on it.
A valuation order number is generated, based on the number group in "Number Group for Valuation" (whina000.vang). The
Series Length of this number group is used to determine the series of the created order number.

Solution: 131290
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
1. In session "Purchase Invoices" (tfacp1110s000), a cost invoice is entered with "Rate Determiner" set to "Manually
Entered". Then the transaction lines are entered and the home currencies are calculated with the manually entered amount on
the invoice. After closing the session transaction lines, if the rate is changed on the invoice, the rate is not updated for
the transaction lines. Hence it creates an unbalanced document.
2. If the rate determiner is of type "Manually entered", then after changing the rate on the form, the amount in home
currency is not updated immediately when exiting the field currency rate.
3. An invoice with no tax code is saved. Later when this invoice is updated with a group tax code the tax transactions are
not created, hence the batch remains unbalanced. And it is no longer possible to finalize the batch.
SOLUTION DESCRIPTION:
1. If the lines or costs are entered for a purchase invoice, then it is no longer possible to change the field's currency, rate
determiner and currency rate on the form.
2. After changing the rates, when exiting the field the amount in home currency is updated.
3. When the invoice is updated with a group tax code, the tax transactions are created correctly.

Solution: 131297
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
The IBAN functionality is not yet available for the BTL91 ABN Amro payment file (report 14) and for the remittance
report 4.
SOLUTION DESCRIPTION:
The IBAN functionality has been implemented now for the BTL91 report and for the remittance report.

Solution: 131299
SITUATION IDENTIFIED IN:
"Archive Projects" (tppdm7820m000)
SITUATION DESCRIPTION:
When projects are archived, the necessary tables from the Enterprise Management Module (tcemm) are not archived in
the archive company. Only the field Logistic Company is changed into the archive company number.
Moreover the action for these tables is performed again for every project within the selection. This is unnecessary.
SOLUTION DESCRIPTION:
When projects are archived, the necessary tables from the Enterprise Management Module (tcemm) are now stored in the
archive company.
Also this archiving is executed only once instead of for every project within the selection.

Solution: 131303
SITUATION IDENTIFIED IN:
"General Table Display" (ttaad4500)
SITUATION DESCRIPTION:
From session General Table Display a text editor can be started when a reference to a text is present in the current record.
This text editor is started in ReadWrite mode.
SOLUTION DESCRIPTION:
From session General Table Display the text editor will be started in ReadOnly mode.

Solution: 131307
SITUATION IDENTIFIED IN:
"Download, Scan and Connect Solution (Multi-Level)" (ttpmc2210s000)
SITUATION DESCRIPTION:
The session "Download, Scan and Connect Solution (Multi-Level)" (ttpmc2210m/s000) can be used to download dumps from
the Baan FTP-server. But if you try this for weekly collections, the message "Downloaded file corrupt" is printed on the
report.
SOLUTION DESCRIPTION:
The Multi-Level Download Tool (MLDT) has been changed. Now also weekly collections can be downloaded and
scanned.
Note that the MLDT will not automatically download the dependent solutions of the individual solutions, which are
contained in the weekly collections.

Solution: 131311
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When receiving an order change message, with a change type code |Cancel Order" on the header, and some lines have a
change type code |Change Line", the order is cancelled but not all lines are cancelled.
SOLUTION DESCRIPTION:
There was no check on the type of change code for the order lines in case of canceling the complete order (order header
change type code |Cancel Order"). The program script has been corrected. Now, an error is generated if the change type on
the header is |Cancel Order" but the lines have a code other than |Cancel Order Line". The |Errors in Received Messages"
report will show the lines and the error message(s) that modification or adding order lines is not allowed.

Solution: 131314
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
When creating a follow-up Call, the program picks up the wrong Currency, Country and Language but this information
should be the similar to the Parent Call.
SOLUTION DESCRIPTION:
When creating a follow-up Call the fields Currency, Country and Language are retrieved from the Parent Call.

Solution: 131315
SITUATION IDENTIFIED IN:
"Selection of Open Items" (tfcmg2118s000)
SITUATION DESCRIPTION:
In case Business Partners have more than 4 children, in some situations a fatal error "Index 11 out of dims [1] 10" occurs.
SOLUTION DESCRIPTION:
Now the fatal error does not occur anymore, even with a more complex structure and more children.

Solution: 131328
SITUATION IDENTIFIED IN:
"Totals for Business Partner by Company" (tfacr2534m000)
SITUATION DESCRIPTION:
Fatal Error in session "Totals for Business Partner by Company " : 'Index 3 out of dims, cannot continue in
tfacr2534m000'
SOLUTION DESCRIPTION:
Fatal error does not occur now.

Solution: 131350
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
In the session "Reconciliation Payments/Receipts" (tfcmg2103s000) anticipated payments can be reconciled. If an
anticipated payment is reconciled partially and later on the status is changed from "partially" to "rejected", the whole
anticipated payment is rejected and not just the partially reconciled one. This happens, when the remainder of the
anticipated payment amount has not been reconciled yet.
SOLUTION DESCRIPTION:
Rejection of partially reconciled payments now occurs for the partially reconciled amount only, when the remainder of
the anticipated payment has not been reconciled yet.

Solution: 131362
SITUATION IDENTIFIED IN:
"Base Units" (tcmcs0100s000)
SITUATION DESCRIPTION:
In Baan IV a warning comes up when the field "Base Length Unit" or "Base Area Unit" is changed. The warning states:
"Base length unit and base area unit must be of the same potential".
SOLUTION DESCRIPTION:
The warning is now also present in BaanERP.

Solution: 131363
SITUATION IDENTIFIED IN:
"Maintain installments" (tppin4151s000)
SITUATION DESCRIPTION:
When the contract amount for a business partner is split up in several currencies, the default installment amount doesn't
change with the currency.
SOLUTION DESCRIPTION:
Now the default amount of the installment changes according to the selected currency.
The default will be the remaining amount of the contract sub-amount for that selected currency.

Solution: 131365
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4501m300)
SITUATION DESCRIPTION:
When the purchase order lines are received with the 'Global Confirmation of Receipts' option, the same Receipt number is
not applied to all the lines. Every line is assigned with a unique receipt number.
SOLUTION DESCRIPTION:
All the lines have the same receipt number when they are received with the 'Global Confirmation of Receipts' option.

Solution: 131377
SITUATION IDENTIFIED IN:
"Project" (tppdm6100s000)
SITUATION DESCRIPTION:
When a user (located in timezone A) was trying to create a project and the periods in tcccp060 (Period Table) was created
with timezone B, an error message would popup that "periods in Project are not equal to periods in Finance". This message
was technically correct, but functionally incorrect.
SOLUTION DESCRIPTION:
When user 1 (located in timezone A) and user 2 (located in timezone B) are trying to create the same project there
should be no difference when the Project periods are matched with the Finance periods, even when the periods were
created in timezone C.
However, it is strongly recommended to create the Periods in the Periods table (tcccp0560m000) with the same timezone
as the timezone of the Financial company to which they are going to be linked.

Solution: 131381
SITUATION IDENTIFIED IN:
"tfacr1110s000" (Sales Invoices)
SITUATION DESCRIPTION:
Updating of Net amount (tfgld110.amnt) and Base value (tfgld110.bvam.l) in Maintain Tax analysis (tfgld110) is wrong.
SOLUTION DESCRIPTION:
When the cash discount parameter is "ON", the Net amount and the Base value are updated correctly.

Solution: 131382
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100m000)
SITUATION DESCRIPTION:
The reference given on the 2nd form of session 'Bank Transactions' is not filled within 'Non finalized transactions'
(tfgld102) during payment/receipt reconciliation. The reference within tfgld102 is generated automatically and filled
with bank relation and anticipated document number. This is a particular problem when recording the cheque number sent
to the supplier or received by a customer.
SOLUTION DESCRIPTION:
After reconciliation, if the reference is blank, the reference field within 'Non-finalized transactions' is filled with the
bank relation and anticipated document number for the documents that were reconciled. If the reference is filled manually
during reconciliation, this manual entered reference is considered.

Solution: 131386
SITUATION IDENTIFIED IN:
"Transfer order manually" (cprrp1250s000)
SITUATION DESCRIPTION:
Message code "cprrp1250.2" appears instead of the message, "The purchase order type is not allowed".
SOLUTION DESCRIPTION:
The message appears correctly.

Solution: 131390
SITUATION IDENTIFIED IN:
"Print Detailed Scheme of Fixed Asset Transactions" (tffas0441m000)
SITUATION DESCRIPTION:
In report "Purchase Details" of session "Print Detailed Scheme of Fixed Asset Transactions" (tffas0441m000), the column
"By end of fiscal year" was showing incorrect values in case of disposed assets.
SOLUTION DESCRIPTION:
In case of disposed assets, the column "By end of fiscal year" displays zero value.

Solution: 131393
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
When a manual warehouse transfer of an item is completed, the valuation results are booked in finance, even though the
issue and receipt values do not differ.
SOLUTION DESCRIPTION:
The actual amounts from warehousing and calculated amounts from costing are rounded based on same domain, which
eliminates the calculation of valuation results, if receipt and issue values are same.

Solution: 131395
SITUATION IDENTIFIED IN:
"Objects by Business Partner" (tscfg2503m000)
SITUATION DESCRIPTION:
User is not able to sort the Objects in the session "Objects by Business Partner (tscfg2503m000)". Only one sort option is
provided. No other relevant options are available for sorting the objects in the above sessions.
SOLUTION DESCRIPTION:
One more sort option is made available for the user for searching the objects using the search argument.

Solution: 131396
SITUATION IDENTIFIED IN:
"Select Batches for Finalization " (tfgld1212s000)
SITUATION DESCRIPTION:
After Installing solution 130368, Fatal error "No definition in definition file for sopen ( F_BRDD:dtfgld126, dtfgld126) "
occured.
This error message occurs when the Create runtime data dictionary for the table tfgld126 is not run.
SOLUTION DESCRIPTION:
The Finalization process is now modified so that when there is no data definition present for table tfgld126, updating the
table will be skipped.
Solution: 131397
SITUATION IDENTIFIED IN:
"Print Origin by Lot" (whltc3401m000)
"Print Origin by Order" (whltc3402m000)
"Print Where-used Lots" (whltc3400m000)
SITUATION DESCRIPTION:
When performing lot tracking for negative Production receipt, error 'Index 100 out of dims (1) 99' occurs.
SOLUTION DESCRIPTION:
It is possible to perform lot tracking without any error.

Solution: 131416
SITUATION IDENTIFIED IN:
"Business Processes" (tgbrg5500m000)
SITUATION DESCRIPTION:
When the copy option is used for a marked Business Process, then all data is taken from the original Business Process, but
the description is emptied.
SOLUTION DESCRIPTION:
The session is changed, so that now also the original description is put as default for the copied Business Process.
The problem is also solved for Business Control Diagrams, Business Functions, Reference Models, Project Models and
Wizards.

Solution: 131444
SITUATION IDENTIFIED IN:
"Price Simulator" (tdpcg0200m300)
SITUATION DESCRIPTION:
he Discount percentage displayed in the session "Purchase Order Lines" (tdpur4101s000) and the session "Price
Simulator" (tdpcg0200m300) are different.
SOLUTION DESCRIPTION:
The prices displayed through the Purchase Order Line and the Price Simulator are the same.

Solution: 131449
SITUATION IDENTIFIED IN:
"Service Order Actual Other Costs" (tssoc2141s000)
SITUATION DESCRIPTION:
When a service order quotation is transferred to a service order, an actual other cost line is created with description
"Quotation Invoice". The invoice amount field for this cost line is always zero and is not equal to the service quotation
amount.
SOLUTION DESCRIPTION:
When a service order quotation is transferred to a service order, the "Quotation Invoice" other cost line has the invoice
amount filled correctly.

Solution: 131450
SITUATION IDENTIFIED IN:
"Print Payment Advice" (tfcmg1401m000)
SITUATION DESCRIPTION:
In a payment advice, when different invoices of onetime business partners are linked to different addresses; the payment
advice is printed wrongly.
SOLUTION DESCRIPTION:
Now the names of the Business partners are printed correctly

Solution: 131453
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
Starting a second document from the Dynamic Menu Browser on a Windows 2000 client gives an error, although the
document is opened.
SOLUTION DESCRIPTION:
On Windows 2000 another return value was send, when there was already a document opened. The session did not
recognize this return value.
Now the session recognizes also this return value and does not give an error.

Solution: 131457
SITUATION IDENTIFIED IN:
"Export and Translate XML-files to start Baan Workflow" (tgbrg1288m000)
SITUATION DESCRIPTION:
When an export is done on a NT server, then always an error -1 is given.
SOLUTION DESCRIPTION:
This error was referring to the fact, that the session could not find the "Translator" executable.
This was caused by the fact, that the slashes were used in the wrong way.
The function used to detect, which slashes to use in the path-name to the "Translator" executable is changed.
Now an export on a NT-server is going correct.

Solution: 131461
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When doing an internal sale from one "company" to another the system books tax even though the internal invoice-to
business partner has all tax flags deactivated. When the session "Confirm Shipments/Loads" (whinh4275m000) is run, it
creates an invoice for the warehouse order. When this invoice is confirmed the tax amounts are filled and posted to
finance.
SOLUTION DESCRIPTION:
The tax details are picked from the first record for the invoice-to business partner.

Solution: 131462
SITUATION IDENTIFIED IN:
"Maintain and confirm backorders" (tdsls4125m000)
SITUATION DESCRIPTION:
It is not possible to manually confirm a backorder for a Purchase Item with Order Policy set to 'To Order' in combination
with direct delivery. Whereas when for the same situation the parameter 'Confirm Backorders' is on 'Automatic', the
backorder is confirmed.
SOLUTION DESCRIPTION:
It is possible to manually confirm a backorder for a Purchase Item with Order Policy set to 'To Order' in combination with
direct delivery.

Solution: 131475
SITUATION IDENTIFIED IN:
"Lots" (whltc1100s000)
SITUATION DESCRIPTION:
In session "Lots", when the lot date is updated, then incase there are inventory transactions present with the same
transaction date but with different inventory date, then the error message "Error 100 Duplicate" pops up, and it not
possible to update the date.
SOLUTION DESCRIPTION:
The inventory transactions are updated successfully. If there are duplicates present then the sequence number is updated.

Solution: 131478
SITUATION IDENTIFIED IN:
"Master Data Parameters" (whwmd0100s000)
SITUATION DESCRIPTION:
1. Dutch and German description of the field, "Revisions Active" is incorrect. It says, "Koppeling met Finance" and
"INV-Modul mit FiBu verb."
2. The Help text for this field is in all languages incorrect.
SOLUTION DESCRIPTION:
1. The description of the field "Revisions Active" is correct in all languages now.
2. The Help text is now as follows:
"If this check box is selected, you can enter revisions on warehouse orders. The warehouse order contains data about the
revisions that are used in a project."

Solution: 131480
SITUATION IDENTIFIED IN:
"Move Plan to Planned Orders" (cprmp2240m000)
SITUATION DESCRIPTION:
During the transfer of Plans to Planned Orders, many warnings like ' WARNING: OVERFLOW: format="9999"
value="-2147483648" '
are logged in BW and in Windows Event Viewer.
This is the result of corrupted data. (there were missing records in table cprpd120: Plan Item Codes)
SOLUTION DESCRIPTION:
Error handling improved to avoid improper use of incomplete data.

Solution: 131481
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
It is not possible to receive purchase order lines after the lot cost has been assigned. For Purchasing and Pricing
conversion factors are used, such that the lot price (per inventory unit) will be more than 4 decimals.
SOLUTION DESCRIPTION:
Lot prices where not compared in a correct way.

Solution: 131485
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0520m000)
SITUATION DESCRIPTION:
While using back-flush materials (in a multi-environment setup) at the time of closing production orders, the integration
transactions created have a wrong finance company. For example if the material issue warehouse is linked to a different
financial company the integration transactions for material issue are still created in the original company as the finance
company.
SOLUTION DESCRIPTION:
The integration transactions for production issue are now created with the correct finance company.

Solution: 131491
SITUATION IDENTIFIED IN:
"pmc correction " (ttpmccoriex)
SITUATION DESCRIPTION:
Solution 131241 was not quite correct.
SOLUTION DESCRIPTION:
This solution contains a correction on the ttpmccoriex object. For more information read the details in solution 131241

Solution: 131495
SITUATION IDENTIFIED IN:
"Material to issue for Production orders" (ticst0101s000)
SITUATION DESCRIPTION:
Items with alternative item with 'Replacement' flag as YES cannot be issued through "Material to issue for Production
orders" (ticst0101s000). If an Item is having alternative item with 'Replacement' flag as YES, then while issuing the item
an error message will pop up and it is not possible to issue the item and proceed further.
SOLUTION DESCRIPTION:
If an Item is having a set up with alternative item with 'Replacement' flag as YES, then while issuing this item a question
will pop up "Item is replaced; Continue?" in "Material to issue for Production orders" (ticst0101s000). If the answer is YES
for the question, then this means that user is aware that the item is a 'Replacement' item but wants to issue the material.
If the answer is NO, then the material cannot be issued through "Material to issue for Production orders" (ticst0101s000).

Solution: 131497
SITUATION IDENTIFIED IN:
"Check / Change rounding of amounts." (tfcor9996s000)
SITUATION DESCRIPTION:
This correction program does not check or change the Payment difference amounts in Accounts payable and Accounts
receivable Open Entries. This could cause differences in Control Account check list.
SOLUTION DESCRIPTION:
Now the correction program also checks the payment difference amounts to see if they are correctly rounded.

Solution: 131500
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
This receipt is not performed automatically for the following situation:
- an intra warehouse item transfer
- a transfer manual order
- an empty receipt procedure is defined
Because in this case, the destination location is mandatory on the order header, the receipt should be processed
automatically. If the destination location is not filled, automatic receipt is not possible. That is correct, else the order
get stuck during the inbound procedure.
SOLUTION DESCRIPTION:
For the empty receipt procedure a check is added to verify if the destination location is known. In that case, an automatic
receipt is done for an intra warehouse item transfer.

Solution: 131503
SITUATION IDENTIFIED IN:
"Warehouse Orders" (whinh2100s000)
SITUATION DESCRIPTION:
It is not possible to change the information present under the tab "Miscellaneous" for a sales order of type transfer
between a normal warehouse and a consignment warehouse.
SOLUTION DESCRIPTION:
The information under the tab "Miscellaneous" can now be modified.
Solution: 131505
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
130273, 132218
Descriptions:
- Defect 130273 Not all marked records are deleted when using shift and ctrl during marking
- Defect 132218 AFS stpapi.get.mess.code doesn't return the message completely
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 131512
SITUATION IDENTIFIED IN:
"Match/Approve Purchase Invoices by range" (tfacp2280m000)
SITUATION DESCRIPTION:
The problem occurs in session tfacp2280m000 (Match/Approve Purchase Invoices by range).
When entering a packing slip afterwards and trying to match and approve an invoice with a purchase order with multiple
lot receipts and one packing slip, the message "Match succeeded, not all documents balanced' appears.
When not entering a packing slip the session works correctly.
SOLUTION DESCRIPTION:
When entering a packing slip afterwards and trying to match and approve an invoice with a purchase order with multiple
lot receipts and one packing slip, the message "Match succeeded, not all documents balanced' doesn't appear anymore..

Solution: 131513
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
In the following situations inventory variances were created:
- change price after receipt for a purchase order
- actual costs differed from estimated cost for a production order
When processing the inventory variances by running session whina1200m000, it was not possible to map on the related
order data.
Example: Financial Business Partner Group (tfgld415.ficu) or Main Work Center (tfgld415.mnwc) are not filled.
SOLUTION DESCRIPTION:
Now the relevant order data is retrieved and posted in the financial package.

Solution: 131517
SITUATION IDENTIFIED IN:
"Element Budget (Material)" (tpptc1110s000)
"Activity Budget (Material Lines)" (tpptc2110s000)
SITUATION DESCRIPTION:
In sessions tpptc1110s000 "Element Budget (Material)" and tpptc2110s000 "Activity Budget (Material Lines)" the button
"Make Customized" was translated as "Artikelcategorie", where it should be "Klantspecifiek maken".
SOLUTION DESCRIPTION:
The label that is used on the button was not present in original solution.

Solution: 131520
SITUATION IDENTIFIED IN:
"Scan Solution File" (ttpmc2200s000)
SITUATION DESCRIPTION:
When a PMC solution with a text attached to it, is scanned, the message "Table F 6Text not expected in pmc info file" is
displayed and the scanning stops.
This only happens when the solution is scanned in the same BSE-environment where it has been created.
SOLUTION DESCRIPTION:
When the scanning process encounters a text field in the dump file for a solution, which is already present in the PMC
registry, it is skipped and the scanning continues with the data following the text field.

Solution: 131533
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
When sales order is raised in one company and the sales office is linked to another finance company, running
correction program "Correct COGS" (cicor0111m000) gives error "Record not locked".
SOLUTION DESCRIPTION:
Now the fatal error does not arise.

Solution: 131539
SITUATION IDENTIFIED IN:
"Specific Business Partner 2 Selection" (tdsst2105s000)
SITUATION DESCRIPTION:
The business partner 2 code is not checked. The system should not allow users to enter business partner codes that do no
exist in the business partner tables.
SOLUTION DESCRIPTION:
A check function has been implemented in the program script. This is to allow the session to check the business partner
code entered. The record won't be saved in case the code does not exist.

Solution: 131540
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
It is possible to create a manual outbound advice (whinh2125s000) for a return purchase order although there is no
Project (Baan Project-TP) inventory present.
SOLUTION DESCRIPTION:
When trying to create a manual outbound advice (session whinh2125s000) for a return purchase order without Project
inventory, the following message is shown: "Advice shortage of X for item Y"

Solution: 131548
SITUATION IDENTIFIED IN:
"Select Batches for Finalization " (tfgld1212s000)
SITUATION DESCRIPTION:
After installing solution 130368, when the create table is not done for the new table tfgld126, then during finalization
process, the records in Non-finalized transaction table was deleted, but no records were created in the Finalized transaction
table.
SOLUTION DESCRIPTION:
To Avoid the data corruption during finalization, now a check is done to see if tfgld126 table has been created properly.
Please run correction program tfcor1826m000 to initialize the table Reference to finalized transaction ( tfgld126 ). When this
table is not initialized, then this table is not used for updates.

Solution: 131558
SITUATION IDENTIFIED IN:
"Delete Budget Version Data" (tpptc5201m000)
SITUATION DESCRIPTION:
The Dutch translation of "Version" is wrong. It now says "Tekeningversie" but it should be "Versie".
SOLUTION DESCRIPTION:
The Dutch translation is now "Versie".

Solution: 131559
SITUATION IDENTIFIED IN:
"Solutions and Patches" (ttpmc1500m000/ttpmc1100m000)
SITUATION DESCRIPTION:
After the installation of solution 131157 you were not able anymore to create new PMC solutions.
Also the insert-button was not active or inactive at the right moment;
SOLUTION DESCRIPTION:
The authorization check has been corrected; now you are able to add solutions for non-standard Base VRC's again. Also the
availability of the insert-button has been corrected.

Solution: 131563
SITUATION IDENTIFIED IN:
"Receipt corrections" (whinh3121s000)
SITUATION DESCRIPTION:
While doing a receipt correction, the system gives the error message "Receipt Correction not allowed for already
approved items" even when the order is not approved.
SOLUTION DESCRIPTION:
System allows user to do the receipt correction and if the quality management package is implemented, the system will
update the corresponding inspection order quantities also.

Solution: 131568
SITUATION IDENTIFIED IN:
"Check Ledger account Write-off Currency Difference Booking" (otfcorcont_ac05)
SITUATION DESCRIPTION:
In the correction program "Check Ledger account Write-off Currency Difference Booking", in case the line number of the
invoice is 5 digits long, the report doesn't print the line number correctly.
SOLUTION DESCRIPTION:
The report now prints the line number of the invoice correctly.

Solution: 131579
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When assigning an advance receipt with an amount different from the sales invoice amount, in some cases the assignment
transaction is not balanced because of a difference of 0.01. As a result it cannot be finalized
SOLUTION DESCRIPTION:
Now the transaction is balanced and can be finalized.

Solution: 131580
SITUATION IDENTIFIED IN:
"Import Actual Performance" (tfcat2220m000)
SITUATION DESCRIPTION:
The session "Import Actual Performance" (tfcat2220m000) did a wrong import of the records from HRA if the option "Old
Values" on the form is set to "Replace".
SOLUTION DESCRIPTION:
The import of actual performance information from HRA module takes place correctly.

Solution: 131585
SITUATION IDENTIFIED IN:
"Labor Costs" (tpppc2531m000)
SITUATION DESCRIPTION:
In Dutch the Label "Normal Hours" reads "Normal Hrs".
In Dutch the Label "Overtime" reads "Gewone werkuren" which means Normal workinghours.
SOLUTION DESCRIPTION:
Now the label "Normal Hours" reads "Uren" and the label "Overtime" reads "Overuren".

Solution: 131595
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When doing an internal sale from one "company" to another the system books tax even though the internal invoice-to
business partner has all tax flags deactivated. When the session "Confirm Shipments/Loads" (whinh4275m000) is run, it
creates an invoice for the warehouse order. When this invoice is confirmed the tax amounts are filled and posted to
finance.
SOLUTION DESCRIPTION:
The tax details are picked from the invoice-to business partner-department combination entered in the sales order. In case it
is not found the first record from the invoice-to business partner.

Solution: 131597
SITUATION IDENTIFIED IN:
"Standard labor" (tppdm0511m000)
SITUATION DESCRIPTION:
When the labor is used in both element & activity budgets, the error message duplicates. This has to be corrected.
SOLUTION DESCRIPTION:
Now the error message is displayed only once even when labor is used in both element and activity budgets.

Solution: 131603
SITUATION IDENTIFIED IN:
"Inventory - Inspection Data" (whinh3122s000)
SITUATION DESCRIPTION:
No new shipment line is created when two users at the same time approve an advice line for the same advice
(whih3122s000)
SOLUTION DESCRIPTION:
In such a situation also for the second line a correct shipment line is created.

Solution: 131605
SITUATION IDENTIFIED IN:
"Purchase Order Types" (tdpur0194s000)
SITUATION DESCRIPTION:
Not possible to change the Series for the Order Types that are in use.
SOLUTION DESCRIPTION:
Change in the Order Series, Quotation Series, and the Contract Series is now possible, even when they are of the Order
type that are in use.

Solution: 131606
SITUATION IDENTIFIED IN:
"Hours-Accounting Transactions" (tphrs1500m000)
SITUATION DESCRIPTION:
The description of the wage component is not displayed.
SOLUTION DESCRIPTION:
The description of the wage component is displayed now.

Solution: 131614
SITUATION IDENTIFIED IN:
"Remove Contracts Incorrectly linked to Sales Orders / Print Order Acknowledgements/RMAs" (tdcor0011m000 /
tdsls4401m000)
SITUATION DESCRIPTION:
Label was missing on Dutch form of session (correction program) "Remove Contracts Incorrectly linked to Sales
Orders" (tdcor0011m000).
Labels were missing on Dutch and German report (Sales Order Acknowledgement/RMA; tdsls440101000). This was only
relevant for B50L_c_bgl0.
SOLUTION DESCRIPTION:
Labels have been translated and are now shown properly on form and report.

Solution: 131625
SITUATION IDENTIFIED IN:
"Clear Corrupted Inventory" (whcor0200m000)
SITUATION DESCRIPTION:
Due to inventory corruption there is need for a generic correction program to rebuild the inventory.
SOLUTION DESCRIPTION:
This correction program will correct inventory and the receipt/consumption tables:
When checking the check box 'Rebuild Inventory Transactions by Item Warehouse' on the first form the table whinr110
(Inventory transactions by Item/Warehouse) is checked. Also the inventory on hand on item/warehouse level
(whwmd215.stoc), will be balanced with the inventory transactions by Item/Warehouse (whinr110) when this check box is
set.
The following tables will be corrected when checking the check box 'Rebuild Receipt/Consumption transactions' on the
first form:
- whinr112 (Inventory receipt transactions)
- whinr114 (Inventory receipt transaction consumptions)
Correcting Inventory:
To be able to correct the corrupted inventory additional checks/updates are done like:
- detecting/inserting missing shipment lines
- detecting/correcting outbound line status.
The inventory can be checked/corrected by item and location type as defined on the 2nd form.
The inventory values that are corrected by this session in order of detail are:
Inventory on item level:
- Inventory on hand (tcibd100.stoc)
- Inventory on hold (tcibd100.bloc)
Inventory on item/warehouse level:
- Blocked inventory (whwmd215.blck)
- Location Allocated inventory (whwmd215.alpl)
* Note that the inventory on hand on item/warehouse level (whwmd215.stks) is normally not updated by this program.
Inventory on item/warehouse/lot level:
- Inventory allocated (whltc105.stka)
- Inventory on hold (whltc105.stkh)
* Note that the inventory on hand on item/warehouse/lot level (whltc105.stks) is normally not updated by this program.
Stock point level:
- Inventory on hand (whinr140.stks)
- Inventory on hold (whinr140.stkh)
- Inventory on order (whinr140.stko)
- Allocated inventory (whinr140.stka)
Inventory structure level
- Inventory on hand in inventory unit (whinr150.stks)
- Inventory on hand in storage unit (whinr150.strs)
- Inventory blocked in storage unit (whinr150.strb)
- Inventory allocated in inventory unit (whinr150.stka)
- Inventory allocated in storage unit (whinr150.stkr)
Form description:
On the 2nd form the following options are available:
- Rebuild Locations of type 'Receipt'
- Rebuild Locations of type 'Inspection'
- Rebuild Locations of type 'Pick/Bulk' or empty Locations
- Rebuild Location of type 'Staging'
Selecting one or more of these options will make the program correct the inventory on stock point (whinr140) and
inventory structure (whinr150) level on the selected location type.
- balance inventory
When this option is selected the inventory by item (tcibd100), inventory by item/warehouse (whwmd215) and inventory by
item/ warehouse and lot (whltc105) is corrected. A part of this correction is based on the inventory figures on stock point
level. Therefore always first the inventory should be rebuild by location before 'balance inventory' is set.
The inventory on hand figures in the several inventory tables are balanced based on the inventory on item/warehouse level.
This means when selecting this option it is possible that the inventory on hand on stock point level is changed. There are
two possibilities:
1) Inventory on hand on item/warehouse level > inventory on hand on stock point level.
The program will increase the inventory on hand on stock point level and inventory structure level. In case of a location
controlled warehouse/item combination the created inventory is put on the 'correction' location as defined on the session
form. In case of none location controlled item/warehouse combination the created inventory is put on the empty location.
2) Inventory on hand on item/warehouse level < Inventory on hand on stock point level.
The program will decrease the inventory on hand on stock point level and inventory structure level. This is done based on
the outbound priority after the program first tried to decrease the inventory on the 'correction' location.
- correction location
Not actual location. If the filled in location does not exist yet the program will automatically create it. When the program
did create this location it will be blocked for all transactions.
This location is used by the program in case the inventory on stock point level and inventory structure level needs to be
decreased in order to get the inventory tables balanced (see balance inventory)
- Allow automatic processing of Adjustment Orders
There are instances where the correction program is unable to decrease the inventory at location level
(whinr140/whinr150) or at lot level to balance the inventory with the inventory on hand registered at item/warehouse
level (whwmd215.stoc). In that case message code 0001 ("Stock Points in Warehouse ### can not be decreased by ###") or
message code 0002 ("Stock Points for lot ### in Warehouse ### can not be decreased by ###") is printed. This situation
can be corrected by processing an adjustment order to get additional inventory available. When setting the option 'Allow
automatic processing of Adjustment Orders' this adjustment orders is created and processed automatically and the
correction program will continue with correcting the situation.
On the third form the following options are available:
- Insert missing Shipment Lines
This option will detect/create missing shipment lines. This option will be automatically set when the options 'Rebuild
Locations of type 'Pick/Bulk' or empty Locations' or 'Rebuild Location of type 'Staging' is set. This because the inventory
on the pick/bulk/staging or empty locations are partially rebuild based on the shipment lines.
- Check Outbound Line Data
This option will perform checks on the outbound line quantities and check/correct the outbound line status. Also this
option is automatically set when the options 'Rebuild Locations of type 'Pick/Bulk' or empty Locations' /'Rebuild Location
of type 'Staging' or 'Insert Missing Shipment Lines' is set.
- Maximum execution time and unit.
In this field the maximum time the program is allowed to run can be filled in.
After correcting the inventory of each item the program will check whether the maximum execution time has been exceeded.
If so, the program will quit and the report will be printed. On the report also a message is printed that the program has
been quit due exceeding of the maximum execution time.

Solution: 131629
SITUATION IDENTIFIED IN:
"Maintain Table Relations (Import)" (tu(da)xch0521m000)
SITUATION DESCRIPTION:
Invalid sorting keys were available in Baan versions B50b and newer, which created confusion: less records were shown
after applied sorting key. There should be only two sorting keys for this session for the view change.
SOLUTION DESCRIPTION:
Session modified so that only valid sorting keys are available.

Solution: 131632
SITUATION IDENTIFIED IN:
"Cycle Counting/Adjustment order lines" (whinh5101s000)
SITUATION DESCRIPTION:
Problem in Inventory adjustment if Package definition not used on a stock point and inventory is not available directly in
base unit (but only in higher levels) and in the session "Cycle Counting/Adjustment order lines" (whinh5101s000), if user
enters the storage unit as the base unit.
The Actual inventory defaulted should be zero, but a non-zero value is defaulted. This confuses the user and moreover,
when the user modifies it to zero (so that the 'Variance' is a negative value), and stock point inventory goes wrong.
SOLUTION DESCRIPTION:
The quantity defaulted for the field 'Actual Inventory' will be equal to the quantity that is available in the warehouse for
the 'Storage unit' entered by the user.
For example, if there is one box of an item which contains ten pieces of the same item, then if the user enters the 'Storage
unit' as box, the 'Actual inventory' defaulted will be 1. But, if the user enters the 'Storage unit' as pieces, the 'Actual
inventory' defaulted will be 0.

Solution: 131634
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
A Sales Order Line (session tdsls4101s000) is created and saved. Without leaving the session a new sales order line is added
(using the button on tdsls4501m000 or Ctrl-N). When tabbing through the fields the 'item' defaults with the same item as the
previous added line (correct) the 'order quantity' is zero (correct). The following is incorrect: the 'discount percentage',
'discount code' and 'discount amount' are taken from the first line.
SOLUTION DESCRIPTION:
When following the above procedure the fields 'discount percentage' and 'discount amount' are set to zero and the field
'discount code' is made empty

Solution: 131641
SITUATION IDENTIFIED IN:
"Booked price variance Analysis" (tfacp1460m001)
SITUATION DESCRIPTION:
When running session "Booked Price Variance Analysis - tfacp1460m001" by printing the report, without details set, when
the numbers are big it is impossible to read them as they appear with #######.
SOLUTION DESCRIPTION:
Because of enlarging the printable numbers in session
"Booked Price Variance Analysis - tfacp1460m001" the numbers are printed well

Solution: 131642
SITUATION IDENTIFIED IN:
"Print Order Acknowledgments" (tdsls4401m000)
SITUATION DESCRIPTION:
In the following setup for session Print Sales Order Acknowledgment (tdsls4401m000) not all orders in a selection are
printed:
- Orders are entered using option "Specific Orders";
- The Device Selection should be 'User Definition';
- One order (not the last) has a line with the Item Code System filled.
SOLUTION DESCRIPTION:
Using the setup as described in the Situation Description, all orders are correctly printed.

Solution: 131649
SITUATION IDENTIFIED IN:
"Check/change rounding of amounts" (tfcor9996s000)
SITUATION DESCRIPTION:
The following problems are present in the correction program.
1. The selection on the form checked for periods, which are closed. Hence it is not possible to detect rounding differences
in closed periods.
2. The report was printing the wrong fiscal year.
3. In case of linked documents to an invoice, the rounding on the linked document's invoice amounts was on the linked
document's currency instead of on the invoice currency.
SOLUTION DESCRIPTION:
The following correction has been done.
1. The selection will not check for closed periods, but while updating the finalized transactions, the period checking will
be done.
2. The report prints the correct fiscal year.
3. For rounding the linked document's invoice amounts, the invoice currency and invoice rounding is used.

Solution: 131655
SITUATION IDENTIFIED IN:
"Generate project structure for product variant" (tipcs2220m000)
SITUATION DESCRIPTION:
When using the same generic item several times on several positions in a generic BOM or BOM structure, then the
generation of a product variant structure is aborted with the following blocking error message: "Item with this generated
item code already present". This problem only occurs when the PCF-parameter "Identifying Item code" is set to "Yes".
SOLUTION DESCRIPTION:
It's now possible to have the same generic item several times on several positions in a generic BOM or BOM structure and
generate a product variant structure without getting the blocking error-message: "Item with this generated item code
already present". This message will still be printed, but now only as a warning message, and not as a blocking message.
This message is only non-blocking if in the BOM, duplicate customized item codes are created on different positions with
identical derived-from items. Creating duplicate main items remains blocked.

Solution: 131660
SITUATION IDENTIFIED IN:
"Print Receipts" (tdpur4431m000)
SITUATION DESCRIPTION:
Unable to print the report for the option "Receipts (by Invoice)".
SOLUTION DESCRIPTION:
It is possible to print report for the option "Receipts (by Invoice)".

Solution: 131667
SITUATION IDENTIFIED IN:
"Import Data Dictionary" (ttiex1288m000)
SITUATION DESCRIPTION:
After exporting a program script with its object with session ttiex1280m000 (Export Data Dictionary), and next importing
this export dump with session ttiex1285m000 (Import Data Dictionary) the compilation date and compilation time of the
imported object is not correct.
This situation occurs when the dump is imported into a VRC where the object is already present, and when the
form-option Overwrite is checked in session ttiex1285m000.
The compilation date and time of the imported object should be equal to the compilation date and time of the object in
the export dump.
The compilation date and time of an object can be checked in session ttadv2439m000 (Print Objects by Program
Scripts/Libraries).
SOLUTION DESCRIPTION:
The compilation date and compilation time of the imported object are now equal to the compilation date and compilation
time of the object in the dump.

Solution: 131668
SITUATION IDENTIFIED IN:
"Item/Channel Master Plan" (cprmp2401m000)
SITUATION DESCRIPTION:
When printing the Item/Channel master plan with the report type "Detailed (Item)", the projected inventory was not
printed on the report.
SOLUTION DESCRIPTION:
When printing the Item/Channel master plan with the report type "Detailed (Item)", the project inventory is printed on the
report.

Solution: 131670
SITUATION IDENTIFIED IN:
"Create Runtime Data Dictionary" (ttadv5210m000)
SITUATION DESCRIPTION:
In session Create Runtime Data Dictionary all user files of the package combinations are dumped. If an environment has
many users, this takes a long time.
SOLUTION DESCRIPTION:
The dumping of the user files is made optional.

Solution: 131672
SITUATION IDENTIFIED IN:
"Print Goods Received Note" (whinh3412m000)
SITUATION DESCRIPTION:
When performing the original print of "Goods Received Note" (whinh3412m000), for the second and third receipt of
production main items in warehousing, the report only prints the still to be manufactured quantity remaining.
SOLUTION DESCRIPTION:
When the Goods Received Note is printed for the first time for the second or later receipts of production main items in
warehousing, it prints the second receipt quantity and the new pending quantity remaining if any.

Solution: 131690
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
131892, 211742
Descriptions:
- Defect 131892 AFS FS in 4GL caused hanging sessions
- Defect 211742 AFS action on locked records
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 131693
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103m000)
SITUATION DESCRIPTION:
While reconciling the document a fatal error is occurred and stops the process.
SOLUTION DESCRIPTION:
Reconciliation is possible with out any fatal error.

Solution: 131710
SITUATION IDENTIFIED IN:
"Update sales statistics" (tdsst0201m000)
"Update purchase statistics" (tdpst0201m000)
SITUATION DESCRIPTION:
The statistics are wrongly updated in case partial updates are done by using the actual customer data. The data is
getting corrupted when updating the statistics for an order, which has been already updated but the header was modified
afterwards. The system add negatives figures where codes e.g. country code is empty. The existing figures get doubled.
SOLUTION DESCRIPTION:
The business partner related tables are read in the wrong place. This has been reversed. These tables will be read now right
before the actual customer data is getting assigned

Solution: 131712
SITUATION IDENTIFIED IN:
"Sales Contract Acknowledgment" (tdsls3405m000)
"Sales Contract Reminder: (tdsls3406m000)
SITUATION DESCRIPTION:
Several fields are missing from the Sales Contract Acknowledgment and Sales Contract Reminder (when comparing
with Sales Order Acknowledgment):
- Terms of Payment Code and Terms of Delivery Code. Now only the description of both fields are printed
- Alternative Item Code
- Item Revision Code
SOLUTION DESCRIPTION:
The following data is now also printed on the Acknowledgment and the Reminder:
- Terms of Payment Code and Terms of Delivery Code
- Alternative Item System
- Item Revision Code

Solution: 131725
SITUATION IDENTIFIED IN:
"Select Values for Receivable Invoices Specifications" (tfacp1235m000)
SITUATION DESCRIPTION:
The message tfacps1435.07 that comes in the error report for language 1 (Dutch) is not correct.
SOLUTION DESCRIPTION:
The message now shows the correct description.

Solution: 131728
SITUATION IDENTIFIED IN:
"Enterprise Units" (tgbrg0131s000)
SITUATION DESCRIPTION:
When in session "Enterprise Units"(tgbrg0530m000) is double-clicked on an unit, which is not of type site, then the details
of the next unit are shown and not of the selected unit.
SOLUTION DESCRIPTION:
The session is changed and when now a double-click is done the details of the selected unit are shown.

Solution: 131734
SITUATION IDENTIFIED IN:
"Archive Warehousing Order History" (whinh2255m000)
SITUATION DESCRIPTION:
Order history of warehouse orders of transaction type "item transfer" is not archived using session whinh2255m000
"Archive Warehousing Order History" even when item transfer is not linked to any project.
SOLUTION DESCRIPTION:
An order of transaction type "item transfer" will be archived in session whinh2255m000 also in following situations when
order is not linked to a project or project has status closed or archived

Solution: 131735
SITUATION IDENTIFIED IN:
"Release to Warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
An item has commitment policy 'Batch' and there is not enough inventory. This item is sold on a sales order without the
order step 'Generate Inventory Commitments' and with a shipping constraint. It is not possible to release the order to
warehousing. The error message is: "Quantity not yet fully committed. Release to warehousing not allowed"
SOLUTION DESCRIPTION:
It is possible to release such a sales order line to warehousing when it meets the following conditions:
- The sold item has commitment policy 'Batch'
- The sales order has no 'Generate Inventory Commitments' (whinp2200m000) in the order steps.
- The sales order line has a shipping constraint
- No quantity is committed yet (or the whole quantity is committed)

Solution: 131737
SITUATION IDENTIFIED IN:
"Program Scripts" (ttadv2530m000)
SITUATION DESCRIPTION:
A program script or library can be deleted from the Baan table, even when the source and object files are still on the file
system.
This occurs when the user permissions on the operating system are not sufficient to allow these files to be deleted.
For reports it is not possible to delete a report from Baan, when the report script can not be deleted: a message is given to
inform the user that a file could not be deleted, and the session aborts. The report is not deleted from the Baan table.
Deleting reports and program scripts should work the same.
SOLUTION DESCRIPTION:
Now the delete of a program script/library is similar like the delete of a report.
An error message is displayed to inform the user that a file could not be deleted.
The program script/library is not deleted from the Baan table. The session is not aborted.
The report session has also been modified: the session is not aborted anymore when the delete action failed.

Solution: 131738
SITUATION IDENTIFIED IN:
"Update sales statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
When actualizing the sales statistics of a customized item which is derived from a generic item, the following
error message occurs in the report: "Standard item XXXXXXXXXXXXXXXXXXXXXXXXXXXXX not found" This happens for
instance when the product variant for project item has been regenerated.
SOLUTION DESCRIPTION:
This error message will not be printed anymore in case the item data is not present, this will prevent that a huge report is
generated. However, the sales statistics will not be processed when the item data is not present because relevant data such
as product class might be missing.

Solution: 131742
SITUATION IDENTIFIED IN:
"Rebuild Planned Inventory Transactions" (whinp1200m000)
SITUATION DESCRIPTION:
Rebuild Planned Inventory Transactions (whinp1200m000) does not take into account Service Order Material Lines with
delivery type 'By Purchase Order', which results in low allocations for Items used in these Service Order Material
Lines.
SOLUTION DESCRIPTION:
Rebuild Planned Inventory Transactions (whinp1200m000) will take into account the following delivery types for Service
Order Material Lines:
From Warehouse
From Warehouse in Car
From Warehouse by Transport
From Service Kit
By Purchase Order
To Warehouse
To Warehouse by Transport

Solution: 131749
SITUATION IDENTIFIED IN:
"Doubtful sales invoice" (tfacr2140m000)
SITUATION DESCRIPTION:
Business partner's description is not displayed for all business partners.
SOLUTION DESCRIPTION:
Now description is displayed properly for all the available business partners.

Solution: 131753
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
The invoice rate for an invoice with a manually entered rate is changed in session "Purchase Invoices" (tfacp1110s000). If
the difference between the old rate and the new rate was less than the tolerance for the home currency, then the home
currency amount in the non-finalized transactions was not updated correctly.
If for an invoice related to orders where the order number is not yet filled, the currency rate picked up is always
1.000001.
SOLUTION DESCRIPTION:
The rates are correctly picked up and updated in non-finalized transactions.

Solution: 131755
SITUATION IDENTIFIED IN:
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
Error "Run time function call problem" on running the session "Print Actual Cost-Price by Project" (tipcs3462m000) for
a PCS project having surcharges more than 200.
SOLUTION DESCRIPTION:
The allocation of maximum surcharges for a PCS project has been increased to 500 from 200.

Solution: 131756
SITUATION IDENTIFIED IN:
"recompute phase-numbers" (cprpd6200m000)
SITUATION DESCRIPTION:
Big performance-problems when this session is run, both for net-change and regenerative mode.
SOLUTION DESCRIPTION:
Improved the processing and skipped all bom-line expired on the starting date of the current scenario.
Also a new table-booster is made for the warehouse-table (tcemm112) that must be added and activated for this session.

Solution: 131758
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Up to Period (Logistical)" (tfacp1439m000)
SITUATION DESCRIPTION:
When the session Print Receivable Invoices Up to Period (Logistical) ( tfacp1439m000 ) is run in logistical company it
receives the following error message - "
"process 6 - fatal error: bis_alloc_mem: sym '', i=0""
SOLUTION DESCRIPTION:
The session Print Receivable Invoices Up to Period( Logistical) ( tfacp1439m000 ) can now only be started from a
financial company.

Solution: 131765
SITUATION IDENTIFIED IN:
"Sales Contract Lines" (tdsls3101s000)
SITUATION DESCRIPTION:
1. After entering the item on a Sales Contract Line (tdsls3101s000), the Alternative Item Code is not automatically picked
up.
2. When modifying the Sales Contract Line, the fields "Item Code System" and "Alternative Item Code" are disabled.
SOLUTION DESCRIPTION:
1. After entering the item on a Sales Contract Line (tdsls3101s000), the Alternative Item Code is automatically picked up.
2. When there is no sales order or sales schedule linked to a contract (called quantity and invoice quantity both are
zero), the fields "Item", "Item Code System", "Alternative Item Code" and "Apply contracts for all Items in Price group"
are enabled. Otherwise they are disabled.

Solution: 131766
SITUATION IDENTIFIED IN:
"Item Production Data" (tiipd0101s000)
SITUATION DESCRIPTION:
System is not changing the Critical in Master Planning flag to NO in the session "Item Production Data"
(tiipd0101s000), when the order system is changes from planned to manual in the session "Item Ordering Data"
(tcibd2100s000).
SOLUTION DESCRIPTION:
System will change the Critical in Master Planning flag to NO in the session "Item Production Data" (tiipd0101s000),
when the order system is changes from planned to manual in the session "Item Ordering Data" (tcibd2100s000).

Solution: 131767
SITUATION IDENTIFIED IN:
Storage List (whinh2515m100)
SITUATION DESCRIPTION:
In session Storage List (whinh2515m100) the procedure mask (whinh215.pmsk isn't updated correctly. The activity field
(whinh215.acti) of Inbound Advice is updated (changed from 'y' to 'e') but the procedure mask wasn't updated with it.
This means that the wrong procedure mask can be written into table Inbound Advice (whinh215).
SOLUTION DESCRIPTION:
The script is changed. The procedure mask now is updated in the correct way. The corresponding field in the procedure
mask is now also changed from 'y' to 'e'

Solution: 131769
SITUATION IDENTIFIED IN:
"Export Solution" (ttpmc1200s000/ttpmc1200m000)
SITUATION DESCRIPTION:
When you export a solution in PMC, a check is done whether the objects, you want to export, are compiled in debug-mode.
If so, you cannot export the solution. This check was not correct for report-objects; only the object for the first language
was checked.
SOLUTION DESCRIPTION:
For all languages specified on component-level in the solution the check for a debug-object is performed.
Solution: 131773
SITUATION IDENTIFIED IN:
"Control account checklist" (tfacp2415m000)
SITUATION DESCRIPTION:
Incase two finance companies share the same transaction type and series for anticipated payment, and when there is an
inter company payment by one of this company, and a normal anticipated payment by another company then the control
account checklist can potentially show differences when there are no differences.
SOLUTION DESCRIPTION:
The situation happened because, the document number of a non-inter-company payment and an inter company payment were
same. Because of this the normal anticipated payment was mistaken to be a inter company payment. The situation no
longer occurs.

Solution: 131778
SITUATION IDENTIFIED IN:
"Print Questionnaire Results " (tdpur8493m000)
SITUATION DESCRIPTION:
When the user is trying to print the questionnaire results by any year/period, in the session "Print Questionnaire Results
(tdpur8493m000)", the system always prints the report for the first period present for the given Business Partner, Period
table code, Year, Period and Employee. The system is not considering the period given by the user.
SOLUTION DESCRIPTION:
The user can able to print the questionnaire results by any year/period. The system will only print the questionnaire results
report for the period given by the user.

Solution: 131780
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
Converted EBS Picking up details of last invoice even when the EBS file contains details of several invoices.
SOLUTION DESCRIPTION:
Converted EBS Picks up of details of the required number of invoices when the EBS file contains details of several
invoices

Solution: 131794
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When a supplier invoice has been entered and the Supplier (Business partner) is changed, then there is no more check done
for duplicate invoices for the supplier. This could potentially result in entering a duplicate supplier invoice for the same
supplier without any warning.
SOLUTION DESCRIPTION:
Now, when the business partner is changed, the check on duplicate supplier invoice is done again.

Solution: 131795
SITUATION IDENTIFIED IN:
"Sales Contracts" (tdsls3100s000)
SITUATION DESCRIPTION:
The status of the Sales Contract Header (tdsls3100s000) is 'Free' or 'Active'. When one of the sales contract lines is on
status 'Terminated' and the Contract Header is (de)activated, the 'Terminated' line gets (de)activated again. When this is
for some reason not possible, the contract remains on status 'Free' or 'Active'.
SOLUTION DESCRIPTION:
The line with status 'Terminate' is (de)activated when possible. But when changing the status for some reason is not
possible, the line remains on 'Terminated'. This does not influence the (de)activating of a contract by using the
(de)activate option on the contract header. All other lines and contract header are (de)activated. An message is shown why
the 'terminated' contract line can not be (de)activated.

Solution: 131802
SITUATION IDENTIFIED IN:
"Maintain Approvals" (whinh3522m000)
SITUATION DESCRIPTION:
When ever receipt correction is made more than once on a purchase order, then the system while processing the inspection
order is not closing the QMS inspection order. It keeps the Inspection order with status "Processed".
SOLUTION DESCRIPTION:
The system which processing the inspection order in the quality management side, will close the inspection order and
updates the approval record also.

Solution: 131807
SITUATION IDENTIFIED IN:
"Confirm Shipment" (whinh4275m000)
SITUATION DESCRIPTION:
When Confirming Shipment during a Triangular Invoicing process covering EU and Non-EU countries, an incorrect Tax
Code was retrieved and stored in Finance for the Purchase Invoice.
SOLUTION DESCRIPTION:
When Confirming Shipment during a Triangular Invoicing process covering EU and Non-EU countries, the correct Tax
Country and Tax Code are retrieved and stored in Finance for the Purchase Invoice.
Important Note:
This situation described above can be summarized as a transaction between an EU and a Non-EU Country. This means that
other situations where Sales and Purchase transactions between an EU and a Non-EU Country are involved are influenced
as well.
Beside this, even Sales transactions between two Non-EU countries are influenced.
Example; a Sales Order Line from Home Company Switzerland to Norway previously showed the Tax Country from the
Sales Order Header, but now it will show the Tax Country which is the Ship-From Country, which is Switzerland in this
case.

Solution: 131811
SITUATION IDENTIFIED IN:
"Reorganize/Reconfigure tables" (ttadv5215m000)
SITUATION DESCRIPTION:
Bdbreconfig functionality is changed. Now it will no longer stop as soon as an error has occurred.
It will reconfigure as many tables as possible, and mention the errors at the end.
To handle this changed functionality correctly, the tools sessions that use bdbreconfig need to be modified as well.
However the tools sessions should still work correctly with the binairy bdbreconfig from older portingsets.
SOLUTION DESCRIPTION:
When bdbreconfig exits with an error code then the tools sessions will no longer stop immediately.

Solution: 131814
SITUATION IDENTIFIED IN:
"Print Log Files" (tu(da)xch0215m000)
SITUATION DESCRIPTION:
From session Print Log File [daxch0215m000] while zooming from field Run number it was not possible for user to chose
Run number because it was part of the view (and appeared only once).
SOLUTION DESCRIPTION:
When zooming from field Run number this field is removed from the view into multi-occurrence part of the form.

Solution: 131819
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000).
SITUATION DESCRIPTION:
When adding a Sales Order Line (linked to a Sales Contract) to a Return Order in session "Sales Orders" (tdsls4100s000)
using button "Select Orig. Lines", the Contract data of the original Line is not copied to the new Line.
The new Line does not get linked to the Sales Contract of the original Line and the wrong Sales Unit (tdsls401.cuqs) and
Sales Price Unit (tdsls401.cups) are used. Both Units are defaulted as defined in Item Sales Data and are not taken from
the Contract of the original Line.
SOLUTION DESCRIPTION:
When returning a Sales Order Line, linked to a Sales Contract, the Contract data will also apply to the new Line.
As a result:
- the new Line will be linked to the Contract of the original Line
- Sales Unit (tdsls401.cuqs) and Sales Price Unit (tdsls401.cups) are taken from the Contract that was linked to the
original Order Line.

Solution: 131828
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
132207, 132334
Descriptions:
- Defect 132207 AFS Error messages not correct returned from functions
- Defect 132334 Report.template variable added for correct crystal report template handling
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 131835
SITUATION IDENTIFIED IN:
"Copy from DD, Table Auths by Company" (ttams3244m001)
SITUATION DESCRIPTION:
Fatal error : Error 205 (Out of range) on ttams344000 in db_insert(51)
This problem happens when form field "New Authorization" is set to blank spaces, and the Continue button is pressed.
SOLUTION DESCRIPTION:
It is no longer possible to set the value for form field "New Authorization" to blank spaces.
New Authorization must be set to one of the predefined options for authorizations.

Solution: 131846
SITUATION IDENTIFIED IN:
"Confirm Shipment" (whinh4275m000)
SITUATION DESCRIPTION:
The Planned Inventory Transactions for a Sales Order Line could be incorrect after confirming a shipment.
This occurred in the situation described bellow.
1. Create a Sales Order Line with an Ordered Quantity = 20
Fill in the Back Order Field with Back Quantity = 5 (the Back Order field could as well be filled in if the Ordered
Quantity cannot be fully committed)
2. Release the Sales Order Line to Warehousing
An Outbound Order Line (for the Warehouse Order generated) is created with an Order Quantity = 15
3. 4 Outbound Advices are created for the Outbound Order Line.
PIT = Planned Inventory Transactions
Expected PIT Qty = Ordered Quantity - Delivered Quantity
= 20 - Delivered Quantity
Actual PIT Qty = PIT Qty observed in the session whinp1501m000 (Planned Inventory Transactions by Order) for the
Sales Order Line
Advice Qty Shipped Qty Expected PIT Qty Actual PIT Qty
(1) 10 9 11 11
(2) 2 2 9 9
(3) 5 5 4 5 ==> ERROR
(4) 1 1 3 5 ==> ERROR
When the Shipped Qty of the Outbound Order Line (whinh220.qshp) exceeds the Ordered Qty of the Outbound Order Line
(whinh220.qstk), the Planned Inventory Transactions are not correctly updated anymore.
When shipping the 3rd. Outbound Advice, the Planned Inventory Transactions for the Sales Order Line are erroneous.
Even if the Sales Order Line is fully delivered, the Back Order Quantity remains in the Planned Inventory Transactions.
SOLUTION DESCRIPTION:
The Planned Inventory Transactions will now be correctly updated after performing a shipment for this kind of situation.

Solution: 131848
SITUATION IDENTIFIED IN:
"Engineering Item Revision" (tiedm1500m000)
SITUATION DESCRIPTION:
When a new revision is released and not copied to Logistics, the system shows empty revision in the General Item data.
SOLUTION DESCRIPTION:
When a new revision is released and not copied to an Item, then system will show the previous revision, which is already
copied in Item data.
Purchase engineering item and manufacturing engineering item without bills of material needs to be copied to Logistics
for new revision to show up in the General Item Data.
Manufacturing engineering item with bills of material, needs engineering bills of material to be copied (i.e.) EBOM
copied flag has to be YES in EBOM Copy Data.
In all other cases, system will show up the old revision (Previous revision).

Solution: 131854
SITUATION IDENTIFIED IN:
"Process Hours Accounting" (tihra1210m00)
SITUATION DESCRIPTION:
A series for a project or a production order can always be blocked for input. This means that, there cannot be anymore new
project or order created using this series. But already created production orders and project are valid. But session
"Process Hours Accounting" (tihra1210m000) does not process hours for already created production orders/project, for
which the series are currently blocked for input.
SOLUTION DESCRIPTION:
It is possible to process hours accounting for an existing order / project even if their corresponding series is now blocked.

Solution: 131859
SITUATION IDENTIFIED IN:
"Role Data" (ttams2201m000)
SITUATION DESCRIPTION:
When deleting a sub-role, that is part of a role, the action "convert changes to runtime" of the role is not reflected in the
file that holds the role information on the Operating System.
For example: two roles RP1 and RC1, where RC1 is a sub-role of RP1.
When RC1 is deleted and "convert changes to runtime (ttams2200m000)" is done, the file $BSE/lib/roles/db/R/RP1 still
shows a relation with RC1.
SOLUTION DESCRIPTION:
Now when deleting the sub-role, the relation with the "parent-role" is checked and modified.

Solution: 131862
SITUATION IDENTIFIED IN:
"Enterprise Unit Categories" ((tgbrg0132m000))
SITUATION DESCRIPTION:
When in the EME a new Enterprise Unit category is defined and linked to an Enterprise Unit, then the category is not
saved as category with the Enterprise Unit.
SOLUTION DESCRIPTION:
Categories are Master Data. When the EME is starting up, then the Master Data is retrieved. So only with the startup of
the EME new Master Data becomes useable. Even when the session, for defining this new data, is started from the EME.
In all other category sessions a warning is given, when a new category is defined. This mechanism is now also working in
the Enterprise Unit Category session.

Solution: 131866
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
Service engineers who carry out service tasks, especially those who repair technical failures, require specific skills.
These skills can be recorded per engineer. The experience of an engineer can be expressed by specifying the object groups
he/she is familiar with.
The service order planning system uses this information when assigning orders to employees or when matching service
orders and employees. When releasing a service order or activity, this information will be checked in order to see whether
the engineer is qualified enough or not.
However, the object group is only used as a constraint when releasing the service order or activity via DSRP.
SOLUTION DESCRIPTION:
The experience of an engineer can be expressed by specifying the object groups he/she is familiar with.
When the configuration and object is specified on the service order activity, the object group will always be taken into
account, when checking whether the service engineer is qualified to carry out service tasks on certain objects.
In case the configuration and object are filled on the activity, the object group will be taken into account always if the object
group for the skill is filled:
a check is done on engineer/object group/skill.
If no object group is defined for the engineer/skill then only a check is done on engineer/skill since object group refines the
skills per engineer.
See the following 3 definition examples:
1. For Engineer X, the Skill Y is defined for all Object groups (Object Group is left empty).
-> Engineer X may work on tasks which requires skill Z-1 and he may work on task which requires skill Z-2
2. For Engineer X, the Skill Y is defined for Object Group Z-1 (Object Group is filled with Z-1) and the Skill Y is also
defined for all Object Groups (Object Group is left empty)
-> Engineer X may work on tasks which requires skill Z-1 and he may work on task which requires skill Z-2
3. For Engineer X, the Skill Y is defined for Object Group Z-1.
-> Engineer X may work on tasks which requires skill Z-1, but he is not allowed to work on tasks which requires skill
Z-2.
Functionally, the definition of skills in situation 2 makes no sense since engineer X has got skill Y for all object groups.
So, there is no need to make a separate definition of skill Y and Object Group Z-1.

Solution: 131873
SITUATION IDENTIFIED IN:
"Sales order lines" (tdsls4101s000)
"Sales order header" (tdsls4100s000)
"Sales order change code history" (tdsls5507m000)
SITUATION DESCRIPTION:
-1- Records in change history, which are displayed in the session 'Sales order change code history' (tdsls5507m000), are
duplicate every time a change is made to the sales order line.
-2- When the sales order header's delivery date is updated by two users, two different orders, both orders with many
lines, the system performance is very slow. This occurs by instance when the combination item/warehouse are the same in
both orders.
SOLUTION DESCRIPTION:
-1- A check has been introduced which will prevent that the change codes related fields are filled in case the sales order
line record is being counterbooked. This is in order to prevent that records are duplicate.
-2- The item selected in the sales order line table will be locked by an application lock. If an application lock is detected
for another user who is attempting to modify the same item, the system will wait for while and continue with the
transaction.

Solution: 131882
SITUATION IDENTIFIED IN:
"Generate Control Data" (tpptc1230m000)
SITUATION DESCRIPTION:
It is not possible to run the control data with "Net Change" option, when there are Elements with status "Free" and Cost
Control set to "yes"
SOLUTION DESCRIPTION:
Now the above-mentioned problem is solved. System allows running the control data with "Net Change" option correctly.

Solution: 131883
SITUATION IDENTIFIED IN:
"Print Currency wise Trial Balance" (tfgld3403m000)
SITUATION DESCRIPTION:
Under Job Process, Rotate Currency does not work. The details in the report are always in the default form currency.
SOLUTION DESCRIPTION:
When Job Process is used, details are printed in the home currency, selected using Rotate Currency.

Solution: 131884
SITUATION IDENTIFIED IN:
"Element Budget (Material Lines)" (tpptc1110s000)
SITUATION DESCRIPTION:
For a Equipment, even if contract exists, while entering a budget line for same, the message shows that price is retrieved
from "Item Purchase Data", but, the price is correctly taken as that maintained in the contract. This confuses the user.
SOLUTION DESCRIPTION:
Now, correct price source will be displayed.

Solution: 131885
SITUATION IDENTIFIED IN:
"Calculate cost and valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
The updating of standard cost price is not correct, if the cost price of manufacturing item is zero.
SOLUTION DESCRIPTION:
The standard cost price will be updated correctly, if the calculated cost price of manufacturing item is zero.

Solution: 131886
SITUATION IDENTIFIED IN:
"Purchase Requisitions Lines History" (tdpur2514m000)
SITUATION DESCRIPTION:
In the session "Purchase Requisitions History" a Requisition record with a particular status is marked and the option to
show the corresponding Lines history is chosen. When the next group button is pressed in the session "Purchase
Requisitions Lines History", the line status is shown incorrectly.
SOLUTION DESCRIPTION:
Though a Requisition header record of particular status is marked before zooming to the lines history session, system shows
the latest status of the Requisition Lines History record.

Solution: 131887
SITUATION IDENTIFIED IN:
"Assign unallocated / advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Error log of 'difference in home currency between debit en credit is very high!!!' is created after finalizing the
unallocated receipt document, which was assigned to sales invoice in case of inter-company transactions.
SOLUTION DESCRIPTION:
No error log is created after finalizing the unallocated receipt document, which was assigned to sales invoice in case of
inter-company transactions.

Solution: 131889
SITUATION IDENTIFIED IN:
Integration to Baan backend.
SITUATION DESCRIPTION:
Integration to Baan backend is not working after installing iPacks and set up the BIS connections.
SOLUTION DESCRIPTION:
When both the IntegrationPack_iBaan_E_Enterprise_Server-BaanIVc_2.5 and
iPack_IntegrationPack_for_BaanIVc4_iBaan_E-Procurement2.2 (or E-Sales or iBTE etc), have been installed the BIS will
be inserted twice in E-Dashboard, see attached example.
BIS Property Name BIS Property Description BIS
componentid componentid OW4
componentid name of the LDAP component OW4
This results in the Baan Integration not working.
The situation can be solved by removing one of the componentid's. Make sure you only remove the componentid for which
no further data was defined.

Solution: 131890
SITUATION IDENTIFIED IN:
"Import Version Dump" (tgbrg1245m000)
SITUATION DESCRIPTION:
During import of a version a question appears, but has no text on it.
SOLUTION DESCRIPTION:
The question should have been part of solution 114568 (5.0b/5.0c)

This solution contains the question in all A-languages.

Solution: 131897
SITUATION IDENTIFIED IN:
"Service Order Activities" (tssoc2110s000)
SITUATION DESCRIPTION:
A Service Order with an activity and a material requirement is created and released. The Goods are shipped out of
Warehouse. When user tries to insert a new activity line, system does not allow stating that the Warehousing Procedures
are in process.
SOLUTION DESCRIPTION:
The user will be able to add a new activity, if the Warehousing Procedure(s) for the existing Service Order Material lines
already is completed.
When an activity is added to an order, the order times itself will change in case parameter 'Planning Method'
(tssoc000.srpm) is defined as 'By Service Order'. With a change of order times, planned inventory transactions and
warehousing orders for Service Order Material Lines will only be updated accordingly if warehousing procedures for the
Service Order Material Line did not start yet.

Solution: 131898
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinhm4725m000)
SITUATION DESCRIPTION:
The case of bilateral or triangular invoicing the surcharge amount isn't calculated and therefore wrong data is written to
the import export table (tccom710)
SOLUTION DESCRIPTION:
Just before the import/export data is written the surcharge amount is retrieved and the surcharge amount is calculated.
The calculated amount is added up to the goods value and the statistical value and written into the import/export table.

Solution: 131903
SITUATION IDENTIFIED IN:
"Bills of Material" (tibom1510m000)
SITUATION DESCRIPTION:
The customer wants component item description in multi occurrence session of "Bills of Material" (tibom1510m000). They
want the script change in standard and customer will go for the form customization.
SOLUTION DESCRIPTION:
Script changes required for displaying the component item description is provided in the session "Bills of Material"
(tibom1510m000) with this solution. Customer will go for form customization.

Solution: 131920
SITUATION IDENTIFIED IN:
"Planned Purchase Orders (Equipment)" (tppss6111s000)
SITUATION DESCRIPTION:
If the "Purchase Office" of a Purchase Order is changed, then if any contract is linked to that Order, it should either
stand void or a new contract if any for that office should be fetched. But, that is not happening currently and the same
contract remains on the order. However, we cannot transfer the order to Order Management. An error message is
returned.
SOLUTION DESCRIPTION:
The above problem is now solved and if the purchase office of purchase order is changed, then either a new contract related
to that office is fetched or a blank is returned.

Solution: 131937
SITUATION IDENTIFIED IN:
"Enter amounts for assignment" (tfcmg2107s000)
SITUATION DESCRIPTION:
The automatic assignment does not consider payment difference tolerances that are defined in the CMG parameters. This
happens only when the invoice amount is less than the received amount and the remaining amount is within the
tolerances.
SOLUTION DESCRIPTION:
When the invoice amount is less than the received amount and the remaining amount is within the tolerances, payment
differences are posted. For example:
Payment difference tolerances (in CMG Parameters): 50 USD less than or greater than the invoice amount
Receipt: 1010 USD
Invoice: 1000 USD (Due: 980 USD, Discount: 20 USD)
After linking:
Amount received in invoice currency: 1010
Discount: 20
Payment Difference: -30
Remaining amount on the Receipt: 0

Solution: 131938
SITUATION IDENTIFIED IN:
"Check/ Change rounding of amounts" (tfcor996s000)
SITUATION DESCRIPTION:
When running the correction program Check/ Change rounding of amounts, a float exception error occured after
installation of solution 131649.
SOLUTION DESCRIPTION:
The float exception error no longer occurs.
Solution: 131940
SITUATION IDENTIFIED IN:
"Print Goods receipt Notes" (whinh3412m000)
SITUATION DESCRIPTION:
When Product Configurator (PCF) is implemented, the field "Print Variant Option Description" is disabled in session
"Print Goods Received Notes" (whinh3412m000).
SOLUTION DESCRIPTION:
Now The Option "Print Variant Option Description" is disabled only when both parameter fields "Configurator
Implemented " and "Product Configurator for MTO " is set to NO.

Solution: 131951
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Tax amount rounded incorrectly when two invoices of different currencies and with different rounding factors are posted
using a single Billing Request. For example, the first invoice is having a currency 'USD' with rounding factor 0.001 and
the second invoice is having a currency 'JPY' with rounding factor 1.
SOLUTION DESCRIPTION:
Now the tax amounts are rounded correctly.

Solution: 131954
SITUATION IDENTIFIED IN:
"Generate control data" (tpptc1230m000)
SITUATION DESCRIPTION:
The error related to the check on progress field for elements appearing more than once in the element structure not
reproduced when control data is run second time.
SOLUTION DESCRIPTION:
Now the check on progress field of the elements which have frequency greater than one or which appear more than once in
the structure would be done every time the control data is run.

Solution: 131955
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100)
SITUATION DESCRIPTION:
A Sales Order (session tdsls4100s000) has three lines. The lines are released to Warehousing and
Outbound Advices are generated for all of them. Now the following procedure is followed:
- Cancel Sales Order Header by using the button on the form in session "Sales Orders" (tdsls4100s000)
- System gives error "Order line 1, sequence 0 cannot be modified. It has been released or is linked to a receipt"
- Before clicking OK, the Outbound Advice for the first Sales Order Line is deleted.
- Now the user presses OK for the error.
- The same error is given for the second Sales Order Line. The user follows the same procedure as above.
The result is that the Sales Order Header and the second Sales Order Line are cancelled, which is incorrect.
SOLUTION DESCRIPTION:
When following the procedure as described in the situation description, the cancel process is now stopped after the first
error-message is given. After the user clicks 'OK', session "Sales Orders" is refreshed and the user needs to use the button
again when he wants to re-try to cancel the order.

Solution: 131956
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0501m000)
SITUATION DESCRIPTION:
The value of the parameter Engineering Revisions Lot Control (whltc000.erac) isn't considered ins session Production
Orders. In case the value of this parameter is set to No the mentioned function shouldn't be carried out.
SOLUTION DESCRIPTION:
A section is added to the function whltc.dll0005.check.revisions.ok() the retrieves the parameter whltc000.erac from the
table Lot Control Parameters.
With this parameter a check is created that determines if the function should be carried out or not.

Solution: 131957
SITUATION IDENTIFIED IN:
"Print Where Used Functions" (ttadv2465m000)
SITUATION DESCRIPTION:
When session "Print Where Used Functions" (ttadv2465m000) is run on a multibyte system an error can occur:
When the report is created for the Japanese language, it works fine.
When the report is created for the English language a message comes up:
"Error in reading sort file record: 37 fields scanned 39 expected"
SOLUTION DESCRIPTION:
The report was compiled with an old portingset. Recompiled and delivered the report.

Solution: 131958
SITUATION IDENTIFIED IN:
"Assign Unallocated / Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Postings for "Assignment of Unallocated Receipt to Advance receipts" are wrong.
SOLUTION DESCRIPTION:
Postings for "Assignment of Unallocated Receipt to Advance receipts" are correct.

Solution: 131960
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When the document-date is used as rate-determiner also the equivalent rate should be used and not the rate of the filled
'order'.
SOLUTION DESCRIPTION:
Because now the document date is the transaction date and not the document date of the order the rate of the transaction
date will be taken in account when the rate-determiner is on document date.

Solution: 131962
SITUATION IDENTIFIED IN:
"Split Shipment" (whinh4231m000)
SITUATION DESCRIPTION:
When a user tries to split a shipment the error message "Quantity per shipment must be a multiple of ####" can appear.
This is due to rounding problems.
SOLUTION DESCRIPTION:
Before the software tries to split a shipment some amounts, needed for calculation, are rounded so no rounding problem
occurs.

Solution: 131967
SITUATION IDENTIFIED IN:
"Planned PRP Purchase Orders (Material)" (tppss6110s000)
SITUATION DESCRIPTION:
If a contract is linked to a purchase order and for some reason if we remove the contract and try saving the record, a
message pops indicating that the price is retrieved from contracts.
SOLUTION DESCRIPTION:
Now, if a contract is manually removed, no message will come. It will be assumed that the user has given is own price
and not from any predefined prices.

Solution: 131973
SITUATION IDENTIFIED IN:
"Reconfig table definitions" (ttaad5210m000)
SITUATION DESCRIPTION:
The reconfig is always done using the rows before indexes. This can cause error messages when the tempory table space is
to small.
SOLUTION DESCRIPTION:
The option rows before indexes is made optional. Both for session "Create Runtime Data Dictionary" (ttadv5210m000)
and "Convert to Runtime Data Dictionary" (ttadv5215m000)

Solution: 131982
SITUATION IDENTIFIED IN:
"Planned Orders" (cprrp1100s000)
SITUATION DESCRIPTION:
When Planned Purchase Order is realized into actual Purchase Order, and if carrier is mentioned in the order details, it is
not defaulted on to the Purchase Order Header.
SOLUTION DESCRIPTION:
The Carrier mentioned in the Order details is defaulted properly on to the Purchase Order Header.

Solution: 131988
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
When creating a Purchase Requisition line it is not possible to fill Plan, Element, Activity and Cost Component details on
the Projects tab. System does not allow saving the line without these details, and pops up an error "Planning and activity
code must be filled for cost control".
SOLUTION DESCRIPTION:
The Plan, Element, Activity and Cost Component details are enabled, when a project item is filled in Requisition line.

Solution: 131993
SITUATION IDENTIFIED IN:
EDI
SITUATION DESCRIPTION:
In the following situation, a fatal error 606 on table whinh301("ASN Lines") occurred when reading ASNs:
1. The batch/file contains 2 ASNs.
2. The first ASN has specific address information; the second ASN does not have specific address information.
3. The conversion setup does not have the field whin300.cwar (Warehouse) and whinh300.dadd (Delivery Address)
included on header level.
The fatal error occurred for the second ASN; the first one was properly inserted.
SOLUTION DESCRIPTION:
The error occurred because a variable was not initialized. This has been corrected in the program script. When a batch is received like
described above, the first ASN will be properly inserted and the second one will error out, showing the following error on the "Errors in Received
Messages" report: "Either warehouse or delivery or both must be filled". So if the warehouse code is not included in the conversion setup, the
delivery address code (whinh300.dadd) needs to be filled by reading the address code from the file (so whinh300.dadd included in the setup) or
the delivery address code needs to be filled via the specific address code information. If both (code and specific information) are in the incoming
file, the newly generated address code from the specific address information will overrule the code read from the file via whinh300.dadd.

Solution: 131996
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
127102, 128293, 132082, 132540, 132680, 212222
Descriptions:
- Defect 127102 AFS synchronize cont.process in api mode
- Defect 132540 AFS Field descriptions in generated dll made case insensitive
- Defect 132680 When.field.changed not executed in pagemode
- Defect 212222 AFS Hanging OW because of exit.child
- Defect 128293 The error "Date/Currency %D002,JPY is not available" happens on MB-system.
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 131997
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
When running 'Select invoices for payment' (tfcmg1220m000) in a job, the 'to' field of 'total amount by BP' is reset to
99999999.99 (default) when the job is activated via session 'Activate Job' (ttaad5203s000).
SOLUTION DESCRIPTION:
The 'to' field of 'total amount by BP' is defaulted correctly when activating the job for 'Select invoices for payment'.

Solution: 131998
SITUATION IDENTIFIED IN:
"Enter amounts for assignment" (tfcmg2107s000)
SITUATION DESCRIPTION:
While using 'Blank' write-off status for processing assignments, balance amount on the invoice is going wrong.
SOLUTION DESCRIPTION:
Now, 'Blank' Status works as 'No' as far as default amounts are concerned. The record cannot be saved with 'Blank'
write-off status. The balances are updated properly when one of the valid statuses 'No', 'Automatic' or 'Manual' is selected

Solution: 131999
SITUATION IDENTIFIED IN:
"Generate Invoice by Self billing" (tfacp2290m000)
SITUATION DESCRIPTION:
Incase the compress option is used while generating self billed invoices and one of the receipts which is being processed
encounters a problem when non-finalized transactions are being created ( like ledger account cannot be determined) then ,
the self billing process does not show an error log, and also link between the invoice and receipts are created and the
totally matched flag for the order line/ receipt is set to "Yes". This could create a problem during GRNI reconciliation.
SOLUTION DESCRIPTION:
Now, when there is an error encountered in the situation mentioned above, all the previous transactions are reverted, and
also an error report is printed.

Solution: 132002
SITUATION IDENTIFIED IN:
"Default Order Types by Origin" (whinh0520m000)
SITUATION DESCRIPTION:
When we use a number group, the flag "In Use" is changes to yes. If the record is deleted, without creating any transactions,

and try to use that number group, it is still flagged as "In use".
SOLUTION DESCRIPTION:
Now the Flag "In Use" is set to " No", once the record is deleted from the session " Default Order Types by Origin".

Solution: 132003
SITUATION IDENTIFIED IN:
"Variables by Algorithm" (qmptc0122m000)
SITUATION DESCRIPTION:
While entering the variables for an algorithm, system allows to enter the variables whose characteristic is of type 'option'.
SOLUTION DESCRIPTION:
System will allow entering the variable whose characteristic is of type 'fraction' or 'integer'.

Solution: 132009
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Bad performance when confirming a receipt for a lot by unit item.
SOLUTION DESCRIPTION:
The session is adapted to confirm faster.

Solution: 132013
SITUATION IDENTIFIED IN:
"Solution for mb help" (ttstphelp)
SITUATION DESCRIPTION:
Multibyte helptext got truncated at 160 characters
SOLUTION DESCRIPTION:
Now it will not be truncated

Solution: 132019
SITUATION IDENTIFIED IN:
"Archive Engineering Item Data" (tiedm1250m000)
SITUATION DESCRIPTION:
System is giving fatal Error 606 (reference does not exit), while archiving engineering item data when engineering item
revisions are linked to the ECO.
SOLUTION DESCRIPTION:
ECO number will not be archived. System will not give the fatal Error 606 (reference does not exit), while archiving
engineering item revisions.

Solution: 132023
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Two problems are reported:
1. Balance on the invoice is updated as 0 instead of 0.0000. It's a rounding problem. The balance amount is
0.000000000001, so it is updated as 0. If it is 0.000000000000000, it will be updated as 0.0000.
2. Unnecessary debit amount appeared in non-finalized report.
SOLUTION DESCRIPTION:
1. Balance of the invoice is properly updated as 0.0000 instead of 0. And is also shown in 'Fully Paid Invoices' list
2. Entries are properly posted.

Solution: 132030
SITUATION IDENTIFIED IN:
"Maintain and Confirm Back Orders" (tdsls4125m000).
SITUATION DESCRIPTION:
When running "Maintain and Confirm Back Orders" (tdsls4125m000) in Dutch, the description of browse column
"Backorder Type" is in German.
SOLUTION DESCRIPTION:
Right translations for description of "Backorder Type" in "Maintain and Confirm Back Orders" (tdsls4125m000) are
provided by this solution.

Solution: 132032
SITUATION IDENTIFIED IN:
"Warehouse Orders" (whinh2100s000)
SITUATION DESCRIPTION:
A warehousing order of type "Sales (Manual)" is inserted via "Warehousing Order" (whinh2100s000). A normal warehouse
is entered in the field "Ship-from Code". Even after entering a valid warehouse code, the error message "Warehouse not
allowed because of warehouse type or relation" is displayed. Due to this, the order cannot be maintained.
SOLUTION DESCRIPTION:
Sales manual order can be saved if valid warehouse is entered in the session. Irrelevant error messages do not pop up

Solution: 132036
SITUATION IDENTIFIED IN:
"Release to Invoicing (batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
When releasing a Sales Order to Central Invoicing a message pops up "Installment closed: correction installment must be
invoiced before goods can be released to invoicing".
Steps to take:
1. Enter a Sales Order with "Invoicing by Installment" (tdsls400.futo) = "Indirect Settlement".
2. Enter a least one Order line and an Installment schedule.
3. Define two Installment Lines (line 1 "normal" installment, line 2 "guarantee" installment).
4. Release first Installment Line to Invoicing and create an Invoice for the Installment.
5. Release Sales Order to Warehousing and deliver all goods.
6. Close all Installment lines.
7. Release Sales Order to Central Invoicing. Error: "Installment closed: correction installment must be invoiced before
goods can be released to invoicing".
SOLUTION DESCRIPTION:
From now on it is possible for a given Sales Order, to be released to Central Invoicing, having all goods delivered and the
Installment Schedule being closed, as described in the situation above.

Solution: 132046
SITUATION IDENTIFIED IN:
"Report dll" (ttstprepdll)
SITUATION DESCRIPTION:
Text containing tabs is not correctly printed. On a multibyte envirioment.
SOLUTION DESCRIPTION:
The conversion of tabs to spaces was done wrongly for multibyte. This is now corrected.

Solution: 132059
SITUATION IDENTIFIED IN:
"Production Planning" (tisfc1101s000)
SITUATION DESCRIPTION:
1. The allocation date of materials is updated wrongly, when planning is shifted either forward or backward for a
production order.
2. When sending the new production planning dates from SCS Scheduler to Baan, the dates on production orders are not
updated.
SOLUTION DESCRIPTION:
1. When shifting the operations of a production order either forward or backward, the allocation date of the materials
linked to the corresponding operations also gets updated accordingly.
2. When sending the new production planning dates from SCS Scheduler to Baan, the dates on production orders will be
updated based on the new dates on the production planning.

Solution: 132060
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
Message "When following the outbound procedure for this advice, negative inventory can result." (whinhs0602) is not
displayed when negative inventory is created when storage unit is the same as inventory unit when inserting Outbound
Advice.
SOLUTION DESCRIPTION:
When item does not have package definition then message "When following the outbound procedure for this advice, negative
inventory can result" will be displayed if we change the unit to a unit in which we do not have quantity available
Exception: when we change the unit to inventory unit then no message will be displayed if enough inventory enough
exists, else message will be displayed too.

Solution: 132062
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
"Select Invoices for Payment (Not selected)" (tfcmg1222s000)
"Payment Advices" (tfcmg1120m000)
"Select Invoices for Direct Debit" (tfcmg4220m000)
SITUATION DESCRIPTION:
Debit purchase invoices that are corrected into credit purchase invoices cannot be selected for payment. Due to this they
cannot be settled.
SOLUTION DESCRIPTION:
Debit purchase invoices corrected to credit purchase invoices can be selected for payment and overpaid invoices with a
negative balance can be selected too.

Solution: 132063
SITUATION IDENTIFIED IN:
"Print Receipts" (tdpur4431m000)
SITUATION DESCRIPTION:
'Print Receipts' report not correct for partial receipts of lines with header discount. The values of 'Order Discount' and
'Amount' are wrongly calculated for the first sequence of a partial receipt.
SOLUTION DESCRIPTION:
The Order Discount is displayed only for the delivered quantity now. The amount also shows the correct value.

Solution: 132069
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1) The "Total Discount Amount" in the Purchasing tab of the Purchase-Order Lines (tdpur4101s000) session is displayed
incorrectly when user switches to this Purchasing tab second time. This happens when partial receipts are done for the
purchase order line.
2) A purchase order line is created and saved. Without leaving the session, a new purchase order line is added (using the
button on tdpur4501m000 or Ctrl-N). When tabbing through the fields, the item defaults with the same item as the former
added line (correct) the order quantity is zero (correct). The following is incorrect: the discount percentage and discount
code is taken from the first line.
SOLUTION DESCRIPTION:
1) The 'Total Discount Amount' is displayed correctly even when the user switches to the Purchasing tab from any other
tab any number of times.
2) The discount found, if any, during the search for the price and discounts will be defaulted instead of getting the
discount from the previous purchase order line if a new purchase order line is added with out closing the session.

Solution: 132073
SITUATION IDENTIFIED IN:
"Release to invoicing (batch)" (tdsls4247m000)
"Release to invoicing" (tdsls4501m130)
SITUATION DESCRIPTION:
The session takes too long when releasing an order to invoicing which has an item by lot by unit, in case the ordered
quantity is a huge number e.g. 99
SOLUTION DESCRIPTION:
A check has been built in the program script so a determined function is not called in case the inventory and the sales unit
are the same. This will improve the performance since this function doesn't need to be performed for all sales order lines.

Solution: 132078
SITUATION IDENTIFIED IN:
"Print Work-In-Process " (ticst0450m000)
SITUATION DESCRIPTION:
In the session "Print Work-In-Process" (ticst0450m000), when the "Report Type" is "By Ledger Account", the user can select
records for a range of "Ledger Accounts" only. It is not possible to select the records for a range of production orders,
projects and work center. This makes the output report far too long.
SOLUTION DESCRIPTION:
Users can select the records for a range of production orders, projects and work center, when the "Report Type" is "By
Ledger Account" in the session "Print Work-In-Process" (ticst0450m000).

Solution: 132084
SITUATION IDENTIFIED IN:
"Receipt Lines" (whinh3120s000)
SITUATION DESCRIPTION:
In session whinh3120s000 "Receipt Lines", when having a lot item controlled by unit, if Split Lots by Unit is done and for
that first line Generate Lot Codes is also done, message "Record already exists" arises when saving it.
SOLUTION DESCRIPTION:
Problem has been corrected: no mismatch between receipt lines exists any longer, then message does not arise.

Solution: 132088
SITUATION IDENTIFIED IN:
"Print Registered and Matched Purchase Invoices" (tfacp1433m000)
SITUATION DESCRIPTION:
1. When an Invoice is registered and matched, but not approved, this report does not show this invoice in the list.
2. When there are multiple approvals and un approvals in a period then this report prints based on the first approval or
un approval of that period.
SOLUTION DESCRIPTION:
The situation mentioned above has been solved.

Solution: 132091
SITUATION IDENTIFIED IN:
"Maintain Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Text of original document changes to that of the copied document.
SOLUTION DESCRIPTION:
Text of original document won't get changed to that of the copied document.

Solution: 132092
SITUATION IDENTIFIED IN:
"Quality combinations" (qmptc0111s000)
SITUATION DESCRIPTION:
System allows maintaining a quality combination for the customized item, even though the project is completed.
SOLUTION DESCRIPTION:
System will allow maintaining a quality combination for the customized item, only when the project status is free,
simulated or active.

Solution: 132094
SITUATION IDENTIFIED IN:
"Service Hours Accounting" (tssoc2136s000)
SITUATION DESCRIPTION:
When the spent time of a service hours accounting line is updated using session Service Hours Accounting (tssoc2136s000),
the associated actual labor cost line shows wrong cost rate and surcharge rate. This happens only when there is a surcharge
associated with the hourly labor type.
SOLUTION DESCRIPTION:
The cost rate and surcharge rate are displayed correctly on a service order actual labor cost line when the spent hours on a
service hours accounting line is updated.

Solution: 132107
SITUATION IDENTIFIED IN:
"Object Masks" (dmcom0122s000)
SITUATION DESCRIPTION:
When the default value for the object mask is only of the fixed character without the generated character, system gives the
fatal error index out of dims.
SOLUTION DESCRIPTION:
The default value for the object mask must contain both fixed characters and generated characters. For generated characters,
use the number symbol (#) to represent a digit and an asterisk (*) to represent a letter. This check will be done while
entering the value for default field.

Solution: 132120
SITUATION IDENTIFIED IN:
"Global Update of Prices via Price Matrices" (tdpcg0230m300)
SITUATION DESCRIPTION:
-1- The Report shows prices that are already expired also updates with changed price.
-2- The currency changes back to home currency when using 'Update price by value'.
SOLUTION DESCRIPTION:
-1- When the expiry dates are mentioned in the selected range, then those particular records which are falling in the range
will be considered first. If the expiry date is not mentioned, then the records that are not having the expiry dates only will
be considered.
-2- Currency will not change back to home currency even when using 'Update price by value'.

Solution: 132122
SITUATION IDENTIFIED IN:
"SFC Parameters" (tisfc0100s000)
SITUATION DESCRIPTION:
When creating a new company the Sfc costing parameter 'Transfer Wip Method' is put in a combination that is not
allowed (Not Implemented).
SOLUTION DESCRIPTION:
When creating a new company the default parameters are set via the session Initialize Parameters (tcmcs0295m000) the
Costing parameter 'Transfer Wip Method' is set to 'Always'. In addition, when this invalid combination is used the
system will give an error and will not allow to close the parameter session. When using Costing Results per Workcenter
the 'Transfer Wip Method' should be 'Always' or 'Only Upon Completion'.

Solution: 132130
SITUATION IDENTIFIED IN:
"Copy Range of Lots" (whltc1201m000)
SITUATION DESCRIPTION:
When we copy a lot from a lot Item which has a shelf life, while calculating the lot date of the "To Lot" shelf life of the
Item is not added up. When we create a new lot with out copying, shelf life is considered and the lot date is a future date
including the shelf life.
SOLUTION DESCRIPTION:
The shelf life is added to determine the "Lot date " while copying from the existing lots to new lots.

Solution: 132131
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices " (ticpr2210m000)
SITUATION DESCRIPTION:
Performance problem in the session "Calculate Cost and Valuation Prices" (ticpr2210m000) when calculating the cost price
of a single item, if the item group range is wide open.
SOLUTION DESCRIPTION:
Performance improvement while calculating cost prices of the Item, when the Item Group is wide open (without filling up
the range).

Solution: 132134
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Payments to Invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
When assigning an unallocated payment to another Unallocated / Advance payment, the assignment can never be reversed
in the unfinalized batch. The assignment is done through the session "Assign unallocated /advance payments to invoices
(tfcmg2131s000)".
SOLUTION DESCRIPTION:
Now the assignment can be reversed.

Solution: 132139
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1) Consider that order discount is present for a Cost Item. Enter the cost item in the purchase order lines and save. The
order balance is updated by applying the discount while the open balance is updated without applying the order discount.
2) The 'Credit Limit' and 'Linked order line data' Labels are not displayed correctly.
SOLUTION DESCRIPTION:
The Order Balance will be correctly calculated excluding the order discount if the item on the purchase order line is a
Cost or Service Item.
The Labels for 'Credit Limit' and the 'Specific option' namely 'Linked order line data' are displayed correctly.

Solution: 132140
SITUATION IDENTIFIED IN:
"Material to Issue for production orders" (ticst0101s000)
SITUATION DESCRIPTION:
When we return a LOT BY UNIT Item to the shop floor in quantities greater than one, from the session ticst0101s000
(Material to Issue Production Orders) with the Flag " Direct Process Outbound set to "Yes. Fatal Error 100 (Duplicate
value) occurs.
SOLUTION DESCRIPTION:
Now the Sequence number is incremented properly and the Fatal error doesn't occur doesn't occur even when the
quantity returned is more than one for a LOT BY UNIT item

Solution: 132141
SITUATION IDENTIFIED IN:
"User Data" (ttams1100s000)
SITUATION DESCRIPTION:
A normal user without a role assigned to it, has no permissions to work with the software. He is not able to logon.
However an application manager can create and save a normal user without a role attached to it. No warning or error
message is shown.
SOLUTION DESCRIPTION:
When an application manager tries to save a normal user without a role, a message is shown. The save does not succeed.

Solution: 132159
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Fatal error tfcmg103.refr index 106 out of dim [1] 200' occurs while printing the report 'ABN AMRO BTL91 Format'
SOLUTION DESCRIPTION:
Report 'ABN AMRO BTL91 Format' is printed properly without fatal errors.

Solution: 132160
SITUATION IDENTIFIED IN:
"Select for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
While reconciling multiple anticipated documents a fatal error occurs and the process is stopped.
SOLUTION DESCRIPTION:
Automatic Reconciliation is now possible for multiple anticipated documents without any fatal errors.

Solution: 132171
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Warehouse and Item" (whina1210m000)
SITUATION DESCRIPTION:
The performance is too slow.
SOLUTION DESCRIPTION:
Performance has been improved. It is advisable not to use the progress indicator.

Solution: 132175
SITUATION IDENTIFIED IN:
"Activity Progress" (tpppc1560m000)
SITUATION DESCRIPTION:
Fatal error while opening session 'activity progress' when qty. on activity is 0.
SOLUTION DESCRIPTION:
Now when the quantity of the charge element is 0 then the progress % also becomes 0.

Solution: 132177
SITUATION IDENTIFIED IN:
"Planned Activities" (tsspc2100s000)
SITUATION DESCRIPTION:
When manually inserting a Planned Activity the Service Center is defaulted from the Reference Activity however when
generating Planned Activities by using session "Generate Maintenance Planning" (tsspc200) the Service Center is
defaulted from the Configuration.
SOLUTION DESCRIPTION:
When a Planned Activity is manually created, the Service Center is defaulted from the Configuration instead of from the
Reference Activity.

Solution: 132183
SITUATION IDENTIFIED IN:
"Calculate Demand Forecast by Item" (whina2202m000)
SITUATION DESCRIPTION:
When the session calculates safety stock and if this value is negative, Fatal Error 205 occurs (Out of Range).
SOLUTION DESCRIPTION:
The Fatal Error 205 (Out of Range) no more occurs.

Solution: 132184
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b
132312, 211441, 212025
Descriptions:
- Defect 132312 Grid error while switching forms
- Defect 211441 AFS spool.report not set in api mode stpapi.set.report fails
- Defect 212025 AFS incorrect domain check
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 132192
SITUATION IDENTIFIED IN:
"Fill "Reference to Finalized Transaction" table" (tfcor1826m000)
SITUATION DESCRIPTION:
The following error occurred when running the session Fill "Reference to finalized Transaction" table.
Fatal error: Error 2555 (bdb_errno 2555) on Select
Fatal error: Cannot continue in tfcor1826m000 ()
Error: tfcor1826m000: A not terminated transaction is aborted.
SOLUTION DESCRIPTION:
The user input in the form has been changed now. Please use a smaller range in the user input field, when this error
repeats.

Solution: 132198
SITUATION IDENTIFIED IN:
"Hours accounting transactions" (tphrs1100s000)
SITUATION DESCRIPTION:
Extension not defaulted when an element is filled.
SOLUTION DESCRIPTION:
Now the extension is defaulted by element by system automatically.

Solution: 132206
SITUATION IDENTIFIED IN:
"Change Prices and Discounts after Delivery" (tdsls4122m000)
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
1. If multiple discounts are used using discount codes for each level, the line discount code cannot be changed in
session 'Change Prices and Discounts after Delivery' (tdsls4122m000). (only B50c)
2. If a sales order line is blocked for release to invoicing, the backorder for this line is visible in session "Order (Line)
Blocking" (tdsls4520m000) but the field 'blocked' in session "Sales Order Lines" (tdsls4101s000) is not checked. This means
that this line can be released to invoicing, which is incorrect.
3. When a sales order line has detail lines, it is impossible to enter a project, the message "Calculation office not found
for the project" is shown.
4. In some cases it is not possible to fill the hold back quantity in session "Sales Order Lines" (tdsls4101s000). The
error message: "not able to increase order quantity due to commitment and backorders" appears. (only B50b)
SOLUTION DESCRIPTION:
1. The line discount code can be changed in session 'Change Prices and Discounts after Delivery' (tdsls4122m000).
2. The backorder for a blocked line is also blocked. This means that the backorder is visible in session "Order (Line)
Blocking" (tdsls4520m000) and the field 'blocked' in session "Sales Order Lines" (tdsls4101s000) is checked.
3. When a sales order line has detail lines, it is impossible to enter a project until one of the detail lines is advised.
4. It is possible to fill the hold back quantity in session "Sales Order Lines" (tdsls4101s000).

Solution: 132215
SITUATION IDENTIFIED IN:
" Payments by Purchase Invoice" (tfacp2523m000)
SITUATION DESCRIPTION:
When creating payments in the group company for a Business Partner, paying invoices from two different companies,
the check number of the payment for invoices from the group company does not show up in session " Payments by
Purchase Invoice - tfacp2523m000"
SOLUTION DESCRIPTION:
Because of searching for the check number in the group company the check number will be displayed in session "
Payments by Purchase Invoice - tfacp2523m000".

Solution: 132226
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
When a cost item or a project item is added to a Purchase Order that is linked to a Direct Delivery Sales Order, system
doesn't allow the user to process it further. The cost line is not linked to the sales order. Due to that, lot of unprocessed
purchase orders will remain in the system.
SOLUTION DESCRIPTION:
It is now possible to process the non linked sales order line and can also be matched and invoiced.
Solution: 132232
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
Error index out of dims 250[251], during cost price calculation and inventory revaluation for an item. The item has
multiple cost price components defined and the item is present in large number of warehouses.
SOLUTION DESCRIPTION:
Inventory revaluation is done without any errors, If multiple cost price components are defined for an item present in
large number of Warehouses.

Solution: 132240
SITUATION DESCRIPTION:
Financial transactions of type "Issue" and transaction origin "Service" do not populate the "Additions to Integration
Transactions"(tfgld415) table with Item and Item Group. Hence, it is not possible to make use of Item Group for
integration account steering.
For versions B50_b and B50_c, activity data is populated in the table even though an activity is not linked to the material
line.
SOLUTION DESCRIPTION:
For transaction origins "Service" and "Sales Invoicing (Service)", all item related financial postings will have the Item
and Item Group filled in the "Additions to Integration Transactions"(tfgld415) table. So, it is possible to make use of
Item Group for integration account steering and dimension steering.
For versions B50_b and B50_c, activity data is not populated in the table when an activity is not linked to the material
line.

Solution: 132241
SITUATION IDENTIFIED IN:
"tssoc0100s000" (Service Order Control Parameters)
SITUATION DESCRIPTION:
When a Service Order has a Project linked to it, then its associated travel costs with a cost component of the type
"Operation" is not possible.
SOLUTION DESCRIPTION:
For a Service Order with a Project linked to it, travel costs of the type "Operation" is also allowed in addition to costs of
type "General". So if in the parameters, the cost component of the type "Operation" is entered for travel costs, the release
of a Service Order with Project linked is not blocked.

Solution: 132247
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Payment difference amount in home currency appears as difference on the Control Account checklist even when the
received amount to the total invoice amount is within the payment difference tolerance.
SOLUTION DESCRIPTION:
Payment difference in home currency is posted correctly. No difference is appearing anymore on the control account
checklist.

Solution: 132249
SITUATION IDENTIFIED IN:
"Estimated materials" (ticst0110s000)
SITUATION DESCRIPTION:
The value of the field 'Committed Inventory' in the session "Inventory by Warehouse and Item" (whwmd2515m000) goes
wrong if warehouse is changed in the session "Estimated materials" (tisfc0110s000) for a production order for which
inventory commitment has been generated.
Steps:
1. Created two new warehouses WH1 and WH2.
2. Item I1 is raw material for a main item M1 as declared in BOM.
3. Created 10 pcs of inventory for item I1 in each warehouse.
4. Created production order for main item M1 for 4 pcs in warehouse WH1.
5. Generated inventory commitment for the production order.
6. 'Committed Inventory' in the session "Inventory by Warehouse and Item" is 4 pcs for warehouse WH1 and item I1.
7. In the session "Estimated materials", changed warehouse code to WH2 and saved.
8. Checked the session "Inventory by Warehouse and Item".
Committed inventory is -4 pcs for the combination WH2-I1 and 4 pcs for the combination WH1-I1.
Expected result: 'Committed Inventory' should be 0 pcs for both the combinations.
SOLUTION DESCRIPTION:
'Committed Inventory' is updated correctly in the session "Inventory by Warehouse and Item", if any data is modified in
the session "Estimated materials".

Solution: 132256
SITUATION IDENTIFIED IN:
"Receipt Correction" (whinh3121s000)
SITUATION DESCRIPTION:
While doing a Receipt Correction of changing the Final Receipt flag from 'No' to 'Yes', for a Purchase Order or
Purchase Schedule Receipt, the message "Location Should be filled" is popped when "Processing" the Receipt Correction.
This happens only for items with no inventory in the warehouse.
SOLUTION DESCRIPTION:
Changing of Final Receipt is possible for Purchase Order / Purchase Schedule Receipt, even when there is no inventory
for that Item in the Warehouse.

Solution: 132259
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
If the tax amount is corrected through session "tfacp2110s000 - Maintain Purchase Invoice Corrections", the accounting
entries go wrong and the batch becomes unbalanced.
SOLUTION DESCRIPTION:
The accounting entries are done correct now. The batch is balanced after correction now.

Solution: 132260
SITUATION IDENTIFIED IN:
"Print Tax Details for unpaid/Partially paid Invoices" (tfacp2423m000)
SITUATION DESCRIPTION:
This is a new requirement, which is to be added according to VAT Changes in UK - this became a new law on 24th July
2002
Clause 22 of the Finance Act 2002 states that if a company does not pay a supplier's invoice within 6 months of the date of
supply or the due date for payment, which ever is the later,
then input tax claimed for that supply must be repaid.
The input tax is repaid by making an adjustment to the input tax that the business claims on the VAT return for the
accounting period in which the end of the six months falls.
SOLUTION DESCRIPTION:
Now, the invoices which are having tax and overdue(unpaid/partially paid) are printed.

Solution: 132261
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
While posting service contract sales invoice, series cannot be used as an integration element.
SOLUTION DESCRIPTION:
Series can be used as an integration element for service contract sales invoice. The dimensions will be correctly retrieved.

Solution: 132262
SITUATION IDENTIFIED IN:
"Column Content by Layout Code" (tdpst0197s000)
SITUATION DESCRIPTION:
User is unable to save a record with field "Subprompt 2" empty in session "Column Content by Layout Code
(tdpst0197s000)". System gives an error message saying "Input string too short, minimum of 1 character" and doesn't allow
the user to save the record. This is not the case in sales side. Here, user will be able to save the record even with the
field "Subprompt 2" empty.
SOLUTION DESCRIPTION:
User will be able to save the column content for a layout code even with empty "Subprompt 2" field.

Solution: 132264
SITUATION IDENTIFIED IN:
"Print Reminder Letters" (tfacr3420m000)
SITUATION DESCRIPTION:
Calculation of interest amount is done for all the overdue documents (Advance/Unallocated) including Sales Invoice or
Sales Credit Notes.
SOLUTION DESCRIPTION:
Calculation of interest amount is avoided for all the overdue documents (Advance/Unallocated) other than Sales Invoice
or Sales Credit Notes.

Solution: 132271
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
Processing of inventory variances for items with valuation method "lot price" can result in wrong financial postings.
When processing inventory variances, these variances are assigned to inventory based on the wrong assumption that the
oldest lot is consumed first.
Example:
Item A; valuation method "lot price"
1. Purchase and receive 10 item A on 01-01; Lot "LOT01"; Price 10
Purchase and receive 10 item A on 02-01; Lot "LOT02"; Price 20
2. Sell and ship 10 item A on 04-01; lot "LOT02"
3. Now the purchase price for lot LOT02 is adjusted and an inventory variance is created.
When processing this variance, lot LOT02 is assumed to be still on hand because lot LOT01 is assumed being consumed.
Hence wrong integration transactions are created.
SOLUTION DESCRIPTION:
Now the lot inventory is taken into account. Processing of the inventory variances is done based on the right quantities and
correct financial postings are created.

Solution: 132280
SITUATION IDENTIFIED IN:
"Production Planning" (tisfc1101s000)
SITUATION DESCRIPTION:
When operation other than the first operation is rescheduled, system indirectly reschedules first operation also. At this
point the allocation date of materials linked to the first operation goes wrong.
SOLUTION DESCRIPTION:
The allocation date of materials is updated rightly when operations are shifted either forward or backward via the
production planning session.

Solution: 132290
SITUATION IDENTIFIED IN:
"Items - Service" (tsmdm2100m000)
SITUATION DESCRIPTION:
In session 'Items - Service" (tsmdm2100m000) the option 'Delete Range' is disabled.
SOLUTION DESCRIPTION:
In session 'Items - Service" (tsmdm2100m000) the option 'Delete Range' is enabled.

Solution: 132292
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Receipts cannot be booked for a Business partner when the Invoice-to role is Inactive.
SOLUTION DESCRIPTION:
Receipts can be booked for a Business partner when the Invoice-to role is Inactive.

Solution: 132293
SITUATION IDENTIFIED IN:
1. "Cycle-Counting/Adjustment Order Lines" (whinh5500m000)
2. "Receipts" (whinh3520m000)
3. "Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Issue 1:
When an issue is processed for a FTP valuation method the revaluation is booked with the wrong sign on the stock
account.
Issue 2:
The surcharge for a receipt record in Intrastat was calculated twice in case of a transfer order.
Issue 3:
Performance problem when doing "Confirm Shipment". The process takes a huge amount of time.
SOLUTION DESCRIPTION:
Issue 1:
For issues the sign of the new revaluation has been modified to correct (adding or subtracting) the first one.
Issue 2:
A check is created that controls the surcharge calculation and prevents the session from calculating twice.
Issue 3:
The process is optimized and it terminates within an acceptable time frame.

Solution: 132294
SITUATION IDENTIFIED IN:
"Initialise, Roll and Update Scenario's" (cprpd4200m000)
SITUATION DESCRIPTION:
Demand Forecast becomes negative when rolling a scenario and "Round=Yes" in EP Parameters.
Aggregation data is removed after rolling a scenario with day-periods. After a second update, the aggregation data is
rebuild.
SOLUTION DESCRIPTION:
Demand Forecast is distributed in such a way that it cannot become negative when rolling a scenario and "Round=Yes" in
EP Parameters.
Aggregationdata is not removed when rolling a scenario with day-periods

Solution: 132302
SITUATION IDENTIFIED IN:
"Calendar Lines" (tcccp0120m000)
SITUATION DESCRIPTION:
When copying a Calendar line which is derived from a template or Calendar, the new record is also derived from that
template or Calendar and therefore not all fields in the new record can be modified
SOLUTION DESCRIPTION:
When copying a Calendar line which is derived from a template or Calendar, the new record is not derived from that
template or Calendar.
All fields in the new record can be modified.

Solution: 132311
SITUATION IDENTIFIED IN:
"Print Remittance letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
Wrong bank account of the factoring bank is getting printed in the Remittance letter
SOLUTION DESCRIPTION:
Correct bank account of the factoring bank will get printed now in the Remittance letter

Solution: 132314
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
The fields "Invoice-to Contact" and "Pay-by Contact" cannot be changed on the Sales Order Header (tdsls4100s000) when
the order is released to invoicing.
SOLUTION DESCRIPTION:
The fields "Invoice-to Contact" and "Pay-by Contact" can be changed when the order is released to invoicing.

Solution: 132318
SITUATION IDENTIFIED IN:
"tfacr3420m000" (Print Reminders)
SITUATION DESCRIPTION:
If more than one report is attached to the session then the users are forced to choose the report twice.
SOLUTION DESCRIPTION:
User is allowed to choose the report only once when there is more than one report attached.

Solution: 132323
SITUATION IDENTIFIED IN:
"Finance Table definition" ()
SITUATION DESCRIPTION:
In Baan ERP, performance problems were noticed in the following sessions, which can be solved only with a table
change
- Match Purchase Receipt Line( tfacp2544m000)
- Send Trade Notes/Checks to Bank ( tfcmg4130m000 )
SOLUTION DESCRIPTION:
The table changes have been implemented. The tables involved are
- Orders by Packing Slip ( tfacp245 )
- Anticipated Payment / Receipts ( tfcmg110 ).
Solution: 132349
SITUATION IDENTIFIED IN:
"Service Contract Installments" (cisli2165s000)
SITUATION DESCRIPTION:
When a Service Contract Installment is posted to Central Invoicing, the forecast amount was incorrectly posted. The
forecast amount in home currency was also shown incorrectly.
SOLUTION DESCRIPTION:
The forecast amount from the Service Contract Installment is correctly converted to the required currency and posted to
Central Invoicing.

Solution: 132357
SITUATION IDENTIFIED IN:
"Complete Production Order" (tisfc0520m000)
SITUATION DESCRIPTION:
When using Lot by Unit controlled End Items and the receipt is partial, wrong warehouse lines are made. Also a receipt
booking, led to a blocked outbound line for the end-item.
The quantities for the end-item in the inbound line are incorrect.
SOLUTION DESCRIPTION:
When using a Lot by Unit controlled end-item and report partial complete the inbound order quantities are correct.
Also when returning a quantity from warehouse to shopfloor a unblocked outbound line is created.

Solution: 132362
SITUATION IDENTIFIED IN:
"display browser" (ttstpdisplay)
SITUATION DESCRIPTION:
When printing to display and viewing the last page of the printout then the sessiontimeout mechanism is not working. While
ttstpdisplay every 4 seconds checks if there is more to print.
SOLUTION DESCRIPTION:
Now when the print job is ready the ttstpdisplay process will stop checking for more data.

Solution: 132364
SITUATION IDENTIFIED IN:
"Sales order lines" (tdsls4101s000)
"Sales orders below/above allowed margin" (tdsls4518m000)
"Sales order parameters" (tdsls0100s400)
SITUATION DESCRIPTION:
The following situations occurred:
-1- The target price, displayed in the session "Sales orders below/above allowed margin" (tdsls4118s000), is wrong. This
price is not being properly converted in the reference currency.
-2- If a discount amount applies for a sales order line, the target price in the margin control is incorrect.
-3- Gross margin header logs are not displayed anymore in the session 'Sales orders above/below Allowed Margin'
(tdsls4518m000).
-4- The functionality doesn't work according to the help text of the field Margin control (tdsls000.maco.4). In the help
text, the attached note says:
"Note:
BAAN ERP uses the Upper Margin Control field and the Lower Margin Control field, defined in the Sold -To Business
Partner session, to control the margin per order"
This is not correct since the upper and the lower margin control specified in the sold-to business partner, is used to
check the GROSS margin header.
SOLUTION DESCRIPTION:
-1- Some unnecessary functions have been avoided. One of them is not needed since the required price is already expressed
in the reference currency; it is totally unnecessary to convert this price into the home currency (once again).
Other functions has been rewritten. The purpose of these functions is to convert the net price and the commission price
into the home currency and assign them to tables margin data. The target price is retrieved depending on the parameter
'Target price for margin control', as follows:
1. Sales price of item -> Sales price (tdisa001.pris) expressed in the reference currency
2. Rec. retail price of item-> Suggested retail price (tdisa001.prir) expressed in the reference currency
3. Acc. to price structure -> Price book of item (tdpcs031.bapr) expressed in the price book currency (tdpcg031.curn) (*)
4. Cost price of item -> Cost price (tcibd007.ecpr) expressed in the cost price currency (tcibd007.ccur) (**)
(*) When calculating the required price, the price from the price book is already converted in the transaction currency.
(**) The cost price is expressed in the reference currency when entering an order line.
-2- The field 'Structure discount' won't be updated in case the price/amount are manually modified.
-3- The filter, which selected sales order lines. has been reprogrammed. Therefore, the margin data logged for sales order
headers will be displayed. These query extensions have been rebuilt so all logs are shown.
In case the option 'Hide cancelled lines' is selected, all none cancelled order lines will be displayed. When selecting the
option 'Show all lines', all sales order lines will be displayed; including those which are cancelled.
-4- The help text has been adjusted. The note specified in the problem description has been removed from the margin
control's help text and it has been placed in the gross margin control header's help text. This is done in order to avoid
some confusion concerning the use of the fields upper and lower margin control defined in the sold-to business partner
data.

Solution: 132379
SITUATION IDENTIFIED IN:
"Purchase Order lines" (tdpur4501m000)
SITUATION DESCRIPTION:
Message:Financial dimension not found when generating Purchase Order
-1- When a Subcontracting purchase order is generated from a subcontracting operation in Shop floor, the account to the
Purchase order line is picked up from the integration traction Production / Subcontracting. The ledger account derived so
requires the dimensions to be filled up mandatory. The dimensions are also defined for the integration traction Production
/ Subcontracting. But these dimensions are not defaulted and the system is not generating the purchase orders.
-2- A purchase order is generated from a purchase requisition and then the requisition is deleted. If the purchase order is
deleted, the system does not allow that.
SOLUTION DESCRIPTION:
-1- The Dimensions that are defined for the integration traction Production / Subcontracting are picked up instead of
Purchase / General Cost.
-2- The deletion of the Purchase order line is possible even after the linked requisition is deleted.

Solution: 132386
SITUATION IDENTIFIED IN:
"MAUC Correction" (whina1230m000)
SITUATION DESCRIPTION:
Inventory values of items using valuation method MAUC are determined out of all inventory increasing transaction values.
This means that when goods are received against an incorrect transaction price, the MAUC value is update with this wrong
transaction price and results in an incorrect MAUC value for this item.
All kinds of transactions can increase inventory levels and therefore influence the MAUC value. For example:
- Purchase
- Production
- Service
- Project
- Inventory Adjustment
- Inventory Transfer
The most frequently used transaction for increasing the inventory levels is the purchase transaction. When goods are
purchased, the purchase price is used for updating the MAUC value. When an incorrect purchase price is used when receiving
the goods, the MAUC is updated against this incorrect purchase price. It is possible to correct the transaction price via a
correction on the receipt price of the purchase order. The MAUC value will be adjusted as long as the goods received are
still 'financially' present in the warehouse.
For the other transactions, which can increase inventory levels and therefore influence the MAUC value while for those
transactions there is no functionality present to correct the MAUC value.
SOLUTION DESCRIPTION:
The new session whina1230m000 "MAUC Correction" is developed to make it possible to adjust the MAUC value at any
time, independent of the transaction origin that caused the incorrect MAUC value.
This session will replace the current MAUC value with a user defined value and process a financial integration transaction
of type 'revaluation' for the difference to adapt the inventory value registered in the finance module.
Several options are available:
- Consider only those items for which the MAUC differs more then a defined percentage
- Execute program in test mode or update mode
- Replace the current MAUC with:
- the Standard Valuation Price or
- the Last Purchase Price or
- a user-defined value (this is only possible for 1 item at a time)

Solution: 132387
SITUATION IDENTIFIED IN:
"Estimated Materials " (tisfc0510m000)
SITUATION DESCRIPTION:
When an operation is deleted in production planning, the material is linked to the next operation. But the warehouse linked
to the work center is not updated for the next operation. It still carries the warehouse linked to the Worcenter of the
previous /deleted operation.
SOLUTION DESCRIPTION:
Now if we delete an operation, the warehouse in the estimated materials is replaced with the warehouse related to the work
center of the next operation

Solution: 132388
SITUATION IDENTIFIED IN:
1. "Item Supplier Information" (tdipu0110s000)
2. "General Table Maintenance" (ttaad4100)
SITUATION DESCRIPTION:
1. The default value for the "Capacity Time Unit" field in the "Item Supplier Information" table definition is 'Year'. But,
the allowed values are 'Week' and 'Month'. This causes a problem when data is imported in to this table using Baan
Exchange, which sets the initial value even though that value is not allowed.
2. The name of the table tdpur451 is displayed as "Purchase Order Lines" even though this should be "Purchase Order
Lines History".
SOLUTION DESCRIPTION:
1. The initial value for the field "Capacity Time Unit" is changed from 'Year' to 'Week'. When user imports data in to the
"Item Supplier Information" table through Baan Exchange, the initial value for this field "Capacity Time Unit" will be
'Week' instead of 'Year'.
2. System will display the correct name for the Purchase Order Lines History table.

Solution: 132390
SITUATION IDENTIFIED IN:
"Form Editor" (ttadvformedit)
SITUATION DESCRIPTION:
When the size of a report layout containing multibyte labels was increased (e.g. extra lines were added), the extra space
created was not empty, but contained garbage.
Note: this only happened for reports being maintained for a multibyte language.
SOLUTION DESCRIPTION:
When a report layout is increased, the new space is empty now.

Solution: 132396
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2120s000)
SITUATION DESCRIPTION:
1. When a Service Order is linked to a PCS project and the actual cost lines for this order are split into an "Invoicing"
part and an "Internal(other)" part, then when costing the order, only the "Invoicing" part will be booked as "Approved for
Invoicing" financial integration, but the financial integration posting "Internal Service Costs" is not booked.
2. When a Service Order is linked to a PCS project, the WIP-reversal postings for Service Order Material Costs, pass the
wrong entity type(from). It is "Warehouse" but it should be "Department". The entity should be the calculation office of
the project.
3. When changing the Cost Component of an Actual Material Line, Baan exits completely without saving the change. This
does not always happen, it depends on the number of Cost Components linked to the Item. See session "Cost Component
Details" (tcibd0110m000). If this number exceeds 3 the problem occurs (only in B50c).
4. When changing the Cost Component of an Actual Material Line and the at number 3 mentioned problem does not occur,
then the new issue integration bookings are all linked to the project. So the credit Issue integration booking from
Warehousing which was originaly not linked to the project is now counterbooked with a negative issue amount but linked to
the project and then newly booked with a positive amount but then also with a link to the project.
SOLUTION DESCRIPTION:
1. When a Service Order is linked to a PCS project the Financial Integration postings "Internal Service Costs", "Warranty
Costs" and "Field Change Order Costs" are taken into account when costing the cost line.
2. When a Service Order is linked to a PCS project, the WIP-reversal postings for Service Order Material Costs, will have
the entitype from as 'Department' and use the calculation office of the project.
3. When changing the Cost Component of an Actual Material Line, the Cost Component is changed where necessary. The
System keeps running without errors.
4. When changing the Cost Component of an Actual Material Line the following steps are performed.
A. The existing credit issue booking is counterbooked with the same amount but then negative. With the old Cost
Component. Without a link to the project.
The existing debit issue booking is counterbooked with the same amount but then negative. With the old Cost
Component. With a link to the project.
B. A new credit issue booking is created with the same amount but now positive. With the new changed Cost Component.
Without a link to the project.
A new debit issue booking is created with the same amount but now positive. With the new changed Cost Component.
With a link to the project.

Solution: 132397
SITUATION IDENTIFIED IN:
"Print Variance Analysis" (tfacp1460m000)
SITUATION DESCRIPTION:
The "Rotate Currency" button should be accessible when there is more than one currency.
SOLUTION DESCRIPTION:
Since there is only 1 company the test on 'dependent' is not valid anymore and is removed. There for the "Rotate
Currency" button is now accessible when there is more than one currency.

Solution: 132398
SITUATION IDENTIFIED IN:
"Split Shipments" (whinh4231m000)
SITUATION DESCRIPTION:
An error message appeared due the calculation problems.
SOLUTION DESCRIPTION:
The calculation problems are solved so that the message only appears in case of a real error (false input).

Solution: 132401
SITUATION IDENTIFIED IN:
"Service order: Actual Material Costs" (tssoc2121s000)
SITUATION DESCRIPTION:
The 'to-be delivered quantity' is not properly rounded. This occurs in case entering an item, which unit's rounding factor
is set as 1.0000. Therefore, the to-be delivered quantity gets a negative value once the issue has been performed. Also the
message 'Service item not found' was displayed which is not valid.
SOLUTION DESCRIPTION:
The to-be delivered quantity is being rounded immediately after entering, using the unit's rounding factor. The same is
done for the fields 'Estimated Quantity', 'Subsequent Delivery' and 'Actual Quantity'. Also the rounding has been done for
quantities for Material requirements of Reference activities.

Solution: 132420
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
When a service order is linked to a PCS Project then, in the integration transactions created from Central Invoicing, the
Entity (From) and the Entity (To) both have the service department, while this should be the calculation office of the PCS
Project.
SOLUTION DESCRIPTION:
Now when a service order is linked to a PCS Project, in the integration transactions created from CI, the Entity (From) and
the Entity (To) both have calculation office of the PCS Project.

Solution: 132422
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
Fatal Error 205 "Out of Range" occurs, if the "Print" option in "EDI messages" is changed after confirming lines in
Central Invoicing,
SOLUTION DESCRIPTION:
Now Fatal Error does not occur. The user will now be able to change the "Print" option, if no lines relating to the order
have the status "Confirmed".

Solution: 132429
SITUATION IDENTIFIED IN:
"Insert GRNI Correction" (tfacp1137s000)
SITUATION DESCRIPTION:
In the session, when entering a manual correction, after entering the document date, the fiscal periods do not default.
SOLUTION DESCRIPTION:
Because the document date is taken in account, now the fiscal period is defaulted according this document date.
When the period according to the document date is closed or not present the period will be the period of the present date.
Also the session "Create GRNI correction batch - tfacp1240m000" is updated so the periods are here defaulted as well.

Solution: 132434
SITUATION IDENTIFIED IN:
"Print Scheme of Fixed Asset Transactions" (tffas0440m000)
SITUATION DESCRIPTION:
Depreciation Adjustment amounts of previous year are not considered while calculating the depreciation amounts for the
previous year in report "Print Scheme of Fixed Asset Transactions" (tffas0440m000).
SOLUTION DESCRIPTION:
The previous year's depreciation adjustment amounts are taken into consideration.

Solution: 132435
SITUATION IDENTIFIED IN:
"Print Sales Orders" (tdsls4401m000)
SITUATION DESCRIPTION:
1. When a sales order is printed and the customer belongs to same country (i.e.) the country mentioned in the address and
the country maintained in the company data are same, Country name is also printed on the report which is not
correct. (DF 132733 )
2. When printing an address, if the report has fewer lines available for output than defined in the Address format/Address
combination, the lines in the middle are dropped instead of the last line defined in the sequence. (DF 132922)
SOLUTION DESCRIPTION:
1. Now the country name is printed on the report only when the customer address belong to a different country .
2. The line numbers defined in the address format are considered and printed correctly.

Solution: 132436
SITUATION IDENTIFIED IN:
"Print Business Processes" (tgbrg5400m000)
SITUATION DESCRIPTION:
The where-used option for printing Business Processes is not working correct.
For example Project Models in a version derived from Business Process version are not mentioned on the report.
SOLUTION DESCRIPTION:
The where-used reports of more components in DEM did not take versions, which were derived from the component
version into account.
The where-used reports for Business Processes, Business Functions, Business Control Diagrams and Support
Applications (Utilities) are changed, so that now also versions derived from the component version are taken into account.

Solution: 132440
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Warehouse and Item" (whina1210m000)
SITUATION DESCRIPTION:
The report "Inventory Valuation by Warehouse and Item" shows wrong values in case of items with valuation method "lot
price".
This happens when lots are totally consumed and an inventory valuation is done based on a date in the past.
In this case the lot isn't taken into account, even if it was on stock on the requested date.
SOLUTION DESCRIPTION:
Consumed lots are taken into account properly, so that the right amounts are reported.

Solution: 132442
SITUATION IDENTIFIED IN:
"Sales order lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Help text is missing for field 'Hold Back Qty'.
SOLUTION DESCRIPTION:
The runtime data dictionary has been executed for the help text as well as for the form fields. This will allow the system to
display the help text for the form field 'Hold Back Qty'.

Solution: 132450
SITUATION IDENTIFIED IN:
"Purchase Orders" (tdpur4501m000)
SITUATION DESCRIPTION:
The execution mode of the Purchase Order Type is 'Interactive'. But, the order is 'Release to Warehousing' manually and
the status of the order line is waiting for receipts in warehousing. Now, when the user runs the option "Direct
Processing" the system prompts "Execute Release to Warehousing (Batch) for the Order?" and says "No Data within
selection" and then the question "Execute Purchase Order Receipts for the order?" pops up and answering YES to that also
yield a message says "No Data within selection".
When there is no suitable order line present for Releasing to warehousing, the system should not ask the question
"Execute Release to Warehousing (Batch) for the Order?"
SOLUTION DESCRIPTION:
The question "Execute Purchase Order Receipts for the order?" means the receipts that are made in the purchasing module
and not the ones that are carried out in the warehousing module. The warehousing receipts are automatically carried out
when the order is released to warehousing with the interactive process. If the order is already released to warehousing
manually, the system no longer asks the question "Execute Release to Warehousing (Batch) for the Order?" Also the
question "Execute Purchase Order Receipts for the order?" pops up only when there is any receipt that is to be carried out
in the purchase department.

Solution: 132452
SITUATION IDENTIFIED IN:
"Planned material transaction" (tppss6110s000)
SITUATION DESCRIPTION:
Wrong way of recalculating the Purchase price when business partner is changed.
SOLUTION DESCRIPTION:
Now the price is also calculated properly when we change the buy from business partner.

Solution: 132459
SITUATION IDENTIFIED IN:
"Sales Quotation Lines" (tdsls1501m000)
SITUATION DESCRIPTION:
When "Recalculate Price/Discount entire Quotation" is executed, amount was calculated with new price retrieved from
price book, but price remained old price.
SOLUTION DESCRIPTION:
When "Recalculate Price/Discount entire Quotation" is run, both Price and Amount changes in synchronization.

Solution: 132460
SITUATION IDENTIFIED IN:
"tdpur4100s000" (Purchase Order Header)
SITUATION DESCRIPTION:
Purchase order is created with a particular ship from BP and a ship from contact. Lines are also created with the same
data. Now, the Ship from BP is changed in the Purchase Order and the Ship from contact that was entered earlier is
blanked out. When tried to save the changes, the system gives the error 606 (Reference does not exists)
SOLUTION DESCRIPTION:
The error 606 does not pop up any more. The changes that are made to the Purchase Order header are updated to the
Lines.

Solution: 132466
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Sales price printed in the invoice is per quantity unit and not per price unit.
Also, when two sales lines are present in an invoice and if the second line has zero amounts, then the whole invoice is
not printed if the parameter "Suppress zero amounts" is ON.
SOLUTION DESCRIPTION:
Both the units will be printed and the price will be printed per price unit.
Also the invoice is printed correctly when the parameter "Suppress zero amounts" is ON.

Solution: 132468
SITUATION IDENTIFIED IN:
"Purchase order lines" (tdpur4501m000)
SITUATION DESCRIPTION:
For a Purchase order line with split delivery the order balance does not get updated with the option 'Recalculate price and
discount' for order line.
SOLUTION DESCRIPTION:
The Purchase order balance at the header level now gets updated when the option 'Recalculate price and discount' is used
for order line with split delivery.

Solution: 132472
SITUATION IDENTIFIED IN:
"Item purchase business partner" (tdipu00110m000)
SITUATION DESCRIPTION:
Values of Fields "Order Quantity Increment" and "Minimum Order Quantity" are
getting lost once the user tabs a previous form and comes once again to the
current form.
SOLUTION DESCRIPTION:
Now values of "Order Quantity Increment" and "Minimum Order Quantity" retain even when forms are changed.

Solution: 132480
SITUATION IDENTIFIED IN:
"Release to Invoicing (batch)" (tdsls4247m000).
SITUATION DESCRIPTION:
Message tdslss401.4 is missing.
SOLUTION DESCRIPTION:
Message tdslss401.4 ?????????? was introduced in Solution 128621.
By mistake the message was not included in the deliverables of solution 128621.
By installing this solution (132480), the right message will be in place.
This message will be shown when the Sold-to Business Partner of Sales Order Header differs form Sold-to BP on Lines.
Message text: "Sold-to Business Partner of Line does not match with Sold-to Business Partner of Header." will be
displayed.

Solution: 132484
SITUATION IDENTIFIED IN:
"Post Payments" (tfcmg1257m000)
SITUATION DESCRIPTION:
When a Standing order and a Purchase invoice are composed and posted simultaneously, reference of Standing order is
copied to transaction reference of anticipated payment.
SOLUTION DESCRIPTION:
When a Standing order and a Purchase invoice are composed and posted simultaneously, reference of Standing order won't
be copied to transaction reference of anticipated payment.

Solution: 132486
SITUATION IDENTIFIED IN:
"Assign unallocated / advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
While re-entering session 'Assign Unallocated/Advance Receipts to Invoices, documents which belongs to other business
partners are shown although no parent-child structure exists.
The problem situation is as follows:
1) When two unallocated receipt documents are created with the same document number and the same series but with
different line numbers for different business partners and part of the unallocated receipt document is assigned to the Sales
Invoice.
2) When trying to assign the remaining part of the unallocated receipt document, the system is picking up a different
business partner record and the wrong document is displayed in this session.
SOLUTION DESCRIPTION:
As long as no parent-child structure between business partners exist, only documents of the Pay-by business partner to
which the unallocated receipt belongs are shown within session 'Assign Unallocated/Advance Receipts to Invoices'.

Solution: 132497
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
The step "Confirm Picking List" takes a huge amount of time.
SOLUTION DESCRIPTION:
The process is optimized so that it completes within an acceptable time frame.

Solution: 132500
SITUATION IDENTIFIED IN:
"Activity Budget (Material Lines)" (tpptc2110s000)
SITUATION DESCRIPTION:
If for an Item, discount is maintained in Contract or Price Matrix, the same is not considered in Budgets.
So, the price value is different from actual price that will be incurred.
SOLUTION DESCRIPTION:
Now, Budget Price will be Net price (i.e. Price - Discount) if discount is present.

Solution: 132504
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
"Correction Type" and "Correction document" not getting filled when invoices are posted from Central Invoicing. This is
essential as many legal reports pick the invoice lines only if these fields are filled.
SOLUTION DESCRIPTION:
Now the fields are correctly filled.

Solution: 132509
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000) / "Process Patches" (ttpmc2102m000)
SITUATION DESCRIPTION:
After installation of a range of solutions or a Service Pack, not all solutions got status 'Installed'. If a Service Pack was
installed some solutions belonging to that Service Pack still had status 'Available'. When individual solutions were
installed, some retained status 'To Install'.
This problem is caused by the combination of the superseding concept, which has been introduced by solution
122399, and missing dependencies. When dependencies are missing, it can be that a newer solution for a
component was already installed, but the superseding algorithm sees this solution as a superseding solution. Because the
latter is already installed, the status of the so-called superseded solutions is not changed to 'Installed'.
In the past, for some solutions, dependencies were not defined, for example for the standard program (ttstpstandard).
Nowadays all solutions, created by Baan, are sent with the correct dependencies.
SOLUTION DESCRIPTION:
The superseding algorithm has been changed: an already installed solution is never considered as a superseding solution
anymore.

Solution: 132512
SITUATION IDENTIFIED IN:
"Purchase contract lines" (tdpur3102s000)
SITUATION DESCRIPTION:
It is possible to leave the fields 'Purchase unit' and 'Price unit' empty in the session "Purchase Contract Lines"
SOLUTION DESCRIPTION:
It is not possible to leave the fields 'Quantity unit' and 'Price unit' in the session "Purchase contract lines" as blank.
The reason for this change is as follows:
It is not logical to specify Agreed quantity or Price without specifying any unit.
When those fields are left blank, then during linking of contract to a Purchase order line, the system would not be able to
retrieve price due to the absence of the unit.

Solution: 132517
SITUATION IDENTIFIED IN:
"Print Costing History by Item Group" (ticst3401m000)
SITUATION DESCRIPTION:
In the German and Dutch language the label Added Value is not displayed
SOLUTION DESCRIPTION:
Report is changed and more space is created for the label Added Value.

Solution: 132533
SITUATION IDENTIFIED IN:
"Match Invoices to Purchase Receipt Line" (tfacp2151s000)
SITUATION DESCRIPTION:
The field Totally matched in the table "Receipts by Packing slip" ( tfacp245 ) is not updated properly.
SOLUTION DESCRIPTION:
This field was never intended to be used during normal matching and approval. It was used only during selfbilling process
historically, and not used anymore even in selfbilling. So updating this field has been stopped.

Solution: 132549
SITUATION IDENTIFIED IN:
"Print surveyor's report" (tpppc4421m000)
SITUATION DESCRIPTION:
Wrong Work in progress amount when a main project has subproject(s).
SOLUTION DESCRIPTION:
Now correct amount in Work in progress is displayed.

Solution: 132550
SITUATION IDENTIFIED IN:
"tdsls4401m000" (Print Sales Orders )
SITUATION DESCRIPTION:
When a 'Space After' is specified on a line in the Session " Address Formats ", and the field to which the space belongs is
empty, the space is included on the address. The address is printed with unnecessary spaces on the report.
SOLUTION DESCRIPTION:
Now the Blank spaces are not created even though they are specified in the "Address Formats " if the field is empty in the
session "Addresses "

Solution: 132552
SITUATION IDENTIFIED IN:
"Service Order Activities" (tssoc2510m000)
SITUATION DESCRIPTION:
The performance of session "Service Order Activities" (tssoc2510m000) is very low when using buttons First Group,
Previous group, Next group, or Last Group.
SOLUTION DESCRIPTION:
The performance of session "Service Order Activities" (tssoc2510m000) is optimised by improving the search for the
appropriate service order.

Solution: 132554
SITUATION IDENTIFIED IN:
"Check Opening-Balance" (tfcorcont_ac40)
SITUATION DESCRIPTION:
If ever in the past on a balance sheet account a transaction is done with an emu currency, it will stay on that balance sheet
account.
A correction program for this is needed.
SOLUTION DESCRIPTION:
The correction program takes care of the conversion of the emu currency of the balance sheet account into the euro.

Solution: 132556
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the parameter "Date of Sales Invoice Tax" is empty, system is not calculating tax. It should take the invoice date as
default.
SOLUTION DESCRIPTION:
Now if the parameter is left empty, the tax is calculated based on the invoice date.

Solution: 132561
SITUATION IDENTIFIED IN:
"Purchase Invoice" (tfacp1100s000), "Purchase-Invoice Transactions" (tfacp1120s000) and "Sales-Invoice Transactions"
(tfacr1120s000), "Open Entries" (tfacp2520m000)
SITUATION DESCRIPTION:
1. The help text option is not accessible in sessions "Purchase-Invoice Transactions" (tfacp1120s000) and "Sales-Invoice
Transactions" (tfacr1120s000). In session "Purchase Invoice" (tfacp1100s000), the help text option is enabled only in the
last form.
2. In B50_c, the print option in session "Open Entries" (tfacp2520m000) is not enabled.
3. In B50_c, if the invoice-from details are maintained for a business partner and the accounting department, then the
default values (like currency, payment method, terms of payment) should be picked up from here when entering a new
purchase invoice.
4. In B50_c, if a zero amount purchase invoice is approved, unapproved and then the invoice deleted. Then in session
"Transactions" (tfgld1101m000), the approval transaction type is mentioned and the status is ready. If the transactions for
the approval transaction type is opened and then closed, the status of the transaction type in session "Transactions"
(tfgld1101m000) becomes free. It is not possible to delete this transaction type as there are transactions present, hence the
batch cannot be finalized.
SOLUTION DESCRIPTION:
1. The help text option is enabled on all forms for the sessions mentioned.
2. The print option is enabled in the session "Open Entries".
3. The default values are picked up when entering a new invoice from the invoice from business partner details for the
business partner and accounting department combination if they are maintained.
4. It is now possible to delete the approval transaction type from session "Transactions" (tfgld1101m000) when the status
is free.

Solution: 132582
SITUATION IDENTIFIED IN:
"Generate Bills of Critical Capacities" (tirou2230m000)
SITUATION DESCRIPTION:
When the purchased items are used as components in the generic bills of material, the lead time offset calculated is wrong
while generating bills of critical capacities.
SOLUTION DESCRIPTION:
The lead time offset will be calculated correctly while generating bills of critical capacities, even if the purchased items
are used as components in the generic bills of material.

Solution: 132583
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
When a cost item or a project item is added to a Purchase Order that is linked to a Direct Delivery Sales Order, system
doesn't allow the user to process it further. The cost line is not linked to the sales order. Due to that, lot of unprocessed
purchase orders will remain in the system.
SOLUTION DESCRIPTION:
It is not possible to enter a new line for a Purchase Order originated from a Direct Delivery Sales Order.
Solution: 132588
SITUATION IDENTIFIED IN:
"Create Session DLL" (ttstpcreatdll)
SITUATION DESCRIPTION:
Package and Module are not added to the function name generated by session 'ttstpcreatdll'. Because of this it is
possible that two function server DLL's have the same name.
SOLUTION DESCRIPTION:
To solve this problem and to maintain the old functionality a new checkbox is introduced.
If the new checkbox is checked the package & module name are added to functions generated by FS, otherwise they are
not added.

Solution: 132591
SITUATION IDENTIFIED IN:
"netlist" (ttstpaudread)
SITUATION DESCRIPTION:
While filling primary key values in xml tree, they were stripped.
SOLUTION DESCRIPTION:
While filling primary key values in xml tree, they were stripped. Now before filling values in xml tree, its domain is
checked if domain is String or Multibyte String, the primary key value is not stripped. For any other type the value is
stripped.

Solution: 132592
SITUATION IDENTIFIED IN:
"Print Project Model" (tgbrg4400m000)
SITUATION DESCRIPTION:
When the Project Model information is printed, the descriptions of the Business Processes are not correct.
SOLUTION DESCRIPTION:
It turned out, that the wrong information was read for the Business Process description.
The way of reading is changed and now the right descriptions are printed.

Solution: 132597
SITUATION IDENTIFIED IN:
"Table Definition" (Not Applicable)
SITUATION DESCRIPTION:
The solution 132323 has made some changes to table definitions in Finance package. One of the changes made is adding
of new indices. However the new indices were not translated to other languages.
SOLUTION DESCRIPTION:
The indices have been translated to all A languages. The involved tables are tfacp245 and tfcmg110.

Solution: 132598
SITUATION IDENTIFIED IN:
"Print Ranges" (tuxch0412m000)
SITUATION DESCRIPTION:
For an export exchange scheme a number of ranges are entered, used to specify under which conditions a record must be
export or not.
When the ranges of this particular exchange scheme are printed, column 'range value upto' does not show the correct values
[where this value should not be printed at all, previous value taken].
SOLUTION DESCRIPTION:
Initialization of the Range Value Upto added so previously printed one is erased.

Solution: 132599
SITUATION IDENTIFIED IN:
"Print Multi-level Cost Price Calculation" (ticpr2420m000)
SITUATION DESCRIPTION:
When the session "Print Multi-level Cost Price Calculation" (ticpr2420m000) is run to print the report for standard items
with EOQ (Economic order quantity) sub item flag set to NO, then system takes the BOM quantity as order quantity for sub
item cost calculations, instead of end item's order quantity.
SOLUTION DESCRIPTION:
If EOQ (Economic order quantity) Sub item flag set to NO for standard items, then the order quantity for sub item will be
BOM quantity times the end item's order quantity, for operation cost calculation in the report.

Solution: 132611
SITUATION IDENTIFIED IN:
"Print Purchase Back Orders" (tdpur4430m000)
SITUATION DESCRIPTION:
Label " Back Ord. Seq " (pur.bck.ord.seq) is not printed in the "Purchase Back Orders" report in German and Dutch
languages.
SOLUTION DESCRIPTION:
Label will be printed on the "Purchase Back Orders" report in Dutch and German languages.

Solution: 132612
SITUATION IDENTIFIED IN:
"Confirm receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Statuses are not set correctly when receipt is cancelled in warehousing and
0 receipt records are created in session tfacp245.
Situation:
Purchase 10 pcs.
Receive 8 pcs. (Final receipt flag is No)
Match and approve the 8 pcs.
Cancel the 2 pcs in warehousing. (Final Receipt flag is Yes)
The result is that a 0 quantity transaction is created in tfacp245 but the
statuses of tfacp240.toma and tfacp240.ppvp are not set and (if necessary)
the last purchase price variance (if currency rate has been changed between
the order and the invoice or in case of rounding) has not been created.
SOLUTION DESCRIPTION:
As soon as a receipt of 0 quantity is created in order to cancel the delivery, the record in tfacp245 should not be created
and the statuses of the approval should be set correctly and (if necessary) a purchase price variance
has to be created.
0 quantity records are created in tfacp245 for the following conditions:
- When maintaining receipts for items with inspection
- When maintaining receipts for items with a ordered quantity of 0

Solution: 132617
SITUATION IDENTIFIED IN:
"Global Confirmation of Future Invoices" (cisli2219m000)
SITUATION DESCRIPTION:
Exception report needed for "Global Confirmation of Future Invoices" session. If there are any errors, and if invoice
lines are not confirmed, the user never knows the reason.
SOLUTION DESCRIPTION:
Now an exception report is printed, which prints the reasons for not confirming the lines.

Solution: 132618
SITUATION IDENTIFIED IN:
"Print Item Supplier Information" (tdipu0410m000)
SITUATION DESCRIPTION:
Item Purchase text is maintained in BP language, which is different from user language. When it is printed, this text will
not get printed in the report.
SOLUTION DESCRIPTION:
When a user is opening the session in one particular language say for example language 2 (English), and for the Business
Partner language is in language 1(Deutsch), then Item purchase internal text will be printed in English and the Item
purchase text which has opened in BP language will also be printed in BP language.

Solution: 132620
SITUATION IDENTIFIED IN:
"Location Capacity" (whwmd3101s000)
SITUATION DESCRIPTION:
For a finite capacity location, even if some (very small quantity of) inventory was put-away to the location during
inbound, still it was possible to advise new inventory to the same location, which leads to exceeding the capacity.
This problem occurs because, the system rounds the small inventory that was first put away to zero, when executing 'Put
away inbound advice'.
Hence it was again possible to advise new inventory to the same location to the extent of full capacity of the location.
SOLUTION DESCRIPTION:
More inventory than the capacity of a location will not be advised.

Solution: 132623
SITUATION IDENTIFIED IN:
"Split Shipment" (whinh4231m000)
SITUATION DESCRIPTION:
The message "Quantity per shipment must be multiple of ..." can appear when numbers are used with more numbers after
the figure than the domain for this number allows. This is due to very small rounding differences.
SOLUTION DESCRIPTION:
With the new created check very small differences are ignored so the message doesn't appear in case of very small
differences.

Solution: 132625
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
- When entering a new detail line in session "Sales Order Line Details" (tdsls4101s200) and tabbing over the 'calc'
button the message "Item Code not found" pops up.
- When leaving the "Sales Order Lines Details" session (tdsls4501m200) and immediately changing the price on the total
line (tdsls4101s000) the open balance is not updated correctly.
- When using recalculate prices and discounts from 'Specific' in session "Sales Order Lines" (tdsls4501m000), the open
balance is not updated correct.
- Question "Recalculating Prices and Discounts on Details" pops up in when closing session " Sales Order Lines"
(tdsls4501m000).
SOLUTION DESCRIPTION:
- Sales Order Line Details can be added without the message "Item Code not found" popping up
- When changing the price on a sales order line, either manually or by recalculating using option "Recalculate prices and
discounts" from 'Specific', the open balance is calculated correctly.
- The question "Recalculating Prices and Discounts on Details" is only being asked when closing the session "Sales
Order Line Details" (tdsls4501m200)

Solution: 132626
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100m000)
"Service request"
SITUATION DESCRIPTION:
1. When a service call is entered for a specific configuration, the contract check box is checked. When entering an
object with serial number, the contract checkbox is unchecked. When saving the call the contract check box is checked
again.
2. The e-service session hangs indefinitely when a service request is submitted to the backend.
SOLUTION DESCRIPTION:
1. The contract check box in session 'Calls' (tsclm1100s000) reflects the correct value during call entry.
2. The e-service session is executed properly when a service request is submitted to the backend.

Solution: 132637
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When Simulating Orders for Customized Clustered Items, derived from a Standard Clustered Plan Item, records are inserted
in internal table 'Plan Item Codes' (cprpd120) for non-existing Standard Clustered Plan Items. The table sizes of 'Plan
Items' (cprpd100) and 'Plan Item Codes' (cprpd120), which should be equal now become different.
When Simulating Orders is run in multibshell, one of the shells runs into an endless loop while inserting records in
internal table 'Plan Item Codes' (cprpd120). This loop consumes very much CPU-time, causing the other shells to stop.
SOLUTION DESCRIPTION:
When Simulating Orders for Customized Clustered Items, derived from Standard Clustered Plan Item" only records for
existing Standard Clustered Plan Items are inserted in table 'Plan Item Codes' (cprpd120).
For non-existing Standard Clustered Items, the signal "Error: Missing Item Data; Item skipped" is generated and printed
on the error-report.
The handling of inserting records in internal table 'Plan Item Codes' (cprpd120) is improved to avoid endless loops when
Simulating Orders in multibshell mode.

Solution: 132638
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Having the following situation:
Company country NLD
Invoice To country: NLD
Invoice From country: NLD
Ship From country: NLD
Ship To country: DEU
A sales order line with a cost item picks up the incorrect VAT country.
SOLUTION DESCRIPTION:
Having a situation as described above, the tax country NLD and domestic tax code from the item sales data is taken.

Solution: 132650
SITUATION IDENTIFIED IN:
"Standard Subcontracting" (tppdm0113s000)
SITUATION DESCRIPTION:
If a new Subcontracting / Equipment record is opened, without closing the old record, all changes made in the second
record are updated in the first record.
SOLUTION DESCRIPTION:
The above problem is solved and now all values will be properly updated in their respective records.

Solution: 132652
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
When having a consignment replenishment sales order, the session "Generate Project Structure for Product Variant
(tipcs2220m000)" is disabled.
SOLUTION DESCRIPTION:
When having a consignment replenishment sales order and the product variant is filled, the session "Generate Project
Structure for Product Variant (tipcs2220m000)" is enabled.

Solution: 132661
SITUATION IDENTIFIED IN:
"Item Issue by Period (Graph)" (whinr1720m000)
SITUATION DESCRIPTION:
When starting session "Item Issue by Period (Graph)" (whinr1720m000) two error messages are logged in the log file of
the bshell.
"Log_mesg: Overflow: format='9999' value='-32768'"
"Log_mesg: Overflow: format='9999' value='32768'"
This is caused because the form fields "Year from" and "Year to" are initialized with the minimum and maximum value of the
field. Directly after this, the current year is displayed.
SOLUTION DESCRIPTION:
Now the fields are not initialized with the minimum value for "Year from" or the maximum value for "Year to".
The current year is displayed without this initialization.

Solution: 132663
SITUATION IDENTIFIED IN:
"Print Statement of Accounts" (tfacr3440m000)
SITUATION DESCRIPTION:
The Pay by Business Partner is not printed correctly on the Customer Statements.
SOLUTION DESCRIPTION:
The Pay by Business Partner is printed correctly on the Customer Statements.

Solution: 132666
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
Billing Request gets posted, even though some errors occurred in the interim turnover posting. This happens only when the
invoice posted is having two tax lines and only the first line is having some problems in posting.
SOLUTION DESCRIPTION:
Now the Billing Request and the invoice remains in the status 'Printed' until all the errors are resolved.

Solution: 132674
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
The service area cannot be changed after the service order has been released, but the location address still is editable.
SOLUTION DESCRIPTION:
The service area and location address can be changed as long as no actual cost lines are present and the service order
status is not "Costed".

Solution: 132679
SITUATION IDENTIFIED IN:
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
The report "Print Actual Cost-Price by Project" shows incorrect quantities, if the receipts for the purchase order lines are
more than one and are not backorders.
SOLUTION DESCRIPTION:
The report "Print Actual Cost-Price by Project" will show only one record per purchase order with correct delivered and
approved quantity.
Please note that this session is developed for printing costing details and not for printing logistical details. So detailed
info on receipts will have to be collected elsewhere; for example in "WIP Transactions by Project"(tcfin1500m001))

Solution: 132685
SITUATION IDENTIFIED IN:
"Charge elements" (tppss2500m000)
SITUATION DESCRIPTION:
Parent Element is not getting updated with the minimum progress of child elements.
SOLUTION DESCRIPTION:
Now the progress of the parent element is getting updated with the minimum most progress of the child elements.

Solution: 132695
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements / RMAs" (tdsls4401m000)
SITUATION DESCRIPTION:
In the following situation, a total line for a sales order line is generated, together with the details:
1. Sales order created via EDI.
2. Print: message prepared for the original line.
3. Before the messages are generated, the line is split into several details.
4. Print: details will be added to prepared messages.
5. After generation, the file contains both the total line and the details.
SOLUTION DESCRIPTION:
The program script has been modified in order to avoid generation of the total line. When printing, the system deletes the
prepared EDI line for the total line, which was still present because it was prepared for the original line.

Solution: 132701
SITUATION IDENTIFIED IN:
"Generate Invoice by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The following Situations were handles by this solution
1. The date of registering the Purchase price variance was the system date.
2. The batch was not balanced when using compression option with tax amounts, due to rounding differences in some case
( when using a currency rate with lot of decimals ).
3. In B50J_b_wrk, purchase variance was not calculated due to the difference in rate between Purchase order and
Invoice. This happens when compression is used.
SOLUTION DESCRIPTION:
The software has been modified to solve the above issues.
1. The purchase price variance will be booked with the transaction date, specified by the user in the form. Additionally
the following changes involving date handling has been done
- The date of approval in the table Maintain Invoice related to purchase order line (tfacp250) will be the transaction date.
- The average purchase price will be updated with the rate information of the invoice instead of the latest rate.
- The check for the blocking of ledger account will be made based on the transaction date instead of the current date.
NOTE: This solution is not available in B50L_c_wrk, since there is no possibility for the user to specify the transaction
date.
2. Now when compression is used, the amounts in General ledger are handled in the same way as in the open entries, to
avoid the batch unbalanced issue.
3.In B50J_b_wrk, the purchase variance is now booked when there is a rate information change between the order and
invoice, when compression is used.
4. In B50_c, the table Compressed orders by document ( tfgld150 ) is updated correctly when compression is used.

Solution: 132707
SITUATION IDENTIFIED IN:
"tdpur1202m000" (Copy RFQ lines to Contracts/Orders)
SITUATION DESCRIPTION:
-1- The Dimension that is defined for the 'Enterprise unit' of the TP project is not retrieved in to the Purchase Requisition
line as well as to the Purchase Order line.
-2- While globally updating the price books via the price matrices, the same price is filled to all the newly created
price books. This happen only when the price is increased/decreased by amount and the currency being different from
the home currency.
-3- Two suppliers quoted for the same RFQ line with different units. Both the suppliers are approved for conversion in to
actual order. When splitting the quantity between the suppliers generates the order, the order amount of one business
partner goes wrong who had quoted in a different unit other than the unit of the RFQ line.
SOLUTION DESCRIPTION:
-1- The 'Dimension' defined for the Enterprise Unit of the TP project is retrieved properly to the Purchase requisition
Lines as well to the Purchase Order Lines.
-2- The Price books are updated with the correct price
-3- The order amount of the generated purchase order is correctly calculated.

Solution: 132719
SITUATION IDENTIFIED IN:
"Print Registered and Matched Purchase Invoices" (tfacp1433m000)
SITUATION DESCRIPTION:
When an invoice related to order is linked to a credit note or a purchase correction is made against it, then the report
does not show these sort of records, even though they were not approved, and there is a balance in the registered ledger
account.
SOLUTION DESCRIPTION:
The above situation has been solved. The report Print Registered and matched invoices have been rewritten when the usage
of the new table tfgld126 has been activated.

Solution: 132729
SITUATION IDENTIFIED IN:
"Print Vendor Ratings" (tdpur8402m000)
SITUATION DESCRIPTION:
When printing Vendor Ratings, only ratings for Subjective Parent criteria are printed (level 0) even though user can select
ratings for Child criteria (levels > 0) by zooming from the Criteria field. This confuses the user as to why the child criteria
are not printed and only the Parent Criteria in the selected range is printed.
SOLUTION DESCRIPTION:
In session "Vendor Ratings by Period" (tdpur8102m000) only the parent criteria is displayed. The same is applicable for
printing the Vendor Ratings also. Only the parent criteria are to be used for the reporting purpose. So, user should be
able to select only the parent criteria when zooming to the session "Subjective Criteria (tdpur8190m000)" from the
Criteria field in "Print Vendor Ratings (tdpur8402m000)" session.
Modifications are now made to display only the parent subjective criteria when user zooms to the "Subjective Criteria
(tdpur8190m000)" session from the Criteria field.

Solution: 132754
SITUATION IDENTIFIED IN:
"Process delivered purchase orders" (tdpur4223m000)
SITUATION DESCRIPTION:
-1- The order quantity of the direct delivery purchase order is less than that of the corresponding sales order. After
completely receiving the purchase order, it is not possible to process the purchase order. The system gives an error
report ""No linked Purchase Order found for sales order line XXXXXXXXX/XX/0". This happens only when the 'Confirm
Back orders Automatically' is YES for the sales orders.
-2- A purchase order is fully received and all the received quantities are rejected in the approvals. When the order is
deleted after processing, the system gives an error report 'The invoice for the receipt of purchase order XXXXXXX has
to be approved in ACP'.
SOLUTION DESCRIPTION:
-1- It is possible to process the direct delivery purchase order.
-2- The deletion of the purchase order is possible now. The system no longer gives the error report.

Solution: 132759
SITUATION IDENTIFIED IN:
"Confirm Shipment" (whinh4275m000)
SITUATION DESCRIPTION:
Some components were missing when delivering the Solution 131846.
SOLUTION DESCRIPTION:
These components are now delivered with the Solution 132759.

Solution: 132766
SITUATION IDENTIFIED IN:
"Match/Approve Purchase Invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
The price difference at the time of purchase invoice approval of a service subcontracting order is not sent to service.
Hence the WIP account is unbalanced after the service order is "Costed".
SOLUTION DESCRIPTION:
The solution is applicable for purchase invoices related to service subcontracting orders.
If the service order is not "Costed", then the price difference at the time of purchase invoice approval is send to service
so they are posted to finance when the service order is "Costed".
If the service order is "Costed", then the price difference at the time of approval has to be manually posted to the profit
and loss account by adding costs in session "Matched Purchase Invoice Transactions" (tfacp1133s000). It is no longer
possible to un-approve an invoice whose service order is "Costed".

Solution: 132767
SITUATION IDENTIFIED IN:
"Approve Purchase Invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
When approving a Purchase Invoice via session "tfacp2107s000 - Approve Purchase invoices" a float exception occurred.
SOLUTION DESCRIPTION:
No more float exceptions occur while approving a Purchase invoice.

Solution: 132771
SITUATION IDENTIFIED IN:
"Check and Install Solutions" (ttpmc2204s000) / "Install Solution" (ttpmc2205s000)
SITUATION DESCRIPTION:
During the installation of a Service Pack or an individual solution, the following fatal error could be given:
Fatal error : Error 205 (Out of range) on ttadv130000 in db_insert(51)
Fatal error : Can not continue in ttpmc2204s000 in DLL: ottpmcdllblang ()
Error : ttpmc2204s000: A not terminated transaction is aborted
Note: In stead of "ttpmc2204s000" also "ttpmc2205s000" could be displayed, if you used the option "Install Solution".
This only happened when you installed solution 123464 and activated the PMC B-Language Support. The
fatal error occurred when a solution was installed, which contained one modified table definition and the modification was
the addition of an index in that table.
When you restarted the installation of the solution, the solution was installed correctly.
SOLUTION DESCRIPTION:
The B-Language processing in PMC has been corrected. A solution with an index added to a table definition, is processed
correctly the first time.

Solution: 132781
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
When a Business Partner has a factoring company but the factoring bank is not defined in the "Pay-to" role
(tccom4124s000), the "Remittance Letter" (tfcmg1270m000) and "Print Composed Payments" (tfcmg1403m000) do not use
the default bank of the factoring company defined in the session "Factoring Companies" (tcmcs0125m000).
SOLUTION DESCRIPTION:
1) When a Business Partner has a factoring company but no factoring bank is defined in the "Pay-to" role of the Business
Partner, the default bank of the factoring company defined in the session "Factoring companies" is printed on the
Remittance Letter (tfcmg1270m000).
2) The factoring bank is not stored in table "Composed Payments" (tfcmg103). Therefore the bank of the "Pay-to
Business Partner" is printed on report "Composed Payments" (tfcmg1403m000) instead of the factoring bank.

Solution: 132783
SITUATION IDENTIFIED IN:
"Sold-To Business Partners" (tccom4110s000)
SITUATION DESCRIPTION:
When Contract Module is not implemented in SLS Parameters, While entering a New Sold-To B.P, an irrelevant message "
Orders and/or contracts present; changing status not allowed." pops up
SOLUTION DESCRIPTION:
Now the system doesn't give irrelevant error message while entering a new Sold- o Business partner.

Solution: 132794
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Tax not calculated for "Advance Receipt Request' when "Date of Sales Invoice Tax" parameter is set to 'Delivery Date'.
SOLUTION DESCRIPTION:
Now the tax is calculated correctly.

Solution: 132796
SITUATION IDENTIFIED IN:
"Sales order lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When using many Exceptions for Taxes (session tcmcs1138m000), after the item on the sales order line is entered it takes
long time to get to the quantity field (next field in sequence).
SOLUTION DESCRIPTION:
When entering the item on a sales order line, the default VAT-code will be looked up by the system. Also the exceptions
have to be considered for this and the lookup routine for that table has been improved. Therefore it now takes less time to
go to the quantity field.

Solution: 132798
SITUATION IDENTIFIED IN:
"tdsls4101s000" (Sales-Order Lines)
SITUATION DESCRIPTION:
Release Date (tdsls401.rdta) for Sales Orders with future Delivery Date (tdsls400.ddat) are not correct for Item of type:
Cost, Service, List, Subcontracting, Equipment and Generic.
Release Date is equal to Order Date (tdsls400.odat) of the Sales Order Header. However, it should be defaulted to
Planned Delivery Date of the Sales Order Header (tdsls400.ddat).
SOLUTION DESCRIPTION:
On Sales Order Lines for Items of type: Cost, Service, List, Subcontracting, Equipment and Generic, the Release Date
(tdsls401.rdta) should be equal to the Planned Delivery Date (tdsls401.ddta).
For all other Item types Release Date will be calculated by subtracting the Item's Outbound Lead time
(whwmd210.oltm) from the Planned Delivery Date. Outbound Lead time of Items can be defined in "Item Data by
Warehouse" (whwmd2510m000).
When no Warehouse is filled for these types of Items, Release Date will be equal to the Order Date (tdsls400.odat) of the
Sales Order Header.

Solution: 132809
SITUATION IDENTIFIED IN:
"Copy Sales Orders" (tdsls4201s000)
SITUATION DESCRIPTION:
When copying a Sales Order Line to an existing Sales Order Header, the copied line does not have the order date of the
Sales Order Header.
SOLUTION DESCRIPTION:
When a Sales Order Line is copied to an existing order header, the order date of the new Order Line is taken from this
header. When a Sales Order Line is copied to a new order header, the current date is used for both new header and lines.

Solution: 132811
SITUATION IDENTIFIED IN:
"Delete Incorrect Warehouse Data" (whcor2003m000)
SITUATION DESCRIPTION:
When a Purchase Order Line was deleted or cancelled and status set to 'Awaiting Deliveries', one should expect
'Inbound Order Lines' and 'Warehouse Order Header' to be deleted. This was not happening before installing SOL
126264. Purchase Order Lines were deleted, but Warehousing data was not being updated accordingly.
SOLUTION DESCRIPTION:
Correction program now available to
1 - Identify and delete pending Inbound Order Lines (whinh210) linked with Purchase Order Lines that are cancelled or
deleted.
2 - Delete the Warehouse Orders (whinh200), which are without lines.
3 - Update history tables Warehouse Order History (whinh250) and Warehouse Order Lines History-Receipts
(whinh260).
Introduction
==========
When a Purchase Order line is either 'Deleted' or 'Cancelled', the Warehouse Order Lines are removed. This happens only
after installation of Solution 126264. Prior to this the Warehouse Records were not appropriately deleted, and so the
records remain.
Table (field) s involved
==================
Warehouse Orders (whinh200) Full Record
Warehouse Order Lines-Receipts (whinh210) Full Record
Warehouse Order History (whinh250) Full Record
Warehouse Order Line History- Receipts (whinh260) Full Record
Ranges and options
================
The correction program provides following selection ranges and options:
Range Purchase Order From/To
Range Purchase Order Position From/To
Option to select if Test Run of Definite Run should be performed
Reporting
========
One report is printed for printing the Purchase Order Number and the Position number of the Warehouse Order that is
deleted. If there is some error in deleting, the message is printed in the same report.
Trace ability
==========
It is not possible to mark the updated records. The report is the only way to trace which records are changed.
Pre-conditions
===========
None.
Post-conditions
============
After running the Correction Program, it should be ensured that the Solution 126264 available for solving the problem is
installed.
Multi-site aspects
==============
The correction program will take care of only one company at the time. This means that the End-user must run the
correction program for every individual company.

Solution: 132830
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
Session "Print Project Work In Process" (tipcs3480m000), when using form selection "By Ledger Account" (for detail level
) will show in the report field "Total of Leger Account xxxxxx in History" an incorrect amount. This will only occur when
a range of ledger accounts is selected and listed on the report. Also this amount is not recalculated when the Print
currency is changed on the second form.
SOLUTION DESCRIPTION:
The session "Print Project Work In Process" (tipcs3480m000), when using form selection "By Ledger Account" ( for detail
level ) will show the correct amount in the report field "Total of Leger Account xxxxx in History".

Solution: 132832
SITUATION IDENTIFIED IN:
"Release Batch to Warehousing" (tdsls4246m000)
SITUATION DESCRIPTION:
Session "Release Batch to Warehousing" is not closed and button Continue is pressed for a just released Sales Order
again. When this order has a shipping constraint the error "Set could not be released completely" occurs.
SOLUTION DESCRIPTION:
When the above procedure is followed the message "No Data within Selection" is given.

Solution: 132836
SITUATION IDENTIFIED IN:
"Print Product Variants" (tipcf5401m000)
SITUATION DESCRIPTION:
When printing the product variants, some features are not printed in the report.
SOLUTION DESCRIPTION:
The session will print all the features attached to the product variant.

Solution: 132840
SITUATION IDENTIFIED IN:
"Print Purchase Order History by Supplier and Item" (tdpur5401m000)
SITUATION DESCRIPTION:
In a company, if the home currency is different from purchase order currency, the currency rate is applied incorrectly for
amounts recalculated to home currency for the invoiced purchase order history. For the created purchase order history the
figures are correct.
SOLUTION DESCRIPTION:
Now, when Purchase Order History is printed with Transaction type as "Invoiced", the amount in home currency will be
correctly printed.

Solution: 132843
SITUATION IDENTIFIED IN:
"Totals for Business Partner by Company" (tfacr2534m000)
SITUATION DESCRIPTION:
BP Balances displayed in session tfacr2534 were in Reference currency but the label showed "Amount in HC"
SOLUTION DESCRIPTION:
The Labels have been modified accordingly and the amounts are printed in Reference currency

Solution: 132848
SITUATION IDENTIFIED IN:
"Billing Requests" (cisli2100s000)
SITUATION DESCRIPTION:
The option "Instead of Defaults" in 'Billing Request' does not allow credit note's Transaction type even if the 'Overwrite'
option in the 'Billing Request Addition' has 'Credit Note Transaction type' enabled.
This prevented the user to combine positive and negative lines to create a sales credit note even if the final invoice
amount was negative.
SOLUTION DESCRIPTION:
Now the user is given the flexibility to enter a credit note in the BR addition, but if the final invoice amount is
positive, then the system will give an error message and come out of the composing process.

Solution: 132863
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
"Sales Contracts" (tdsls3100m000)
"Sales Quotations" (tdsls1100s000)
SITUATION DESCRIPTION:
When zooming in session Sales Orders (tdsls4100s000) to "Text" in Dutch Language "Offertetekst" instead of "Koptekst"
is shown
SOLUTION DESCRIPTION:
Correct text is shown now.

Solution: 132864
SITUATION IDENTIFIED IN:
"Update Vendor Ratings" (tdpur8850m000)
"Purchase Order lines" (tdpur4101s000)
SITUATION DESCRIPTION:
-1- When no employee has responded via the questionnaire result for particular subjective criteria, the subjective rating for
that criteria is considered as 0. The user has to be intimated about this at the time of calculating the vendor rating.
-2- For the cost items, the order unit and the price unit will always be the same. Even though the price is maintained in
some other unit than the default purchase unit, the price is not converted to this unit as the price from the item data is
always picked up. The user can always change the purchase unit and the price books that are maintained in the corresponding
unit will be defaulted to the purchase order line. But, in case of direct delivery purchase order line the unit is always
disabled and the user cannot retrieve the prices that are maintained in other units. The purchase unit has to be enabled for
changing for the direct delivery purchase order lines for the cost items.
SOLUTION DESCRIPTION:
-1- When the questionnaire results are not found for particular criteria, an error report is printed saying,
"Questionnaire results for vendor XXXX and scenario XXX not found"
-2- The purchase unit for the direct delivery purchase order lines with cost item is enabled for the user to modify.

Solution: 132871
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When trying to save a modified Sales Order Line (tdsls4101s000) after the following steps a fatal error message "Index
out of dims" occurs:
1. Session Sales Order Lines (tdsls4501m000) Double click to open a Sales Order Line (tdsls4101s000)
2. Change a field on the Selling tab
3. Click on the warehouse tab (change nothing)
4. Go back to the general tab and change the quantity
5. Save
6. The tdpcg0240s000 Price and Discount Recalculation Parameters session is displayed with 'Recalculate Price' and
'Recalculate Discounts' ticked. Click 'OK'.
7. Without leaving the lines repeat the above steps and again Save.
8. The tdpcg0240s000 Price and Discount Recalculation Parameters session is displayed with 'Recalculate Price' and
'Recalculate Discounts' ticked. Click 'OK'
--> This gives a BW error message that begins:
Error: "bis_alloc_mem: sym ' ', i = 0 (tcemm.dll5010.calculate.amounts.in.hc.utc() in object otcemmdll5010)."
SOLUTION DESCRIPTION:
A sales order line can be saved without fatal errors when following the steps as described in the Situation Description.

Solution: 132873
SITUATION IDENTIFIED IN:
"Print Query Data" (ttadv3482m000)
SITUATION DESCRIPTION:
SQL query: a query that requests input-values from the user.
When this query is run, session ttadv3482m000 (Print Query Data) is started, so the user can provide his values.
When information is entered in the From field, this is not defaulted to the matching To field in session Print Query Data
(ttadv3482m000).
SOLUTION DESCRIPTION:
Modified script, information entered by the user in a From field will now become the default value of the matching To
field.

Solution: 132878
SITUATION IDENTIFIED IN:
"Planned Cost Object Transaction" (tppss6800m000)
SITUATION DESCRIPTION:
Planned delivery date is not correct after transferring the planned PRP-purchase order to Order Management or when the
delivery date on the PRP purchase order is changed. It always shows the current date as delivery date.
SOLUTION DESCRIPTION:
The above problem is solved and now delivery date will be correctly filled.

Solution: 132882
SITUATION IDENTIFIED IN:
"Export Translation Solution" (ttpmc1208s000) / "(Check and) Install Solution" (ttpmc2204s000/ttpmc2205s000)
SITUATION DESCRIPTION:
During the export of a PMC translation solution an overflow error was displayed in the bshell/BW messages window,
e.g.:
1 : process 49 - Warning : Overflow: format='99' value='340' (<85>() in object ottpmcdllblang)
This was the case when a menu was exported with not-linked menu field descriptions and for the menu field a sequence
number higher than 99 was used.
This overflow message could also be displayed during the installation of a solution with a menu if the B-language support
was activated. The installation didn't abort, but the description of the menu field was not filled correctly.
SOLUTION DESCRIPTION:
A correct format is used now to hold sequence numbers, which are higher than 99.

Solution: 132885
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
In session "Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000), it is possible to enter duplicate
invoice numbers in the same EBS batch.
SOLUTION DESCRIPTION:
An error message pops up and it is not possible to enter the same invoice again.

Solution: 132887
SITUATION IDENTIFIED IN:
"Generate Invoice by Self-Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
The Purchase variance was booked with the wrong date, when compression was used, even after installation of solution
132701.

SOLUTION DESCRIPTION:
Now, the Transaction entry date is used to create the purchase variance booking in integration.

Solution: 132890
SITUATION IDENTIFIED IN:
"Audit Posting Data for Electronic Bank Statements" (tfcmg5203m000)
SITUATION DESCRIPTION:
On report 'Audited Electronic Bank Statements' the currency description is printed behind 'Amount in HC' instead of
currency code. 'Amounts in HC' for Batch and Total Amount are printed as %.
SOLUTION DESCRIPTION:
Currency code and amounts in Home Currency are printed properly on report 'Audited Electronic Bank Statements'.

Solution: 132896
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
It is not possible to insert the Receipt method of the parent BP in the session "Sales Invoices" if the "Pay-by" Role of the
child BP is not defined.
SOLUTION DESCRIPTION:
It is now possible to insert the receipt method of the parent BP in the session "Sales Invoices" even if the "Pay-by" Role of
the child BP is not defined.

Solution: 132902
SITUATION IDENTIFIED IN:
"Update Receipts by Packing slip" (tfcor2245m000)
SITUATION DESCRIPTION:
Solution 130204 delivered this session, but the form dump was not delivered in languages 1( Dutch ) and 3 ( German ).
SOLUTION DESCRIPTION:
This solution has the form dump in all the relevant languages.

Solution: 132905
SITUATION IDENTIFIED IN:
"Generated Order Advice" (whina3200m000)
SITUATION DESCRIPTION:
Message unclear when generating Order Advice as replenishment if the generation is by Item-Warehouse.
SOLUTION DESCRIPTION:
The warehouse is displayed as part of the generated error message if the message is printed based on Item-Warehouse
data. Otherwise, the message without Warehouse is generated.
In either case, the Warehouse in the Header, which is the central warehouse, is not changed.

Solution: 132907
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved

212722
Descriptions:
- Defect 212722 AFS session hangs when using afs calls in 4GL session
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 132918
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000)
SITUATION DESCRIPTION:
In the session "Process Solutions" (ttpmc2101m000), the description "Check and Install Solutions" was missing in the
specific menu. This was the case if the user language was Dutch or German.
SOLUTION DESCRIPTION:
The specific menu contains now the correct description.

Solution: 132923
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When user changes the currency rate after saving Sales Invoice (before entering lines), the amount in home currency in
Non-finalized Transactions (tfgld102) was not changed.
The invoice rate for an invoice with a "Manually entered rate" is changed in session "Sales Invoices" (tfacr1110s000). If
the difference between the old rate and the new rate is less than the tolerance for the home currency, then the home
currency amount in the Non-finalized transactions was not updated correctly.
SOLUTION DESCRIPTION:
The rates are correctly picked up and the amounts are updated correctly in Non-finalized transactions.

Solution: 132934
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Two or more sales invoices of Child BP are assigned to an unallocated receipt of Parent BP and both Business Partners
belong to different financial groups. Then from the second invoice of Child BP, the system takes wrong control account
for the unallocated receipt.
SOLUTION DESCRIPTION:
The system takes the right control account for booking the unallocated/advanced receipt.
Solution: 132936
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Unable to link a sales invoice directly to a credit note if the due date of the sales invoice is before the document date of the
credit note.
SOLUTION DESCRIPTION:
Able to link a sales invoice directly to a credit note even if the due date of the sales invoice is before the document date of
the credit note.

Solution: 132967
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
It is not possible to cash an amount in Direct Debits that exceeds the invoice balance. Error 'Amount to be cashed exceeds
invoice balance' is given and it is not possible to proceed.
SOLUTION DESCRIPTION:
It possible to cash an amount via Direct Debit, that exceeds the invoice balance. Warning message 'Amount to be cashed
exceeds invoice balance' will be given and a payment different will be posted.
Now the problem is solved.

Solution: 132971
SITUATION IDENTIFIED IN:
"Print Direct Debit Advices" (tfcmg4401m000)
SITUATION DESCRIPTION:
On the report of the Direct Debit Advice, no Business Partner number is printed for the total lines per Business Partner
for amounts in home currency.
SOLUTION DESCRIPTION:
On the report of Direct Debit Advice, the Business Partner number is also printed for total line per Business Partner for
amount in home currency.

Solution: 132980
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
Purchase order is not printed when printing with the option Specific Orders; instead a message " Process Completed "
alone is appearing.
SOLUTION DESCRIPTION:
The purchase order will be printed even with the option Specific Orders.

Solution: 132981
SITUATION IDENTIFIED IN:
"Qualified Demand by Period" (whinr1520m000)
SITUATION DESCRIPTION:
When a production order is registered completed with a negative quantity in session "Report Orders Completed"
(tisfc0520m000), the returned quantity is shown as "Actual Issue" in session "Qualified Demand by Period"
(whinr1520m000).
SOLUTION DESCRIPTION:
Returns of end items to production aren't registered as "Actual Issue" in session "Qualified Demand by Period"
(whinr1520m000).

Solution: 132984
SITUATION IDENTIFIED IN:
"Created Purchase Order / Schedule History - by Item" (tdpur5503m000)
SITUATION DESCRIPTION:
Purchase order amount is not correctly displayed in the home currency when calculated using "Calculate Totals" button
from the specific menu.
Also, when "Refresh" button is pressed, the amount disappears.
SOLUTION DESCRIPTION:
-- Now, when "Calculate Totals" is pressed, the order total shown will be the in first home currency.
-- Total amount & currency will not be changed if "Refresh" button is pressed.

Solution: 132988
SITUATION IDENTIFIED IN:
"Update VRC's" (ttpmc2140m000)
SITUATION DESCRIPTION:
It was possible to connect more than one Update VRC for the same Base VRC to one VRC Combination. This is not
allowed.
VRC Combinations are meant to handle co-requisite dependencies between different Base VRC's (e.g. standard solutions
and localization solutions) and not for updating different Update VRC's with solutions for the same Base VRC's at the
same time.
When PMC was setup in this way, unpredictable errors might occur. One of the symptoms of this setup is that during the
checking of solutions, the solutions keep the status 'Available' and there is no error message in the report why the
solutions could not be installed.
SOLUTION DESCRIPTION:
It is not possible anymore to connect an Update VRC to a VRC combination if another Update VRC for the same Base
VRC is connected to that VRC combination already.

Solution: 132990
SITUATION IDENTIFIED IN:
"Program structure diagram" (ttadv2430m000)
SITUATION DESCRIPTION:
Session "Print Program Structure Diagram" (ttadv2430m000) does not correctly print when the source contains dllusage.
The second print of the same data results in no data within selection
SOLUTION DESCRIPTION:
No the dllusage is handled correctly and the data is printed correctly. Also the second print of the same session.

Solution: 132991
SITUATION IDENTIFIED IN:
"Consignment inventory and usage" (whinh2540m000)
SITUATION DESCRIPTION:
Database MS SQL2000 crashes when duplicate fields are present in an 'order by' clause in combination with a level2
driver in session whinh2540m000 "Consignment inventory and usage"
SOLUTION DESCRIPTION:
Duplicate fields have been removed from 'order by' clause.

Solution: 133002
SITUATION IDENTIFIED IN:
"Sales Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
Enter a menu-item on a Sales Quotation and selecting two list items. When the second line should have a price of zero, the
price of the first item is taken.
This also happens when a Sales Quotation is copied and the price of the second line is changed from zero (as is defined in
the price structure) to a manual price. When option 'Recalculate Prices and Discounts' is checked, still for the second line
the manual entered price is taken.
SOLUTION DESCRIPTION:
When a list item in a menu has price zero, the price on the resulting Sales Quotation Line is also zero.
When copying such a line for which the price is manually changed, the price on the copied Sales Quotation Line is zero
when option 'Recalculate Prices and Discounts' is checked.

Solution: 133003
SITUATION IDENTIFIED IN:
"Solutions" (ttpmc1100m000/ttpmc1500m000)
SITUATION DESCRIPTION:
If you are authorized to maintain descriptions of software components in a standard Baan VRC, but not authorized to
maintain other properties of the components, you could not create PMC solutions to deliver the changed descriptions.
This situation only exists for partners of Baan, who translate the Baan software to other languages. The problem was
introduced in solution 131157.
SOLUTION DESCRIPTION:
To deliver PMC solutions for a standard Baan Base VRC, you don't need the authorization to maintain the standard Baan
software anymore. It is enough to have the authorization to change descriptions of standard Baan components.

Solution: 133006
SITUATION IDENTIFIED IN:
"Global Confirmation of Future Invoices" (cisli2219m000)
SITUATION DESCRIPTION:
When the user tries to confirm "Manual Sales lines" through the session "Global confirmation of Future Invoices", the
lines gets confirmed even when the Invoice-to Business Partner is inactive.
SOLUTION DESCRIPTION:
Now a message is printed in the exception report and also the line does not get confirmed.

Solution: 133015
SITUATION IDENTIFIED IN:
"tfcmg5222m000" (Post EBS)
SITUATION DESCRIPTION:
Not able to complete the job process while posting Electronic Bank Statements batch.
SOLUTION DESCRIPTION:
Posting of Electronic Bank Statements can be executed properly in job mode.

Solution: 133018
SITUATION IDENTIFIED IN:
"Match Orders" (tfacp2541s000)
"Match Receipts" ( tfacp2544s000 )
SITUATION DESCRIPTION:
1. It was not possible to see the Orders / Receipts belonging to the child Business partners of the Invoice from Business
partner mentioned in the Invoice header.
2. A fatal error( Syntax incorrect ) occurs when choosing the Option "Change Order" in the session Match orders.
3.The sorting of the data in the session Match receipts is not correct when choosing to change the Sort by option Via
the View option.
SOLUTION DESCRIPTION:
1.Its possible to view the child business partner belonging to the Invoice from Business partner mentioned in the Invoice
header.
2. The fatal error no longer occurs when choosing the option "Change Order "
3. When changing the sort by option, the data is sorted according to the option chosen by the user.
Notes on additional changes to the session.
Changes in Specific options:
---------------------------------------------
There has been added 4 new Specific options , namely
- Show BP data only
This option is the default when the invoice is not matched and will show only the Order/ receipts belonging to the
invoice from Business partner mentioned in the Invoice header.
- Show Parent BP and its children
This option will display the Order / Receipt data belonging to the Invoice from Business partner of the Invoice header, Its
parent, and the children of this parent business partner.
- Show BP and its children
This option will show all the Orders/ Receipts belonging to the current Invoice from BP, and its children BP.
- Show Parent and child BP data
This option will show the orders / receipts belonging to all the related BP – So the invoice from BP, its parent, the
parents children and the children of the Invoice from BP.
These options will be disabled when,
- Choosing to see only the Matched Orders / receipts using the option "Hide/ Show Matched Order lines.
- Choosing the Change Order Option.
Changes to the specific option "Change Order" / "Change Packing slip Order number"
---------------------------------------------------------------------------------------------------------------------------------------
1. It will not be possible to Enter an order which is not related to the Invoice from Business Partner of the Invoice header.
2. When an order number is mentioned in the Invoice header, and using the Change order option, if the invoice is matched
with a different order number, then the order number mentioned on the Invoice header will be blanked ( filled with spaces
).
What happens when the invoice is already matched ?
-------------------------------------------------------------------------------------
When the Invoice is already matched then when going to the session "Match order" or "Match Receipt" only the matched
order / receipts will be displayed. The user can see the other non matched Orders/ Receipts by the Specific option "Hide
/ Show matched Order line"

Solution: 133019
SITUATION IDENTIFIED IN:
"Match Electronic Bank Statements" (tfcmg5212m000)
SITUATION DESCRIPTION:
- Wrong document was getting matched against the document within the EBS File. This problem is encountered when
the "Transaction Type" has numeric character(s) and when we have similar Transaction Type and Document number.
- A match is made to an incorrect document if the document from the EBS file was already paid.
- On report 'Matched Electronic Bank Statements' the currency description is printed before the amount in Home currency
instead of currency code. Furthermore the 'Total for Batch' and the 'Total Amount' are printed as " % " instead of
amounts.
SOLUTION DESCRIPTION:
- The session matches to the exact document, which was entered in the EBS file.
- On report 'Matched Electronic Bank Statements' the currency code is printed properly before the amounts in Home
currency, the 'Total for Batch' and the 'Total Amount'.

Solution: 133021
SITUATION IDENTIFIED IN:
"Print Specifications Delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
Wrong data is displayed, in the case of "direct delivery" with Multiple Shipments. Besides, the performance of the
session was bad.
SOLUTION DESCRIPTION:
Correct data is displayed now. In addition, the performance of the session is improved.

Solution: 133025
SITUATION IDENTIFIED IN:
"Inventory Transactions by Order" (whinr1511m000)
SITUATION DESCRIPTION:
When searching the Orders in the session "Inventory Transactions by Order" (whinr1511m000) using the Order Type as
'Adjustment/Cycle Count', the 'Adjustment/Cycle Count' Orders are not obtained. Only the Warehouse Orders are
obtained.
SOLUTION DESCRIPTION:
When zooming for Order in the search, 'Adjustment/Cycle Count' order is obtained, when the Order Type is
'Adjustment/Cycle Count'.

Solution: 133036
SITUATION IDENTIFIED IN:
"Availability Type" (tcccp0501m000)
SITUATION DESCRIPTION:
When adding a new Availability Type in Session "Availability Types" (tcccp0501m000), the field Availability Type is
greyed out/disabled.
After a mouse click on Description (tcccp001.dsca) the field 'Availability Type is enabled and data entry is possible
SOLUTION DESCRIPTION:
When adding a new Availability Type in Session "Availability Types" (tcccp0501m000), the field Availability Type is
enabled and data entry is possible.

Solution: 133040
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
When a second report is added to session "Print Remittance Letters" (tfcmg1270m000) the system will ask to select the
required report two times before executing.
SOLUTION DESCRIPTION:
Now, the system will not ask the report twice before executing.

Solution: 133046
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2100s000)
SITUATION DESCRIPTION:
Issue 1:
Label "Reference" is translated in Dutch language as "Contactpersoon" instead of "Referentie" in session
whinh2100s000 "Warehousing Orders".
Issue 2:
Help text for "Returned Quantity" checkbox shows wrong information in session whina2202m000 "Calculate Demand
Forecast by Item".
SOLUTION DESCRIPTION:
Issue 1:
Label has been actualized in Dutch to description "Referentie".
Issue 2:
Help text has been modified from
The Demand Direct Delivery can be taken into account for ...
into
The Returned Quantity can be taken...

Solution: 133062
SITUATION IDENTIFIED IN:
"Copy Purchase Contracts" (tdpur3801m000)
SITUATION DESCRIPTION:
Save defaults is pressed while copying the contract once. Then, if another contract is selected (from tdpur3500m000) and
copied, the previous contract value is displayed in the source contract.
SOLUTION DESCRIPTION:
The selected contract number alone will be displayed. When the session is run from Menubrowser, the saved defaults are
displayed.

Solution: 133075
SITUATION IDENTIFIED IN:
"Installments" (tppin4151s000)
"Advance Payment Requests" (tppin4110s000)
SITUATION DESCRIPTION:
Information about the status of the Triggering Activity and the status of the Charge Element was missing in session
Installments (tppin4151s000). Also the Contract Sub Amount was missing, as well as the Rate and Rate Factor. Beside
this, invoicing a negative Installment with a negative Advance Payment Request (tppin4110s000) showed an incorrect
message.
SOLUTION DESCRIPTION:
All information in session Installments (tppin4151s000) about the Charge Element status, the Triggering Activity status,
the Contract Sub Amount and the Rate and Rate Factor are shown, if applicable.
Session Advance Payment Requests (tppin4110s000) is now able to handle negative amounts linked to a negative
Installment amount.
Note; The amounts of the Installment and the Advance Payment Request should either be both positive or negative.

Solution: 133079
SITUATION IDENTIFIED IN:
"Export Language-Dependent Software Components" (ttadv6230m000)
SITUATION DESCRIPTION:
When exporting Hypertext Info Lines for Help Topics, too many #INFO lines are present in the created File for Texts.
#INFO lines should not be in the File for Texts when there is no hypertext code in the comment line.
SOLUTION DESCRIPTION:
A comment line is now checked stricter: if it does not contain a hypertext code no #INFO line is created.

Solution: 133080
SITUATION IDENTIFIED IN:
"Receipt Lines" (whinh3120s000)
SITUATION DESCRIPTION:
Maintain a Purchase Order and release it to Warehousing. Maintain a warehousing receipt. When doing the receipt, split the
receipt line to two lines, ensuring that the total quantity of both is equal to the total order quantity. The final receipt is
not defaulted as "Yes", even when the total receipt quantity matches with the total order quantity.
SOLUTION DESCRIPTION:
The final receipt flag will be defaulted as "Yes" when the total receipt quantity matches the total order quantity.

Solution: 133082
SITUATION IDENTIFIED IN:
"Purchase Order Headers" (tdpur4100s000)
SITUATION DESCRIPTION:
Cannot change buyer field on a purchase order that has a line existing. Many situations demand that the Buyer is changed
after the Purchase Order is raised.
SOLUTION DESCRIPTION:
The above problem is solved and now, the "Buyer" field will be disabled only if the order (at least one line) is delivered.

Solution: 133083
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b:
134222
Descriptions:
- Defect 134222 AFS stack error when find.data in init.form
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 133085
SITUATION IDENTIFIED IN:
"Assign Unallocated / Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
After assigning unallocated receipts to invoices in session "Assign Unallocated / Advance Receipts to Invoices"
(tfcmg2105s000) the unallocated receipt balance still remains. This happens when there is a change in rate between the
invoice and the unallocated receipt and the invoice is at a lower rate as compared to the unallocated receipt. The
rounding difference is created with the document type "Correction" in table "Open Entries" (tfacr200). The sign
indication of the amount is wrong; hence in session "Invoice to Business Partner Aging Summary" (tfacr2511m000), the
balance is shown.
SOLUTION DESCRIPTION:
The correction document created in table "Open Entries" (tfacr200) is with the correct indication. Hence the amounts
are shown correctly in Aging Summary.

Solution: 133091
SITUATION IDENTIFIED IN:
"Select Device" (ttstpsplopen)
SITUATION DESCRIPTION:
The default font is not defined when using a conversion program different than ttstpconv.
The date/time scheduling can be defined for windows printer but is not working..
SOLUTION DESCRIPTION:
The default font is now defined if any conversion program is defined for a device.
The fields for date/time are disabled when using a windows printer because this functionality is not supported for windows
printer.

Solution: 133102
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
- The field 'project' in session "Sales Order Lines" (tdsls4101s000) is enabled although the parameter 'Project Control
(PCS)' in session "Companies" (tccom0100s0000) is not checked.
- The field 'e-item revision' in the same session is also enabled although the parameter ' Engineering Revisions Active in
Sales' in session "Sales Parameters" (tdsls0100s000) is not checked.
SOLUTION DESCRIPTION:
Both fields are disabled when they should be disabled according to parameter settings

Solution: 133105
SITUATION IDENTIFIED IN:
"Maintain Anticipated Receipts (Details)" (tfcmg2117s000)
SITUATION DESCRIPTION:
In session "Maintain Anticipated Receipts (Details)" it is possible to insert an invoice, which is already paid
completely. Hence after selecting the invoice and changing the defaulted amount from 0, the invoice balance becomes
negative. In Baan ERP this problem occurs only when the balance of the invoice is exactly zero.
SOLUTION DESCRIPTION:
If an already paid invoice is selected in session "Maintain Anticipated Receipts (Details)", error message 'No open balance
amount' comes up and it is not possible to continue further.

Solution: 133111
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Enterprise Unit of Calculation office is not populated in the 'Integration Additions' table when PCS item is used.
SOLUTION DESCRIPTION:
Now the enterprise unit of the calculation office gets filled if PCS item is
used.

Solution: 133112
SITUATION IDENTIFIED IN:
"Backflush hours and materials" (tisfc0220m000)
SITUATION DESCRIPTION:
Manually backflushing materials for production orders without operations do not work.
SOLUTION DESCRIPTION:
Functionality is returned.

Solution: 133116
SITUATION IDENTIFIED IN:
"Global Acceptance of GRNI Reconciliation" (tfacp1237m000)
SITUATION DESCRIPTION:
The flag, accepted, is not checked. When this is not checked, if you run the select values session "tfacp1235m000 -
Select Values for GRNI Reconciliation", any manual entries are deleted.
SOLUTION DESCRIPTION:
The flag, Accepted is checked now. All further processes run correctly now.

Solution: 133119
SITUATION IDENTIFIED IN:
"Print Totals for Customer per Company" (tfacr2434m000)
SITUATION DESCRIPTION:
Customer balance calculated wrongly, if future dated Unallocated Document assigned to Sales Invoice.
SOLUTION DESCRIPTION:
Customer balance calculated correctly. Balances are in accordance to "Print Open Entries"(tfacr2421m000) and "Print
Aging Details"(tfacr2420m000)

Solution: 133120
SITUATION IDENTIFIED IN:
"Project" (tppdm6100s000)
SITUATION DESCRIPTION:
An Enterprise Unit (EU) is always linked to financial Company & all the project related financial transactions are always
posted in the financial company linked to this EU. So, when a EU is changed to one, which has a different financial
Company, it will carry lot of consequences with it. Normal users are not allowed to change a EU with different financial
co. Only Super User can. But if the super user adds a EU with different financial co by mistake, he/she will have no
information about it.
SOLUTION DESCRIPTION:
Now, if a Super User tries to change an Enterprise Unit, linked to a different financial co., a warning message will be
shown.

Solution: 133126
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
The remittance letter is not printed if the total amount for a payment advice is zero (using Checks and Check Master).
SOLUTION DESCRIPTION:
The remittance letter is getting printed even if the total amount is zero for a payment advice.

Solution: 133134
SITUATION IDENTIFIED IN:
"Report Library" (ttstprepdll)
SITUATION DESCRIPTION:
When printing detail text over more then one page where the header contains also a text field then, the text on the second
page only contains 1 line
SOLUTION DESCRIPTION:
Now the text will continue correctly after the page break

Solution: 133139
SITUATION IDENTIFIED IN:
"Service Contract Installments" (cisli2165s000)
SITUATION DESCRIPTION:
When a Service Contract Installment is posted to Central Invoicing, the forecast cost amount was incorrectly posted. The
forecast amount in home currency was also shown incorrectly, i.e. different as in service.
SOLUTION DESCRIPTION:
The forecasted amount in home currency from the Service Contract Installment (tsctm400.fcmt), is posted to the forecasted
cost amount in home currency in central invoicing (cisli265.fcah), no conversion is needed.
Also the forecasted amount in home currency from the Service Contract Installment (tsctm400.fcmt) is posted to the
forecasted cost amount in invoice currency in central invoicing (cisli265.fcai), as conversion the internal rate is used on
the date the installment is posted towards central invoicing.

Solution: 133141
SITUATION IDENTIFIED IN:
"Global Update of Prices via Price Books" (tdpcg0231m000)
SITUATION DESCRIPTION:
It is not possible to update the price when both the effective and expiry dates are filled in the Price Book. When the
global update session is run, the message " No data with in selection " pops up.
The same problem is found out in the similar session " Global Update of Discounts via Price Matrices."
SOLUTION DESCRIPTION:
The problem was because of the reason that the price books that have effective date were not taken in to global update. In
the session, a selection range has been provided for the expiry date. Based on the values in the selection range, the price
books are selected and the price is updated.

Solution: 133145
SITUATION IDENTIFIED IN:
"Print Help Topics" (ttadv1460m000)
SITUATION DESCRIPTION:
Make Job button is missing in Form "Print Help Topics (ttadv1460m000)"
SOLUTION DESCRIPTION:
The button is present now. So we can add the session to Job.

Solution: 133148
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
If the rate type on the Sales Order Header (tdsls4100s000) is changed to a rate type where the currency does not exist
in, the following message is given: "Cannot retrieve local and reporting currency rates for currency XXX, exchange
rate YYY, Invoice to BP ZZZ"
Still the Sales Order Header can be saved and rate 1.000000 is used, which is incorrect.
SOLUTION DESCRIPTION:
If the rate type on the Sales Order Header (tdsls4100s000) is changed to a rate type where the currency does not exist in,
the error message is given and the header cannot be saved. A correct rate type must be entered.

Solution: 133155
SITUATION IDENTIFIED IN:
"Delete Job History" (ttaad5210m000)
SITUATION DESCRIPTION:
When selecting a range for 'Delete Job History' session and zooming in the 'Job From' or 'Job To' fields, the session 'Job
History' comes up with one specific job and all of its history instead a list of all the jobs.
SOLUTION DESCRIPTION:
Now when the user zooms from the fields 'job from' or 'job to', Session 'Job Data' (ttaad5500m000) is started to enable the
user to select values for range of Jobs to be deleted.

Solution: 133160
SITUATION IDENTIFIED IN:
"Sales Statistics Layout Codes" (tdsst0196s000)
SITUATION DESCRIPTION:
The selection check box was not properly updated when selections where entered.
SOLUTION DESCRIPTION:
The layout data will be saved once selections are added. This is to prevent that the selection button is not correctly
updated.

Solution: 133165
SITUATION IDENTIFIED IN:
"Initialize, Roll and Update Scenario" (cprpd4200m000)
SITUATION DESCRIPTION:
When having small capacity requirements defined in the Bill of Critical Capacities, a Fatal Error 205 in cprmp120.rcap
might occur when executing session "Initialize, Roll and Update Scenario"
SOLUTION DESCRIPTION:
The field "Capacity Required" in the table "Rough Capacity Requirements by Plan Period" (cprmp120) can only be
expressed in two decimals.
Capacity requirements less than 0.01 are rounded up to 0.01

Solution: 133166
SITUATION IDENTIFIED IN:
"Generate Invoices by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
1. There is no Invoice printed, which can be sent to the supplier, during the Generate Invoices by Selfbilling
process.
2. The report, which is now printed, some time shows also, those receipts, which are not invoiced, as invoiced. This could
happen when there is an error in invoicing one of the receipt for which an error report is printed, and the previous
receipts which were invoiced have to be rolled back because of this, when choosing the Option compress invoices.
SOLUTION DESCRIPTION:
1. Now an additonal report " Invoice ( Credit Note) " is printed when running the session generate Invoices by
Selfbilling ( tfacp2290m000 ), when the Option "Print Credit Note to Invoice from Business Partner" is chosen.
2. The report "Invoice by Packing Slip", which is printed by the session Generate Invoices by Selfbilling ( tfacp2290m000
), will now print only those receipts which have been actually Invoiced.

Solution: 133169
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000).
SITUATION DESCRIPTION:
Errors occur when releasing Orders to Invoicing, due to an invalid country / tax code combination.
This error is caused by not checking for a valid country / tax code combination when modifying Sales Order Header
information that affects calculation of vat codes (for example: changing the Invoice-to Address (tdsls400.itad)).
SOLUTION DESCRIPTION:
When modifying Sales Order Header information that might affect the country (tdsls401.ccty) / tax code (tdsls401.cvat) on
the Lines, message "Adjust all line tax codes?" pops up.
When choosing "Yes", the country and tax code of all lines are re determined. The system checks whether the combination
of country and vat code is valid.
Non valid combination cannot be saved anymore.

Solution: 133172
SITUATION IDENTIFIED IN:
"Print Business Partners Balance" (tfacp2424m000)
SITUATION DESCRIPTION:
When printing the report the sum total line field 'Payments linked to Invoices' prints the amount.
However, a detailed line of the report field 'Payments linked to Invoices' does not print the amount.
SOLUTION DESCRIPTION:
Because of change in the calculation of the field sum total line the detailed line of the report field 'Payments linked to
Invoices' will print the amount.

Solution: 133176
SITUATION IDENTIFIED IN:
"Release Sales Orders to Invoicing (Batch)" (tdsls4247m000)
SITUATION DESCRIPTION:
When opening session "Release Sales Orders to Invoicing (Batch)" (tdsls4247m000) through the Specific option from
session "Sales Orders" (tdsls4500m000) the session does not open with the selected Sales Order. This happens when
defaults are saved in "Release Sales Order to Invoicing (Batch)". The session always opens with these defaults.
SOLUTION DESCRIPTION:
When opening session "Release Sales Orders to Invoicing (Batch)" (tdsls4247m000) through the Specific option from
session "Sales Orders" (tdsls4500m000) the session does open with the selected Sales Order.
When opening the session from the menu, the saved defaults are shown.

Solution: 133178
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
1. When receiving an EDI invoice for a zero amount, the invoice was not automatically matched.
2. When receiving an EDI invoice for a back order line, the invoice was not automatically matched.
SOLUTION DESCRIPTION:
The program script has been corrected.
1. Now the EDI invoice for a zero amount is being matched correctly.
2. Now the EDI invoice for a back order line is correctly matched if a receipt for the incoming line can be found. The fact
that the incoming purchase order sequence still refers to "0" is ignored.

Solution: 133181
SITUATION IDENTIFIED IN:
"Print Sales Order Line History by Sold-To BP and Item" (tdsls5401m000)
"Print Purchase and Sales Orders by Item" (tdsls4412m000)
SITUATION DESCRIPTION:
Labels on reports are missing in German or Dutch language.
SOLUTION DESCRIPTION:
All labels on the reports are printed correct in all languages.

Solution: 133185
SITUATION IDENTIFIED IN:
"Generate Bills of Critical Capacities" (tirou2230m000)
SITUATION DESCRIPTION:
Capacity required calculated is wrong when the purchased components are used in the generic bills of material, while
generating bills of critical capacities.
SOLUTION DESCRIPTION:
System will calculate the correct capacity required even when the purchased components are used in the generic bills of
material, while generating bills of critical capacities.

Solution: 133190
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Two or more sales invoices of Child BP are assigned to an unallocated receipt of Parent BP and both Business Partners
belong to different financial groups. Then from the second invoice of Child BP, the system takes wrong control account
for the unallocated receipt.
SOLUTION DESCRIPTION:
The system takes the right control account for booking the unallocated/advanced receipt.

Solution: 133193
SITUATION IDENTIFIED IN:
"Service Order Actual Other Costs" (tssoc2141s000)
SITUATION DESCRIPTION:
When cost component is changed in an actual other cost line in "Service Order Actual Other Costs" (tssoc2140s000), the
amounts are reversed and the reversed transactions are correctly updated with the old cost component in "Integration
Transactions by Project / Order" (tfgld4510m000) session. But, the corresponding record in "Maintain Additions to
Integration Transactions" (tfgld415) table has the new cost component instead of the old one.
SOLUTION DESCRIPTION:
The reversed transactions in "Maintain Additions to Integration Transactions" (tfgld415) table are now correctly updated
with the old cost component.

Solution: 133197
SITUATION IDENTIFIED IN:
"Anticipated Payments" (tfcmg2110s000)
"Anticipated Receipts" (tfcmg2111s000)
SITUATION DESCRIPTION:
When entering a new anticipated payment in session "Anticipated Payments" (tfcmg2110s000) or a new anticipated receipt
in session "Anticipated Receipts" (tfcmg2111s000), the default series maintained for the transaction type is not picked up.
Instead the first series maintained comes up.
SOLUTION DESCRIPTION:
The default series maintained in session "Transaction Types" (tfgld1111s000) is picked up when entering a new
anticipated payment or anticipated receipt.

Solution: 133201
SITUATION IDENTIFIED IN:
"Run Global SRP" (tssoc2260m000)
SITUATION DESCRIPTION:
An activity is inserted for a Service Order. A material line is linked to the activity with an Item whose delivery type is
"By Purchase Order". Global SRP is run and system creates the Purchase Order. Now an additional activity is inserted for
the Service Order and the activity line number in the material line is changed to the latest one. On re-running SRP with
"Re-plan" option, system creates unwanted Purchase Orders.
SOLUTION DESCRIPTION:
On re-running Global SRP with "Re-plan" option after modifying the Activity line number in the material line, system
does not create unwanted Purchase Order lines.

Solution: 133203
SITUATION IDENTIFIED IN:
""Print Aging analysis by Invoice-to-business partner" " (tfacr2420m000)
SITUATION DESCRIPTION:
Inconsistent data when option "use Euro instead of EMU" in session "Print Aging analysis by Invoice-to-business partner"
is ticked "ON". Invoices already paid and with zero balance are printed.
SOLUTION DESCRIPTION:
Invoices already paid and with zero balance won't get printed when the option "use Euro instead of EMU" in session
"Print Aging analysis by Invoice-to-business partner" is ticked "ON".

Solution: 133205
SITUATION IDENTIFIED IN:
"Print Specifications Delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
If limited/Small range of Orders selected, report is taking longer time to print. Required to optimize the query to
improve performance.
SOLUTION DESCRIPTION:
Performance improvement comes into picture when a limited/small range of Orders selected.
If the huge/open range of Orders selected then there may not be any change in the performance.

Solution: 133210
SITUATION IDENTIFIED IN:
"Purchase Invoice Correction" (tfacp2110s000)
SITUATION DESCRIPTION:
When a purchase invoice is present with level of tax calculation as "Transaction Line", then it is no longer possible to
make and purchase invoice corrections to this invoice with session "Purchase Invoice Corrections" (tfacp2110s000).
SOLUTION DESCRIPTION:
For purchase invoice with the level of tax calculation is "Transaction Line" but with no tax transactions present, then it is
possible to change the supplier or the invoice amount. If there are tax transactions present at the transaction line level, then
it is still not possible to correct the purchase invoice.

Solution: 133212
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Payments to Invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
In case of tax code with zero percentage the net and the gross advance payment ledger accounts are not contra posted
after the assignment of the advance payment to the invoice.
SOLUTION DESCRIPTION:
The ledger account of the net advance payment and the ledger account of the gross advance payment are contra posted
after the assignment.

Solution: 133216
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When zooming to session "Invoiced Sales Orders - by Sold-to BP and Item" (tdsls5502m000):
1. No records are displayed in browse, even when for the combination of Sold-to BP, Proj, Item turnover records do exist.
When a Sales Order has been (partially) released to Invoicing and the order has been processed, turnover records are
created in "Sales Order Line History" (tdsls451).table. These records should be shown when zooming from "Sales Order
Lines" (tdsls401.pric).
2. No return value is entered into the field after zooming took place.
SOLUTION DESCRIPTION:
When zooming to session tdsls5502m000, the browse list shows turnover records of the same combination of Sold-to BP,
Proj, Item as mentioned on the Sales Order Line one is zooming from.
When selecting a record, the value of the zoom-field is properly filled with the value chosen from the browse list.

Solution: 133220
SITUATION IDENTIFIED IN:
"Customer Balances" (tfacr2424m000)
SITUATION DESCRIPTION:
Amounts are shown with a negative sign under the description "Total Balance for Business Partners with Balance <0". >
Negative sign should not be shown as the description itself clearly indicates that the amounts shown are less than zero.
SOLUTION DESCRIPTION:
Amounts are shown without a negative sign under the description "Total Balance for Business Partners with Balance <0". >

Solution: 133221
SITUATION IDENTIFIED IN:
"Compose Payments" (tfcmg1240m000)
SITUATION DESCRIPTION:
Fatal error: tfcmg101.refr index 1 out of dims [1] 30. Cannot continue in tfcmg1240m000 (write.blocked.payment)
appears when a payment batch with sub-contracting invoice is processed.
SOLUTION DESCRIPTION:
When a payment batch with sub-contracting invoice is processed, fatal error does not occur anymore.

Solution: 133224
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
The requirement for a sales order is fulfilled by issuing goods from stock points with different inventory dates. If these
goods are returned, the inventory date of the receipt lines is not correct.
If the outbound priority of the item is LIFO, the latest (highest) inventory date is found and assumed to be the original
inventory date. If the outbound priority is FIFO, the application searches for the lowest inventory date.
In both situations, one inventory date is correct, but the others are not.
SOLUTION DESCRIPTION:
Now always the correct inventory date is assigned to a returned goods.

Solution: 133227
SITUATION IDENTIFIED IN:
"EBOM Copy Data" (tiedm2510m000)
SITUATION DESCRIPTION:
When finalizing engineering data to production from the session "EBOM Copy Data (tiedm2510m000)", the system give
the fatal error 100.
SOLUTION DESCRIPTION:
The problem occurred when the EBOM Copy Method was changed FROM "Non-Project Item to Project Item" TO "EBOM to
PBOM Only". The system will allow finalizing the engineering data.

Solution: 133229
SITUATION IDENTIFIED IN:
"Print Registered and Matched Purchase Invoices" (tfacp1433m000)
SITUATION DESCRIPTION:
Session "Print Registered and Matched Purchase Invoices "tfacp1433m000" is not picking a Journal entry made in the
correction period.
SOLUTION DESCRIPTION:
The correction period is taken into account now.

Solution: 133233
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Specifications" (tfacp1432m000)
SITUATION DESCRIPTION:
Fatal error, "Index out of dims", is generated when the currency system is dependent.
SOLUTION DESCRIPTION:
Because of the position of the home currency is taken in account the error "Index out of dims" is no longer generated.

Solution: 133243
SITUATION IDENTIFIED IN:
"Connect Components to PMC Solution" (ttpmc1221m000)
SITUATION DESCRIPTION:
If you use the option 'Next Solution Number' for handling the exceeding of the maximum number of components,
sometimes the next solution cannot be generated.
This is the case if the solution code contains a hyphen before the numeric part, or the numeric part starts with (a) leading
zero(s).
Examples:
- For SOL-100, SOL-001 and SOL001 no next solution was generated.
- For SOL100 one or more next solutions were generated.
SOLUTION DESCRIPTION:
Now, next solutions are generated correctly when the solution code ends with a numeric part. Note: when the solution
code does not end with a numeric part, you cannot select the option 'Next Solution Number'.

Solution: 133246
SITUATION IDENTIFIED IN:
"Update sales statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
Cost prices get doubled when the sales statistics are partially updated after sales order headers, which have been
processed, are modified.
SOLUTION DESCRIPTION:
The cost price amount was not properly calculated for turnovers. This was due to a check, which had been removed in order
to get the cost price amount calculated for all record types (intake, turnover and cancellations).
Some extra checks have been added as well, to prevent that the cost amount is wrongly calculated for return orders, since
in this case the cost amount will be negative.

Solution: 133249
SITUATION IDENTIFIED IN:
"Cancel Production Order" (tisfc0203m000)
"Initiate Inventory Issue" (tisfc0207m000)
"Easy Warehousing Order Entry" (whinh2202m000)
SITUATION DESCRIPTION:
1) Lot tracking link not created for a production issue of an item/lot if the item has 'Outbound Priority' as other than
FIFO in "Item Warehousing Data" (whwmd4500m000) and lot type is "By Unit".
This occurs, if the item/lot was previously issued to a production order and that production order was cancelled
subsequently.
2) Performance problem in some sessions like "Initiate Inventory Issue" (tisfc0207m000) and "Easy Warehousing
Order Entry" (whinh2202m000)
SOLUTION DESCRIPTION:
1) The lot-tracking link is created for production issue correctly.
2) Performance is improved in the sessions mentioned above.

Solution: 133262
SITUATION IDENTIFIED IN:
"Components by Solution" (ttpmc1120s000)
SITUATION DESCRIPTION:
After you installed solution 133264 or a newer solution for the standard program (ttstpstandard), it
could be that you were not able anymore to add a component to a PMC solution. After you pressed the insert-button in
the overview session "Components by Solution" (ttpmc1520m000), the detail screen was shown with some data, but you
could not enter new data.
This was the case if no components were connected to the solution yet and the first solution in the Solution table had status
'Released'. Because of this status, the insert action was forbidden. In older versions of the standard program it was still
possible to continue, but this has been fixed in the standard program.
SOLUTION DESCRIPTION:
To determine whether you are allowed to add components to a solution, the correct solution is checked now.

Solution: 133264
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b

134313, 134536, 134653
Descriptions:
- Defect 134313 When field changed executed to often for segmented field on editable grid
- Defect 134536 Column freeze for form with segmented fields fails.
- Defect 134653 Segmented fields on editable grid not handled correctly
- Internal AFS field not allowed given to often. caused by fix 212722
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 133272
SITUATION IDENTIFIED IN:
"Match Receipts" (tfacp2544m000)
SITUATION DESCRIPTION:
The starting of the session is too slow.
SOLUTION DESCRIPTION:
Now the performance of the session has been improved.
Solution: 133273
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Invoice date is empty in 'Sales Listing' when Bilateral or Triangular Invoicing is done.
SOLUTION DESCRIPTION:
Now the date is correctly filled.

Solution: 133284
SITUATION IDENTIFIED IN:
"Print Registered Invoices " (tfacp1433m000)
SITUATION DESCRIPTION:
When printing registered and matched invoices transaction lines with zero amounts are also included.
SOLUTION DESCRIPTION:
After installing this solution transaction lines with zero amounts are not printed anymore.

Solution: 133296
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
"Transfer Purchase Order Advice" (whina3212m000)
"Purchase Order Lines Overview" (tdpur4501m500)
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1) There is a direct delivery sales order line created with a PCS project. Generation of purchase order for this direct
delivery sales order is not possible as the system gives the error report "Standard items not allowed for this project."
2) All the lines in the display session "Purchase Order Lines Overview" (tdpur4501m500) display the activity as 'Awaiting
Shipment', when the last line of the form is a return order. In reality for the orders lines with a positive quantity, the
activity should be displayed as 'Awaiting Receipts'
3) When a new purchase order line is created, a BW error "Unknown form field 'addnl.cost.l'" pops up.
4) When a TP project is entered in the "Purchase Order Line" (tdpur4101s000), the 'Warehouse' field is not defaulted to the
line even when the default warehouse is eligible for the project.
5) A purchase order line is created with 'Vendor Rating' as YES. Then the order line is received in warehousing. In the
mean time, the default value of the 'Vendor Rating' field is changed for the Buy-from Business partner and the
Ship-from Business partner. Now, opening the "Purchase Order Line" (tdpur4101s000) displays the Vendor Rating as
NO.
6) When the "Purchase Order Lines" (tdpur4501m000) is reached after creating a new header, the single occurrence
session "Purchase Order Line" (tdpur4101s000) does not pop up automatically.
7) A purchase order line is partially received with the flag 'Final Receipt' as YES. The back order line is generated
automatically. The user cancelled the generated back order and then the received quantity is approved fully. This action
creates the back order lines once again, though the user has cancelled them.
8) While entering a ledger account with Integration Indicator 'PCS project', the system does not block the user using such
a ledger account
SOLUTION DESCRIPTION:
1) Generation of purchase order line is possible and the system does not give any error report.
2) The activity of the order line is properly displayed in "Purchase Order Lines Overview" (tdpur4501m500) depending on
whether the line is to be received or shipped.
3) The BW error "Unknown form field 'addnl.cost.l'" does not pop up anymore.
4) The default warehouse entered in the purchase order header is defaulted to the purchase order line if it is valid for TP
project.
5) The value of the field 'Vendor Rating' does not change after the order is linked to a receipt.
6) When the user comes to the purchase order lines after creating a new header, the single occurrence session "Purchase
Order Line" (tdpur4101s000) pops up automatically.
7) Approval of the purchase order receipts does not create the back order again that was cancelled earlier.
8) The user is not allowed to enter the ledger account with Integration Indicator 'PCS project' in the purchase order line
for a Cost item

Solution: 133300
SITUATION IDENTIFIED IN:
"Service Order Activities" (tssoc2110m000)
SITUATION DESCRIPTION:
When releasing a Service Order Activity that is added to an already Service Order, the status remains "Free" and the option
to release has been greyed out. So, it is not possible anymore to release the activity at all.
The error message on the report stating that an Employee does not have the required or desired Skills, only shows the
code of the Employee.
Please, include the name of the Employee as well for clarification.
SOLUTION DESCRIPTION:
A Service Order Activity that is added to an already Service Order can be released without any problems.
The name of the Employee is added on the error report.

Solution: 133301
SITUATION IDENTIFIED IN:
"Import Version Dump" (tgbrg1245m000)
SITUATION DESCRIPTION:
When we have our version imported in English and then afterwards import in Dutch, then we have lost the English texts.
SOLUTION DESCRIPTION:
The import session did not take the multi-language side of texts correct into account.
The session is changed and now a multi-language import is possible.
For that you need to check the "overwrite" option with the import of the second language.

Solution: 133303
SITUATION IDENTIFIED IN:
"Maintain Posting data For Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
When a journal posting is created to a ledger account with integration indicator to 'tp' project, then after filling the lines
in 'tp' session it cannot be saved due to error message " the posting period is not correct".
SOLUTION DESCRIPTION:
No more the error message "the posting period is not correct" will be displayed.

Solution: 133304
SITUATION IDENTIFIED IN:
"Availability Check for Tools" (titrp0213m000)
SITUATION DESCRIPTION:
There were some queries that had duplicate fields in the 'Order by' clause. This had very serious problems with the
database MS SQL2000.
SOLUTION DESCRIPTION:
All the relevant queries are corrected.

Solution: 133307
SITUATION IDENTIFIED IN:
"Print specifications delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
In the session, it is not possible to select and print the report for a range of PCS-Projects.
SOLUTION DESCRIPTION:
It is now possible to select and print the report for a range of PCS-Projects.

Solution: 133309
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
When reprinting Remittance Letters (tfcmg1270m000), the payment date is defaulted always with the current date and not
with the payment date of the batch.
SOLUTION DESCRIPTION:
When reprinting Remittance Letters, the payment date is defaulted with the payment date of the payment batch. During
processing a payment batch, the payment date for Remittance Letters will be defaulted with the current date.

Solution: 133315
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
When changing the start date of a production order with no operations and the planning method is backwards
the entered start date and not the recalculated start date is used for the delivery date of the components.
SOLUTION DESCRIPTION:
When changing the start date for a production order with the planning method 'backward' the start date is recalculated
based on the end date. After updating the production order with the correct start date the planned inventory transactions
are updated.

Solution: 133318
SITUATION IDENTIFIED IN:
"Approvals" (whinh3522m000)
SITUATION DESCRIPTION:
Items with different units (conversion factor) remain stock when transferring it from inspection to bulk location causing
corrupt inventory.
Problem occurs only in very specific situations (see following example)
- item with conversion factor: lbs * 0,63744 = mk.
- a quantity of 9.4700 lbs is purchased
- a quantity of 9.0000 lbs is received and confirmed
- a quantity of 5.7030 mk is approved
When inbound is completed, 0.001 mk is still left on inspection location.
SOLUTION DESCRIPTION:
Modifications have been included to avoid the cause of corrupted stock after inspection.

Solution: 133320
SITUATION IDENTIFIED IN:
"Change Language" (tttxt2210s000)
SITUATION DESCRIPTION:
When the text editor is started from session ttaad4500 (General Table Display), in session "Change Language" a switch to
another language can be made. When a language, which does not yet contain a text, is chosen, a new record is created in
table tttxt002 (Language Dependent Text Data).
SOLUTION DESCRIPTION:
When "Change Language" is done from the text editor in read only mode no new records will be added to table tttxt002
(Language Dependent Text Data).

Solution: 133321
SITUATION IDENTIFIED IN:
"Maintain Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
When increasing the Production Order Quantity after the release of the production order, extra Outbound Lines (with
Sequence Numbers > 1) are created. For these outbound order lines, Direct Initiate Inventory Issue does not happen,
although this Flag is selected. This was because the outbound order lines were not activated after they were generated.
SOLUTION DESCRIPTION:
When the production order quantity is increased, for the extra material to be issued Direct Process Outbound happens if
the flag is checked and also the outbound order line is not blocked.

Solution: 133327
SITUATION IDENTIFIED IN:
"Match Purchase Order Lines" (tfacp2541m000)
SITUATION DESCRIPTION:
If an orderline is entered for an order quantity of zero then when the order is matched and unmatched again, the totally
matched flag of the order is still "totally matched", which is not correct.
SOLUTION DESCRIPTION:
Now also for orders with a quantity of zero the totally matched flag is determined correctly.

Solution: 133333
SITUATION IDENTIFIED IN:
"Delete Hours Accounting History" (tssoc8220m000)
SITUATION DESCRIPTION:
1. It is not possible to delete the hours accounting history. (tssoc8520m000)

2. When deleting calls with session "Delete Call History" (tsclm8210m000) the Call Transaction Log (tsclm8580m000) is
not cleared
SOLUTION DESCRIPTION:
1. A new session is available in the Service Control - History menu. The session is called "Delete Hours Accounting
History" (tssoc8220m000). In the session a range can be filled in. The Hours Accounting History which is within the
entered range and which is not service order related is deleted when this session is run. When the checkbox 'Process
Report' is checked a report with the deleted hours is shown.
Service order related hours are deleted with session "Delete Service Order History" (tssoc8250m000).
2. When running session "Delete Call History" (tssoc8210m000) the call transaction log for the calls within the range is
also deleted.

Solution: 133334
SITUATION IDENTIFIED IN:
"Report Orders Complete" (tisfc0120s000)
SITUATION DESCRIPTION:
If less than ordered quantity is completed in "Report orders completed"(tisfc0120s000), then the remaining quantity is
shown as 'Planned Receipt" line of the end item in "Planned Inventory transaction by order"(whinp1501m000).
SOLUTION DESCRIPTION:
If less than ordered quantity is completed in "Report orders completed"(tisfc0120s000) and if the order is completed
then no lines will remain in "Planned inventory transaction by order"(whinp1501m000).

Solution: 133335
SITUATION IDENTIFIED IN:
"Transactions Cash Management" (tfcmg2120s000)
SITUATION DESCRIPTION:
On the 2nd transaction line within session 'Transactions Cash Management' (tfcmg2120s000), the tax amount of the previous
record is defaulted in case a tax code with zero percentage is used.
SOLUTION DESCRIPTION:
Tax amount is defaulted correctly when using a tax code with zero percentage. Further more it is possible to modify the
defaulted zero amount after saving the transaction.

Solution: 133394
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When running "Simulate Orders" for a Multisite Scenario, we cannot perform a net change run. (Checkbox is disabled.)
A net change run is only allowed for the Actual Scenario, but a Multisite Scenario itself cannot be an Actual Scenario.
SOLUTION DESCRIPTION:
For a 'valid' Multisite Scenario, a net change run is allowed.
A valid Multisite Scenario has at least 2 Sites and all Sites are set with Actual Scenario as defined in "Plan Sites"
(cprpd4140m000)

Solution: 133396
SITUATION IDENTIFIED IN:
"Print Element-budget structure " (tpptc1409m000)
SITUATION DESCRIPTION:
1. If the given element has child elements, the system starts reading from the next level and prints from that level. The
given element is never printed.
2. If the given element has no child elements, i.e. if it is at the bottom of the structure, the budget structure of the
element is not printed. A message "No data within selection" comes up.
SOLUTION DESCRIPTION:
Now, for the indicated element if it has child elements, then it's budget lines will be printed and for the rest of the
structure element details as well as budget structure will be printed.
If the indicated element is bottom most element in the structure then also only the budget lines will be printed. But, for
this element if the option of "print budget lines" is not checked, then the message "No data within selection" will be
given.

Solution: 133405
SITUATION IDENTIFIED IN:
"Print Specifications Delivered not yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
The report of session tfacr1432m000 will compare the Sales Invoice amounts with the Sales Issue amounts. For closed
Sales Orders no difference should exist while in practice in some situations an unexpected difference may occur.
SOLUTION DESCRIPTION:
A correction program has been developed to correct differences between the Sales Invoice amounts and the Sales Issue
amounts. By inserting financial integration transactions this difference is cleared.
Furthermore the COGS amounts stored on the Sales Order Line, Sales Order History Line and the Sales Order Invoice
Line are updated.
An option is available to execute this correction program in test mode. In test mode no actual table updates will be
performed. Before the correction program is executed in update mode the output reported in test mode should be
carefully analyzed.
Financial integration origins (TROR) and financial integrations types (FITR) considered by this correction program are:
- Sales / General Cost
- Sales / Direct Delivery
- Sales / Issue
- Sales / Issue (Invoiced)
- Warehousing Consignment / Issue
- Warehousing Consignment / Issue (Invoiced)
- Service / Approved for Invoicing
- Sales Invoicing (Sales) / COGS (material)
- Sales Invoicing (Sales) / COGS (operation)
- Sales Invoicing (Sales) / COGS (surcharge)
- Sales Invoicing (Sales) / COGS (general)
- Sales Invoicing (Service) / COGS (material)
- Sales Invoicing (Service) / COGS (operation)
- Sales Invoicing (Service) / COGS (surcharge)
- Sales Invoicing (Service) / COGS (general)
Several options are available when executing the correction program:
Fiscal Year/Period:
When left empty the fiscal year and period is determined based on the original transaction date of the corrected
transaction. In case the fiscal year and period are closed the transaction will be booked into the next open period based
on the parameter "Posting to next open period allowed" (tfgld4150s000) The user can overrule the automatic determination
of the fiscal year and period by filling this field on the form. Only an open fiscal year and period can be chosen.
Reporting Year/Period:
Logic identical to fiscal year/period field
Tolerance:
The allowed tolerance for the difference between the issue and COGS amounts
Correct only when difference on Specification Delivered not yet invoiced:
When this option is set no financial integration transactions will be inserted when there is no difference reported by
tfacr1432m000 on a certain interim account even though there might be a difference between the issue/COGS amount
stored in logistics and finance.
Consider Delivered:
When this option is not selected a possible difference between the issue amount in finance and logistics is not corrected.
Consider Invoiced:
When this option is not selected a possible difference between the COGS amount in finance and logistics is not corrected
Update mode:
Determines whether this correction program is executed in test or update mode
Currency:
The currency in which the found differences should be reported. In an Dependent or Single currency system this will
always be the reference currency. The "rotate currency" button is only enabled in an Independent currency system, which
will allow the user to rotate between the different defined home currencies.
Some things have to be taken care of when executing this correction program:
1) Execution in Job mode
When executing the correction program in Job mode care has to be taken when selecting a device of type 'file' (when
selecting an actual printer device the issue described below is not applicable). This is because the correction program will
report the corrected data in two separate reports, while when running in Job mode only one output file can be specified. To
prevent both reports do overwrite each other a device of type 'append to file' has to be chosen. The second report output
will then be appended to the first report output in the same output file.
2) Archiving
Once the sales order history is archived this program is not able to correct the financial transactions anymore. Archived
Sales Order history lines will just not be considered.
The inventory transactions stored in Warehousing are also needed by this correction program and can be archived as well. In
case an issue/receipt is selected (as it still exists in the sales order history) for correction while the transaction date Is
before the last archiving date a message will be displayed and the correction is skipped.
Furthermore the financial integration transactions can have been archived which are needed to be able to correct as well.
Since its not possible to determine whether a certain financial integration transaction is just missing or archived care has
to be taken with this scenario as the correction program is not capable of preventing unnecessary insertion of archived
transactions. So incase the correction program inserts integration transactions before the last archive action those orders
should be skipped manually.

Solution: 133407
SITUATION IDENTIFIED IN:
"Audit Payment" (tfcmg1255m000)
SITUATION DESCRIPTION:
Error message "Payment method cannot be used: different currencies" is displayed on the error report of 'Audit
Payments' (tfcmg1255m000) although the payment currency and the currency of the payment method are the same.
SOLUTION DESCRIPTION:
In case the payment currency is equal to the currency of the payment method, no error message is displayed on the error
report of 'Audit Payments'.

Solution: 133421
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
Add a return sales order line to an order by using the "Select Orig. Lines" button on the Sales Order Header
(tdsls4100s000). After selecting one or more order lines, these are copied to the order. The Execution Mode of the used
order type is 'Automatic'. When closing the order, the order is not automatically processed.
SOLUTION DESCRIPTION:
When adding sales order lines to a return order by using the "Select Orig. Lines" the order is processed according to the
Execution Mode of the order type.

Solution: 133434
SITUATION IDENTIFIED IN:
"Element budget" (tpptc1810m000)
SITUATION DESCRIPTION:
Item description field on the session "item project data" should be made available for and easy search.
SOLUTION DESCRIPTION:
Now the field "item description" is made available for an easy identification of the item.

Solution: 133435
SITUATION IDENTIFIED IN:
"Run Global SRP" (tssoc2260m000)
SITUATION DESCRIPTION:
In a Subcontracting activity of a Service Order, a Cost Item is present. This Item is present in a Purchase Contract and
its Cost Price is a non-zero value. When Global SRP is run, system creates Purchase Orders for this Item, but the Purchase
Contract is not linked and the Price is also not picked from the Contract.
SOLUTION DESCRIPTION:
The defaulting of Estimated Cost Price in the Service "Order Other Costs" is set to zero. User can insert his own price. If
user defines his price, that price will be used in the Purchase Order created for Subcontracting Activity. If user doesn't
define a price, the Purchase Order line Price will be picked from Pricing structure (which includes linking of Purchase
Contracts, if any, and picking Contract Price) and will be updated back in the Service Estimation Line.

Solution: 133440
SITUATION IDENTIFIED IN:
"Table Relations (Import)" (tu (da)xch0121s000)
SITUATION DESCRIPTION:
Condition was always created, even if user at the last moment decided not to add any text and cancel the action. Such
non-linked empty condition leads to confusion.
SOLUTION DESCRIPTION:
New functionality implemented: if user presses Create/Edit button but then does not create any text now there is a question
pop up: "Condition script is empty, use empty condition?" In case user says No, condition is not created (in case Yes -
created condition remains without text, as it was before, but user is aware of it).

Solution: 133445
SITUATION IDENTIFIED IN:
"Maintain Program Scripts" (ttadv2130m000)
SITUATION DESCRIPTION:
A program script/library can be deleted in Baan, even when the authorization settings on the operating system do not allow
that the files are deleted by the user.
This was partly solved by solution 131737, but when the directory were the files were stored was closed for reading, the
program script/library was still deleted in Baan. (On UNIX: directory authorization = 700)
SOLUTION DESCRIPTION:
When the directory where the files are stored is closed for reading, an error message is displayed.
message ttadv2130o : Error reading file %s, error %d
The delete action will fail: the program script/library is not deleted.

Solution: 133463
SITUATION IDENTIFIED IN:
"Link invoices to credit notes II" (tfacr2121m000)
SITUATION DESCRIPTION:
When a sales invoice is created with child business partner whose Pay-by role is not defined, a sales credit note is
created with parent business partner. When this credit note is assigned to invoice an error message "No invoices found for
this business partner" pops up.
SOLUTION DESCRIPTION:
Its possible to apply credit notes to invoices of a child business partner, When a sales invoice is created with child
business partner and a sales credit note with parent business partner, when this credit note is assigned to invoice, no
error message is showing

Solution: 133464
SITUATION IDENTIFIED IN:
"Reconciliation of Receipts/Payments " (tfcmg2103s000)
SITUATION DESCRIPTION:
When re-entering session "Reconciliation of Receipts/Payments " (tfcmg2103s000) after the reconciliation is done the
"Amount in Home Currency" has been changed.
SOLUTION DESCRIPTION:
"Amount in Home Currency" is not changed when re-entering session "Reconciliation of Receipts/Payments " after
reconciliation.

Solution: 133465
SITUATION IDENTIFIED IN:
"Activity budget(material)" (tpptc2110s000)
SITUATION DESCRIPTION:
Data gets lost while switching between forms without saving
SOLUTION DESCRIPTION:
The values of dates and schedule link are now retained even while switching between the forms.

Solution: 133467
SITUATION IDENTIFIED IN:
"Correct Incorrect Contract Data" (tdcor0013m000)
SITUATION DESCRIPTION:
When running the correction program in update mode, in some cases the program gets into a loop. The only way to end the
program is to kill the process.
SOLUTION DESCRIPTION:
When running the correction program in update mode, sales contracts quantities are corrected and sales contract history
is counter booked without getting into a loop.

Solution: 133474
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000)
SITUATION DESCRIPTION:
When a Translation Solution was installed, wrong post-installation instructions were printed. This applied to the "Check to
Install", "Check and Install", and "Install" functionality.
On the report an instruction was printed to run session ttadv5215m000 (Convert to Runtime Data Dictionary) for a domain
or a table. However, when you executed this session, nothing happened, so you still used the old or not translated
descriptions. The Convert to Runtime session didn't process the components, because during installation of the solution
no indicators were written, which the Convert to Runtime session needs.
Besides this, also instructions were printed for tables and sessions, but for translation solutions it is not necessary to
convert these component type to runtime.
SOLUTION DESCRIPTION:
When a Translation Solution is installed, the correct indicators are written for domains. The Convert to Runtime session
will now process this indicator. Instructions for tables and sessions will no longer be printed.

Solution: 133475
SITUATION IDENTIFIED IN:
"copy element budget data" (tpptc1245m0000)
SITUATION DESCRIPTION:
Label field length for "project" is not enough for translation to other languages.
SOLUTION DESCRIPTION:
The label field length of "project" is increased to 9 from 7 to avoid problems while translating to other languages.

Solution: 133476
SITUATION IDENTIFIED IN:
"Select Invoices for Reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
"Adv. anticipated receipt" not selected for reminding when ACR Parameter "Action on 0 or Negative amount" is "Do not
send".
SOLUTION DESCRIPTION:
"Adv. anticipated receipt" are selected for reminding when ACR Parameter "Action on 0 or Negative amount" is "Do not
send".

Solution: 133479
SITUATION IDENTIFIED IN:
"Release to Warehousing" (tdpur4246m000)
SITUATION DESCRIPTION:
When releasing a item of type 'Cost' or 'Service' to warehousing with a project warehouse the message "Advice Shortage of
## for item ##" is returned due which the release fails.
SOLUTION DESCRIPTION:
The Baan system tried to update the project inventory (whinh2545m000) for item of type 'Cost' and 'Service'. As no
inventory is kept for these kinds of items the mentioned error message was returned. Now the system will skip the update of
the project inventory for items of type 'Cost' or 'Service'.

Solution: 133492
SITUATION IDENTIFIED IN:
"Global Acceptance of GRNI Reconciliation" (tfacp1237m000)
SITUATION DESCRIPTION:
The flag, accepted, is not checked. When this is not checked, if you run the select values session "tfacp1235m000 -
Select Values for GRNI Reconciliation", any manual entries are deleted.
SOLUTION DESCRIPTION:
The flag, Accepted is checked now. All further processes run correctly now.

Solution: 133493
SITUATION IDENTIFIED IN:
"Print Specifications Delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
If transaction origin is 'sales (invoicing)' or if sales order has sequence number then status information not reported.
SOLUTION DESCRIPTION:

Now, status information is displayed in all cases.

Solution: 133497
SITUATION IDENTIFIED IN:
"Delete forms/menu's/reports that don't have a source" (ttcor9211m000)
SITUATION DESCRIPTION:
When running the session on the AS400 platform, often messages appeared that the session was not able to remove files.
However, the concerning files were not present at all.
SOLUTION DESCRIPTION:
Problem has been solved. The AS400 is returning a different error value for missing files compared to other platforms. Due
to this incorrect messages were created. The session is not taking care of the error value that is generated on the AS400
platforms.

Solution: 133511
SITUATION IDENTIFIED IN:
"Calculate Cost Prices by Project" (tipcs3250m000)
SITUATION DESCRIPTION:
When service orders are related to a PCS project then the Cost of Goods Sold (COGS ) are made for the Sales Invoicing
(Service) but also for the PCS project.
SOLUTION DESCRIPTION:
When service orders are related to a PCS project then the Cost of Goods Sold (COGS ) are made only for the Sales
Invoicing (Service) transaction.

Solution: 133534
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
When the Shipping Constraint on the Sales Order Header (tdsls4100s000) is changed and the question 'Adjust Delivery Dates
on Lines?' is answered with 'yes', the delivery dates on the Sales Order Lines are not adjusted.
SOLUTION DESCRIPTION:
When following the procedure as described above, the delivery dates on the lines are changed to the value of the delivery
date of the Sales Order Header.

Solution: 133537
SITUATION IDENTIFIED IN:
"Report Production Orders Completed From Production Schedules" (tirpt1102s000)
SITUATION DESCRIPTION:
When reporting production orders completed from Production Schedules only one lot allowed when reporting production
orders completed from schedules
SOLUTION DESCRIPTION:
When reporting production orders completed from Production Schedules it is possible to use a different LOT numbers
per completion.

Solution: 133541
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
While calculating the cost price for an item range, the system takes long time to compute the cost price.
SOLUTION DESCRIPTION:
The performance of the session is increased, by avoiding the recalculation of already calculated items through the cost
price indicator.

Solution: 133547
SITUATION IDENTIFIED IN:
"Copy Company Data" (tccom0214m000)
SITUATION DESCRIPTION:
Session "Copy Company Data" (tccom0214m000) does not change the company numbers in tables of the Enterprise
Decision Manager.
SOLUTION DESCRIPTION:
Added functionality to session "Copy Company Data" to handle dumps of the tables of Enterprise Decision Manager.
Table fields that are of domain tgedm.comp will receive a new value.

Solution: 133550
SITUATION IDENTIFIED IN:
"Calculate cost prices by Project" (tipcs3250m000)
SITUATION DESCRIPTION:
When cost price of a project is calculated, system generates an error report with message "Cost price of the item is zero",
even if the calculated cost price of customized item is non-zero.
SOLUTION DESCRIPTION:
If the calculated cost price of the customized item is zero, then only system generates an error report with message "Cost
price of the item is zero".

Solution: 133551
SITUATION IDENTIFIED IN:
"EBOM Copy Data" (tiedm1220m000)
SITUATION DESCRIPTION:
If an Engineering Item component has order policy anonymous and when we copy the main Engineering Item and
Engineering BOM, the component's copy method is shown as "Non-project item to project item" and then after
finalizing, this item becomes Customized which is wrong. While we have the order policy as Anonymous, the E item
should not become customized even if the EDM parameter read as "Customize copied item".
SOLUTION DESCRIPTION:
While identifying the EBOM copy method for a project item, if there exists a relation with a standard item, then
based on the parameter "Customized Copied Item" and Order Policy, the system will determine whether to customize
the item or not. If the order policy is "Anonymous" and the parameter "Customize Copied Item" reads YES, the
EBOM Copy Method will be "EBOM to PBOM" only.

Solution: 133554
SITUATION IDENTIFIED IN:
"Hours Accounting Transaction" (tphrs1100m000)
SITUATION DESCRIPTION:
When inserting a record, extension is defaulted if it is linked to the given Element / Activity. But, if the Element /
Activity is changed to some other value; the changed extension is not fetched. Also, if there is no extension linked to the
Element / Activity, the earlier extension is defaulted.
SOLUTION DESCRIPTION:
Now, an extension linked to the given Element or Activity will always be defaulted while adding a record. And, if there is
no extension linked, the field will remain blank without taking previous records value.

Solution: 133562
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000) / "Process Patches" (ttpmc2102m000)
SITUATION DESCRIPTION:
During the installation of a translation solution or a translation service pack, help texts were not always updated in the
B-language. The help text contained still the old information or the text was in English.
This happened when the text-window properties of the help texts in the receiving system differed from the text-window
properties of the sending system or when the sending or receiving system was a multi-byte system.
SOLUTION DESCRIPTION:
The method to compare the current English help text in the system and the English help text, which was the base for the
translation, has been changed. When the contents of the help texts are the same, they are considered as equal, in spite of
differences in the format.
Note: this comparison is used to know whether already a newer solution for the help text has been installed; if this is the
case, the B-language help text is not updated.

Solution: 133576
SITUATION IDENTIFIED IN:
"Price Calculator" (tdpcg0200m100)
SITUATION DESCRIPTION:
In the Price Simulator, the total discount calculated for the first time is different from what is calculated for the second
time even with out changing the values of any of the fields on the Price Calculator. Both times the recalculation of the
Prices and Discounts should be consistent.
SOLUTION DESCRIPTION:
The total discount percentage is calculated correctly, even for the first time and the results will be consistent how many
ever times user recalculates the prices and discounts.

Solution: 133579
SITUATION IDENTIFIED IN:
"Release Sales Orders/Schedules to Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
When releasing a sales order line to invoicing (tdsls4247m000) using a payment method with option 'Foreign countries
allowed' disabled and option 'Bank Address Required' enabled, error message 'Payment method cannot be used: different
countries' is printed on the log report even when the Bank Address of Business Partner is not filled.
SOLUTION DESCRIPTION:
When during the release of a sales order line to invoicing a payment method is used with option 'Bank Address Required',
message 'Bank Address of Business Partner not found' is printed on the log report in case no bank is filled within the
pay-by Role of the Business Partner. In case the Bank of the Business Partner is filled and the country of the bank
differs from the company's country, message 'Payment method cannot be used: different countries' is printed on the log
report in case option 'Foreign countries allowed' on the payment method is off.

Solution: 133580
SITUATION IDENTIFIED IN:
"Confirm Shipments" (whinh4275m000)
SITUATION DESCRIPTION:
When confirming a shipment for which triangular trade (trade within EU with invoice relation) with price type is
commercial price is applicable while the transfer price stored on the warehouse order header is zero at the moment of
confirm shipment, the fatal error "Error 205 (Out of range) on tccom710### in db_insert(51)" is returned.
SOLUTION DESCRIPTION:
Now when confirming a shipment in above described scenario the system will retrieve the transfer price from the price book.
If no price is found, the message "Transfer price could not be retrieved for intra company invoicing" is returned. If a price
is found this price is used for creating the Intrastat records in tccom7571m000 "Import/Export Statistics".

Solution: 133582
SITUATION IDENTIFIED IN:
"Chart of Item/Channel Planning" (cprmp2701m000)
SITUATION DESCRIPTION:
A bw error message "Invalid property value" is given when running "Chart of Item/Channel Planning" for some charts.
SOLUTION DESCRIPTION:
When running "Chart of Item/Channel Planning" (cprmp2701m000), maximum of 80 positions is set for the top chart title
to avoid the message "Invalid property value".

Solution: 133591
SITUATION IDENTIFIED IN:
"Release to Warehousing (Batch)" (tdsls4246m000)
"Release to Warehousing" (tdsls4501m140)
SITUATION DESCRIPTION:
For collect orders that are not directly released to Warehousing, no Released Outbound Report is printed. Although in
Warehousing, the parameter "Print Released Outbound Report for Collect Orders" is set to 'yes'.
SOLUTION DESCRIPTION:
When running session "Release to Warehousing (Batch)" (tdsls4246m000) for collect orders that are not directly
released to Warehousing, the Released Outbound Report is printed.
A collect order that is not directly processed can also be released to Warehousing using session "Release to Warehousing"
(tdsls4501m140). In that case a report is also printed.

Solution: 133595
SITUATION IDENTIFIED IN:
"Audit Payments" (tfcmg1255s000)
SITUATION DESCRIPTION:
The session 'Audit Payments' (tfcmg1255s000) gives the audit error "Payment is = 0" when the total amount of the
payment batch is 0, although the payment method uses the check master.
SOLUTION DESCRIPTION:
Checks can be processed for the zero payments.

Solution: 133599
SITUATION IDENTIFIED IN:
"Item Customer Information" (tdisa0110s000)
SITUATION DESCRIPTION:
When entering a new record in session "Item Customer Information" (tdisa0510m000) the single occurrence session "Item
Customer Information" (tdisa0110s000) opens with a few disabled fields until the 'tab' key is hit.
SOLUTION DESCRIPTION:
When entering a new record in session "Item Customer Information" (tdisa0501m000) the single occurrence session
"Item Customer Information" (tdisa0110s000) opens with enabled fields.

Solution: 133603
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
At the moment we also see sub business processes in the Dynamic Menu Browser, for which there is no authorization.
We do not want our end-users to see those business processes.
SOLUTION DESCRIPTION:
These business processes are shown, because on a lower level an activity can exist for which the end-user is authorized.
We build a view option, so the end-user can select to see the not authorized sub business processes or not.
The risk is, that also some lower level activities for which there is no authorization are not shown at that moment.

Solution: 133608
SITUATION IDENTIFIED IN:
"Easy SQL" (ttadv3180m000)
SITUATION DESCRIPTION:
Generate report will fail if the query has an odd number of parentesis. It will fail during the second generate. If it is then
corrected then it will continue to fail until you restart the session.
SOLUTION DESCRIPTION:
This problem is now solved and there will no error occur even if there is an odd number of parentesis.

Solution: 133613
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
"Approvals" (whinh3522m000)
SITUATION DESCRIPTION:
Create an Inbound Order Type with the following steps.
Receipt:
1. Print Goods Received Note
2. Receipts
3. Put Away Inbound Advice
Inspection:
1. Approvals
2. Put Away Inbound Advice
Execute the steps for an Inbound Order Line, the Procedure mask (whinh215.pmsk) is not updated properly, after
execution of each step. The updation of proper value occurs only when Putaway Inbound Advice is done.
SOLUTION DESCRIPTION:
The procedure mask (whinh215.pmsk) is updated properly after execution of every step in the Inbound Order Type, and
not finally after the execution of Putaway Inbound Advice.

Solution: 133615
SITUATION IDENTIFIED IN:
"Spool Close" (ttstpsplclose)
SITUATION DESCRIPTION:
When printing (via a job) to a non existing device the job will finish as there was totaly no problem.
SOLUTION DESCRIPTION:
No a check is done if the device exists. If it doesn't exist then the job will fail in a runtime error

Solution: 133623
SITUATION IDENTIFIED IN:
"Direct Debit Advices" (tfcmg4120s000)
SITUATION DESCRIPTION:
It is not possible to cash an amount which exceeds Invoice balance in the session Direct Debit Advice. Error message
'Amount to be cashed exceeds invoice balance' is given and the user is not allowed to proceed further.
SOLUTION DESCRIPTION:
It is possible to cash an amount which exceeds Invoice balance in the session Direct Debit Advice. Warning message
'Amount to be cashed exceeds invoice balance' is given and a Payment Difference will be posted.

Solution: 133624
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
In Triangular Invoicing scenario, zero price and amount are booked for Sales Return Order when transfer pricing method is
"Valuation Price". When the receipt is confirmed, invoice details are booked in Central Invoicing with negative quantity.
But zero price and amount are posted, instead of proper price and amount. This situation occurs when the Return Sales
Order is linked with a normal Sales Order.
SOLUTION DESCRIPTION:
Price and amount is calculated properly based on the Valuation Price and the amounts displayed correctly.

Solution: 133626
SITUATION IDENTIFIED IN:
"Archive Inventory Transaction by Item and Warehouse" (whinr1210m000)
SITUATION DESCRIPTION:
When archiving orders from session Archive Inventory Transaction by Item and Warehouse (whinr1210m000), session
gives "No Data selection" and wrong records are getting archived.
SOLUTION DESCRIPTION:
Now system archives the correct records on Archive Inventory Transaction by Item and Warehouse table.

Solution: 133627
SITUATION IDENTIFIED IN:
"Assign Invoices to Credit Notes" (tfacp2121s000)
SITUATION DESCRIPTION:
If the currency difference ledger account is not defined for the currency, then no assignment takes place when assigning
the credit note to invoice in session "Assign Invoices to Credit Notes" (tfacp2121s000). And no error message comes up.
SOLUTION DESCRIPTION:
When the currency difference ledger account is not defined for the currency, then an error message pops when the
relevant message.

Solution: 133628
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved

134216, 134498
Descriptions:
- Defect 134216 Input expression for form field not correctly handled
- Defect 134498 Retry setting of application lock if appl.set fails with -3
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 133635
SITUATION IDENTIFIED IN:
"Compare Package VRCs" (ttadv6450m000)
SITUATION DESCRIPTION:
'Session Status' is not used as an attribute for comparison when comparing sessions using 'Compare Package VRC's '
SOLUTION DESCRIPTION:
Now the field 'Session Status' of both VRC's is also compared and the result is printed in the report when the comparison
is done for sessions.

Solution: 133643
SITUATION IDENTIFIED IN:
"Print Aging-Analysis by Invoice-from Business Partner" (tfacp2420m000)
SITUATION DESCRIPTION:
In session "Print Aging-Analysis by Invoice-from Business Partner" (tfacp2420m000), the defaults are not saved under
the group "Dates and Periods".
SOLUTION DESCRIPTION:
The defaults are not getting changed to the current date or periods.

Solution: 133651
SITUATION IDENTIFIED IN:
"Compose/print/post invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Service contract Invoices with "Zero Amounts" are printed though the option "Suppress Zero Amounts " is checked in
session 'Billing Request Additions' (cilsi1520m000).
SOLUTION DESCRIPTION:
Service contract Invoices with "Zero Amounts" are not printed when the option "Suppress Zero Amounts " is checked in
session 'Billing Request Additions' (cilsi1520m000).

Solution: 133653
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
There are 3 cases where Costs are booked on a Service order linked to a PCS project, and where these Costs are not
recognized
as "Outgoing value" in "Print Project Work In Process" (tipcs3480m000). This results in wrong WIP amounts.
Case 1:
Service Order linked to a PCS Project, and service order costs are made marked as "internal";
These Costs are booked as "Internal Service Costs", but are not seen in "Print Project Work In Process" (tipcs3480m000)
as
"Outgoing value".
Case 2 :
Service order which is created from a Field change order is linked to a PCS Project; when costs are booked on this service
order
related to Field change order activities, then these costs are booked as "Field change order Costs". These costs are not
seen in
"Print Project Work In Process" (tipcs3480m000) as "Outgoing value".
Case 3:
Service order with Warranty Costs is linked to a PCS Project; when Warranty Costs are booked on this service order these
Costs
are booked as "Warranty Costs". These costs are not seen in "Print Project Work In Process" (tipcs3480m000) as
"Outgoing value".
In all 3 situations the WIP amount in Service and PCS is not correct.
SOLUTION DESCRIPTION:
The session "Print Project Work In Process" (tipcs3480m000) is modified such that the integration transaction with
Transaction Origin "Service" and Financial transaction "Internal Service Costs" or "Field change order Costs" or
"Warranty Costs" are now included in the "Outgoing value" amount on the report. Because of this also the WIP amount is
now correct.

Solution: 133658
SITUATION IDENTIFIED IN:
"Receipt Correction" (whinh3121s000)
SITUATION DESCRIPTION:
When trying to do a receipt correction (session whinh3121s000 "Receipt correction") for a subcontracting item message
"Receipt correction not possible" arises.
SOLUTION DESCRIPTION:
It is possible to do a receipt correction for Cost, Service or Subcontracting, items, therefore message "Receipt correction
not possible" does not pop up.

Solution: 133664
SITUATION IDENTIFIED IN:
"audit posting data of electronic bank statements" (tfcmg5203m000)
SITUATION DESCRIPTION:
When the Invoice-to Business Partner has the status 'doubtful', the audit error report "audited electronic bank
statements" created by the session "audit posting data of electronic bank statements" (tfcmg5203m000) shows this Business
Partner as "Inactive". This is incorrect. It should be possible to receive money from the Business Partner.
SOLUTION DESCRIPTION:
The audit error report "audited electronic bank statements" created by the session "audit posting data of electronic bank
statements" (tfcmg5203m000) shows this Business Partner on the report as inactive only when the status of the Business
Partner is "Inactive".

Solution: 133668
SITUATION IDENTIFIED IN:
"Transfer Purchase Order Advice" (whina3212m000)
"Copy Purchase Orders" (tdpur4201m000)
SITUATION DESCRIPTION:
-1- There is a direct delivery sales order. The purchase order advice is generated for this sales order line and the
Supplier of that order advice is linked to a consignment owned warehouse. This does not allow the purchase order being
created as the system gives the error report
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
"Purchase Order could not be generated" "Warehouse not allowed because of Warehouse type or relation"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-2- Manually adding a subcontracting item to the purchase order line is not allowed. But, it is possible to copy an existing
subcontracting line in to another line.
SOLUTION DESCRIPTION:
-1- The purchase order is generated now. The warehouse is no longer defaulted to the purchase order while the order type
is direct delivery.
-2- Copying a line with 'Subcontracting' item is also not allowed.

Solution: 133669
SITUATION IDENTIFIED IN:
"Archive / Purge Finance Transaction" (tfgld6205m000)
SITUATION DESCRIPTION:
When running session "Archive / Purge Finance Transaction - tfgld6205m000" the error message "Fatal error 206 :
"Record not Locked" pops up.
SOLUTION DESCRIPTION:
When running session "Archive / Purge Finance Transaction - tfgld6205m000" there are no more error messages.

Solution: 133675
SITUATION IDENTIFIED IN:
"Print Purchase Orders for Subcontracted Operations" (tisfc2410m000)
SITUATION DESCRIPTION:
A label in the report is used which suggests this has to do with serial numbers.
SOLUTION DESCRIPTION:
The label for serial number is used to display the serial numbering.

Solution: 133680
SITUATION IDENTIFIED IN:
"Process transaction" (tpppc4802m000)
SITUATION DESCRIPTION:
Surcharges of type "Adjustment entry - commitments" are created at a wrong point of time while trying to close a project.
SOLUTION DESCRIPTION:
The creation of surcharges of type "adjustment entry- committment" are now created at the final stages of closing the
project. Hence the surcharges wont be created when there are still unprocessed purchase orders are present.

Solution: 133688
SITUATION IDENTIFIED IN:
"Scan Solution File" (ttpmc2200m000 / ttpmc2200s000)
SITUATION DESCRIPTION:
With session "Scan Solution File" (ttpmc2200m000 / ttpmc2200s000) it is possible to scan all files in a directory. However,
if an error occurred on one file (e.g. a file with an incorrect format), you could not see which file caused the error.
SOLUTION DESCRIPTION:
The session displays the files being processed. When an error occurs and the error message is displayed, the concerning file
is still displayed, so you can see which file caused the error.

Solution: 133699
SITUATION IDENTIFIED IN:
"Print Customer Statements" (tfacr3440m000)
SITUATION DESCRIPTION:
When payment schedule is defined on an invoice, all the scheduled payments doesn't show up in the report "Print
Customer Statements" (tfacr3440m000).
SOLUTION DESCRIPTION:
When payment schedule is defined on an invoice, all the scheduled payments will show up in the report "Print Customer
Statements" (tfacr3440m000).

Solution: 133700
SITUATION IDENTIFIED IN:
"Print Query Data" (ttadv3482m000)
SITUATION DESCRIPTION:
When in session "Print Query Data" a range must be specified using a 'from' and a 'to' field the 'to' field becomes empty
when the 'from' field is also empty.
SOLUTION DESCRIPTION:
When the 'from' field of the form of session 'Print Query Data' is empty the 'to' field will be filled with the maximum value
possible for that field.

Solution: 133704
SITUATION IDENTIFIED IN:
"Service Order: Actual Other Costs" (tssoc2141s000)
SITUATION DESCRIPTION:
1 When assigning two lines of service costs, which originate from a CMG-batch, the message "BAAN Service Amount not
splitted up completely" appears, and the batch cannot be finalized.
2 When posting Service General Costs to the Service General Cost interim account, an existing actual other cost lines
which are linked, to another financial document can be updated in session "Service Order Actual Other Costs"
(tssoc2140m000).
3.After finalization of a batch, updating costs on an actual other cost line is still possible.
SOLUTION DESCRIPTION:
1 A CMG-batch can be finalized without any problem if amounts on the document lines are split up in several service
order cost lines in Baan Service.
2 When splitting up costs, the overview session tssoc2521m000 or tssoc2541m000 will be started.
Here, cost lines related to a service order are shown. Costs on material lines can be updated if the delivery type is "Local
Purchase" and costs on other lines can be updated if the cost type = "Other".
The lines will be linked to the financial document when saving the lines.
It is also possible to insert a new line (with the correct position number defaulted) for a service order/activity with the
status "Released" or "Completed" or to update an existing line, which is not linked to another financial document.
The cost line itself will have the status "Free" and should be costed by Service.
3. Updating costs on cost line that is linked to a financial document is only possible via Finance.

Solution: 133707
SITUATION IDENTIFIED IN:
"Copy Software Components to new Package VRC" (ttadv6265m000)
SITUATION DESCRIPTION:
When running session "Copy Software Components to New Package VRC" in a job then it is not possible to change the
session data.
SOLUTION DESCRIPTION:
Now changing of the session data is possible

Solution: 133708
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100m000) and
"Select Open Items" ( tfcmg2118s000 )
SITUATION DESCRIPTION:
1.Wrong "Pay-from/Pay-to" Business partner is defaulted when a transaction is entered in session "Bank Transactions"
(tfcmg2100m000). This is happened if the Child Business Partner has defined the role "Pay by, but in "Invoice to" the
Parent Business Partner is set as a "Pay- by".
SOLUTION DESCRIPTION:
1. The defaulted "Pay-from/Pay-to" Business Partner is the Business Partner defined in the "Invoice to" role of the
Business Partner for which the bank transactions is made.
2. In session "Select Open Items" ( tfcmg2118s000 ) all open items of the related Business Partners are selected - invoices,
credit notes, unallocated/advance receipts.

Solution: 133712
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
- When opening the Selling tab of session "Sales Order Lines" (tdsls4101s000), the amounts are not correct. The field 'Cum.
Disc. Perc.' remains zero, until the user tabs through the discount field. But, when the order is shipped the fields are
disabled and 'Cum. Disc. Perc.' remains zero, which can be incorrect.
- When changing forms for a sales order line (session tdsls4101s000) with backorder the field Total Discount Amount is
changing
SOLUTION DESCRIPTION:
- When opening the Selling tab of session "Sales Order Lines" (tdsls4101s000), all amounts have the correct values.
- The field Total Discount Amount displays the Discount Amount based on the Shipped Quantity, as described in the help
text. The value of the field is not changing when changing forms.

Solution: 133723
SITUATION IDENTIFIED IN:
"Created Sales Order History by Item" (tdsls5503m000).
SITUATION DESCRIPTION:
1. Calculation of "Total Amount" (totlqana) and "Total Quantity" (form.amnt) was not correct.
2. Help text not correct.
Following part of the help text is not relevant: "If you start this session, iBaan ERP displays the following question:
Only balance per order/position? If you select No,
detailed information about each order line position is displayed."
SOLUTION DESCRIPTION:
1. Calculation of "Total Amount" (totlqana) and "Total Quantity" (form.amnt) are now correct.
Calculation is done for all home currencies of the current company.
In a multisite environment, using a currency system of type 'Dependent', calculation did not take into account that
per company the home currencies used may be
different (except for the reference currency which is mandatory for all companies and should be the same in all used
companies).
The way the calculation was done, it was possible that order amounts in different currencies were added. From now on
only, order amounts, which are in the same currency are added.
In multisite environments, using currency system 'Dependent', total amount is calculated and displayed in the reference
currency.
2. Session help modified. Now reflects actual functionality of session.
At startup of the session, no question is asked concerning balance per order / position. This was the case in earlier
versions. Now this is not applicable anymore.
This functionality is now available as an option to be chosen via specific-menu.

Solution: 133735
SITUATION IDENTIFIED IN:
"Payments Schedule" (tfacp1103m000)
SITUATION DESCRIPTION:
1.) In case of invoices with a payment schedule, and a part of it was paid, the field "To be scheduled" has the same value
as field "Already Paid Amount".
2.) When running session "Payments Schedule - tfacp1103m000" from the menu and inserting a New Group, the error
message "Total amount of payment schedule unequal to total invoice amount" pops up.
SOLUTION DESCRIPTION:
1.) Because the fully paid amount is taken in account ( the paid amount before a payment schedule is made and the amount
paid of one of the schedule-lines ) the right amounts are displayed.
2.) Because the equality check of "Total Invoice Amount" and "Total Scheduled Amount" is now done after the input
the message "Total amount of payment schedule unequal to total invoice amount" does not pop up anymore.

Solution: 133747
SITUATION IDENTIFIED IN:
"MAUC Correction" (whina1230m000)
SITUATION DESCRIPTION:
-1- The table "Item Inventory by Warehouse Cost Details" isn't updated. This leads to wrong MAUC result/values.
-2- The MAUC values are rounded as amounts while the MAUC is defined as cost price.
SOLUTION DESCRIPTION:
-1- The determination of cost components and their values is improved. The right values are written in the table "Item
Inventory by Warehouse Cost Details".
-2- The MAUC values are now rounded as cost price in stead of amount.

Solution: 133752
SITUATION IDENTIFIED IN:
"Sales Quotations" (tdsls1100s000)
SITUATION DESCRIPTION:
When a Sales Quotation (session tdsls1100s000) has lines, it is not possible to change the Sales Order Type on the
Quotation Header. Customers may not know the order type in advance. Changing the order type is no problem as different
orders are created for each quotation line.
SOLUTION DESCRIPTION:
When a Sales Quotation (session tdsls1100s000) has Lines, the field 'Sales Order Type' on the Quotation Header is
enabled.

Solution: 133767
SITUATION IDENTIFIED IN:
"Print Role Data" (ttams2400m000)
SITUATION DESCRIPTION:
Session "Print Role Data" (ttams2400m000) does not produce a report that shows the complete role authorizations of a
role.
The subroles of a role are present in the report, but the authorizations of these subroles are not present.
Only the authorizations of the role are present on the report.
SOLUTION DESCRIPTION:
The report now shows the authorizations of the subroles as well.

Solution: 133768
SITUATION IDENTIFIED IN:
"Check Solution to Install", "Check and Install Solutions" (ttpmc2203s000/ttpmc2204s000)
SITUATION DESCRIPTION:
After installation of solution 133474 it could occur that during the checking of a PMC solution the
error message
"Error -2 during open of patch" or
"Error -2 during seq.open file ......."
was displayed. This happened when a pre-requisite solution was found, which was installed already, but the solution dump
didn't exist on the directory anymore.
SOLUTION DESCRIPTION:
Because information in the dumps of installed solutions is not needed, these dumps are not read anymore by the session.
So, when these dumps are not present, no error message will occur.

Solution: 133770
SITUATION IDENTIFIED IN:
"Inspection Order Lines" (qmptc1501m000)
SITUATION DESCRIPTION:
When user wants to create a new record for "Inspection Order lines" (qmptc1101s000), "Enter Test Data by
Characteristic" (qmptc1115s000), "Enter Test Data by Serial Number" (qmptc1116s000), system does not show the default
data in the created new record.
SOLUTION DESCRIPTION:
The system will display the default data, when user creates a new record for "Inspection Order lines" (qmptc1101s000),
"Enter Test Data by Characteristic" (qmptc1115s000), "Enter Test Data by Serial Number" (qmptc1116s000).

Solution: 133784
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
The report group 4, "Report & Remittance Bank File (Clieop)" (tfcmg126041000) does not reflect the totals for the
Clieop03 bank file. The Clieop03 expects the own account number to be added for every line of the customer's bank
account.
SOLUTION DESCRIPTION:
The report "Report & Remittance Bank File (Clieop)" (tfcmg126041000) adds the own account to the totals each time a
customer's bank account is added. The result reflects the totals that are present in the Clieop03.

Solution: 133790
SITUATION IDENTIFIED IN:
"Copy Table Fields from Data Dictionary" (ttams3243m000)
SITUATION DESCRIPTION:
It's not possible to Copy Table Fields from Data Dictionary for Tools tables (tt).
I.e. For a particular role, the system doesn't copy tools table fields when we try to add them via session Copy Table
Fields from Data Dictionary (ttams3243m000)
SOLUTION DESCRIPTION:
Now, its possible to copy 'tools table fields' from data dictionary through this session.

Solution: 133791
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
135112
Descriptions:
- Defect 135112 AFS set.report should always overrule the device if device is specified
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 133795
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7210m000)
SITUATION DESCRIPTION:
When the tax code (tdsls401.cvat) is not included in the conversion setup, the default tax code is not checked. Sales order
lines can be inserted with an invalid tax code.
SOLUTION DESCRIPTION:
Now the defaulted tax code is also checked in case the field is not included in the conversion setup. If the defaulted code
has no financial data, for example, then the proper error message is given on the "Errors in Received Messages" report and
the order is rejected.

Solution: 133801
SITUATION IDENTIFIED IN:
"cprrp1210m000" (Simulate Orders)
SITUATION DESCRIPTION:
After installing solution 133247 (tcmcsdll0095 and only for B51_a) and Simulate Orders the planning of new orders goes
backwards in time instead of starting from the current date. There are no errors printed to the error report.
SOLUTION DESCRIPTION:
Problem is found in the "Handle Cache Memory" functionality and can occuur in all versions.
The caching table will be reset before calling the caching functionality for a new changing action. The Cache Memory will
be used with correct data.

Solution: 133810
SITUATION IDENTIFIED IN:
"Copy Forms/Reports to New VRC using a given Label" (ttadv6270m000)
SITUATION DESCRIPTION:
After you specified all selections in the session "Copy Forms/Reports to New VRC using a given Label" (ttadv6270m000)
and pressed the "Copy"-button a fatal error was given:
Fatal error : Use of NULL pointer on ' '
Fatal error : Can not continue in ttadv6265m000 in DLL: ottstpstandard ()[exec_function]
No components were copied to the new VRC.
SOLUTION DESCRIPTION:
The session has been corrected, the components will be copied.

Solution: 133813
SITUATION IDENTIFIED IN:
"Generate Subcontracting Purchase Orders" (tisfc2250m000)
SITUATION DESCRIPTION:
While trying to generate the subcontracting purchase order, an error message is reported saying that Dimension 1 of
ledger account XXXXXX must be filled.
SOLUTION DESCRIPTION:
The dimensions will be retrieved correctly for the ledger account and is filled by default.

Solution: 133816
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When a Purchase Order Line, which is linked to a contract is created, and if the Price Unit in the Item Purchase Data is
different from the Price Unit in the contract, the Price Unit from the contract is not picked up. Instead the Price Unit of
the Item Purchase Data is picked up.
SOLUTION DESCRIPTION:
The Price Unit of the contract is picked, and not the Price Unit defined in the Item Purchase data.

Solution: 133818 SITUATION IDENTIFIED IN: "Sales Order Input Controls" (tdsls0195m000). SITUATION DESCRIPTION: Error: "Field <> is not found on table ".Error occurs when adding a non standard or localized field in "Sales Order Input Controls" (tdsls0195m000). SOLUTION DESCRIPTION: Non standard or Localized fields can be handled in "Sales Order Input Control" (tdsls0195m000). Format of standard table fields is: ppmmmtttt.nnnn (where p = package, m = module, t = table, n = field). Solution: 133821 SITUATION IDENTIFIED IN: "Finalize engineering Data" (tiedm3240m000) SITUATION DESCRIPTION: When the engineering BOM component is not copied to production, while finalizing the engineering the engineering data, the engineering BOM component is to be customized in Production, system is giving the error message saying warehouse not allowed. SOLUTION DESCRIPTION: When the engineering BOM component is to be customized at Production side, if the engineering BOM component is not having the relationship at production side also, system will create the customized component and finalize the engineering data. Solution: 133829 SITUATION IDENTIFIED IN: "Print Supplier Balance Report" (tfacp2424m000) SITUATION DESCRIPTION: Session "tfacp2420m000 - Print Supplier Aging Analysis" gets the assignment document as payment document and shows invoice balance is zero. However session "tfacp2424m000 - Print Supplier Balance Report" shows invoice is outstanding. SOLUTION DESCRIPTION: Session "tfacp2424m000 - Print Supplier Balance Report" outputted wrong data. This has been solved now. Solution: 133831 SITUATION IDENTIFIED IN: "Copy Table Fields from Data Dictionary" (ttams3243m000) SITUATION DESCRIPTION: It's not possible to Copy Table Fields from Data Dictionary for Tools tables (tt). I.e. For a particular role, the system doesn't copy tools table fields when we try to add them via session Copy Table Fields from Data Dictionary (ttams3243m000) SOLUTION DESCRIPTION: Now, its possible to copy 'tools table fields' from data dictionary through this session. Solution: 133834 SITUATION IDENTIFIED IN: "'Transfer Installments to Central Invoicing' " (tsctm4203m000) SITUATION DESCRIPTION: When using session 'Transfer Installments to Central Invoicing' (tsctm4203m000) for more then 1 contract installment per contract, the end date (cisli265.iedt) is not correctly calculated for the last transferred installment per contract. It will have the same end date as the previous installment send to Central Invoicing in the same run for the same contract. SOLUTION DESCRIPTION: The Installment End Date (cisli265.iedt) will be filled correctly. If it cannot be determined from the next installment, it is calculated based on the planned invoice date; the number of period and the period unit. Solution: 133838 SITUATION IDENTIFIED IN: "User Defaults" (tsmdm1150s000) SITUATION DESCRIPTION: When changing the department of an employee in Common, it is not possible to change this department in the User Defaults in Service. SOLUTION DESCRIPTION: When the department of the User Defaults differs from the department of the employee, the User Default department is modifyable. Note: Always be careful with modifying Master Data. Like in the above described case, when modifying the department on the employee in session Employees (tccom0101s000) for which also user defaults exist in service in session User Defaults (tsmdm1150s000), you need to check whether the department, sales rep, and all the series defined on the User Defaults need modification. Solution: 133841 SITUATION IDENTIFIED IN: "Print Receivable Invoices Checklist" (tfacp1438m000) SITUATION DESCRIPTION: The project field is not printed on the report "Print Receivable Invoices Checklist". SOLUTION DESCRIPTION: The project field is now printed in the first 2 reports of the session "Print Receivable Invoices Checklist". Solution: 133843 SITUATION IDENTIFIED IN: "Install Solution" (ttpmc2205s000) SITUATION DESCRIPTION: When you installed a Translation Service Pack a fatal error could occur when the English version of a help text in the Translation Service Pack was empty. The following error messages were displayed: Fatal error : index 2 from Dim [0] 1 Fatal error : Can not continue in ttpmc2205s000 in DLL : ottpmcdllblang ()[bms.receive$] The Translation Service Pack and the individual solution, which was being installed, retained the status 'Installing'. SOLUTION DESCRIPTION: The session now can handle empty help texts. Solution: 133846 SITUATION IDENTIFIED IN: "Specifications Delivered, not yet invoiced" (tfacr1432m000) SITUATION DESCRIPTION: The report ' Specifications Delivered, not yet invoiced ' is showing incorrect values for the consignment payment sales order. SOLUTION DESCRIPTION: The report ' Specifications Delivered, not yet invoiced ' is showing correctly for the consignment payment sales order. Solution: 133847 SITUATION IDENTIFIED IN: "Recalculate Customer Balances" (tfacr2245m000) SITUATION DESCRIPTION: Anticipated balance is wrongly calculated, if anticipated document is rejected. SOLUTION DESCRIPTION: Anticipated balance is correctly calculated. Solution: 133851 SITUATION IDENTIFIED IN: "print open orders" (tpcor0400m000) SITUATION DESCRIPTION: A report is required to print all the open / unprocessed orders for TP projects so that necessary action can be taken regarding the orders so as to cause no problems while closing the project. SOLUTION DESCRIPTION: A new print session is been created which will print all the data to take necessary action for all the orders by TP project. Solution: 133859 SITUATION IDENTIFIED IN: "Select Device" (ttstpsplopen) SITUATION DESCRIPTION: When a session, which prints automatically to display is executed in Function Server mode, the print to Display is executed like the session is being executed in GUI mode. Print to Display should not be executed in Function Server mode. SOLUTION DESCRIPTION: Print to Display is skipped when session is executed in Function Server mode. Solution: 133861 SITUATION IDENTIFIED IN: "Sales Quotation Lines" (tdsls1501m000). SITUATION DESCRIPTION: Errors caused by duplicate records during Global Confirmation of Sales Quotation Lines in session "Sales Quotation Lines" (tdsls1501m000). SOLUTION DESCRIPTION: Application logic for writing records to Sales Quotation Line History table (tdsls151) is modified. During Global Confirmation of Sales Quotation Lines no "Duplicate Record" error will be generated anymore. Solution: 133863 SITUATION IDENTIFIED IN: "Print Business Partner Statements" (tfacp3441m000) SITUATION DESCRIPTION: When running session "Print Business Partner Statements - tfacp3441m000" and printing with a device "CR" then it is printing only an empty page. SOLUTION DESCRIPTION: Because a change of steering the device, printing with a device "CR" will deliver a good XML-page in Crystal. Solution: 133880 SITUATION IDENTIFIED IN: "Copy Components of Solution to B-Language" (ttpmc3200m000) SITUATION DESCRIPTION: In the session "Copy Components of Solution to B-Language", it was not possible to select all solutions of a Service Pack. Besides this, there were two other problems: - Components were always compiled after they were copied to the B-Language. If this session had to be repeated for different ranges of solutions or Service Packs, components could be compiled more than once, which increased the time needed for this session. - Menus could be copied to the B-Language and dumped before sub menus were copied. This resulted in menu codes being displayed on the menus instead of menu descriptions. SOLUTION DESCRIPTION: The session allows you to enter a range of Service Packs. Compilation of the copied components is optional. If you decide not to compile the components during the execution of this session, you have to do it afterwards with the sessions "Compile Reports" (ttadv3240m000) and "Create Runtime Data Dictionary (Forms and Menus)" (ttadv5214m000). Menus are dumped after the sub menus have been copied, so the menu description of the sub menu in the B-Language is known before the calling menu is dumped. Solution: 133881 SITUATION IDENTIFIED IN: "General Item Data" (tcibd0501m000) SITUATION DESCRIPTION: Wrong active revisions are displayed, when the ASCII value of engineering item revisions are created in descending order. SOLUTION DESCRIPTION: System will display the correct engineering item revision, even if the ASCII value of engineering item revisions is descending. Solution: 133883 SITUATION IDENTIFIED IN: "Invoice-to BP aging summary" (tfacr2511m000) SITUATION DESCRIPTION: Invoices with greater than "as of" date are not selected. SOLUTION DESCRIPTION: Invoices with greater than "as of" date are also selected. Input fields "Last Invoice Date/Period" and "Last Receipt Date/Period" are added. Solution: 133885 SITUATION IDENTIFIED IN: "Print Invoice-from/to Business Partner's Finalized Transactions" (tfacp2416m000/tfacr2416m000) SITUATION DESCRIPTION: It is only possible to print this session up to a period and not to print this session from until a period. SOLUTION DESCRIPTION: Because changing the functionality of the session the possibility to print from/until is there. Solution: 133905 SITUATION IDENTIFIED IN: "Service Order Actual Labor Costs" (tssoc2531m000) SITUATION DESCRIPTION: 1) Cost Amounts on a Service Order Actual Labor line are doubled in case the end user executes the following steps: - Enter an Hours Accounting Line in session Service Hours Accounting (tssoc2135s000 or tssoc2136s000). - Without leaving the session change the Hourly Labor Type (tssoc235.chlt) or the Cost Component (tssoc235.ccmp). - Without leaving the session change the Hourly Labor Type (tssoc235.chlt) or the Cost Component (tssoc235.ccmp) again. - The total cost amount in the Service Order Actual Labor Line is now doubled. 2) Cost Amounts on a Service Order Actual Labor line are wrong in case the end user executes the following steps: - Enter Hours Accounting Lines in session Service Hours Accounting (tssoc2135s000 or tssoc2136s000) for 2 or more Service Orders. - Change the status of one of the Service Order Actual Labor Lines to status 'Costed'. - In session Service Hours Accounting, change the Service Order Number of the Hours Accounting lines related to the Service Order Actual Labor Lines with status 'Costed', to the another Service Order Number (status should not be costed). - On the Service Order with the Labor Line on Costed, a new, corrective, Labor line is created with a wrong Cost Amount. 3) Only B50_c: When coping an Hours Accounting Line for a Service Order (tssoc2136s000), and saving the data, error message pops up: Service Center not allowed. SOLUTION DESCRIPTION: 1) and 2) Changes in Service Order Hours Accounting lines are now properly reflected on the Service Order Actual Labor Lines. 3) When coping an Hours Accounting Line for a Service Order (tssoc2136s000), and saving the data, an error message does not pops up anymore. Data is properly saved. Solution: 133918 SITUATION IDENTIFIED IN: "Open Entries by Business Partner" (tfacr2421m000) SITUATION DESCRIPTION: The report "Open Entries by Business Partner" (tfacr242111000) shows a wrong label in German. It shows "Finanzielle Kreditorengruppe" but it should be "Finanzielle Debitorengruppe". This was caused by a wrong translation of label tfacr001.itbp. This has been corrected SOLUTION DESCRIPTION: The report "Open Entries by Business Partner" (tfacr242111000) now shows the correct label in English and German via label tfacr002.bprg. Solution: 133926 SITUATION IDENTIFIED IN: "Delete Incorrect Warehouse Data" (whcor2003m000) SITUATION DESCRIPTION: When a purchase order line was deleted or cancelled and status set to "Awaiting Deliveries", one should expect "Inbound Ordrer Lines" and "Warehouse Order Header" to be deleted. This was not happening before installing solution 126264. Purchase order lines were deleted, but warehousing data was not being updated accordingly, which was being done after solution 132811. But this solution doesn't work for backorder lines. SOLUTION DESCRIPTION: The Warehouse backorders are also deleted when running the correction program "Delete Incorrect Warehouse Data"(whcor2003m000). Solution: 133929 SITUATION IDENTIFIED IN: "Created Sales Order Line History by Business Partner and Item" (tdsls5501m000) SITUATION DESCRIPTION: Fields Price and Unit are empty in sessions "Created Sales Order Line History by Business Partner and Item" (tdsls5501m000) and "Created Sales Order Line History by Item" (tdsls5503m000) when the Specific option "Only Balance per Order/Position" is chosen. SOLUTION DESCRIPTION: Fields Price and Unit are filled when the Specific option "Only Balance per Order/Position is chosen". In session "Created Sales Order Line History by Business Partner and Item" (tdsls5501m000) also the field gross profit is always shown. For both sessions the help texts are changed. Solution: 133937 SITUATION IDENTIFIED IN: "Service Order: Actual Other Costs" (tssoc2141s000) SITUATION DESCRIPTION: When changing the Cost Price to zero the Invoicing amount of the Costs (tssoc240.acin) is not updated. SOLUTION DESCRIPTION: When changing something on an Actual Service Order Cost line the coverage amounts are always recalculated, which means that also the Invoicing amount will be recalculated and updated. Solution: 133949 SITUATION IDENTIFIED IN: "whinh4531m000" (Shipment Lines) "whinh4275m000" (Confirm Shipment) SITUATION DESCRIPTION: It is impossible to confirm multiple shipment lines in a row in case a project is linked to the corresponding sales order lines. Once a shipment line is confirmed, the following shipment lines cannot be confirmed and error message "Enterprise unit not defined for sales office" (whinhs0249) is given. SOLUTION DESCRIPTION: The check on departments is improved and shipment lines are confirmed properly. Solution: 133952 SITUATION IDENTIFIED IN: "Receipt Lines" (whinh3120s000) SITUATION DESCRIPTION: In session "Receipt Lines" (whinh3120s000) it is possible to enter a larger Received Quantity than the production order completion quantity. Message "The received quantity may not exceed the ordered quantity for % orders" is displayed, but it is possible to save it and continue. However, it will be not possible to confirm the receipt. SOLUTION DESCRIPTION: Message "The received quantity may not exceed the ordered quantity for % orders" is displayed and user is forced to input the data again. Solution: 133966 SITUATION IDENTIFIED IN: "Process Transactions" (tpppc4802m000) SITUATION DESCRIPTION: When a transfer order from a warehouse to a project is completely received in two or more parts, it is not possible to close the project in session "Process Transactions" (tpppc4802m000). The flag "Process Financial Result" must be selected. Then a message comes up saying that an open warehousing order is present. SOLUTION DESCRIPTION: The check whether the order was completely received did not take the status into account. Therefore always indicated that the order was not finalized. Solution: 133967 SITUATION IDENTIFIED IN: standard program. SITUATION DESCRIPTION: Defects solved in B50b, 134755, 134953, 135112, 135480, 213538 Descriptions: - Defect 134755 Not able to use function stp.reset.value - Defect 134953 Record marking in mocc when just added new one. - Defect 135112 AFS set.report should always overrule the device if device is specified - Defect 135480 Not all form table fields are present in qbf - Defect 213538 Correction on fix for DF134216 for Input/Ref expressions - SOLUTION DESCRIPTION: These defects are solved in the standard program Solution: 133969 SITUATION IDENTIFIED IN: "Direct Network Communication" (tcedi7205m000/ecedi7205m000) SITUATION DESCRIPTION: When the incoming ASCII file contains a negative price, this price is inserted on the sales order line. This is not allowed in manual order entry. SOLUTION DESCRIPTION: A negative price is not allowed. Now the system rejects the line/order with the negative price. The error is written to the "Remarks in Copied Messages" report. Solution: 133972 SITUATION IDENTIFIED IN: "Print Budgeted Project Costs" (tpptc3440m000) SITUATION DESCRIPTION: When printing Budgeted Project Costs for a range of Projects, and for instance project A contains an extension with a contract amount equal to zero and project B contains an extension with a contract amount greater than zero, the second print run showed other amounts than the first run. This is incorrect. SOLUTION DESCRIPTION: When printing Budgeted Project Costs for a range of Projects the correct contract amounts are printed, independent of the number of times the report is printed. Solution: 133975 SITUATION IDENTIFIED IN: "Display Gross Profit of Purchase Order Line" (tdpur4808s000) SITUATION DESCRIPTION: Some times the session crashes when the session is started. SOLUTION DESCRIPTION: Now, the session will not crash when the session is started. Solution: 133978 SITUATION IDENTIFIED IN: "Statement Layout Details" (tfacr3114s000) SITUATION DESCRIPTION: Label shown wrongly as "Letter No" instead of "Statement Layout" SOLUTION DESCRIPTION: Label now correctly shown as "Statement Layout" Solution: 133979 SITUATION IDENTIFIED IN: "Copy Sales Contracts" (tdsls3801m000) SITUATION DESCRIPTION: When copying an active contract to another Business Partner, message "item X already included in active contract Y" is shown. But this is incorrect as the Business Partner of contract Y is the Business Partner from the source contract, not the Business Partner of the copied contract. SOLUTION DESCRIPTION: The message "item X already included in active contract Y" only appears when the item X is used in an active contract for the Business Partner of the copied contract. Solution: 133984 SITUATION IDENTIFIED IN: "Specifications Delivered, not yet invoiced " (tfacr1432m000) SITUATION DESCRIPTION: The Report ' Specifications Delivered, not yet invoiced ' is printing incorrectly even though sales invoice maintained for order. SOLUTION DESCRIPTION: The Report ' Specifications Delivered, not yet invoiced ' is printing correctly Solution: 133988 SITUATION IDENTIFIED IN: "Copy project" (tipcs2210m000) SITUATION DESCRIPTION: Copy from a source budget to a target budget is not possible, when source budget have final Budget Calculation, Material Prices, Operation Rates or Subcontracting Rates. SOLUTION DESCRIPTION: The final flag for Budget Calculation, Material Prices, Operation Rates and Subcontracing Rates of the target budget is set to NO, irrespective of source budget, when copying a budget. Solution: 133989 SITUATION IDENTIFIED IN: "Purchase Order Lines" (tdpur4101s000) SITUATION DESCRIPTION: When creating a Purchase Order Line, the Purchase Office country is ignored for VAT determination, even when the Purchase Office has a VAT registration on its address. SOLUTION DESCRIPTION: When creating a Purchase Order Line with a Purchase Office in a different Country than the Financial Company and the Purchase Office has a VAT registration on its address, this Country of the Purchase Office is taken into account for determining the default VAT Code. Solution: 133995 SITUATION IDENTIFIED IN: "Select Device" (ttstpsplopen) SITUATION DESCRIPTION: Print to display is present in some program scripts. When the sessions using these program scripts are run in the function server, print to display was skipped. This was not only done when no user interface is present, but also when this script was run from another session in the function server. SOLUTION DESCRIPTION: Print to display is only skipped when the session is started without user interface. Solution: 133997 SITUATION IDENTIFIED IN: "Print Registered Invoices" (tfacp1433m000) SITUATION DESCRIPTION: Invoices that should be included in the selection are not always shown on the report. SOLUTION DESCRIPTION: The "To" fields in the selection form are only refreshed after tabbing them. When only changing the "From" fields this can result in wrong selection criteria. After installing this solution the "To" fields are refreshed immediately after leaving the corresponding "From" fields. Solution: 133999 SITUATION IDENTIFIED IN: "Copy Budget to Project" ( tipcs2220m000 ) "Copy Project" ( tipcs2210m000 ) SITUATION DESCRIPTION: When using session "Copy Budget to Project" ( tipcs2220m000 ) and using a zoom in the "Target Project Field" to the session "Display First Free Numbers" ( tcmcs0547s000 ) and selecting a serie, you will get the message "Copying not allowed because of project status" when a project with the same number and status > active does already exist. This results in the fact that the next project number for the selected series is not created. SOLUTION DESCRIPTION: Now when using the session "Copy Budget to Project" ( tipcs2220m000 ) and using a zoom in the "Target Project Field" to the session "Display First Free Numbers" ( tcmcs0547s000 ), it is possible to select a series and return to the original session without getting a message ( even when a project with the same number as the selected series and project status > active does already exist ). The next project number for the selected series is now created correctly. Solution: 134003 SITUATION IDENTIFIED IN: "Import/Export Statistics" (tccom7571m000) SITUATION DESCRIPTION: When a cost item does not have the option "release to warehousing" activated in session "Item Sales Data" (tdisa0101s000), then this item is not taken into account for import/export statistics. SOLUTION DESCRIPTION: Import/export statistics are created when appropriate. Solution: 134007 SITUATION IDENTIFIED IN: "Selection Open Items" (tfcmg2118s000) SITUATION DESCRIPTION: In session "Select Open Items" ( tfcmg2118s000 ) not all open items of the related Business Partners are selected - in case of unallocated or advanced receipts which have the same transaction type en number, but different sequential number, only one of them is selected. SOLUTION DESCRIPTION: In session "Select Open Items" ( tfcmg2118s000 ) all open items of the related Business Partners are selected. Solution: 134020 SITUATION IDENTIFIED IN: "Dependencies" (ttpmc1540s000 / ttpmc1541m000) SITUATION DESCRIPTION: When you used the option to display the dependencies of a solution from "Process Solutions" (ttpmc2101m000), it could happen that a wrong solution description for the dependent solution was displayed. This was the case when a dependent solution was displayed, which was not yet scanned. The description of the previous solution was repeated. SOLUTION DESCRIPTION: The descriptions of not yet scanned solutions are empty now. Solution: 134027 SITUATION IDENTIFIED IN: "Update Vendor Rating" (tdpur8850m000) SITUATION DESCRIPTION: 1) In the Online Manual for the Vendor Rating, it was mentioned that Invoiced Price would be used for calculating the Price Accuracy Rating even though Average Purchase Price is used for the Price Accuracy Calculation. This confuses the user as the mentioned one is Invoiced Price and there is no Invoicing related things performed before updating the Vendor Rating for the purchase order. 2) When the Price Unit of the Item is different from the Inventory Unit then the Linear Objective Ratings are wrong. SOLUTION DESCRIPTION: 1) The help text for the calculation of the objective vendor rating for the Cost Performance using Linear Basis is corrected. The Price Accuracy Rating is calculated using Average Purchase Price but not the Invoiced Price. 2) The Objective Vendor rating for the Cost Performance is now calculated correctly even when the Purchase Price Unit is different from the Inventory Unit of the Item. Solution: 134030 SITUATION IDENTIFIED IN: "Inbound Lines" (whinh2510m000) "Outbound Order Lines" (whinh2520m000) SITUATION DESCRIPTION: Some form commands have the wrong authorization settings in session whinh2510m000 and whinh2520m000. This could mean that for example an user with print/display authorization can perform an undo/release of the outbound advice. SOLUTION DESCRIPTION: The authorization settings of the form commands of session whinh2510m000 and whinh2520m000 are corrected to prevent a user can execute an action for which he/she is not authorised.. Solution: 134033 SITUATION IDENTIFIED IN: "Print Business Partners Balance" (tfacp2424m000) SITUATION DESCRIPTION: When running the second report "Balances by Invoices from BP" the total of some Financial Business Groups are printed twice. SOLUTION DESCRIPTION: Because a change of sorting the report "Balances by Invoices from BP" the totals of the Financial Business Groups are printed correct. Solution: 134041 SITUATION IDENTIFIED IN: "Print Detailed Cash Forecast in Home Currency" (tfcmg3413m000) SITUATION DESCRIPTION: On report 'Cash Forecast Details in Home Currency' (tfcmg341311000) both 'Inflow' and 'Outflow' are printed as positive amounts however the 'Outflow' should be printed as negative amounts. SOLUTION DESCRIPTION: On report 'Cash Forecast Details in Home Currency' the 'Inflow' is printed as positive amounts and the 'Outflow' is printed as negative amounts. Solution: 134051 SITUATION IDENTIFIED IN: "Purchase Invoice Corrections" (tfacp2110s000) SITUATION DESCRIPTION: After maintaining a purchase invoice correction for a tax amount the tax amount in invoice currency is incorrect on the purchase invoice. SOLUTION DESCRIPTION: After maintaining a purchase invoice correction for a tax amount the tax amount in invoice currency remains correct on the purchase invoice. Solution: 134053 SITUATION IDENTIFIED IN: "Assign Unallocated / Advance Receipt" (tfcmg2105s000) SITUATION DESCRIPTION: Small Amount of balance is showing for customer even though the invoice amount is paid in full. SOLUTION DESCRIPTION: Now correct balance is shown for the customer balance when the invoice amount paid in full Solution: 134065 SITUATION IDENTIFIED IN: "Receipt Correction" (whinh3121s000) SITUATION DESCRIPTION: It is not possible to toggle the "Final Receipt Flag" while doing "Receipt Correction" (whinh3121s000), for a purchase order line with inspection, after confirming and approving the receipt line. SOLUTION DESCRIPTION: Changes made to allow toggling of the "Final Receipt" flag, when there is no change in either the quantity or the unit, when doing "Receipt Correction". Solution: 134085 SITUATION IDENTIFIED IN: "Created Sales Order Line History by Business Partner and Item" (tdsls5501m000) "Created Sales Order Line History by Item" (tdsls5503m000) SITUATION DESCRIPTION: Field Unit is empty for cost items without inventory unit in sessions "Created Sales Order Line History by Business Partner and Item" (tdsls5501m000) and "Created Sales Order Line History by Item" (tdsls5503m000) when the Specific option "Only Balance per Order/Position" is chosen. SOLUTION DESCRIPTION: Unit fields are filled with the unit of the last entry when option "Only Balance per Order/Position" is chosen Solution: 134105 SITUATION IDENTIFIED IN: "Shipment Packing Structure" (whinh3116m000) SITUATION DESCRIPTION: When the field "Shipped Quantity" is changed in session "Shipment Packing Structure" (whinh3116m000), which is activated from session "Shipment Lines" (whinh4131s000), the fields "Net Weight" and "Gross Weight" aren't changed in the session "Shipment Lines" (whinh4131s000). SOLUTION DESCRIPTION: When changing the field "Shipped Quantity" in session "Shipment Packing Structure" (whinh3116m000), the fields "Net Weight" and "Gross Weight" are updated accordingly in the session "Shipment Lines" (whinh4131s000). Solution: 134107 SITUATION IDENTIFIED IN: "Invoice-To Business Partner Aging Summary" (tfacr2411m000) SITUATION DESCRIPTION: If invoice date is greater than the advance payment (or unallocated receipt) and "Invoice fiscal year" is greater than the "last invoice date/period" then amounts are wrongly calculated. SOLUTION DESCRIPTION: Amounts are calculated correctly. Solution: 134110 SITUATION IDENTIFIED IN: "Sales Invoice" (tfacr1110s000) SITUATION DESCRIPTION: Tax amount posted incorrectly for receipt transaction in case of partly received sales invoice. This problem is happening in the following conditions. 1) Credit note linked to the sales invoice partly 2) In the receipt transaction, discount is given for partly received sales invoice. SOLUTION DESCRIPTION: Tax amount posted correctly for receipt transaction in case of partly received sales invoice Solution: 134127 SITUATION IDENTIFIED IN: "Global Table Maintenance" (ttaad4100) SITUATION DESCRIPTION: In session Global Table Maintenance (ttaad4100), the option Modify Rows can be used. For this option a Start Position and an End Position must be filled in. For both the Start Position and the End Position 4 positions are available to enter digits, but only 3 digits are accepted. SOLUTION DESCRIPTION: Now for Start Position and End Position all 4 available positions can be used to enter digits. Solution: 134129 SITUATION IDENTIFIED IN: "Check Solution to Install / Check and Install Solution" (ttpmc2203s000 / ttpmc2204s000) SITUATION DESCRIPTION: If you selected the option to check also the customizations during the check of solutions, customized objects were not always printed on the report. This was the case when the solution contained a script source and your customization VRC contained only the object of that same component. SOLUTION DESCRIPTION: If a solution contains a script source and the corresponding object exists in the customization layer, the script is being considered as customized and is printed on the report. Solution: 134132 SITUATION IDENTIFIED IN: "Copy Sales Budget to Demand Forecast" (cpdsp1280m000) SITUATION DESCRIPTION: When using session (cpdsp1280m000) "Copy Sales Budget to Demand Forecast" and Channel is selected then the item channel sales budget must be copied to Channel master plans forecast. Currently program doesn't take care about channel when selecting sales budget. SOLUTION DESCRIPTION: When using session (cpdsp1280m000) "Copy Sales Budget to Demand Forecast" and Channel is selected then the item channel sales budget will be copied to Channel master plans forecast. When no Channel is selected then all sales channels budgets will be copied. Solution: 134137 SITUATION IDENTIFIED IN: "Enter Receipt Amounts for Assignment" (tfcmg2107s000) SITUATION DESCRIPTION: 1. During automatic write off, payment difference tolerances, defined in CMG parameters, are not taken into consideration. 2. Discount is not calculated for overpaid invoices. SOLUTION DESCRIPTION: 1. During automatic write off, payment difference tolerances in CMG parameters are considered. 2. Discount is calculated for overpaid invoices. Solution: 134143 SITUATION IDENTIFIED IN: "Print Engineering BOM (Multi-level)" (tiedm1411m000) SITUATION DESCRIPTION: While printing the Engineering BOM (Multi-Level), net quantity for the lower level component items calculated is wrong, when the BOM Unit is maintained for the Engineering BOM component. SOLUTION DESCRIPTION: Net quantity will be calculated correctly, even when the BOM Unit is maintained for the Engineering BOM component, while printing the Engineering BOM (Multi-Level). Solution: 134145 SITUATION IDENTIFIED IN: "Maintain Price List Matrix Codes" (ticpf4110m000) SITUATION DESCRIPTION: It is possible to enter and save a blank 'Price list matrix' code in "Maintain Price List Matrix Codes" (tipcf4110m000). Once saved, it is not possible to delete the blank record. SOLUTION DESCRIPTION: It is not possible to enter and save a blank 'Price list matrix' code in "Maintain Price List Matrix Codes" (tipcf4110m000). When a blank 'Price list matrix' is entered, a message "Price list matrix code not allowed" will pop up and user has to enter a new 'Price list matrix' code. Solution: 134147 SITUATION IDENTIFIED IN: "Sales Orders" (tdsls4100s000). "Sales-Order Lines" (tdsls4101s000). SITUATION DESCRIPTION: Wrong country (tdsls401.ccty) defaulted when changing a sales order line's Ship-to Address (tdsls401.stad). SOLUTION DESCRIPTION: Recalculation of tax modified. When changing any tax-related field on a Sales Order Header or Line, tax will be recalculated automatically. No question is asked anymore whether or not to recalculate tax: - When changing the Ship-to Address (tdsls400.stad), a question is asked if all Line's Ship-to addresses should be adjusted. If answered 'Yes', tax is recalculated for all Lines as well. - When changing Invoice-to Address (tdsls400.itad) or Sales Office (tdsls400.cofc), tax code of lines is recalculated without user intervention. - When changing any tax-related field like Warehouse (tdsls401.cwar), Ship-to Address (tdsls401.stad) or Ship-to Business Partner (tdsls401.stbp), no question is asked anymore whether to recalculate tax or not. From now on tax will always be recalculated. Solution: 134151 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: When all receipts are done and a final zero receipts is made for a subcontracting purchase order linked to a production order, the production order is not getting closed and an error message is generated saying "Purchase Invoice for purchase order not yet processed". SOLUTION DESCRIPTION: The zero final receipts made after all receipts done to a subcontracting purchase order will not be a hurdle to close the production order linked to the subcontracting purchase order. Solution: 134160 SITUATION IDENTIFIED IN: "Generate Progress from Planning" (tpppc1240m000) SITUATION DESCRIPTION: Generate progress from planning session has serious performance problems. It takes unreasonably high time to complete the process. This makes it impossible for customers with large data to run this session every day. SOLUTION DESCRIPTION: The performance issue is solved to a greater extent and the process should now be completed in much lesser time. Solution: 134180 SITUATION IDENTIFIED IN: "Purchase Requisitions" (tdpur2101s000) SITUATION DESCRIPTION: 1. Fields "Delivery Warehouse" & "Delivery Address" should be disabled when a Requisition is submitted. This was not happening. 2. While submitting the requisition, "Last Transaction Date" field in table "Purchase Requisitions" and "Requisition Processing Date" field in table "Purchase Requisition Approval" get different time values and hence the Approval field is not accessible. SOLUTION DESCRIPTION: Now, if a requisition is submitted, delivery warehouse and address cannot be changed. Also, the "Last Transaction Date" field in table "Purchase Requisitions" and "Requisition Processing Date" field in table "Purchase Requisition Approval" will have same values when a requisition is submitted so that Approval is done. Solution: 134182 SITUATION IDENTIFIED IN: "Convert Electronic Bank Statements" (tfcmg5202m000) SITUATION DESCRIPTION: During conversion of Electronic Bank Statements (tfcmg5202m000), amounts are converted to 0.00. SOLUTION DESCRIPTION: Amounts are converted correctly during the conversion of Electronic Bank Statements. Solution: 134184 SITUATION IDENTIFIED IN: "help viewer" (ttstphelp) SITUATION DESCRIPTION: When in a help text an enum description is shown and that enum contains a dot and there also exist a simular domain (not enum) without a dot then the enum description is not shown correctly. Example domain tccitt is a domain type string and domain tccitt.type is a domain of type enum. SOLUTION DESCRIPTION: Now the correct enum description of the right domain is shown Solution: 134189 SITUATION IDENTIFIED IN: "Simulate Orders" (cprrp1210m000) SITUATION DESCRIPTION: When using 24 hours a day calendar and calculation of time segment of Planned Purchase Order Finish Date results in 00:00:00 then a wrong Planned Purchase Order Finish Date is created. In that case 1 second is subtracted which results in previous date at 23:59:59 hours which is wrong. Currently in Reschedule signals only dates without time segment are advised which is confusing in cases as described above. SOLUTION DESCRIPTION: When time segment of Planned Purchase Order Finish Date results in 00:00:00 then no 1 second subtractions takes place anymore. Modifications for 91300 and 128730 are removed. To prevent confusion, Time segment of reschedule date will be displayed in Reschedule signals now. Order finish date is "The moment on which the order has finished." Solution: 134196 SITUATION IDENTIFIED IN: "Process Solutions" (ttpmc2101m000) SITUATION DESCRIPTION: If the PMC B-Language Support copied a help text from English to the B-Language during the installation of a solution, the B-Language help text could not be exported with the session "Copy Language-dependent Software Components" (ttadv6230m000). The reason was that no Help Text Status record was written for the B-Language help text. SOLUTION DESCRIPTION: Now a Help Text Status record is written for the B-Language help text during the installation of a solution; the help text can be exported. Solution: 134197 SITUATION IDENTIFIED IN: "Receipt Lines" (whinh3120s000) SITUATION DESCRIPTION: Error messages appears and saving of receipt line is not possible, when an "Unexpected Receipt" line is created and the order quantity is entered. There are two situations in which unexpected receipts can occur 1. When "Unexpected Receipts" is selected through the specific option in warehouse receipts. 2. When the final receipt flag is set to 'Yes' for the inbound order line, and more goods are received for the same inbound order line. SOLUTION DESCRIPTION: Error messages do not appear, when an "Unexpected Receipt" line is created and the order quantity is entered, and saving of Receipt line is possible. Solution: 134205 SITUATION IDENTIFIED IN: "Export Version Dump" (tgbrg1235m000) SITUATION DESCRIPTION: When we export in language English and we have a help-text in Dutch, but not in English, the export gives an error-message and the session ends. This is not correct behavior. SOLUTION DESCRIPTION: The export session did not check if the help-text was present in other languages then the current language. We changed the session and now the export continues in the above described situation. A message will be shown, when a help-text code is present, but there is no corresponding text found. Solution: 134211 SITUATION IDENTIFIED IN: "Sales Order Lines" (tdsls4501m000). SITUATION DESCRIPTION: For Consignment Invoicing Orders it is allowed to set "Inventory Issue Status" (tdsls401.isss) on a Sales Order Line to "Issue Components". This can be confusing because solution #110442-9 made this impossible for Consignment Replenishment orders. SOLUTION DESCRIPTION: "Inventory Issue Status" (tdsls401.isss) cannot be set to "Issue Components" in case of Consignment Invoicing Orders. Due to limitations of Warehousing Module in handling generated Transfer Orders, solution #110442-9 made it impossible to use this status in case of Consignment Replenishment Orders. Only status "Issue Main Item" is valid in that case. For consistency reasons this now also applies to Consignment Invoicing Orders. Solution: 134217 SITUATION IDENTIFIED IN: "Projects" (tcmcs0152s000) SITUATION DESCRIPTION: The implementation of a tools variable was changed/corrected. Prior to the change, changing the project search key from session 'Projects' (tcmcs0152s000) did not update the search key in Manufacturing (module tipcs) or in Project (module tppdm). SOLUTION DESCRIPTION: After the change of the tools variable, changing the project search key from session 'Projects' (tcmcs0152s000) does update the search key in Manufacturing (module tipcs) or in Project (module tppdm). Solution: 134224 SITUATION IDENTIFIED IN: "Delete or Print Unused Texts" (tttxt1210m000) SITUATION DESCRIPTION: Delete Unused Text (tttxt1210m000) ends with Oracle error ora1555: 'Snapshot too old'. SOLUTION DESCRIPTION: Too avoid the Oracle error the processing of the text range has been split into smaller parts. Now 10.000 records are processed, and then the next 10.000 and so on, until the complete range of texts has been processed. Solution: 134233 SITUATION IDENTIFIED IN: "Addresses" (tccom4530m000) SITUATION DESCRIPTION: When selecting an address and then press the print button the selected address is not transferred to the print session. SOLUTION DESCRIPTION: When an address is selected this will be transferred to the print session as an address print range. When there is no record selected the full range for addresses is taken as print selection. Solution: 134237 SITUATION IDENTIFIED IN: standard program. SITUATION DESCRIPTION: Defects solved in B50b136040 Descriptions: - Defect 136040 AFS/OW events removed by AFS causing problems in OW SOLUTION DESCRIPTION: These defects are solved in the standard program Solution: 134256 SITUATION IDENTIFIED IN: "Warehousing Orders" (whinh2100m000) SITUATION DESCRIPTION: A production order is created and released. The needed material for this order has the flag "Direct Initiate Inventory Issue" ticked including "Direct Process Warehouse Order Line" for the same material. When the order quantity is changed after release of the production order, the outbound order lines are incorrect in warehousing. SOLUTION DESCRIPTION: The flag, "Direct Initiate Inventory Issue" is ONLY used, by releasing a production order to initiate the Inventory Issue. (See the help text) This flag has no influence when after order release the order quantity is changed. No automatic correction of the outbound order lines in warehousing is done. Consequently in session "Material to Issue for Production Orders" (ticst0101m000) the estimated quantity is decreased, actual quantity is still actual issued quantity (too high compared with the new estimated) and the "to issue" field is filled with the difference quantity between estimated and actual quantity. This "to issue" quantity MUST be issued by hand. When done, the inbound and outbound lines are updated correctly. Solution: 134258 SITUATION IDENTIFIED IN: "Reprint Invoices" (cisli2405m000) SITUATION DESCRIPTION: When the invoices are reprinted, then the page numbers are not printed correctly. SOLUTION DESCRIPTION: When the invoices are reprinted, then the page numbers are to be printed correctly. Solution: 134263 SITUATION IDENTIFIED IN: "Call" (tsclm1100m000) "Serialized Items" (tscfg2100m000) SITUATION DESCRIPTION: The Help text, of field Warranty Type (tscfg020.wttp) in session "Warranties" (tscfg0120s000) is not correct. It states that the Suppliers Warranty is valid from the installation date and that the Own/Dealer Warranty is valid from the delivery date. It should be the other way round. SOLUTION DESCRIPTION: The help texts have been changed. As in an earlier solution already mentioned: Warranty type Start Date Own/Dealer's Warranty Installation date Supplier's Warranty Delivery date Non Specific Warranty Lesser of Installation & Delivery date Solution: 134275 SITUATION IDENTIFIED IN: "Rebuild Planned Inventory Transactions " (whinp1200m000) SITUATION DESCRIPTION: While rebuilding the planned inventory transactions, session fails with a heap space error. SOLUTION DESCRIPTION: Session runs and completes the rebuilding of planned inventory transactions with out any heap space error. Solution: 134276 SITUATION IDENTIFIED IN: "Material to Issue for Production Orders" (ticst1501m000) SITUATION DESCRIPTION: The subsequent delivery field (ticst001.subd) is stored with a value of 0 (zero) but a small residual value is stored in the database level instead of 0.0000, while reporting operations completed and backflushing the material in session "Report Operations Completed" (tisfc0530m000). SOLUTION DESCRIPTION: The subsequent delivery field (ticst001.subd) is stored with a value of 0 (zero) and at the database level also the value is stored as 0.0000 without any residual values, while reporting operations completed and backflushing the material in session "Report Operations Completed" (tisfc0530m000). Solution: 134280 SITUATION IDENTIFIED IN: "Text editor" (tttxt2230m000) SITUATION DESCRIPTION: Some texts not possible to edit after creating. SOLUTION DESCRIPTION: Fix was done. Solution: 134289 SITUATION IDENTIFIED IN: "Service Order Actual Material Costs" (tssoc2121s000) SITUATION DESCRIPTION: Labels 'Financial Company' and 'Line' are missing on the third form of the sessions "Service Order Actual Material Costs" (tssoc2121s000) and "Service Order Actual Other Costs" (tssoc2141s000) SOLUTION DESCRIPTION: Labels 'Financial Company' and 'Line' are present again on the third form of the sessions "Service Order Actual Material Costs" (tssoc2121s000) and "Service Order Actual Other Costs" (tssoc2141s000) Solution: 134291 SITUATION IDENTIFIED IN: "Transactions" (tfgld1101m000) SITUATION DESCRIPTION: In a multi-finance/single-logistics environment, following problem occurs: When linking service order lines to a financial document, one can choose a service order line of a service order that has got another financial company than the target company on the document in Finance. But when finalizing the batch, error message " The BaanERP Service amount not completely split up" (tfglds0634) appears. SOLUTION DESCRIPTION: 1. It is not possible to link a service order line of a service order that has got another financial company than the target company on the document in Finance. 2. When finalizing a batch, the service order lines will be checked in order to find out if the costs are split up correctly. Here, the amount given from Finance is checked with the amount retrieved from the service order lines. These amounts are converted in the same currency (local currency). Solution: 134292 SITUATION IDENTIFIED IN: "Copy Routing" (tirou2201m000) SITUATION DESCRIPTION: When two existing routing code with operations are to be copied into another target routing and if the position numbers of the operations are the same, the routing operations are not copied correctly to the target routing. In short, the copy process 'Add' does not work correctly. SOLUTION DESCRIPTION: Routing operations from two source routings can now successfully being copied to a target routing with the copy process as 'Add' via the session "Copy Routing" (tirou2201m000). Solution: 134293 SITUATION IDENTIFIED IN: "Receipt Correction" (whinh3121s000) SITUATION DESCRIPTION: When trying to do a receipt correction (session whinh3121s000 "Receipt correction") for a subcontracting item message "Receipt correction not possible" arises. SOLUTION DESCRIPTION: It is possible to do a receipt correction for Cost, Service or Subcontracting items, therefore message "Receipt correction not possible" does not pop up. Solution: 134301 SITUATION IDENTIFIED IN: "Generate Cycle-Counting Orders" (whinh5200m000) SITUATION DESCRIPTION: The fatal error 606 can occur when several count numbers within 1 order exist. This is due to the fact that the needed order header doesn't exist. SOLUTION DESCRIPTION: The check on the existence of the order header is changed so that if the header doesn't exist it will be created. Solution: 134305 SITUATION IDENTIFIED IN: "Copy Budgets" (tffbs1202m000) SITUATION DESCRIPTION: When a budget is copied with the actual via session Copy Budgets (tffbs1202m000), there is a difference between the amounts in tfgld205, where the amounts are always positive with the correct debit/credit indication, while the credit amounts in session "Budget Amounts and Quantities per Period" (tffbs1101m000) are always negative. The report of "Print Budget Amounts and quantities" (tffam1400m000) prints wrong values. Also the total calculation for the quantities is wrong. The debit/credit indicator is not taken into account. SOLUTION DESCRIPTION: The amounts of the actual are copied correctly and the calculation of the totals for the quantities is correct. It takes the debit/credit indicator into account. Solution: 134310 SITUATION IDENTIFIED IN: "Print Inbound Data" (whinh3460m000) SITUATION DESCRIPTION: Size of label "View Advice To Be Put Away" (FSinh2515m000.03) is smaller than the display width in German language (language 3) SOLUTION DESCRIPTION: Size of label altered from 30 to 34 to accommodate the German language width. Solution: 134316 SITUATION IDENTIFIED IN: "Receipts" (whinh3520m000) SITUATION DESCRIPTION: When trying to confirm a receipt line that has a zero receipt quantity and "Final Receipt" flag checked, an empty message is displayed and the receipt line is not confirmed. SOLUTION DESCRIPTION: It is possible to confirm a receipt line that has zero receipt quantity and "Final Receipt" flag checked without any error messages. Solution: 134330 SITUATION IDENTIFIED IN: "Split Shipment" (whinh4231m000) SITUATION DESCRIPTION: It can take too long for this session to present the first set of data. SOLUTION DESCRIPTION: The initial search routine is changed so that it is more logic and that the search time is shorter. Solution: 134333 SITUATION IDENTIFIED IN: "Copy Sales Order" (tdsls4201s000). SITUATION DESCRIPTION: 1. New form is not showing new label "Use Delivered Quantities" (tdsls4201.03) as delivered via solution #116720. 2. Label for field tdsls4201s0001.copy.only.header very unclear in Dutch ("Alleen kop kopieren" instead of "Alleen kop kop.") SOLUTION DESCRIPTION: This solutions solves 2 issues mentioned above. 1.Form "Copy Sales Order" (tdsls4201s0001), as it was modified by solution #116720, is correctly displayed. With solution #116720 a new label was introduced for field tdsls4201s0001.add.up.deliveries. The description of this label was changed from "Cumulate Deliveries" to "Use Delivered Quantities". 2. For Dutch cusomers: a more speaking label is used. Description "Alleen kop kopieren" is now used instead of "Alleen kop kop." (field: tdsls4201s0001.copy.only.header). Solution: 134342 SITUATION IDENTIFIED IN: "Print Aging Summary" (tfacr2411m000) SITUATION DESCRIPTION: If invoice/credit note fiscal period is greater than the receipts/assignment periods then wrong data is printed. SOLUTION DESCRIPTION: If invoice/credit note fiscal period is greater than the receipts/assignment periods, the balance is now correctly calculated. Solution: 134349 SITUATION IDENTIFIED IN: "Purchase Order Lines" (tdpur4101s000) SITUATION DESCRIPTION: If the Integration Mapping Scheme for the Purchase / General Costs is maintained with the Logistic Company "0", then the Dimensions are not defaulted correctly when user maintains a Purchase Order Line for a Cost Item. The Ledger Account is defaulted correctly on to the Purchase Order Line even when the Integration-Mapping Scheme is maintained for the Logistic Company "0". SOLUTION DESCRIPTION: The dimensions are defaulted now even when the Integration-Mapping Scheme is maintained with the Logistic Company "0". Solution: 134369 SITUATION IDENTIFIED IN: "Purchase Budgets" (tdpst0550m000) SITUATION DESCRIPTION: The session description is not correct, for session "tdpst0550m000", and also the zoom session description under specific is not correct for language 1 (Dutch). SOLUTION DESCRIPTION: The system will display the correct session description and also, correct zoom session description under specific in the session "tdpst0550m000" for language 1 (Dutch). Solution: 134378 SITUATION IDENTIFIED IN: "Sales Orders" (tdsls4100s000) SITUATION DESCRIPTION: Sales Order Line is recalculated with blank tax code, when changing any tax-related field on the corresponding sales order Header. This only applies to the FIRST Line; for subsequent lines the tax code is calculated correctly. However, if the combination of tax country and blank tax code is not a valid one, no changes will be made to any of the lines. SOLUTION DESCRIPTION: When changing any tax-related field on a Sales Order Header, forcing a recalculation of tax for all related Sales Order Lines, recalculation should be done correctly. Solution: 134380 SITUATION IDENTIFIED IN: "Specifications Delivered, not yet invoiced " (tfacr1432m000) SITUATION DESCRIPTION: On the Report ' Specifications Delivered, not yet invoiced ' the Order-line Status is needed for further interpretation of the results. This status was displayed incorrectly which led to confusion in which action should be taken. SOLUTION DESCRIPTION: The Report ' Specifications Delivered, not yet invoiced ' will now print a status 'Open' or 'Closed' depending on the order-line status within logistics. The status is printed per sales orderline. If the issue is booked and the cost of goods sold is not booked then the status is 'Open' which means invoicing should take place. If the issue and the cost of goods sold is booked then the status is 'Closed'. Please note that if a sales orderline has backorders then the status can switch from 'Closed' to 'Open'. This happens when a backorder is confirmed and for that backorder only the issue is booked and not the cost of goods sold. It is not possible to print tfacr1432m000 per sales orderline sequence. Solution: 134384 SITUATION IDENTIFIED IN: "Maintain Sales Invoices" (tfacr1110m000) SITUATION DESCRIPTION: When the session " print non finalized transactions" is executed, the text entered in the Sales invoice header is not printed for the control account . SOLUTION DESCRIPTION: Now, when the session " print non finalized transactions" is executed, the text entered in the Sales invoice header is printed for the control account. Solution: 134412 SITUATION IDENTIFIED IN: "Print Shipments" (whinh4430m000) SITUATION DESCRIPTION: In session "Print Shipments" (whinh4430m000), shipment lines are present but not printed. SOLUTION DESCRIPTION: Installation of latest report solves the problem: shipment lines can be printed. Solution: 134421 SITUATION IDENTIFIED IN: "Remove Closed Warehousing Orders" (whinh2250m000) SITUATION DESCRIPTION: It is not possible to remove Receipt Headers via a standard Baan session. SOLUTION DESCRIPTION: The functionality of removing receipt headers has been added to session "Remove Closed Warehousing Orders" (whinh2250m000). Receipt headers for which no receipt lines do exist will be deleted when running this session. Solution: 134433 SITUATION IDENTIFIED IN: "Generate Invoices by Selfbilling" (tfacp2290m000) SITUATION DESCRIPTION: The invoice amount generated by the selfbilling process was based on the Order amount and order quantity. When there are multiple receipts, then the Invoice amount calculated with this method differed from the Invoice amount calculated based on the Quantity and price by few cents. SOLUTION DESCRIPTION: The Invoice amount is now calculated based on the Receipt quantity and the Price and discount information from the order. Solution: 134436 SITUATION IDENTIFIED IN: "Print Machine Utilization by Week " (tisfc1407m000) SITUATION DESCRIPTION: When machine utilization is printed, the report usually shows operation with a 'S' where 'S' indicates that an operation may start. This is not printed when the utilization is printed without selecting the option 'Previous Operation Must Be Completed'. SOLUTION DESCRIPTION: The indication for a start operation 'S' is printed when the utilization by machine is printed without the option 'Previous Operation Must Be Completed'. Solution: 134438 SITUATION IDENTIFIED IN: "Sales Orders" (tdsls4100s000) SITUATION DESCRIPTION: Help text for field 'Planned Receipt Date' on Sales Order Header (tdsls4100s000) and Sales Order Lines (tdsls4101s000) is incorrect. It says: "An anticipated receipt that corresponds to an open purchase order or open production order" SOLUTION DESCRIPTION: Help text on the 'Planned Receipt Date' is now: The date on which the customer is planned to receive the goods" Solution: 134448 SITUATION IDENTIFIED IN: "Business Partners by Project" (tppdm6101s000) SITUATION DESCRIPTION: When filling in Business Partners that have Signals linked to them, these Signals are not or incorrectly displayed. SOLUTION DESCRIPTION: Now the signals are correctly displayed when a Business Partner is filled in that has a Signal linked to it. Solution: 134450 SITUATION IDENTIFIED IN: "Bank Balances" (tfcmg2101s000) SITUATION DESCRIPTION: Opening Balance is not correctly calculated within session 'Bank Balances' (tfcmg2101s000) when option 'Other Currencies allowed' is enabled for the Bank relation (tfcmg0510m000) and an opening balance exists in more than one currency. SOLUTION DESCRIPTION: Opening balance is calculated correctly in session 'Bank Balances'. Solution: 134451 SITUATION DESCRIPTION: When reset the status of a voided check, the status of the anticipated check associated to the voided check remains unchanged. Due to this duplicate anticipated checks are created during reprinting the damaged checks. SOLUTION DESCRIPTION: If the status of a voided check associated with an anticipated check is reset, all checks, which are related to the same anticipated check, are reset to the same status. Solution: 134461 SITUATION IDENTIFIED IN: "Sales Quotation Lines" (tdsls1101s000) SITUATION DESCRIPTION: When entering a Sales Quotation Line (tdsls1101s000), the vat code is defaulted. When the vat code of the Item Sales Data is used, and this code does not exist for the vat-country, the message "Tax Code by Country not found" is displayed, and the line cannot be saved. SOLUTION DESCRIPTION: When the vat code of the item sales data is used, and this code does not exist for the vat-country, the tax code is made empty. Sales Order Lines and Sales Quotation Lines are working similarly now. Solution: 134464 SITUATION IDENTIFIED IN: "Generate control data" (tpptc1230m000) SITUATION DESCRIPTION: When two users use generate control data at the same time for the same project the quantities generated from budget get doubled. SOLUTION DESCRIPTION: An application lock is been developed which will not allow the second user to run the session for the same project till the first user finishes the process and hence the quantities getting doubled while generating the data is prevented. Solution: 134465 SITUATION IDENTIFIED IN: "Print Composed Direct Debits" (tfcmg4403m000) SITUATION DESCRIPTION: In report "Print Composed Direct Debits" (tfcmg4403m000), the business partner name is printed as "********". SOLUTION DESCRIPTION: The name of the Business Partner mentioned in the address of the pay-by business partner is printed on the report. Solution: 134471 SITUATION IDENTIFIED IN: "Print Project Work In Process" (tipcs3480m000) SITUATION DESCRIPTION: 1. Sales Issues on PCS project are recognized as "Incoming value" on both the "Interim Sales Delivery (PCS / WIP)" and "Inventory" accounts. This is incorrect and results in an overstatement of the PCS wip account. The amount being issued should be recognized as incoming on the "Interim Sales Delivery (PCS / WIP)" account and as Outgoing on the "Inventory" account. 2. When for a PCS project no transactions are posted yet, values are being printed twice with a blank ledger account, although the message "Only posted integration Transactions will be printed" is printed. SOLUTION DESCRIPTION: 1. In session "Print Project Work In Process" (tipcs3480m000) with option Detail level "By Ledger account" the Sales Issues on a PCS project are now recognized as incoming on the "Interim Sales Delivery (PCS / WIP)" account and as Outgoing on the "Inventory" account. 2. With option Detail level "By Ledger account" values are now only being printed when they are posted. Solution: 134488 SITUATION IDENTIFIED IN: "Update Vendor Rating" (tdpur8850m000) SITUATION DESCRIPTION: The Linear Delivery Time Vendor Rating for a Purchase Order is incorrect when the Current Planned Delivery Date is equal to the Actual Delivery Date and when Planned Delivery Date is equal to the Order Date on the Purchase Order Line. SOLUTION DESCRIPTION: Calculation of Linear Delivery Time Vendor Rating for a Purchase Order is corrected even when the Current Planned Delivery Date is equal to the Actual Delivery Date and when Planned Delivery Date is equal to the Order Date on the Purchase Order Line. Solution: 134491 SITUATION IDENTIFIED IN: "Receipts" (whinh3520m000) SITUATION DESCRIPTION: In a triangular invoicing scenario, zero prices and amounts are booked for sales return orders when transfer pricing method is "Valuation Price". This situation occurs when the sales return order is not linked to a normal sales order and no surcharges are involved. SOLUTION DESCRIPTION: Prices and amounts are calculated properly based on the valuation price and the amounts are displayed correctly. Solution: 134493 SITUATION IDENTIFIED IN: "Print Variance Analysis" (tfacp1460m000) SITUATION DESCRIPTION: The rounding of standard cost price and purchase price is done on two decimals instead of four. SOLUTION DESCRIPTION: Because of changing the print format the rounding of standard cost price and purchase price is done on four decimals. Solution: 134499 SITUATION IDENTIFIED IN: "Print Inventory Transactions" (whinr1400m000) SITUATION DESCRIPTION: The performance of this session could be improved. SOLUTION DESCRIPTION: By changing the software, responsible for finding the needed data, the performance has improved. Solution: 134500 SITUATION IDENTIFIED IN: "One-time Business Partners Addresses" (tfacp1102s000) SITUATION DESCRIPTION: In case an invoice with bank data and one-time business partner address is entered, the bank data fields remain disabled. This is not correct. After saving and clicking on the address field the bank data fields are enabled SOLUTION DESCRIPTION: After installing this solution the bank data fields are enabled when entering an invoice with bank data and one-time business partner address Solution: 134516 SITUATION IDENTIFIED IN: "Print GRNI Reconciliation Balances" (tfacp1435m000) "Accept values of Receivable Invoices" (tfacp1535m000) SITUATION DESCRIPTION: 1. When zoom to purchase orders is done in session "Print GRNI Reconciliation Balances" (tfacp1435m000) only the self-billing invoices are displayed. 2. In the above session, the report "Balances per Order Line (View by Document)" (tfacp143511000) doesn't print the purchase invoice number of the approval document. 3. The balance displayed in session "GRNI Reconciliation" (tfacp1535m000) is not updated after inserting a correction document. SOLUTION DESCRIPTION: 1. All the orders will be displayed when zoom on purchase order is clicked. (B50_c, B52_a). 2. The purchase invoice document is printed on the report for approval documents. (B52_a). 3. The balances are calculated correctly after inserting a correction document. (B50_b, B50_c, B52_a). Solution: 134520 SITUATION IDENTIFIED IN: "Sales Invoice details" (tfacr2100s000) SITUATION DESCRIPTION: 'Due Date' of sales invoice detail does not change though the date of 'Planned Receipt Date' in receipt schedule is changed. SOLUTION DESCRIPTION: Now, 'Due Date' of sales invoices detail changes whenever the date of 'Planned Receipt Date' in receipt schedule is changed. Solution: 134525 SITUATION IDENTIFIED IN: "Compose/Print/Post Invoices" (cisli2200m000) SITUATION DESCRIPTION: Sales/Issue and Sales Invoicing Sales/COGS are not congruent if rates are changed after shipments. For COGS bookings, the same rates, as on delivery date has to be used. SOLUTION DESCRIPTION: Now the COGS are booked using the same rate as on the delivery date. So the Issue and the COGS tally. Solution: 134530 SITUATION IDENTIFIED IN: "Print Sales Orders" (tdsls4405m000) SITUATION DESCRIPTION: The Sales Order Report is printed with option 'Order Lines' checked. When a sales order is split and partially delivered, the report shows incorrect values for the delivered quantities and for amounts. SOLUTION DESCRIPTION: Quantities and amounts on the report are correct. The delivered quantity for a total line is the sum of all the delivered quantities of the details. The amounts are based on the setting of the field 'Calculate Amount Based on' Solution: 134531 SITUATION IDENTIFIED IN: "Register Purchase Invoices" (tfacp1110s000) SITUATION DESCRIPTION: When the level of tax calculation is set to Transaction Line and a Purchase Order is entered with tax specified, the amount defaulted in session "tfacp1110s000 - Register Purchase Invoices" is the Order Amount minus the Vat amount. When the tax calculation is set to header now the tax is recalculated taking the amount defaulted as gross. When from the beginning the level of vat calculation is set to header all defaulting is done correctly. SOLUTION DESCRIPTION: When the level of vat calculation is set to transaction line the gross order amount is defaulted now. The amount is now similar defaulted as done with level of tax calculation set to header. Solution: 134537 SITUATION IDENTIFIED IN: "Correct COGS Integrations" (cicor0111m000) SITUATION DESCRIPTION: Missing label "Direct Delivery", in report "Correct COGS SLI245 and SLS401"(cicor0111111004). SOLUTION DESCRIPTION: Now the label has been linked. Solution: 134546 SITUATION IDENTIFIED IN: "Section codes" (tfgldl108m001l) SITUATION DESCRIPTION: The next labels were missing in the Japanese localization: On form gld1520 the label Taxable amount in HC, on form gld1402 the label Print Header report, form cmgl170 the label Date details, and on report cor3401 the labels Cono and Type and on report cmgl4221 the label for the dot, and on the form gldl108 a label for the description was programmed twice, so one is removed. SOLUTION DESCRIPTION: The mentioned forms, reports and labels are delivered Solution: 134554 SITUATION IDENTIFIED IN: "Print Subcontracting Invoices" (tfacp3460m000) SITUATION DESCRIPTION: When running session "Printing Subcontracting Invoices - tfacp3460m000" on the report the "Total Amount" is always zero. SOLUTION DESCRIPTION: Because of changing the layout of the report and getting first the total amount of the invoice, the total amount is printed correctly. Solution: 134557 SITUATION IDENTIFIED IN: "Generate Update VRC Structure" (ttpmc2240s000) SITUATION DESCRIPTION: Create Runtime Data Dictionary for a package combination could fail after running the session "Generate Update VRC Structure" (ttpmc2240s000/ttpmc2240m000). If you decided not to create an Update VRC for a certain package (which is not good practice!), the session could change a package combination to use this Update VRC. In the session "Packages by Package Combination" (ttaad1121m000), the VRC description was shown with asterisks (*****). In BaanERP 5.0 and BaanERP 5.2 this problem occurred mainly for the "ed" package. The session skipped always the creation of an Update VRC for this package, because this package is exclusively and in a special way used within the Baan Enterprise Modeler (DEM). But the package combination was changed automatically to use the (not created) Update VRC. SOLUTION DESCRIPTION: Now the Package VRC in the package combination is only changed to the Update VRC if the Update VRC exists for the package. Solution: 134561 SITUATION IDENTIFIED IN: standard program. SITUATION DESCRIPTION: Defects solved in B50b 136216 Descriptions: - Defect 136216 AFS set.report function not generated when form has no print option SOLUTION DESCRIPTION: These defects are solved in the standard program Solution: 134562 SITUATION IDENTIFIED IN: "Import/Export Statistics" (tccom7571m000) SITUATION DESCRIPTION: The parameter "Method of Logging Cost/Service Items" as defined in session "Intra EU Transaction Parameters" (tccom7500m000) is not taken into account when it is set to "If Commodity Code Filled". This means that import/export statistics are also logged for cost/service items without commodity code in this case. SOLUTION DESCRIPTION: If the parameter "Method of Logging Cost/Service Items" as defined in session "Intra EU Transaction Parameters" (tccom7500m000) is set to "If Commodity Code Filled", then import/export statistics are only logged for cost/service items with a commodity code. Solution: 134563 SITUATION IDENTIFIED IN: "Performance Boosters" (tcmcs0197s000) "Table Boosters" (tcmcs0198s000) SITUATION DESCRIPTION: In the session it is possible to enter a session code for which Performance Boosters cannot be used. SOLUTION DESCRIPTION: The field "session" is disabled. This prevents entering a session code for which Performance Boosters cannot be used. Session codes are automatically entered by the system. Solution: 134572 SITUATION IDENTIFIED IN: "Service Order: Estimated Material Costs" (tssoc2120m000) SITUATION DESCRIPTION: A text is entered in the Material line of a Service Order. A delivery type is chosen which results in the creation of "Issue" type Warehousing Order is chosen. The Service Order is released and the Warehousing Orders are created. How ever the Text entered in the Material Line is not carried to the Warehousing Orders. SOLUTION DESCRIPTION: The Texts entered in the Material Lines are carried on to the Warehousing Orders created for those Material Lines. This enables the user to print the Service Order Material Text on the Goods Receive Note or on the Packing Slip. Special Note: =========== Baan provides the facility of hiding / printing a text or a part of a text in the Reports. 1) When a line in the Text is preceded by a '<' (less than) symbol, this line is meant for internal reports only (example Goods Receive Note). These lines will not be printed on external documents (example Packing Slip). 2) When a line in the Text is preceded by a '>' (greater than) symbol, this line is meant for external reports only (example Packing Slip). These lines will not be printed on internal documents (example Goods Receive Note). Solution: 134575 SITUATION IDENTIFIED IN: "Print Specifications Delivered not yet Invoiced" (tfacr1432m000) SITUATION DESCRIPTION: The report of session tfacr1432m000 will compare the Sales Invoice amounts with the Sales Issue amounts. For closed Sales Orders no difference should exist while in practice in some situations an unexpected difference may occur. SOLUTION DESCRIPTION: A correction program has been developed to correct differences between the Sales Invoice amounts and the Sales Issue amounts. By inserting financial integration transactions this difference is cleared. Furthermore the COGS amounts stored on the Sales Order Line, Sales Order History Line and the Sales Order Invoice Line are updated. An option is available to execute this correction program in test mode. In test mode no actual table updates will be performed. Before the correction program is executed in update mode the output reported in test mode should be carefully analyzed. Financial integration origins (TROR) and financial integrations types (FITR) considered by this correction program are: - Sales / General Cost - Sales / Direct Delivery - Sales / Issue - Sales / Issue (Invoiced) - Warehousing Consignment / Issue - Warehousing Consignment / Issue (Invoiced) - Service / Approved for Invoicing - Sales Invoicing (Sales) / COGS (material) - Sales Invoicing (Sales) / COGS (operation) - Sales Invoicing (Sales) / COGS (surcharge) - Sales Invoicing (Sales) / COGS (general) - Sales Invoicing (Service) / COGS (material) - Sales Invoicing (Service) / COGS (operation) - Sales Invoicing (Service) / COGS (surcharge) - Sales Invoicing (Service) / COGS (general) Several options are available when executing the correction program: Fiscal Year/Period: When left empty the fiscal year and period is determined based on the original transaction date of the corrected transaction. In case the fiscal year and period are closed the transaction will be booked into the next open period based on the parameter "Posting to next open period allowed" (tfgld4150s000) The user can overrule the automatic determination of the fiscal year and period by filling this field on the form. Only an open fiscal year and period can be chosen. Reporting Year/Period: Logic identical to fiscal year/period field Tolerance: The allowed tolerance for the difference between the issue and COGS amounts Correct only when difference on Specification Delivered not yet invoiced: When this option is set no financial integration transactions will be inserted when there is no difference reported by tfacr1432m000 on a certain interim account even though there might be a difference between the issue/COGS amount stored in logistics and finance. Consider Delivered: When this option is not selected a possible difference between the issue amount in finance and logistics is not corrected. Consider Invoiced: When this option is not selected a possible difference between the COGS amount in finance and logistics is not corrected Update mode: Determines whether this correction program is executed in test or update mode Currency: The currency in which the found differences should be reported. In an Dependent or Single currency system this will always be the reference currency. The "rotate currency" button is only enabled in an Independent currency system, which will allow the user to rotate between the different defined home currencies. Some things have to be taken care of when executing this correction program: 1) Execution in Job mode When executing the correction program in Job mode care has to be taken when selecting a device of type 'file' (when selecting an actual printer device the issue described below is not applicable). This is because the correction program will report the corrected data in two separate reports, while when running in Job mode only one output file can be specified. To prevent both reports do overwrite each other a device of type 'append to file' has to be chosen. The second report output will then be appended to the first report output in the same output file. 2) Archiving Once the sales order history is archived this program is not able to correct the financial transactions anymore. Archived Sales Order history lines will just not be considered. The inventory transactions stored in Warehousing are also needed by this correction program and can be archived as well. In case an issue/receipt is selected (as it still exists in the sales order history) for correction while the transaction date Is before the last archiving date a message will be displayed and the correction is skipped. Furthermore the financial integration transactions can have been archived which are needed to be able to correct as well. Since its not possible to determine whether a certain financial integration transaction is just missing or archived care has to be taken with this scenario as the correction program is not capable of preventing unnecessary insertion of archived transactions. So incase the correction program inserts integration transactions before the last archive action those orders should be skipped manually. Solution: 134580 SITUATION IDENTIFIED IN: "Print Job History" (ttaad5410m000) SITUATION DESCRIPTION: In 7.3_a you get the following error when running the session: SQLState QP010: Invalid parameter type (error 0) (read.main.table() in object ottaad5410 This is cause by comparing too many fields with the index of the main table. SOLUTION DESCRIPTION: Only the relevant fields are now used for the main table. Solution: 134584 SITUATION IDENTIFIED IN: "Post Electronic Bank Statements" (tfcmg5222m000) SITUATION DESCRIPTION: The posting of EBS batches with session 'Post Electronic Bank Statements' (tfcmg5222m000) stops in case of doubtful invoice-to Business Partners. The posting can be continued after changing the status of the Business Partner into 'Active'. Everytime the process stops a new batch is created. SOLUTION DESCRIPTION: Transactions of doubtful invoice-to Business Partners within an EBS batch can be posted. Solution: 134594 SITUATION IDENTIFIED IN: "Origin by Lot" (whltc3501m000) "Origin by Order" (whltc3502m000) SITUATION DESCRIPTION: When receiving a particular lot for an order line multiple times, the total quantity received is calculated and displayed in the column "Quantity". This label description is confusing and also the help text does not cover the real functionality. SOLUTION DESCRIPTION: The description of the field 'Quantity' is changed to 'Total Quantity received'. The help text of the field describes clearly that the above field will display the total quantity received per order line for the same lot. Solution: 134596 SITUATION IDENTIFIED IN: "Accept Values for GRNI Reconciliation" (tfacp1535m000) SITUATION DESCRIPTION: When creating corrections for GRNI, it was not possible to create rounding corrections correctly. It was creating rounding corrections always the on reference currency. Also in session "Insert Correction" (tfacp1137s000), it was not possible to enter the transaction currency and transaction amount. SOLUTION DESCRIPTION: 2 new options have been provided in session "Accept Values for GRNI Reconciliation" (tfacp1535m000). The first option "Insert Correction" can be used to enter a correction amount to the GRNI record selected. In this option the transaction currency and transaction amount fields are enabled and the user can modify the transaction amount or the amounts in home currency to make the correct correction to balance the order. In the second option "Insert Rounding Correction", the transaction amount field is not enabled. The user can edit only the amount in home currency to make the necessary adjustment to make the order balanced. Solution: 134602 SITUATION IDENTIFIED IN: "Simulate Orders" (cprrp1210m000) SITUATION DESCRIPTION: Fatal error (error 100: duplicate record on cprrp010) while running Simulate Orders SOLUTION DESCRIPTION: No duplicate records will remain because of improved error handling. Solution: 134607 SITUATION IDENTIFIED IN: "Display Browser" (ttstpdisplay) SITUATION DESCRIPTION: While printing the report, the vertical scroll bar does not appear initially when there is more than one page. The scroll bar appears, only after hitting a Page Down or up or resizing. SOLUTION DESCRIPTION: This problem is solved and the vertical scroll bar option is enabled. Solution: 134611 SITUATION IDENTIFIED IN: "Link Suppliers to RFQ's" (tdpur1221m000) SITUATION DESCRIPTION: When Business Partners are linked to RFQ's by session "Link Suppliers to RFQ" & the RFQ is processed, the corresponding RFQ is not deleted in TP package. The same gets deleted when Business Partners are linked by session "Suppliers per RFQ". SOLUTION DESCRIPTION: Now, when Business Partners are linked to RFQ's by session "Link Suppliers to RFQ's", the 'Project' field if present gets filled up in table 'B P's by RFQ lines' and also, if the RFQ is processed, corresponding RFQ line is deleted in TP Projects. Solution: 134612 SITUATION IDENTIFIED IN: "Table Definitions" (ttadv4520m000) SITUATION DESCRIPTION: When we modify the table description of a checked out table, the change is not reflected in SCM. The session "Table Definitions (ttadv4520m000)" shows the old table description. SOLUTION DESCRIPTION: The change is reflected now and the table definition shows the changed description. Solution: 134617 SITUATION IDENTIFIED IN: "Item Purchase Data" (tdipu0101s000) SITUATION DESCRIPTION: Even when there is no change in purchase price, question "Replace latest purchase price by actual purchase price? " followed by another question "Replace average purchase price by actual purchase price?" pops up when we try to view the purchase text of an Item. SOLUTION DESCRIPTION: The questions "Replace latest purchase price by actual purchase price?" and "Replace average purchase price by actual purchase price?" would be popped only when there is a change in the purchase price. Solution: 134620 SITUATION IDENTIFIED IN: "Configure DEM users" ((tgbrg4250m000, tgbrg8240m000)) SITUATION DESCRIPTION: The session to configure a Baan user from DEM does not allow to generate the Worktop settings. SOLUTION DESCRIPTION: With this solution some enhancements for generating a Baan user from DEM are delivered. They will be described per release. Furthermore is in every release changed, that when a new Baan user is created from the DEM employee, that no longer the system login is used from the person who is generating, but the system login will be the same as the generated Baan user name. In this release is only the system login change made, because Worktop is not available for this release. Solution: 134628 SITUATION IDENTIFIED IN: "Print Business Partner wise Aging Analysis" (tfacr2420m000) SITUATION DESCRIPTION: 'Aging analysis of Business partner wise' report is not matching with 'Aging analysis of Business Partner summary' report and it is showing a difference of 0.01 SOLUTION DESCRIPTION: 'Aging analysis of Business partner wise' report is matching with 'Aging analysis of Business Partner summary' report. Solution: 134630 SITUATION IDENTIFIED IN: "Checks" (tfcmg1260s000) "Print Forwarding Notes" (tdsls4421m000) SITUATION DESCRIPTION: Two main sessions exist that display amounts in words: 1. In the sub session 'Transfer Payments' (tfcmg1260m000) payments can get transferred to a check. On these checks the amount is presented both in digits and in words. 2. In the session "Print Forwarding Notes" (tdsls4421m000) bills of lading can be printed. When "Cash on Delivery" has been selected as the type of bill of lading the amount to be received is printed in words as well. Amounts are incorrectly translated to words in Spanish language on check reports. SOLUTION DESCRIPTION: Amounts are correctly translated to words in Spanish language on check reports. Solution: 134631 SITUATION IDENTIFIED IN: "Create GRNI Correction Batch" (tfacp1240m000) SITUATION DESCRIPTION: In session "Create GRNI Correction Batch" (tfacp1240m000), when entering a ledger account with the dimensions set to mandatory, the error message "Dimension is not filled" comes up. SOLUTION DESCRIPTION: It is not possible to enter a contra ledger account with dimensions set to mandatory while creating the GRNI correction batch. It has to be an interim account with no dimensions. The error message has been changed to "Ledger Account with Dimensions not allowed". Solution: 134632 SITUATION IDENTIFIED IN: "Print Reminders" (tdpur4403m000) SITUATION DESCRIPTION: Due to a defect in the internal maintenance tools, the help topic was not included in the proper way in the preceding solution 125878. The help topic was missing in the solution. SOLUTION DESCRIPTION: The missing help topic is included in the current solution. Solution: 134633 SITUATION IDENTIFIED IN: "Archive Projects" (tppdm7820m000) SITUATION DESCRIPTION: When selecting a range of projects to be archived, for every project in that range that has a status lower than "Closed", the system will give a message: "Status must be Closed or Archived". However only projects with these statuses should be considered in the first place. SOLUTION DESCRIPTION: The system now only considers projects with the status "Closed" or "Archived" and the message is no longer given. Solution: 134659 SITUATION IDENTIFIED IN: "Business Partner Totals By Company" (tfacp2534m000) "Business Partner Totals By Company" (tfacr2534m000) SITUATION DESCRIPTION: In session "Business Partner Totals By Company" (tfacp2534m000), the totals are always shown by reference currency. SOLUTION DESCRIPTION: The totals are shown in the home currency. The "Rotate Currency" option has been enabled in the script. Solution: 134670 SITUATION IDENTIFIED IN: "Calculate Cost Prices by Project" (tipcs3250m000) SITUATION DESCRIPTION: When calculating the project costs with simulated price calculation code and project specific operation rates are not defined, then system is not taking the operation rates defined for simulated price calculation code without project. It will take operation rates defined for standard price calculation code without project. SOLUTION DESCRIPTION: On calculating project costs, if project specific operation rates are not defined for a price calculation code, system will take operation rates of same price calculation code without project. If operation rates are not maintained for that price calculation code, then system will give an error message. Solution: 134675 SITUATION IDENTIFIED IN: "Planned PRP Purchase Orders (Subcontracting)" (tppss6512m000) SITUATION DESCRIPTION: When trying to link a Business Partner to a planned subcontracting / equipment PRP purchase order, the error message 'VAT code for buy from BP country not found' pops up. This happens only if there is no Blank VAT code defined in tax code by country for the company and business partner country. SOLUTION DESCRIPTION: Now, correct vat code by country of business partner will found and the business partner can be linked to the purchase order. The above problem is also solved for equipment order. Solution: 134679 SITUATION IDENTIFIED IN: "Purchase Contract Lines" (tdpur3101s000) SITUATION DESCRIPTION: User is not allowed to enter a position number of 9999 in the Purchase Contract Lines but is allowed to enter a position of 9998. SOLUTION DESCRIPTION: User will be allowed to enter a position number of 9999 in the Purchase Contract Lines. Solution: 134680 SITUATION IDENTIFIED IN: "Purchase Order Lines" (tdpur4101s000) SITUATION DESCRIPTION: 1.Confirmed Delivery dates and Changed delivery dates are copied to the detail session, if it is filled in the Total line/ original line of the purchase order. 2.The field VAT Country Code "tdpur401.cvat" in the purchase order lines session "tdpur4101s000" is disabled. 3.When the actual delivery date in the purchase order receipt is set to blank and saved back order is created automatically, Delivery date is blank after creation of the back order also and the receipt is not confirmed. SOLUTION DESCRIPTION: 1.To maintain the dates in the detail session, now the user is been prompted with a question Yes/ No? When the answer is YES, then the dates are maintained in the detail session. If it is not, then the dates are cleared off in the Original as well as Detail lines. And in the Line Details session, to maintain the same dates while splitting the detail, a similar question will be asked. If the answer is YES, then the dates will be maintained and if it is NO, Confirmed and Changed delivery dates will be cleared. It is also noted that if a line has to be split, then the split quantity should be less than the ordered quantity of that particular line. If the user tries to enter the same and greater than the ordered quantity, then a warning message will pop up and the user will be again prompted to correct the order quantity. 2.The field VAT Country Code "tdpur401.ccty" is enabled in the purchase order lines session. 3.When the receipt is saved, and the back order is created delivery date is filled with current date and the receipt is confirmed automatically. Solution: 134682 SITUATION IDENTIFIED IN: "Inventory by Warehouse and Item" (whwmd2515m000) SITUATION DESCRIPTION: The help text for field "Date Hist. Inventory Level" in session "Item Inventory by Warehouse" (whwmd2115s000) indicates that this field represents the date of the most recent inventory transaction that is "registered" for this item/warehouse combination. This is wrong because the field represents the date of the most recent inventory transaction that is "archived". SOLUTION DESCRIPTION: The help text is corrected. Solution: 134683 SITUATION IDENTIFIED IN: "Print Reminders" (tfacr3420m000) SITUATION DESCRIPTION: Interest gets calculated for the unallocated receipts, on re-executing session without closing, after the first execution SOLUTION DESCRIPTION: Interest does not get calculated for the unallocated receipts, on re-executing session without closing, after the first execution Solution: 134695 SITUATION IDENTIFIED IN: "Remove Fully Paid Purchase Invoices" (tfacp2250m000) SITUATION DESCRIPTION: The documents in table "Reference to Finalized Transactions" (tfgld126) are not deleted if the related documents in table "Finalized Transactions" (tfgld106) are deleted. SOLUTION DESCRIPTION: When running session "Remove Fully Paid Purchase Invoices" (tfacp2250m000) or "Remove Fully Paid Sales Invoices)" (facr2260m000), the documents in table "Reference to Finalized Transactions" (tfgld126) are also deleted. Solution: 134699 SITUATION IDENTIFIED IN: "Assign unallocated / advance receipts to invoices" (tfcmg2105s000) "Assign unallocated / advance payments to invoices" (tfcmg2106s000) SITUATION DESCRIPTION: With the sessions "Assign unallocated / advance receipts to invoices" (tfcmg2105s000) and "Assign unallocated / advance payments to invoices" (tfcmg2106s000) unallocated documents can be assigned to invoices. When an unallocated document is assigned to more than one invoice and for that same Business partner a new unallocated document is created with the same document number (but with another line number), the balance of the previous unallocated document has changed after processing this second assignment. Furthermore, the other unallocated documents that were created within the same batch show up in the list for the next unallocated document, even when the balance is zero and they can be maintained as well. This is incorrect. SOLUTION DESCRIPTION: The list in the sessions "Assign unallocated / advance receipts to invoices" (tfcmg2105s000) and "Assign unallocated / advance payments to invoices" (tfcmg2106s000)only shows the other unallocated documents from the same batch, when the balance is unequal to zero. They can only be maintained from the place where they were processed originally. Solution: 134704 SITUATION IDENTIFIED IN: "Direct Network Communication" (ecedi7205m000) SITUATION DESCRIPTION: System is searching for Active Sales Contracts when contracts are not implemented. SOLUTION DESCRIPTION: Improved search for active Sales Contracts. Now Sales Parameter "Contract Module Implemented" (tdsls000.cons.3) is taken into account. If this parameter is set to 'false', no active Sales Contracts are in place. Hence, the search for such a Contract can be aborted. Performance of Sales Order entry (especially when reading Sales Orders by means of EDI) improved significantly. Solution: 134708 SITUATION IDENTIFIED IN: "Print GRNI Reconciliation - Balances" (tfacp1435m000) SITUATION DESCRIPTION: If session "Print GRNI Reconciliation - Balances" (tfacp1435m000), the report "Balances by order line (view by business partner)" (tfacp143513000) is printed, it gives a wrong report in the following situation. The purchase order belongs to one business partner but the purchase order is linked to a purchase invoice with a different business partner. In this scenario the report doesn't print the balances for each business partner separately, hence the sub total on the business partner is showing wrong values. SOLUTION DESCRIPTION: The report now prints correct values. Solution: 134714 SITUATION IDENTIFIED IN: "Print Locations" (whwmd3400m000) SITUATION DESCRIPTION: If no capacity record for a certain localization is available the data from the previous printed record is printed again. SOLUTION DESCRIPTION: After printing the data from a record the printed fields are emptied so that the same cannot be printed again. Solution: 134725 SITUATION IDENTIFIED IN: "Import Conversion Data" (tgbrg5256m000) SITUATION DESCRIPTION: In session "Import Conversion Data" a strange default for the file-name appears. SOLUTION DESCRIPTION: The default on the form was not logical. Default in script was more logical, so default of form is removed. Solution: 134730 SITUATION IDENTIFIED IN: "Print invoice to Business Partner Open Entries" (tfacr2421m000) SITUATION DESCRIPTION: Changed amounts are not displayed when the credit note amount is modified through a sales correction. SOLUTION DESCRIPTION: Changed amounts are displayed for credit note. Solution: 134731 SITUATION IDENTIFIED IN: standard program. SITUATION DESCRIPTION: Defects solved in B50b 213510 Descriptions: - Defect 213510 JOB Function exec.cont.process correctly handled in job mode. SOLUTION DESCRIPTION: These defects are solved in the standard program Solution: 134733 SITUATION IDENTIFIED IN: "Cycle Counting / Adjustment Orders" (whinh5500m000) SITUATION DESCRIPTION: Quantities in inventory unit are calculated wrongly when entering adjustment order lines. This happens if first a line is entered for an existing stock-point, and then a new line for a not existing stock-point is entered via "CTRL-N" without leaving the session. SOLUTION DESCRIPTION: This situation is corrected and values are calculated properly. Solution: 134746 SITUATION IDENTIFIED IN: "Confirm Shipments" (whinh4275m000) SITUATION DESCRIPTION: In this session several performance problems occurred. SOLUTION DESCRIPTION: The database functions that are responsible for the performance problems are optimized to improve performance. Solution: 134758 SITUATION IDENTIFIED IN: "Direct Network Communication" (ecedi7205m000) SITUATION DESCRIPTION: When receiving an order change, the discount code on the sales order line is not changed, although the value in the incoming ASCII file differs from the code on the sales order line and the difference is reported on the "EDI Change Order Comparison" report. SOLUTION DESCRIPTION: The discount code on the sales order line was not changed when more than one level of discount was used. The program script has been corrected. Now the discount code on the sales order line is properly changed via the order change message. Solution: 134764 SITUATION DESCRIPTION: 1. The field 'lot code' on a Sales Order Line (tdsls4101s000) is displayed as empty after the line is delivered. SOLUTION DESCRIPTION: 1. The field 'lot code' on a Sales Order Line (tdsls4101s000) always displays the correct data. Solution: 134770 SITUATION IDENTIFIED IN: "Budget amounts and quantities by period" (tffbs1101m000) SITUATION DESCRIPTION: When in session tffbs1500m000 (Budget Amounts and Quantities by year) actuals are posted, actual amounts are not stated on parent account level when they are defined in the general ledger. SOLUTION DESCRIPTION: Now when in session tffbs1500m000 (Budget Amounts and Quantities by year) actuals are posted, actual amounts are also stated on parent account level when they are defined in the general ledger. Solution: 134776 SITUATION IDENTIFIED IN: "Conversion to File Word Processor" (ttstpconv) SITUATION DESCRIPTION: The ttstpconv creates under conditions files with the name "CopyOf". These files will stay on the server also if they are no longer used. SOLUTION DESCRIPTION: The files are now deleted after they are no longer used. Solution: 134780 SITUATION IDENTIFIED IN: "Print open orders for a project" (tpcor0400m000) SITUATION DESCRIPTION: Unapproved fully received purchase orders for the project are skipped and not printed on the report. SOLUTION DESCRIPTION: The un invoiced or unapproved but fully received purchase orders will also be printed on the report which actually are also a cause of hindrance while closing the project. Solution: 134786 SITUATION IDENTIFIED IN: "Bank Transactions" (tfcmg2100) SITUATION DESCRIPTION: After reconciling and un-reconciling a check payment, it is possible to delete the reconciliation transaction from session 'Bank Transactions' (tfcmg2100s000). SOLUTION DESCRIPTION: If the status of an anticipated document is changed from 'Completed' to 'Open', it's not possible anymore to delete the reconciliation transaction from session 'Bank Transactions'. Message: 'Reconciliation data found for this payment document. Record cannot be deleted' will be displayed Solution: 134789 SITUATION IDENTIFIED IN: "Split Shipment" (whinh4231m000) SITUATION DESCRIPTION: It can take too long for this session to present the first set of data. SOLUTION DESCRIPTION: The initial search routine is changed so that it is more logic and that the search time is shorter. Solution: 134794 SITUATION IDENTIFIED IN: "Print Open Entries" (tfacp2421m000) SITUATION DESCRIPTION: In report "Print Open Entries by Invoices from Business Partner" (tfacp2421m000), the amounts in the column "Amount" are not printed in the correct currency format. SOLUTION DESCRIPTION: The amounts are printed in the correct currency format using the currency-code in the Open-Items. Solution: 134797 SITUATION IDENTIFIED IN: "Add Costs" (tfacp1133s000) SITUATION DESCRIPTION: In session "Match/Approve Purchase Invoices" (tfacp2107s000), when the session "Add costs" (tfacp1133s000) is started and if the period of the invoice has been closed, the periods default to the next open period. In case it is a correction period, it defaults with the correction period. SOLUTION DESCRIPTION: The periods default to the next open period, which is not a correction period. Solution: 134799 SITUATION IDENTIFIED IN: "Split Shipment" (whinh4231m000) SITUATION DESCRIPTION: It can take too long for this session to present the first set of data. SOLUTION DESCRIPTION: The initial search routine is changed so that it is more logic and that the search time is shorter. Solution: 134805 SITUATION IDENTIFIED IN: "Print Employees Responsible by Project" (tppdm6431m000) SITUATION DESCRIPTION: In session "Print Employees Responsible by Project" (tppdm6431m000) the selection range fields "Responsibility" and "Employee" do not have a zoom option to select the codes. Thus the user must search for these codes in another session before entering the selection. SOLUTION DESCRIPTION: Zoom options for the selection range fields "Responsibility" and "Employee" have been added. Solution: 134816 SITUATION IDENTIFIED IN: "Material to Issue for Production Orders" (ticst1501m000) SITUATION DESCRIPTION: The subsequent delivery field (ticst001.subd) is stored with a value of 0 (zero) but a small residual value is stored in the database level instead of 0.0000, while reporting operations completed and back flushing the material in session "Report Operations Completed" (tisfc0530m000). SOLUTION DESCRIPTION: The subsequent delivery field (ticst001.subd) is stored with a value of 0.0000 and at the database level also the value is stored as 0.0000 without any residual values, while reporting operations completed and back flushing the material in session "Report Operations Completed" (tisfc0530m000). Solution: 134824 SITUATION IDENTIFIED IN: "Purchase Requisition Lines" (tdpur2101m000) SITUATION DESCRIPTION: The Item Types Subcontracting and Equipment are not allowed in Purchase Requisitions. This restriction has to be relaxed for Project Subcontracting and Project Equipment items. SOLUTION DESCRIPTION: 1. In Purchase Requisitions, the check for Item has been modified. Currently, Items of type Subcontracting or Equipment will be allowed only if they are linked to a Project (TP). 2. Purchase Requisitions for Subcontracting or Equipment can be converted directly to Purchase Orders allowed only if those Items are linked to a project. Solution: 134839 SITUATION IDENTIFIED IN: "Cycle Count / Adjustment order lines" (whinh5101s000) SITUATION DESCRIPTION: When processing cycle counting orders for an item which does have package definitions and some inventory is allocated the following blocking message could be returned: "Negative net available on hand not allowed (on hand - on hold - allocated - variance)" (message code: whinhs0026). This could happen even though sufficient inventory is available to be decreased. When multiple cycle count lines exist for a stock point, the stock point was unblocked after the first cycle counting line that was processed, despite of the fact that other unprocessed lines could still be present. SOLUTION DESCRIPTION: The check on inventory availability when processing a cycle-counting order has been corrected, which allows the user to process the cycle count order in above mentioned situation. Unblock of stock point is only done when all cycle counting lines for the same stock point have been processed. Solution: 134842 SITUATION IDENTIFIED IN: "Maintenance Sales Order Lines" (tsmsc1110m000) SITUATION DESCRIPTION: When warehouse order text is changed, the change appears in the service order also. SOLUTION DESCRIPTION: 1) It is now possible to save a maintenance sales order line correctly. 2) Changes in warehousing order text are not reflected back to service order text. Solution: 134860 SITUATION IDENTIFIED IN: "Production Orders" (tisfc0101s000) SITUATION DESCRIPTION: Creation of Production Order with lot-controlled item is very slow. SOLUTION DESCRIPTION: Performance improved now. Solution: 134868 SITUATION IDENTIFIED IN: "Sales-Order Lines" (tdsls4101s000). SITUATION DESCRIPTION: When adding a non-project item in "Sales-Order Lines" (tdsls4101s000), field "Project" (tdsls401.cprj) gets defaulted with the value this field has on the first occurrence as displayed in "Sales-Order Lines" (tdsls4501m000). SOLUTION DESCRIPTION: Defaulting of field "Project" is corrected. When a project-item is entered, the project field will be filled with the item's project segment. When a non-project item is entered, the project field can be filled manually. Solution: 134875 SITUATION IDENTIFIED IN: "Selection for Automatic Reconciliation" (tfcmg2123s000) SITUATION DESCRIPTION: Anticipated documents selected via 'Select for Automatic Reconciliation' (tfcmg2122s000) are not displayed when session 'Selection for Automatic Reconciliation' (tfcmg2123s000) comes up. The user needs to scroll down to see the selected records. SOLUTION DESCRIPTION: Anticipated documents selected via 'Select for Automatic Reconciliation' are being displayed directly when session 'Selection for Automatic Reconciliation' comes up. Solution: 134888 SITUATION IDENTIFIED IN: "Planned equipment transactions" (tppss6110s000) SITUATION DESCRIPTION: Invalid contract line can be maintained for an equipment and subcontracting item in planned purchase orders. SOLUTION DESCRIPTION: Error will be displayed if an invalid contract line is maintained for equipment and subcontracting item also. Solution: 134892 SITUATION IDENTIFIED IN: "Signal Overview by Planner" (cprao1120m000) SITUATION DESCRIPTION: The item description "Signal Overview by Planner" (cprao1120m000) and "Signals by Item/Planner" (cprao1125m000) is not displayed on the form. SOLUTION DESCRIPTION: The item description is retrieved and displayed on the form. Solution: 134893 SITUATION IDENTIFIED IN: "Sales Contracts" (tdsls3100s000) SITUATION DESCRIPTION: When de-activating a Sales Contract (tdsls3100m000) the field 'Effective Date' remains disabled. When clicking on another field, it is enabled. SOLUTION DESCRIPTION: When de-activating a Sales Contract (tdsls3100m000) the field 'Effective Date' is enabled. Solution: 134894 SITUATION IDENTIFIED IN: "Print User History" (ttaad2402m000) SITUATION DESCRIPTION: In session Print User History (ttaad2402m000) it is possible to sort the report by date/time or by user. When the session is run in a job, the report is always sorted by user. SOLUTION DESCRIPTION: When the session is run in a job, the report is now correctly sorted. Solution: 134901 SITUATION IDENTIFIED IN: "Print Reminder Letters" (tfacr3420m000) SITUATION DESCRIPTION: In session "Print Reminder Letter" (tfacr3420m000), the reminder-procedure will use the credit notes for checking the open-balance for a certain customer. Since the credit note will not get a letter-number it's impossible to calculate a proper interest-amount. SOLUTION DESCRIPTION: The interest amount is calculated only when the letter-number is updated. Solution: 134902 SITUATION IDENTIFIED IN: "Calculate Demand Forecast by Item." (whina2202m000) SITUATION DESCRIPTION: Help text for "Returned Quantity" check box shows wrong information in session "Calculate Demand Forecast by Item" (whina2202m000). Solution 133046 (Label "Reference" is not properly translated in Dutch language and Help text shows wrong information on check box "Returned Quantity".) was created for that issue but help text was not present. SOLUTION DESCRIPTION: Help text has been modified from "The Demand Direct Delivery can be taken into account for the demand forecast. The value will be added up to one of Actual Issue by Period or Demand Quantity." into "The Returned Quantity can be taken into account for the demand..." Solution: 134912 SITUATION IDENTIFIED IN: "Print Project Work In Process" (tipcs3480m000) SITUATION DESCRIPTION: There are 3 cases where Costs are booked on a Service order linked to a PCS project, and where these Costs are not recognized as "Outgoing value" in "Print Project Work In Process" (tipcs3480m000). This results in wrong WIP amounts. Case 1: Service Order linked to a PCS Project, and service order costs are made marked as "internal"; These Costs are booked as "Internal Service Costs", but are not seen in "Print Project Work In Process" (tipcs3480m000) as "Outgoing value". Case 2 : Service order which is created from a Field change order is linked to a PCS Project; when costs are booked on this service order related to Field change order activities, then these costs are booked as "Field change order Costs". These costs are not seen in "Print Project Work In Process" (tipcs3480m000) as "Outgoing value". Case 3: Service order with Warranty Costs is linked to a PCS Project; when Warranty Costs are booked on this service order these Costs are booked as "Warranty Costs". These costs are not seen in "Print Project Work In Process" (tipcs3480m000) as "Outgoing value". In all 3 situations the WIP amount in Service and PCS is not correct. SOLUTION DESCRIPTION: The session "Print Project Work In Process" ( tipcs3480m000 ) is modified such that the integration transaction with Transaction Origin "Service" and Financial transaction "Internal Service Costs" or "Field change order Costs" or "Warranty Costs" are now included in the "Outgoing value" amount on the report. Because of this also the WIP amount is now correct. Solution: 134915 SITUATION IDENTIFIED IN: "Purchase Invoice Transactions" (tfacp1110s000) SITUATION DESCRIPTION: (1) A credit note with normal tax and the subcontracting flag is not set gets assigned to an original invoice for which the original invoice has shifted tax and the subcontracting flag is set. (The credit note amount is the same as the invoice amount.) (2) After saving a correction is done on the credit note. The normal tax is changed to shifted tax and the subcontracting flag is set. (3) Now when confirming the record gives an open amount although this should be zero. SOLUTION DESCRIPTION: Assigning and changing invoices to credit notes with or without shifted tax and with or without the subcontracting flag set does not give any problems anymore. Solution: 134916 SITUATION IDENTIFIED IN: "Inventory by Warehouse and Item" (whwmd2515m000) SITUATION DESCRIPTION: The help text for field "Date Hist. Inventory Level" in session "Item Inventory by Warehouse" (whwmd2115s000) indicates that this field represents the date of the most recent inventory transaction that is "registered" for this item/warehouse combination. This is wrong because the field represents the date of the most recent inventory transaction that is "archived". In order to solve this issue solution 134682 was created, but the help text was not present. SOLUTION DESCRIPTION: The help text is corrected and a new solution is created. Solution: 134917 SITUATION IDENTIFIED IN: "Change Prices and Discounts after Delivery" (tdsls4122m000) SITUATION DESCRIPTION: Performance problems occur when starting the session the first time as well as when a record is searched. SOLUTION DESCRIPTION: The problem occurs due to the wrong index is used for sorting the data. This has been changed in the session. Solution: 134936 SITUATION IDENTIFIED IN: "Transfer Purchase Order Advice" (whina3212m000) SITUATION DESCRIPTION: An active purchase contract exists for a particular Item - Supplier combination subject to a minimum order quantity per order. A purchase advice for the same Item - Supplier combination (but the order quantity is less than the minimum order quantity specified in the purchase contract, hence the contract cannot be applied) is transferred to Purchase Order. The resulting order line is linked to the Purchase Contract even though the order quantity does not qualify for the contract to be applicable. This does not happen when a purchase order is created manually with the same data. SOLUTION DESCRIPTION: If the retrieved purchase price for the Purchase order line has not originated from the linked purchase contract then the order line will be disconnected from the contract. Solution: 134942 SITUATION IDENTIFIED IN: "Purchase Order Lines" (tdpur4101s000) SITUATION DESCRIPTION: It is possible to insert a Discount Code with "Use in Agreement" marked for a purchase order line that does not meet the agreement at all. On the purchase order line you can insert manually a price, manually a discount percentage and then you can enter any discount code you like in the field Discount Code. SOLUTION DESCRIPTION: User is not allowed to enter a discount code marked with use is agreements on a purchase order line when the prices and discounts are entered manually. In this case, system gives an error message saying, "Discount code must be of type Discount and should not be used in agreements". Solution: 134961 SITUATION IDENTIFIED IN: standard program. SITUATION DESCRIPTION: Defects solved in B50b 135112, 136728 Descriptions: - Defect 135112-2 AFS set.report should overrule device - Defect 136728 Default button handling corrected SOLUTION DESCRIPTION: These defects are solved in the standard program Solution: 134964 SITUATION IDENTIFIED IN: "Print Open Entries" (tfacr2421m000) SITUATION DESCRIPTION: Help text not in line with the Application. Code is exploded as 'print.purchase'. Same text "Purchase Invoices" as present on form should be exploded. SOLUTION DESCRIPTION: Now the Help text will be in line with the Application. Solution: 134972 SITUATION IDENTIFIED IN: "Change Prices/Discounts after Receipts" (tdpur4122m000) SITUATION DESCRIPTION: When the financial period of the delivery date is closed, the system does not allow receiving the purchase orders by giving the error +++++++++++++++++++++++++++++++++++++ Fiscal year 2003 period 3 not open in company XXX" ++++++++++++++++++++++++++++++++++++++ The integration posting created at the time of changing the price after receipt in the session "Change Prices/Discounts after Receipts" (tdpur4122m000) are also logged with the receipt date of the purchase order line. But, at this time the system does not check if the period corresponding to the receipt date is already closed or not. SOLUTION DESCRIPTION: The following error message pops up at the time of changing the price after receipt in the session "Change Prices/Discounts after Receipts" (tdpur4122m000). +++++++++++++++++++++++++++++++++++++ Fiscal year 2003 period 3 not open in company XXX" ++++++++++++++++++++++++++++++++++++++ Solution: 134976 SITUATION IDENTIFIED IN: "Standing Orders" (tfcmg1110s000) SITUATION DESCRIPTION: When changing the rate determinator to 'Manual Entered' in session 'Standing Orders' (tfcmg1110s000) and also the rate is changed, the rate changes back to the previous value when saving the record. SOLUTION DESCRIPTION: In session 'Standing Orders' the manually entered rates are saved properly when the rate determintor is 'Manual Entered'. In case a currency is entered for which no rates exists, message 'No Currency Rate is defined between and ' Solution: 134982 SITUATION IDENTIFIED IN: "Purchase order header" (tdpur4100s000) SITUATION DESCRIPTION: 'Pay to BP' on order header can not maintained since it is disabled. SOLUTION DESCRIPTION: 'Pay to BP' on order header level is available to be maintained. Solution: 134991 SITUATION IDENTIFIED IN: "Compose/Print/Post Invoices" (cisli2200m000) SITUATION DESCRIPTION: Rate filled in invoice is rounded heavily if the rate defined is having 6 digits after decimal, and the rate factor is defined as 1000. SOLUTION DESCRIPTION: Now the rate filled in the invoice is rounded correctly. Solution: 134992 SITUATION IDENTIFIED IN: "Write off Payment Difference" (tfacp2230m000) SITUATION DESCRIPTION: When the session "Write off Payment Differences" (tfacp2230m000) was run, if there was a payment difference the balance amount of the invoice was updated but not the balance in home currency of the invoice. SOLUTION DESCRIPTION: After running the session "Write off Payment Differences", it updates the balance correctly of the invoice. Solution: 135010 SITUATION IDENTIFIED IN: "Purge Sales Invoice Data" (cisli3210m000) SITUATION DESCRIPTION: Even though only project invoice is selected for purging, the system gives a fatal error 205 (Out of Range) for service order lines table. SOLUTION DESCRIPTION: Now the fatal error does not arise. Solution: 135014 SITUATION IDENTIFIED IN: "Planned Inventory Transactions" (whinp1500m000) SITUATION DESCRIPTION: When the inventory handling parameter "Correct SFC Production Order till" is set to "Generate Outbound Advice" or "Release Outbound Advice" the following two problems are experienced: A redundant inbound line and wrong planned inventory transactions remain in the Warehousing module after processing a negative material issue in production. SOLUTION DESCRIPTION: When the inventory handling parameter "Correct SFC Production Order till" is set to "Generate Outbound Advice" or "Release Outbound Advice" and processing a negative material issue in the Baan Production module the outbound and inbound lines are updated correctly. Furthermore the planned inventory transactions are updated accordingly. Solution: 135019 SITUATION IDENTIFIED IN: "Register Purchase Invoices" (tfacp1110s000) SITUATION DESCRIPTION: When changing the currency of a purchase invoice, the newly stored currency does not get saved correctly in the documents table (tfgld018). SOLUTION DESCRIPTION: When changing the currency of a purchase invoice, the newly stored currency is correctly saved in the documents table (tfgld018). Solution: 135021 SITUATION IDENTIFIED IN: "Purchase-Invoice Corrections" (tfacp2110s000) SITUATION DESCRIPTION: 1. In session "Purchase-Invoice Corrections" (tfacp2110s000), if the tax code is changed from singular tax code to a multiple tax code, then the tax line amounts are not calculated correctly. 2. Also in the session, when only the business partner is changed in the purchase invoice, then no tax transactions are created, hence the information in session "Tax Analysis" (tfgld1520m000) is wrong. SOLUTION DESCRIPTION: 1. The tax line amounts are calculated correctly. 2. Tax transactions are created when the business partner is changed. Solution: 135031 SITUATION IDENTIFIED IN: "Print Sales Invoices" (tfacr2421m000) SITUATION DESCRIPTION: For invoices which are created long back (overdue days greater than 999), hashes(#) are printed on the report for the column overdue days SOLUTION DESCRIPTION: For the invoices created long back are printed correctly. Solution: 135033 SITUATION IDENTIFIED IN: "Write off payment difference" (tfacr2240m000) SITUATION DESCRIPTION: Wrong warning message when invoice period compared with fiscal period. SOLUTION DESCRIPTION: Correct warning message displayed when invoice period compared with fiscal period. Solution: 135034 SITUATION IDENTIFIED IN: "Business Partner Statements" (tfacr3440m000) SITUATION DESCRIPTION: Footer text is restricted to maximum of 10 lines. SOLUTION DESCRIPTION: Footer text displayed for more than 10 lines also Solution: 135035 SITUATION IDENTIFIED IN: "Sales Order Lines" (tdsls4101s000) SITUATION DESCRIPTION: 1. When entering an item which does not have enough inventory, the Stock Shortage Menu appears after the ordered quantity is entered. When choosing option 'Alternative Items' and choosing an item which also does not have enough inventory, the Shortage Menu does not appear again. 2. When splitting a Sales Order Detail by using the 'Split'-button, a fatal error occurs (only B50_b and B50_c) SOLUTION DESCRIPTION: 1. When the Alternative Item also does not have enough inventory, the Shortage Menu appears again. 2. A Sales Order Detail can be split without fatal errors. Solution: 135037 SITUATION IDENTIFIED IN: "Process Quotations" (tdsls1200m000) SITUATION DESCRIPTION: Sales orders are not being created when sales quotations are processed. This occurs when the calendar doesn't have null availability type. SOLUTION DESCRIPTION: The release date is zero when the calender doesn't have null availability type. Therefore, the release date will be equal to the order date. This is to allow the sales order to be created since sales orders cannot be inserted with an empty release date. Solution: 135042 SITUATION IDENTIFIED IN: "Invoice-To Business Partner Aging Analysis" (tfacr2420m000) SITUATION DESCRIPTION: Amounts are wrongly aged when invoices have receipt schedules and reported is printed based on "Due Date" SOLUTION DESCRIPTION: Amounts are correctly aged. Solution: 135045 SITUATION IDENTIFIED IN: "Initiate Inventory Issue" (tisfc0207m000) SITUATION DESCRIPTION: While initiating inventory and issuing materials, if there is a shortage, the planned inventory transaction date of the material line is changed to the issue date value when the "Initiate Inventory Issue"(tisfc0207m000) session is executed. SOLUTION DESCRIPTION: The planned inventory transaction date does not change when materials are not issued because of shortage. Solution: 135048 SITUATION IDENTIFIED IN: "Print Forecast Components by Date/Currency " (tfcmg3420m000) SITUATION DESCRIPTION: A budget created for a credit Balance Sheet account is printed under the Inflow Budget in the session "Print Forecast Components by Date/Currency (tfcmg3420m000)". This should be the opposite. For a credit ledger account and a budget defined for the credit site the budget should be printed under Outflow Budget. SOLUTION DESCRIPTION: A budget created for a balance sheet account. Which is defined on credit side of the budget, will be printed under the Outflow Budget, in the session "Print Forecast Components by Date/Currency (tfcmg3420m000)". Solution: 135053 SITUATION IDENTIFIED IN: "Sales Orders" (tdsls4100s000) SITUATION DESCRIPTION: Help text for field 'Planned Receipt Date' on Sales Order Header (tdsls4100s000) and Sales Order Lines (tdsls4101s000) is incorrect. It says: "An anticipated receipt that corresponds to an open purchase order or open production order" SOLUTION DESCRIPTION: Help text on the 'Planned Receipt Date' is now: The date on which the customer is planned to receive the goods" Solution: 135054 SITUATION IDENTIFIED IN: "Perform Inventory Valuation by Warehouse and Item" (whina1210m000) SITUATION DESCRIPTION: A range of warehouses can be entered. The check on this range however was carried out with the 'to' warehouse only instead of with the 'from' and the 'to' warehouse. SOLUTION DESCRIPTION: The range check is changed so that the proper warehouses are taken into account. Solution: 135055 SITUATION IDENTIFIED IN: "Receipts" (whinh3520m000) SITUATION DESCRIPTION: When purchase order receipts are done in "Receipts"(whinh3520m000), then unexpected small amounts are posted as results in finance. The result amount is posted on Surcharge component and is due to surcharges defined for the item in "Item surcharges"(ticpr1510m000). SOLUTION DESCRIPTION: No results are posted in "Integration Transaction by Project/Order"(tfgld4510m000), when purchase order receipts are done in "Receipts"(whinh3520m000) for an Item having surcharges defined. Solution: 135056 SITUATION IDENTIFIED IN: "Manual Sales Header" (cisli2520m000) SITUATION DESCRIPTION: Only the first invoice gets printed when several manual sales headers are selected for direct processing. The rest of the invoice gets printed only if the session "Manual Sales Header" (cisli2520m000) is closed. And also when a range of headers is selected for direct processing, the system tries to process right from the first manual sales header instead of the first selected header. SOLUTION DESCRIPTION: Now all the invoices are printed correctly. Also only the selected range of headers are processed. Solution: 135067 SITUATION IDENTIFIED IN: "Generage Cost Forecast by Cost Object" (tpppc2216m000) SITUATION DESCRIPTION: Forecast Quantities are not correctly calculated. In case the leading Forecast method is Estimated to Complete, the quantities are not correctly calculated. If the base for Forecast is Budget then Quantity should be Budgeted Quantity - Actual Quantity and in case the base is Previous forecast then quantity should be Previous Forecast Quantity - Actual Quantity. SOLUTION DESCRIPTION: Now, the problem is solved. Program calculates the actual quantity spend from the Cost History and uses this value for calculating the Forecast. Solution: 135068 SITUATION IDENTIFIED IN: "Change Prices/Discounts after Receipts" (tdpur4122m000) "Commitments (Materials)" (tpppc2110s000) SITUATION DESCRIPTION: 1. If the price of a purchase order linked to project is changed after receiving the item, then the 'Registration Date' in project commitment is updated with 'Current Date'. Instead it should be 'Receipt Date' of the order. 2. Similarly, the 'Registration Date' in case of 'Order' commitment line should be 'Order Date' instead of 'Planned Delivery Date'. This will then be consistent with the normal purchase order with respect to finance entries. SOLUTION DESCRIPTION: . For a price change after the receipt of goods, the 'Registration Date' in 'Projects' commitment line will be the 'Receipt Date'. In case the price is changed where there have been partial receipts, the 'Registration Date' for the commitment line will be the corresponding 'Receipt Date'. 2. The 'Registration Date' in case of 'Order' commitment line (i.e. the Soft Commitment line) will be 'Order Date' instead of 'Planned Delivery Date'. Solution: 135074 SITUATION IDENTIFIED IN: "Print Specifications Delivered, Not Yet Invoiced" (tfacr1432m000) SITUATION DESCRIPTION: In report "Print Specifications Delivered, Not Yet Invoiced" (tfacr1432m000), the amount is incorrectly calculated for an order/position because of incorrect rounding. SOLUTION DESCRIPTION: The report now prints correct values. Solution: 135087 SITUATION IDENTIFIED IN: "Create Sequential Dump of Table" (ttaad4226m000) SITUATION DESCRIPTION: The session "Create Sequential Dump of Table" creates dump files and splits them after 2 GB by default. The company number for the tables containing it is stored as 1 in the files and not as 001. Now the session "Copy Company Data" (ccom0214m000) will change the company number to a three-digit number, like 801 (increase the size of each line by 2 bytes). The result is that a new dump file should be written with a size larger than 2 GB. This will fail and will result in loss of data. SOLUTION DESCRIPTION: In session "Create Sequential Dump of Table" a new field is introduced: Maximum file size (mb). In this field the user can enter the maximum size of the table dump files in megabytes. In this way he can prevent the creation of dump files of 2 gigabyte, to which no characters can be added. Solution: 135088 SITUATION IDENTIFIED IN: "Table Definitions" (ttadv4520m000) SITUATION DESCRIPTION: When the VRC of a table is higher than the VRC of the package as found in the Package combination of the user, then the table description is not displayed. SOLUTION DESCRIPTION: Now the table description is correctly retrieved and displayed as found in the table 'Language Dependent Descriptions'. Solution: 135110 SITUATION IDENTIFIED IN: "Close Production orders" (ticst0201m000) SITUATION DESCRIPTION: It is possible to close the production order even before the purchase invoice is approved for the sub-contracting purchase orders corresponding to the production order. SOLUTION DESCRIPTION: The production order is now prevented from being closed when the invoice of the corresponding purchase order is not approved in finance. Solution: 135135 SITUATION IDENTIFIED IN: "tdpur4101s000" (Purchase Order Lines) SITUATION DESCRIPTION: When the Purchase Order lines are already maintained and if the same Purchase Order is reached from the Purchase Order header session by pressing "Order Lines" button, the system opens a new single occurrence Purchase Order lines session, instead of Purchase Order lines multi occurrence session. SOLUTION DESCRIPTION: The problem is solved, when the lines are already maintained and if the same Purchase Order is reached from the Purchase Order Header session by pressing "Order Lines" button, then the system will open the multi occurrence Purchase Order Lines session. If a new Purchase Order is maintained and "Order Lines" button is pressed from the header then the system will automatically open the single occurrence Purchase Order Lines session. Solution: 135137 SITUATION IDENTIFIED IN: "Display Browser" (ttstpdisplay) SITUATION DESCRIPTION: While printing the report, initially the vertical scroll bar is shown. Now, when the window is maximized the scroll bar is lost SOLUTION DESCRIPTION: Now the Vertical scroll bar is shown when the window is maximized. Solution: 135151 SITUATION IDENTIFIED IN: "Report Viewer" (ttstpdisplay) SITUATION DESCRIPTION: When printing to display then it is not possible to scroll through the complete report by use of the scrollbar. SOLUTION DESCRIPTION: Now the scrollbar is correctly initialized Solution: 135152 SITUATION IDENTIFIED IN: "Outbound Advice by Order Line" (whinh2525m200) SITUATION DESCRIPTION: In session "Outbound Advice by Order Line" (whinh2525m200) the fields Minimum Quantity and Maximum Quantity are not rounded according to the Inventory Unit of the item when no Outbound Advice is present yet. SOLUTION DESCRIPTION: The fields Minimum and Maximum Quantity are now rounded correctly according to the Inventory Unit of the item, regardless whether Outbound Advice is present or not. Solution: 135155 SITUATION IDENTIFIED IN: -1- "Receipts" (whinh3520m000) -2- "Import/Export Statistics"(tccom7571m000) SITUATION DESCRIPTION: -1- When a sales return order is processed for an item with valuation method "lot price", the amount for "Cost Of Goods Sold" in session "Release to Invoicing" (tdsls4501m130) is determined as zero. This happens when the return order is not linked to an original sales order. -2- Import/export statistics are created when a purchase order line is entered with quantity zero. SOLUTION DESCRIPTION: -1- The value of the "Cost Of Goods Sold" is determined properly. -2- Import/export statistics are only created when goods are received, not when a purchase order line is created. Solution: 135175 SITUATION IDENTIFIED IN: "Payment Advice " (tfcmg1120s000) SITUATION DESCRIPTION: Error 'Amount exceeds invoice balance' is given when adding a Purchase Credit Note into a payment advice even when the amount is less than the invoice balance. SOLUTION DESCRIPTION: When adding a Purchase Credit Note into a payment advice, error 'Amount exceeds invoice balance' is not given when the amount is less than the invoice balance. Solution: 135178 SITUATION IDENTIFIED IN: "Generate Inventory Commitment" (whinp2200m000) SITUATION DESCRIPTION: Though all Inventory Commitments are generated correctly the report does not show all the commitments that are generated. SOLUTION DESCRIPTION: All Inventory Commitments that are generated are now also printed on the report. Solution: 135194 SITUATION IDENTIFIED IN: "Print Inventory Transactions by Project" (whinr1410m000) SITUATION DESCRIPTION: When running session "Print Inventory Transactions by Project" (whinr1410m000) the consignment usage could be reported with the wrong sign. This also resulted in a wrong calculated 'Total quantity' printed at the bottom of the report. This is only a reporting issue as the actual data is correctly stored within the system. SOLUTION DESCRIPTION: A consignment usage is now identified as requirement by the session "Print Inventory Transactions by Project" (whinr1410m000) and therefore printed with a negative sign. As a result the 'Total quantity' as printed at the bottom of the report is also calculated correctly. Solution: 135207 SITUATION IDENTIFIED IN: "General Product Addon Installer" (ttiexgpainst) SITUATION DESCRIPTION: The General Product Addon Installer was copied from ttB40c4 to BaanERP. Not all ttB40c4 commands did actually work in the higher Baan versions. SOLUTION DESCRIPTION: Function server calls in the General Product Add on Installer are changed from ttB40c4 commands to the correct BaanERP function calls. Solution: 135235 SITUATION IDENTIFIED IN: "Select Device" (ttstpsplopen/close) SITUATION DESCRIPTION: 1) If you have a device saved as default and this is not a display device then you cannot zoom on the paper type. 2) If you print on a device of type write file or append file and the is no output generated then the status of the print job keeps premature. SOLUTION DESCRIPTION: 1) The zoom is now possible. 2) The status is updated according to the users definition. Solution: 135240 SITUATION IDENTIFIED IN: "Purchase Order Lines" (tdpur4501m000) SITUATION DESCRIPTION: It is possible to delete a Direct Delivery back order from Purchase side. This causes incorrect updating of Linked Order line data in Sales and the user is not able to process the delivered Purchase Orders. The direct delivery purchase back orders are created (triggered) from sales and that means the deletion/cancellation of the back orders should also be triggered from sales. It should never be possible to delete the back order in purchase with out the knowledge of sales. SOLUTION DESCRIPTION: From Purchase side, the back order for a Direct Delivery order cannot be deleted any more. Solution: 135286 SITUATION IDENTIFIED IN: "Register Purchase Invoices" (tfacp1110s000) SITUATION DESCRIPTION: When inserting a second invoice without leaving the session with a business partner that not belongs to the business partner structure of the business partner from the previous invoice the message "BP xxx does not belong to the business partner structure of BP yyy" pops up wrongly because it is a new invoice. SOLUTION DESCRIPTION: Because the business partner structure check now is done for each separate invoice the message "BP xxx does not belong to the business partner structure of BP yyy" will not pop up. Solution: 135291 SITUATION IDENTIFIED IN: standard program. SITUATION DESCRIPTION: Defects solved 135376, 136930, 137165 Descriptions: - Defect 135376 Defects solved - Defect 136930 Marking of rec after adding new record - Defect 137165 AFS Maxfield len should be calc based on inplen SOLUTION DESCRIPTION: These defects are solved in the standard program Solution: 135297 SITUATION IDENTIFIED IN: "Process Delivered Purchase Orders" (tdpur4223m000) SITUATION DESCRIPTION: While deleting a Purchase Order line created through Requisition process, system throws Fatal error 605 (Reference exists). SOLUTION DESCRIPTION: The Fatal error no does not appear now and system deletes the purchase order line without any problem. Solution: 135308 SITUATION IDENTIFIED IN: "Direct Network Communication" (ecedi7205m000) SITUATION DESCRIPTION: When receiving a sales order for a business partner without tax, and the tax field in the ASCII file is empty, an error occurs ("Tax code cannot be changed") and the order is rejected. SOLUTION DESCRIPTION: The programs script has been modified. An empty tax code read from the file is no longer giving an error message when tax is not applicable. The sales order is properly inserted. Solution: 158774 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000, tfcmgl200m000) SITUATION DESCRIPTION: Implement 1099-MISC requirements per U.S. IRS tax publication 1220 for year 2002. The following solutions were for the 2001 changes: 156275 - All versions - The solution with the IRS changes for 2001 is # 156275 4c, 4b & 3b solutions to load with the 2001 updates are # 157002, 157014 and 157431 5b & 5c solutions to load with the 2001 updates are # 157002, 157014, 157220, 157431 and 156842 The IRS has not made any significant changes to the 1099-MISC paper form for the year 2002. This will be monitored on a regular basis and any changes will be noted and updated in this generic solution. Electronic form information is available in Internal Revenue Bulletin 2002-25 as a Revenue Procedure. DF # 208852 has been logged to accommodate electronic filing change requirements per IRB 2002-25. Laser printer instructions are now available. See solution 157257 SOLUTION DESCRIPTION: General (1) 9-track magnetic tape is no longer an acceptable type of media for submitting information returns to IRS/MCC. (2) A new field Record Sequence Number was added to Field Positions 500-507 in all records. The Record Sequence Number will be in Field Positions 500-507 of the "T" Record, the "A" Record(s), the "B" Record(s), the "C" Record(s), any applicable "K" Record(s), and the "F" Record. Programming Changes - Transmitter "T" Record: (1) For all forms, Payment Year, Field Positions 2-5, must be incremented to update the four-digit report year (2001 to 2002), unless reporting prior year data. (2) Contact Email Address was added to Field Positions 359-393. (3) Cartridge Tape File Indicator was moved to Field Positions 394-395. (4) Electronic File name for a Replacement File was moved to Field Positions 396-410. (5) Transmitter's Media Number was added to Field Position 411-416. (6) Vendor Indicator was moved to Field Position 518. (7) Vendor Name was moved to Field Positions 519-558. (8) Vendor Mailing Address was moved to Field Positions 559-598. (9) Vendor City was moved to Field Positions 599-638. (10) Vendor State was moved to Field Positions 639-640. (11) Vendor ZIP code was moved to Field Positions 641-649. (12) Vendor Contact Name was moved to Field Positions 650-689. (13) Vendor Contact Phone Number and Extension was moved to Field Positions 690-704. (14) Vendor Contact Email Address was moved and expanded to 35 positions in Field Positions 705-739. Programming Changes - Payer "A" Record: (1) For all forms, Payment Year, Field Positions 2-5, must be incremented to update the four-digit report year (2001 to 2002), unless reporting prior year data. Programming Changes - Payee "B" Record: (1) For all forms, Payment Year, Field Positions 2-5, must be incremented to update the four-digit report year (2001 to 2002), unless reporting prior year data. Programming Changes - End of File "F" Record: (1) Total Number of Payees was added to Field Positions 50-57. Multi-site: Several multisite issues have also been resolved for companies that invoice and make payment across multiple companies. Solution: 159448 SITUATION IDENTIFIED IN: "Close Periods" (tfgld1206m000) SITUATION DESCRIPTION: If an error is found during the process of period closing then corresponding error message will be given and process will be stopped. It's impossible to get a full list of errors to fix them at once. SOLUTION DESCRIPTION: New mode has been added to satisfy the need to know all errors that prevent period from being closed. In this mode all errors are printed on the report. New form field "Print all errors" has been added to switch between modes. If this field is set to "NO" then as soon as an error is detected the error message will be shown and next period will be processed. If the value of the field "Print all errors" is "YES" then all errors will be printed on the report. If no errors are found then period will be closed. Some performance issues have been solved as well. Solution: 159844 SITUATION IDENTIFIED IN: "Signal Types by Planner" (cprao1110m000) SITUATION DESCRIPTION: The default values of certain signals were incorrect. Without having the correct default values, the signals were not being issued when they should. The user cannot update or change these default values. SOLUTION DESCRIPTION: When a signal is being saved after it has been modified, a check is performed to correct any errors in the default values. Solution: 159898 SITUATION IDENTIFIED IN: "Signal Types by Planner" (cprao1110m000) SITUATION DESCRIPTION: The default values of some of the records in the Signals by Item/Planner were set to an incorrect value. Depending on the default value on the table, the value determines if a signal is issued or not. The user has no method of updating or correcting the default values on this table. SOLUTION DESCRIPTION: A correction session is created to identify and reset the records to the correct default values. Correcting these values allows for the signals to be correctly issued should the condition arise in the normal planning processes. Solution: 160317 SITUATION IDENTIFIED IN: "Calendar Lines" (tcccp0120m000) SITUATION DESCRIPTION: When 'Refresh Mode' of Calendar is set to "Automatic refresh" for the whole Calendar and CCP-parameter "Use Std Calendar Template" is selected, opening session "Calendar Lines" (tcccp0120m000) takes a long time. SOLUTION DESCRIPTION: Performance is improved but session still may take some time to open due to size of the calendar. Solution: 160345 SITUATION IDENTIFIED IN: "Print Commission/Rebate Invoices" (tdcms2402m000) SITUATION DESCRIPTION: When printing commission invoices for multiple orders and the same relation in a multi-finance environment, commissions for different finance companies are being grouped together, rather than printing separately. SOLUTION DESCRIPTION: In a multi-finance environment, the sales office is used to determine to which finance company the invoices will be posted. However, the session was only grouping commissions together by relation, ignoring the different sales offices of the commissions. The session has been modified to group the commissions by relation and then by sales office as well, so that commissions for different finance companies will no longer be printed together on one invoice. Solution: 160348 SITUATION IDENTIFIED IN: "Rebuild Ledger/Dimension History of Period" (tfgld3206m000) SITUATION DESCRIPTION: When rebuilding ledger/dimension history with the "Opening Balance" box checked, the Dual Accounting Indicator field in table tfgld206 (Opening Balances - Combination of Dimension/Ledger/Currency) was not being populated. SOLUTION DESCRIPTION: The Dual Accounting Indicator field in table tfgld206 (Opening Balances - Combination of Dimension/Ledger/Currency) is now being populated based on the value of the Dual Accounting Indicator in the Chart of Accounts. Solution: 160359 SITUATION IDENTIFIED IN: "Copy Balances to History Before Specified Year" (tfgld6206m000) SITUATION DESCRIPTION: The program would not complete in a job as a question was asked during processing. SOLUTION DESCRIPTION: The question asking if data should be deleted is no longer given at runtime. This option is now added to the form. The functionality of the session has changed to become consistent with other versions and other archiving sessions. This session will now archive/delete up to and including the year on the form. Previously, the program would do this up to the year on the form minus the value specified in the company parameters ("Store Data For N Years"). This parameter is now checked when entering the year on the form, to make sure only achievable years are processed. The session help text has been modified to reflect this. Solution: 160372 SITUATION IDENTIFIED IN: "Post Integration to Finance Transactions" (tfgld4201m000) SITUATION DESCRIPTION: When using session tfgld4201m000 (Post Integration Transactions to Finance) or other sessions that are capable of creating transactions to finance, if the session is unable to post to the next open period, the English version of the error message that is responsible for notification is different from its Dutch and German counterparts. SOLUTION DESCRIPTION: The error message in now correct across all three languages (English, Dutch, and German). Solution: 160385 SITUATION IDENTIFIED IN: "Production Orders" (tisfc0101s000) SITUATION DESCRIPTION: When using a new tool with a tool life based on hours or number of times used and using this tool in session 'Est. Tool Requirements' for an operation with a short time, e.g., one minute, it was not possible to save a production order, which used this operation, due to the message 'Tool Usage is not allowed as tool life based on...'. SOLUTION DESCRIPTION: It is now possible to save a production order without getting the message 'Tool Usage is not allowed as tool life based on...' anymore. Solution: 160387 SITUATION IDENTIFIED IN: "Termination Process (actual)" (tfgld1212s000) SITUATION DESCRIPTION: When a foreign currency invoice with a vat on payment tax code is entered at one rate, and the rate changes and the currency difference is written off, the amount of the tax entry generated at the time of payment was written incorrectly in the tax analysis table (tfgld110). The tax amount was being calculated based on the new currency rate. Since general ledger accounts used for tax are not defined to recognize currency differences, the amount should be calculated based on the rate at the time of the invoice. SOLUTION DESCRIPTION: Corrections have been made so that when paying invoices where a currency difference has occurred and a vat on payment tax code is used, the interim tax clearing transactions will be calculated based on the original invoice currency rate. Solution: 160398 SITUATION IDENTIFIED IN: "cprrp1101s000" (Planned order line) SITUATION DESCRIPTION: When several operations exist for Planned Production order and the Critical Capacity Type of the Workcentre in the first operation is "Man Capacity" and the Critical Capacity Type of the Workcentre in the second operation is "Machine Capacity", the production time is calculated as 0 and seen in "Capacity Use by Planned Order" (cprrp2500m000). SOLUTION DESCRIPTION: The production time will be calculated based on the routing correctly. Solution: 160412 SITUATION IDENTIFIED IN: "cisli2200m000" (Compose/Print/Post Invoices) SITUATION DESCRIPTION: Transactions from Central Invoicing are posted to manually created batch when manual batch and Central Invoicing batch are being created at the same time. The reason behind this problem lies in the handling of the simultaneous update of the table "Maintain Last Used Batch Number" (tfgld014) by the sessions "Maintain Transactions"(tfgld1101m000) and "Compose/Print/Post Invoices" (cisli2200m000). Both sessions use the same batch number. SOLUTION DESCRIPTION: The handling of the update of the table "Maintain Last Used Batch Number" (tfgld014) by the session "Compose/Print/Post Invoices" (cisli2200m000) has been changed. If the table is being updated by the session "Maintain Transactions"(tfgld1101m000) then the session "Compose/Print/Post Invoices" (cisli2200m000) will get the next available batch number. Solution: 160413 SITUATION IDENTIFIED IN: "Imported Journals" (tfgld2513m000) SITUATION DESCRIPTION: There is no way to delete journal data once it has been imported into Baan. SOLUTION DESCRIPTION: The session has been adjusted to allow deletion of journals (Batch Header Data - tfgld213). Changes have also been incorporated to delete the corresponding document header (tfgld214) and document line (tfgld215) data. Solution: 160414 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Order" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure for sales order for a phantom item, the new structure is not generated if the "check standard item inventory" flag is set to YES and there is no economic stock for the components. SOLUTION DESCRIPTION: Now when generating project structure for sales order for a phantom item, the new structure is generated if the "check standard item inventory" flag is set to YES and there is no economic stock for the components. Solution: 160420 SITUATION IDENTIFIED IN: "Product Configurator" (tipcf5120s000) SITUATION DESCRIPTION: During the configuration process within the product configurator, when certain previous disabled features are dynamically enabled by constraints, these features are erroneously skipped. SOLUTION DESCRIPTION: Now during the configuration process within the product configurator, when certain previous disabled features are dynamically enabled by constraints, these features are properly processed. Solution: 160424 SITUATION IDENTIFIED IN: "Compare Package VRCs" (ttadv6450m000) SITUATION DESCRIPTION: In order to display differences due to program scripts of functions, a detailed report was required. SOLUTION DESCRIPTION: Changed it so that the compare non-language dependent components option was not tied to the detailed report option. Also made it so that if the non-language option is turned off, you cannot enter script or function data on the second tab. Solution: 160431 SITUATION IDENTIFIED IN: "Job Data" (ttaad5500m000) SITUATION DESCRIPTION: When setting up a job from ttaad5400m000, if you zoomed to ttaad5500m000 in order to set your job range then the last one you selected will be your default job in ttaad5102s000. SOLUTION DESCRIPTION: Changed ttaad5500m000 so that if its parent is ttaad5400m000 then it won't save the current selection as "last used". Solution: 160439 SITUATION IDENTIFIED IN: "Direct Network Communication" (ecedi7205m000) SITUATION DESCRIPTION: When processing a purchase order, with Vertex active and via EDI, that requires the addition of a new address record within Baan, the "Select Tax Jurisdiction" (tccom7250m000) session incorrectly pops up, requiring user interaction in choosing a GEO code. SOLUTION DESCRIPTION: The session has been corrected and now new address records, created as a result of a purchase order processed via EDI with Vertex active, will be automatically assigned the first valid GEO code based on the address information. Solution: 160456 SITUATION IDENTIFIED IN: "Project Parts" (tipcs2511m000) SITUATION DESCRIPTION: The functionality to duplicate a group of project parts between two projects was previously only working for standard items and not for customized items. SOLUTION DESCRIPTION: The functionality to duplicate a group of project parts between two projects has been improved. It is now possible to copy project parts with customized items between two projects, if the items exist for the target project. Non-existing target items will not be automatically created! Solution: 160458 SITUATION IDENTIFIED IN: "Commissions/Rebates Parameters" (tdcms0100s000) SITUATION DESCRIPTION: "Commissions/Rebates Parameters" (tdcms0100s000) may inadvertently remove Agreement Search Priorities for both Commissions & Rebates. This happens when one enters the session and only changes values on the first form and then saves the record. If any other form tab is displayed the error will not occur. SOLUTION DESCRIPTION: Changed the session to correctly and timely update the Agreement Search Priorities form fields to be sure that only the fields that users enter/modify are updated. Solution: 160468 SITUATION IDENTIFIED IN: "Print Finalized Transactions by Ledger Account" (tfgld1406m000) "Print Finalized Transactions by Ledger Account/Dimensions" (tfgld1407m000) SITUATION DESCRIPTION: The sessions Print Finalized Transactions by Ledger Account (tfgld1406m000) and Print Finalized Transactions by Ledger Account/Dimension (tfgld1407m000) do not have the functionality of printing the reports by Reporting Period. This functionality exists in Baan 4 but is missing in ERP. SOLUTION DESCRIPTION: The above functionality has been added into ERP as well. A new field "Period Type" has been added on the form. The user can choose to print the above sessions either by "Fiscal Period" or "Reporting Period". Solution: 160478 SITUATION IDENTIFIED IN: "Ledger History" (tfgld3501s000) "Distribution By Period For Ledger Account" (tfgld3505m000) SITUATION DESCRIPTION: When running the session if the percentage variance was greater than 999.99 or less than -999.99 then overflow characters '#####' were displayed on the form and an error was written into the bshell log. SOLUTION DESCRIPTION: A change has been made to several forms to allow another decimal place to the percent variance field. The sessions will now allow values from -9999.99 to 9999.99 to be displayed without error. Anything exceeding the above range will still be displayed as overflow characters "#####" and should be controlled by using proper data. Solution: 160499 SITUATION IDENTIFIED IN: "Finalization Process" (tfgld1212s000) SITUATION DESCRIPTION: When intergroup company transactions are finalized, the source document information is missing in tfgld106. SOLUTION DESCRIPTION: Problems in the script were causing inter-group company transactions to be treated as single company transactions. Hence the required information was not getting filled in. Solution: 160513 SITUATION IDENTIFIED IN: "Maintain Transaction Scheme Details" (tfgld0113s000) SITUATION DESCRIPTION: When entering a new line to an existing transaction schedule, it is only possible to enter this line at the end of the schedule. If the user wanted to add a new line in the middle of an existing schedule they had to delete all the lines they wanted after the new line, insert the new line, and re-enter all the data they just deleted. SOLUTION DESCRIPTION: This solution now allows the user to change the line number when entering a transaction schedule. Thus they can leave open line numbers within the schedule which can then be used to add more details at a later date without having to delete and re-enter data. Solution: 160526 SITUATION IDENTIFIED IN: "Commissions Calculated by Order/Schedule" (tdcms0150s000) SITUATION DESCRIPTION: When the calculation method parameter is set to "Paid Invoice", it is not possible to insert commissions manually in the session 'Commissions Calculated by Order/Schedule' (tdcms0150s000). The session always returns the message, "Invoice not fully paid." (tdcmss0067) SOLUTION DESCRIPTION: Manual commissions can now be entered, in the session. 'Commissions Calculated by Order/Schedule' (tdcms0150s000). These commissions cannot be approved until the invoice is paid but they can be entered. Solution: 160534 SITUATION IDENTIFIED IN: "Journal Vouchers (Multiple Lines)" (tfgld1115m000) SITUATION DESCRIPTION: When entering a multiple line journal voucher, it was not possible to create documents for complementary accounts. SOLUTION DESCRIPTION: Functionality has been added so that it is now possible to create journal vouchers to complementary accounts. The fields for 'currency base' and 'dual accounting scheme' are now input fields when entering the document header. Solution: 160556 SITUATION IDENTIFIED IN: "Customization Parts" (ttadv1177s000) SITUATION DESCRIPTION: User is unable to browse between individual customization parts. SOLUTION DESCRIPTION: Changed the type of the session so that it is now Modal Window with Menu and the browsing buttons now show up. Solution: 160560 SITUATION IDENTIFIED IN: "Import Data Dictionary" (ttiex1288m000) SITUATION DESCRIPTION: When importing ttadv240 records, the old ones were not first being deleted. SOLUTION DESCRIPTION: Fixed the select so that the delete actually happens now. Solution: 160626 SITUATION IDENTIFIED IN: "Post Transactions" (tpppc4202m000) SITUATION DESCRIPTION: When using session tpppc4202m000 (Post Transactions) or other sessions that are capable of creating transactions to finance, if the integration parameter (tfgld4150s000) "Posting to Next Open Period Allowed" is set - transactions can be posted into closed periods. SOLUTION DESCRIPTION: The process tfglddll4011 (Write Integration Transactions part II) has been modified to properly handle posting transactions to the correct period. Solution: 160627 SITUATION IDENTIFIED IN: "Print References to Parent" (ttaad4229m000) SITUATION DESCRIPTION: When running in multibyte, a particular component of the where clause would become too large, causing the program to fail and exit. SOLUTION DESCRIPTION: The component has been adjusted so that it is no longer affected by multibyte factors. Solution: 160644 SITUATION IDENTIFIED IN: "List Components" (tcibd3100m000) SITUATION DESCRIPTION: When first opening the session "List Components" (tcibd3100m000), a form error "Grid Selection out of Range" is displayed. SOLUTION DESCRIPTION: Session "List Components" (tcibd3100m000) is now executed properly without a "Grid Selection out of Range" error. Solution: 160680 SITUATION IDENTIFIED IN: "Compile Constraints by Generic Item" (tipcf2201m000) SITUATION DESCRIPTION: PCF constraints that are compiled in profiler mode and then executed via the associated PCF sessions do not generate any profiler output. SOLUTION DESCRIPTION: Now PCF constraints that are compiled in profiler mode and then executed via the associated PCF sessions do generate profiler output. Solution: 160682 SITUATION IDENTIFIED IN: "Calculate Commissions/Rebates" (tdcms0240m000) SITUATION DESCRIPTION: When calculating commissions for a sales order line with a zero amount and grading by the total amount in agreement parameters, the calculation is giving a 'No agreement found' error, instead of a 'Commission amount is zero error'. This is a problem, because there is a valid agreement, but the commission amount that is calculated should be zero. SOLUTION DESCRIPTION: The script has been modified to handle this situation correctly. Now, the commission agreement will be found correctly, and the calculated commission will be zero. If the user elects to print errors when calculating, the error 'Commission amount is zero.' will be given in the error report. Solution: 160683 SITUATION IDENTIFIED IN: "Performance Boosters" (tccomdll0200) SITUATION DESCRIPTION: When running multi bshells, it was possible that a unique message queue id could not be determined. This resulted in a fatal error and ending of the sessions. Creating a temporary file and using the unique i-node number from this file determine message queue ids. The system tries to find a new id, if the first one is already in use. This error only occurred in very rare situations when the system was mostly idle. The first temporary file got deleted and the new temporary file got the same i-node number. SOLUTION DESCRIPTION: When running multi bshells, the functionality to determine a unique message queue id has been improved. In case that the message queue id is already in use, a new temporary file gets created first with a new i-node number and afterwards the previous temporary file gets deleted. Solution: 160689 SITUATION IDENTIFIED IN: tfgld4418m000 (Print Financial Integration Transactions) SITUATION DESCRIPTION: Total amounts are calculated incorrectly, if there are debit and credit transactions present for the same ledger account. The amounts are simply added together, without taking into account the debit/credit indicator. SOLUTION DESCRIPTION: The totals are now printed correctly. Solution: 160725 SITUATION IDENTIFIED IN: "Production Orders" (tisfc0101s000) SITUATION DESCRIPTION: When creating a production order, it was possible to get an 'UTC Date Conversion Error' message with an abort of the process. SOLUTION DESCRIPTION: It is now possible to create a production order without getting the 'UTC Date Conversion Error' message. Solution: 160733 SITUATION IDENTIFIED IN: "Simulate orders" (cprrp1210m000) SITUATION DESCRIPTION: When deleting the only item a BOM, Simulate orders does not remove the requirement for the component. SOLUTION DESCRIPTION: Simulate orders will remove the requirements from item to component if there is no longer a link between them. Solution: 160737 SITUATION IDENTIFIED IN: "Transfer Planned Orders" (cprrp1250s000) SITUATION DESCRIPTION: It is possible to transfer planned distribution orders to warehousing even if the item on the planned order line has no cost price. SOLUTION DESCRIPTION: It is not possible anymore to transfer planned distribution orders to warehousing, if the item on the planned order line has no cost price. Solution: 160740 SITUATION IDENTIFIED IN: "Archive Warehousing Order History" (whinh2255m000) SITUATION DESCRIPTION: When the session "Archive Warehouse Order History (whinh2255m000)" processes a large number of records, the session stops with the error "Snapshot too old" [Error Code: 1555]. SOLUTION DESCRIPTION: Now, even when the session "Archive Warehouse Order History (whinh2255m000) processes a large number of records, the session doesn't stop with the error "Snapshot too old". Technical information about the solution: Every 30 minutes, the open queries are closed and started again. Hence, the rollback segments are cleared and the data are read again. Solution: 160741 SITUATION IDENTIFIED IN: "Product Configurator" (tipcf5120m000) SITUATION DESCRIPTION: During the product configuration process, the user is receiving the error message "record modified by other user ...". This was being experienced on a "display only" feature, on which a before input constraint was attached which disabled the input. SOLUTION DESCRIPTION: Now during the product configuration process, for the same generic structure as described in the SITUATION DESCRIPTION, the generic item is able to be configured without any "record modified by other user ..." error message. Solution: 160755 SITUATION IDENTIFIED IN: "Conversion Factors DAL" (tcibd003) SITUATION DESCRIPTION: When inserting conversion factors via the EXCHANGE product, the error message "Unit is not a base unit" is received, even for valid base unit values. SOLUTION DESCRIPTION: Now conversion factors can be inserted via EXCHANGE product without receiving the "Unit is not a base unit" error message for valid base unit values. Solution: 160761 SITUATION IDENTIFIED IN: "Print Object Information by Program Script / Libraries" (ttadv2439m000) SITUATION DESCRIPTION: The report was not showing the proper information about the objects. SOLUTION DESCRIPTION: Changed the code so that it uses the correct table fields and notices changes to VRC. Solution: 160762 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: after field layouts were not being printed properly in multicolumn reports. SOLUTION DESCRIPTION: Fixed the processing so that after field layouts were treated like any other detail process. Solution: 160768 SITUATION IDENTIFIED IN: "Print Unbalanced Ledger Accounts during Year End " (tfgld6403m000) SITUATION DESCRIPTION: The session designed to show unbalanced ledger accounts would also erroneously print data for balanced ledger accounts. This would only happen when selecting 'yes' for the option 'also include finalized transactions (tfgld106)' and if there were finalized opening balance transactions within the year/ledger account/currency ranges selected. SOLUTION DESCRIPTION: The problem occurred because the total of all finalized transactions including opening balance transactions were compared to history tables amounts. The history tables do not include opening balance amounts so the report would always show the amount of the opening balance transactions as a difference. - Selection of finalized transactions has been changed to not select opening balance transactions from the finalized transactions table (tfgld106) when running with the session using report option #1 "Compare History tables tfgld201 and tfgld205" - Selection of finalized transactions has been changed to select only opening balance transactions from the finalized transactions table (tfgld106) when running with the session using report option #2 "Compare Opening Balances tables tfgld203 and tfgld206" Solution: 160773 SITUATION IDENTIFIED IN: "Simulate orders" (cprrp1210m000) SITUATION DESCRIPTION: When an item has a master plan with an inventory plan in the past and "Simulate Orders"(cprrp1210m000) was ran using the scenario's dates, orders were planned using the past inventory plan as a demand. SOLUTION DESCRIPTION: Inventory plans in the past will not be considered as demand. Solution: 160779 SITUATION IDENTIFIED IN: "Product Configurator" (tipcs5120m000) SITUATION DESCRIPTION: When configuring a product variant, and then doing several page down operations, the first sequence number is repeated several times. SOLUTION DESCRIPTION: Now during the product configuration process, on doing several page down operations, the first sequence number remains stable. Solution: 160782 SITUATION IDENTIFIED IN: "Rebuild Planned Inventory Transaction" (whinp1200m000) SITUATION DESCRIPTION: If the session "Rebuild Planned Inventory Transaction (whinp1200m000)" is run in job mode, the allocation for the sales quotation is removed if the success percentage of the sales quotation is not equal to 100%. This problem doesn't occur if the session is run manually. SOLUTION DESCRIPTION: Now, if the session "Rebuild Planned Inventory Transaction (whinp1200m000)" is run either manually or through job mode, the allocation for the sales quotation is rebuilt, provided the success percentage in the sales quotation is greater than the minimum success percentage mentioned in the sales quotation parameter. Solution: 160800 SITUATION IDENTIFIED IN: "Maintain Journal Vouchers (Multiple lines)" (tfgld1115s000) SITUATION DESCRIPTION: In Baan version 4c, session tfgld1103m000 (Maintain Journal Vouchers) or tfgld1115s000 (Maintain Journal Vouchers - Multiple lines) no warning message is given when Recurring / Reversing Instructions have not been entered. In versions 5c and 5b the error message is reported, regardless of whether or not the instructions were entered. SOLUTION DESCRIPTION: In versions 5b and 5c the message has been changed from "Have you "Recurring/Reversing Instructions not created - Continue?" to "Recurring/Reversing Instructions not created - Continue?". Further the message is only displayed if the instructions were not entered vs. always being displayed on the session's exit. In 4c the latter functionality was completely back ported. Solution: 160813 SITUATION IDENTIFIED IN: "Generate Budget Structure for Sales Quotations" (tdsls1201m000) SITUATION DESCRIPTION: When generating a budget structure for a sales quotation, there is no input option "Include Cost Item". The same functionality of "Including Cost Items" that exists for sales needs to be added to the generation of budget structures. When generating a project structure for a sales order, the existing input option "Include Cost / Service Items" is incorrect. The option should only be applicable for cost items and not service items. The input option should show "Include Cost Item". SOLUTION DESCRIPTION: Now when generating a budget structure for a sales quotation, the input option of "Include Cost Item" is available. Now when generating a project structure for a sales order, the input option of "Include Cost Item" is now shown. Solution: 160826 SITUATION IDENTIFIED IN: "Print Warehousing Parameters" (whwmd0400m000) SITUATION DESCRIPTION: In the report, the inventory handling (INH) parameters 'Correct SFC Production Order till' and 'Over Delivery' are not printed. SOLUTION DESCRIPTION: Now, in the report, the inventory handling (INH) parameters 'Correct SFC Production Order till' and 'Over Delivery' are printed. Solution: 160861 SITUATION IDENTIFIED IN: "Simulate Orders" (cprrp1210m000) SITUATION DESCRIPTION: The planned orders generated for a customized item are always rounded. For Example - If the demand for a customized item is 12.656 Kg, the planned order is always generated for 13 kg (even though the rounding factor for the inventory unit is 0.0001). SOLUTION DESCRIPTION: The planned orders generated for a customized item will now be based on the rounding factor of the inventory unit and the domain of the field "Order Quantity Multiple of". Solution: 160873 SITUATION IDENTIFIED IN: iBaan Integration for Baan 5.0b - E-Procurement 2.1 "Purchase Orders BOI" (ccpurpoproc) "Purchase Orders BOI" (tdboidll0008) SITUATION DESCRIPTION: When a purchase order is created in Baan via the E-Procurement, and the delivery address is sent with the purchase order, this address code is not used when creating the purchase order. SOLUTION DESCRIPTION: Now when a purchase order is created in Baan via the E-Procurement, the delivery address code that is sent by E-Procurement will be used. If the delivery address code is NOT sent and a new actual address is sent, then a new address code with that new address data will be created in Baan. If NO address code or actual address data is sent, then the address code will default to the warehouse address. Solution: 160895 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000) SITUATION DESCRIPTION: When running session tfcmg3204m000 (File 1099-MISC) in ERP versions (5b & 5c) using the FORM print mode the session may not print the 'payers' telephone number on the 1099-MISC form. The session may also produce one or both of the following error messages in all supported versions 3.1b to 5c. For versions less than 4c the session id is tfcmgl200m000 (File 1099-MISC). Fatal error : Error 205 (Out of range) on tfcmg304xxx in db_insert(n) For versions before 4c: Fatal error : Error 205 (Out of range) on tfcmg938xxx in db_insert(n) The range error can occur when more than 10 payments have been applied to a business partner or supplier per a single invoice. When running in a multi-site environment the following error may also be generated: Fatal error: Error 100 (Duplicate value) on tfcmg304nnn (Max retries (10) For versions before 4c Fatal error: Error 100 (Duplicate value) on tfcmg938nnn (Max retries (10) The duplicate error can occur in multi-site environments were document types are not unique between individual companies. SOLUTION DESCRIPTION: The 1099-MISC report (FORM) has been corrected to properly print the 'payers' telephone number on the form. The 10 payments per business partner or supplier limitation have been increased to 1000. And for multi-site configurations, the session will now properly handle duplicate documents between different companies correctly. Solution: 160902 SITUATION IDENTIFIED IN: "Report Operations Completed" (tisfc0130s000) SITUATION DESCRIPTION: After installing solution 130722, partial completion of a production order or operation, with material backflushing, leads to incorrect updates for subsequent materials to issue. SOLUTION DESCRIPTION: Partial completion of a production order or operation, with material backflushing, no longer results in any problems with subsequent material issue. Solution: 160911 SITUATION IDENTIFIED IN: "Print Commission/Rebate Invoices" (tdcms2402m000) SITUATION DESCRIPTION: When calculating and invoicing commissions/rebates, the exchange rate type from the CMS Parameters should be used, if one has been defined there. It is currently using the exchange rate type from the sales order. SOLUTION DESCRIPTION: The programs have been modified to use the exchange rate type from CMS parameters for commissions/rebates whenever one is defined in the parameters session. If it is not defined, the programs use the default exchange rate type as it has in the past. Solution: 160913 SITUATION IDENTIFIED IN: "Find and remove duplicate records." (tdcor0014m000) SITUATION DESCRIPTION: When entering a range of orders to be corrected, the correction program only fixes the first position of the first order. The program then must be re-run over an over to find and correct the remaining orders and positions. SOLUTION DESCRIPTION: The program has been modified and will now correctly find and correct all of the duplicate records in the specified range. Solution: 160920 SITUATION IDENTIFIED IN: "Export Data Dictionary" (ttiex1280m000) SITUATION DESCRIPTION: The header for the dump was not listing function scripts as being dumped, even though it was selected on the form. SOLUTION DESCRIPTION: Preserved the value on the form so that once the header is created, the original value still exists. Solution: 160927 SITUATION IDENTIFIED IN: "Generate Sales Quotations for Project" (tipcs2240m000) SITUATION DESCRIPTION: When generating sales quotations from budget parts and there is no sales item data for the budget part, the quotation header will be created, but the line will not be created, even though the resulting message is that the quotation was created OK. SOLUTION DESCRIPTION: Now if there is no item sales data for a budget part, when generating a sales quotation for this part, there will be an error message indicating that the item has no sales item data. Solution: 160928 SITUATION IDENTIFIED IN: "Print PCS Project Transaction Specification" (tfgld4418m100) SITUATION DESCRIPTION: Report totals are calculated incorrectly. SOLUTION DESCRIPTION: The report totals are now calculated correctly. Solution: 160934 SITUATION IDENTIFIED IN: "Period Status" (tfgld0107m000) SITUATION DESCRIPTION: There are problems when attempting to close tax periods. #1- An error message that unposted fixed asset transactions existed was given even though no such transactions existed. This occurred because the tax year and period being closed were being compared to the fiscal year/period in the fixed asset tables. #2- A check for unposted recurring transactions was not done correctly when the company calendar has different tax and fiscal years. When closing a tax period, the fiscal year was being checked instead of the tax year. This could result in an error message that unposted recurring transactions exist when no transactions existed or result in no error message being given when there were transactions present. SOLUTION DESCRIPTION: - The session will now only check for unposted fixed asset transactions when closing fiscal periods. - The error check for unposted recurring transactions will now be done based on tax year when closing a tax period. - The error message will now display the fiscal year as part of the error message for unposted recurring transactions present. Solution: 160937 SITUATION IDENTIFIED IN: "Print Trial Balance - Dimensions" (tfgld3405m000) SITUATION DESCRIPTION: 1. Trial Balance reports could not be printed for all companies within the group. 2. Reports don't have enough space for amounts and total amounts. Amounts are shown as ############## instead of real numbers. SOLUTION DESCRIPTION: 1. New option "All companies of group" that is enabled only for multi companies has been introduced. If this new option is selected then report will be printed for all companies within the group. In case of dependent currency system selection of the option "All companies of group" disables the currency rotation because companies may have different currencies except for the reference currency. 2. Format of the report fields has been expanded to allow printing of more characters and to show amounts according to the selected currency format. The reports now have the maximum possible size for the amount fields. Anything more than this will have to be customized by adjusting the formats and report fields. Solution: 160942 SITUATION IDENTIFIED IN: "Process Hours Accounting" (tihra1210m000) "Process Hours and Expenses" (bptmm1203m000) SITUATION DESCRIPTION: When processing hours accounting with a negative total amount of hours for a project and activity, a fatal error 205 (out of range) occurred. SOLUTION DESCRIPTION: When processing hours accounting with a negative total amount of hours for a project and activity, an error message is now given on the report and the session finishes normally. Solution: 160955 SITUATION IDENTIFIED IN: "Plan Item defaults" (cprpd1110s000) SITUATION DESCRIPTION: When entering a new plan item group in session "Plan Item Defaults"(cprdp1110s000), it was possible to reduce the planning horizon to below the order horizon and save. SOLUTION DESCRIPTION: The planning horizon field should only be changeable if Maintain Master plan has been set to yes. Solution: 160963 SITUATION IDENTIFIED IN: "Purchase Order Creation DLL" (tdpurdll1234) SITUATION DESCRIPTION: When e-procurement sends a purchase order request to Baan, with a purchase unit that is different from the purchase unit of the item in Baan, the newly created purchase order's quantity is incorrectly multiplied by the conversion factor between the two different units. SOLUTION DESCRIPTION: Now when e-procurement sends a purchase order request to the Baan, with a purchase unit that is different from the purchase unit of the item in Baan, the newly created purchase order's quantity is not changed. Solution: 160964 SITUATION IDENTIFIED IN: "Sales Order Lines" (tdsls4101s000) SITUATION DESCRIPTION: Even with all proper parameters set, it is not possible for commissions to calculate automatically or interactively. One must manually calculate commissions later. SOLUTION DESCRIPTION: Automatic and Interactive commission calculation is now correctly executed from within "Sales Order Lines". Solution: 160975 SITUATION IDENTIFIED IN: "Maintain Purchase Invoice Transactions" (tfacp1120s000) SITUATION DESCRIPTION: If "Dimension Ranges by Ledger Account" (tfgld0509m000) were empty for a ledger account, the session would accept any dimension for that ledger account. SOLUTION DESCRIPTION: An error message is now given when the user put a dimension on a ledger account, which has no valid dimension range. Solution: 160980 SITUATION IDENTIFIED IN: "Easy Warehousing Order Entry" (whinh2202m000) SITUATION DESCRIPTION: It is not possible to process multiple easy transfer warehousing orders simultaneously. When the second easy transfer warehousing order (which normally gets processed quickly) is started immediately after the first easy transfer warehousing order (which involves multiple lots and normally takes a longer time), the system waits for the first order to get completed before the second order gets processed. SOLUTION DESCRIPTION: Now, it is possible to process multiple easy transfer warehousing orders simultaneously. Solution: 160985 SITUATION IDENTIFIED IN: "Clear Corrupted Inventory" (whcor0200m000) SITUATION DESCRIPTION: Due to inventory corruption there is need for a generic correction program to rebuild the inventory. SOLUTION DESCRIPTION: This correction program will correct inventory and the receipt/consumption tables: When checking the check box 'Rebuild Inventory Transactions by Item Warehouse' on the first form the table whinr110 (Inventory transactions by Item/Warehouse) is checked. Also. The inventory on hand, on item/warehouse level, (whwmd215.stoc) will be balanced with the inventory transactions by Item/Warehouse (whinr110) when this check box is set. The following tables will be corrected when checking the check box 'Rebuild Receipt/Consumption transactions' on the first form: - whinr112 (Inventory receipt transactions) - whinr114 (Inventory receipt transaction consumptions) Correcting Inventory: To be able to correct the corrupted inventory additional checks/updates are done like: - detecting/inserting missing shipment lines - detecting/correcting outbound line status. The inventory can be checked/corrected by item and location type as defined on the 2nd form. The inventory values that are corrected by this session in order of detail are: Inventory on item level: - Inventory on hand (tcibd100.stoc) - Inventory on hold (tcibd100.bloc) Inventory on item/warehouse level: - Blocked inventory (whwmd215.blck) - Location Allocated inventory (whwmd215.alpl) * Note that the inventory on hand on item/warehouse level (whwmd215.stks) is normally not updated by this program. Inventory on item/warehouse/lot level: - Inventory allocated (whltc105.stka) - Inventory on hold(whltc105.stkh) * Note that the inventory on hand on item/warehouse/lot level (whltc105.stks) is normally not updated by this program. Stock point level: - Inventory on hand (whinr140.stks) - Inventory on hold (whinr140.stkh) - Inventory on order (whinr140.stko) - Allocated inventory (whinr140.stka) Inventory structure level - Inventory on hand in inventory unit (whinr150.stks) - Inventory on hand in storage unit (whinr150.strs) - Inventory blocked in storage unit (whinr150.strb) - Inventory allocated in inventory unit (whinr150.stka) - Inventory allocated in storage unit (whinr150.stkr) Form description: On the 2nd form the following options are available: - Rebuild Locations of type 'Receipt' - Rebuild Locations of type 'Inspection' - Rebuild Locations of type 'Pick/Bulk' or empty Locations - Rebuild Location of type 'Staging' Selecting one or more of these options will make the program correct the inventory on stock point (whinr140) and inventory structure (whinr150) level on the selected location type. - balance inventory When this option is selected the inventory by item (tcibd100), inventory by item/warehouse (whwmd215) and inventory by item/ warehouse and lot (whltc105) is corrected. A part of this correction is based on the inventory figures on stock point level. Therefore always first the inventory should be rebuild by location before 'balance inventory' is set. The inventory on hand figures in the several inventory tables are balanced based on the inventory on item/warehouse level. This means when selecting this option it is possible that the inventory on hand on stock point level is changed. There are two possibilities: 1) Inventory on hand on item/warehouse level > inventory on hand on stock point level. The program will increase the inventory on hand on stock point level and inventory structure level. In case of a location controlled warehouse/item combination the created inventory is put on the 'correction' location as defined on the session form. In case of none location controlled item/warehouse combination the created inventory is put on the empty location. 2) Inventory on hand on item/warehouse level < Inventory on hand on stock point level. The program will decrease the inventory on hand on stock point level and inventory structure level. This is done based on the outbound priority after the program first tried to decrease the inventory on the 'correction' location. - correction location Not actual location. If the filled in location does not exist yet the program will automatically create it. When the program did create this location it will be blocked for all transactions. This location is used by the program in case the inventory on stock point level and inventory structure level needs to be decreased in order to get the inventory tables balanced (see balance inventory) - Allow automatic processing of Adjustment Orders There are instances where the correction program is unable to decrease the inventory at location level (whinr140/whinr150) or at lot level to balance the inventory with the inventory on hand registered at item/warehouse level (whwmd215.stoc). In that case message code 0001 ("Stock Points in Warehouse ### can not be decreased by ###") or message code 0002 ("Stock Points for lot ### in Warehouse ### can not be decreased by ###") is printed. This situation can be corrected by processing an adjustment order to get additional inventory available. When setting the option 'Allow automatic processing of Adjustment Orders' this adjustment orders is created and processed automatically and the correction program will continue with correcting the situation. On the third form the following options are available: - Insert missing Shipment Lines This option will detect/create missing shipment lines. This option will be automatically set when the options 'Rebuild Locations of type 'Pick/Bulk' or empty Locations' or 'Rebuild Location of type 'Staging' is set. This because the inventory on the pick/bulk/staging or empty locations are partially rebuild based on the shipment lines. - Check Outbound Line Data This option will perform checks on the outbound line quantities and check/correct the outbound line status. Also this option is automatically set when the options 'Rebuild Locations of type 'Pick/Bulk' or empty Locations' /'Rebuild Location of type 'Staging' or 'Insert Missing Shipment Lines' is set. - Maximum execution time and unit. In this field the maximum time the program is allowed to run can be filled in. After correcting the inventory of each item the program will check whether the maximum execution time has been exceeded. If so the program will quit and the report will be printed. On the report also a message is printed that the program has been quit due exceeding of the maximum execution time. Solution: 160988 SITUATION IDENTIFIED IN: "Imported Journals" (tfgld2513m000) SITUATION DESCRIPTION: The session tfgld2215m000 (Import Journal Voucher Batches by ID Number) is not updating the import batch header information after importing. This causes the display session tfgld2513m000 (Imported Journals) to not display the username and batch number used/created during the import process. SOLUTION DESCRIPTION: The session tfgld2215m000 (Import Journal Voucher Batches by ID Number) has been corrected to update the username and batch number per successful import. Solution: 160998 SITUATION IDENTIFIED IN: "Calculate Cost Prices by Project" (tipcs3250m000) SITUATION DESCRIPTION: When buying purchased items for a project and returning the full quantity for a different amount, the actual average item cost price was too high, because the total quantity received was set to 1 instead of the actual quantity of 0. Example: Purchase order for 10 x item X for $100, return order for 10 x item X for $60. The total cost for the project is $400, but the actual inventory of item X is 0. The actual cost price used to be calculated as $400 divided by 1, which resulted in a very high average actual cost price for item X. SOLUTION DESCRIPTION: The average actual cost price for this item is now set to $0 in this situation, but the cost is still reflected in the project costs. Solution: 161000 SITUATION IDENTIFIED IN: "Planned Inventory Movements by Order" (cprrp0511m000) SITUATION DESCRIPTION: After selecting an order/item combination in session "Planned Inventory Movement by item" (cprrp0511m000) and then zooming to "Planned Inventory Transaction by Order", the wrong item would be displayed. SOLUTION DESCRIPTION: When after selecting an order/item combination in session "Planned Inventory Movement by item" (cprrp0511m000) and then zooming to "Planned Inventory Transaction by Order", the correct item and orders will be displayed. Solution: 161011 SITUATION IDENTIFIED IN: "Report Operations Completed" (tisfc0130s000) SITUATION DESCRIPTION: When backflushing for a partial quantity of materials, with a to issue quantity less than the quantity required to produce one unit of the manufactured item, the wrong quantity is issued and subsequent delivery for the material line is calculated incorrectly. SOLUTION DESCRIPTION: Material is issued for the correct quantity and subsequent delivery is calculated correctly in the above-mentioned scenario. Solution: 161020 SITUATION IDENTIFIED IN: "Simulate Master Plan" (cprmp1202m000) SITUATION DESCRIPTION: 1. When Simulating Master Plan for different range of items twice, without exiting the session, the session aborts with Fatal Error "last.item.sost.rule index out of dims". 2. When Simulating Master Plan, Planned Distribution Order lines are never created (only distribution order header created) SOLUTION DESCRIPTION: 1. When Simulating Master Plan for different range of items twice, without exiting the session, the session will now run successfully. The sourcing rules are read for every run. 2. When Simulating Master Plan, Planned Distribution Order lines are created correctly. Solution: 161021 SITUATION IDENTIFIED IN: "Signals by item/Planner" (cprao1125m000) SITUATION DESCRIPTION: The whole signal is not displayed in session "Signal by item/Planner" (cprao1125m000). SOLUTION DESCRIPTION: All positions of the signal will be displayed in "Signal by item/Planner" (cprao1125m000). Solution: 161028 SITUATION IDENTIFIED IN: "Version Scan Tool" (ttaad0500m000) SITUATION DESCRIPTION: When the ORACLE_HOME environment variable exceeds 32 characters in length, it is truncated. SOLUTION DESCRIPTION: Changed the length of the variable that the ORACLE_HOME value is read into so that it can all be seen. Solution: 161031 SITUATION IDENTIFIED IN: "E-procurement backend BOI" (ccpurpoproc) ("bcbe" connnection only) SITUATION DESCRIPTION: When e-procurement sends a purchase order request to Baan, with a purchase unit that is different from the purchase unit of the item in Baan, the newly created purchase order's quantity is incorrectly multiplied by the conversion factor between the two different units. SOLUTION DESCRIPTION: Now when e-procurement sends a purchase order request to the Baan, with a purchase unit that is different from the purchase unit of the item in Baan, the newly created purchase order's quantity is not changed. Solution: 161036 SITUATION IDENTIFIED IN: "Journal Vouchers" (tfgld1103s000) "Journal Voucher (Multi-Line)" (tfgld1115m000) SITUATION DESCRIPTION: When re-entering a Journal Voucher batch, if any other non-finalized batch exists with the same number and document type (from other years) then that document becomes visible for update in the current batch. SOLUTION DESCRIPTION: The selection of documents to be displayed was not checking whether the year on the batch was the same as the current batch. Thus documents in batches from previous years, which were still un-finalized, got displayed in the current batch. This has been corrected. Solution: 161041 SITUATION IDENTIFIED IN: "Spool Close" (ttstpsplclose) SITUATION DESCRIPTION: When printing to a windows printer using BI interface an error is given that the report file can not be found. SOLUTION DESCRIPTION: Fixed the positioning of the quotation marks around the filename so that bwprint works correctly. Solution: 161045 SITUATION IDENTIFIED IN: "Tax analysis" (tfgld1520m000) SITUATION DESCRIPTION: When user switches the finance company in the session and balances are shown in the currency which is home currency in the current finance company but not in the switched finance company, the system generates error message "No home currencies are defined for company xxx". SOLUTION DESCRIPTION: Now if currency on the form is not one of the home currencies of the new company, then balances will be shown in local currency (home currency 1) of the new company. Solution: 161055 SITUATION IDENTIFIED IN: "Conversion Factors" (tcibd0103m000) SITUATION DESCRIPTION: When entering a conversion factor with 8 digits after the decimal and then tabbing through the field, the value shown is rounded to 6 digits after the decimal with the last 2 digits shown as "0", even though the actual value stored in the database contains the complete value entered. SOLUTION DESCRIPTION: Baan standard functionality is to round any real value to 6 digits after the decimal. The form for "Conversion Factors" has been modified to show only the 6 digits after the decimal as per Baan standard. Solution: 161089 SITUATION IDENTIFIED IN: "Product Configurator" (tipcf5120m000) SITUATION DESCRIPTION: During the configuration process, a feature that has been enabled for input via a before input constraint is erroneously skipped. SOLUTION DESCRIPTION: Now during the configuration process, a feature that has been enabled for input via a before input constraint is not skipped. Solution: 161090 SITUATION IDENTIFIED IN: "Global Selection of Batches For Finalization" (tfgld1210m000) SITUATION DESCRIPTION: The session has a check to make sure all transaction lines have been processed by the background programs if the update mode of the transaction type is "Real Time" or "End Of Session". This check was not done correctly in a multi-finance environment which could cause batches to be selected for finalization that have not yet been processed by the background process. SOLUTION DESCRIPTION: Error checks for invalid reporting periods are no longer done if a company does not use reporting periods. Batches which contain transaction lines unprocessed by the background programs (Real Time or End of Session update mode) will no longer be selected for finalization in a multi-company environment. Solution: 161096 SITUATION IDENTIFIED IN: "Print Differences between Logistic and Financial Integration Tables" (tfgld4418m300) SITUATION DESCRIPTION: For integration transactions Receipt or Shipment Variance under transaction origin Warehousing (Transfer) or Warehousing (Transfer Manual), differences which did not exist were being printed on the report. SOLUTION DESCRIPTION: This was being caused by an incorrect check on the sequence number. The correct check is now done on the sequence number for these Transaction Origin/Financial Transaction combinations. Solution: 161098 SITUATION IDENTIFIED IN: "Find and Remove Duplicate +/- Records in tdcms050" (tdcor0014m000) SITUATION DESCRIPTION: When running the correction program to remove duplicated +/- records from commissions/rebates, the user sometimes gets the error 'No records found', even though there are +/- records on the order. SOLUTION DESCRIPTION: The program has been modified and will now find these records. Solution: 161127 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000, tfcmgl200m000) SITUATION DESCRIPTION: When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session does not select invoices that have been reconciled. SOLUTION DESCRIPTION: The session's tfcmg3204m000 and tfcmgl200m000 have been modified to select invoices that have reconciled. Solution: 161128 SITUATION IDENTIFIED IN: "Copy Master Plan between Scenarios" (cprmp2203m000) SITUATION DESCRIPTION: After adding the session to job and viewing the settings for the session in the session " Sessions by Job (ttaad5501m000)", some values in the form are changed automatically. SOLUTION DESCRIPTION: When viewing the settings for the session in the session " Sessions by Job (ttaad5501m000)", values in the form will not change unless changed by the user. Also when copying the plan, the quantities are rounded based on the domain and the inventory unit of the item. Solution: 161130 SITUATION IDENTIFIED IN: "Material Issue for Production Orders" and "Report Orders Completed" (ticst0101s000 and tisfc0120s000) SITUATION DESCRIPTION: When issuing material for a rework production order, the lot size is decreased. The lot size of the issued lot is subsequently increased when the rework production order is reported completed. SOLUTION DESCRIPTION: The lot size is not decreased when issuing to a rework production order. If the same lot is received into inventory following the completion of the rework production order, the lot size is not increased. Solution: 161132 SITUATION IDENTIFIED IN: "Calculate Commissions/Rebates" (tdcms0240m000) SITUATION DESCRIPTION: When you do a partial delivery and confirm the backorder before calculating commissions, no commissions get calculated. SOLUTION DESCRIPTION: The program has been modified to correctly calculate commissions when the backorder is confirmed before calculating. Solution: 161135 SITUATION IDENTIFIED IN: "General Table Maintenance" (ttaad4100) SITUATION DESCRIPTION: It was possible to create a new table using ttaad4100 in a company that did not exist. SOLUTION DESCRIPTION: If the company does not exist, do not allow the table to be created. Solution: 161145 SITUATION IDENTIFIED IN: "General Table Maintenance" (ttaad4100) SITUATION DESCRIPTION: Solution 161135 was not completely ported to B50_b. SOLUTION DESCRIPTION: Completed to porting. Solution: 161149 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: Errant variance postings lead to work in process amounts for production orders upon closing of the orders. SOLUTION DESCRIPTION: Variance calculations are corrected and work in process for production orders is zero upon closing. Solution: 161153 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: Mulitcolumn horizontal printing did not work properly with multiple layouts or after.field layouts. SOLUTION DESCRIPTION: Fixed the multicolumn horizontal logic so that it works properly. Solution: 161161 SITUATION IDENTIFIED IN: "E-procurement backend BOI" (ccpurpricing) SITUATION DESCRIPTION: When retrieving the purchase price lookup for E-Procurement, the conversion factor for the purchase price unit and the E-Procurement purchase unit is not considered in the price. Thus the price retrieved is not correct. SOLUTION DESCRIPTION: Now the retrieved lookup purchase price is correctly considering the conversion factor resulting in the correct price. Solution: 161174 SITUATION IDENTIFIED IN: "Baan Applications Integrations Parameters" (cfint0100s000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161175 SITUATION IDENTIFIED IN: "Product Configurator" (tipcf5120m000) SITUATION DESCRIPTION: When navigating to previous option sets within the product configurator, and there are display features on the current option set being calculated via before input constraints, the newly calculated values are not being updated to the database. Conversely, when navigating to next option sets, the values are saved to the database. SOLUTION DESCRIPTION: Now within the product configurator, when navigating to previous option sets, the display feature values on the current option set are saved to the database. Solution: 161181 SITUATION IDENTIFIED IN: "Simulate Orders" (cprrp1210m000) SITUATION DESCRIPTION: When generating planned purchase orders for customized items, the purchase orders generated are always rounded to 1. SOLUTION DESCRIPTION: When generating planned purchase orders for customized items, the purchase orders generated will be rounded to the rounding factor of the inventory unit or the rounding of the domain, whichever is larger. Solution: 161184 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000, tfcmgl200m000) SITUATION DESCRIPTION: When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session may not select invoices reconciled in the next year (2003). SOLUTION DESCRIPTION: The session's tfcmg3204m000 and tfcmgl200m000 have been modified to use the anticipated payment year vs. the reconciled year. Solution: 161186 SITUATION IDENTIFIED IN: "Outgoing Messages by Session" (ecedi0115m000) "Print Outgoing Messages by Session" (ecedi0415m000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161188 SITUATION IDENTIFIED IN: "Companies" (tccom0100s000) "Item Segmentation" (tcibd0100s000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161189 SITUATION IDENTIFIED IN: "Activities by Order Type" (tdpur0560m000) "Activities by Order Type" (tdsls0560m000) "Sales Order Types" (tdsls0194s000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161190 SITUATION IDENTIFIED IN: "Transaction Types" (tfgld0111s000) "Payment Receipt Methods" (tfcmg0140s000) "Audit Payments" (tfcmg1255m000) "Create Payment Orders" (tfcmg1256m000) "Audit Direct Debits" (tfcmg4255m000) "Create Direct Debit Orders" (tfcmg4256m000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161191 SITUATION IDENTIFIED IN: "EDM Parameters" (tiedm0100s000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161192 SITUATION IDENTIFIED IN: "Activities by Procedure" (whinh0106m000) "Master Data Parameters" (whinh0100s000) SITUATION DESCRIPTION: New/Customized sessions were not found when a session checked for the existence of other sessions using the tools function tt.session.present(). SOLUTION DESCRIPTION: The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function are now recompiled and delivered by this solution. Solution: 161202 SITUATION IDENTIFIED IN: "Spool Open" (ttstpsplopen) SITUATION DESCRIPTION: If user saves defaults, the saved font will override the report's default font and unpredictable results will follow. SOLUTION DESCRIPTION: No longer use the default loaded through 'Get Defaults'. Solution: 161209 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000, tfcmgl200m000) SITUATION DESCRIPTION: When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session will not select invoices if the tax year and fiscal year are the different. SOLUTION DESCRIPTION: The session's tfcmg3204m000 and tfcmgl200m000 have been modified to exclusively use the tax year. Solution: 161213 SITUATION IDENTIFIED IN: "Print Tax Analysis" (tfgld1420m000) SITUATION DESCRIPTION: 1. If multiple taxes are on the report then total net amounts by company and by country will include net amounts only from the first tax lines of the multiple taxes. But if report is to be printed only for the tax authority that is linked to the tax of the second line then total net amount will be zero because first line tax is not printed. 2. Total tax amount by tax authority group is printed after each change of the tax authority, but not after change of the tax authority group. 3. When form fields "Tax authority group from" and "Tax authority group to" are not blank then records without any tax authority group will be printed as well. 4. Some net amounts are printed with a star while they should not. SOLUTION DESCRIPTION: 1. Total net amounts include net amount from the first PRINTED tax line of the multiple tax. 2. Report layouts have been adjusted. 3. Empty tax authority groups are checked. 4. Star is printed only for the net amounts that are not included in the totals. Solution: 161214 SITUATION IDENTIFIED IN: "Job Session History" (ttaad5511m000) SITUATION DESCRIPTION: The label over the sequence field was listed as Session Number. SOLUTION DESCRIPTION: Changed the label to Sequence Number. Solution: 161224 SITUATION IDENTIFIED IN: Print Program Structure Diagram (ttadv2430m000) SITUATION DESCRIPTION: Running Print Program Structure Diagram (ttadv2430m000) on an NT system, when printing is attempted, get the error: "PTY error: "no more PTY´s available"" SOLUTION DESCRIPTION: Corrected how sorting is done for this session's reports. It now works correctly for NT as well as Unix without the specified error. Solution: 161226 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000, tfcmgl200m000) SITUATION DESCRIPTION: When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session may not include invoices that were not processed via anticipated payment steps. SOLUTION DESCRIPTION: The session's tfcmg3204m000 and tfcmgl200m000 have been modified to include electronic or wired invoice / payment scenerios. Solution: 161235 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000) SITUATION DESCRIPTION: When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), invoices paid by wire transfer payment method using no anticipated steps are not selected for 1099's when paid in the following year. When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session may select only one check for invoices with several checks (this was happening for invoices with and without anticipated steps) SOLUTION DESCRIPTION: The session's tfcmg3204m000 and tfcmgl200m000 have been modified to include electronic or wired invoice and multiple payment scenarios. Solution: 161236 SITUATION IDENTIFIED IN: "Print Finalized Transactions By Date" (tfgld1440m000) SITUATION DESCRIPTION: -When running the session in a multicompany/dependent currency system and printing for all companies it was possible for the wrong currency or for no currency to be displayed on the report. -(B50_c only) The option 'rotate currency' was not always enabled/disabled at the correct time. This option should be disabled if running the session in a multicompany/dependent currency system and printing for all companies. On changing the form field 'print all companies' the session would not check to see if the rotate currency option should be enabled or disabled. SOLUTION DESCRIPTION: Changes have been made to the reports so that the same currency selected on the session form is displayed on the report header. All amount fields will also print in the currency format of this currency. The program script has been changed so that when selecting or unselecting 'Print All Companies" the program will check to determine if the user should be allowed to choose the option "rotate currency". Solution: 161243 SITUATION IDENTIFIED IN: "Receive Sales Orders" (tdslsdll4280) SITUATION DESCRIPTION: Updating a sales order with a receipt date that is earlier than the delivery date, through the Baan Open World DLL, is incorrectly allowed with no returned error. SOLUTION DESCRIPTION: Now updating a sales order receipt date that is earlier than the delivery date, through the Baan Open World DLL, will result in a returned error "Receipt date cannot be before delivery date". Solution: 161252 SITUATION IDENTIFIED IN: "Request and Return Tools" (titrp0215m000) SITUATION DESCRIPTION: The helptext indicates that a tool request can be processed for a production order with status 'Completed' which is incorrect. SOLUTION DESCRIPTION: The helptext for the session has been modified to indicate that a tool request can only be processed for production orders that are 'Released' or 'Active'. Solution: 161259 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: When closing more than one production order with each order having more than one cost component with a price variance, the price variance amounts for an order are not cleared between orders and are added into each subsequent order's price variances. This results in incorrect price variances and incorrect calculation variances for a production order. SOLUTION DESCRIPTION: The price variance amounts are cleared between production orders so that the price variance will not incorporate amounts from previously closed orders. Solution: 161261 SITUATION IDENTIFIED IN: "Print PCS Project Transaction Specification" (tfgld4418m100) SITUATION DESCRIPTION: 1) Cannot print "Cost of Goods Sold" financial transactions. 2) When printing the session even if the "Include Archive Company" choice on form 1 was not selected the error "Arcive company cannot be 0" shows up when trying to run the report. 3) Summarized report prints no data when the detail report prints data for the same selection criteria. Totals in summarized report are incorrect. 4) Lines are printed double on the detail report "Financial Project Transactions". 5) Period in summarized report is always zero 6) Both fitr's "Add calc Office variance" & "Correction" get selected/deselected when either one fo the fitr's is checked or unchecked SOLUTION DESCRIPTION: 1) Added financial transactions "Cost of Goods Sold" on form 3 of the report, couple of financial transactions have been moved to form 4 to make space for this fitr. Necessary changes in script have also been made. 2) This was caused because the check.input.section, was being activated when the user tried to process. A condition has been added in the check.input section to only do the check on archive company if the user selects that choice. 3) Necessary changes have been made and some report variables, which were not reinitialized were causing the incorrect amount problems. 4) The records were printing twice as there were dr & cr lines for the transactions. Since the report details are identical for bot lines on the report changes have been made to print the line only once. 5) The domain on the report for fiscal period was wrong , domain was tfgld.year instead of tfgld.prod. 6) The financial transactions "Add Calc. Office Variance" on form 3 had the wrong array element number, it was 10 instead of 1. This caused problems since the fitr "Correction" was supposed to be element 10. Solution: 161270 SITUATION IDENTIFIED IN: "Period Status" (tfgld0107m000) SITUATION DESCRIPTION: During the process of closing a fiscal period for GLD module program checks whether depreciation has been calculated for this period. Since depreciation cannot be calculated for the future periods these periods cannot be closed. Such functionality restricts users from having only one open period at a time. SOLUTION DESCRIPTION: Now depreciation will be checked only in case of final close of a period or in case of close of a year. Solution: 161271 SITUATION IDENTIFIED IN: "Print Non-Finalized Transactions" (tfgld1401m000) SITUATION DESCRIPTION: The defaulting of currency is not done correctly in a dependent currency system. The session defaults are company 000 to 999 and the screen currency = reference currency. When the user changes the company range to print only the current company the currency default does not change from reference currency, to local currency as it should. When running the session in a job the report is always printed in the local home currency instead of the currency specified when creating the job. SOLUTION DESCRIPTION: Changes have been made in the program so that when running in a dependent currency system for only the current company the local home currency is defaulted instead of the reference currency. Now the report will print in the user specified currency when running the session in a job. Solution: 161274 SITUATION IDENTIFIED IN: "Maintain Sessions" (ttadv2500m000) SITUATION DESCRIPTION: In most of the tools Maintain sessions there was an option on the Specific menu called Verify Technical Design. This option tried to start a session that does not exist. SOLUTION DESCRIPTION: Removed the option from the form. Solution: 161281 SITUATION IDENTIFIED IN: "Print Tax Analysis" (tfgld1420m000) SITUATION DESCRIPTION: In the US there are two kinds of taxes that need to be tracked by business. 1099 taxes that have to work with calendar years and the regular purchase/sales tax which can use any calendar (e.g. company calendar). When a business has to support both these they have to use the tax calendar for one purpose say 1099 and the use the fiscal calendar for the purchase/sales tax because we do not have two tax calendars. In case of summary report the session "Print Tax Analysis" (tfgld1420m000) prints one line per tax country, code, tax/fiscal period and the amount details. When running this report over multiple periods there is no way to know what the total for the tax code for the entered range of periods is. Thus option of printing totals by tax codes should be available for the summary reports. SOLUTION DESCRIPTION: Required option "Print Totals by tax Code" has been added. This option is enabled for the summary reports only. If "Print Totals by tax Code" is selected then totals for purchase and sales will be printed for each tax code. Solution: 161286 SITUATION IDENTIFIED IN: "Costing History by Item Group" (ticst3401m000) SITUATION DESCRIPTION: When printing the report, large amounts in 'Total Estimated', 'Total Actual' or 'Total Result' overrun the set display values for the report and only "####" appears where the totals should be. SOLUTION DESCRIPTION: The formatting of the report has been adjusted and all totals now appear correctly. Solution: 161288 SITUATION IDENTIFIED IN: "Confirm Shipments/Loads" (whinh4275m000) SITUATION DESCRIPTION: When running the Confirm Shipments/Loads session (whinh4275m000), the system locks up. This only occurs when using CMS with automatic commission calculation and when we are short shipping a sales order line that has commission relations linked to it. SOLUTION DESCRIPTION: When you short ship a sales order, it causes a backorder. If you have the parameter "Confirm backorders automatically" checked in Sales-Order Parameters (tdsls0100s400), the backorder is automatically confirmed at the time of confirming the shipment. When the backorder is confirmed, a new sales order line detail is added to the sales order line for the backorder amount. If you are using commissions, this will also link default commissions to the new order line detail and, if automatic commission calculation is set up in Commissions/Rebates Parameters (tdcms0100s000), the commission calculation will also be done in the background at this time. There was a problem with how the commission calculation was being executed that would cause the system to sometimes hang. This procedure has been modified to eliminate the problem, so the system will no longer hang. Solution: 161290 SITUATION IDENTIFIED IN: "Commission Agreements" (tdcms0130m000) SITUATION DESCRIPTION: If you are entering a new agreement, stop after entering the header information (before entering lines), go to view another record, and then change your mind and attempt to enter the agreement again, you get the error 'Agreement overlaps.' and are not allowed to continue. SOLUTION DESCRIPTION: The session has been modified to properly remove the header information when you stop entering an agreement before you enter any lines. If you choose to enter the same agreement later on, you will no longer get the error. Solution: 161292 SITUATION IDENTIFIED IN: "Copy Item Data" (tcibd0205m000) SITUATION DESCRIPTION: When copying general item data, which has incorrect item supplier information, linked to the purchase item data, the copy process completes, but does not copy the item supplier information and does not inform the user of the reason why. SOLUTION DESCRIPTION: Now during the copying of general item data which has incorrect item supplier information linked to the purchase item data, the copy process does not copy the item supplier information, aborts the copy process and informs the user of the reason why. Solution: 161295 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: When closing a production order with more than 300 operations, a fatal "Out of Dims" error occurs. SOLUTION DESCRIPTION: A production order with more than 300 operations can be closed without the fatal error. Solution: 161309 SITUATION IDENTIFIED IN: "Inbound Advice" (whinh2515m000) SITUATION DESCRIPTION: It is impossible to put away an inbound advice if the unit on the inbound advice is different from the unit in which the goods are received. The problem occurs in case the inventory unit of the item is not the smallest physical unit. Example: -Item "A" -Inventory unit = "box" -1 "box" = 10 "pcs". When 9 "box" are received it is possible to create a manual inbound advice for 90 "pcs". When trying to put away the advice the message whinhs0277 "Corrupt inventory detected in Whs xxx, Location xxx, Item xxx, Lot xxx, Inv. Date xxx" appears. SOLUTION DESCRIPTION: It is no longer possible to change the unit for an inbound advice if the receipt is done in inventory units. Hence the situation cannot occur anymore. Solution: 161311 SITUATION IDENTIFIED IN: "Print Company Parameters" (tfgld0404m000) SITUATION DESCRIPTION: Solution 106818 has introduced a new field to the company parameters table. The corresponding print/display sessions do not report this information. SOLUTION DESCRIPTION: - Changes have been made to the report and display sessions to now include the missing fields from the company parameters as well as the field descriptions. Solution: 161332 SITUATION IDENTIFIED IN: "Archive/ Purge Financial Transactions" (tfgld6205m000) SITUATION DESCRIPTION: When archiving transactions with text, the error 606 "reference does not exist on tfgld106" (on the current company) was given which prevents the process from finishing. SOLUTION DESCRIPTION: This error occurred because the wrong company was used for the text in the company where the session was being run. Changes have been made so that the correct company is now used and the error will no longer occur. Solution: 161337 SITUATION IDENTIFIED IN: "Print Tax Analysis (Invoice-to Business Partner)" (tfgld1431m000) SITUATION DESCRIPTION: When sales tax returns are filed based on a fiscal year, it is necessary to retrieve tax information based on the fiscal year/period. Fiscal and Tax periods are not always the same. For example, in the USA, tax periods are defined within Baan based on a Calendar year (January 1 through Dec 31), but the company's fiscal year may be different (April 1 through March 31). SOLUTION DESCRIPTION: The report can now be generated based on a tax year and period range or a fiscal year and period range. A business partner range has been added to the form, as well. Solution: 161340 SITUATION IDENTIFIED IN: "Test Function Server" (tuddc2530m000) SITUATION DESCRIPTION: When using a system that has DB2 as a database, DDC function servers do not work correctly. SOLUTION DESCRIPTION: The program has been modified to correctly handle the use of DDC function servers on systems that have DB2 for a database. Solution: 161348 SITUATION IDENTIFIED IN: "Material to Issue Production Orders" (ticst1501m000) SITUATION DESCRIPTION: The Specific menu command "Transfer Subseq. Delivery to Issue" moves any quantity in the subsequent delivery field of a material line to the issue field, whether or not backflushing is on for the line. This can result in double issue of materials (via manual issue and then backflushing) and the command should not make this adjustment for materials to be backflushed. SOLUTION DESCRIPTION: The menu command has been modified and no longer changes material lines that have the backflushing checkbox selected. In order to manually issue materials that are set for backflushing, double click on the material line and turn backflushing off. The quantity in subsequent delivery will automatically be moved to the 'to issue' field, and inventory can then be issued via "Initiate Inventory Issue". Solution: 161353 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: When closing a production order that makes use of more than 2000 cost components, a fatal error: "Index out of dims (2001)" occurs. SOLUTION DESCRIPTION: Production orders using more than 2000 cost components can now be closed without the fatal error. Solution: 161354 SITUATION IDENTIFIED IN: "Print Packing Slip" (whinh4475) SITUATION DESCRIPTION: The packing slip report prints lines for which the shipped quantity of normal item is zero. SOLUTION DESCRIPTION: The packing slip report now only prints the lines for which the shipped quantity of normal item is non-zero. For cost and service items, the printing of zero shipped lines is still applicable. Solution: 161371 SITUATION IDENTIFIED IN: "Expected Order Lines" (whinh3820m000) SITUATION DESCRIPTION: During search, it is not possible to zoom from Ship-from Business partner field. SOLUTION DESCRIPTION: During search, now it is possible to zoom from Ship-from Business partner field to the session "Business Partners" (tccom4500m000). Solution: 161372 SITUATION IDENTIFIED IN: "Print Costing History by Item Group" (ticst3401m000) SITUATION DESCRIPTION: Total fields on the report do not line up to label fields at the top of the page. SOLUTION DESCRIPTION: The report has been reformatted so that the labels are printed directly above the totals for easier reading. Solution: 161389 SITUATION IDENTIFIED IN: "Ledger History" (tfgld3501s000) SITUATION DESCRIPTION: If company currency system is dependent and Ledger History is printed for one specific company, the default currency was reference currency instead of local currency. SOLUTION DESCRIPTION: Now if Ledger History is to be shown for only one company the local home currency of that company will be selected by default. Solution: 161396 SITUATION IDENTIFIED IN: "Integration Transactions by Project/Order" (tfgld4510m000) SITUATION DESCRIPTION: In a multi logistic environment, ledger account for the default project cannot be found or a wrong ledger account could be selected. This problem happens because default projects are looked up in the finance company instead of the logistic company. SOLUTION DESCRIPTION: Now default project is searched in the logistic company. Solution: 161397 SITUATION IDENTIFIED IN: "Copy Project" (tipcs2210m000) SITUATION DESCRIPTION: When copying a project from within the session "Maintain Projects", the marked project is not displayed within session "Copy Project" and the field defaults are not restored on the form. SOLUTION DESCRIPTION: Now when copying a project from within the session "Maintain Projects", the marked project is displayed within session "Copy Project" and the field defaults are restored on the form. Solution: 161398 SITUATION IDENTIFIED IN: "Material to Issue Production Orders" (ticst1501m000) SITUATION DESCRIPTION: When the "Material to Issue for Production Orders" (ticst1501m000) session is opened to a closed order, it is possible to add a new material line to the order. SOLUTION DESCRIPTION: It is no longer possible to add material lines to a closed production order under any circumstance. Solution: 161409 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000 (B40c and above), tfcmgl200m000(B40b and below)) SITUATION DESCRIPTION: When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), Standing orders created in current year and reconciled in the next year, are reported in the reconciled year. When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC) for a reconciled standing order the currency information maybe invalid. This can cause the order amount to be incorrectly calculated, and not reported in 1099-MISC. SOLUTION DESCRIPTION: The session's tfcmg3204m000 and tfcmgl200m000 have been modified to correctly handle standing orders that have been created & reconciled in separate years. Further, the session now correctly calculates the amount using the correct currency code. Solution: 161410 SITUATION IDENTIFIED IN: "Rebuild Opening Balance/History from Transactions" (tfgld3203m000) SITUATION DESCRIPTION: The program rebuild opening balance/history from transactions takes a long time to complete. SOLUTION DESCRIPTION: Technical changes have been made to program script so that the session run more efficiently. Solution: 161411 SITUATION IDENTIFIED IN: "Create Transactions from Schedule" (tfgld1204s000) SITUATION DESCRIPTION: This solution addresses two issues. 1. When creating transactions with gross tax and multiple debit lines, the last debit line had an incorrect amount. This was due to the tax amount not being considered as part of the total transaction amount. The same problem existed for credit lines, as well. 2. The document status for the document created within the session would be "used" even when no transactions are created. SOLUTION DESCRIPTION: 1. The tax amount is now considered as part of the total transaction amount. 2. A check is introduced to make sure transactions will be created prior to creating the document. Solution: 161423 SITUATION IDENTIFIED IN: "Print Trial Balance" (tfgld3402m000) "Print Trial Balance- Currency" (tfgld3403m000) "Print Trial Balance Ledger Account/Dimensions" (tfgld3404m000) "Print Trial Balance- With Dimensions" (tfgld3405m000) "Print Trial Balance Dimension Code/Ledger Accounts" (tfgld3406m000) "Print Trial Balance Dimension Type/Dimension Code" (tfgld3408m000) SITUATION DESCRIPTION: Several problems have been identified and corrected in the various print trial balance sessions. tfgld3402m000 "Print Trial Balance" #1- The session did not print in the correct currency when running from a job. #2- It was possible that budget amounts were rounded by the incorrect rounding format. This could cause budget amounts to have too many or too few decimal places on the report. tfgld3403m000 "Print Trial Balance- Currency" The session did not perform properly if the following conditions are met: - Dependent multi-company system - Being run from a job for all companies in the group - Being run from a company where the local currency is not same as the reference currency The result was that either wrong amounts are printed on the trial balance (amounts in the local currency and not the reference currency) or error "index out of dims". tfgld3404m000 "Print Trial Balance Ledger Account/Dimensions" #1 The session did not print in the correct currency when running in a job. Report was always in the local currency. #2 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many or too few decimal places on the report. #3 Budget amounts were not calculated correctly when budgets were for a credit amount. #4 Amounts did not total up correctly when printing over all companies in the group. tfgld3405m000 "Print Trial Balance- With Dimensions" #1 The session did not print in the correct currency when running in a job. Report was always in the local currency. #2 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many or too few decimal places on the report. tfgld3406m000 "Print Trial Balance Dimension Code/Ledger Accounts" #1 The session did not print in the correct currency when running in a job. Report was always in the local currency. #2 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many or too few decimal places on the report. #3 Amounts did not total up correctly when printing over all companies in the group. tfgld3408m000 "Print Trial Balance Dimension Type/Dimension Code" #1 The session did not print in the correct currency when running in a job. Report was always in the local currency. #2 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many or too few decimal places on the report. SOLUTION DESCRIPTION: Changes have been made to the trial balance sessions so that the errors listed above will no longer occur. Solution: 161454 SITUATION IDENTIFIED IN: "Archive and Purge Integration Transactions" (tfgld4210m000) SITUATION DESCRIPTION: When attempting to run session tfgld4210m000 (Archive and Purge Integration Transactions) in a job, the session fails to execute. SOLUTION DESCRIPTION: The session was terminating abnormally, because several verification dialogs were being prompted for user input. These dialogs are still prompted when creating a job, however they no longer interfere when the session executes in a job. Solution: 161460 SITUATION IDENTIFIED IN: "Receipts" (whinh3520m000) SITUATION DESCRIPTION: For a return sales order of a lot controlled item, split the receipts into two. While confirming the second receipt, the system gives the error message "Lot %s: returned quantity may not exceed shipped quantity" (whinhs0358) even though the returned quantity is less than the shipped quantity. SOLUTION DESCRIPTION: Now, for return sales orders, when the returned quantity is less than the shipped quantity, the system doesn't give any error message. Solution: 161478 SITUATION IDENTIFIED IN: "Global Approval of Commissions/Rebates" (tdcms0250m000) SITUATION DESCRIPTION: When running on a system with Level 2 Informix database driver, the session does not find any records for approval, even though there are valid commissions/rebates to be approved. SOLUTION DESCRIPTION: A change was made to ensure that the session will properly find and approve commissions/rebates on all systems, regardless of the database driver being used. Solution: 161479 SITUATION IDENTIFIED IN: "Simulate Master Plan" (cprmp1202m000) SITUATION DESCRIPTION: When Simulating Master Plan for a large range of items the session aborts with Fatal Error "last.item.sost.rule index out of dims". SOLUTION DESCRIPTION: When Simulating Master Plan for a large range of items twice, without exiting the session, the session will now run successfully. The sourcing rules are read for every phase number that is being planned. Solution: 161538 SITUATION IDENTIFIED IN: "Post Integration Transactions to Finance Transactions" (tfgld4201m000) SITUATION DESCRIPTION: When posting integration transactions, some transactions would generate the error message "Ledger account not defined" and not be posted even if the ledger account is defined. This problem occurred when table boosters are being used. SOLUTION DESCRIPTION: An insufficient amount of memory was being allocated to store the mapping scheme when using table boosters. The amount of memory available for storing the mapping scheme has been increased to the maximum allowable value so that transactions can now be posted properly. Solution: 161550 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Order" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure for generic items for which generic item description data is set for the items, the newly created customized items have the Search Key I set to the Search Key I of the original generic item and not equalized to the new customized item description. This behavior causes search possibilities on the newly created customized items to be limited. SOLUTION DESCRIPTION: When generating a project structure for generic items for which generic item description data is set for the items, the newly created customized items have the Search Key I set to the new customized item description. Solution: 161558 SITUATION IDENTIFIED IN: "Simulate orders" (cprrp1210m000) SITUATION DESCRIPTION: When generating, inserting, or re-planning, an item with multiple levels of phantom items not linked to operations, the requirements for the lowest non-phantom item was not correct. SOLUTION DESCRIPTION: The requirement for the lowest level should be correct taking in all the BOM settings of each phantom level. Solution: 161561 SITUATION IDENTIFIED IN: "Process Commission/Rebate" (tdcms2201m000) SITUATION DESCRIPTION: When processing commissions/rebates, the current date is passed to finance instead of the invoice date. SOLUTION DESCRIPTION: The session has been modified so that the invoice date of the commission/rebate invoice will be sent to finance instead of the current date. Solution: 161569 SITUATION IDENTIFIED IN: "Copy Budget Period Allocations into Actuals" (tfcat4200m000) SITUATION DESCRIPTION: Error message "Dimension is blocked" did not provide enough information. SOLUTION DESCRIPTION: Now Dimension code is indicated in the error message. Solution: 161572 SITUATION IDENTIFIED IN: "tssoc2121s000" (Actual Material Costs) SITUATION DESCRIPTION: Modifying the "To Be Delivered" quantity is not allowed for a service order in the session "Actual Material Costs" (tssoc2121s000) even though there exists a corresponding "Open" outbound line in warehousing. The system issues the error message "The order is being processed within warehousing (outbound advice started)". SOLUTION DESCRIPTION: It now allowed to modify the "To Be Delivered" quantity for service order in the session "Actual Material Costs" (tssoc2121s000), provided that there exists a corresponding "Open" outbound line in warehousing. If the quantity is made zero, then the "Open" outbound line is deleted. Solution: 161573 SITUATION IDENTIFIED IN: "Import Actual Costs from GLD" (tfcat2210m000) SITUATION DESCRIPTION: When using session tfcat2210m000 (Import Actual Costs from GLD) if the default currency code in the FBS parameters has not been setup or contains a currency that is not a home currency - the session will generate a Fatal Error: tfgld205.fdah index 0 out of dims. SOLUTION DESCRIPTION: If a default currency has not been setup in FBS parameters with one of the company's home currencies, an appropriate error message is displayed and the session will exit. Follow the instructions in the error message before re-running this session. Solution: 161575 SITUATION IDENTIFIED IN: "Process Commissions/Rebates" (tdcms2201m000) SITUATION DESCRIPTION: There is no reference information in finance for rebate integration transactions. SOLUTION DESCRIPTION: When processing commissions/rebates, the reference field will now be filled in. It will show whether the transaction is a commission or a rebate and the relation for which it was paid. This will allow users to look up information in the CMS module, based on the financial integrations. Solution: 161589 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Orders" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure for a range of sales orders, and cost items are selected to be added to the project parts, only the last sales order in the selection range gets updated with the cost items. SOLUTION DESCRIPTION: Now when generating project structure for a range of sales orders, and cost items, are selected to be added to the project parts, all the sales order in the selection range gets updated with the cost items. Solution: 161592 SITUATION IDENTIFIED IN: "Generate Demand and Inventory plan" (cpdsp1210m000) SITUATION DESCRIPTION: When running session "Generate Demand and Inventory plan" (cpdsp1210m000), the user would choose specific range of periods but 1 extra period would get updated before the start of the range. SOLUTION DESCRIPTION: Only the range of periods given by the user in session "Generate Demand and Inventory plan" (cpdsp1210m000) will be updated. Solution: 161612 SITUATION IDENTIFIED IN: "Journal Vouchers (Summarized)" (tfgld1114s000) SITUATION DESCRIPTION: It is not possible to access the Baan Project Transaction session through the specific menu on the Journal Vouchers (Summarized) session. SOLUTION DESCRIPTION: The specific options for the session Journal Vouchers (Summarized) (tfgld1114s000) has been modified to include the same options as those contained in the Journal Voucher (tfgld1103s000). Solution: 161631 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: When using repeat expression with multicolumn reports, the layouts were not printed correctly. SOLUTION DESCRIPTION: Changed the way we handle repeat expressions. Solution: 161655 SITUATION IDENTIFIED IN: "File 1099-MISC" (tfcmg3204m000 SITUATION DESCRIPTION: 1.) When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC) using the filing option FORM + Electronic the session unnecessarily collects the payment information twice. 2.) In multi-finance environments, the user must select all the possible companies where a 1099 related invoice, standing order, or stand alone payment was created within the 'to' and 'from' company range. This company range must also include companies were the actual payment(s) were processed - possibly in another finance company. This prevents the session from running for an individual company(s) if invoices and payments were processed in different companies. 3.) The 1099-MISC sessions lacks functionality to collect Stand-alone payments that are 1099-MISC related. SOLUTION DESCRIPTION: 1.) The payment collection process has been consolidated such that - the payment information is only collected once - improving performance for the filing option Electronic + Form by 50%. 2.) The 1099 processing has been altered to allow the printing of a single company or a subset of companies, without having to include in the 'to' and 'from' company range the possible set of companies were the payment may have been processed. 3.) Added additional functionality to retrieve stand-alone payments that are 1099-MISC related. Several adjustments were also made to the two 1099-MISC detail reports to all the display of stand-alone payments. On the detail report under the invoice/standing order column - a stand-alone payment document id will be "(Stand Alone)" for each payment that occurred. Solution: 161673 SITUATION IDENTIFIED IN: "Finalization Process" (tfgld1212s000) SITUATION DESCRIPTION: In case of inter-company transactions the Vat records in table Tax Analysis (tfgld110) are created in the target company. SOLUTION DESCRIPTION: The Vat records will not be created in the Original Company. This will be consistent with the Vat Lines in the Finalized transactions table (tfgld106). Solution: 161676 SITUATION IDENTIFIED IN: "Report Operations Completed" (tisfc0130s000) SITUATION DESCRIPTION: When the SFC Parameter (Planning Tab) 'Calculation Method Remaining Prod. Time' is set to 'Planned Quantity', and an SFC operation is completed for which quantity completed exceeds quantity planned, the error message "Lead time for Planning is less than zero" is displayed and the operation can not be completed. SOLUTION DESCRIPTION: The session has been corrected so that production order operations where quantity completed exceeds quantity planned, under the circumstances mentioned in SITUATION DESCRIPTION, can now be completed without error. Solution: 161684 SITUATION IDENTIFIED IN: "Business Partners" (tccom4500m000) SITUATION DESCRIPTION: When changing the Search Key for a Business Partner, the system needs to update the Search Key in all the Roles by Business Partner tables. In the situation that the Business Partner table is shared between the companies and the Roles by Business Partner tables are not shared and there is no Roles by Business Partner record defined in the actual company, the system did not update possibly existing records in the other companies. SOLUTION DESCRIPTION: The system is now updating the Search Key for the Roles by Business Partner tables in all companies that share the Business Partner table. Solution: 161687 SITUATION IDENTIFIED IN: "Copy Item Data" (tcibd0205m000) SITUATION DESCRIPTION: When copying item data, and the sales pricing parameter 'default price book' and 'default service price book' are the same, an error 100 (duplicate value) is received on the price book data table. SOLUTION DESCRIPTION: Now when copying item data, and the sales pricing parameter 'default price book' and 'default service price book' are the same, the copy process is completed properly. Solution: 161701 SITUATION IDENTIFIED IN: "Integration Mapping Scheme" (tfgld4500m000) SITUATION DESCRIPTION: It was not possible to map to ledger accounts with integration indicator for transactions - WIP Via Finance - Revenue Via Finance SOLUTION DESCRIPTION: Adjustments have been made so that it is now possible to map integrations for WIP Via Finance & Revenue Via Finance. Solution: 161708 SITUATION IDENTIFIED IN: "Material Issue for Production Orders" (ticst0101s000) SITUATION DESCRIPTION: When the material is returned from shop floor, if the outbound order line is open/advised/released and even when the order quantity in outbound order line can be reduced, a new inbound order line is created. SOLUTION DESCRIPTION: When the material is returned from shop floor, if the outbound order line is open/advised/released, and if the order quantity in outbound order line can be reduced, new inbound order line is not created. Instead, outbound order line quantity is reduced. Solution: 161726 SITUATION IDENTIFIED IN: "Qualified Demand by Period" and "Calculate Demand Forecast by Item" (whinr1520m000 and whina2202m000) SITUATION DESCRIPTION: When material is issued to a rework production order, the issued quantity is recorded as "Actual Issue" as can be seen in the session "Qualified Demand by Period" (whinr1520m000). This data is later used in the session "Calculate Demand Forecast by Item" (whina2202m000). SOLUTION DESCRIPTION: Material issues to a rework production order are not registered as "Actual Issue" in session "Qualified Demand by Period" (whinr1520m000). Solution: 161729 SITUATION IDENTIFIED IN: "Close Periods" (tfgld1206m000) SITUATION DESCRIPTION: Get a BW error because a couple of messages in the script are missing an argument. The messages that have the problem are displayed when the P&L document is not in balance SOLUTION DESCRIPTION: The necessary changes made to the script. Messages will not cause a BW error anymore. Solution: 161740 SITUATION IDENTIFIED IN: "Print Trial Balance - Ledger Account/Dimensions" (tfgld3404m000) "Print Trial Balance - Dimensions" (tfgld3405m000) "Print Trial Balance - Dimensions/Ledger Account" (tfgld3406m000) SITUATION DESCRIPTION: If the user chose to generate the report without visiting the second form/tab the following errors occurred: 1. Run time error "Index out of Dims" was given and the session aborted. This occurred only for tfgld3404m000. 2. The report output did not print the currency in which the report was being printed. SOLUTION DESCRIPTION: The problem happened because of some initialization issues in the scripts. These have been corrected. Solution: 161748 SITUATION IDENTIFIED IN: "Generate Product Variant Structure for Project." (tipcs2220m000) SITUATION DESCRIPTION: When generating a product variant structure, with a lower level generic item set to be replaced by a standard anonymous item via the generic item data settings, the generation process continues down through the generic bom structure to the lower levels below the standard item, which is not necessary and only presents performance issues. SOLUTION DESCRIPTION: Now when generating a product variant structure, with a lower level generic item set to be replaced by a standard anonymous item via the generic item data settings, the generation process does not continue down through generic bom structure to the lower levels below the standard item. Solution: 161758 SITUATION IDENTIFIED IN: "Integration Mapping Scheme (General)" (tfgld4500m000) "Integration Transactions by Project/Order" (tfgld4510m000) "Integration Transactions by Document Line" (tfgld4512m000) "Integration Transactions Log" (tfgld4532m000) SITUATION DESCRIPTION: It is possible to set up a mapping scheme for the integration combination Purchase/Receipt(Invoiced). However, no integration transactions with this combination are ever created. SOLUTION DESCRIPTION: The integration combination Purchase/Receipt(Invoiced) is not used by the application. It has been removed from all the required sessions. Solution: 161765 SITUATION IDENTIFIED IN: "Remove Fully-Paid Sales Invoices" (tfacr2260m000) SITUATION DESCRIPTION: The session is working very slowly even when trying to delete a few invoices. SOLUTION DESCRIPTION: The master data is archived each time this session is run to make sure that there are no reference errors in the archive company. However, this process was being triggered more than once leading to excessive amount of time being taken. Now this will be done just once. Solution: 161766 SITUATION IDENTIFIED IN: "Hours Accounting Transactions" (tphrs1100s000) SITUATION DESCRIPTION: When entering hours for a project, no check was done if the date fell in the correct period when the project time zone was taken into account. SOLUTION DESCRIPTION: When entering hours for a project, a check is now always done if the date falls in the correct period when the project time zone is taken into account. Solution: 161767 SITUATION IDENTIFIED IN: "Spool Close" (ttstpsplclose) SITUATION DESCRIPTION: When printing to a direct printer which has been rejected at the Unix level, no error is given to inform the user that nothing printed. SOLUTION DESCRIPTION: An error is given, the device queue record is marked as in error and the report is not deleted. Solution: 161771 SITUATION IDENTIFIED IN: "Dimension Master" (tfgld0510m000) SITUATION DESCRIPTION: It is not possible to zoom and select the dimension type while searching or inserting a group. SOLUTION DESCRIPTION: A zoom option has been made available on the dimension type field. Solution: 161775 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: When there is a mixture of single column records and multicolumn records, the record count can get off and cause problems in placement of the layouts. SOLUTION DESCRIPTION: Added logic to keep track of when we switch from non-multicolumn to multicolumn so we can keep the record count correctly. Solution: 161776 SITUATION IDENTIFIED IN: "Spool Close" (ttstpsplclose) SITUATION DESCRIPTION: When printing to a direct printer which has been rejected at the Unix level, no error is given to inform the user that nothing printed. SOLUTION DESCRIPTION: An error is given, the device queue record is marked as in error and the report is not deleted. Solution: 161791 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: When closing production orders and calculating price variances, rounding between actual and estimated costs can differ resulting in incorrect price variance postings. SOLUTION DESCRIPTION: The rounding of costs in calculating price variances has been modified and the incorrect price variances are no longer posted. Solution: 161799 SITUATION IDENTIFIED IN: "Generate Product Variant Structure for Project" (tipcs2220m000) SITUATION DESCRIPTION: 1. When re-generating the project structure from the sales line and then selecting a component of the main top level item, this component item is placed back on the sales line overwriting the main top level item. This is incorrect. The main top level item should remain on the sales line. 2. When re-generating the project structure and the description is changed via generic item data settings, the search key 1 is not updated with the new description. 3. When generating the project structure, the search key 2 is not updated with the new customized item code. SOLUTION DESCRIPTION: 1. Now when re-generating the project structure from the sales line and then selecting a component of the main top level item, this main top level item remains on the sales line. 2. Now when re-generating the project structure and the description is changed via generic item data settings, the search key 1 is updated with the new description. 3. Now when generating the project structure, the search key 2 is updated with the new customized item code. Solution: 161803 SITUATION IDENTIFIED IN: "Integration Mapping" (tfgld4500m000) "Integration Mapping Scheme" (tfgld4101s000) "Options by Integration Element" (tfgld4121m000) "Integration Relations by Range" (tfgld4122s000, tfgld4124s000) "Integration Relations by Elements" tfgld4123s000, tfgld4125s000) SITUATION DESCRIPTION: When creating the integration mapping for Warehousing (Order) / Cycle Counting Adjustment, when doing a ZOOM in the field Reason, sub-session Reasons (tcmcs0105m000) is displayed instead of session whinh5110m000 (Reason Codes for Variance Changes). For the above integration mapping combination the only valid option for the reason code will be the one from the warehousing module, therefore the zoom should be made to Reason Codes for Variance Changes and not to session Reasons. SOLUTION DESCRIPTION: 1) In session Integration Mapping Scheme (tfgld4101s000) if the financial transaction is "Cycle Counting Adjustment" then the zoom session will be Reason Code Variance Changes (whinh5110m000) for all other financial transactions the zoom session will be "Reasons" (tcmcs0105m000). 2) In sessions Integration Relations by Range (tfgld4122s000, tfgld4124s000) and Integration Relations by Elements (tfgld4123s000, tfgld4125s000) a new menu will be displayed when the user zooms on the "Reason Code" field. The menu will provide the option to select session "Reasons" (tcmcs0105m000)" or session "Reason Code Variance Changes (whinh5110m000)". 3) In session Integration Mapping Scheme (tfgld4500m000) the same Integration Element cannot be used for Transaction Origin/Financial Transaction combinations Warehousing (Order)/Correction and Warehousing (Order)/Cycle Counting Adjustment, if any integration option for the integration element is "Reason" 4) In session Options by Integration Element (tfgld4121m000) the integration option cannot be set to Reason if the same Integration Element is used in the Mapping Scheme (tfgld4500m000) for Warehousing (Order)/Correction and Warehousing (Order)/Cycle Counting Adjustment. Solution: 161810 SITUATION IDENTIFIED IN: "Print Trial Balance - With Dimensions" (tfgld3405m000) SITUATION DESCRIPTION: Two problems were discovered when printing the report "Budget Variances (Dimension/Ledger Account)" (tfgld340514000). In some cases, ledger account/dimension combinations that contained no values are still printed on the report. SOLUTION DESCRIPTION: Changes have been made to the report logic so that records without amounts are no longer printed on the report. Solution: 161818 SITUATION IDENTIFIED IN: "Inbound Advice" (whinh2515m000) SITUATION DESCRIPTION: Create Inbound Advice for a production order using a storage unit other than the storage unit which was produced. The session will allow a converted quantity greater than the quantity produced to be advised. SOLUTION DESCRIPTION: The session will no longer advise for a quantity greater than produced. Solution: 161820 SITUATION IDENTIFIED IN: "Text dll" (ttstp_textdll) SITUATION DESCRIPTION: Using text.write() did not format the text to fit the window size properly. SOLUTION DESCRIPTION: Convert the text so that each line truncates to fit the window size. Solution: 161835 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: Multicolumn horizontal printing stopped working after installing solution 161153. SOLUTION DESCRIPTION: Implemented the code needed to get multicolumn horizontal printing again. Solution: 161839 SITUATION IDENTIFIED IN: "Simulate orders" (cprrp1210m000) SITUATION DESCRIPTION: When running Simulate orders (cprrp1210m000), a fatal float exception error happens. Fatal error: float exception in 'cprrp1210m000' Fatal error: Can not continu in cprrp1210m000 in DLL: ocpintirou06(cpinttirou06.get.opno.req.date)(bms.receive$] SOLUTION DESCRIPTION: Simulate orders (cprrp1210m000) will run and plan correctly. Solution: 161871 SITUATION IDENTIFIED IN: "Print Integration Transactions Log" (tfgld4432m000) SITUATION DESCRIPTION: When running the session with the default "log time to" (24:00:00), the report would print correctly. However, if the user tried to print the report a second time without reentering this "log time to" the error message 'No data within selection' was given. SOLUTION DESCRIPTION: The problem occurred because of an incorrect conversion done on the time value after printing the report. This has been corrected and it is now possible to run the report multiple times without reentering the time for each run. Solution: 161883 SITUATION IDENTIFIED IN: "Print Finalized Transactions By Date" (tfgld1440m000) "Print Journal" (tfgld1441m000) SITUATION DESCRIPTION: When printing over all companies, transactions that are in batches that were created in other companies did not display on the report. SOLUTION DESCRIPTION: Changes have been made so that transactions from all the companies entered on the form are now reported. Solution: 161886 SITUATION IDENTIFIED IN: "Print Inbound Advice" (whinh3460m000) SITUATION DESCRIPTION: Currently when the session "Print Inbound Advice" (whinh3460m000) is run, all the advice lines (advice lines that are already put away and advice lines that are yet to be put away) are printed. If the user wants only one of those advice lines to be printed, it is not possible. SOLUTION DESCRIPTION: The functionality of the session "Print Inbound Advice" (whinh3460m000) is enhanced such that the user can choose to print - Only the advice lines that are already put away [View Advice Put Away = Yes and View Advice To be Put Away = No] - Only the advice lines that are yet to be put away [View Advice Put Away = No and View Advice To be Put Away = Yes] - All the advice lines [View Advice Put Away = Yes and View Advice To be Put Away = Yes] If both the options View Advice Put Away = No and View Advice To be Put Away = No, then the system would give the error message "Option not allowed". The existing customers, who do not want to use this enhancement, can ignore those options. By default both the options are set to yes and hence all the advice lines are printed, which is equivalent to the previous functionality. Additionally, the help text of the field Location is adjusted to indicate that it is the source location from which the goods are moved. Solution: 161908 SITUATION IDENTIFIED IN: "Maintain Projects" (tipcs2501m000) SITUATION DESCRIPTION: When deleting a project just after creating it with the copy project function, a series of error messages are displayed indicating that the project cannot be deleted. SOLUTION DESCRIPTION: Now when deleting a project just after creating it with the copy project function, the newly created project is properly deleted. Solution: 161929 SITUATION IDENTIFIED IN: "Conversion to File Word Processor" (ttstpconv) SITUATION DESCRIPTION: Three problems addressed with Postscript: 1) When printing A4L, the text was not positioned well depending on how many lines the device was set for. 2) Excess show pages cause an extra blank page to print when using an actual postscript device. 3) A5 was not numbering its pages correctly. SOLUTION DESCRIPTION: 1) A4L now always positions the top of the page at the same point. If more lines are set on the device than the page can actually print, the extra lines will be lost. 50 lines appear to give the best results, much more than 50 and you start losing lines. 2) Removed explicit show pages for most formats since 'p' or 'p2' usually includes a show page instruction. 3) Changed how A5 '%%Page' instructions were numbered so that it processes correctly now. Solution: 161930 SITUATION IDENTIFIED IN: "Integration Mapping Scheme (Manufacturing/Order Management)" (tfgld4101s000) SITUATION DESCRIPTION: When trying to set-up an integration mapping scheme for transaction origin Manufacturing/Order Management, with the combination 'Financial Business Partner Group(ACP)/Item Group/Reason Code', the error message " Invalid combination of selected field for Key Definition " was given. Similar combinations are allowed ('Financial Business Partner Group(ACP)/Reason Code' or 'Item Group/Reason Code') but it is not possible to map using all three of these key elements. SOLUTION DESCRIPTION: Functionality has been changed to allow mapping the combination "Financial Business Partner Group(ACP)/Item Group/Reason Code" as well as the related combination "Financial Business Partner Group(ACP)/Item/Reason Code" The help text for integrations has been changed to show the new combinations and some changes have been made to the posting process to make sure the new combinations are used when posting integration transactions. Solution: 161932 SITUATION IDENTIFIED IN: "Print Financial Integration Transactions" (tfgld4418m000) SITUATION DESCRIPTION: When zooming to the Document History sub-session (tfgld1504m000) from the "Document Number" field, documents which do not correspond to the "Transaction Type" field of the main session are displayed. SOLUTION DESCRIPTION: This was due to the transaction type not being passed to the sub-session. The transaction type is now passed to the sub-session so that the relevant documents are shown. Solution: 161937 SITUATION IDENTIFIED IN: "Conversion to File Word Processor" (ttstpconv) SITUATION DESCRIPTION: When printing Russian or eastern European characters to ASCII or RTF file, the characters are not converted properly SOLUTION DESCRIPTION: When doing these conversion, we now change the character set from ISO88595 to CP1251 and ISO88592 to CP1250. Solution: 161954 SITUATION IDENTIFIED IN: "Generate Outbound Advice" and "Outbound Order Lines " (whinh4201m000 and whinh2520m000 ) SITUATION DESCRIPTION: This situation applies when "Issue Components" is selected on the sales order lines. When generating outbound advice for a list or phantom item or for the components of the main line item on a sales order, which has insufficient inventory for its components, the system correctly generates outbound advice with a shortage the first time. Subsequently, when more inventory, is available for the components but not enough to cover the entire ordered quantity, the system does not generate additional advice. SOLUTION DESCRIPTION: The system now generates additional outbound advises correctly, based on the additional inventory available for the components. Solution: 161958 SITUATION IDENTIFIED IN: "Confirm Shipments / Loads" (whinh4275m000) SITUATION DESCRIPTION: While confirming the shipment lines, the value of COGS (Cost of Goods Sold) in sales order lines depends on the behavior of the database i.e. based on the sequence in which shipment positions are returned by the database. SOLUTION DESCRIPTION: Now, while confirming the shipment lines, the value of COGS (Cost of Goods Sold) in sales order lines are consistent by forcing the database to return shipment positions in the required order. Solution: 161965 SITUATION IDENTIFIED IN: "Intercompany Relations" (tfgld0115s000) SITUATION DESCRIPTION: Due to a security change in tools standard, the record insert capability of a session is disabled if the session isn't specifically setup with that function. Several sessions, namely (tfgld0105s000, tfgld0111s000, and tfgld01115s000) Periods, Transactions Types, and Inter company Relations did not have this function enabled, which prevented the insertion of new records. SOLUTION DESCRIPTION: The sessions (tfgld0105s000, tfgld0111s000, and tfgld01115s000) have been modified so insertion of new records is now enabled. Solution: 161967 SITUATION IDENTIFIED IN: "Close periods" (tfgld1206m000) SITUATION DESCRIPTION: 1. Some amounts in the "History" tables (tfgld201, tfgld202 and tfgld205) and the "Opening balances" tables (tfgld203, tfgld204 and tfgld206) have more digits after the decimal point than amounts in the "Transactions" tables (tfgld102 and tfgld106) although amounts in the "History" tables and in the "Opening balances" tables are the sum of amounts from the "Transactions" tables. 2. The last fiscal period cannot be finally closed for GLD module because difference between total credit and total debit is too big. But all amounts in the "History" tables are correct. SOLUTION DESCRIPTION: Some amounts are stored in the database with more numbers after the decimal point than allowed (For instance, 0,4399999999). But in BAAN these amounts appear as numbers that are rounded according to the rounding factor (In our example, 0,44). If we sum a great number (more than 40000) of these amounts then the result will have more decimals than it should. That is why "History" tables and the "Opening balances" tables contain amounts that have more decimals than allowed by the rounding factor. 1. Sessions that update the "History" tables and the "Opening balances" tables have been changed to round amounts before saving. Refer to the components list to see the all changed sessions. 2. Total debit and total credit are rounded before comparing. Solution: 161970 SITUATION IDENTIFIED IN: "General Item Data" (tcibd0101s000) SITUATION DESCRIPTION: The item revision is not shown correctly when selecting different items with different revisions. SOLUTION DESCRIPTION: Now the item revision is not shown correctly when selecting different items with different revisions. Solution: 161988 SITUATION IDENTIFIED IN: "Tax Provider Functions Library" (tccomdll0020) SITUATION DESCRIPTION: If an error occurs while calculating tax in a third-party tax provider, the description of the problem in the Tax Calculation Error Report is left blank. SOLUTION DESCRIPTION: This was due to the error message for third-party tax not being reset correctly. This error message is now properly reset, so that the description of the error is now given in the report. Solution: 161989 SITUATION IDENTIFIED IN: "Product Configurator" (tipcf5120m000) SITUATION DESCRIPTION: 1. When configuring a product variant, the before input constraints are executed too many times during the process. This results in a performance issue when large before input constraints exist. 2. When navigating to the next option set, the cursor is positioned incorrectly. SOLUTION DESCRIPTION: 1. The number of times for executing before input constraints during the product configuration process has been reduced. This results in a performance improvement when large before input constraints exist. 2. Now when navigating to the next option set, the cursor is positioned correctly. Solution: 161991 SITUATION IDENTIFIED IN: "Print TAX Analysis" (tfgld1420m000) SITUATION DESCRIPTION: When using the session tfgld1420m000 (Print Tax Analysis) with the Final Print option, contra tax lines for shifted tax are not being updated as printed. This prevents the archive session tfgld6207m000 from archiving these records. SOLUTION DESCRIPTION: The session has been modified to properly update contra tax lines for shifted tax when processing a 'Final Print'. An additional change was made to the report layout to ensure that the contra tax lines for shifted tax are displayed correctly on the report when using the option print contra for shift taxes. Solution: 161995 SITUATION IDENTIFIED IN: "Transfer Maintenance Planning to Service Orders" (tsspc2220m000) SITUATION DESCRIPTION: Two situations exist: 1) Sales representative for a service order is not being correctly derived when the service order is created from a transferred call, contract, planned maintenance activity, service order quotation, etc. 2) When manually entering a service order quotation, service order, service contract quotation, service contract, etc., the sales representative on the service center is not being considered when deriving the default sales representative. SOLUTION DESCRIPTION: Both situations have been resolved with the derivation structure for sales representative being defined as: 1) The sales representative on "User's Defaults" (tsmdm1150s000 via tsmdm1550m000) is used. 2) If not found, the sales representative on "Service Centers" (tsmdm1100s000 via tsmdm1500m000) is used. 3) If not found, and a contract is applicable, the sales representative on "Contracts" (tsctm3100s000 via tsctm3500m000) is used. 4) If not found, the external sales representative on "Sold-to Business Partners" (tccom4110s000 via tccom4100s000 via tccom4500m000) is used. 5) If not found, the internal sales representative on "Sold-to Business Partners" (tccom4110s000 via tccom4100s000 via tccom4500m000) is used. NOTE: For field change orders and service order quotations the sales representative on the service contract is not being considered. This is because a quotation, for example, is an agreement with the customer that is independent from the contract and therefore contract information is not applicable. This holds true for field change orders as well. Solution: 162004 SITUATION IDENTIFIED IN: "Picking List" (whinh2525m100) SITUATION DESCRIPTION: When confirming the shipments, with negative inventory allowed, the message "Cannot determine the cost of goods sold" (whinas0062) is issued and the shipments are not confirmed. SOLUTION DESCRIPTION: The shipments can now be confirmed successfully. It is now not allowed to confirm shipment lines of stock points which are blocked for inspection. Solution: 162008 SITUATION IDENTIFIED IN: "Copy Project" (tipcs2210m000) "Projects" (tipcf2101m000) SITUATION DESCRIPTION: When copying a project, the flag 'Investment Project' on the project details is not copied. SOLUTION DESCRIPTION: Now when copying a project, the flag 'Investment Project' on the project details is copied. Solution: 162009 SITUATION IDENTIFIED IN: "Version Scan Tool" (ttaad0500m000) SITUATION DESCRIPTION: Solution 161028 delivered the wrong object. SOLUTION DESCRIPTION: The correct object is now being delivered. Solution: 162028 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: When using layout conditions in such a way that no layout is printed for a given record in multicolumn printing, the resulting report can be rather unbalanced. SOLUTION DESCRIPTION: Added some code to keep track of the number of records that do not get any layouts printed so that we can better layout the data correctly on the page. Solution: 162109 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Orders" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure for sales order for a generic item, and there is item data text generated as part of this process, then the generated text does not appear on the sales acknowledgement, packing list or the sales invoice. SOLUTION DESCRIPTION: Now when generating project structure for sales order for a generic item, and there is item data text generated as part of this process, then the generated text does appear on the sales acknowledgement, packing list or the sales invoice. Solution: 162118 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Order" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure for a non-generic phantom item from a sales order, with the option 'create order lines for phantom' set to YES, and the main item has another phantom item as a component, then the error 'no valid components present' is received for the customized component. SOLUTION DESCRIPTION: Now when generating project structure for a non-generic phantom item from a sales order, with the option 'create order lines for phantom' set to YES, and the main item has another phantom item as a component, then the customized component is added to the sales order with the issue status set to 'issue main'. Solution: 162133 SITUATION IDENTIFIED IN: "Remove Closed Warehousing Orders" (whinh2250m000) SITUATION DESCRIPTION: The session is run for a particular range with the option Error Report = No. Without closing the window, the session is run for another range with the option Error Report = Yes. In the error report, the error logs corresponding to first range is printed. SOLUTION DESCRIPTION: Now, even when the session is run repeatedly without closing the window, the error logs are printed correctly. Solution: 162137 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Orders" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure, the production item data flag 'Use Phantom Inv.' is not set in the new customized BOM. SOLUTION DESCRIPTION: When generating project structure, the production item data flag 'Use Phantom Inv.' is set in the new customized BOM. Solution: 162144 SITUATION IDENTIFIED IN: "Generate Subcontracting Purchase Orders" (tisfc2250m000) SITUATION DESCRIPTION: When generating a purchase subcontracting order, the error message "Dimension for ledger account must be filled" was given. The problem is that when determining dimensions the "product line" and "production line" were not filled correctly and thus dimensions mapped on either of these two fields could not be found. SOLUTION DESCRIPTION: Changes have been made so that when generating a subcontracting order it is now possible to find dimensions mapped on "product line" and "production line". Solution: 162156 SITUATION IDENTIFIED IN: "Integration Transactions by Order/Project" (tfgld4510m000) SITUATION DESCRIPTION: The credit portion of the transaction for material issue of a standard item for a customized end item was incorrectly posted with the project ID filled. Only the debit side should reflect the project ID. This error has already been solved, but for records created prior to the solution 117006 a correction program is needed to remove the project ID from the credit entry. SOLUTION DESCRIPTION: Two correction programs tfcor0008 - Correct Project in tfgl418 (version 5c) and tfcor0011 (version 5b) are now available to correct the credit entry. Solution: 162165 SITUATION IDENTIFIED IN: "General Item Data" (tcibd0101m000) SITUATION DESCRIPTION: After inserting a new item and then changing the inventory unit in the session "General Item Data" (tcibd0101m000), the warning message "No conversion factor found between inventory unit and sales unit" (tcibds0150) is received. This is incorrect, as no inventory is present and no orders are placed against this new item. The functionality should ask the question to change the other units in sales, purchasing and service. SOLUTION DESCRIPTION: Now after inserting a new item and changing the inventory unit in the session "General Item Data" (tcibd0101m000), a question is asked to "Change other units with same value?" (tcibd0101b). When answering yes to the question, the units in sales, purchasing and service are updated to the new inventory unit. Solution: 162177 SITUATION IDENTIFIED IN: "Chart of Accounts" (tfgld0508m000) SITUATION DESCRIPTION: It should not be possible to remove a ledger account using the "Chart of Accounts" (tfgld0508m000) session if an account number has finalized transactions. This issue is only applicable in a multi-finance environment, since the deletion process was not checking all possible companies for transactions. SOLUTION DESCRIPTION: When removing an account, the session now checks all companies for finalized transactions before permitting a deletion. Solution: 162184 SITUATION IDENTIFIED IN: "Print Production Order Planning" (tisfc1401m000) SITUATION DESCRIPTION: The 'Select Report' menu was displayed twice, but only the second time the choice of the report was used. This happened when another report was added to an existing report group in a customization. SOLUTION DESCRIPTION: The 'Select Report' menu is now only displayed once and the chosen option is used. Solution: 162194 SITUATION IDENTIFIED IN: "Import Journal Voucher Batches by ID Number" (tfgld2215m000) SITUATION DESCRIPTION: Two users cannot use this session one after another until the first user exits the session. This is because the second user is given the message "Journal Voucher Batches are being imported by other user". It should be possible for the second user to import journals as soon as the first user has finished processing even if the first user forgets to exit the session. SOLUTION DESCRIPTION: This session, should not be run by more than one user at a time. To prevent this, the session puts a lock on itself as soon as importing begins. This lock was being removed too late i.e. only when the user exited the session. Now the lock will be removed as soon as the importing ends allowing a second user to start using the session even if the first user has forgotten to exit the session. Solution: 162247 SITUATION IDENTIFIED IN: "Maintain Journal Vouchers (Multiple Lines)" (tfgld1115m000) SITUATION DESCRIPTION: When using "Maintain Journal Vouchers (Multiple Lines)" (tfgld1115m000), the ledger account and dimension descriptions are not included on the display. SOLUTION DESCRIPTION: The ledger account and dimension description have been added to the session. Solution: 162252 SITUATION IDENTIFIED IN: "Close Year - Provisional" (tfgld6201m000) SITUATION DESCRIPTION: 1. Opening balances in the "Customer/Supplier History" (tables tfacr500 and tfacp500) have been updated based on the batch year instead of the fiscal year. 2. Creation of the opening balances in the "Customer/Supplier History" (tables tfacr500 and tfacp500) has performance problems. 3. LOCALIZATION ONLY: Opening balances in the "Customer/Supplier History" (tables tfacr500 and tfacp500) have not been created for the non-trade control accounts. SOLUTION DESCRIPTION: 1. The fiscal year is used when updating the "Customer/Supplier History" (tables tfacr500 and tfacp500). 2. The database requests have been optimized. 3. LOCALIZATION ONLY: The opening balances are created for the non-trade control accounts as well. Solution: 162276 SITUATION IDENTIFIED IN: "Reprint Journal Report" (tfgld1410m000) SITUATION DESCRIPTION: Intergroup transactions generated in the target company could not be printed by the "reprint journal report" session. SOLUTION DESCRIPTION: Changes have been made so that the intergroup transactions generated in the target company will now be reported when running the "reprint journal report" session in the target company. Solution: 162294 SITUATION IDENTIFIED IN: "Invoice Reserved Commissions/Rebates" (tdcms2403m000) SITUATION DESCRIPTION: When trying to reprint reserved commissions/rebates, the user receives a "Use of NULL pointer" fatal error. SOLUTION DESCRIPTION: The report script has been changed so that the fatal error will no longer occur. The session will now correctly reprint reserved commissions/rebates. Solution: 162299 SITUATION IDENTIFIED IN: "Print Financial Transactions" (tcfin1400m000) SITUATION DESCRIPTION: When using a multi-company setup and printing the financial transactions of a logistic company, the exchange rate types of the company were not correctly read. This resulted that the amounts on the report were not converted to the report currency. SOLUTION DESCRIPTION: The exchange rate types are now correctly read for the actual company. The defined 'Exchange Rate Types' (tcmcs040) and the 'Currency Rates' (tcmcs008) need to be shared between all linked companies and the exchange rate types need to be the same for all the linked company. Solution: 162303 SITUATION IDENTIFIED IN: "Inventory Handling Parameters" (whinh0100s000) SITUATION DESCRIPTION: The help text for the parameter 'Correct SFC Production Order till' (whinh000.crpr) does not clearly state the intended functionality. SOLUTION DESCRIPTION: The help text of the parameter 'Correct SFC Production Order till' (whinh000.crpr) is re-written to clearly state the intended functionality. Solution: 162307 SITUATION IDENTIFIED IN: "API Functions Library" (tcapidll0001) SITUATION DESCRIPTION: When trying to access a third-party tax software, the error message "API message not received. Error or Data message expected, Error code 11" is given when it should not be. SOLUTION DESCRIPTION: This was being caused by an incorrect check in an application library, which has been corrected. Solution: 162320 SITUATION IDENTIFIED IN: "Initiate Inventory Issue" (tisfc0207m000) SITUATION DESCRIPTION: When initiating inventory for a production order, if the 'Issue Date' is backdated and the component item is new and doesn't have a cost price for the date the user backdates to, the system still unblocks the outbound order line. This outbound line cannot be released because there is no cost price for the date it's trying to issue. System issues the error message "Effective Cost Component Structure for Item %s not found on Date %s and Time %s" (tcibds1204). SOLUTION DESCRIPTION: When initiating inventory for a production order, the system now ensures that cost price is present for the component as of the 'Issue Date'. If the cost price is not present, the outbound is left blocked and the system issues the message "Cost price structure not present for this date" (whinhs0510). Solution: 162328 SITUATION IDENTIFIED IN: "Post Integration Transactions To Finance Transactions" (tfgld4201m000) SITUATION DESCRIPTION: In the session "Default Project Data By Number Group" (tipcs0503m000), it is possible to set up a default project to be used in integration mapping for a series of actual projects. When assigning ledger accounts to integration transactions and using default projects for mapping, it was possible that ledger accounts were assigned based on a mapping scheme of lower priority even though a valid mapping of higher priority existed. For example: A ledger account would be picked up based on a match with item group before a match with project/item group if the mapping was based on default project. SOLUTION DESCRIPTION: The functionality of assigning ledger accounts for integration transactions has been changed. This will only change when using default projects. The priority list will now check the highest priority combination for actual project and then for default project before checking the next highest priority. Previously, all combinations were checked for actual project before any combinations were checked based on default project. Solution: 162346 SITUATION IDENTIFIED IN: "Estimated Tool Requirements" (titrp0511m000) SITUATION DESCRIPTION: When planning tool numbers with the parameter 'Maximum Tools to be Planned' set to 1, a fatal error 'Index 2 out of dims[1] 1' occurred. SOLUTION DESCRIPTION: When planning tool numbers with the parameter 'Maximum Tools to be Planned' set to 1, the fatal error is now not occurring anymore. Solution: 162347 SITUATION IDENTIFIED IN: "Copy Master Plan between Scenarios" (cprmp2203m000) SITUATION DESCRIPTION: When copying a scenario with large periods to a scenario with much smaller periods, a fatal error "Index out of Dims" would crash the program. SOLUTION DESCRIPTION: When running "Copy Master Plan between Scenarios" (cprmp2203m000), the session will copy the correct quantities with no run time errors. Solution: 162348 SITUATION IDENTIFIED IN: "Shipment Lines" (whinh4131s000) SITUATION DESCRIPTION: When confirming shipments using the session "Shipment Lines" (whinh4131s000), the outbound order line status is not changed from "Staged" to "Shipped". This happens only when using package definitions. SOLUTION DESCRIPTION: The outbound line status is now correctly updated from 'Staged' to 'Shipped' when confirming a shipment line in the session "Shipment Lines" (whinh4131s000) when packaged definitions are involved. Solution: 162349 SITUATION IDENTIFIED IN: "Clear Corrupted Inventory" (whcor0200m000) SITUATION DESCRIPTION: Due to inventory corruption there is need for a generic correction program to rebuild the inventory. SOLUTION DESCRIPTION: This correction program will correct inventory and the receipt/consumption tables: When checking the check box 'Rebuild Inventory Transactions by Item Warehouse' on the first form the table whinr110 (Inventory transactions by Item/Warehouse) is checked. Also, the inventory on hand on item/warehouse level (whwmd215.stoc), will be balanced with the inventory transactions by Item/Warehouse (whinr110) when this check box is set. The following tables will be corrected when checking the check box 'Rebuild Receipt/Consumption transactions' on the first form: - whinr112 (Inventory receipt transactions) - whinr114 (Inventory receipt transaction consumptions) Correcting Inventory: To be able to correct the corrupted inventory additional checks/updates are done like: - detecting/inserting missing shipment lines - detecting/correcting outbound line status. The inventory can be checked/corrected by item and location type as defined on the 2nd form. The inventory values that are corrected by this session in order of detail are: Inventory on item level: - Inventory on hand (tcibd100.stoc) - Inventory on hold (tcibd100.bloc) Inventory on item/warehouse level: - Blocked inventory (whwmd215.blck) - Location Allocated inventory (whwmd215.alpl) * Note that the inventory on hand on item/warehouse level (whwmd215.stks) is normally not updated by this program. Inventory on item/warehouse/lot level: - Inventory allocated (whltc105.stka) - Inventory on hold (whltc105.stkh) * Note that the inventory on hand on item/warehouse/lot level (whltc105.stks) is normally not updated by this program. Stock point level: - Inventory on hand (whinr140.stks) - Inventory on hold (whinr140.stkh) - Inventory on order (whinr140.stko) - Allocated inventory (whinr140.stka) Inventory structure level - Inventory on hand in inventory unit (whinr150.stks) - Inventory on hand in storage unit (whinr150.strs) - Inventory blocked in storage unit (whinr150.strb) - Inventory allocated in inventory unit (whinr150.stka) - Inventory allocated in storage unit (whinr150.stkr) Form description: On the 2nd form the following options are available: - Rebuild Locations of type 'Receipt' - Rebuild Locations of type 'Inspection' - Rebuild Locations of type 'Pick/Bulk' or empty Locations - Rebuild Location of type 'Staging' Selecting one or more of these options will make the program correct the inventory on stock point (whinr140) and inventory structure (whinr150) level on the selected location type. - balance inventory When this option is selected the inventory by item (tcibd100), inventory by item/warehouse (whwmd215) and inventory by item/ warehouse and lot (whltc105) is corrected. A part of this correction is based on the inventory figures on stock point level. Therefore always first the inventory should be rebuild by location before 'balance inventory' is set. The inventory on hand figures in the several inventory tables are balanced based on the inventory on item/warehouse level. This means when selecting this option it is possible that the inventory on hand on stock point level is changed. There are two possibilities: 1) Inventory on hand on item/warehouse level > inventory on hand on stock point level. The program will increase the inventory on hand on stock point level and inventory structure level. In case of a location controlled warehouse/item combination the created inventory is put on the 'correction' location as defined on the session form. In case of none location controlled item/warehouse combination the created inventory is put on the empty location. 2) Inventory on hand on item/warehouse level < Inventory on hand on stock point level. The program will decrease the inventory on hand on stock point level and inventory structure level. This is done based on the outbound priority after the program first tried to decrease the inventory on the 'correction' location. - correction location Not actual location. If the filled in location does not exist yet the program will automatically create it. When the program did create this location it will be blocked for all transactions. This location is used by the program in case the inventory on stock point level and inventory structure level needs to be decreased in order to get the inventory tables balanced (see balance inventory) - Allow automatic processing of Adjustment Orders There are instances where the correction program is unable to decrease the inventory at location level (whinr140/whinr150) or at lot level to balance the inventory with the inventory on hand registered at item/warehouse level (whwmd215.stoc). In that case message code 0001 ("Stock Points in Warehouse ### can not be decreased by ###") or message code 0002 ("Stock Points for lot ### in Warehouse ### can not be decreased by ###") is printed. This situation can be corrected by processing an adjustment order to get additional inventory available. When setting the option 'Allow automatic processing of Adjustment Orders' this adjustment orders is created and processed automatically and the correction program will continue with correcting the situation. On the third form the following options are available: - Insert missing Shipment Lines This option will detect/create missing shipment lines. This option will be automatically set when the options 'Rebuild Locations of type 'Pick/Bulk' or empty Locations' or 'Rebuild Location of type 'Staging' is set. This because the inventory on the pick/bulk/staging or empty locations are partially rebuild based on the shipment lines. - Check Outbound Line Data This option will perform checks on the outbound line quantities and check/correct the outbound line status. Also this option is automatically set when the options 'Rebuild Locations of type 'Pick/Bulk' or empty Locations' /'Rebuild Location of type 'Staging' or 'Insert Missing Shipment Lines' is set. - Maximum execution time and unit. In this field the maximum time the program is allowed to run can be filled in. After correcting the inventory of each item the program will check whether the maximum execution time has been exceeded. If so the program will quit and the report will be printed. On the report also a message is printed that the program has been quit due exceeding of the maximum execution time. Solution: 162369 SITUATION IDENTIFIED IN: "Write to Message Queue (Interactive)" (tuddc1218m000) SITUATION DESCRIPTION: When starting the session (in B50_b), an error was generated about an invalid domain value. Also (in all versions), the message queue was not being closed. SOLUTION DESCRIPTION: Changed the initial value so that it matches the field's domain. Also, added choice sections so that the message queue is closed when the session ends. Solution: 162375 SITUATION IDENTIFIED IN: "Reprint Journal Report " (tfgld1410m000) SITUATION DESCRIPTION: When reprinting the journal report, intercompany documents unrelated to the current company/run were included on the report. SOLUTION DESCRIPTION: Changes have been made to the session so that intercompany documents not related to the current company/run number are not longer printed. Solution: 162383 SITUATION IDENTIFIED IN: "Transfer Planned Orders" (cppat1210m000) SITUATION DESCRIPTION: When transferring planned purchase orders for the same supplier but different buyers, the buyer on some of the purchase order headers were incorrect. SOLUTION DESCRIPTION: When transferring planned purchase orders for the same supplier but different buyers, the buyer is correctly populated on to the purchase order header. Solution: 162384 SITUATION IDENTIFIED IN: "Item Costing Data" (tcibd0507m000) SITUATION DESCRIPTION: It is currently possible to delete the item costing data when there is an existing inventory or orders against the item. SOLUTION DESCRIPTION: Now, item costing data cannot be deleted when there is existing inventory or orders against the item. Solution: 162395 SITUATION IDENTIFIED IN: "Generate Project Structure for Sales Orders" (tdsls4244m000) SITUATION DESCRIPTION: When generating project structure for sales order, for the newly generated item, the main item text is copied to the sales item text. However, the text number of both the main item and the sales item are the same, thus preventing the sales item text to be edited separately from the main item text. SOLUTION DESCRIPTION: Now when generating project structure for sales order, for the newly generated item, the main item text is copied to the sales item text with a separate and different text number, thus allowing the sales item text to edited separately. Solution: 162402 SITUATION IDENTIFIED IN: "Company Parameters" (tfgld0103s000) SITUATION DESCRIPTION: When entering the company parameters and zooming on the ledger accounts, the accounts displayed for selection were not correct. - For both the currency difference profit and loss accounts, only accounts of type "profit & loss" were displayed even though the session accepts both "profit & loss" and "balance sheet" accounts. - For the currency difference profit account, only accounts with the dual accounting indicator = "Statutory", currency translation method = "BOTH", and currency analysis = "Not required" are allowed. The zoom on currency difference profit account did not filter the ledger accounts displayed accordingly. - For several other accounts defined in the parameters, only accounts with the currency translation method = "Both" are allowed. The zoom would show accounts with currency translation methods other than "Both". - There are two different currency translation accounts in the parameters one for "statutory" and one for "complementary". The zooms for both of these accounts would show both statutory and complementary accounts. SOLUTION DESCRIPTION: - When zooming to select currency difference accounts, "balance sheet" accounts will now be displayed along with "profit & loss" accounts. - For the currency difference profit account, only ledger accounts that have dual accounting indicator = "Statutory", currency translation method = "BOTH", and currency analysis = "Not required" will be displayed. - For parameters that only accept ledger accounts with currency translation method = "BOTH" zooming will now only display accounts that are defined as "BOTH". - When zooming to select currency translation accounts, only "Statutory" or "complementary" accounts will be displayed based on the currency translation account that is being selected. Solution: 162441 SITUATION IDENTIFIED IN: "Conversion Factors" (tcibd0103m000) SITUATION DESCRIPTION: Conversion factors that are still in use by item data, can be modified or deleted. SOLUTION DESCRIPTION: Conversion factors that are still in use by item data can no longer be modified or deleted. Solution: 162444 SITUATION IDENTIFIED IN: "Production Planning Board" (tisfc1120m000) SITUATION DESCRIPTION: When sorting the Production Planning Board by Project, the Project code was truncated to six characters in its column. SOLUTION DESCRIPTION: When sorting the Production Planning Board by Project, the Project code is now completely shown in its column. Solution: 162449 SITUATION IDENTIFIED IN: "Report Orders Completed" (tisfc0120s000) SITUATION DESCRIPTION: When reporting a certain quantity complete in session tisfc0120s000 "Report Order Completed" for a second time without leaving the session the following error message is returned 'No more receipts may be made for order Production xxx/y-z, as final receipt has already been made'. This problem does not occur when closing the session between the two subsequent deliveries. SOLUTION DESCRIPTION: It is now possible to report multiple deliveries for a production order, without having to exit the session. Solution: 162457 SITUATION IDENTIFIED IN: "Integration Transactions by Document Line" (tfgld4512m000) SITUATION DESCRIPTION: When starting the "Integration Transactions by Document Line" (tfgld4512m000), the error "Unknown form field form.amount" occurs. The session's form is attempting to display a data field that is not defined in the session's program script. SOLUTION DESCRIPTION: The inconsistency between form data field and its corresponding program script are now corrected allowing the session to properly load. Solution: 162493 SITUATION IDENTIFIED IN: "Copy Sales Quotation" (tdsls1201m000) SITUATION DESCRIPTION: When copying sales quotation lines for generic items with new customers, the sales quotation is not copied, but the variant is copied with the original customer. Also, when copying sales order lines, the sales order is copied, but again the variant is copied with the original customer. SOLUTION DESCRIPTION: Now when copying sales quotation/order lines for generic items with new customers, the sales quotation/order are copied, and the variant is copied with the new customer. Solution: 162511 SITUATION IDENTIFIED IN: "Remove Confirmed Shipments" (whinh4250m000) SITUATION DESCRIPTION: Sales order lines cannot be released to invoicing, if the confirmed shipments have been removed to history. The error message "Cannot determine the cost of goods sold" is issued. SOLUTION DESCRIPTION: Now the confirmed shipments can be removed only after the sales order lines are released to invoicing. Solution: 162522 SITUATION IDENTIFIED IN: "Production Orders" (tisfc0501m000) SITUATION DESCRIPTION: Text button enabled for selected order with or without text present. SOLUTION DESCRIPTION: Text button is only enabled for selected order with text present. Solution: 162524 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: When using lattr.recordtimes, multicolumn horizontal printing did not print correctly. SOLUTION DESCRIPTION: Fixed the logic to process the extra layouts being printed. Solution: 162530 SITUATION IDENTIFIED IN: "Commissions Calculated by Order/Schedule" (tdcms0150s000) SITUATION DESCRIPTION: When the commission calculation method parameter is set to "Invoice", the system does not allow you to manually enter a commission for a sales order that has not yet been invoiced. It should be possible to create a manual commission in this case, but you should not be able to approve it yet. SOLUTION DESCRIPTION: The program has been changed to allow manual commissions to be linked to a sales order, regardless of the calculation method. The calculation method and the sales order invoice status will only be considered for manual commissions at the time that you try to approve them. Solution: 162539 SITUATION IDENTIFIED IN: "Import Journal Voucher Batches by ID Number" (tfgld2215m000) SITUATION DESCRIPTION: No transaction lines are imported even though they should be. SOLUTION DESCRIPTION: The form field Audit was not being initialized properly. This was causing the process that imports the data to be skipped. Now the form field Audit is initialized allowing the import process to occur. Solution: 162549 SITUATION IDENTIFIED IN: "Report Library" (ttstprepdll) SITUATION DESCRIPTION: When printing text on a line with an additional field that happens to be blank, the text is not displayed to the right column. SOLUTION DESCRIPTION: Fixed logic that positioned text so that it stays in it's proper place. Solution: 162554 SITUATION IDENTIFIED IN: "Post Integration Transactions To Finance Transactions" (tfgld4201m000) SITUATION DESCRIPTION: In the session "Default Project Data By Number Group" (tipcs0503m000), it is possible to set up a default project to be used in integration mapping for a series of actual projects. When assigning ledger accounts to integration transactions and using default projects for mapping, it was possible that ledger accounts were assigned based on a mapping scheme of lower priority even though a valid mapping of higher priority existed. For example: A ledger account would be picked up based on a match with item group before a match with project/item group if the mapping was based on default project. SOLUTION DESCRIPTION: The functionality of assigning ledger accounts for integration transactions has been changed. This will only change when using default projects. The priority list will now check the highest priority combination for actual project and then for default project before checking the next highest priority. Previously, all combinations were checked for actual project before any combinations were checked based on default project. Solution: 162559 SITUATION IDENTIFIED IN: "Close Production Orders" (ticst0201m000) SITUATION DESCRIPTION: When closing shop floor orders, with variances posted across more than one detailed cost component, resulting inventory variances, posted by aggregated cost component, can differ from variance amounts posted to the general ledger due to differing methods of rounding. SOLUTION DESCRIPTION: Variances, posted to inventory and the general ledger, are now rounded in the same manner eliminating the potential for rounding error discrepancies between the two packages. Solution: 162564 SITUATION IDENTIFIED IN: "Termination Process (Actual)" (tfgld1212s000) SITUATION DESCRIPTION: The lines written to the Tax Analysis Table (tfgld110) have the wrong sign for the contra for shifted tax record. SOLUTION DESCRIPTION: This was caused by the incorrect initialization of field values when the contra for shifted tax lines were created. Now the values are initialized correctly and the signs will be correct. Solution: 162581 SITUATION IDENTIFIED IN: "Transaction types" (tfgld0111s000) SITUATION DESCRIPTION: 1. When an existing transaction type is opened and the user just looks at the data in all three forms and exists without modifying anything a message is shown "Data has been changed....". Since nothing has been changed this message should not appear. 2. For a transaction type of category Journals or Recurring/Reversing journals if one sets up the decimal characters for quantities and amounts on form 2 as a comma, they get displayed as dots instead of comma when viewing them later. 3. When inserting or modifying a transaction type, if the transaction category is entered as anything other than Purchase or Sales Credit note and then changed to Purchase or Credit Note one can get a confusing message "Enter Yes/No" when trying to save the changes and the changes do not get saved. SOLUTION DESCRIPTION: 1. Only transaction types of category Journals or Recurring / Reversing Journals can have values in the fields "Date Format", "Decimal character for Amount", and "Decimal character for Quantity". The user does not have access to these fields for any other transaction category and these fields are displayed as blanks. However, when saving a new transaction type, these fields got saved with values incorrectly. When this record was selected for modification the system internally corrected the values to blanks and hence the user received the message even though the user did not change anything. The problem of incorrect value while creating new transaction types has been corrected so the problem will not happen for new transaction types. For existing transaction types the user should select "Save" when prompted with the message once. Then the correct values will be stored and the user will not receive this message from next time onwards for that transaction type. 2. Now the correct value comma or dot as entered by the user will be displayed. 3. This message got shown because the field "Negative Amount for Credit Notes" on the third form got an incorrect value when the steps defined above are followed. This field should either have a "yes" or "no" value but got an empty value. Thus the saving of the record failed. Now this field will have a value and this message will not appear. Solution: 162586 SITUATION IDENTIFIED IN: "Process NA Tax Provider Adjustments" (tccom6214s000) SITUATION DESCRIPTION: A fatal error: float exception is occurring when the user enters a tax adjustment with the net amount as 0.00 in the Tax Provider Calculation Utility session (tccom6212). If the sales amount is correct in the Vertex register, but an adjustment is needed to the tax amount, it is necessary to enter an adjustment in this session where the net amount is 0.00 and the tax amount is not. SOLUTION DESCRIPTION: The fatal error is caused by a calculation that is done to determine the tax rates for the given tax amount. When an adjustment is needed only for the tax amount, the tax rates are set to 0.00 making this calculation unnecessary. The calculation will be skipped now for adjustments with a net amount of 0.00, and the error will no longer occur. Solution: 162599 SITUATION IDENTIFIED IN: "Item Costing Data" (tcibd0107m000) SITUATION DESCRIPTION: When manufacturing is turned off, item costing data can still be accessed, however the costs cannot be calculated. SOLUTION DESCRIPTION: Now when manufacturing is turned off, item costing data can be accessed, and the costs can be calculated. Solution: 162608 SITUATION IDENTIFIED IN: "Archive/Purge Finance Transactions" (tfgld6205m000) SITUATION DESCRIPTION: Multi-company transactions in which the current company is the target company, do not always get archived even if they belong to the fiscal year being archived. SOLUTION DESCRIPTION: The archiving session picks up data from the Finalized Transactions table (tfgld106) based on the batch number and year retrieved from the Batch Status table (tfgld100). In an inter-company transaction the transactions in the target company are stored with the batch number of the originating company. If the target company has less usage, and thus the batch number has not advanced to the number, which was used in the inter-company transaction then such transactions will be missed from the archive/purge process. Now an additional search for such transactions is done, by making use of the Relations Inter-company Documents table (tfgld112) to make sure the transactions missed in the first processing get processed. After downloading this solution please run this session in the last archived year and it will process all the missed transactions from that year and any earlier year.. Solution: 162611 SITUATION IDENTIFIED IN: "Create Transactions from Scheme" (tfgld1204s000) SITUATION DESCRIPTION: When creating transactions from a schedule where expense tax codes are used, the tax lines are created with the wrong ledger account. SOLUTION DESCRIPTION: Now if the tax code is defined as an expense tax, the expense account will be used instead of the account defined in Financial Data for Tax Codes (tfgld0170s000/tfgld0171s000). Solution: 162628 SITUATION IDENTIFIED IN: "Copy Item Data" (tcibd0205m000) SITUATION DESCRIPTION: When copying general item data, and no warehouse item data exists, an error 606 (reference does not exist) is received. SOLUTION DESCRIPTION: Now when copying general item data, and no warehouse item data exists, the item is copied without error. Solution: 162658 SITUATION IDENTIFIED IN: "Product Configurator" (tipcf5120m000) SITUATION DESCRIPTION: When aborting the product configurator after marking a record, when further option sets to be configured are present, the session hangs. SOLUTION DESCRIPTION: Now when aborting the product configurator after marking a record, when further option sets to be configured are present, the session checks the subsequent option sets and properly alerts with validation messages. Solution: 162742 SITUATION IDENTIFIED IN: "Update Interim History - Ledger Account Totals" (tfgld1215s000) "Rebuild Ledger History" (tfgld3201m000) "Rebuild Dimension History" (tfgld3202m000) "Rebuild Opening Balance/History from Transactions" (tfgld3203m000) "Close Year - Provisional" (tfgld6201m000) SITUATION DESCRIPTION: Ledger history amounts that are shown on the Trial Balance reports are rounded incorrectly. Rounding in the sessions listed above has been done using the same rounding factor for all amounts regardless of currency. SOLUTION DESCRIPTION: Each currency has its own rounding factor, which determines the number of decimal places up to which an amount is stored and displayed in Baan. Due to a problem the same rounding factor (for the first currency read) got re-used while calculating rounded amounts for the other currencies processed by the above sessions. This led to amounts being stored with incorrect number of decimals. The above sessions have been corrected to use the rounding factor of the currency whose amounts are being processed. The amounts in the history tables can be corrected after downloading this solution and running the re-build sessions listed above again. Solution: 162748 SITUATION IDENTIFIED IN: "Archive/Purge Finance Transactions" (tfgld6205m000) SITUATION DESCRIPTION: In multi-company, records in the Documents table (tfgld018) in which the current company is the target company do not always get archived/purged even if they belong to the fiscal year being archived/purged. Currently, the Finalized Transactions table (tfgld106) is archived/purged correctly. SOLUTION DESCRIPTION: Changes have been made to the session to process data in the Documents table (tfgld018) along with the data in the Finalized Transactions table (tfgld106). 134904 SITUATION IDENTIFIED IN: "Transfer Payments" (tfcmg126091000) SITUATION DESCRIPTION: 1.The report "Nordic Payment Report" (report 9, rtfcmg126091000) cannot handle bank accounts that consist of more than 17 positions. This cannot be printed on the report and the account number will be truncated. 2. The value for 'Total Bank Account' does not summarize correctly. This is because the value is outside the system boundaries. SOLUTION DESCRIPTION: 'Bank Type' has been adjusted to display the account number completely (25 characters). The value in the field 'Total Credit Bank Accounts' is also displayed correctly. 135304 SITUATION IDENTIFIED IN: "Match Purchase Receipt Lines" (tfacp2544m000) SITUATION DESCRIPTION: 1. If a purchase invoice is matched to an order and later in session "Match/Approve Purchase Invoices" (tfacp2107s000) if a different order number is entered to be matched, then the session "Match Purchase Receipt Lines" (tfacp2544m000) doesn't show the lines from the new order number. 2. If the purchase order is not yet approved, then these orders are still displayed in the session "Match Purchase Receipt Lines". SOLUTION DESCRIPTION: 1. The session "Match Purchase Receipt Lines" will display the details of the order entered. 2. Orders are displayed only if the approved quantity is not equal to zero. 135305 SITUATION IDENTIFIED IN: "Change Prices and Discounts after receipts" (tdpur4122m000) SITUATION DESCRIPTION: If the back orders are not confirmed, the planned inventory transactions/on order quantities are doubled while changing the prices/discounts after receipt. SOLUTION DESCRIPTION: The Order Quantity / Planned Quantity is not doubled while changing the prices and discounts after receipts even when the back orders are not confirmed. 135325 SITUATION IDENTIFIED IN: "Print Purchase Receipts" (tfacp1430m000) SITUATION DESCRIPTION: The report "Print Purchase Receipts" (tfacp1430m000) doesn't print whether the orders have been matched to order to receipts. SOLUTION DESCRIPTION: The report now prints whether the order has been matched to order or to receipt. 135348 SITUATION IDENTIFIED IN: "Print Specifications Delivered, Not Yet Invoiced" (tfacr1432m000) SITUATION DESCRIPTION: In report "Print Specifications Delivered, Not Yet Invoiced" (tfacr1432m000), the rounding of amounts is being done per order/position number. Where this should happen only for Sales/Service Invoicing type Integration transactions and for all others the rounding should be done per line. SOLUTION DESCRIPTION: The rounding is done per transaction line in the integration if the Integration record is not of type Sales/Service Invoicing. 135355 SITUATION IDENTIFIED IN: "Installment Orders" (tdsls4506m000) SITUATION DESCRIPTION: Installment Lines can have status "Release for Invoicing" in session "Sales Installment Orders" (tdsls4506m000). This means the line still must be released to invoicing, before it can processed further. In Dutch this status is translated as "Vrijgegev. v. facturering", which gives the impression the installment line is already released to Invoicing. SOLUTION DESCRIPTION: The Dutch description of Installment Lines with status "Release for Invoicing" is "Vrijgeven voor Facturing". This line should still be released to invoicing. 135356 SITUATION IDENTIFIED IN: "Print Direct Debit Letters" (tfcmg4270m000) SITUATION DESCRIPTION: Fatal Error "itccom0010.report_opened index 0 out of dims" occurs when trying to do a "Test Print" of the Direct Debit Letter. SOLUTION DESCRIPTION: The Fatal Error does not occur anymore when doing a 'Test Print' of the Direct Debit Letter. 162766 SITUATION IDENTIFIED IN: "Calculate Commissions/Rebates" (tdcms0240m000) SITUATION DESCRIPTION: When using a calculation method of 'Order' in CMS parameters, it is possible for calculated commissions/rebates to be incorrect when a backorder occurs. If you calculate commissions/rebates before confirming the backorder, the calculated amount will be for the entire order line. Then, when the backorder is confirmed, a new sales order line detail is added with commissions/rebates linked to it. When you calculate again, the original calculation stays the same, but commissions/rebates are also calculated for the new line. This is incorrect, as the backorder detail amount should have been deducted from the original amount in the original commission/rebate calculation. SOLUTION DESCRIPTION: When a backorder is confirmed, unconfirmed, or cancelled, the change can affect commissions/rebates linked to the order line. To handle this, the status of all linked relations for which commissions/rebates have already been calculated will be changed from 'Processed' to 'Recalculate'. This will force the user to calculate again, ensuring that the correct amounts are calculated for the entire order. 162774 SITUATION IDENTIFIED IN: "Close Periods" (tfgld1206m000) SITUATION DESCRIPTION: Error messages are improperly displayed in languages that require multi byte characters to display properly. SOLUTION DESCRIPTION: The session has be modified to properly handle multi byte characters. 162824 SITUATION IDENTIFIED IN: "Report Operations Completed" (tisfc0130s000) SITUATION DESCRIPTION: When completing an operation, after completing more than the planned quantity for the previous operation, then rejecting some quantity and manually adjusting the 'back flushing to do' field to reflect the non-rejected quantity, the system issues the full planned back flushing quantity. SOLUTION DESCRIPTION: Now, in the above scenario, only the amount manually entered into the 'back flushing to do' field is issued. The remaining quantity is registered in subsequent delivery for the material line and must be zeroed out manually by the user before closing the order. 135296 SITUATION IDENTIFIED IN: "Maintain Activity budget lines" (tpptc2110s000) SITUATION DESCRIPTION: The user is not able to save an activity budget line, without moving to the second form. SOLUTION DESCRIPTION: Now the user is able to save the record even without moving to the second form. 162801 SITUATION IDENTIFIED IN: "Simulate Orders" (cprrp1210m000) SITUATION DESCRIPTION: When using Oracle Level 2 driver, and running simulate orders for one generic item, it was taking a long time to complete the run. SOLUTION DESCRIPTION: Query has been optimized to improve performance on Oracle Level 2 Driver. 135746 SITUATION IDENTIFIED IN: "Print Sales Contract Reports" (tdsls3401m000) "Print Sales Contracts by Item and Price group" (tdsls3410m000) "Print Sales Contract Line Reports" (tdsls3411m000) SITUATION DESCRIPTION: 1. When opening print sessions via the 'print'-button on session "Sales Contracts" (tdsls3500m000) the contract number is not filled on the print-sessions. 2. When printing 'Sales Contracts by Item and Price group' (tdsls3410m000) and 'Sales Contract Line Reports' (tdsls3411m000), the effective and expiry dates are taken from the Sales Contract Header and not from the Lines. SOLUTION DESCRIPTION: 1. On the following sessions the contract number is now automatically filled when opened from "Sales Contracts" (tdsls3500m000): - Print Sales Contract Reports (tdsls3401m000) - Print Sales Contracts by Item and Price group (tdsls3410m000) - Print Sales Contract Line Reports (tdsls3411m000) 2. On the 'Sales Contracts by Item and Price group' (tdsls3410m000) and "Sales Contract Line Reports" (tdsls3411m000) the effective and expiry dates are taken from the Sales Contract Lines now. 135480 SITUATION IDENTIFIED IN: "Update Sales Order Line with Shipped Quantity" (whcor0212m000) SITUATION DESCRIPTION: When running session "Update Sales Order Line with Shipped Quantity" (whcor0212m000) a fatal error occurs: "Illegal number of arguments (11) for function whint.dlltdsls.update.delivery.so.line expected 12" SOLUTION DESCRIPTION: An extra argument has been added no error arises now. 135558 SITUATION IDENTIFIED IN: "Purchase Order Lines" (tdpur4101s000) SITUATION DESCRIPTION: Error message "Equipment Items not allowed" is given when user tries to enter standard equipment item in the purchase order line. Earlier user is able to enter and save the purchase order line with standard equipment item. SOLUTION DESCRIPTION: User is allowed to enter and save a purchase order line for a standard equipment item. 162950 SITUATION IDENTIFIED IN: "Create Transactions from Scheme" (tfgld1204s000) SITUATION DESCRIPTION: When creating transactions from a schedule where expense tax codes are used, the tax lines are created with the wrong ledger account. SOLUTION DESCRIPTION: Now if the tax code is defined as an expense tax, the expense account will be used instead of the account defined in Financial Data for Tax Codes (tfgld0170s000/tfgld0171s000). 135233 SITUATION IDENTIFIED IN: "Service Order Actual Other Costs" (tssoc2141s000) SITUATION DESCRIPTION: 1. When having subcontracting costs on a service order or work order, and the purchase office of the purchase order has a different financial company than the service department, all WIP bookings are done for the financial company of the service department. The credit WIP booking however, should be booked on the financial company of the purchase office. 2. When running DSRP, a zero amount transaction is booked for a subcontracting line. This also happens when changing just any data on the subcontracting cost line. SOLUTION DESCRIPTION: 1. When having subcontracting costs on a service order or work order, and the purchase office of the purchase order has a different financial company than the service department, the credit WIP booking is done on the financial company of the purchase office. 2. Zero amount bookings will only done when updating the subcontracting costs (which can be zero) from the related purchase order. 135446 SITUATION IDENTIFIED IN: "Service Orders" (tssoc2100s000) SITUATION DESCRIPTION: Originally, main sessions were not refreshed after processes such as releasing, costing, accepting or canceling have been carried out. The solution 115462 provides a solution so that the main sessions and sub sessions are refreshed and updated after these processes are carried out. The changes were made in several sessions including the sessions Service Contracts (tsctm3100s000), Contract Installments (tsctm4100s000), Service Orders (tssoc2100s000) and Service Order Activities (tssoc2110s000). In these sessions, the changes were not needed and in fact, they are blocking for running the session under workflow control. SOLUTION DESCRIPTION: The changes made for solution 115462 will be undone in sessions Service Contracts (tsctm3100s000), Contract Installments (tsctm4100s000), Service Orders (tssoc2100s000) and Service Order Activities (tssoc2110s000) since they are not needed and they are causing problems for Workflow. 135477 SITUATION IDENTIFIED IN: "Print Specifications Delivered not yet Invoiced" (tfacr1432m000) SITUATION DESCRIPTION: The report of session tfacr1432m000 will compare the Sales Invoice amounts with the Sales Issue amounts. For closed Sales Orders no difference should exist while in practice in some situations an unexpected difference may occur. SOLUTION DESCRIPTION: A correction program has been developed to correct differences between the Sales Invoice amounts and the Sales Issue amounts. By inserting financial integration transactions this difference is cleared. Furthermore the COGS amounts stored on the Sales Order Line, Sales Order History Line and the Sales Order Invoice Line are updated. An option is available to execute this correction program in test mode. In test mode no actual table updates will be performed. Before the correction program is executed in update mode the output reported in test mode should be carefully analyzed. Financial integration origins (TROR) and financial integrations types (FITR) considered by this correction program are: - Sales / General Cost - Sales / Direct Delivery - Sales / Issue - Sales / Issue (Invoiced) - Warehousing Consignment / Issue - Warehousing Consignment / Issue (Invoiced) - Service / Approved for Invoicing - Sales Invoicing (Sales) / COGS (material) - Sales Invoicing (Sales) / COGS (operation) - Sales Invoicing (Sales) / COGS (surcharge) - Sales Invoicing (Sales) / COGS (general) - Sales Invoicing (Service) / COGS (material) - Sales Invoicing (Service) / COGS (operation) - Sales Invoicing (Service) / COGS (surcharge) - Sales Invoicing (Service) / COGS (general) Several options are available when executing the correction program: Fiscal Year/Period: When left empty the fiscal year and period is determined based on the original transaction date of the corrected transaction. In case the fiscal year and period are closed the transaction will be booked into the next open period based on the parameter "Posting to next open period allowed" (tfgld4150s000) The user can overrule the automatic determination of the fiscal year and period by filling this field on the form. Only an open fiscal year and period can be chosen. Reporting Year/Period: Logic identical to fiscal year/period field Tolerance: The allowed tolerance for the difference between the issue and COGS amounts Correct only when difference on Specification Delivered not yet invoiced: When this option is set no financial integration transactions will be inserted when there is no difference reported by tfacr1432m000 on a certain interim account even though there might be a difference between the issue/COGS amount stored in logistics and finance. Consider Delivered: When this option is not selected a possible difference between the issue amount in finance and logistics is not corrected. Consider Invoiced: When this option is not selected a possible difference between the COGS amount in finance and logistics is not corrected Update mode: Determines whether this correction program is executed in test or update mode Currency: The currency in which found differences, should be reported. In a Dependent or Single currency system this will always be the reference currency. The "rotate currency" button is only enabled in an Independent currency system, which will allow the user to rotate between the different defined home currencies. Some things have to be taken care of when executing this correction program: 1) Execution in Job mode When executing the correction program in Job mode care has to be taken when selecting a device of type ‘file’ (when selecting an actual printer device the issue described below is not applicable). This is because the correction program will report the corrected data in two separate reports, while when running in Job mode only one output file can be specified. To prevent both reports do overwrite each other a device of type ‘append to file’ has to be chosen. The second report output will then be appended to the first report output in the same output file. 2) Archiving Once the sales order history is archived this program is not able to correct the financial transactions anymore. Archived Sales Order history lines will just not be considered. The inventory transactions stored in Warehousing are also needed by this correction program and can be archived as well. In case an issue/receipt is selected (as it still exists in the sales order history) for correction while the transaction date Is before the last archiving date a message will be displayed and the correction is skipped. Furthermore the financial integration transactions can have been archived which are needed to be able to correct as well. Since its not possible to determine whether a certain financial integration transaction is just missing or archived care has to be taken with this scenario as the correction program is not capable of preventing unnecessary insertion of archived transactions. So incase the correction program inserts integration transactions before the last archive action those orders should be skipped manually. 162985 SITUATION IDENTIFIED IN: "Audit and Terminate Batches" (tfgld1211s000) SITUATION DESCRIPTION: A check to determine if amounts are completely split up in Service was erroneously removed. This is allowing non-opening balance transactions with split amounts to finalize. SOLUTION DESCRIPTION: The previous error checks have been incorporated back into the session "Audit and Terminate Batches" (tfgld1211m000) - to prevent these type of transactions from improperly finalizing. 135805 SITUATION IDENTIFIED IN: "Quotation Lines" (tdsls1100s000) "Correct Contract Data" (tdcor0013m000) SITUATION DESCRIPTION: Some labels regarding session 'Quotation Lines' (tdsls1100s000) and 'Correct contract data' (tdcor0013m000) are missing. SOLUTION DESCRIPTION: Regarding labels are re-dumped. 135790 SITUATION IDENTIFIED IN: "Print PCS Project Transaction Specification" (tfgld4418) "Delete WIP Transactions by Project/Order" (tffin1200) "Generate Invoice by Self Billing" (tfacp2290) "File 1099-MISC" (tfcmg3204) "Dimensions " (tfgld0510) SITUATION DESCRIPTION: Labels are missing in several forms and reports of the sessions, mentioned above. They are delivered or given more space so that the labels fit in the space, available on the form/report. SOLUTION DESCRIPTION: Labels are missing in several forms and reports. They are delivered or given more space so that the labels fit in the space, available on the form/report. 135807 SITUATION IDENTIFIED IN: "Print Installments" (tppin4451m000) "Copy Plans" (tppss0211m000) "Copy Element Budget Data" (tpptc1245m000) SITUATION DESCRIPTION: Several labels were missing. This resulted in empty spaces on forms and reports. * In session tppin4451m000 "Print Installments" the label "Print lines in installment currency an total in currency of B.P." was missing. * In session tppss0211m000 "Copy Plans" the label "Use Already existing Cost Objects" didn't have a German Translation. * On the report from session tpptc1245m000 "Copy Element Budget Data" in the header there was no label for German for the column "Line number". SOLUTION DESCRIPTION: The missing labels are made available. 135814 SITUATION IDENTIFIED IN: "Several" (Several) SITUATION DESCRIPTION: Missing labels in reports and forms SOLUTION DESCRIPTION: Labels that are not present are created. Labels present in all languages in Gamma, but not in Explorer are redelivered along with the forms and reports. Labels not translated are given for translation SITUATION IDENTIFIED IN: "Quotation Lines" (tdsls1100s000) SITUATION DESCRIPTION: Label called 'Rep 2' regarding session 'Quotation Lines' (tdsls1100s000) is missing. SOLUTION DESCRIPTION: Regarding label has been re-dumped. This solution contains a Functional Optimization. Please read solution <sol_nr> 134994 </sol_nr> for the background of Functional Changes. 136024 SITUATION IDENTIFIED IN: "Quotation Lines" (tdsls1100s000) SITUATION DESCRIPTION: Label called 'Rep 2' regarding session 'Quotation Lines' (tdsls1100s000) is missing. SOLUTION DESCRIPTION: Regarding label has been re-dumped. This solution contains a Functional Optimization. Please read solution <sol_nr> 134994 </sol_nr> for the background of Functional Changes 135979 SITUATION IDENTIFIED IN: "Print Program Structure Diagram" (ttadv2430m000) SITUATION DESCRIPTION: Problem 1: When running session "Print Program Structure Diagram" (ttadv2430m000) for a range of scripts, a fatal error occurred. Problem 2: When running session "Print Program Structure Diagram" (ttadv2430m000) twice without leaving the session, the second run will not result in a report. SOLUTION DESCRIPTION: Problem 1 was caused by incorrect placing of "#pragma" statements in the application scripts. Now the session no longer aborts, the "#pragma" statements are accepted. Problem 2 is solved, by re-initializing several program variables before the second run. 135928 ITUATION IDENTIFIED IN: "Print Rejects" (tisfc0403m000) SITUATION DESCRIPTION: Missing Label 'Completion Date' for Session Print Rejects (tisfc0403m000) SOLUTION DESCRIPTION: Label 'Completion Date' for Session Print Rejects (tisfc0403m000) 135746 SITUATION IDENTIFIED IN: "Print Sales Contract Reports" (tdsls3401m000) "Print Sales Contracts by Item and Price group" (tdsls3410m000) "Print Sales Contract Line Reports" (tdsls3411m000) SITUATION DESCRIPTION: 1. When opening print sessions via the 'print'-button on session "Sales Contracts" (tdsls3500m000) the contract number is not filled on the print-sessions. 2. When printing 'Sales Contracts by Item and Price group' (tdsls3410m000) and 'Sales Contract Line Reports' (tdsls3411m000), the effective and expiry dates are taken from the Sales Contract Header and not from the Lines. SOLUTION DESCRIPTION: 1. On the following sessions the contract number is now automatically filled when opened from "Sales Contracts" (tdsls3500m000): - Print Sales Contract Reports (tdsls3401m000) - Print Sales Contracts by Item and Price group (tdsls3410m000) - Print Sales Contract Line Reports (tdsls3411m000) 2. On the 'Sales Contracts by Item and Price group' (tdsls3410m000) and "Sales Contract Line Reports" (tdsls3411m000) the effective and expiry dates are taken from the Sales Contract Lines now. 162529 SITUATION IDENTIFIED IN: "Print Costing History by Item Group" (ticst3401m000) SITUATION DESCRIPTION: Cost amount values for a production order can exceed the size of their respective report fields, leading to overflow ("########") problems on the report. SOLUTION DESCRIPTION: The report has been reformatted so that even the largest cost amounts can be printed on the report without error. 162797 SITUATION IDENTIFIED IN: "Audit and Terminate Batches" (tfgld1211m000) SITUATION DESCRIPTION: When entering opening balance transactions for an account linked to projects, the session is not verifying that the amount entered is fully allocated against a project. A check should be done to prevent the batch from being finalized if the amount entered has not been fully allocated against a project. SOLUTION DESCRIPTION: When finalizing opening balance batches a check has been introduced to verify that the amounts entered are fully allocated against the project. If the amount has not been fully allocated, the error message "Baan project amount not split up completely" will be given and the batch cannot be finalized. 135953 SITUATION IDENTIFIED IN: "Outbound Order Lines" (whinh2520m000) SITUATION DESCRIPTION: For an item with package definition, outbound advice cannot be released (session "Outbound Order Lines" (whinh2520m000)) if it is not advised in inventory unit. Blocking message "Negative inventory not allowed" pops up. SOLUTION DESCRIPTION: Inventory unit and Storage unit were mixed up, creating a negative inventory, that causes message "Negative Inventory not Allowed" to appear. Negative inventory is calculated now using the inventory unit, then no negative inventory is created. 135858 SITUATION IDENTIFIED IN: "Link Invoices to Credit Notes II" (tfacr2121s000) SITUATION DESCRIPTION: When linking a sales credit note created in one of the home currencies with a sales invoice created in a foreign currency, the document goes out of balance. Due this the document cannot be finalized. SOLUTION DESCRIPTION: When linking a sales credit note created in one of the home currencies with a sales invoice created in a foreign currency, the document won’t go out of balance. Batch can be finalized.