Solution: 114568
VERSION(S):
B50_b, B50_c
SITUATION IDENTIFIED IN:
"Import Version Dump" (tgbrg1245m000)
"Revalidate Licensed Version" (tgbrg1247m000)
SITUATION DESCRIPTION:
No authorization for importing a version dump or revalidating a licensed version.
SOLUTION DESCRIPTION:
Due to different date formats depending on the locale used, an incorrect license check was done.
Now the date format used for licensing is not depended anymore on which locale is set.

Solution: 117286
SITUATION IDENTIFIED IN:
Copy Solution Registry to Derived Update VRC (ttpmc2290m000)
SITUATION DESCRIPTION:
When the vrc's are not derived the message "pmcs22901 ??????????" is displayed
SOLUTION DESCRIPTION:
This problem is solved by delivering the message

Solution: 117399
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
"Generate Outbound Advice" (whinh4201m000)
SITUATION DESCRIPTION:
The situation applies to sales orders with a linked purchase order.
If the item on the sales order has available stock and an outbound advice is made, the outbound advice doesn't take an
existing inbound advice into account.
The following can happen:
-Item A; inventory available 5 pcs
-A sales order is made for 10 pcs; from this sales order a purchase order is generated
-A receipt is done for the purchase order
-An inbound advice is generated; 10 pcs are advised to the staging location
-An outbound advice is made for the outbound line, 5 pcs from stock are advised to the staging location.
This means that in total 15 pcs are advised to the staging location (10 from the inbound advice, 5 from the outbound advice).
Both advices can be put away or released, so the system will put 15 pcs on the staging location.
This is wrong because only 10 pcs will be shipped.
SOLUTION DESCRIPTION:
The "advised quantity" on the related outbound order line is modified when an inbound advice is created, changed or
deleted.
If an outbound advice is made only the remaining part, for which no inbound advice exists, will be advised.

Solution: 118032
SITUATION IDENTIFIED IN:
"Print Item Production Data" (tiipd0401m000)
SITUATION DESCRIPTION:
Session takes a long time to print the item production data when the session runs with a range of Item Group or Item Type
SOLUTION DESCRIPTION:
Now the performance is improved with the modification of select queries.

Solution: 121334
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
1. On a Configuration it is possible to manually change the currency of the Call out charge in session "Configurations"
(tscfg2120s000) This Currency is not used by Calls or Service Orders on this Configuration. On an Internal Configuration
the same situation occurs.
2. When creating a new call the initial and actual priority are calculated based on the initial time left and the actual time left. If these times are
still empty, what they are when creating a new call, then value 0 will be used to calculate the priorities. In the "Priority Time Scale" table (tsclm024)
the priority descriptions are obtained based on the time left. If this time left is 0 then it will always take the highest priority (with the lowest time left)
when creating a new call.
3. If Execution Start Time and
Execution Finish Time are filled it is
mandatory to fill the duration.
SOLUTION
DESCRIPTION:
1. The currency for the Call Out Charge can manually be changed because the currency of the Business Partner can change. This will not influence the
specified
currency defined on the Call Out Charge so the amount will always be in the correct currency. The possiblitlity to manually change it to whatever
currency is desired, is then allways there. It also gives the flexibility to define all Call Out Charges in the same currency.
For an internal Configuration this
has no meaning. The call
out charge will not be
used. So in that case
the following
fields will be
disabled:
Session "Configurations" (tscfg2120s000): Field "Call Out Charge" (tscfg220.ccha) and field "Currency" (tscfg220.ccur)
Session "Calls" (tscfg1100s000): Field "Currency" (tsclm100.ccur) and "Country" (tsclm100.ccty)
Session "Service Orders" (tssoc200.ccur) and
"Exchange Rate Type"
(tssoc200.rtyp).
2. When creating a new call the Initial and Actual priority are shown when the actual time left is available, which is just after saving the call.
3. If the execution times are filled it is not mandatory to fill the duration. In SOC the check on the duration when planning the order with GSRP is
removed. It is now possible to plan a service order without having duration filled on the order or on any activities.
The following situations will then occur when transferring a call to a service order.
Transfer:
With no execution start and finish time:
Old situation: it was possible to transfer without duration.
New situation: same as old situation
With execution start and finish times filled:
Old situation: it was mandatory to fill the duration
New situation: possible to transfer without duration
Emergency release:
With no execution start and finish time:
Old situation: you could release a service order without duration.
New situation: same as old situation
With execution start and finish times filled:
Old situation: it was mandatory to fill the duration
New situation: possible to release a service order without duration
Plan:
Without execution start and finish time:
Old situation: not possible to plan without duration
New situation: possible to plan a service order without duration
With execution start and finish times filled:
Old situation: it was mandatory to fill the duration
New situation: possible to plan a service order without duration
Invoice:
Without execution start and finish time:
Old situation: it was possible to solve and invoice the call without duration
New situation: same as old situation
With execution start and fnish times filled:
Old situation: it was possible to solve and invoice the call without duration
New situation: same as old situation.

Solution: 121385
SITUATION IDENTIFIED IN:
"Bill of Material" (tibom1110s000)
SITUATION DESCRIPTION:
It should be possible to copy a non-customized component to a customized component in session tibom1110s000 when a
non-customized "to order" item is found in the BOM of a customized parent item.
SOLUTION DESCRIPTION:
A button to copy from standard to customized is added to session tibom1110s000.

Solution: 121466
SITUATION IDENTIFIED IN:
"Material to 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 orderline 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 orderline can be reduced, new inbound orderline is not created. Instead, outbound orderline quantity is reduced.
DOCUMENTATION:
For more detailed functional info please ask for document #22199.
SOLUTION 125117 AFTER THIS SOLUTION.
If your Current VRC is B50L_c_bgl0, download solution 125264 also.
VERSION(S):
B50_b, B50_c

Solution: 121580
SITUATION IDENTIFIED IN:
"International Bank Account Number" (IBAN)
SITUATION DESCRIPTION:
The table changes in order to make the International Bank Account Number (IBAN) available for use within Baan have been
delivered with the solution 119866. It has been noticed that not all the tables that contain a bank account, have been
adapted for use with IBAN.
SOLUTION
DESCRIPTION:
With this current solution (still the 1st phase) additional changes in the data model, needed to store the entered data, have come available as well as help texts to
support the use of the new fields.
This means that you can still ONLY ENTER the IBAN and the Bank Identifier AT THIS MOMENT. The components to
use the data filled in these fields will soon become available in the 2nd phase. In that phase the display sessions and some reports will be delivered
together with a (changed) form in the module 'Finance / Cash Management' (tfcmg), where you can switch on/off the use of IBAN per payment
method.

Solution: 121914
SITUATION IDENTIFIED IN:
"Integration Transactions by Project / Order" (tfgld4510m000)
SITUATION DESCRIPTION:
Integration transaction amount not correct because of rounding
SOLUTION DESCRIPTION:
The rounding is done uniformly and the order amount in purchase as well as finance is same

Solution: 122007
SITUATION IDENTIFIED IN:
"Contract Other Terms" (tsctm1536m300)
SITUATION DESCRIPTION:
1) The allocated and spent costs are booked on the first cost term. This is only happening for Subcontracting and Other.
2) For B50_b only: When the cost component changes on a Service Order Actual Cost Line, allocation on the Contract
Coverage term and/or Cost term is not updated accordingly.
SOLUTION DESCRIPTION:
1) Also for cost types Subcontracting Costs and Other Costs the allocation will be done on the right cost term, I.E using the
differentiators.
For Other Costs the only differentiator is the Cost Component. For Subcontracting Costs there is also the Business Partner as
differentiator.
2) For B50_b only: Changing the cost component on a Service Order Actual Cost Line, will be reflected on the Contract
Coverage Term and Cost Term.

Solution: 122191
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
We want to use the FIND function in the Dynamic Menu Browser. However this function does not work for multi-byte
characters.
SOLUTION DESCRIPTION:
After some searching we discovered, that a used system function was the cause. We changed the FIND functionality, so it
uses now another function, which can work with multi-byte characters.

Solution: 122350
SITUATION IDENTIFIED IN:
"Planned Activities" (tsspc2500m000)
SITUATION DESCRIPTION:
1) When generating planned activities with session "Generate Maintenance Planning" (tsspc2200m000), the last generated
planned activity falls outside the time range defined in this generate session.
2) When generating planned activities using predicted activities, the first planned activity will be planned after the first time
interval, however when generating without predictions but straight from the concept the first planned activity will fall ON the
start date, so before the first time interval.
3) Field "Maint. Planned Till" (tscfg220.medt) on session "Configurations" (tscfg2120s000 "Service Data" tab) is not
updated correctly:
When generating planned activities the "Maint. Planned till" date is based on the Planned Finish Date of the last activity.
This can cause double activities to be planned when generating planned activities later when an overlap in the time range
is defined on the "Generate Maintenance Planning" (tsspc2200m000) session, when using planning method "Start Date of
Object" or "1st of January".
When deleting planned activities with session "Delete Maintenance Planning" (tsspc2202m000) field "Maint. Planned Till"
is filled with the "Time From" date (form field tsspc2202m0001time.f) defined on the "Delete Maintenance Planning" session.
Even when deleting activities which are followed by activities in future which should not be deleted.
SOLUTION DESCRIPTION:
1) The planning dates are generated using backward planning instead of forward planning.
Example:
Concept of a frequency of 4 activities per year results in 4 interval periods of 91,25 days.
In the old situation when starting to plan on the first of January (with methods "Date From" or "1st of January") this would
result in a Planned Start Date of the first Planned Activity on 01 April at 07:00:00hrs.
In the new situation this will be the Planned Finish Date instead of Planned Start Date. The Planned Start Date will be
determined as Planned Finish Date minus the duration of the activity.
If the Planned Start Date will fall before the "Time From" on the "Generate Maintenance Planning" session the system will
however plan forward to assure that this Planned Activity is included in the planning.
The reason for this change is that the last Planned Activity would always fall outside the time range set on the generate
session because it would start in the new period.
Example: frequency of 4 activities per year is 365 / 4 results in 4 intervals of 91,25 days. The last interval point will fall
exactly on 365 +1 = 366
When planning from the first of January with methods "Date From" or "1st of January" the last activity would start on 1st of
January of the next year on 00:00:00 hrs. To ensure that all activities are planned within the given range they are planned
backwards in the new situation. So the 1st of January of next year at 00:00:00 is then the Planned Finish Date instead of
Planned Start Date.
If any of the Planned Activities would fall outside the given time range due to Calendar influences, message "Not able to
plan on %D001; No availability in the Calendar." is printed on the error report (if selected). %D001 represents the initial
date on which the planned activity was to be planned.
2) When generating planned activities the start of the first activity is planned AFTER the first time interval calculated from
the start date. This is made consistent for both planning with predictions or without predictions.
For example: 4 planned activities within one year. The time interval will be 365days / 4 activities = 91,25 days between the
finish dates of the activities. When the start date is the 1st of January, the first activity will finish on the 2nd of April and
NOT start on the 1st of January.
(this example is based on a logical unit conversion of 365 days per year, the outcome will be different if the unit
conversions are setup differently. Calendars are not considered in this example)
3) Updating field "Maint. Planned till" (tscfg220.medt) on session "Configurations" (tscfg2120s000 "Service Data" tab):
When generating planned activities:
The "Maint. Planned till" date on the Configuration is based on the "Time To" on the "Generate Maintenance Planning"
session instead of on the Planned Finish Date of the last planned activity.
Note: if the "Time To" time is not 00:00:00 (midnight) then the "Maint. Planned till" date will be set on the next day. The
"Maint' Planned till" date is only a date and has no time specified.
Example. When the "Time To" on the generate session is defined as 1st of June of 2002 at 13:00:00hrs the "Maint. Planned
till" date will be 2nd. of June 2002.
When deleting planned activities:
The "Maint. Planned till" date on the Configuration is based on the "Time From" date defined on the "Delete Maintenance
Planning"(tsspc2202m000) session. But only when no Planned Finish Date exist which is on or past this "Time From" date.
Example:
There are two activities for which Planned activities have been generated. Activity A and Activity B.
The Planned Finish Date of the last Planned Activity B is 1st of January 2003 at 00:00:00.
In the delete session a range is set of deleting Activity A from the 1st of April of 2002. at 00:00:00.
The "Maint. Planned till" date will in that case not be changed to the 1st of April because after this date there are still planned
activities.
IMPORTANT NOTES!
Manual changes in Planned Activities will NOT change the "Maintenance Planned till" date on the Configuration. Only the
generate and the delete sessions.
If there are no planned activities left after the delete process then the date field will be emptied.
Deleting a range of activities from a certain date might cause double planned activities to be generated when generating new
planned activities from that date, because of backward planned activities which originally would be included in the deleted
range. (This is only applicable when using planning methods "Start Date of Object" and "1st of January")
Example:
A planned activity would originally be planned on the 1st of April but due to unavailability in the calendar it is backward
planned to the 30th of March.
Next all the planned activities from the 1st of April are deleted with the delete session. The "Maint. Planned till" date on the
configuration is now automatically set to the 1st of April.
When generating a new maintenance planning with a "Time From" before the "Maint. Planned till" date, the "Maint. Planned
till" date will be considered as "Time From" date. The system will try to plan the original activity on the 1st of April
again. On the 1st of April is no availability in the calendar so the system will try to plan backward but due to the "Maint.
Planned till" date it cannot be planned backward but will be planned forward and hence will be planned double.

Solution: 122488
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
After solving a call in session "Calls" (tsclm1100s000) which has a Sold-To Business Partner with a Rate Determiner of
"Fixed Hard", then the call cannot be invoiced and no Service Order is created as the error message "This Rate Determiner is
not allowed" appears. This situation means that an invoice can never be created and the costs cannot be put on the Contract
or Warranty.
SOLUTION DESCRIPTION:
Checks are now made to ensure the validity of the Rate
Determiner and therefore Calls can now be solved and invoiced correctly.
The following explains about the Rate Determiners:
a) The value "Receipt Date" is not allowed in Service and is only used in Purchase Order and Purchase Invoice
transactions. Document date should be used.
b) The value "Delivery Date" is not allowed in Service and is only used in Sales Order and Sales Invoice transactions.
Document date should be used.
c) In a Dependent Multi-currency system (out of the "fixed"
Rate Determiner variants) only "Fixed
Local and Hard" is allowed.
A Single Currency system set up is very similar to a Dependent Multi-currency set up, because all rates are only set up to
the single home currency. Actually, a Single Currency set up can be seen as a Dependent Multi-currency set up having only
the reference currency in place.
With both these currency systems the currencies are considered hard so "Fixed Local and Hard" is the only allowed Rate
Determiner for both these currency systems.
d) In an Independent Multi-currency system all 3 fixed Rate Determiner variants are allowed.
e) The values "Manually Entered" and "Expected Cash Date" can be used in all currency systems and by all transactions.
When defaulting a rate determiner on a contract (quotation) (only B50c) and on a service order (quotation), then the rate
determiner will be defaulted with
- the rate determiner of the business partner as specified in "Sold-to Business Partners" (tccom4110s000) or
- 'Document Date'
in case the rate determiner defined in the business partner's data is 'Receipt Date'.
- 'Document Date'
in case the rate determiner defined in the business partner's data is
'Delivery
Date'.
- 'Fixed Local and Hard' in case in case the rate
determiner defined in the business partner's data is 'Fixed Local' or 'Fixed Hard' and the currency system is either Single Currency system or Dependant
Multi-currency system.

Solution: 122576
SITUATION IDENTIFIED IN:
"Print Estimated vs. Actual Material Costs" (ticst0401m000)
SITUATION DESCRIPTION:
1. When the quantity reported complete + the rejected quantity on an operation exceeds the quantity planned input, the net
quantity (ticst001.qune) is changed according to the reported quantities. This is not correct because estimates should not
change when reporting operations complete.
Due to this problem estimated quantities were incorrectly calculated in session Print Estimated vs. Actual Material Costs
when using the option 'Correct Estimates Based on Progress'.
These problems were solved in that session itself without identifying and solving the original problem.
After these solutions the Estimated Quantity is still not correctly calculated in this session in case the net quantity of the sub item in the Bill Of
Material is not equal to 1. This factor is not taken into account when calculating the Estimated Quantity to be printed on the report.
The same problem occurs for production orders without routing. The calculation of the estimated quantity is then based on the
Quantity Delivered on the order, without taking the net quantity of the material in the BOM into account.
2. The Estimated Quantity printed on the report is not rounded according to the unit of the material.
3. When the quantity reported complete on an operation exceeds the quantity planned output, the quantity planned output is
changed according to the quantity reported complete, and the Quantity Planned is not changed.
Next, when the order quantity is changed in case the estimated costs are frozen, then the quantity planned is changed as follows:
new quantity planned = ( old quantity planned - cumulative scrap ) * new order quantity / old quantity planned output + cumulative scrap.
This is not correct because the old quantity planned is based on the old order quantity and not on the old quantity planned output.
4. When changing the quantity of a production order without a routing and the costs are already frozen, only the net quantity in table Estimated and Actual Material
Costs was updated. The estimated quantity wasn't changed.
SOLUTION
DESCRIPTION:
1. Reporting quantities complete on operations / orders doesn't result anymore in updating the Net Quantity in table Estimated and Actual Material Costs.
Due to this change the calculation in session Print Estimated vs. Actual Material
Costs of the Estimated Quantity based on the progress is changed back to the original.
2. The Estimated Quantity printed on the report is now rounded to the unit of the sub item.
3. When the order quantity is changed after reporting complete more then was ordered, the calculation of the new quantity planned is based on the old order quantity.
4. Also the Estimated Quantity is changed now when changing the quantity of a production order without a routing.

Solution: 122673
SITUATION IDENTIFIED IN:
"Item Sales Data" (tdisa0101s000)
SITUATION DESCRIPTION:
It is possible to set 'Release to Warehousing' flag to 'No' for Cost, Service, Subcontracting and Equipment items, even if
sales order lines exist for that item, for which shipment is not confirmed or Release to Invoicing is not done.
SOLUTION DESCRIPTION:
Now it is not possible to set 'Release to Warehousing' flag to 'NO' if :
1. Shipment for the sales order line for the item is not yet confirmed OR
2. Invoice is not yet processed for the sales order.
Similarly it is not possible to set 'Release to Warehousing', for Cost, Service, Subcontracting and Equipment items, to 'YES'
from 'NO', if at lease one sales order line is already created for the item.

Solution: 122793
SITUATION IDENTIFIED IN:
"Inventory Receipt Transaction Consumptions" (whina1514m000)
SITUATION DESCRIPTION:
When confirming a shipment a financial integration transaction of type 'issue' is created. This transaction will debit the
'Interim delivery' account. At the moment the invoice is posted a financial integration transaction of type 'COGS' is created.
This transaction will credit the 'Interim delivery' account. Both transactions are created in two separate processes and due
rounding it can happen that the 'issue' amount is unequal to the 'COGS' amount.
A side aspect of this rounding issue is that the MAUC value which is displayed in session whwmd2515m000 "Inventory by
Item and Warehouse" is updated incorrectly.
COGS = Cost Of Goods Sold
MAUC = Moving Average Unit Cost
SOLUTION
DESCRIPTION:
The rounding of the calculated issue amounts has been changed. This will prevent the 'issue' amount being different from
the 'COGS' amount and prevent the MAUC value from being updated incorrectly.

Solution: 122924
SITUATION IDENTIFIED IN:
"Cancel Production Orders" (tisfc0203m000)
SITUATION DESCRIPTION:
A delivery for a production order has been completed via "Report orders completed" (tisfc0120s000) and later a negative
delivery is done to back out the delivery in "Report orders completed" (tisfc0120s000). Even though no materials/hours are
posted to the production order, the production order cannot be cancelled.
On canceling the production order the message "Warehouse order line %/% with order origin '%' has not been deleted because of status" will appear.
When the components are not balanced, the production order was deleted, but a remaining line in warehousing existed.
SOLUTION
DESCRIPTION:
Now all order lines for the end item are taken into account. The number of main items, issued to shop floor, is compared
to the quantity put away back in the warehouse. If these are equal, the order lines are balanced against each other. In that case canceling is allowed.
If the components are not balanced, it is not possible to cancel the production order. Now the message "Warehouse order line %/%
with order origin '%' has not been deleted because of status" is returned.

Solution: 122925
SITUATION IDENTIFIED IN:
"Check and print hours transactions" (tphrs1410m000)
SITUATION DESCRIPTION:
When printing the report with "Check all employees" = "Yes", the hours available and days per week were printing as 0
for some employees.
Also in B40_c : when checking to see if the number of hours booked equaled the number of hours available, not all
employers were being taken into account, only those within the selection criteria. This could give a message "Check
Incorrect" even though hours were booked correctly.
The report should only display booked hours against those employers in the selection criteria but should check against all
employers for the purpose of the calculation.
SOLUTION DESCRIPTION:
The hours available and days per week are now always printed.
Now all employers are checked when calculating number of hours booked.

Solution: 123019
SITUATION IDENTIFIED IN:
"Purchase Budget Details Lines" (tpptc4520m000)
SITUATION DESCRIPTION:
This is a very technical problem. The project data was not always available because the query extend was not used. Instead
of the query extend separate query's were used.
SOLUTION DESCRIPTION:
Query extend implemented and the separate query's were not necessary anymore.

Solution: 123190
SITUATION IDENTIFIED IN:
"Run Global SRP" (tssoc2260m000)
SITUATION DESCRIPTION:
When a Service Order is linked to a configuration that only has an engineer linked to an object and not one for the
configuration itself, then when Global SRP is run, the engineer from the Object is not defaulted to the Service Order.
This occurs when the Parameter settings are as follows:
Allocate Engineers during Global SRP = YES
Detailed Planning Method = By Service Order
SOLUTION DESCRIPTION:
With the following parameter settings:
Allocate Engineers during Global SRP = YES
Detailed Planning Method = By Service Order
When Global SRP is run then an engineer is firstly obtained from the object and if not filled then the engineer from the
configuration will be taken and defaulted to the Service Order.

Solution: 123269
SITUATION IDENTIFIED IN:
"tipcs3540m000" (General Actual Project Cost)
"tipcs3140s000" (General Actual Project Costs)
SITUATION DESCRIPTION:
When a journal voucher is maintained in tfgld1103s000 "Journal vouchers" started via tfgld1101m000 "Transactions" and a
ledger account is used with integration indicator "PCS Project", the amounts for general actual project costs ( in
tipcs3140s000 ) are zero when using the "Rotate Currency" button. This happens when the amount is split over more then
one record on the same or another project, in combination with an independent currency system ( as defined in
tcemm1570m000 "Companies").
The same problem occurs when entering General Actual Project Costs via purchase invoices (tfacp1110s000).
SOLUTION
DESCRIPTION:
Now the amounts for general actual project costs ( tipcs3140s000 ) are correctly calculated and showed when using the
"Rotate currency" button.

Solution: 123275
SITUATION IDENTIFIED IN:
"Inventory-Inspection Data" (whinh3122s000) (Via whinh3522m000)
SITUATION DESCRIPTION:
Inventory data in inventory structure (whinr1550m000) goes wrong if an item is purchased in a storage unit and
received in same storage unit (without package definition) but rejected in the inventory unit.
Example:
For an item, inventory unit = pcs
Conversion factor is defined for this item with another storage unit pc1.
Conversion factor between pcs and pc1 is 1.
In a purchase order 25 pcs and 30 pc1 are purchased in 2 lines, both with inspection.
Both lines are received (without package definition) and confirmed.
In approvals, only the line in which 30 pc1 is purchased is selected and in that 0 pc1 is approved and 30 pcs (note it is pcs) is
rejected.
When whinr150 is checked it would be wrong.
SOLUTION DESCRIPTION:
Now the inventory data in inventory structure (whinr1550m000) is updated correctly even if purchased in a storage unit and
rejected in inventory unit.

Solution: 123294
SITUATION IDENTIFIED IN:
"CI Process" (tccri7203m000)
SITUATION DESCRIPTION:
After the internal conversion the Trial Balance is not correct. This is due to the fact that the currency differences that
were generated with the sessions "Write Off Currency Differences" (tfacp2240m000 and tfacr2250m000) are not converted
correctly.
SOLUTION DESCRIPTION:
The correction program included in this solution repairs the records of the Finalized Transactions. After that the Trial Balance
is correct.

Solution: 123314
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When Creating multiple lines for the same item on a sales order, the user receives the error "item group not found" and is
unable to save the line. They must exit out and input the line again.
SOLUTION DESCRIPTION:
Creating Multiple Lines is Possible.

Solution: 123370
SITUATION IDENTIFIED IN:
"International Bank Account Number" (IBAN)
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
In order to implement the desired changes regarding International Bank Account Number (IBAN), we have implemented the
IBAN related changes within the Baan sessions in 2 phases. The table changes and changes to the forms, in order to enter
the IBAN into Baan, have been delivered with the solutions 119866 and 121580 (phase 1). The display sessions and some
reports that show the entered IBAN code still have not come available.
SOLUTION
DESCRIPTION:
With this current solution (the 2nd phase) the display sessions and some reports that show the entered IBAN code
have come available, as well as additional help texts to support the use of the new fields.
Furthermore, a check has been built in, to verify the existence of the entered IBAN code.
This means that you can now change the IBAN in all sessions where you can enter it and the IBAN code has been added to the summary reports where
the bank account is printed. Furthermore, an enhancement for B40_c has been added to see the name of the chosen report in the session 'Maintain
Payment Methods' (tfcmg0140m000). Extra messages will warn if an entered Report Group does not exist for that session. In that same session 'Maintain Payment Methods' (tfcmg0140m000), an extra field has been added, where you can switch on/off the use of IBAN per payment method. It is, however, only accessible, when both the chosen
'Report Group' and the additional 'Report
Group Report', are prepared for the use of IBAN and when the field 'Bank account required' has been set to 'yes'.
Be aware that, from this moment on, although the IBAN functionality has been implemented, IT IS ONLY POSSIBLE TO USE THE IBAN
FUNCTIONALITY IN BAAN FOR THE CHOSEN PAYMENT REPORTS THAT HAVE BEEN ADAPTED TO USE IBAN. Individually adapted
reports will follow from time to time. You can contact your support office if you have questions about (to be) adapted reports.
Solution: 123382
SITUATION IDENTIFIED IN:
"Import Journal Voucher Batches by ID Number" (tfgld2215m000)
SITUATION DESCRIPTION:
The journal import status report is not sorted by document number and line number
SOLUTION DESCRIPTION:
Now the report sorted by the document number and line number considering those fields as numeric fields.

Solution: 123456
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When receiving an ASN with multiple lines for the same direct delivery purchase order position (multiple lots; partial
shipments), only the first line is automatically linked to the purchase receipt. The additional lines of the ASN (for the same
purchase order position) are being saved in the system, but are not updating the purchase order. Only by backordering the
rest of the purchase order (processing the delivered purchase order), the next line can be received. This process needs to be
repeated for every line to receive the complete ASN.
SOLUTION
DESCRIPTION:
Each line on an incoming ASN was considered as a final receipt (when manually receiving or via EDI). This has been changed. Now, only the last line within
the ASN (for one ASN header) for a specific purchase order position is considered as the final receipt. Shipped quantities are
cumulated for those lines. In case the ordered quantity is not reached, then the normal backorder procedure for direct delivery purchase orders and ASNs (see problem description) applies. Note, prior to this fix, the "Remarks on Copied Messages" report gave a warning on each line that was
linked to a purchase order position. Now, there is only one remark, similarly as in the manual receipt process: " # Direct Delivery Line(s) has/have been received."

Solution: 123464
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000)
SITUATION DESCRIPTION:
Baan delivers PMC solutions for Baan IV c4 only in the languages Dutch, English, German and French. For BaanERP 5.0 b and
5.0 c, PMC solutions are delivered only in Dutch, English and German. When you use a so-called B-Language (a language for
which components are not delivered in the individual PMC solutions), installing a PMC solution wasn't always beneficial.
E.g. when a form and an object were changed to solve a problem, after installation of the solution you used the new object
(because an object is language-independent), but you still used the 'old' form, because it was not updated in your
B-Language.
By installing the Translation Service Packs, the B-Language components were up to date again. However, installing Translation Service
Packs could cause other problems, because components of installed newer solutions could be overwritten with older ones.
SOLUTION DESCRIPTION:
The Advanced B-Language Support provides for functionality to keep your B-Language
components on the same level as the components of the languages, which are delivered in the PMC solutions. During
installation of the PMC solution, also the B-Language components are updated automatically. Language-dependent parts of
the components are retained as much as possible.
To prevent newer components being overwritten by older ones a new format for Translation Service Packs has been defined. The software to
handle this new format will be made available under solution 127841.
For more information on the new functionality and how to activate it, please download and read the following document:
For Baan IV c4:
ftp://ftp.support.baan.com/updates/Documents/123464b40.doc
(This linked document was updated on 08/27/2002)
For BaanERP 5.0 b and 5.0 c:
ftp://ftp.support.baan.com/updates/Documents/123464b50.doc
(This linked document was updated on 08/27/2002)

Solution: 123508
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Simulate Orders does not uncheck the Item Ordering Data netchange flag/date.
SOLUTION DESCRIPTION:
When running Simulate Orders the netchange flag/date of the Item Ordering Data is used and will be reset after the order
planning.

Solution: 123527
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" (whinh4201m000)
SITUATION DESCRIPTION:
Too many components are advised if an outbound advice is generated twice for the same sales order.
This problem doesn't occur if the outbound advice is generated via "Specific" of session "Outbound Order Lines"
(whinh2520m000).
Example:
Main Item : MAIN
Component item : COMP1 Inventory 20 pcs
Component item : COMP2 Inventory 1 pcs
Sales order for 2 items MAIN; released to warehousing
When the first advice is generated, it advises 1 "COMP1" and 1 "COMP2".
This is correct because the advice is made based on the number of complete main items that can be delivered.
When the advice for the same sales order is generated again, it additionally advises 1 "COMP1".
This is wrong because now in total 2 "COMP1" and 1 "COMP2" are advised.
When trying to confirm the shipment the errormessage whwmds0196 "BOM components partially staged." is given.
SOLUTION DESCRIPTION:
This situation is corrected.
In case of "issue components" an outbound advice will always take the number of complete main items that can be delivered
into account. The second time no additional advice will be generated.

Solution: 123556
SITUATION IDENTIFIED IN:
"Flexible Printing" (tdsmi2410m100)
SITUATION DESCRIPTION:
In the session flexible printing (tdsmi2410m100) only the role 'General' for a business partner is selected.
SOLUTION DESCRIPTION:
The selection section is changed so that all available roles are selected and printed.

Solution: 123560
SITUATION IDENTIFIED IN:
"Global Update of Inventory Parameters" (whina2200m000)
SITUATION DESCRIPTION:
Sometimes safety stock is not set to the desired value instead the re-order point is taken.
SOLUTION DESCRIPTION:
The re-order point is taken only in case of order system "SIC".

Solution: 123570
SITUATION IDENTIFIED IN:
"Close Production Order" (ticst0201m000)
SITUATION DESCRIPTION:
After hours are processed via Process Hours Accounting (tihra1210m000) the history table for hours (tihra350) is filled with
the (processed) hour information. When a production order is closed via session Close Production Order (ticst0201m000) this
history record is updated. Because the Close Production Order session could not find the history record, it inserts a new
history record with the corrections. For the reporting session that is using this history table, it is not a problem because
these sessions are aggregating the history records (old and new inserted one).
SOLUTION
DESCRIPTION:
When the production order is closed via session Close Production Order ticst0201m000 the history record is updated.

Solution: 123590
SITUATION IDENTIFIED IN:
"Print Production-order documents" (tisfc0408m000)
SITUATION DESCRIPTION:
When modifying the start date and /or finish date of a production order and selecting the option 'Modified', all the
selected documents are not getting printed. Currently the material related documents like Material List, Material Issue
Note and Assembly Material Issue Note etc are only getting printed. Where as all the other documents like Routing Sheet,
Covering Note and Operation Note etc are not reprinted.
SOLUTION DESCRIPTION:
After changing the dates of a Production order, and after selecting the Option MODIFIED in Print Production order Documents, system prints all the documents user selects instead of printing the Documents related to Materials only.

Solution: 123601
SITUATION IDENTIFIED IN:
"Vendor Rating Parameters" (tdpur0100s800)
SITUATION DESCRIPTION:
Error 100 occurs if the Period Table code is changed in the Vendor rating Parameters and a Partial Update of Vendor Rating
is done.
SOLUTION DESCRIPTION:
Now, the user is prompted to run a Full Update of Vendor Rating when the Period table code is changed.

Solution: 123606
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
Can not import MultiByte fb file.
SOLUTION DESCRIPTION:
This is due to session tfcmg5202m000 does not use MB process and the file buffer is also only for single byte.

Solution: 123607
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
"Cost of Goods sold cannot be determined" error when trying to confirm shipments for components.
SOLUTION DESCRIPTION:
In case of 'issue to components' the delivered quantity must be corrected by the actual ratio of the component.
SOLUTION 123607 PLEASE ALSO INSTALL SOLUTION 128772.
Solution: 123610
SITUATION IDENTIFIED IN:
"Print Supplier Aging Summary" (tfacp3425m000)
SITUATION DESCRIPTION:
1. Change functionality : add "Selection by" field.
2. When running session "Print Supplier Aging Summary - tfacp3425" and only changing the "As Of" field, this field is not
taken in account.
SOLUTION DESCRIPTION:
1. Functionality changed by adding the "Selection by" field.
2. When running session "Print Supplier Aging Summary - tfacp3425" and only changing the "As Of" field this field is now
taken in account.

Solution: 123615
SITUATION IDENTIFIED IN:
"Chart of Item/Channel Planning" (cprmp2701m000)
SITUATION DESCRIPTION:
Cash Flow chart figures do not include forecast.
SOLUTION DESCRIPTION:
Unconsumed Demand forecast after forecast time fence is included in Cashflow, Cost & Cashflow and Demand, Supply &
Inventory Chart.
Valuation of cashflow is depending on parameter 'Dependent Demand Forecast' in Plan Item data (cprpd1101s000). When
Dependent Demand Forecast is checked, both dependent and independent demand is included in the forecast and Cashflow
valuation is against material cost. When Dependent Demand Forecast in not checked the forecast only consists of
independent demand and the Cashflow valuation is against sales price.

Solution: 123654
SITUATION IDENTIFIED IN:
"Calculate Commission/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
Commission invoices cannot be posted to finance. This occurs in any multi site environment, where the sales order and
commissions are processed in the logistic company and the invoices are to be posted to the financial company. This
particular situation occurs when the commission transaction type, defined in the parameters, has a last used number in the
logistic company, which has been already used in the financial company.
SOLUTION
DESCRIPTION:
The financial company will be read before the new invoice number is determined. This will be done before performing the
function where the record is printed and updated.

Solution: 123657
SITUATION IDENTIFIED IN:
"Specifications, Delivered Not Yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
The doesn't print Goods delivered not yet invoiced for service, & also it doesn't show the status of the orders.
SOLUTION DESCRIPTION:
Now It shows the statuses of the Orders, & it also prints Service Orders now.

Solution: 123682
SITUATION IDENTIFIED IN:
"Installment Orders" (tdsls4506m000)
SITUATION DESCRIPTION:
When a settlement installment is made the project number field for this installment order is not filled.
SOLUTION DESCRIPTION:
For the filling of this field the value of parameter "Link Installments to Project" (in session Sales Order Parameters,
tdsls0100s400) is important.
Parameter is yes: all lines of the sales order which is invoiced with installments have the same projectnumber. Furthermore
the projectnumber field for all installment lines is filled with this projectnumber. And now also the settlements.
Parameter is no: lines of the sales order which is invoiced with installments can have several projectnumbers. The
projectnumber field for all installment lines remains empty.

Solution: 123696
SITUATION IDENTIFIED IN:
"Service Contracts" (tsctm3500m000)
SITUATION DESCRIPTION:
On session Service Contracts (tsclm3500m000), when using the view/filter option, to filter occurrences for the Business
Partner name, together with a filter command such as : "=", "<", ">", "Like", "Not Like", "Between", "not in Between", etc.
the data-set that comes as a result is not accurate. Not all the occurrences are shown.
SOLUTION DESCRIPTION:
Now when using view/filter option, to find a specific Service contract using the field "Business Partner" and a search
command, the result data-set is accurate. While retrieving the records, the same search path will be used as the
search path which is used in order to display the Name on the form.

Solution: 123754
SITUATION IDENTIFIED IN:
"Process Import/Export Statistics" (tccom7271m000)
SITUATION DESCRIPTION:
Subsequent receipts of goods are not reported in session "tccom7271m000" (Process Import/Export Statistics).
This happens when a partial receipt of a purchase order line is confirmed and this receipt is reported in session "Process
Import/Export Statistics" (tccom7271m000).
Subsequent receipts of this purchase order line will not be reported, because the "Import/Export Statistics" line already has
the status "processed".
SOLUTION DESCRIPTION:
In case the line in "Import/Export Statistics" has the status "processed" a new line is created.
All receipts are reported in session "Process Import/Export Statistics" (tccom7271m000).

Solution: 123762
SITUATION IDENTIFIED IN:
"Print check master" (tfcmg2415m000)
SITUATION DESCRIPTION:
When linking support application to the user DEM desktop, for some sessions print button was disabled if the session has
print and display authorization.
SOLUTION DESCRIPTION:
This problem has been sorted out .The print button is being enabled now.

Solution: 123780
SITUATION IDENTIFIED IN:
"(Re)calculate price" (tsctm1201s000)
SITUATION DESCRIPTION:
When selecting a contract with the status free, in session "Service Contracts" (tsctm3500m000), select "Specific/Contract
terms" (tsctm1100m000), after this select a service type and then, "Specific/Recalculate price" (tsctm1201s000), the
following situations occur:
A.- When filling in the selection criteria, the field "Coverage term to"is defaulted with nine 9s. Then, when this field is passed, using tab again,
the following error message appears,"Not allowed" (ttstps0108); in order to continue, at least one 9 of that defaulted value, must be deleted.
B.- When activating the (Re)calculate button, two error messages pop-up:

Unknown formfield 'cost. term.f' Unknown formfield 'cost. term.t'
However these two issues described above, the outcome of the session is correct.
SOLUTION
DESCRIPTION:
Some changes were applied to the form, the initial value for the field "Coverage term to"is defaulted with eight 9s and the
form was re-compiled. Now, no pop-up messages appear.

Solution: 123782
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
1. The 'Delete Order Data if Received Completely' parameter is By Order in the "Purchase Order Parameters"
(tdpur0100s400).
2. There are two purchase order lines with delivery date 21-12-2001 and 25-12-2001 respectively.
3. The whole order is matched and approved in Finance and order is processed with "Process Delivered Purchase Orders"
(tdpur4223m000).
4. Now if the 'Delete up to' filed is filled as 23-12-2001, the system deletes the whole order. This should not happen and it
should stop since the Delivery Date of the second line is after the 'Delete up to' date.
SOLUTION DESCRIPTION:
When the parameter 'Delete Order Data if Received Completely' is By Order, the Delivery Date would be checked on all the
lines and the whole order would not be deleted even if one lines does not have the delivery date with in the 'Delete up to
date'.

Solution: 123788
SITUATION IDENTIFIED IN:
"Print BaanERP Project Financial Reconciliation" (tcfin2400m000)
SITUATION DESCRIPTION:
In case of an Integration Transaction with debit and credit in two different finance companies, the records are printed with
zero-amounts. Also no Finalization Run Number and Fiscal Year is printed. Report is "BaanProject Financial
Reconciliation".
SOLUTION DESCRIPTION:
Problem is solved. The document details are correctly retrieved now.

Solution: 123791
SITUATION IDENTIFIED IN:
"Process Hours Accounting" (tihra1210m000)
SITUATION DESCRIPTION:
The year, week and day are not updated correctly based on the current date in the session when the session is run in the job
mode. The session always displays the year, week and day when it was added to the job and does not get updated as per the
current date in the session when run in job mode.
SOLUTION
DESCRIPTION:
With changes made in the script, the year, week and day are updated
correctly based on the current date in the session when the session is run in job mode.

Solution: 123796
SITUATION IDENTIFIED IN:
"Print history" (tpppc241401000)
SITUATION DESCRIPTION:
Run the session Print history and if the sequence number is greater than 9999 then "####" is printed on the report and a lot
of Format Overflow errors on the BaaN Server.
SOLUTION DESCRIPTION:
Field sequence number's domain has been changed from 4 digits one to a 6 digits one.

Solution: 123797

SITUATION IDENTIFIED IN:
"Patches" (ttpmc1501m000)
SITUATION DESCRIPTION:
In the session "Patches" (ttpmc1501m000) the check on present dependencies during a delete action was not correct. It could
be that a patch couldn't be deleted, which was allowed to be deleted and also the other way around.
SOLUTION DESCRIPTION:
Now the correct check is done: when a co-requisite dependency to a released patch is present, the patch cannot be deleted.
When no co-requisite dependency is present and the status of the patch allows it, the patch can be deleted.

Solution: 123799
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When the project field is changed in Purchase order lines, Ledger account is not defaulted in some cases.
Problem occurs mainly when there is an Item, Project for which ledger account is already filled and the project field is
modified later. In this case the new ledger account is not defaulted.
SOLUTION DESCRIPTION:
Now when there is a change in Item or Project in Purchase Order Line, the search is done and corresponding ledger account
and dimensions are defaulted.

Solution: 123801
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
Integration transaction "Warehousing(Valuation)/Value Correction" is not generated, If "Process Inventory Variance
(whina1200m000)" is executed for the production order of 0 quantity. But if the session "Process Inventory Variance
(whina1200m000)" is run for the second time, the transaction is posted to finance.
SOLUTION
DESCRIPTION:
The posting to financing would be done in single step. The user need not run the session again to make the
"Warehousing(Valuation)/Value Correction" transaction to be posted to Finance.

Solution: 123802
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m00)
SITUATION DESCRIPTION:
During posting of Integration Transactions, when Intergroup Transaction are created, the Intergroup ledger account is filled
incorrectly with a dimension code.
SOLUTION DESCRIPTION:
Problem is solved. The intergroup transaction will not have any Dimensions on it anymore.

Solution: 123810
SITUATION IDENTIFIED IN:
"Print Settled Advance Payment Request Lines" (tppin0411m000)
SITUATION DESCRIPTION:
The number of Settled Advance Payment Request Lines can only go up to 99. This is too small in many cases.
SOLUTION DESCRIPTION:
The number is increased to 9999. This should be sufficient.
Because the number is only used in a small number of sessions and only in Baan Project this could be done.

Solution: 123816
SITUATION IDENTIFIED IN:
"Generate Planned PRP Orders" (tppss6200m000)
SITUATION DESCRIPTION:
In case we have defined an item of Item Type 'Purchased' in Item Ordering Data (tcibd2100s000) with an Order Policy 'To
Order' and the Order System 'Planned', and the Project Order System is set to 'PRP' the system creates a Planned
Warehouse Order in tppss6200m000 instead of a Planned Purchase Order.
SOLUTION
DESCRIPTION:
If the available stock is lower than zero or equal to zero, no Planned PRP Warehouse Order is generated but a Planned PRP Purchase Order. This is
done if the parameter "Inventory Check for Warehouse Deliveries is Yes.
For Anonymous items if the flag Inventory Check for Warehouse Deliveries is Yes then more PRP Warehouse orders can be
generated dependent on the available stock in different warehouse. If the flag = No then only one PRP Warehouse order is
generated with the total required quantity
.
For On Order items always the available stock is consumed and a PRP warehouse order is generated for the available
stock. The rest quantity will result in a PRP purchase order. So the, On Order items are not influenced by the flag Inventory Check
for Warehouse Deliveries.

Solution: 123819
SITUATION IDENTIFIED IN:
"Inventory Receipt Transactions" (whina1512m000)
SITUATION DESCRIPTION:
In case the valuation method is MAUC the issue amount is calculated based on the MAUC valid at the moment of the
transaction. In case backdating is involved this can result in a wrong calculation of the new MAUC value.
This problem can occur in the following two situations:
1) When there is more issued than financially registered at the moment of the transaction date
2) In case processed variances already do exist between the transaction and creation date of the backdated issue.
SOLUTION DESCRIPTION:
In case the valuation method is MAUC the issue amount will be calculated based on the current MAUC. This is the MAUC
valid at the moment of the creation date. This will prevent wrong MAUC value calculation in case of backdating and will
also prevent that the MAUC value does change due the issue.

Solution: 123823
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
When zooming from 'Project segment' of 'item' field, the system zooms to session 'General Projects'. However, if zooming from
'Project' field, the system zooms to 'Baan Projects' even if the project in the 'item-project segment' is a PCS project.
SOLUTION DESCRIPTION:
The project entered in the 'Project segment' of item is defaulted into the 'Project' field.
Now, if the project entered/defaulted in the 'Project' field is a 'Baan Project' then the zoom from the 'Project' field takes the
user to 'Baan Projects' session. However, if the project is not a 'Baan Project' or if no project has been entered, then the user
is taken to the 'General Projects' session.

Solution: 123828
SITUATION IDENTIFIED IN:
"Create German Bank order for diskette" (tfcmg1261s000)
SITUATION DESCRIPTION:
Field 'senders.ident' is only 5 characters long. This filed has to be 6 characters long.
SOLUTION DESCRIPTION:
Field 'senders.ident' has 6 characters, the same number than session tfcmg1260m000.
The old domain (tcmcs.str5 = 5 characters) has been modified by tcmcs.str6 (6 characters).

Solution: 123829
SITUATION IDENTIFIED IN:
"Correct Total Approved Quantity in Order approvals" (tdcor0003m000)
SITUATION DESCRIPTION:
It is not possible to match and approve the Purchase invoice for the Consignment Payment Order in the finance side due to
the corrupted data.
SOLUTION DESCRIPTION:
The tables responsible for the corruption have been corrected and the invoice can be matched and approved now.

Solution: 123841
SITUATION IDENTIFIED IN:
"TF" ()
SITUATION DESCRIPTION:
A Cost Invoice transaction (Purchase Invoice, no matching) has been created. A run has been created to finalize the invoice.
The following error occurred twice:
"Unable to start application server;error 3505"
After clicking "OK" twice, another error message came: "Update method 'Finalization' not executed; see error log file".
Finalization Status report displayed:
Finalization Run Status = Finalized successfully
Batch Status = Errors
Status: Errors in Finalization
SOLUTION DESCRIPTION:
If on the client (e.g. desktop) multiple versions of BW are installed, the parallel processing functionality (multiple
bshell) can take the wrong BW version and it is not guaranteed that server applications will work as they should work.
Because BW on the client is of other version than BW on the server.
The solution consists of the calling of the right BW version.

Solution: 123843
SITUATION IDENTIFIED IN:
"Print Calendars" (tcccp0420m000)
SITUATION DESCRIPTION:
Printing a range of calendars with the option "derived from lines" checked results in double (or more) lines.
(a range of N calendars results in printing every line N times)
SOLUTION DESCRIPTION:
When printing a range of calendars with the option "derived from lines" checked, lines are printed only once per calendar

Solution: 123849
SITUATION IDENTIFIED IN:
"Print Posting Report" (tpppc4402m000)
SITUATION DESCRIPTION:
The field sequence number is not aligned correctly in the report (Print Posting Report)
SOLUTION DESCRIPTION:
The field sequence number is not aligned correctly.
The above problem is solved.
Now the field sequence number is aligned properly in the report (Print Posting Report).

Solution: 123850
SITUATION IDENTIFIED IN:
"Transfer Planned PRP Purchase Orders" (tppss6230m000)
SITUATION DESCRIPTION:
When several Planned PRP Purchase Orders with all the key fields having the same value are transferred, system creates
different RFQs even though the values of the key fields are same for the transferred PRP Orders.
SOLUTION DESCRIPTION:
Now, changes are made such that, only when the purchase offices are different, then different RFQs are created for the
Planned PRP Orders.

Solution: 123851
SITUATION IDENTIFIED IN:
"Convert Requisition Lines to RFQ/PO" (tdpur2201m000)
SITUATION DESCRIPTION:
The help text for the Consolidation by BO check box for the conversion type RFQ in the session says, conversion in to
Purchase Order. It has to be RFQ.
SOLUTION DESCRIPTION:
The help text has been modified so that it would read as conversion to RFQ rather than Purchase Order.

Solution: 123852
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
When many invoices are printed without leaving the session, the session sometimes picks up the "Customer order no." for the
previous invoice and prints in the current invoice printed.
SOLUTION DESCRIPTION:
Now the invoices are printed correctly.

Solution: 123854
SITUATION IDENTIFIED IN:
"Generate invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
It can happen that a batch is generated with session tfacp2290m000 (generate selfbilled invoices) and that that batch can not
be finalized. The user will get the message "batch header record missing". If you look with table maintenance (ttaad4500) to
the related tables then indeed a record is missing in tfgld101, whereas all the other tables are populated correctly.
SOLUTION
DESCRIPTION:
A batch header record has to be written once in the selfbilling batch as the transaction type is the same for all documents.

Because of this a certain DLL (dynamic link library) is called to create this record and for performance reasons the creation of a batch header record is only done once.
However when (because of the locking of a table) the process gets into its retry.point() this record will because of this
mechanism never be created again. Now it is also checked whether a db.retry.hit has occurred for determining whether this
batch header record still needs to be created or not.

Solution: 123859
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
If an advance payment request of one currency is processed with an installment invoice using a different currency, the
calculation of the settled amount is not correct. The system adds amounts while they have different currencies.
SOLUTION DESCRIPTION:
The amount is now calculated in the correct currency. Partial settlements are stored in the currency of the advance. When the
rest of the advance is settled, these partial settlements are also taken into account.

Solution: 123867
SITUATION IDENTIFIED IN:
"Initialize, Roll and Update Scenario's" (cprpd4200m000)
SITUATION DESCRIPTION:
After Initialize, Roll and Update Scenario's, Special Demand is removed from the Channel Master Plan.
Special Demand for the Channel Master Plan must be manually restored by pressing 'Update' in session Channel Master
Plan (cpdsp5130m000).
SOLUTION DESCRIPTION:
Initialize, Roll and Update Scenario's loads the Special demand for Channel Items.

Solution: 123885
SITUATION IDENTIFIED IN:
"Release to Invoicing" (tdsls4501m130)
SITUATION DESCRIPTION:
When entering a delivered quantity (tdsls401.dqua) = zero for a Cost Item on a Sales Order of type "Return Order" in
session "Release to Invoicing" (tdsls4501m130), the line could not be processed any further in session "Process Delivered
Sales Orders" (tdsls4223m000).
SOLUTION
DESCRIPTION:
From now on Sales Order Lines of type
"Return Order", with "delivered quantity" = zero for Cost Items,
can be processed in "Process Delivered Sales Orders" (tdsls4223m000).

Solution: 123887
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
The 'Reference' in the anticipated receipt document is not shown in the reconciliation document.
SOLUTION DESCRIPTION:
Now, 'reference' in the reconciliation document is filled with the 'reference' in the anticipated document, if 'reference' is left
empty while reconciliation.

Solution: 123892
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 which 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: 123905
SITUATION IDENTIFIED IN:
"Selected Calls" (tsclm8599s000)
SITUATION DESCRIPTION:
in B50c
Wrong translation of label tsclm.st.trans "Transferred". Now it is "Overgeboekt", but it should be "Overgezet"
This should be in line with call status : "Transferred" -> "Overgezet"
in B50b
Wrong translation of lable tsclm.st.trans "Transferred". Now it is "geactualiseerd", but it should be "Overgezet"
This should be in line with call status : "Transferred" -> "Overgezet"
SOLUTION DESCRIPTION:
The two labels were properly translated.

Solution: 123911
SITUATION IDENTIFIED IN:
"Copy Purchase Contracts" (tdpur3801m000)
SITUATION DESCRIPTION:
When copying a purchase contract to another contract, the messages "Item xxxxx already included in contract xxxxx" and
"Price group xxxx already included in contract xxxxx" are displayed only for the first contract line in the source contract
being copied.
SOLUTION
DESCRIPTION:
Now along with the message, the question "Do you want to see next message?
Yes / No" will be asked. If the user chooses, 'Yes' further messages will be shown for the rest of
applicable contract lines of the source contract. If the user chooses
'No',
further messages will not be shown.

Solution: 123913
SITUATION IDENTIFIED IN:
"Copy Bill of Material" (tibom1216m000)
SITUATION DESCRIPTION:
In session Copy Bill of Material, when the Partial Item number is entered in the Source Item or the Target Item fields and
zooms to the Item Production data session, system is not zooming to the nearest Item.
SOLUTION DESCRIPTION:
System will zoom to the nearest Item if the item does not exist in the Item production data.

Solution: 123916
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40b
123580
Defects solved in B40c
123580, 123647
Defects solved in B50b
123381, 123647
Defect solved in 71a
117901, 123381, 123647
Descriptions:
- Defect 117901 Don't save record before form command.
- Defect 123381 Resize form correct after using scrollmouse
- Defect 123580 Zoom on field during insert not possible
- Defect 123647 New argument for get.last.message code was not optional
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 123918
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
When printing a Purchase Order an incorrect Tax Amount was calculated. This happens only in case of a "Gross over
Hundred" situation. This Tax -scenario can be entered in Tax Codes by Country (tcmcs0536m000).
SOLUTION DESCRIPTION:
The "Gross over Hundred" situation is now calculated correct. Printing a Purchase Order with taxes based on the "Gross over
Hundred" situation are now printed correctly.

Solution: 123919
SITUATION IDENTIFIED IN:
"Composed Payments" (tfcmg1503m000)
SITUATION DESCRIPTION:
Factoring bank is updated for the already composed, paid and posted invoices.
SOLUTION DESCRIPTION:
Now, the "pay-to bank" is filled always with "supplier bank" specified in payment advice instead of "factoring bank" for any
invoice.

Solution: 123921
SITUATION IDENTIFIED IN:
"Copy Tools Solutions to other Languages" (ttpmc3290m000)
SITUATION DESCRIPTION:
The Session "Copy Tools Solutions to other Languages" did not compile report objects.
SOLUTION DESCRIPTION:
The current package combination is passed to the function, which executes the compilation. As a result the compilation of
report objects is done correctly.

Solution: 123925
SITUATION IDENTIFIED IN:
"text editing" (tttxt2230s000)
SITUATION DESCRIPTION:
Change language not possible without entering text in current language. Event not possible if text is present in the other
language.
SOLUTION DESCRIPTION:
The previous fix introduced a message that entering of text is mandatory before switching to an other language. Now this fix
is changed so that it will be possible to switch to other language without entering any data.

Solution: 123927
SITUATION IDENTIFIED IN:
"Aggregate Estimated Capacity to Project" (tipcs4201m000)
SITUATION DESCRIPTION:
Error message display is not correct in Report pcs420101000
in session tipcs4201m000.
SOLUTION DESCRIPTION:
Display Process is not suitable for Multibyte language, and the buffer size is not enough for English as well.

Solution: 123941
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Confirming the receipt of a sales return order with multiple components leads to error 'Costs of Goods sold cannot be
determined'.
SOLUTION DESCRIPTION:
For components the update of sales is executed after the last bomline.

Solution: 123942
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4501m300)
SITUATION DESCRIPTION:
While trying to delete the Purchase Order Lines in the session "Purchase Order Receipts" (tdpur4501m300), the system
puts an un understandable question as "ask enum pur41032".
SOLUTION DESCRIPTION:
The question would be prompted as "The Purchase Order Line is linked to a Sales Order Line. This link will be
disconnected. Continue?"

Solution: 123946
SITUATION IDENTIFIED IN:
"First Free Numbers" (tcmcs0150m000)
SITUATION DESCRIPTION:
It was impossible to enter a "0" for "cache size". As stated in the help, this should be possible.
SOLUTION DESCRIPTION:
Changed the "minimum input length" on the form from "1" to "0"; now it is possible to enter a "0". In this way the session
functionality corresponds to the functionality written in the helptext.

Solution: 123960
SITUATION IDENTIFIED IN:
"Baan Service Scheduler 2.0" (BSS 2.0)
SITUATION DESCRIPTION:
This solution is meant for migrating from BSS 2.0 to BSS 2.1. Several ERP Components are included.
SOLUTION DESCRIPTION:
Before running BSS 2.1 on the iBaan ERP 5.0c Environment, make sure that this solution is installed.

Solution: 123961
SITUATION IDENTIFIED IN:
"Create Payment Orders" (tfcmg1260m000)
SITUATION DESCRIPTION:
Description of the Reason for Payment not printed when the reason is 3 or 4 or 5 in the ABN Bank file.
SOLUTION DESCRIPTION:
Now it is printing in the above mentioned specified condition.

Solution: 123975
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Tax is not recalculated, when changing the Invoice amount, when having a discount on Invoice, specified in the Terms of
Payment.
SOLUTION DESCRIPTION:
When Discount on Invoice is set, Tax and Discount calculations are messed up. The Tax calculation is done on the changed
Invoice amount and the discount calculation is done on the earlier Invoice amount. This has been corrected and now, the
discount calculation is also done on the changed amount itself.

Solution: 123976
SITUATION IDENTIFIED IN:
"Log Message" (ttaadlogmess)
SITUATION DESCRIPTION:
The session tipcs2250m000 has a job (ttaad512) that creates a large number of messages. This cause unnecessary table reads
for session ttaad512.
SOLUTION DESCRIPTION:
Limit number of records read from ttaad512.

Solution: 123988
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
Changing the planned start or planned finish time on the service order header slightly, e.g. 10 seconds, and saving, results in a
resetting of the original date/time, because the time shift is that small that it is rounded off to zero. This error may also
occur when shifting the time e.g. 1 day and 10 seconds. In that case the seconds are being reset to the original ones.
Especially when updating these dates from BSS can result in planning gaps.
SOLUTION DESCRIPTION:
The time shift is now no longer rounded off, planned start and finish date/time are now calculated properly.

Solution: 123997
SITUATION IDENTIFIED IN:
"Confirm planned orders" (cprrp1200m000)
SITUATION DESCRIPTION:
session cprrp1200m000 reports wrong confirmed order values jobmode when DB errors occur.
When a DB error occurs (record is locked), the reporting of the number of confirmed orders is handled wrong. Multiple times
a report line in the job history messages appears:
0 order(s) confirmed successfully.
SOLUTION DESCRIPTION:
Now the message will be given after the actual database update attempt. This implies that when the message appears, the
actual update (and the number of orders that are reported) were successful.
A small disadvantage is that when a record is locked, and the RETRY mechanism exceeds its maximum, the application session
has lost its control, and cannot report anything anymore. The only things you will find is an entry "run time error" in the job
history, and the cause (record is locked) in the database driver logfile.

Solution: 124001
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
In case there is a negative advance payment request and a negative installment is invoiced, the advance amount already
invoiced becomes equal to the installment amount.
The advance is not settled in the correct way.
SOLUTION DESCRIPTION:
If there is a negative advance payment request and it is settled with a negative installment invoice, the system now settles
the correct amounts.

Solution: 124002
SITUATION IDENTIFIED IN:
"Simulate Orders " (cprrp1210m000)
SITUATION DESCRIPTION:
Enterprise Planning is changing planned production orders dates (fixed finish dates/fixed start dates) even when the planned
order was set to firm-planned.
SOLUTION DESCRIPTION:
Firm planned orders are being replanned as part of standard functionality, however when the order is firm planned and
forward, the fixed start date remains fixed. When firm planned and backward, the fixed finish date remains fixed.

Solution: 124015
SITUATION IDENTIFIED IN:
"Sales Quotation Lines" (tdsls1501m000)
SITUATION DESCRIPTION:
When recalculating prices and discounts for sales quotations (session tdsls1501m000), lines with quantity zero are
recalculated as well, giving all kinds of strange results.
Also it is possible to reprice a quotation line using the button "Reprice" on form "Selling" of session "Sales Quotation
Lines" (tdsls1101s000)
SOLUTION DESCRIPTION:
Prices and discounts for lines with zero quantity are not recalculated anymore. Also the button "Reprice" on form "Selling"
of session "Sales Quotation Lines" (tdsls1101s000) is disabled for such a Sales Quotation Line.
Also added the follow functionality as already present for sales order lines (see solution 118717 for sales and purchase
orders):
- Quantity of manually entered lines is also taken for cumulating price
- While Cumulating Prices manual entered price are also overwritten.
- Manually entered price should not be overwritten when reprice the entire order

Solution: 124020
SITUATION IDENTIFIED IN:
"Storage List" (whinh2515m100)
SITUATION DESCRIPTION:
After executing the specific option 'Confirm Current Mission' or 'Confirm Current Run', if Find icon is used, always first
record is displayed.
SOLUTION DESCRIPTION:
Now the correct record is displayed if 'Find' is used even after executing the Specific options 'Confirm Current Mission' or
'Confirm Current Run'.

Solution: 124025
SITUATION IDENTIFIED IN:
"Print Item Inventory" (tcibd1400m000)
SITUATION DESCRIPTION:
Printed report (or displayed to screen) shows the "Average Purchase Price" twice at the bottom of the report plus two other
bracketed fields without any data.
Navigation to the problem:
1) Run program on tcibd0501m000
2) Highlight any item, then select "specific" to "Item Inventory"
3) Select the "Print" icon then select the "Print" button on session "tcibd1400m000"
4) Input "D66" or input a printer...
5) view the last 4 fields on the report... appears to be duplication
SOLUTION DESCRIPTION:
This label description has been changed to "Average Purchase Price (Multi Currency)".
When applicable this field should display the average purchase price in the multi home currencies.
If the company is a single currency system, then only the first position will be filled with the amount in the single home
currency.

Solution: 124027
SITUATION IDENTIFIED IN:
"Correct Sales Orders with Duplicate Records" (tdcor1006m000)
SITUATION DESCRIPTION:
Because of solution 122517 duplicate Sales Order Line History records are created in the Sales Order Line History table
(tdsls451). This is corrected with solution 124063.
The only difference between two records is the field "sequence number" (field tdsls451.sern)
SOLUTION DESCRIPTION:
This correction program deletes the duplicate records. Within the specified range of orders and record type it is checked if all
fields except the field "sequence number" (tdsls451.sern) are equal. If so, the duplicate record is deleted. It is advisable to do
a testrun first.
When running the correction program a report is shown. The records printed on the report will be deleted.

Solution: 124032
SITUATION IDENTIFIED IN:
"Print Intergroup Interim Transactions" (tfgld2402m000)
SITUATION DESCRIPTION:
The Ledger Account printed on the report of session Print Intergroup Interim Trasnactions (tfgld2402m000) is not correct.
The ledger account printed on the report is the Intergroup Account defined in the Intergroup Relations. This should be the
Ledger Account for the Target company.
SOLUTION DESCRIPTION:
The above mentioned have been changed.
Printing the Intergroup ledger account on the report is non-information.
The intergroup relations setup can be printed using session Print Intergroup Relations (tfgld2401m000).
Also the report layout has been changed a little. The Ledger Account information and the linked dimensions have
been put directly after the column Target company.

Solution: 124054
SITUATION IDENTIFIED IN:
"Write Off Payment Differences" (tfacr2240m000)
SITUATION DESCRIPTION:
Cannot write off "Payment Difference", if sales invoice was previously revalued for currency difference.
SOLUTION DESCRIPTION:
Can write off "Payment Difference" for sales invoice , even after revaluation.

Solution: 124069
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
If an advance payment request of one currency is processed with an installment invoice using a different currency, the
calculation of the settled amount is not correct. The system adds and compares amounts while they have different
currencies.
SOLUTION DESCRIPTION:
The amount is now calculated in the correct currency. Partial settlements are stored in the currency of the advance. When the
rest of the advance is settled, these partial settlements are also taken into account.

Solution: 124072
SITUATION IDENTIFIED IN:
"Release To Invoicing" (tdsls4501m130)
SITUATION DESCRIPTION:
When entering zero for the field Delivered Quantity in "Release to Invoicing" (tdsls4501m130), a question pops up indicating
that a backorder for the current position will be generated ("Delivered quantity for position ... is zero. This means this
position will be put in backorder completely. Continue?"). Furthermore the line disappears from the browse list.
SOLUTION
DESCRIPTION:
It is standard functionality that for return orders, no backorders will be generated. Therefore a new question was implemented
that clearly states this to the user, when a Delivered Quantity of zero is entered ("Delivered quantity for position ... is
zero. No backorder will be generated. Continue?").

Solution: 124073
SITUATION IDENTIFIED IN:
"Delete Charge Elements" (tppss2200m000)
SITUATION DESCRIPTION:
When starting this session from charge elements, full range appears for deletion even when we select few records for
deletion in session "Charge Elements".
If the user presses the delete option, entire range will be deleted.
SOLUTION DESCRIPTION:
Now if the user tries to delete the entire range of "Charge Elements", a warning message will come & only if the user says
"Yes", then all the records will be deleted.

Solution: 124082
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
After installing solution 117155 our end-users are able to start utilities for which they have no authorization.
SOLUTION DESCRIPTION:
The result of solution 117155 was, that more Business Processes were shown in the Dynamic Menu Browser. Most of them had
roles attached with the so-called excluded authorization, for those ones no utilities should be shown.
The showing of utilities and the starting of utilities have now more checks, so they are not useable, when the authorization for
the role attached is 'excluded' or 'no-authorization'.

Solution: 124090
SITUATION IDENTIFIED IN:
"Print Posting Report" (tpppc4402m000)
SITUATION DESCRIPTION:
While trying to run the session Print Posting Report if the sequence number of the record is more than 9999 it shows "####"
on the report and a lot of Format Overflow errors on the BaaN Server.
SOLUTION DESCRIPTION:
If the sequence number is greater than 9999 it shows "####" in the report.
The above problem is solved.
Now the system prints the all the records with correct sequence number.

Solution: 124092
SITUATION IDENTIFIED IN:
"Convert Requisition Lines to RFQ/PO" (tdpur2201m000)
SITUATION DESCRIPTION:
1. The Purchase Unit is different from the Inventory unit and price Unit of the item.
2. A purchase requisition is created for this item.
3. The amount shown in the Purchase Order line is different from the amount found in the Requisition Line that originated
the Purchase Order.
SOLUTION DESCRIPTION:
The problem with the conversion factor between the Purchase unit and Purchase Price unit has been solved. Now the amount
of the Purchase Order liens would be same as that of the requisition lines.

Solution: 124093
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
When field 'item' is not filled, zooming from field 'Order quantity Unit' or 'Purchase Price Unit' zooms to session 'Units by
Unit set' but no record is displayed.
When an item of type 'cost' is filled, the system zooms to session 'Units' but the selected record from this session is not
entered into the field 'Purchase Price Unit' on returning.
SOLUTION DESCRIPTION:
Now in case the field 'item' is not filled, then the zoom from field 'Order Quantity Unit' and 'Purchase Price Unit' has been set
to session 'Units'.
When a record has been selected in this session, then this unit is entered into the field 'order quantity unit' or 'Purchase
Price unit' on returning from the zoom session.

Solution: 124104
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
Transfer Orders about several lines cannot be shipped if using same position but different sequence numbers.
SOLUTION DESCRIPTION:
Correct sequence number is selected when creating inbound receipt line.

Solution: 124107
SITUATION IDENTIFIED IN:
"Update Cash Forecast" (tfcmg3210m000)
SITUATION DESCRIPTION:
Generate a Sales Order in a multi-site environment, from one of the financial companies. The Sales Office of the company
should be attached to a different company. In such a case, when the user runs 'Update Cash Forecast', the cash forecast is
shown in both the companies, that is, from the company where the Sales Order is generated, and also the financial company
to which the department is attached.
SOLUTION DESCRIPTION:
The correct financial company has been picked up, and passed,
so that the cash forecast doesn't appear in the wrong company. Check has
also been made to update only the financial company from where the session is run, and not other financial companies.
The company of origin of the document, which was always taken as the current
company is changed so that the origin is company in which the document is created. Now, change has been made to fill the
origin as the logistical company from where the document is created.

Solution: 124115
SITUATION IDENTIFIED IN:
"Copy Requisitions" (tdpur2204s000)
SITUATION DESCRIPTION:
The 'Copy Lines' button enabled little late after the 'Copy all lines' check box is cleared. Only when the control goes to the
next field the button is enabled.
SOLUTION DESCRIPTION:
Once the check box is unchecked, the button 'Copy Lines' would be enabled.

Solution: 124116
SITUATION IDENTIFIED IN:
"Process Variances" (whina1200m000)
SITUATION DESCRIPTION:
-1- Due to rounding error, an Integration Transaction of the type Warehousing(Valuation)/Value Correction could be created
with an amount of 1. These transactions should not have been created.
-2- When session "Process Inventory Variances" (whina1200m000) is executed, a Fatal Error could appear when recalculating
the lot price if the lot valuation method is set to "Lot Price".
The Error would be generated if the "Received Quantity in Inventory Unit" of the "Inbound Order Lines" ( whinh210.astk) is
zero (this situation could occur after performing a receipt correction).
SOLUTION DESCRIPTION:
-1- These erroneous Warehousing (Valuation)/Value Correction will not be created anymore.
-2- When the sum of the "Received Quantity in Inventory Unit" of the "Inbound Order Lines" (whinh210.astk ) is zero, no
Fatal Error appear anymore.

Solution: 124117
SITUATION IDENTIFIED IN:
"Item Master Plan" (cprmp2101m000)
SITUATION DESCRIPTION:
When updating the Master Plan of an Item directly after updating the masterplan of his clustered item which do have
distribution orders, all production orders which do exist for the Production item appear at the field Distribution orders.
SOLUTION DESCRIPTION:
When updating the Master Plan of the clustered item which do have Scheduled Distribution Demands in its masterplan and
after that directly updating the Master plan of the Non-Cluster Item. The Scheduled Production Orders are showed up in the
master plan as Scheduled Distribution Receipts.

Solution: 124122
SITUATION IDENTIFIED IN:
"Maintain bank relations" (tfcmg0110m000)
SITUATION DESCRIPTION:
The anticipated amount is included in the bank balance amount displayed with the bank. However, the calculation of the
anticipated amount is not based on the current date, therefore currency differences may occur.
SOLUTION DESCRIPTION:
The calculation of the anticipated amounts is now based on the current date, so all amounts taken into account for the bank
balance are based on the same date.

Solution: 124129
SITUATION IDENTIFIED IN:
"Receipts" (tdpur4531m000)
SITUATION DESCRIPTION:
It is not possible to zoom on Business Partner when using Find button, when 'Sort by' is on Business Partner.
SOLUTION DESCRIPTION:
Now it is possible to zoom on Business Partner when doing Find, when 'Sort by' is on Business Partner.

Solution: 124131
SITUATION IDENTIFIED IN:
"Purchase Contracts" (tdpur3100s000)
SITUATION DESCRIPTION:
1. It is possible to have expiry date before contract date.
2. It is possible to have expiry date before current date.
SOLUTION DESCRIPTION:
Now it is not possible to have expiry date before contract date.
Now it is not possible to have expiry date before current date.

Solution: 124133
SITUATION IDENTIFIED IN:
"Transactions Cash Management" (tfcmg2120m000)
SITUATION DESCRIPTION:
Even when do not enter tax amount in the session, it is creating records in the tax analysis table.
SOLUTION DESCRIPTION:
Now when the tax amount is empty it is not creating records in tax analysis table

Solution: 124138
SITUATION IDENTIFIED IN:
"Select Bus.part. Receipts for Interest Invoices" (tfacr5210m000)
SITUATION DESCRIPTION:
A fatal error was displaying when the interest invoice days exceeded 999 days.
SOLUTION DESCRIPTION:
Now the fatal error is not displaying when the interest days exceeds 999 days.
The representation will done with 999 days, but the interest calculation will be done with the correct number of days.
Message is displayed when this situation is occuring.
SOLUTION 124971 AFTER THIS SOLUTION
---------------------------------------------------------------------------------------------------
VERSION(S):
B50_b, B50_c

Solution: 124150
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
SITUATION DESCRIPTION:
1. When navigating from header to lines and closing sessions, one of the sales sessions can change into a small blue line.
An example of how this could occur is given below:
- Start the Sales Orders session (tdsls4500m000) and press the lines button on the multi occurrence form. The Sales Order
Lines session is opened (tdsls4501m000)
- Open the Sales Order Line (tdsls4101s000)
- Go to the header via the header button on the single occurrence form. Session tdsls4500m000 is opened.
- Open the order header in the multi occurrence form. Session Sales Orders (tdsls4100s000) is started.
- Go to the order lines via the lines button. The single occurrence form (tdsls4101s000) will be shown.
- Go back to the header via the header button on the single occurrence form (tdsls4100s000).
- Close the single occurrence form of the header (tdsls4100s000)
- Press the lines button on the multi occurrence form (tdsls4500m000). Session tdsls4101s000 is opened.
- Close the single occurrence line session (tdsls4101s000)
- Now the header multi occurrence session (tdsls4500m000) is shown AND the order lines session (tdsls4101s000) is changed
into a small blue line. This blue line will disappear as soon as you close the header session.
2. When switching from one sales order header to another (tdsls4500m000) and the lines (tdsls4501m000 and tdsls4101s000)
had been opened before, the wrong order lines are shown, belonging to the previous order.
SOLUTION DESCRIPTION:
1. The special functionality on B50_b allows to switch rapidly between sales order headers and lines. However, windows
were not closed properly in the situation described the above. The program script has been modified to prevent the
appearance of those windows.
2. Now the correct records will be shown. The switch functionality on B50_b will always search if a single occurrence session
is still open. So if another header is opened, and the line session tdsls4101s000 is still open, that window will be shown,
with the correct order line information. When the new order does not have lines, the tdsls4101s000 will be opened in "insert
mode". When switching between orders with unequal number of lines and on the first order a line had been opened (say line 3)
which does not exists in the next order (next order has 2 lines), then the last line of that order is brought forward.

Solution: 124175
SITUATION IDENTIFIED IN:
"Anticipated Payments (details)" (tfcmg2116m000)
SITUATION DESCRIPTION:
Batch was not balanced in the third home currency when you create anticipated document manually and the invoce currency
not equal to payment currency.
SOLUTION DESCRIPTION:
Batch was balanced.

Solution: 124178
SITUATION IDENTIFIED IN:
"Print Where-Used Multi-Level PBOM Components (Summarized)" (tibom1415m000)
SITUATION DESCRIPTION:
While Printing Where-Used Multi-Level PBOM Components (Summarized), system is not printing intermediate Item under
which the given component is used, when the intermediate item is expired in Main BOM.
SOLUTION DESCRIPTION:
When the component is used under a BOM, which is again a component of the other BOM. If the intermediate component
is expired in Main BOM, then while Printing Where-Used Multi-Level PBOM Components (Summarized), system will print
the intermediate component as Main Item since it can be treated as separate BOM.

Solution: 124179
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
1. Alternate Item code is filled in the session "Purchase Order Line" (tdpur4101s000)
2. After the receipts are made, the price is changed for the line in the session "Change Prices/Discounts after Receipts"
(tdpur4122m000)
3. The 'Purchase/Price Variance' posting is done at this time in finance.
4. These posting does not have any 'Cost component' filled in it.
SOLUTION DESCRIPTION:
The cost component for the 'Purchase/Price Variance' posting would be filled now.

Solution: 124185
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120s000)
SITUATION DESCRIPTION:
"Reference doesn't exist" error is thrown when composing the payments because the field "Tax Country" accepts any value
entered in the Payment Advice Session.
SOLUTION DESCRIPTION:
"Tax Country" field is checked against the value that is entered in the Payment Advice session and if it is not a valid
country then the error "Country not found" error will be thrown.

Solution: 124186
SITUATION IDENTIFIED IN:
"Chart Manager: Set Print Options" (ttchm1160m000)
SITUATION DESCRIPTION:
When printing a chart via Chart Manager, it is not possible to print the resulting Postscript file to another paper type than A4,
or to another orientation than Portrait.
SOLUTION DESCRIPTION:
Two fields are added in the "Set Print Options" session of the Chart Manager: The field "paper type" and the field
"orientation".
So now it will be possible to select a paper type between A1 and A4 and portrait or landscape orientation.
The field "Paper Type" may contain the values: A1, A2, A3, A4
The field "Orientation" may contain the values: Portrait, Landscape
Note: These fields have NO link to the settings in "Maintain Device Data".

Solution: 124188
SITUATION IDENTIFIED IN:
"Correct Invoice Quantity and Invoice Amount in PO Line" (tdcor0006m000)
SITUATION DESCRIPTION:
Earlier the correction program "Correct Invoice Quantity and Invoice Amount in PO Line" (tdcor0006m000) was working
based on the following logic.
Amount in invoice currency -> home currency (on the rate at the invoice date)
Again from home currency -> Order currency (on the rate at the order date)
In this case, if the exchange rates on the invoice date and the order date are different, then Invoice Amount of the
'Purchase Order Line' would be different from the invoice amount even if the invoice currency and the order currency are
the same.
But now the standard functionally has been changed with the solution 124026. In case the invoice currency happens to be the
order currency, then it would not be converted to home currency and then back to the order currency.
SOLUTION DESCRIPTION:
The correction program has also been adapted with the same logic. The conversion would not be done if the invoice currency
and the order currency are the same.

Solution: 124192
SITUATION IDENTIFIED IN:
"Quotation Lines" (tdsls1101s000).
SITUATION DESCRIPTION:
Context-sensitive help for Delivery Lead Time (tdsls101.dtme) in session "Quotation Lines" (tdsls1101s000) wrong. The help
text does not clearly describe the purpose of the field.
SOLUTION DESCRIPTION:
Provided updated help text that clearly describes the purpose of this field.

Solution: 124194
SITUATION IDENTIFIED IN:
"GRNI BaanERP" (several)
SITUATION DESCRIPTION:
This solution holds the new GRNI Reconciliation tools. The solution is available for the versions BaanERP 5.0b and
BaanERP5.0c.
This solution holds several new sessions and table definitions. All software components related to GRNI Reconciliation in
BaanERP are delivered through this solution.
For a functional explanation of the new GRNI Reconciliation Tool a user manual is created. This manual can be
downloaded from:
ftp://ftp.support.baan.com/updates/Documents/U7544B_US_-_GRNI_Reconciliation_User_Manual.pdf
In the new GRNI Reconciliation Tools several Icons/Buttons are used on toolbars of session forms. To make sure every
customer will have the pictures shown on the toolbars, we created a WinZip dump. This dump can be downloaded from:
ftp://ftp.support.baan.com/updates/Documents/grni_gif.zip
After loading the dump the dump must be extracted using WinZip. After that pictures in the dump must be put on the
Baanserver in the directory $BSE/gif/gfd0002. The following pictures are present in the dump: Approve_invoice,
hand_match, match_1, table, Unapprove_invoice, unmatch_1. All files have the extension gif.

Solution: 124204
SITUATION IDENTIFIED IN:
"Simulate Masterplan" (cprmp1202m000)
SITUATION DESCRIPTION:
Performance of recompute phasenumbers is much worse after installing solution 102737.
SOLUTION DESCRIPTION:
The performance of recompute phasenumbers pre solution 102737 is set back.

Solution: 124205
SITUATION IDENTIFIED IN:
"Archive/Purge integration transactions" (tfgld4210m000)
SITUATION DESCRIPTION:
No integration transactions may be removed when it concerns integration transactions involving the invoice accrual account
when not all invoices have been approved. Service - Subcontracting also post credit on invoice accrual and therefore should
also be taken into account when determining whether the integration transactions can be archived/deleted or not.
SOLUTION DESCRIPTION:
Now also Service - Subcontracting is considered while archiving integration
transactions. When the related purchase invoices are not yet approved, no archiving will take place of these integration transactions.

Solution: 124211
SITUATION IDENTIFIED IN:
"Generate Purchase Order Advice" (tdsls4240m000)
SITUATION DESCRIPTION:
When the Buy-from Business Partner in the Item Purchase Data is not filled (session tdipu0101s000), no Purchase Order
Advice can be generated (session tdsls4240m000). The error message: "No valid Buy-from BP is found" is given. However
the user can manually enter an advice for the same item in "Purchase Order Advice" (whina3110s000) and save it without
defining a Buy-from BP. This is inconsistent.
SOLUTION DESCRIPTION:
A Purchase Order Advice can now be generated when the Buy-from Business Partner is not known. The Advice can be confirmed but cannot be transferred
to a Purchase Order. This means the error is given in a later stage of this process.

Solution: 124217
SITUATION IDENTIFIED IN:
"Anticipated Receipts (details)" (tfcmg2117s000)
SITUATION DESCRIPTION:
-When changing the 'Transaction Amount' of an anticipated receipt to 0 (zero) within session "Anticipated Receipts Status"
(tfcmg2113s000) after changing the 'Document Status' from 'document sent to customer' to 'document accepted by customer' in
an earlier stage, the 'rejected' amount will be will be posted as currency difference. This happens when the anticipated
currency differs from the invoice currency.
- When modifying the amount simultaneously with changing the 'Document Status' from 'document sent to customer' to
'document accepted by customer', the Balance Anticipated and the Invoice Balance are wrongly updated.
SOLUTION DESCRIPTION:
Changing the 'Transaction Amount' of an anticipated receipt to zero, will not lead to a currency difference anymore. Both
the Balance Anticipated and the Invoice Balance are updated correctly when changing both the 'Transaction amount' of the
anticipated receipt and the 'Document Status'.

Solution: 124218
SITUATION IDENTIFIED IN:
"Simulate Orders " (cprrp1210m000)
SITUATION DESCRIPTION:
When there are multiple demands for an item, with default source "Distribution", the simulate order session will create
planned distribution orders to match the demands.
But after we firm-plan or confirm a planned distribution order, and run simulate orders again, it will delete all planned
distribution orders except the one that we have firm-planned or confirmed.
This only happens when there is a multi site supplying relation set-up between the same plan item.
SOLUTION DESCRIPTION:
The simulate order session will now respect the firm-planned or confirmed orders, and correctly replan the remaining
requirements into planned distribution orders.

Solution: 124223
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
When currency difference postings arise from EBS, the system does not pick the proper dimensions for the same when
posting to tfgld102 (Non-Finalized transactions).
SOLUTION DESCRIPTION:
Now , the system picks the proper dimensions from Session "Ledger accounts by Business Partner Group" , and post them to
tfgld102 (Non-Finalized transactions)..

Solution: 124227
SITUATION IDENTIFIED IN:
"(Un)Block Lots" (whinh6120m000)
SITUATION DESCRIPTION:
While blocking or unblocking a lot, Inventory on hold for planning is wrongly updated
SOLUTION DESCRIPTION:
The inventory on hold for planning is updated correctly

Solution: 124229
SITUATION IDENTIFIED IN:
"Print Budget Cost Allocation Sheet" (tffbs1413m000)
SITUATION DESCRIPTION:
The "Budget Cost Allocation Sheet" is printed for a dimension without a reference unit. The total amount does not take the
credit flag of the ledger accounts into account and summates all amounts.
SOLUTION DESCRIPTION:
Debit and credit amounts are accumulated correctly now. The debit/credit sign was not read from the tables.

Solution: 124253
SITUATION IDENTIFIED IN:
"Machine Utilization by week overview" (tisfc1504m000)
SITUATION DESCRIPTION:
If a main item has a phantom item as its component and if there are operations for phantom items, the system shows the
main item code and the description of phantom item instead of main item description.
SOLUTION DESCRIPTION:
When a main item has a phantom item as its component and if there are operations for phantom items, with the modifications
made in the script, now the system shows the main item code and the description of main item itself.

Solution: 124258
SITUATION IDENTIFIED IN:
"Archive Project" (tipcs2260m000)
SITUATION DESCRIPTION:
If projects are archived, the following error messages can be displayed:
"Hours transaction already processed"
"Spent hours for activity %s is greater the zero; deletion not allowed"
"Inventory already issued; unable to delete"
"Estimated costs have been frozen already; unable to delete"
"Deleting of order not possible because order is already released"
"The project is inactive. Deletion of the BOM line is not allowed"
These messages disturb the archiving process, resulting in incomplete archiving. Some archiving steps were being skipped
due to above messages.
SOLUTION DESCRIPTION:
When archiving, above mentioned messages will not be displayed anymore as they do not apply to the archiving process.

Solution: 124267
SITUATION IDENTIFIED IN:
"Direct Network Communication" (tcedi7205m000/ecedi7205m000)
SITUATION DESCRIPTION:
When the Maintain Networks session (tcedi0120m000/ecedi0120s000) contains the value CR/LF on form 2, the EDI ASCII file
contains records with no Carriage Return Record separator in the store_sent and store_recv directories.
SOLUTION DESCRIPTION:
The CR separator will now show up in the ASCII files in the store_sent and store_recv directories when the CR/LF option is
used.

Solution: 124274
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Select Invoices for Payment session is overwriting the Payment Date on the Check Layout "15 " and "3" when the
parameter Planned Payment Date = Due Date is "NO".
SOLUTION DESCRIPTION:
Select Invoices for Payment session is not overwriting the Payment Date on the Check Layout 15 and 3 when the
parameter Planned Payment Date = Due Date is "NO".

Solution: 124282
SITUATION IDENTIFIED IN:
"Select invoices for Reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
After selecting reminders, the session "Reminder Advice" displays the wrong letter number and session "Print reminder
letters" prints the wrong reminder letter.
SOLUTION DESCRIPTION:
Now, the session "Reminder Advice" displays the proper letter number and session "Print reminder letters" prints the correct
reminder letter.

Solution: 124286
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When using session "Simulate Orders" (cprrp1210m000) sometimes error 606 occurs. The error occurs when program tries
inserting a new planned purchase order line in table "Planned Order Lines" (cprrp110) while there is no corresponding
planned purchase order header available in table "Planned Order Headers" (cprrp100).
SOLUTION DESCRIPTION:
After creation of planned purchase order header in
table "Planned Order Headers" (cprrp100) the program checks if record is
created successfully before continuing with creation of planned purchase order line in table "Planned Order Lines" (cprrp110). Now program inserts
Planning failed signal and continues with next item.

Solution: 124298
SITUATION IDENTIFIED IN:
"Transfer Orders Selection" (cppat1211m000)
SITUATION DESCRIPTION:
Data disappear from the session Transfer Orders Selection when coming back from the session "Resources by Order"
SOLUTION DESCRIPTION:
The data appears correctly when coming back from the session Resources by Order.

Solution: 124304
SITUATION IDENTIFIED IN:
"Calculate Planning Percentages" (tibom2210m000)
SITUATION DESCRIPTION:
Planning Percentages of Product Families is not correct
SOLUTION DESCRIPTION:
The planning percentages are correctly calculated

Solution: 124310
SITUATION IDENTIFIED IN:
"Maintain Transactions Matched Purchase Invoices" (tfacp1133s000)
SITUATION DESCRIPTION:
When running the session "Maintain Transactions Matched Purchase Invoices - tfacp1133s000" the message "Please check the
period information" should only pop up if the periods are different.
SOLUTION DESCRIPTION:
When running the session "Maintain Transactions Matched Purchase Invoices - tfacp1133s000" the message "Please check the
period information" only pops up when the periods are different.

Solution: 124311
SITUATION IDENTIFIED IN:
"Link Invoices To credit Note" (tfacr2121s000)
SITUATION DESCRIPTION:
After reversing the credit note assignment (unlinking), the Assign Credit note Transaction is not empty.
A small amount is present in home currency.
SOLUTION DESCRIPTION:
After reversing the credit not assignment , transaction is empty with out any amount present in home currency.

Solution: 124312
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
In EDI Messages Supported by Business Partner (ecedi0111s000), you can only enter a Business Partner (BP) in internal EDI
for which the affiliated company is filled. The affiliated company can only be filled if the BP has at least a Sold-to and
Buy-from role. The setup can be designed in such a way that there are Business Partners on the sales side with only a
Ship-to role. They can have a parent with all roles. When sending back the Advanced Shipment Notice (ASN), it cannot
prepare an EDI message due to a missing record in ecedi0111s000.
SOLUTION DESCRIPTION:
Now, the system checks if an ASN can be prepared for the Ship-to BP when confirming the shipment. If not, it checks if an
ASN can be prepared for the parent. In general, this procedure is only followed for those BPs which have a parent and do
not have a Buy-from and Sold-to role.

Solution: 124321
SITUATION IDENTIFIED IN:
"Print Accounts Payable Distribution" (tffacp4410m000)
SITUATION DESCRIPTION:
When posting invoice to the General Ledger including VAT, the vat lines are not included when printing session
tfacp4410m000 (Print Accounts Payable Distribution). For the Matched detail lines the Ledger Account description was
printed repeatedly.
SOLUTION DESCRIPTION:
Now in session tfacp4410m000 (Print Accounts Payable Distribution) the VAT lines are printed and the LA description is
only printed once for the matched detail lines.

Solution: 124325
SITUATION IDENTIFIED IN:
"purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. A purchase order line is created and released to warehousing. The receipts are not yet made.
2. In finance, an invoice is created and matching is done by order.
3. Now the order line is deleted in the session "Purchase Order Lines" (tdpur4501m000) session. The deletion is not done and
also there is no message given to the user as to why the order line not deleted.
SOLUTION DESCRIPTION:
Now, a message
-----------------------------------------------------------------------------------------------------------------
There are invoice(s) matched against this order line. Deleting not possible.
--------------------------------------------------------------------------------------------------------------------
will pop up when the Purchase Order Line is selected for delete, if the order line has been matched already.

Solution: 124329
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
When a service order is released by clicking the 'Release' button in the 'Service Orders' (tssoc2100s000) session, an error
message "Required capacity not available (in calendars) for planning" is displayed. This happens when a calendar is not
attached to the service engineer present on the service order. When finding the planned start and finish times, a hierarchy
is taken into consideration. The same hierarchy should be considered when releasing a service order to.
SOLUTION DESCRIPTION:
The following hierarchy is considered when a service order is released.
1) Object's Calendar
2) Configuration's Calendar
3) Service Engineer Calendar
4) Service Center Calendar
5) Company Calendar
The hierarchy is in decreasing order of precedence. That is, the system first checks whether there is a calendar attached with the Object .If a
calendar is present, it is used to check for the object's availability. If the object is not available on the planned start date, then the error message
"Required capacity not available (in calendars) for planning" is displayed. Only if a calendar is not present in one level, the next level in the hierarchy
is considered.

Solution: 124330
SITUATION IDENTIFIED IN:
"Post transaction" (tpppc4802m000)
SITUATION DESCRIPTION:
Difference in reporting year and fiscal year is causing a problem at GLD side while closing the batches.
SOLUTION DESCRIPTION:
A check is built for the reporting year and fiscal year just before calling finance functions. If they are the same, OK.
If not then the reporting year is made equal to fiscal year and reporting period is made corresponding to the start date of the
fiscal period. Now the reporting year and fiscal year are never different.

Solution: 124334
SITUATION IDENTIFIED IN:
"Select Invoices for Direct Debit" and "Select Invoices for Payment" (tfcmg4220m000 and tfcmg1220m000)
SITUATION DESCRIPTION:
The option "Use EURO for EMU currencies" doesn't work if the parameter "Payment Schedule" and/or " Receipt Schedule"
is "ON". The system gets the amount to be paid from table "Payment Schedule" or "Receipt Schedule" and doesn't
calculate the amount in EUR.
The discount amount in home currency is not calculated correctly from the invoice currency. The system gets the rate of the
transaction currency and not the rate of the invoice currency.
SOLUTION DESCRIPTION:
Now the amount to be paid is calculated in EUR.
The discount amount in home currency is calculated correctly

Solution: 124352
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
The 'Alternative item code' is printed only for the first line of the Purchase Orders. It is not printed for the other lines.
SOLUTION DESCRIPTION:
Now the 'Alternative item code' would be printed for all the appropriate lines.

Solution: 124360
SITUATION IDENTIFIED IN:
"Generate Inbound Advice" (whinh3201m000)
SITUATION DESCRIPTION:
By changing the item of a sales order line or by deleting/cancelling a sales order line a possible existing link between the
sales order line and a purchase order line will be broken as well.
In this scenario the received inventory did get stuck on the receipt location since generating inbound advice did not work.
SOLUTION DESCRIPTION:
Now when the link between the sales order and purchase order line is broken the system will not try to crossdock anymore. The
inventory will just be advised to a pick/bulk location. This will prevent the inventory from getting stuck on the receipt
location.

Solution: 124366
SITUATION IDENTIFIED IN:
"Recalculate Budget Data Based on Actual Data" (tffbs1205m000)
SITUATION DESCRIPTION:
Information missing in the Help
SOLUTION DESCRIPTION:
information supplied about how BaanERP calculates the new budget amounts.

Solution: 124376
SITUATION IDENTIFIED IN:
"Revenue forecast for final results" (tpppc3106s000)
SITUATION DESCRIPTION:
System allows to save a revenue code for an activity of type WBS element which is wrong.
SOLUTION DESCRIPTION:
The second time when we insert a record the plan field of the project remain blank and hence system allows to save a record
for wbs element. Assigning the corresponding value of plan before coming to the first field of the form itself solves the
problem.

Solution: 124377
SITUATION IDENTIFIED IN:
"Print Planned Inv Transactions by Order" (whinp1401m000)
SITUATION DESCRIPTION:
The users having Authorization Group as 'print/display' are not able to print the session "Print Planned Inv Transactions by
Order" (whinp1401m000). Only for those users with Modify authorization, it is possible to use the session.
SOLUTION DESCRIPTION:
Now all the users with authorization 'Print/Display' would be able to print the session "Print Planned Inv Transactions by
Order" (whinp1401m000).

Solution: 124381
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
If the parameter "automatic match" is on and an invoice related to orders is entered in tfacp1110s000 and the invoice
amount corresponds completely with the order amount then automatic match should succeed. Instead an error message is shown
to the user that no orders could be found for the packingslip and automatic match is not possible. If the user however
zooms to the orderline/sequence number then automatic match is possible afterwards.
SOLUTION DESCRIPTION:
Now the information whether the user zoomed or not on orderline is taken into account in the automatic match procedure
and automatic match should be possible without first having to zoom.

Solution: 124382
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
Whenever Destination Sales Tax is applicable in the common parameters (So US or Canada) then during purchase invoice
approval shifted tax should be treated as real tax. If the user now creates a purchase correction (via tfacp2110m000) with the
same transactiontype as the approval transactiontype then the batch can not be finalized as the status is not ready but free.
SOLUTION DESCRIPTION:
The check whether shifted tax should be treated as normal tax was not complete,
as it did not consider the fact that with the approval transactiontype also manual purchase corrections can be done. This has
now been corrected.

Solution: 124383
SITUATION IDENTIFIED IN:
"Operation Rates" (ticpr1150s000)
SITUATION DESCRIPTION:
For an independent currency system, when an operation rate in one currency is changed, then the change is not getting
reflect in other home currencies.
SOLUTION DESCRIPTION:
When there is a change in operation rate in one of the home currencies of an independent currency system, then the change
will be reflected in other home currencies.

Solution: 124384
SITUATION IDENTIFIED IN:
"Print Control Account Checklist" (tfacp/acr2415m000)
SITUATION DESCRIPTION:
When running session `Write off currency difference - tfacr2250m000' including unallocated receipts or payments the report
of session "Print Control Account Checklist - session tfacp/acr2415m000" is showing those as errors on the list which is
wrong.
SOLUTION DESCRIPTION:
When running session `Write off currency difference - tfacr2250m000' including unallocated receipts or payments the report
of session "Print Control Account Checklist - session tfacp/acr2415m000" will not show these as errors anymore.

Solution: 124385
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
If an advance payment request of one currency is processed with an installment invoice using a different currency, the
calculation of the settled amount is not correct. The system adds and compares amounts while they have different
currencies.
SOLUTION DESCRIPTION:
The amount is now calculated in the correct currency. Partial settlements are stored in the currency of the advance. When the
rest of the advance is settled, these partial settlements are also taken into account.

Solution: 124393
SITUATION IDENTIFIED IN:
"Cost Components" (tcmcs0148s000)
SITUATION DESCRIPTION:
When zoomed from field Aggregated Material Cost Component of Item Costing Data, Cost Components displays wrong
record.
SOLUTION DESCRIPTION:
Now the system zooms to correct record.

Solution: 124399
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
The label cisli.slcp has been wrongly translated to language 1.
It was displaying as "Financieel Bedrijf". But it should be "Herkomst Logistiek Bedrijf"
SOLUTION DESCRIPTION:
Now it has been corrected.

Solution: 124403
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
In the Item field, if the user types the "Description" and "," together, the system does not search the corresponding item
and zoom to the session "Item Purchase Data" (tdipu0501m000)
SOLUTION DESCRIPTION:
When the item description of the item and the ", " (Comma) are typed together in the item field of the purchase requisition
lines, the item purchase data session is zoomed showing the required item description.

Solution: 124405
SITUATION IDENTIFIED IN:
"Select Invoices For reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
The system is printing wrong letter numbers.
SOLUTION DESCRIPTION:
Now the system is printing right letter numbers

Solution: 124413
SITUATION IDENTIFIED IN:
"Outbond Order lines" (whinh2120s000)
SITUATION DESCRIPTION:
It was not possible to create a warehouse transfer between locations when the transfer quantity is greater than the capacity
quantity available.
All locations have a capacity defined but the parameter 'block when exceeding capacity' is not checked.
SOLUTION DESCRIPTION:
Now, it's possible to create a warehouse transfer between locations when the transfer quantity is greater than the capacity
quantity available.

Solution: 124420
SITUATION IDENTIFIED IN:
teesv1110m000 - Maintain work orders / Werkorders muteren
SITUATION DESCRIPTION:
It is not possible to invoice installments for one specific work order.
SOLUTION DESCRIPTION:
It has been made possible to invoice installments for one specific work order:
- On the first form of session 'Maintain work orders (teesv1110m000)' a button has been added to invoice installments.
- After this button is pressed, session 'Define equipment invoices (teeqi1200s000)' is started.
- Now it is only possible to invoice installments.
- Before the actual processing is starts, session 'Select installments to invoice (teesc2142s001)' is started.
- After selecting one or more installments and leaving session 'Select installments to invoice' the actual invoicing process is
started automatically.

Solution: 124434
SITUATION IDENTIFIED IN:
"Standing Orders" (tfcmg1110s000)
SITUATION DESCRIPTION:
When a 'Standing Order' is created in session tfcmg1110s000 and a currency without rates is selected, not error message
appear.
The currency rate is defaulted to 1 and the standing order can be processed and, even, paid.
SOLUTION DESCRIPTION:
If a currency has no rates in session 'Currency Rates' (tcmcs0108s000), it is no possible to select this currency in session
'Standing Orders' (tfcmg1110s000) because an error message appears.

Solution: 124436
SITUATION IDENTIFIED IN:
"Transferred Orders Selection" (cppat1211m000)
SITUATION DESCRIPTION:
When jumping between forms the order check box on the bottom of form 1 and 3 are sometimes displayed incorrectly and the
lines aren't accessible anymore.
SOLUTION DESCRIPTION:
The checkboxes on the forms are shown correctly and will remain accessible.

Solution: 124438
SITUATION IDENTIFIED IN:
"Calculate Demand Forecast by Item" (whina2202m000)
SITUATION DESCRIPTION:
The formula shown for the demand forecast is not very clear in the report. The report header column prints as "Actual
Usage/Qualified Dem", where as it should have been either of these two.
SOLUTION DESCRIPTION:
The report formula is corrected now. Either one of the following two " Actual Usage/Qualified Dem" is printed now.

Solution: 124441
SITUATION IDENTIFIED IN:
"tdsls1501m000" (Sales Quotation Lines)
SITUATION DESCRIPTION:
When trying to process sales quotations the error message "Not possible to add an item to project %. The project status..." is
printed in the report.
SOLUTION DESCRIPTION:
Now the error message does not occur unnecessarily.

Solution: 124442
SITUATION IDENTIFIED IN:
"Copy Received Purchase Invoices" (tfacp1210s000)
SITUATION DESCRIPTION:
When the session "Copy Received Purchase Invoices" (tfacp1210s000) is started from session "Maintain Purchase Invoices"
after entering the "Supplier", it displays the data from the First Supplier sorted on supplier/document.
SOLUTION DESCRIPTION:
When the session "Copy Received Purchase Invoices" (tfacp1210s000) is started for an entered supplier, it will display the
Registered Invoices, starting from the entered supplier in "Purchase Invoices" and data is sorted on supplier-document.

Solution: 124446
SITUATION IDENTIFIED IN:
"Maintain Query Data" (ttadv3180m000)
SITUATION DESCRIPTION:
When generating a report, via Maintain Query Data (ttadv3180m000), the following error message appears. "Fatal Error:
index 256 out of dims [0] 255."
When in the User Data ISO-BIN is selected and the report default size (width) is greater the 216 this problem will occur.
SOLUTION DESCRIPTION:
Now the report is generated correctly.

Solution: 124447
SITUATION IDENTIFIED IN:
"Post Payments" (tfcmg1257m000)
SITUATION DESCRIPTION:
Double postings for the reversal of the interim account for VAT on payments when the payment is done automatic. The
postings are doubled for the actual vat account as well.
The problem is generated when running session "post Payments - tfcmg1257m000" When the Payment Batch is being finalized
the problem is made visible on the finalization report.
SOLUTION DESCRIPTION:
The vat on payments is handled correctly for automatic payments now. The reversal for vat on payments and the posting to
the actual vat account is done once now as it should.

Solution: 124448
SITUATION IDENTIFIED IN:
"Match Purchase Order Lines" (tfacp2541m000)
SITUATION DESCRIPTION:
After entering a Purchase Invoice (tfacp1110s000), from specific the option "Match Order" is chosen, the session "Match
Purchase Order Lines" (tfacp2541m000), is started. Now if an order which is in the end, is chosen from a list of orders for
the Business Partner and from Specific the option "Match Selected Order" is chosen, the session after matching the order
displays orders from the start again, instead of continuing with the order list.
SOLUTION DESCRIPTION:
After matching a selected order from a list of orders, the session doesn't go to the first record, instead it stays at the current record.

Solution: 124450
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
Check of maximum sequence number goes wrong in case of production order.
SOLUTION DESCRIPTION:
Check of maximum sequence number is only performed in case of transhipment.

Solution: 124452
SITUATION IDENTIFIED IN:
"Audit Direct Debits" (tfcmg4255m000)
SITUATION DESCRIPTION:
Session tfcmg4255s000 does not print the error message " tfcmg4255 ??????????????????????? " when Zero payments are
being processed through direct debit.
SOLUTION DESCRIPTION:
Now the message (Reciept Amount =0) is dispayed Properly.

Solution: 124454
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000)
SITUATION DESCRIPTION:
From session "Open Entries" (tfacp2520m000), when we open the session "Purchase-Invoice Details" (tfacp2100s000), it is
not possible to modify any details of the invoice, which is possible, when we start session "Purchase Invoice Details"
(tfacp2500m000) and then go into session "Purchase-Invoice Details" (tfacp2100s000).
SOLUTION DESCRIPTION:
It is now possible to edit the Purchase Invoice Details, from session "Open Entries" (tfacp2520m000).

Solution: 124455
SITUATION IDENTIFIED IN:
"Report Operations Completed" (tisfc0530m000)
SITUATION DESCRIPTION:
For a production order with multiple phantom items, the system generates a sequence of network routing in production
planning. This sequence is changed in a way that two parallel sequence of operation occurs simultaneously (2 start
operations). Now when the last operation of the routing is completed, all the preceding operations in the routing are not
completed correctly.
SOLUTION DESCRIPTION:
The logic of searching the preceding operations is generalized. Now for any
change in sequence of phantom routings or normal routings, the system completes all the preceding operations correctly.

Solution: 124465
SITUATION IDENTIFIED IN:
"Inventory Handling Parameters" (whinh0100s000)
SITUATION DESCRIPTION:
The parameter 'Inventory Handling Parameter field Inventory Blocked for Planning' in session "Inventory Handling
Parameters" (whinh0100s000) is YES initially. For the planned items, there are few inspections open and are to be done. At
this time the quantity equal to the inspection quantity is updated in the 'Inventory on Hold for Planning' field in "Item
Inventory by Warehouse" (whwmd2115s000). Before the Inspection is done, the parameter 'Inventory Handling Parameter field
Inventory Blocked for Planning' is turned OFF. So, .at the time of approval the value in 'Inventory on Hold for Planning'
field is not decreased. This creates problem in planning.
SOLUTION DESCRIPTION:
It would not be possible to turn the check box 'Inventory Handling Parameter field
Inventory Blocked for Planning' in session "Inventory Handling Parameters" (whinh0100s000) to NO, when there is some
quantity filled for any item in the field 'Inventory on Hold for Planning'.

Solution: 124471
SITUATION IDENTIFIED IN:
"Authorize Purchase Invoices" (tfacp1104m000)
SITUATION DESCRIPTION:
When starting up the session Authorize Purchase Invoices (tfacp1104m000) and moving trhe vertical bar up and down or going
one page further and backwards, the status of the fields "confirmed" and "returned" are changing. This is not consistent.
SOLUTION DESCRIPTION:
When the vertical bar is moved or a next page is opened and gone backwards the status of the fields "confirmed" and
"returned" are consistent.

Solution: 124472
SITUATION IDENTIFIED IN:
"Report dll" (ttstprepdll)
SITUATION DESCRIPTION:
When printing some documents the first page was printed on two pages. On the first page just the header is printed, on the
second page is the complete text was present. Header and the text should have been printed on one page.
SOLUTION DESCRIPTION:
The first page is printed on one page (just like the other pages).

Solution: 124475
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100m000)
SITUATION DESCRIPTION:
Impossible to set activity with change method Remove/Install to the status "costed" if an other activity with change method
Remove/Install has been processed later for the same Object and the same configuration.
SOLUTION DESCRIPTION:
Now, a new question appears, "Change not executed for Activity Line %d, Continue with status change to Costed?"
(tssocs2100), warning the user before changing the status to "Costed" from the activity line or the service order.
Then, the user can choose to continue or not.

Solution: 124477
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
In a multi-finance set-up, assigned/processed invoices are not seen when entered again to reverse the assignments.
Also, invoices which are linked to OTHER unallocated/advance receipts are wrongly shown in some other
unallocated/advance receipts.
SOLUTION DESCRIPTION:
Now, assignments (invoices) are shown properly to change or reverse them.

Solution: 124478
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Planning does not consider the routing operations, which has an effective date in future. This happens if an operation has
an expiry date and another operation exists with the same operation number, different sequence number and whose effective
date is same as the expiry date of earlier sequence operation and demand exists before and after the expiry/effective date
SOLUTION
DESCRIPTION:
While generating the Planned Production Order and Capacity used by
planned order, system will consider all the operations effective in that period.

Solution: 124483
SITUATION IDENTIFIED IN:
"form editor" (ttadvformedit)
SITUATION DESCRIPTION:
When adding (on a report) a multibyte label before a field then the field will move to the right after save/exit and reopening
of the report layout.
SOLUTION DESCRIPTION:
The field will now no longer move when a label is inserted with multibyte characters.

Solution: 124484
SITUATION IDENTIFIED IN:
"Workcenter Util. by day overview" (tisfc1506m000)
SITUATION DESCRIPTION:
Sometimes the wrong routing-description is displayed.
SOLUTION DESCRIPTION:
The routing-description is also properly fetched and displayed if the item-code changes, and not only when the routing-code
changes.

Solution: 124493
SITUATION IDENTIFIED IN:
"Manual Sales Invoice " (tfacr1110s000)
SITUATION DESCRIPTION:
System creates a manual sales invoice with document number "0" when "undo" option is executed continuously.
SOLUTION DESCRIPTION:
Manual sales invoice with document number "0" is not created.

Solution: 124494
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When using an Independent Multicurrency System in some cases more then one integration transactions is created instead of a
single integration transaction.
This is done when there is a difference in the sign for the currency in a transaction of the values of the (multi-currency)
amount field. This situation can occur when e.g. the values of multi-currency fields of prices are changed manually, or if relative large and frequent changes
occur in the currency rates.
Example
Currency 1 USD -100
Currency 2 RUP 10000
Currency 3 DM 120
For this example, the system generates tree separate integration transactions because currency 1 has a different decimal sign
as currency 2 and 3.
When posting the integration transactions in some cases only for the last currency (3) the posting is correct. An error occurs
for the other two currencies.
This error only occurs when the mapping scheme is mapped on a type that is coming from the additional table (tfgld415).
This example looks a little strange but (for example) when the cost price of an item is based on old currency rates and the rates
are fluctuating a lot it is possible to get a negative amount in one currency and a positive amount in an other currency.
SOLUTION DESCRIPTION:
When creating integration transactions for finance for every integration transaction an additional record is created in table
'Additions for Integration Transactions' (tfgld415).

Solution: 124500
SITUATION IDENTIFIED IN:
"Update BusinessPartner in tfgld106" (tfcor1236)
SITUATION DESCRIPTION:
In the table "Finalized Transactions" (tfgld106), the Business Partner field (tfgld106.bpid) is not getting updated for
Production/subcontracting Integration type of transactions.
SOLUTION DESCRIPTION:
This correction program "Update BusinessPartner in tfgld106" (tfcor1236) is used to update the Business Partner in table
"Finalized Transactions" (tfgld106) under the following conditions. The transaction is of type "Integration Transaction" and
the Business Partner is spaces. The integration transaction type should be of Purchase or Production/Subcontracting.
There is also an option on the form to Update the table "Interim table for GRNI" (tfacp135) for the documents corrected in table tfgld106.
The option is valid only when the option "Test Run" is set to "N".
When running the session first run the report with option "Test Run" = "Y", in which case only a report is printed and no updating take
place. If the report is satisfactory, then the updating can be done by running the session again with option "Test Run" = "N".

Solution: 124508
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
The Invoice-to Business Partner needs to be included in the outgoing Advanced Shipment Notice (ASN). The field "Invoice-to
Business Partner" (whinh430.itbp) is never filled in the application and hence it cannot be send via EDI.
SOLUTION DESCRIPTION:
Now the Invoice-to BP field will be supported for outgoing messages. Since the field whinh430.itbp is not filled in the
application, and there can be more than one sales order on a single shipment, the Invoice-to BP is retrieved from the original
Sales Order header, for each shipment line.

Solution: 124510
SITUATION IDENTIFIED IN:
"Print Purchase Invoice" (tdpur4404m000)
SITUATION DESCRIPTION:
The field 'Invoice Date' of Purchase Order Line is determined and updated incorrectly, on running the session with 'Final
Invoice' flag ticked.
Steps:
1. The session is run for a purchase order line record with an old 'Invoice Date', with the option 'Print Already Printed
Invoice' ticked
2. Without closing the session, the session is run again for a new purchase order line with the option 'Print Already Printed
invoice' un-ticked and 'Final Invoice' (in Form 2) ticked.
SOLUTION DESCRIPTION:
Now the field 'Invoice Date' of Purchase Order Line is determined and updated correctly, on running the session with 'Final
Invoice' flag ticked.

Solution: 124513
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40b and B40c
122489, 123778, 123848
Defects solved in B50b, 7.1a
122092, 122997, 123454, 123778
Descriptions:
- Defect 122092 Obj in proc not found err because wrong window type of qbf
- Defect 122489 mb right aligned fileds not displayed
- Defect 122997 Find window for segmented fields corrected
- Defect 123454 Do not execute init.form when modifying job params
- Defect 123778 Index out of dims in stpcreatdll when short description for form command is empty
- Defect 123848 Busy cursor shown to often
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 124515
SITUATION IDENTIFIED IN:
"Print Open Entries" (tfacp2421m000)
SITUATION DESCRIPTION:
When running the report "Print Open Entries" (tfacp2421m000) for a range of "Financial Companies", the output is not
consistent when the report is run for only 1 Financial Company.
SOLUTION DESCRIPTION:
The report prints consistent data, irrespective whether it is run for a single company or for a range of companies.

Solution: 124519
SITUATION IDENTIFIED IN:
"Transfer Planned PRP Purchase Orders" (tppss6230m000)
SITUATION DESCRIPTION:
When a planned prp purchase order from TP (which has empty warehouse field) is transferred to order management as a RFQ ,
the warehouse field in the generated RFQ is filled with the default warehouse from the item data. This is wrong , it should
be empty.
SOLUTION DESCRIPTION:
Now the system wont fill the warehouse field with the default warehouse from the item data , if the RFQ is generated from
the TP projects.

Solution: 124525
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
When the purchase order is generated from a Direct Delivery sales order, the Carrier filled in the Sales Order line is not
passed on to the Purchase Order line.
SOLUTION DESCRIPTION:
The Carrier in the Direct Delivery Purchase Order would be the same as what is entered in the Corresponding Sales Order
Line.

Solution: 124528
SITUATION IDENTIFIED IN:
"Compose Payments" (tfcmg1257m000)
SITUATION DESCRIPTION:
When paying a purchase invoice that has a tax code with the following characteristics:
Shifted Tax : Yes
Expense Purchase Tax : Yes
And when there is a discount on your payment advice, the following fatal error is generated:
Fatal error : index 2 out of dims [1] 1
Fatal error : Can not continue in tfcmg1257m000 (tcmcs.dll0095.read.parm)
Error : tfcmg1257m000: A not terminated transaction is aborted.
SOLUTION DESCRIPTION:
Now there is no fatal error when paying a purchase invoice that has tax code with shifted tax and expense purchase tax set to
'yes'

Solution: 124533
SITUATION IDENTIFIED IN:
"Update Vendor Rating" (tdpur8850m000)
SITUATION DESCRIPTION:
Unwanted error messages are printed many times for the same order & position while updating Vendor rating using "Full
Update".
SOLUTION DESCRIPTION:
Now, the repeating messages are reduced & the error report is printed properly.

Solution: 124544
SITUATION IDENTIFIED IN:
"Generate Bills of Critical Material" (tibom2220m000)
SITUATION DESCRIPTION:
While Generating the BCM system is not considering the Purchased Item, which is Critical in Master Planning and
maintained as Phantom in BOM.
SOLUTION DESCRIPTION:
While generating BCM system will consider the Purchased Item which is Critical in Master Planning and that has a
checked Phantom field in BOM.

Solution: 124545
SITUATION IDENTIFIED IN:
"Manual Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
The field "Price" (cisli225.pric) has a domain "tcamnt" and the format code linked was %A005. But all other price fields
have a domain "tcpric" and format %A003. Because of this, the user is not able to enter the price as per his need.
SOLUTION DESCRIPTION:
The only difference between these two domains is in the format code only. So instead of changing the domain itself in the
table, the format code linked in the form "Manual Sales Lines"(cisli2125s000) is changed to %A003.
Now the user can enter the price as per his need.

Solution: 124548
SITUATION IDENTIFIED IN:
"Receipt Lines" (whinh3120s000)
SITUATION DESCRIPTION:
The 'Inventory Date' defaulted in the session "Receipt Lines" (whinh3120s000) is Lot Date. This leads to creation of new stock point (which can be seen in the session "Inventory by Item, Warehouse, Location and Lot" (whinr1542m000) ), if Inventory Date of the item is different from Lot Date. This happens in the case of making receipt for return of raw materials, which are lot controlled, from shop floor to Warehouse.
SOLUTION DESCRIPTION:
Lot Date has more priority over Inventory Date for Lot items. Hence the system will continue to default Lot Date, for the field 'Inventory Date', in the session "Receipt Lines" (whinh3120s000). However, it will be made possible to zoom to the session "Inventory by Item, Warehouse, Location and Lot"
(whinr1542m000) from the field 'Inventory Date' (whinh210.idat) in the session whinh3120s000. From this session the user can zoom to the existing stock points of the item and can choose a stock point. The Inventory Date will be defaulted from the selected stock point.

Solution: 124554
SITUATION IDENTIFIED IN:
"Interest Invoice Lines " (cisli2110s000)
SITUATION DESCRIPTION:
Interest invoice transfered to SLI are not processed further because tax country code is not filled. This happens for the
invoices for which tax is calculated at transaction line level.
It is also not possible to enter the Code in SLI.
SOLUTION DESCRIPTION:
Now a default code is always sent from ACR to SLI whenever the Interest Invoice is transferred to SLI. This default can be
changed in SLI.

Solution: 124560
SITUATION IDENTIFIED IN:
"Item Surcharges" (ticpr1510m000)
SITUATION DESCRIPTION:
When a surcharge is duplicated, then the surcharge bases of original will not be copied to the latter surcharge, if the
original one is having a warehouse filled and the copied one is not having the warehouse or different warehouse filled or vice
versa.
SOLUTION DESCRIPTION:
When a surcharge is copied, the surcharge bases will be copied irrespective of the warehouses filled in original and copied
surcharges.

Solution: 124568
SITUATION IDENTIFIED IN:
"Correct Cost Price Component for Pur. Price Variance posting" (tdcor0008m000)
SITUATION DESCRIPTION:
There are few records of 'Transaction Origin/Financial Transaction' as 'Purchase/Price Variance' in "Integration
Transaction by Project/Order" (tfgld4510m000) with out cost price component blank. This happened for the purchase orders
with the alternate item code.
SOLUTION
DESCRIPTION:
The correction program has been created to fill the cost components of the above mentioned records. This cost component is filled
in the Purchase Order Line as well.

Solution: 124573
SITUATION IDENTIFIED IN:
"Form Editor" (ttadvformedit)
SITUATION DESCRIPTION:
When a report is edited and a label is copied (esc+q) and pasted (esc + y) on the first column of a report one space is placed
in front of the label.
SOLUTION DESCRIPTION:
The space was the result of a mistake in the conversion of positions in multibyte reports. When a label is copied to the first
column of a report no extra space is added anymore.

Solution: 124589
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When posting sales invoices which has advances settled, the reversal booking on the interim turnover account went wrong. The
system was picking up the interim sales account from the financial data of a blank tax code. If financial data for a blank
tax code was not defined, then the system displays an error message "Ledger account not defined" in the exception report.
SOLUTION DESCRIPTION:
Now the correct account is picked up from the original tax code used. And so no error message

Solution: 124597
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
"Confirm Backorders" (tdsls4125m000)
"Release to invoicing (batch)" (tdsls4247m000)
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
1. It is possible to Recalculate Prices and Discounts (using option "Recalculate Price/Discounts Order Line" in
Specific-menu in session "Sales Order Lines" (tdsls4501m000)) for an orderline which is already invoiced.
2. When an Outbound Advice for a partial shipment for a commitment item is deleted, the backorder for this line cannot be
confirmed. A new backorderline with order quantity 0 is created.
3.The message "The Data Access Layer doesn't allow the operation update on table tdsls401" pops up when entering the
change/type codes correctly and trying to cancel a line, and user is not able to cancel line.
4.
5. When have a phantom item where some of the components have no availability and/or only partial availability, order
line commitment fails to make a commitment for the components which are available.
6. When modifying header/footer text on a Sales Order Header, the modifications are not applied to Invoices that were printed
already. Although this is standard behavior this might be confusing to users, since no notification was given.
7. Not possible to release sales orders to invoicing (batch), if a Collect type Sales order precedes other orders that qualify for
release to invoicing.
SOLUTION DESCRIPTION:
1. It is first checked whether a line can be repriced before going into the Repricing process. If not, the message:
"Pricing/discounting cancelled" is given.
2. The backorder for a sales order line with a commitment can be confirmed. A new sales order line of type "backorder" is
created with the correct orderquantity.
3. The error message no more occurs, and the user is able to cancel the order line.
4.
5. Commitment is made for available components, but phantom is correct backordered. Line which is completely
backordered cannot be released to Warehousing.
6. When changing header/footer text for a Sales Order that was (partially) released to Invoicing, a message will be shown,
indicating that text on existing Invoices should be modified manually.
7.Now it is possible to release to invoicing (batch), even if a collect order precedes other potential sales orders that qualify
for release to invoicing.

Solution: 124599
SITUATION IDENTIFIED IN:
"Objects" (tscfg2100s000)
SITUATION DESCRIPTION:
Currently, the system does not do a check in the session Objects (tscfg2100s000), to verify that the new combination
Item/Serial number being entered, is already used. The user should be warned about this, because this may mean, that something
is not correct with the data-entry. If this duplicity, is not detected on time, it can lead to additional administrative time and
this could lead to the wrong service deployment, if the call is registered based on the serial number of the item.
SOLUTION
DESCRIPTION:
When the user is entering a new object's information, after the serial number and the item is introduced, a check to verify if such a combination already
exists is done. If there is such a combination already present on the database, an 'warning type' question is going to pop-up, warning the user about this
duplicity, then, the user is able to choice if he wants to continue or not. In case of a positive answer, the Object data will be saved on the database. On
a negative answer, the user must introduce at least a new serial number.

Solution: 124601
SITUATION IDENTIFIED IN:
"Periodical Revaluation Results" (tffas3102m000)
SITUATION DESCRIPTION:
After inserting a new group record in session tffas3102m000 (Periodical Revaluation Results) and trying to insert a new
record (to enter period and amount), the error "Array bound error" for variable 'tffas200.ream' is popped up.
SOLUTION DESCRIPTION:
Now in session tffas3102m000 (Periodical Revalution Results) the Error: Array bound for variable tffas200.ream does not appear anymore.

Solution: 124603
SITUATION IDENTIFIED IN:
"Match purchase order lines" (tfacp2541m000)
SITUATION DESCRIPTION:
If the user matches through session tfacp2541m000 and chooses from the specific menu the option "match all" then if there
are many orderlines for which no receipt has been done yet then the user gets for those order lines a message indicating
that no receipt has been done yet.. The user has no control over the number of error messages. So this could mean clicking
many times on OK, whereas the user allready knows what is wrong and would like to abort the process.
SOLUTION
DESCRIPTION:
Now the user gets after the message a question whether he/she would like to continue. If not then the process is aborted, otherwise the process continues and tries to match the next orderline.

Solution: 124606
SITUATION IDENTIFIED IN:
"Assign Invoices to Credit Notes" (tfacp2121s000)
SITUATION DESCRIPTION:
In session "Assign Invoices to Credit Notes - tfacp2121s000", after reversing the credit note assignment, the assignment
document is not deleted, as it has a small amount left, due to currency difference.
SOLUTION DESCRIPTION:
Now after reversal, the assignment document gets status "deleted"

Solution: 124610
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When the user zooms from the 'Shipment' field of the session "Confirm Shipments/Loads (whinh4275m000)", the zoomed
session "Shipments" (whinh4530m000) does not show the exact shipment number that is present in the 'Shipment' field.
SOLUTION DESCRIPTION:
Now the zoom would go to the shipment number that is present in the field from where the zoom is performed.

Solution: 124614
SITUATION IDENTIFIED IN:
"dump form" (ttdlldumpform)
SITUATION DESCRIPTION:
Table field dumped as mandatory field while it should not be mandatory because of datadictionary of the table.
SOLUTION DESCRIPTION:
Now all table fields are dumped as non mandatory and the bshell will findout at runtime if the field should be mandatory
because of the table definition.

Solution: 124627
SITUATION IDENTIFIED IN:
"Dutch tax audit file" (tfgld8200m000)
"Select Values for GRNI Reconciliation" (tfacp1235m000)
"Integration mapping Scheme" (tfgld4500m000)
SITUATION DESCRIPTION:
Some missing labels and incorrect links in various TF Help topics.
SOLUTION DESCRIPTION:
Codes corrected. Missing labels included in solution.

Solution: 124628
SITUATION IDENTIFIED IN:
"Negative Inventory" (whinh2535m000)
SITUATION DESCRIPTION:
3 Glossary topics are missing.
SOLUTION DESCRIPTION:
Topics supplied

Solution: 124629
SITUATION IDENTIFIED IN:
"Accept Values of GRNI Reconciliation" (tfacp1535m000)
SITUATION DESCRIPTION:
It appears that the English and German Help text of the GRNI session tfacp1535m000 are missing.
SOLUTION DESCRIPTION:
The English and German texts are supplied with this solution.

Solution: 124638
SITUATION IDENTIFIED IN:
"Generate Cost Forecast by Cost Object" (tpppc2216m000)
SITUATION DESCRIPTION:
Generate cost forecast by cost object with previous data as base was not taking account previous data. This was the case
when data is manually entered. So the forecast generated was wrong.
SOLUTION DESCRIPTION:
Now when generating cost forecast with previous data as base, all previous data will be considered for generating the
forecast. The data can be either manually generated or by control data.

Solution: 124641
SITUATION IDENTIFIED IN:
"Maintain Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
The ATP (Available To Promise) is not properly checked in the Quotation Lines.
SOLUTION DESCRIPTION:
The ATP is now properly checked.

Solution: 124643
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40c
123366, 124202, 207375
Defects solved in B40c
123366, 124202
Defects solved in B50b
124289
Defect solved in 71a
123449, 124289, 206304
Descriptions:
- Defect 123366 FONT setting corrected for Multibyte
- Defect 123449 Grid selection out of range
- Defect 124202 Qbf fatal error using sequence order
- Defect 124289 put field on rotating curr field corrected
- Defect 206304 Session type via menu shouldn't be MODAL
- Defect 207375 Error 303 when setting appl lock for text
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 124644
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
1. A particular lot is blocked for Transshipment (In) in the receiving warehouse.
2. In case of Transfer Order, the system happens to generate the outbound advise from the above mentioned lot.
3. But the shipment cannot be confirmed due to the fact that it cannot be received in the receiving warehouse.
4. The goods remain in the staging location and the outbound line is stuck.
SOLUTION DESCRIPTION:
The system would not advise the lot if that lot is blocked for Transshipment (In) in the receiving warehouse.

Solution: 124648
SITUATION IDENTIFIED IN:
"Match/Approve purchase invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
Whenever a receipt has been done in Purchase for a purchase order line and with the first receipt not the whole quantity was
received then a backorder is/can be created. If for the first receipt the whole quantity is matched then still the totally
matched flag is not put to yes, which gives problems while archiving with session tfacp2250m000.
SOLUTION
DESCRIPTION:
Now this has been solved. Also with partial receipts in purchase the totally matched flag is set correctly.

Solution: 124651
SITUATION IDENTIFIED IN:
"Confirm receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Purchase order number of subcontracted production orders was not updated in the integration transaction.
SOLUTION DESCRIPTION:
Purchase order details are now updated in integration transaction.

Solution: 124657
SITUATION IDENTIFIED IN:
"Copy Sales Order" (tdsls4201s000)
SITUATION DESCRIPTION:
When the sales order line are linked to a Child BP which does not have ship to contact role where as the Parent BP has a ship
to contact role, then copying this sales order is not possible.
SOLUTION DESCRIPTION:
Now when the child BP is not having any ship to contact role also, it is possible to copy the sales order line.

Solution: 124659
SITUATION IDENTIFIED IN:
"Material Issue for the production order" (ticst0101m000)
SITUATION DESCRIPTION:
1. The return material from shop floor is received in the warehousing.
2. At that time a 'Warehousing (Valuation) / Revaluation' posting is done due to the difference in FTP on the Receipt date
and Issue Data.
3. The amount of this posting is posted with wrong sign. Due to this the inventory account shows a wrong value.
SOLUTION DESCRIPTION:
The amount on the a 'Warehousing (Valuation) / Revaluation' posting is now done with the correct sign at the time the return
material is received in the warehousing.

Solution: 124663
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
It can be possible that whenever during approval an integration function to a logistical company is started that when
returning the company number is not switched back. This problem therefore can only be a problem in a multi company environment.
SOLUTION DESCRIPTION:
The correct switch back to the financial company is now performed.

Solution: 124684
SITUATION IDENTIFIED IN:
"Print Inbound Advice" (whinh3460m000)
SITUATION DESCRIPTION:
System takes long time to print the Inbound advice, when the selection is by order origin and order number.
SOLUTION DESCRIPTION:
The session "Print Inbound Advice" (whinh3460m000) can print the inbound advice in two ways: Inbound Data by Order and
Inbound Data by Run Number. Disregarding the selected option, the system always retrieved the inbound advices sorted on
Run number . Now this is only done if the advice should be printed by Run number. If the option Inbound Data by Order is
chosen, the system will retrieve the inbound advices sorted on order.

Solution: 124686
SITUATION IDENTIFIED IN:
"Match Electronic Bank Statements" (tfcmg5212m000)
SITUATION DESCRIPTION:
In case a electronic bank statement contains receipts with a document date in the future these receipts are matched
automatically. This is a problem when printing a aging report by document date.. Fully paid invoice are showed as open items then.
SOLUTION DESCRIPTION:
It is not possible to automatch receipts / payments with a document date in the future anymore. These receipts are filtered
out by the automatch session (tfcmg5212) and are printed on the report generated by this session.
After the automatch there is a possibility to match these receipts manually with session tfcmg5503m000 (Electronic Bank
Statements) and to change the document date.

Solution: 124688
SITUATION IDENTIFIED IN:
"Rebuild Planned Inventory Transactions" (whinp1200m000)
SITUATION DESCRIPTION:
When a sales backorder is cancelled and session "Rebuild Planned Inventory Transactions" (whinp1200m000) is run, this
backorder is visible in "Planned Inventory Transactions by Item" (whinp1500m000)
SOLUTION DESCRIPTION:
Cancelled backorder are not visible in "Planned Inventory Transactions by Item" (whinp1500m000) anymore.

Solution: 124691
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
-1- When a non-lot controlled item has a lot controlled components and the receipts is made by components, it is not
possible to release the Purchase Order Line to warehousing.
-2- The Purchase Order generated from service is release to warehouse. After that the item is changed in the Purchase Order
line. The 'Warehouse' field becomes blank now and the status of the line also changes to 'Awaiting Receipts'. But the
Warehouse Orders generated for the previous item are not deleted.
SOLUTION DESCRIPTION:
-1- The user would not be able to save the Purchase Order Line when the non-lot item has a lot controlled component.
-2- When the Warehouse becomes blank in the purchase order lines the already generated warehousing order would be
deleted now.

Solution: 124703
SITUATION IDENTIFIED IN:
"Sales Contract Lines" (tdsls3101s000)
SITUATION DESCRIPTION:
If you insert a new sales contract line ands during the insert-process the VAT code on the last form of the session Sales
Contract Lines (tdsls3101s000) will be default based on several parameters. If this VAT-code is cleared or changed during
the insert-process and Sales Contract Line is saved the default VAT-code will be inserted again.
SOLUTION DESCRIPTION:
The VAT-code will not be changed anymore during the save of the Sales Contract Line.

Solution: 124715
SITUATION IDENTIFIED IN:
"Export Solution Multi-level" (ttpmc1202s000)
SITUATION DESCRIPTION:
When a multi-level export dump of a solution is created, also solutions which are part of a released patch (service pack), are
exported. This implies that the export dump will contain all pre-requisite solutions from the initial release of the product up
to the requested solution, which may result in a very big export dump.
SOLUTION
DESCRIPTION:
Now only solutions are added to the multi-level export dump, which do not belong to a released patch.

Solution: 124717
SITUATION IDENTIFIED IN:
"Element budget" (tpptc1110s000)
SITUATION DESCRIPTION:
The item is getting customized when the user clicks the button make customized twice while item should be customized when
user clicks it for the first time itself
SOLUTION DESCRIPTION:
The no.of error messages present for the item which are actually warning message only seem to create the problem. Now all
these messages are displayed before as soon as the item is entered and hence the item gets customized at the first click of
"Make Customized" itself.

Solution: 124723
SITUATION IDENTIFIED IN:
"Recalculate Prices and Discounts" (tdsls4201m500)
SITUATION DESCRIPTION:
1. When a salesorder line is not shipped but already advised, prices and discounts can be recalculated in Simulation mode,
but cannot be recalculated in Real mode.
2. The error message in that case is not printed complete on the error report: "Order line X sequence Y cannot be modified.
It has been r"
SOLUTION DESCRIPTION:
Prices and discounts can be recalculated until the advice in Warehousing is released. When the advice is already released a
complete error message is given:
" Order line %d, sequence %d cannot be modified. It has been released or is linked to a receipt"
Both the Simulation and the Real mode are consistent in this situation.

Solution: 124724
SITUATION IDENTIFIED IN:
"Menu Fields" (ttadv3561m000)
SITUATION DESCRIPTION:
The session description disappears from menu, after dumping the menu. This problem occurs in the following situation: The session in the highest VRC only has a description in 1 language. Then menu is dumped for a language where the description does not exist.
SOLUTION DESCRIPTION:
Session description in the menu is updated following the VRC structure.

Solution: 124735
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When reading sales orders with multiple order lines with customized items, the following error appears on the "Errors in
Received Messages" report: "Project segment of item code does not match with project". It appears that the data in the file is OK.
SOLUTION DESCRIPTION:
Because some values were not initialized properly, an error message appeared while the data read from the file were
correct. The program script has been modified. Orders with project information are now inserted properly.

Solution: 124736
SITUATION IDENTIFIED IN:
"Business Partners" (tccom4100s000)
SITUATION DESCRIPTION:
When entering a tax number (= VAT- ID) for a business partner, the helptext states that it shall be used as default for the tax number of the addresses.
But this default is neither used in entering a new address, nor in entering a sales order line for the business partner.
SOLUTION DESCRIPTION:
For retrieving the default VAT-code when a sales order line is entered for a business partner, the system now checks the tax
number on the address. If that is empty, it checks for the tax number on the business partner.
If either one is found, the system checks to see if EC-rules apply to retrieve the default VAT-code.
If both are empty or EC-rules do not apply, destination sales tax or domestic VAT are used to retrieve the default
VAT-code.

Solution: 124748
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Incorrect signal " Order must be transferred, Transfer is late" is generated when simulating orders.
This happens for orders which have a start date in the future, within the time fence.
The correct signal would be:"Planned order within time fence. Release order "
This signal ("Planned order within time fence. Release order") is never generated.
SOLUTION DESCRIPTION:
Extended check on Planned Order startdate to generate the correct signals.
For orders with startdate before today, signal " Order must be transferred, Transfer is late" is generated.
For orders with startdate on or after today and the difference between timefencedate and startdate is greater than the defined
tolerance, signal "Planned order within time fence. Release order" is generated.

Solution: 124754
SITUATION IDENTIFIED IN:
"Inventory Receipt Transactions" (whina1512m000)
SITUATION DESCRIPTION:
When processing a positive inventory adjustment for MAUC valuated items the inventory increase is registered against the
MAUC value for the material and operation cost components only. The surcharges are recalculated at the moment of receipt
in stead of directly taken the MAUC amount for the surcharge component. This can result in an incorrect MAUC value.
Especially when adjusting inventory for manufactured items the problem will become visible as can be seen in below mentioned example:
MAIN ITEM (50 EUR)
|
|-----------------------------------
--
---
------|
COMPONENT 1 COMPONENT 2
(20 EUR) (30 EUR)
For item 'MAIN ITEM' a
receipt surcharge of 1 EUR is defined
For item 'COMPONENT 1'
a receipt surcharge of 2 EUR is defined
For item 'COMPONENT 2'
a receipt surcharge of 3 EUR is defined
The first transaction for item 'MAIN ITEM' is an
adjustment of 1 pcs. Since this is the first transaction and no MAUC value is available yet this transactions will be
valuation against the FTP price (56 EUR):
Material = 50 EUR (Booked both debit and credit with aggregated cost component)
Surcharge = 6 EUR (Booked debit with aggregated cost component and credit with detailed cost component)
As a result of this transaction the MAUC will become:
Material = 50 EUR
Surcharge = 6 EUR
The second transaction for item 'MAIN ITEM' is
again an adjustment of 1 pcs. Since a MAUC value is now available the receipt will be done (partially) against this MAUC
value:
Material = 50 EUR (Booked both debit and credit with aggregated cost component)
Surcharge = 1 EUR (Booked debit with aggregated cost component and credit with detailed cost component)
What happens is that the surcharge is recalculated based on the surcharges applicable for the received item. These
surcharges do not include the surcharges of the components as the FTP price does.
As a result of this transaction the MAUC will become:
Material = 50 EUR
Surcharge = 3.5 EUR
The reason for recalculating the surcharge amount upon receipt is because at this point its not known anymore out of
which detailed cost components the total MAUC surcharge amount is made up.
SOLUTION DESCRIPTION:
Now also the total surcharge amount of the MAUC value is logged in case of a positive inventory adjustment. This is done
in the following way:
1) Total surcharge amount per component is determined
2) The surcharges applicable for the counted item are calculated and logged detailed.
3) The remaining surcharge is logged aggregated.
The same situation as described in the section
'situation description'. No differences
are there for the first transaction. After this transaction the MAUC still is:
Material = 50 EUR
Surcharge = 6 EUR
The difference does occur when valuating the inventory increase against MAUC which is from the second transaction onwards.
The second transaction is an adjustment of 1 pcs. This transaction will be valuated against MAUC. This will lead to the
following financial transactions:
Material = 50 EUR (Booked both debit and credit with aggregated cost component)
Surcharge = 1 EUR (Booked debit with aggregated cost component and credit with detailed cost component)
Surcharge = 5 EUR (Booked both debit and credit with aggregated cost component)
What is changed is that the surcharge is recalculated upon receipt and booked with the detailed cost components. The
remaining surcharge will be booked aggregated.
As a result of this the MAUC will remain:
Material = 50 EUR
Surcharge = 6 EUR

Solution: 124765
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads " (whinh4275m000)
SITUATION DESCRIPTION:
An ASN is prepared for the parent Business Partner (BP), where it should not have been prepared at all, because the child
BP had the Buy-from, Sold-to, Ship-to and Invoice-to role and hence it should have been defined in EDI Messages
Supported by Business Partner (ecedi0511m000).
SOLUTION DESCRIPTION:
Solution 124312 enabled the possibility to prepare EDI messages for the parent Business Partner (BP) when no message can
be generated for the child. The intended functionality is that an Advanced Shipment Notice (ASN) or an Invoice can be
prepared for a BP having only a Ship-to or Invoice-to role, respectively.
Example for ASN:
A sales order is created via EDI and released to warehousing. The Ship-to BP is different from the Sold-to BP, and has
only the Ship-to role (and NO Sold-to and Buy-from role). When confirming the shipment, an EDI message will be prepared if
an EDI message for the parent will be defined but not for the child.

Solution: 124766
SITUATION IDENTIFIED IN:
"Generate EDI Messages " (ecedi7201m000)
SITUATION DESCRIPTION:
Some EDI standards require the usage of the "Reference A" field (tdsls400.refa) of the sales order header in the outgoing
ASN. Information in the "Reference A" field is transferred to the warehouse order header ("Reference": whinh200.refe). The
warehouse order header data are not supported currently.
SOLUTION DESCRIPTION:
The program script has been modified to support the warehouse order header data in the outgoing ASN. So the "Reference" field will be filled in the
outgoing ASCII file. The warehouse order header data are read at shipment line level.

Solution: 124772
SITUATION IDENTIFIED IN:
"Print Where used PBOM (Summarized)" (tibom1415m000)
SITUATION DESCRIPTION:
While Printing Where used PBOM Components, the system prints the expired component as a component of itself
SOLUTION DESCRIPTION:
In the case of Multilevel printing, the system has to print the BOM component for expired components also. But the system
should not print for the first level component alone.

Solution: 124775
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Consider a Parent BP with only Invoice-to role and Pay-by role defined. This parent has two childs. One child has Sold-to
Role and Invoice-to role defined and the other child has Sold-to and Ship-to roles defined.
Now if a sales order is raised with Sold-to role of the first child and Ship-to role of the second child, then the Ship-to role is
filled as empty in the invoice created.
SOLUTION DESCRIPTION:
Now the Ship-to role is filled correctly.

Solution: 124778
SITUATION IDENTIFIED IN:
"Print Purchase Order Reports" (tdpur4405m000)
SITUATION DESCRIPTION:
When all the options are used, the system doesnot print the output.
SOLUTION DESCRIPTION:
Now when all the options are used also, the system prints the output.

Solution: 124782
SITUATION IDENTIFIED IN:
"Run Detail SRP" (tssoc2265m000)
SITUATION DESCRIPTION:
When Detail SRP is run using the session "Run Detail SRP"(tssoc2265m000),the preferred engineer attached to the object is
never taken into consideration for planning the service order.
SOLUTION DESCRIPTION:
Detail SRP will now take the preferred engineer of the object attached with the first activity of the service order. If there is
no preferred engineer for the object or the object is not present for the first activity, then the preferred engineers are got
from the configuration. Detail SRP will also take into consideration other service engineers present in the service center for
which it is run. The order will be assigned to the alternate engineers only if it is not possible to assign the preferred engineer
to the service order for various reasons.

Solution: 124792
SITUATION IDENTIFIED IN:
"Create Purchase Order History by B.P and Item" (tdpur5501m000)
"Created Purchase Order History by Item" (tdpur5503m000)
SITUATION DESCRIPTION:
In the sessions, 'Create Purchase Order History by B.P and Item (tdpur5501m000)' and 'Created Purchase Order History by
Item (tdpur5503m000)', when the Specific Option 'Only Last Entry by Order/Position' is selected, fields 'Price' and 'Price
Unit' are displayed blank.
SOLUTION DESCRIPTION:
Now, the values of these fields are properly displayed with correct values.

Solution: 124795
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
Normally the Carrier entered in the sales order line would be defaulted to the corresponding purchase order line. But in case
a contract is linked to the purchase order line, the carrier is blanked out in the Purchase Order Line. The Carrier has been
blank in the purchase contract. The same is defaulted to the purchase order line.
SOLUTION DESCRIPTION:
Normally when the carrier is filled in the contract, it means an agreement being present between the supplier and the purchase office that certain Carrier would be used for the delivery of those items. Hence the current defaulting from contract would be there as it is. But, if it is blank there in the contract, then the purchase order line Carrier would not be blanked any more.

Solution: 124796
SITUATION IDENTIFIED IN:
"Anticipated Receipts(Details)" (tfcmg2117s000)
SITUATION DESCRIPTION:
When entering a journal transaction, the Debit line that is associated with this header is not been created and so the batch is not balanced.
SOLUTION DESCRIPTION:
When entering a journal transaction, the Debit line that is associated with this header is been created correctly and so the batch is balanced now.

Solution: 124797
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When a purchase order is maintained for a TP project, the warehouse field is filled with the default value from item purchase data. This is wrong. The warehouse should not be a normal warehouse.
SOLUTION DESCRIPTION:
Now when a purchase order is maintained for a TP project , the warehouse field will be made empty.

Solution: 124810
SITUATION IDENTIFIED IN:
"Convert Requisition Lines to RFQ/PO" (tdpur2201m000)
SITUATION DESCRIPTION:
Ship from Business Partner in the session "Supplier's per RFQ" (tdpur1505m000) is wrong when two Requisitions are
converted together, first one to a Purchase Order and second one to an RFQ.
SOLUTION DESCRIPTION:
Now the Ship from Business Partner is correctly filled in the session "Supplier's per RFQ" (tdpur1505m000) .

Solution: 124815
SITUATION IDENTIFIED IN:
"Perform ABC Analysis by Item" (whina6210m000)
SITUATION DESCRIPTION:
When the Item Issue (History) field is unchecked in the "Inventory Reporting Parameters" (whinr0100s000) the user cannot
open the session "Perform ABC Analysis by Item" (whina6210m000) session. Still should be able to open the session,
because within the session the user can select Perform ABC Analysis by Warehouse.
SOLUTION
DESCRIPTION:
The session would not open when both 'Item Issue (History)' and 'Item Issue by Warehouse(History)' are unchecked in the "Inventory Reposting Parameter" (whinr0100s000).
If 'Item Issue (History)' alone is checked, 'Perform ABC analysis by Item' alone would be enabled in session whina6210m000. If ''Item Issue by Warehouse(History)' ' alone is selected, 'Perform ABC analysis by warehouse' alone would be enabled.

Solution: 124821
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
-1- When sales order lines are added to a sales order using the Copy Bill of Material functionality from session Sales Order
Lines (tdsls4501m000) the fields carrier and route are not taken over from the Sales Order header.
-2- It should not be possible to recalculate the price and discount of the Sales Order Line from the specific option "
recalculate the price and discount of the Sales Order Line" in the session Sales Order Lines (tdsls4501m000), if the Sales
Order Line cannot be modified.
SOLUTION DESCRIPTION:
-1- This source of this error is pure technical. From now on the fields carrier and route will be taken over from the header if
the Copy Bill of Material functionality is used. The fields will be filled on Sales Order line level based on the fields
present on the Sales Order header. If the field on Order header level are changed during input the changed values will be
carried over to the added Sales Order lines.
-2- If the Sales Order Line cannot be modified anymore, the price and discounts will not be recalculated.

Solution: 124823
SITUATION IDENTIFIED IN:
"Generate Invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
With self-billed invoices, the Average purchase prices for items were not calculated correct, when the method of calculating
average purchase price is "Current Inventory". The current receipt in such a case is added to the old stock, because of which
the current received quantity is counted twice
SOLUTION DESCRIPTION:
The situation occurred because the current received quantity was counted twice. This is no longer done now.
Solution: 124827
SITUATION IDENTIFIED IN:
"Print Forecast Components by Date/Currency" (tfcmg3420m000)
SITUATION DESCRIPTION:
If a 'Sales Invoice' is selected as 'Forecast Component' on session 'Print Forecast Components by Date/Currency'
(tfcmg3420m000) the layout of the report is not showing the Document Number. The report layout has to be the same for
Purchase Invoices and Sales Invoices.
SOLUTION
DESCRIPTION:
When 'Sales Invoices' are printed, report tfcmg342011000 shows the Sales Invoice document number, the layout used is exactly
the same than the Purchase Invoices one (which is already showing the document number).

Solution: 124832
SITUATION IDENTIFIED IN:
"Cash Management Transactions" (tfcmg2120s000)
SITUATION DESCRIPTION:
In the session "Bank Transactions", the user enters some amount in the field "sundry costs/bank costs"and tries to split up
the sundry costs/bank costs into 2 different ledger accounts in the session "Cash Management Transactions".
When trying to enter second document the sequence number is not incremented which causes error message ""Record already exists"
SOLUTION DESCRIPTION:
Now the record is getting saved when a second document is inserted .The sequence number is updated accordingly.

Solution: 124834
SITUATION IDENTIFIED IN:
"Print Purchase Invoices" (tdpur4404m000)
SITUATION DESCRIPTION:
When 'Print Already Printed Invoices' check box is selected in session "Print Purchase Invoices (tdpur4404m000)", even the
lines that are not received are getting printed.
SOLUTION DESCRIPTION:
Now the order line would get printed in session "Print Purchase Invoices (tdpur4404m000) with 'Print Already Printed
Invoices' check box selected only when the following conditions are met
* The activity "Print Purchase Invoices (tdpur4404m000)" should have been already been executed for that line.
* For re-executing the activity "Print Purchase Invoices (tdpur4404m000)", the current activity of the order line should
allow as defined in session "Re-execute Activities by Order Type and Activity" (tdpur0561m000)

Solution: 124838
SITUATION IDENTIFIED IN:
"Maintain Production Bill of Materials" (tibom1110m000)
SITUATION DESCRIPTION:
System shows Main Item's Description for component when new record is created using shortcut keys
SOLUTION DESCRIPTION:
The description of the component is shown correctly. Also, the length, weight, unit fields are enabled correctly

Solution: 124842
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Item and Warehouse" (whina1210m000)
SITUATION DESCRIPTION:
If 'Inventory Valuation by Warehouse' check box is selected in the session "Perform Inventory Valuation by Item and
Warehouse" (whina1210m000), strange characters 'VVVVVVVVVVVVVVVVVVV' are printed at the bottom of the report,
just above the line where 'Grand Total' is printed.
SOLUTION DESCRIPTION:
All those unwanted characters are not printed now.

Solution: 124850
SITUATION IDENTIFIED IN:
"Select Values for GRNI Reconciliation" (tfacp1235m000)
SITUATION DESCRIPTION:
In situation where the logistic and finance companies are different, then when running the session "Select Values for GRNI
Reconciliation" the error message "Integration Transaction (tfgld418) not found" is set for many integration transactions.
Also the records selected into table "Interim table for Receivable Invoices" (tfacp135) do not have order numbers and hence
the reconciliation goes wrong.
SOLUTION DESCRIPTION:
The selection is checking the correct company and the error message is not coming anymore. Also the order number is getting filled up, while inserting in table tfacp135, and hence the reports print data correctly.

Solution: 124852
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2525m000)
SITUATION DESCRIPTION:
It is impossible to advise and ship more goods than were ordered.
SOLUTION DESCRIPTION:
New functionality is implemented in order to make "over deliveries" possible.
In session "whinh0100s000" (Inventory Handling Parameters) a parameter "Over Deliveries" is added. Here the percentage of
allowed over delivery is entered.
Based upon the allowed over delivery the "Maximum Quantity" in the warehousing order header is determined.
This is done for orders type "sales", "sales manual", "transfer" and "transfer manual". Over delivery is not allowed for other order types.
The ordered quantity can be exceeded by adding a manual advice or by changing an existing (manual or generated) outbound
advice.

Solution: 124858
SITUATION IDENTIFIED IN:
"Match Electronic Bank Statements" (tfcmg5212m000)
SITUATION DESCRIPTION:
A wrong Anticipated document was matched instead of original document during automatic match process. Also the statuses
of the matched documents were incorrect.
SOLUTION DESCRIPTION:
Now the original document is matched during the process of automatic match. Also the correct statuses were shown to the
document.

Solution: 124860
SITUATION IDENTIFIED IN:
"Update Vendor Rating" (tdpur8850m000)
SITUATION DESCRIPTION:
Unwanted error messages are printed many times for the same order & position while updating Vendor rating using "Full Update".
SOLUTION DESCRIPTION:
Now, the repeating messages are reduced & the error report is printed properly.

Solution: 124866
SITUATION IDENTIFIED IN:
"Assign Unallocated / Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
The document date and fiscal period of assignments can be inconsistent, when a linking document is used to do the
assignment (via session "Assign Advance / Unallocated Receipts to Invoices - tfcmg2130s000" to session "Assign
Unallocated/Advance Receipts to Invoices - tfcmg2105s000"). This causes problems with several reports, such as the aging
analysis (tfacr2420m000).
SOLUTION DESCRIPTION:
When a linking document is used to do the assignment, the document date will be the "Transaction Entry Date" of the financial batch used in session "Maintain Transactions - tfgld1101m000".
This is a change of functionality that will be valid from the release of this solution onwards. A correction program to change the document date of existing data will
not be provided.

Solution: 124869
SITUATION IDENTIFIED IN:
"text editing" (tttxt2230s000)
SITUATION DESCRIPTION:
Change language not possible without entering text in current language. Even not possible when text is present in the other language.
SOLUTION DESCRIPTION:
The previous fix was not complete. One object was missing. the object tttxt2230 was missing.
This solution will contain that object. The solution text of the previous solution was: The previous fix introduced a message that entering of text is mandatory before switching to an other language. Now this fix is changed so that it will be possible to switch to other language without entering any data.

Solution: 124871
SITUATION IDENTIFIED IN:
"Generate self billed invoices" (tfacp2290m000)
SITUATION DESCRIPTION:
When doing the selfbilling procedure then the invoice amount is in the same currency as the order currency. Still in some
occasions the invoice amount in purchase does not correspond afterwards with the invoice amount in finance. It appears that
during the selfbilling process first a recalculation through the reference currency is performed which should not be done
when the currencies are the same.
SOLUTION DESCRIPTION:
Now no recalculation through the reference currency is done when the order currency and the invoice currency are the same
(which is always the case with selfbilling).

Solution: 124872
SITUATION IDENTIFIED IN:
"Inbound Advice" (whinh2515m000)
SITUATION DESCRIPTION:
When running session "Inbound Advice" from a function server, the session works very slowly. A start filter applies to the
session to view only the advices that are not yet put away. This option is not needed when running from a function server,
but it also cannot be unchecked.
When running the session "Inbound Advice" manually, the user is able to check and uncheck the filter via the specific
option.
SOLUTION DESCRIPTION:
When starting the session from a function server, no filter will apply.

Solution: 124875
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1. The Purchase Order generated from service is released to warehouse.
2. After that the item is changed in the Purchase Order line.
3. The 'Warehouse' field becomes blank now and the status of the line also changes to 'Awaiting Receipts'.
4. But the Warehouse Orders generated for the previous item are not deleted.
SOLUTION DESCRIPTION:
When the item is changed, the 'Warehouse' field would not become blank now. Even if the value of the 'Warehouse' field
changes, it would be updated in the warehousing order.

Solution: 124878
SITUATION IDENTIFIED IN:
"tfacp2290m000" (Generate Invoices by SelfBilling)
SITUATION DESCRIPTION:
When running the session Generate Invoices by SelfBilling, fatal error 606 (Reference not found ) occurred . The error log
shows there is no reference between tfacp251.cmba and tfacp245.cmbb. This error occurred after the installation of the
solution 124194, in the following situations.
1. In B50_c versions, when the session is run with the compression option "on".
2. In B50_b and B50L_b versions, when the Invoice generation is based on packing slip.
3. In case of B50J_b (Japanese Localization), in addition to the situation mentioned in point 2, it also occured when the localization parameter Statement of Accounts (tccom936.stac.l) is switched on.

SOLUTION DESCRIPTION:
The situation occured because the fields receipt number (tfacp251.rcno) and sequence number (tfacp251.rseq) were not populated , in the scenarios mentioned . Now these two fields are populated, and the reference error no longer occurs.

Solution: 124880
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When an unallocated receipt is linked to another unallocated receipt, it is not possible to reverse the assignment.
SOLUTION DESCRIPTION:
Earlier, when an unallocated receipt is linked to another unallocated receipt, it is not possible to reverse the assignment.
Now, it is possible to reverse the assignment made to the unallocated receipt.
Solution: 124883
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When the user does a receipt for ZERO quantity for a Purchase Schedule Line with Final Receipt ticked and confirms the receipt line, system changes the status of the corresponding schedule line to "Partial Receipt" instead of changing the status to "Final Receipt". Also, there will not be an Expected Order Line in session "Expected Order Lines (whinh3820m000)" to receive the remaining quantity. This is wrong. The status of the Purchase Schedule Line should be changed to "Final Receipt" when the user ticks the Final Receipt field while making receipts against this Purchase Schedule Line. This happens only when the user makes a receipt for a quantity of ZERO.
SOLUTION DESCRIPTION:
An unnecessary check was done for ZERO receipt quantity when the user confirms this Receipt with Final Receipt ticked which causes the wrong status on the Purchase Schedule Line. Now changes are made such that when the user tries to confirm a receipt for ZERO quantity done for a Purchase Schedule Line with Final Receipt ticked, system changes the status of the corresponding Purchase Schedule Line to "Final Receipt".

Solution: 124884
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0501m000)
SITUATION DESCRIPTION:
When a new production order is created BaanERP creates Inventory Commitments for all materials. Also when a new material
is added to an existing production order, an Inventory Commit is created. This is functionaly wrong. Inventory Commitments
should be created only in acceptional cases, and must therefor be created manually.
SOLUTION
DESCRIPTION:
Inventory Commitments are not created anymore during the creation of new production order materials.

Solution: 124886
SITUATION IDENTIFIED IN:
"Integration Transactions by Project / Order" (tfgld4510m000)
SITUATION DESCRIPTION:
When making the service order labor cost line 'costed', financial transactions are made. In case the employee who has done
the labor is from a different department (with different financial company, e.g. 805) than the service order department (e.g
fin comp 806), bookings are not done correctly. Wrong result:

Debit: Approved for invoicing (fin comp 806)
Credit: Approved for invoicing (fin comp 805)
SOLUTION DESCRIPTION:
When booking labor WIP, the following bookings are made:
Debit: Operation costs (fin comp 806)
Credit: Operation costs (fin comp 805)
When making a labor cost line 'costed', the following bookings are made:
Debit: Approved for invoicing (fin comp 806)
Credit: Approved for invoicing (fin comp 806)
When doing the bookings for Warranty, FCO, and Internal service costs, it works the same with respect to the financial
companies.
Concluding: when closing WIP (setting cost line to 'costed'), the bookings are done for the financial company of the
department of the service order.

Solution: 124898
SITUATION IDENTIFIED IN:
"Integration of Operation Rates / Surcharges" (tffbs1230m000)
SITUATION DESCRIPTION:
Only one Project was integrated.
SOLUTION DESCRIPTION:
The selection of the Project Range was corrected.

Solution: 124902
SITUATION IDENTIFIED IN:
"Write off Currency Differences" (tfacp2240m000)
SITUATION DESCRIPTION:
When running session "Write of Currency differences - tfacp2240m000/tfacr2250m000" in SIMULATE mode, it`s not
possible to do so for Unallocated Payments/Receipts and Advance Payments/Receipts. No data is displayed
SOLUTION DESCRIPTION:
It`s now possible to SIMULATE a Write of Currency differences for Unallocated Payments/Receipts and Advance
Payments/Receipts .

Solution: 124906
SITUATION IDENTIFIED IN:
"Update Sales Statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
The Sales Statistics are updated incorrectly in "Update Sales Statistics" (tdsst0201m000) when the retry point is not
correctly set. This gives wrong results.
SOLUTION DESCRIPTION:
When the retry was being used it could occur that certain records were being skipped. To prevent this from happening a
small change had to be made to prevent this.

Solution: 124908
SITUATION IDENTIFIED IN:
"Select Values for GRNI Reconciliation" (tfacp1235m000)
SITUATION DESCRIPTION:
While selecting the values for GRNI Reconciliation by running session "Select Values for GRNI Reconciliation"
(tfacp1235m000), the Integration transactions which are getting picked up are inserted in the Interim table (tfacp135)
without Purchase Order Number.
SOLUTION DESCRIPTION:
The integration transactions are getting inserted correctly and hence the reports are printed with correct values.

Solution: 124916
SITUATION IDENTIFIED IN:
"Sales Statistics Parameters" (tdsst0100m000)
SITUATION DESCRIPTION:
The wrong text (Business Partner For Address) was displayed on the fourth form from session Sales Statistics Parameters
(tdsst0100m000).
SOLUTION DESCRIPTION:
A different text (Contact For Business Address) is displayed on the fourth form from session Sales Statistics Parameters
(tdsst0100m000).

Solution: 124917
SITUATION IDENTIFIED IN:
"Installment Orders" (tdsls4506m000)
SITUATION DESCRIPTION:
The last invoice amount is not correct in case of installment orders.
An sales order with an amount of $ 1000 has the following installment lines:
Installment line 1 of $ 1000, type advance
Installment line 2 of $ -1000, type advance
Installment line 3 of $ 600, type advance
Installment line 1 of $ 400, type normal
After processing all advanced installment lines and processing the order in warehousing the last installment lines of $ 400 is
deleted. After this the installment order is closed. While closing a correction should be made of $ 400, since this is not
done the invoice amount of the last invoice will become 0 (zero) instead of the expected $ 400.
SOLUTION DESCRIPTION:
The reason for this to go wrong is that while closing the installment order a check is done if the settled amount is greater
then the total goods amount a correction should be created. Since the installment line of $ 400 was deleted this went wrong.
Now the calculation whether corrections should be made while closing the installment order is changed and the last invoice
will now have an amount of $ 400 instead of $ 0 (zero).

Solution: 124921
SITUATION IDENTIFIED IN:
"Purchase Order Headers" (tdpur4100s000)
SITUATION DESCRIPTION:
A Purchase Order line is linked to a receipt. When the delivery date is changed in the Header and if the question to modify
the lines is answered Yes, the link with the Warehousing is broken and the delivery date is changed.
SOLUTION DESCRIPTION:
Now, if a Purchase Orderline is linked to the receipt, the Delivery date of the lines will not be changed and hence the link
with Warehousing will remain intact.

Solution: 124926
SITUATION IDENTIFIED IN:
"Calculate Currency Difference" (tfgld5201m000)
SITUATION DESCRIPTION:
Problem #1- (B40_c only)
Transactions created by the session "Calculate Currency Difference" (tfgld5201m000) have fields "Journal Book Code" and
"Registration Date" not filled in the non-finalized transaction table (tflgd102). As a result, the batch can not be finalized
as the error " 'Libro giornale' not found or empty' is always given.
Problem #2- (B50_b and B50_c only)
Transactions created by the session "Calculate Currency Difference" (tfgld5201m000) have fields "Section Code" and
"Transaction Entry Date" not filled in the non-finalized transaction table (tflgd102).
Problem #3- (B50_b and B50_c only)
There are several error checks done on the currency difference profit and loss
ledger accounts that are filled in the company parameters. If any of
these checks failed the program would display 'No Data
Within Selection' and the process
would be stopped.
SOLUTION DESCRIPTION:
Problem #1-
Table fields "Journal Book Code" and "Registration Date" now get filled and the currency difference batch can now be
finalized.
Problem #2-
Table fields "Section Code" and "Transaction Entry Date" now get filled when creating currency difference transactions.
Problem #3-
If the currency difference ledger account does not pass error checks, an error message that describes the problem will now
be displayed.

Solution: 124928
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
Outbound advice is not generated when the item transfer is between non-location controlled item to the location controlled
item. The error message
********************************************************************************************
"Location XXXXX not defined as the Receiving Location in the warehouse XXX"
*********************************************************************************************
comes up and the user cannot proceed further.
SOLUTION DESCRIPTION:
Now the outbound advice can be generated for Item-transfer orders.

Solution: 124930
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
In Cross-docking function , Even if Confirm Shipments/Loads is not set as an activity in shipments procedure, Confirm
Shipments/Loads has to be done manually when inspection is needed for the item.
SOLUTION DESCRIPTION:
Now the system automatically confirms the shipments if the activity Confirm Shipments / Loads is not set as an activity

Solution: 124934
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
If the discount percentage on order line level exceeds 100 percent, the Baan System generates a Fatal Error in German and
Dutch language.
SOLUTION DESCRIPTION:
This Fatal Error came because the words '100 percent' were translated from English to Dutch and German as '100%'. The Baan
Tools are not able to handle the %-sign in messages. Instead of using the %-sign now the full word is used as translation.
The %-sign is a predefined character, hence this should not be used in a standard message text.

Solution: 124943
SITUATION IDENTIFIED IN:
"Generate Order Advice" (whina3200m000)
SITUATION DESCRIPTION:
There are two SIC items and the first item has a supplier linked to it with a record being present in "Item Supplier
Information" (tdipu0501m000). For the second item there is no supplier linked. When the order advice is generated via the
session "Generate Order Advice" (whina3200m000), two Purchase Order Advices are generated. The Supplier for the advise of
the second item uses that of first item. Instead, it should have been blank.
SOLUTION DESCRIPTION:
Now the supplier in the advice would be blank for the second item that has no Item Supplier Information.

Solution: 124946
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
It is not possible to generate an outbound advice for a warehouse order type "Transfer Manual" from WAREHOUSE to
PROJECT for a lot controlled item.
SOLUTION DESCRIPTION:
The system allows generating an advice for a warehouse order type "Transfer Manual " from WAREHOUSE to PROJECT for
a lot controlled item.

Solution: 124948
SITUATION IDENTIFIED IN:
"Assign Credit notes to invoices" (tfacr2121s000)
SITUATION DESCRIPTION:
When we try to assign a credit note to an invoice (which is not doubtful), we get message tfacrs0160 "Original invoice is
doubtful".
It happens when the first invoice shown in session "Assign Credit notes to invoices" tfacr2121s000 is doubtful.
SOLUTION DESCRIPTION:
Now no such message is shown when the invoice is not doubtful. Its shown only when the selected invoice is Doubtful.

Solution: 124951
SITUATION IDENTIFIED IN:
"Labor transactions to be Invoiced" (tppin4558m000)
"Equipment transactions to be Invoiced" (tppin4559m000)
"Subcontracting transactions to be Invoiced" (tppin4560m000)
SITUATION DESCRIPTION:
When the sessions 'Cost Pus Tansactions to be Invoiced' for the cost types Labor, Equipment or Subcontracting (
tppin4558m000, tppin4559m000 and tppin4560m000 ) are started by the 'Run program' option, there is no data displayed at
first. Only when the screen is refreshed (e.g. by the F5-key) the data is shown.
SOLUTION DESCRIPTION:
When the sessions 'Cost Pus Tansactions to be Invoiced' for the cost types Labor, Equipment or Subcontracting are started by
the 'Run program' option, the data is now displayed directly.

Solution: 124953
SITUATION IDENTIFIED IN:
"RFQ Header" (tdpur1101s000)
SITUATION DESCRIPTION:
Request for Quotation Date in RFQ Header is displayed wrong
SOLUTION DESCRIPTION:
The RFQ Date is displayed correctly

Solution: 124957
SITUATION IDENTIFIED IN:
"Maintain Solutions" (ttpmc1100m000)
SITUATION DESCRIPTION:
The session "Maintain Solutions" (ttpmc1100m000) doesn't allow you to export solutions when not all recommended
dependencies are present. Recommended dependencies are those dependencies, which would be generated when this option
is used from "Maintain Dependencies" (ttpmc1140m000).
SOLUTION
DESCRIPTION:
Instead of blocking the export of the solution, you will be warned about the missing recommended dependencies, but you can continue with the export process.
Please note that leaving out (some of the) recommended dependencies may result in inconsistent systems at the recipient side.

Solution: 124959
SITUATION IDENTIFIED IN:
"Elements" (tpptc1500m000)
SITUATION DESCRIPTION:
We can delete an element from "Elements" even when we have a element forecast (Manually generated) in any of the cost
transactions. This is not correct, because the next time we generate a forecast based on previous date, this element will also
be considered & an forecast will be generated even when there is no element present.
SOLUTION DESCRIPTION:
A check for presence of forecast lines will be made before deleting the element & if forecast lines are found, a message will come & the element will not be deleted.

Solution: 124960
SITUATION IDENTIFIED IN:
"Maintain Database Users" (ttdba0115m000)
SITUATION DESCRIPTION:
When adding or deleting a database user, the setting of msql_serverhost is not taken in account. Therefore it is tried to delete the user in the "(local)" database.
In case "(local)" does not exist (for example in case the Ms SQL Server resides on another system), the following error is given:
ttdba01155 : Maintain Database Users (message) Error 1 occurred while executing program.
SOLUTION DESCRIPTION:
A fix is made in msql7_maint.exe which solves this problem. This msql7_maint.exe will be delivered with portingset 7.1c.04.
Also a fix is made in object ottdba0115.
Depending how you set msql_serverhost it can be necessary to have this modified object installed also. *)
First try whether the msql7_maint.exe of portingset 7.1c.04 solves the problem, if not, also install this pmc solution,
containing this modified object.
*) In case msql_serverhost is set in $BSE/lib/db_resource file, or specified as system name in the Database Definition.

Solution: 124961
SITUATION IDENTIFIED IN:
"Convert Requisition Lines to RFQ/PO " (tdpur2201m000)
SITUATION DESCRIPTION:
When the requisition lines are converted to Purchase Order, updation of status of Purchase Requisition Approval is not
done.
SOLUTION DESCRIPTION:
Now the updation of status of Purchase Requisition Approval takes place and all the requisition lines are converted
correctly.
Solution: 124962
SITUATION IDENTIFIED IN:
"Copy Projects" (tppdm7840m000)
SITUATION DESCRIPTION:
When a project is copied to a new project and the original project has a text attached to it, then the text is not copied to the
new project.
SOLUTION DESCRIPTION:
The text on a project is now copied along with the other project data to the new project.

Solution: 124967
SITUATION IDENTIFIED IN:
"Print Service Financial Reconciliation" (tcfin3400m000)
SITUATION DESCRIPTION:
Following issues where found:
1) Debit/Credit indicator is not printed for report 'Service Financial Reconciliation (Totals by Ledger Account)'.
2) The cost amount per service order costline is sometimes missing in report 'Service Financial Reconciliation'.
3) The selection criteria printed in the header, show the Service Office TO, in the Service Order TO field.
4) It is possible to encounter a fatal error 506 (table does not exist). This is caused by the fact that the system tries to find
the table "BaanService Financial Reconciliation" (tcfin300) even if this table does not exist for that company.
SOLUTION DESCRIPTION:
1) Debit / Credit indicator is printed for all amounts.
2) Per Service Order Actual Cost line more financial bookings are possible. The printout is sorted by Service Order Costline
and will show in the first printed booking the cost amount of that particular Service Order Cost Line. In the same line the
cost component will be displayed. Both fields are omitted in the subsequent bookings for the same Cost Line.
3) The Service Office To and the Service Order To selection will be printed behind the respective labels in the report.
4) The system now checks if the table "BaanService Financial Reconciliation" (tcfin300) exists for every company that is
selected for printing.
Also 2 enhancements are applied:
1) Check Box 'Print Related Ledger" has been added. When
selecting one or more ledger accounts you can select this option.
Each financial transaction has a debit and a credit posting. Usually the debit and credit amounts are posted to different
ledger accounts.
If this check box is selected, both posting amounts will be printed.
If this check box is cleared only the amounts for the selected ledgers will be printed.
2) In the 'Totals by Ledger Account' report a balance amount is added per ledger account.

Solution: 124971
SITUATION IDENTIFIED IN:
"Select Bus.part. Receipts for Interest Invoices" (tfacr5210m000)
SITUATION DESCRIPTION:
A fatal error was displaying when the interest invoice days exceeded 999 days.
SOLUTION DESCRIPTION:
Now the fatal error is not displaying when the interest days exceeds 999 days.
The representation will done with 999 days, but the interest calculation will be done with the correct number of days.
Message is displayed when this situation is occuring.

Solution: 124972
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh4525m000)
SITUATION DESCRIPTION:
if the lot is filled on the outbound advice, the inventory date can be changed, which leads to fatal errors and/or negative
inventory
SOLUTION DESCRIPTION:
if the lot is filled on the outbound advice, the inventory date is defaulted from the lot, and cannot be changed

Solution: 124984
SITUATION IDENTIFIED IN:
-1-/-3- "Sales Order Line" (tdsls4101s000)
-4- "Sales Order Line Details" (tdsls4101s200)
-2- "Process Delivered Sales Orders" (tdsls4223m000)
-6 - "Release to Warehousing (batch)" (tdsls4246m000)
-7- "Maintain and Confirm Back Orders" (tdsls4125m000)
SITUATION DESCRIPTION:
-1- When trying to cancel a Sales Return Order in the Sales Order Line Details (tdsls4101s200), the message "Warehouse
order line XXXX/YYY with Order origin'Sales' has not been deleted" appeared.
-2- If a Sales Order Line is of the type Consignment Replenishment / Return Order (Cons. Rep. with a negative Order
Quantity), the Sales Order Line could be deleted in the session "Process Delivered Sales Orders" (tdsls4223m000) even if
the corresponding receipt was not yet processed (processed would mean "confirmed" and "inspected -if required-").
-3- The Inventory Shortage Menu appeared in the session "Sales Order Line" (tdsls4101s000) if the order quantity was
negative or the order quantity was reduced. In these cases, no Inventory Shortage Menu should appear.
(Only B50_b)
-4- When cancelling a Sales Order Line Detail in the session Sales Order Line Details (tdsls4101s200), if the Sales Order
Line Detail could not be cancelled, the same error message appeared several times.
-6 - When Releasing a range of Sales Orders to Warehousing using session "Release to Warehousing (batch)" (tdsls4246m000),
for which the Sold-To Business Partners are in descending order, not all Sales Orders are printed on the report.
-7- If the Back Order field (field tdsls401.bqua) was filled in as the full the order quantity could not be committed, it was
possible to confirm the back order even if the Sales Order Line had not be delivered yet.
SOLUTION DESCRIPTION:
-1- The wrong message was beeing generated. When cancelling a Sales Order Line Detail Line, the status of the Warehouse
Order (status of the Outbound Line) created for the Sales Order Line Detail Line will now be checked.
-2- It will not be possible to delete a Sales Order Line is of the type Consignment Replenishment / Return Order (Cons.
Rep. with a negative Order Quantity) in the session "Process Delivered Sales Orders" (tdsls4223m000) if the corresponding
receipt has not be processed.
-3- No Inventory Shortage Menu will appear when maintaining the Sales Order Line of a Sales Return Order or reducing the
order quantity.
-4- If a Sales Order Line Detail cannot be cancelled, the error message will only appear once.
-6 - The selected range of Sales Orders are now being processed in the right order. It was assumed the order of the selected
Sales Order was ascending, which was not always the case.
-7- In this case, it is not allowed to confirm the back order.

Solution: 124985
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When we try to approve a purchase invoice that has been matched to a subcontracting purchase order in a different company,
and that purchase order is linked to a production order that uses a project, the system generates the message:
--------------------------------------------------------------------------------------------------------------------------------------------------------
--
No integration transactions found for logistical order company XXX and order XXXXXXXXX / XX.
--------------------------------------------------------------------------------------------------------------------------------------------------------
SOLUTION DESCRIPTION:
The Purchase Invoice can be approved now in the finance company.

Solution: 124996
SITUATION IDENTIFIED IN:
"Business Processes by Project Model" (tgbrg4560m000)
SITUATION DESCRIPTION:
When we want to use the menu option 'Display Process in User Mode', then we get a message about user not linked and
cannot start any session.
This was not happening in the past and it makes no sense, because we are just modeling.
SOLUTION DESCRIPTION:
This check should not have been added and is now removed again.
So it will be possible to view the process in user mode and also start the sessions in the process.

Solution: 124999
SITUATION IDENTIFIED IN:
"Shift Production Planning" (tisfc1202m000)
SITUATION DESCRIPTION:
During session Shift Production Planning the slack time for operations are recalculated. When the value for this slack time is
outside the range of the corresponding domain, the session aborts with a fatal error 205.
SOLUTION DESCRIPTION:
The value of the calculated slack time is checked against the range of the corresponding domain. In case the value is outside
the range, an error message is given, and the rest of the production order is not processed.

Solution: 125001
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40b
122181
Defects solved in B40c
122181, 124617, 124795
Defects solved in B50b
124617
Defect solved in 71a
122831, 123192, 124617
Descriptions:
- Defect 122181 Enabling of keyfield corrected when enum on first occ.
- Defect 122831 Checkbox handling via spacebar corrected
- Defect 123192 Don't raise multiocc when refresh via single occ.
- Defect 124617 FS Compile error in source generated by stpcreatedll
- Defect 124795 MB Font spacing corrected
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 125005
SITUATION IDENTIFIED IN:
"Enterprise Units" (tgbrg0530m000)
SITUATION DESCRIPTION:
We want to change the company number in the Enterprise Units, which are part of the Operational Enterprise Structure
Model.
SOLUTION DESCRIPTION:
This is not possible. As long as an Enterprise Unit is part of an Operational Enterprise Structure Model (ESM), the
company number is part of the data, which may not be changed.
When you want to change the company number, then you have to copy the Operational ESM to another ESM. Within that
ESM you then make your changes. After that you need to make the new ESM the Operational ESM.
We discovered however that the software was not fully supporting the above procedure. So we changed the software and it
now supports the above described procedure.

Solution: 125008
SITUATION IDENTIFIED IN:
"Print Routing Operations" (tirou1402m000)
SITUATION DESCRIPTION:
While printing 'Routing Operations' in a report, the last record is printed again in the next page of the report after a page
break.
SOLUTION DESCRIPTION:
With the modifications made in the report layout, the last record is not printed again in the next page of the report after a
page break, while printing 'Routing Operations'.

Solution: 125009
SITUATION IDENTIFIED IN:
"Advance Payment Requests" (tppin4510m000)
SITUATION DESCRIPTION:
When we try to link a second advance payment request to an Installment the message tppin0024a "Total advance amount
exceeds installment amount" pops up even when this is not the case.
SOLUTION DESCRIPTION:
The above problem is corrected & now the message "Total advance amount exceeds installment amount" will come only when
the advance amount exceeds the installment amount.

Solution: 125038
SITUATION IDENTIFIED IN:
"Calculate cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
If surcharges are defined for item surcharge, Item by warehouse surcharge, and warehouse surcharge, then the Cost price of
the Item does not include the general warehouse surcharges in the total cost.
SOLUTION DESCRIPTION:
If there are general warehouse surcharges present, then these costs will be included in the cost price of the Item.

Solution: 125042
SITUATION IDENTIFIED IN:
Report Orders Completed (tisfc0120s000)
SITUATION DESCRIPTION:
When some materials are not processed in the Warehouse side and the warehouse orders are open for a Production order,
system is allowing the user to change the warehouse in "Report orders completed" thus changing the destination of the goods.
But the warehouse orders for old warehouse still exists with status blocked. Thus completion of the order is not possible.
SOLUTION DESCRIPTION:
When completing the order, if the user wants to change the destination warehouse to another than the one specified in the production order, the
warehouse (inbound) orders for the parent warehouse have to be cancelled first. Canceling the warehouse orders means completing the order with
value in "Quantity to Deliver" as Zero. If the warehouse (inbound) orders for the original warehouse are open (exist), then the change of warehouse is not allowed in the session "Report Orders Completed".

Solution: 125045
SITUATION IDENTIFIED IN:
"Write off Currency Differences" (tfacp2240m000)
"Write off Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
The processing of' Write-off Currency-Differences' is booking ALL transactions on the 'control-account'.
For Unallocated / Advance the CORRECT control-ledger should be taken from the Supplier/Customer-group.
SOLUTION DESCRIPTION:
For Unallocated / Advance the CORRECT control-ledger is taken from the Supplier/Customer-group now.

Solution: 125054
SITUATION IDENTIFIED IN:
"Determine Phase Numbers" (cprpd6200m000)
SITUATION DESCRIPTION:
Bad performance
SOLUTION DESCRIPTION:
Combined 3 steps and improved the query

Solution: 125055
SITUATION IDENTIFIED IN:
"Release Production Orders" (tisfc0204m000)
SITUATION DESCRIPTION:
When a production order is released with item(s) that have direct initiate inventory on yes and have a signal code which
blocks the prod. issue, there is no error message given that the material has not been issued because it has been blocked for
prod. issue.
SOLUTION DESCRIPTION:
When an item has been blocked by a signal code for prod. issue, than on the erroneous report a message is reported that the
item has been blocked for issue when releasing the production order or initiate inventory issue manually.

Solution: 125060
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Header" (cisli2120m000)
SITUATION DESCRIPTION:
It is possible to enter into the fields of Manual Sales Invoice Header, when it has one or more lines with the status other than ON HOLD.

But the user cannot change any values of the fields in the Manual Sales Header. He can only navigate through the fields.
SOLUTION DESCRIPTION:
Now the functionality is kept the same but the user is not allowed to navigate through the fields as they are now made as
display fields, when it contains one or more lines in status other than ON HOLD. The values in the fields can be changed
only when the status of the respective lines are in status ON HOLD.

Solution: 125064
SITUATION IDENTIFIED IN:
"Copy Company Data" (tccom0214m000)
SITUATION DESCRIPTION:
When running the session "Copy Company Data" (tccom0214m000) to change the number of the company, it is not updating
all the tables in the sequential dump.
SOLUTION DESCRIPTION:
When running the session "Copy Company Data" (tccom0214m000) to change the number of the company, it is now updating
all the tables in the sequential dump.

Solution: 125065
SITUATION IDENTIFIED IN:
"Compose Payments" (tfcmg1240m000)
SITUATION DESCRIPTION:
Session 'Compose Payments' is run and, for any reason, we obtain audit errors or we cancel the composing. After solve the
error, we run, again, the same tfcmg1240m000 session (without closing and re-opening it again) then, the 'Composing Limit'
is not taken into account.
SOLUTION DESCRIPTION:
If session 'Compose Payments' is run with 'Audit errors' and we re-use the same session tfcmg1240m000 again (that means,
without close and restart this session), the 'Composting Limit' is correctly taken into account.

Solution: 125069
SITUATION IDENTIFIED IN:
"Generate Self billed Invoices" (tfacp2290m000)
SITUATION DESCRIPTION:
Whenever the user splits the delivery lines on the purchase order line for a selfbilled order line then the invoice generated
with the session "Generate Self billed Invoices (tfacp2290m000)" has an incorrect amount of 0.
SOLUTION DESCRIPTION:
During selfbilling the invoice amount is calculated for the quantity received. To get the invoice amount the unit price has
to be determined. The unit price is determined by dividing the order amount by the order quantity. It was found that with
backorders the accuracy of the unit price was decreasing and that is why with a former solution always the unit price was
calculated with the sequence number 0 (see tfacp240 record). However if the user splits the receipt lines on purchase order
line level then there is not a record in tfacp240 with sequence number 0, which resulted in the fact that a unit price of 0
was calculated. Now this has been solved by searching for the lowest possible sequence number for a certain purchase order
line in tfacp240.

Solution: 125078
SITUATION IDENTIFIED IN:
"Simulate Master Plan" (cprmp1202m000)
SITUATION DESCRIPTION:
When items configured with lot sizing rules and using Work Load Control (WLC) then lot sizing rules were not taken into
account.
SOLUTION DESCRIPTION:
When items configured with lot sizing rules and using Work Load Control (WLC) then lot sizing rules are taken into
account now.

Solution: 125079
SITUATION IDENTIFIED IN:
"Invoices by Billing Request" (cisli2505m000)
SITUATION DESCRIPTION:
Session does not display records in an archive company.
SOLUTION DESCRIPTION:
Now the records of the live company are displayed in this session in the archive company.

Solution: 125083
SITUATION IDENTIFIED IN:
"Match/Approve Purchase Invoices" (tfacp2507m000)
SITUATION DESCRIPTION:
If the user approves an invoice which is matched to an orderline which is for a cost item related to a PCS project, then the
price variance should post again with transaction origin - financial transaction "Purchase - General Costs" debit to the
calculation office of the PCS project.
SOLUTION DESCRIPTION:
Now also with cost items the calculation office of the PCS (if it is there) project is fetched and used for posting the debit
integration transaction to.

Solution: 125084
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Prompted for print device for each invoice in billing request when using variant reports.
SOLUTION DESCRIPTION:
Now the device window is prompted only for the first time. After that the same device is used to print for the rest of the
invoices.

Solution: 125090
SITUATION IDENTIFIED IN:
"Create Runtime Help" (ttadv5230m000)
SITUATION DESCRIPTION:
The form default values, for the session Create Runtime Help (ttadv5230m000), aren't correct filled.
SOLUTION DESCRIPTION:
The default for session "Create Runtime Help" (ttadv5230m000) is now filled with the Current Package VRC. This is the
same as in the session "Create Runtime Data Dictionary" (ttadv5214m000).

Solution: 125092
SITUATION IDENTIFIED IN:
"Sales-Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
Using the 'Specific / Copy BOM' menu-option when adding Sales Order Lines, having the Sales Order Type parameter
"Execution Mode" (tdsls094.exmo) set to "Interactive", the system should come up with the message "Process this order
immediately?" For normal items the message did show, for BOM items it did not.
SOLUTION DESCRIPTION:
When adding a BOM-item to a Sales Order Line, for a Sales Order with the parameter
"Execution Mode" (tdsls094.exmo) set to "Interactive", the system will show the following message "Process this order
immediately?" when closing the sales order line session.

Solution: 125099
SITUATION IDENTIFIED IN:
"Tool Numbers by Tool Type" (titrp0502m000)
SITUATION DESCRIPTION:
Deleting tool numbers by delete button does not correct the inventory. Tool numbers without last usage date cannot be
deleted through scrap tools globally.
SOLUTION DESCRIPTION:
When deleting a tool number a correction on the inventory is made and when inserting a tool number will fill the last usage
date field so the numbers can be deleted by scrap tools globally.

Solution: 125103
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
If format by Generic Unit is out of range of the domain a float exception can occur during cost price calculation.
SOLUTION DESCRIPTION:
When running cost price calculation the maximum used format of the domain is set, so this cannot be exceeded, which
prevents the float exception error.

Solution: 125110
SITUATION IDENTIFIED IN:
"Service Contracts" (tsctm3100m000)
SITUATION DESCRIPTION:
The moment allocated cost are transferred into spent costs, the allocated amounts of the total contract per configuration line
are not taken into account and are not copied to the spent costs.
SOLUTION DESCRIPTION:
The allocated costs per contract configuration line are now also transferred into spent costs.

Solution: 125115
SITUATION IDENTIFIED IN:
"Generate Invoice by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
When running Generate invoice by selfbilling( tfacp2290m000 ), with the compression option on, Fatal Error 100 on table
tfacp250 is triggered. This happened when there is a return order, or Back orders.
SOLUTION DESCRIPTION:
The situation happened because the pointer was lost on the table tfacp250. This situation occured after the installation of
solution 124823. Now modification has been made so that the pointer is not lost on tfacp250, when running this session.

Solution: 125120
SITUATION IDENTIFIED IN:
"Standard equipment" (tppdm0512m000)
SITUATION DESCRIPTION:
When a standard subcontracting or a standard equipment is deleted using sessions "Standard Subcontracting" (tppdm0513m000)
or "Standard Equipment" (tppdm0512m000), the cost objects are removed from the standard cost object tables in Baan Project.
However, if these cost objects are used in orderlines (e.g. in purchase ) then the corresponding records from the General Item
data are not deleted.
SOLUTION DESCRIPTION:
When trying to delete a subcontracting or equipment cost object, the program will only delete the cost objects (Cost object data and
general item data) if the cost object is not used elsewhere. If it is being used, no data is deleted.

Solution: 125122
SITUATION IDENTIFIED IN:
"Check/change rounding of amounts" (tfcor9996s000)
SITUATION DESCRIPTION:
The correction program "Check/change rounding of amounts" (tfcor9996s000), was not rounding the balance amount fields in
the Open Item tables for Purchase Invoice (tfacp200) and Sales Invoice (tfacr200). The fields are (tfacp200.balc,
tfacp200.balh, tfacp200.bala, tfacp200.bahc) in table tfacp200 and (tfacr200.balc, tfacr200.balh, tfacr200.bala, tfacr200.bahc)
in table tfacr200.
SOLUTION DESCRIPTION:
The balance fields in Open Entries tables (tfacp200 and tfacr200) are rounded correctly.

Solution: 125127
SITUATION IDENTIFIED IN:
"Matched Purchase Invoice Transactions" (tfacp1133s000)
SITUATION DESCRIPTION:
In the session "Matched Purchase Invoice Transactions" (tfacp1133s000), the ledger account entered is related to Project
Costs, and without saving, the option "Baan Project Transactions" is chosen from the specific menu. The related
information is entered and all the project-related sessions are saved and closed. Now when exiting from the session
"Matched Purchase Invoice Transactions", the question "Data has been changed. Do you want to save your changes" is
asked. When the option "yes" is clicked, then the sessions that had been opened when the option "Baan Project
Transactions" was chosen, opens again.
SOLUTION DESCRIPTION:
The option "Baan Project Transactions" is opened only once when adding a new cost transaction.

Solution: 125131
SITUATION IDENTIFIED IN:
"Purge Sales Invoice Data" (cisli3210m000)
SITUATION DESCRIPTION:
When purging Manual invoice data, Fatal error "606 (reference does not exist) on cisli226936 in select" occurred. The system
could not find a reference when inserting the Interim Tax table(cisli226).
SOLUTION DESCRIPTION:
Now the fatal error does not arise.

Solution: 125132
SITUATION IDENTIFIED IN:
"Assign invoices to credit notes" (tfacp2121s000)
SITUATION DESCRIPTION:
Incase no change has been made to the linked amount and Process assignment is done again, the following problems were
observed.
1. The link document for the credit note is deleted.
2. The control account transaction of the assignment document belonging to the credit note is deleted from tfgld102.
3. The balance of the credit note is updated incorrectly.
SOLUTION DESCRIPTION:
Now, when there is no change made to the linked amount, no further processing would be done for that particular
invoice/credit note link.

Solution: 125144
SITUATION IDENTIFIED IN:
"Scan Solution/Patch File" (ttpmc2200s000)
SITUATION DESCRIPTION:
During the scanning of a Patch (Service Pack), it could happen that not all individual solutions, which belong to the Patch
were really attached to the Patch in the Solution Registry at the recipient side.
When the Patch was installed, it was not installed completely.
This only happened when the Patch was rescanned, because the first time it aborted (e.g. due to disk space problems),
without specifying Overwrite = Yes. And even then, only individual solutions, which were already present on the system
(because of scanning them individually or by scanning weekly collections), were not attached to the Patch.
SOLUTION DESCRIPTION:
Now all individual solutions, which belong to the Patch, are attached to the Patch, regardless of Overwrite Yes or No.
Because the user is not always aware that the scanning process aborted, also another change has been made: the patch cannot
be processed in PMC (checked and installed) before the complete patch (the patch itself and its individual solutions) has
been scanned.

Solution: 125152
SITUATION IDENTIFIED IN:
"Planned PRP Purchase Order" (tppss6510m000)
SITUATION DESCRIPTION:
Purchase order line not created with the purchase unit maintained in the session "Planned PRP purchase orders (Material)"
(tppss6510m000). The purchase unit is overwritten with the default purchase unit maintained in the session "Item Purchase
Data" (tdipu0501m000) for the item.
SOLUTION DESCRIPTION:
Now, Purchase order line is created with the purchase unit maintained in the session "Planned PRP purchase orders
(Material)" (tppss6510m000).

Solution: 125153
SITUATION IDENTIFIED IN:
"Sales Invoice Corrections" (tfacr2110m000)
SITUATION DESCRIPTION:
When Sales Invoice Correction is done with session "Sales-Invoice Corrections" (tfacr2110s000), for Invoices with Level of
Tax Transaction as "Transaction Line", then the tax transactions was not getting corrected properly.
When a tax code for a Sales Invoice was changed, the amounts for Tax Analysis, was not getting calculated correctly.
SOLUTION DESCRIPTION:
When a Sales Invoice has Level of Tax Transaction as "Transaction Line", then it is not possible to correct the Sales Invoice
from this session. To correct it, a Credit Note has to be created to reverse the Sales invoice and a new Sales invoice has to
be entered with the correct amounts.
The tax amounts are calculated correctly for the Tax Analysis.

Solution: 125155
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Order discount not printed in the invoice. But in Baan4c, it does get printed.
Line discount amount is printed wrongly if a sales order has more than one line and the line discount of the first line alone is
empty. In that case, the line discount amount of the last line is printed in the first line.
In localization VRCs, Tax percentage and description is not printed. This is printed in the standard reports
SOLUTION DESCRIPTION:
Now the Order discount for Sales orders is printed in the invoice
Now the line discount amounts are printed correctly.
Now in localization VRCs also, tax percentage and description is printed in the invoice.

Solution: 125158
SITUATION IDENTIFIED IN:
"Print Letter for Unsuccessful Bidders" (tdpur1410m000)
SITUATION DESCRIPTION:
help text tcSE1410m000 got corrupted.
SOLUTION DESCRIPTION:
repaired the text.

Solution: 125159
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
If the user enters in tfacp1110s000 an invoice related to orders then the program tries to find as much as defaults possible
from the order entered. These defaults are then shown to the user. The invoice from business partner is one of the defaults
and if the user later on changes the invoice from business partner to a one which is not related to the invoice from business
partner on the order line then a message is shown to the user. This message (warning message) is correct, but with every
save action (initiated by pressing the match button or afterwards the approve button) the same message appears again. This
is not needed and time consuming for the user.
SOLUTION DESCRIPTION:
Now only when the invoice from business partner is changed the check is done
whether the invoice from business partner from the order is related to the invoice from business partner entered on the form.

Solution: 125160
SITUATION IDENTIFIED IN:
"(Un)Block Lots" (whinh6120m000)
SITUATION DESCRIPTION:
It is possible to block the entire lot when some stock point is present in the 'Staging' location. Due to this at the time of
unblocking the lot, the stock point in the staging location is corrupted and the shipment could not be confirmed.
SOLUTION DESCRIPTION:
The lot cannot be blocked as long as there is some stock present in 'Inspection' or ' Receiving' or 'Staging' locations.

Solution: 125165
SITUATION IDENTIFIED IN:
"Selfbilled invoices" (tfacp2290m000)
SITUATION DESCRIPTION:
With solution 125069 the problem was corrected that 0 amount selfbilled invoices could be generated when the sequence
number 0 was not available in the finance purchase invoice lines table (tfacp240).
With this generation the invoices were generated for an amount of 0 and both the invoice accrual as the registered invoice
account was also used for an amount of 0.
SOLUTION DESCRIPTION:
The user is able with running from the menu "tfcor1022m000" to start a session where the receipts which made up these 0 invoices are set in such a
state that they can be reused in the selfbilled invoices session (tfacp2290m000). If any Purchase - Price Variances were created and if they are not
posted then they are deleted from the integration tables. If they are already posted then the same integration records are created, but with opposite sign,
so that if these are also posted they balance out. Note that price variances for cost items (and also the production and service subcontracting price
variances) can not be handled as there is not a difference between the receipt integration records and the (correction) price variance records. These
situations have to be taken care off manually (either manipulate the integration records or enter a journal).

Solution: 125171
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2502m000)
SITUATION DESCRIPTION:
Users belonging to 'Display' authorization type group are able to Submit, Approve and Cancel the requisition lines.
SOLUTION DESCRIPTION:
Now the 'Specific' menu option in the session "Purchase Requisition Lines" (tdpur2502m000) is accessible only for those
users whose authorization type group is at least 'Modify/Print/Display'.

Solution: 125172
SITUATION IDENTIFIED IN:
"Select Invoices for reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
When the "Receipt schedule date" is equal to "as on date", then the invoice is not selected for reminders.
SOLUTION DESCRIPTION:
The invoices are selected for Reminding even when the "Receipt Schedule Date" is equal to " As on date" .

Solution: 125181
SITUATION IDENTIFIED IN:
"Print Purchase orders to be acknowledged" (tdpur4401m100)
SITUATION DESCRIPTION:
It is not possible to print a purchase order if the order type is not having the print purchase order as one of the activity.
SOLUTION DESCRIPTION:
It is possible to print now even if the order type is not having the print purchase order as one of the activity.

Solution: 125182
SITUATION IDENTIFIED IN:
"Planned Material Transaction" (tppss6500m000)
SITUATION DESCRIPTION:
When 2 similar Planned PRP Purchase Orders are transferred to actual Purchase Order, they are accumulated in to single
Purchase Order Line and the Planned Quantity is shown wrongly in "Planned Material Transaction" (tppss6500m000).
SOLUTION DESCRIPTION:
Now the quantities in the session "Planned Material Transaction" (tppss6500m000) are shown correctly.

Solution: 125184
SITUATION IDENTIFIED IN:
"Maintain GRNI Correction" (tfacp1137s000)
SITUATION DESCRIPTION:
In session "Maintain GRNI Correction" (tfacp1137s000), the zoom for the Dimensions not working and the dimensions are not
getting updated in the Interim table (tfacp135).
SOLUTION DESCRIPTION:
The dimension zoom is working correctly now and the dimensions are updated correctly in the Interim table.

Solution: 125187
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When using a multiple shifted tax code for a Sales invoice with tax calculated at header level the tax codes by line are
calculated wrongly. Happens in the case of both parallel or cumulative.
SOLUTION DESCRIPTION:
Now the lines are correctly updated incase of Multiple Shifted Tax Code.

Solution: 125190
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
The quantity to backflush is not correctly calculated when already a quantity was backflushed, but no inbound has been done
for that.
SOLUTION DESCRIPTION:
When no inbound has been done for backflushed quantity, the to backflush field is filled correctly when quantity to deliver is
changed/filled.

Solution: 125206
SITUATION IDENTIFIED IN:
"tfacr2240m000" (Writeoff Payment Differences)
SITUATION DESCRIPTION:
An invoice is fully paid in invoice currency but has Small(0.01) balance in home currency that cannot be written off.
SOLUTION DESCRIPTION:
An invoice is fully paid in invoice currency, Small amount in home currency is written off.

Solution: 125212
SITUATION IDENTIFIED IN:
"Generate outbound advice" (whinh4201m000)
SITUATION DESCRIPTION:
Advised quantity of outbound advice for Kit component of a List Item wrong. It is not according to the ratio defined in the
session 'List Components' (tcibd3100m000). This happens if there is inventory shortage for the Component Item.
SOLUTION DESCRIPTION:
Now, system advises outbound quantity for components of list item is according to the ratio mentioned in the session
'List Components'(tcibd3100m000).

Solution: 125214
SITUATION IDENTIFIED IN:
"Outbound Advice by Order Line" (whinh2525m200)
SITUATION DESCRIPTION:
The descriptions of the labels "Ordered Qty. in St" and "Ordered Qty" were not clear enough.
SOLUTION DESCRIPTION:
The description of the label "Ordered Qty in St" was changed into "Ordered Quantity in Storage Unit" and "Ordered Qty"
into "Ordered Quantity in Inventory Unit" .

Solution: 125218
SITUATION IDENTIFIED IN:
"Send Trade Notes/Checks to Bank" (tfcmg4132s000)
SITUATION DESCRIPTION:
Two problems on field 'Receive form Bank':
1- when a Bank with less than 3 characters is selected an error message, ('Customer Bank does not exist'), appears.
Problem occurs in both B50_c and B50_b.
2- wrong Zoom on same field 'Receive from Bank'. After zoom, session 'Banks by Pay-by Business Partner' (tccom4515m000)
is called but showing another BP's Bank.
Problem exists only in B50_b.
SOLUTION DESCRIPTION:
On field 'Receive form Bank', bank code with less than 3 characters can be selected and when zooming, the correct BP's
Bank, on session 'Banks by Pay-by Business Partner' (tccom4515m000), is displayed.

Solution: 125222
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000)
SITUATION DESCRIPTION:
When PMC installed a form, which was already present, the old references to the help topics were not removed. The actual
installation of these references is an insert: It is only done when the references do not exist. Since the old references were
not removed, the new references could not be inserted.
SOLUTION DESCRIPTION:
The references to the old help topics are removed. As a result the installation of references to the new help topics will
succeed.

Solution: 125226
SITUATION IDENTIFIED IN:
"Correct Inventory Ledger accounts" (whcor0201m000)
SITUATION DESCRIPTION:
This correction program is needed to correct the erroneous records related to the following problem:
- Inventory Valuation Method of the Item is Fixed Transfer Price (FTP)
- The item is issued to the Shop-Floor for the Production Order.
- Then the 'Cost Price' of the item is changed.
- Now, when the goods are returned from the Shop-Floor to the Warehouse, the 'Warehousing(valuation) - Revaluation'
posting is done with wrong sign.
Due to this, the value of the Inventory account is going wrong.
SOLUTION DESCRIPTION:
This correction program can be used to correct the Warehousing(valuation)/(Revaluation postings done wrongly, due to the
Return Issue posting of the following Order origins.
- Production
- Service
- Sales
If the Transaction is not yet posted in Finance module, the sign of the Transaction amount would be reversed. Otherwise, if
the posting has been done, a new Transaction would be created with an amount equal to two times the original entry and with
opposite sign. When this new Transaction is posted, it would yield the same effect as reversing the sign of the original
posting.

Solution: 125233
SITUATION IDENTIFIED IN:
"Register Purchase Invoice" (tfacp1110s000)
SITUATION DESCRIPTION:
When a subcontracting purchase credit note is linked with an invoice, the Fatal error 205 ( reference not found ) occurs when
saving the record.
SOLUTION DESCRIPTION:
The error occurs because the field invoice from business partner ( tfacp200.ifbp ) is not populated. This has been corrected
now.

Solution: 125234
SITUATION IDENTIFIED IN:
"Manual Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
Error "Transaction is ON" when trying to save a Manual sales line if VERTEX is ON.
SOLUTION DESCRIPTION:
Now the error message does not occur

Solution: 125235
SITUATION IDENTIFIED IN:
"Enter Test Data by Serial Number" (qmptc1116s000)
SITUATION DESCRIPTION:
While entering new record manually in session the "Enter Test Data By Serial Number ", system is not displaying the "Option
Set" if the position is linked to option set. So system is always giving the result as BAD, when the lines are created
manually from "qmptc1516m000" (using the new icon). It works correctly if the lines are created automatically from "Create
Test Data Lines" selection from specific.
SOLUTION DESCRIPTION:
While entering new record manually in session the "Enter Test Data By Serial Number ", system should display the "Option
Set" if the poison is linked to option set and system should display the result according to the option selected.

Solution: 125236
SITUATION IDENTIFIED IN:
"Warehouse orders" (whinh2500m000)
SITUATION DESCRIPTION:
Warehouse transfer of tools was not possible between two locations in the same warehouse
SOLUTION DESCRIPTION:
Now It's possible to do manual transfer of tools between two different locations in same warehouse .

Solution: 125239
SITUATION IDENTIFIED IN:
"Print Supplier Aging Summary" (tfacp3425m000), "Print Aging Analysis By Supplier" (tfacp2420m000) and "Display
Supplier Aging Summary" (tfacp3525m000)
SITUATION DESCRIPTION:
If a credit note was linked to a purchase invoice and the document date of the credit note (30/04/2002) was after the
document date of the purchase invoice (30/01/2002) and the linking document (30/02/2002), then when the report "Print
Supplier Aging Summary" (tfacp3425m000) was printed before the date of the credit note (30/03/2002), the amount didn't
match with the report "Print Aging Analysis By Supplier" (tfacp2420m000) as in the later the credit note amount was not
considered.
SOLUTION DESCRIPTION:
The report "Print Supplier Aging Summary" and the report "Print Aging Analysis by Supplier" tally with each other.
Also the amounts shown in the session "Display Supplier Aging Summary" (tfacp3525m000) also tally with the reports.

Solution: 125244
SITUATION IDENTIFIED IN:
"Matched Purchase Invoice Transactions" (tfacp1133s000)
SITUATION DESCRIPTION:
In session "Matched Purchase Invoice Transactions" (tfacp1133s000), if the target company is different from the current
company, then after saving and exiting from the session, if the session is started again the target company displays the
current company value.
SOLUTION DESCRIPTION:
The field target company now displays the correct company. In case the target company is not equal to the current company,
the field is disabled.

Solution: 125253
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Sales Order Lines Details with different prices are aggregated in same invoice line. Actually a separate invoice line has to
be printed when the price changes
SOLUTION DESCRIPTION:
Now the detail lines are not aggregated if price changes. It is printed separately

Solution: 125255
SITUATION IDENTIFIED IN:
"Signals by Item/Planner" (cprao1125m000)
SITUATION DESCRIPTION:
When updating the signals from the session (cprao1125m000) Signals by Item/Planner, signals were generated for customized
items that are connected to project that doesn't have status Active or Simulated.
SOLUTION DESCRIPTION:
System will give a message "Project status of must be 'Active' or 'Simulated" while trying to update the
signals for the Customized item that are connected to the project which doesn't have the status Active or simulated,

Solution: 125261
SITUATION IDENTIFIED IN:
"Material to issue for Production orders" (ticst0101s000)
SITUATION DESCRIPTION:
When quantity ordered in a Production order is changed after releasing the order, then the Quantity in the warehouse
outbound lines of the order is NOT updated accordingly.
SOLUTION DESCRIPTION:
If the quantity ordered is changed after releasing a Production order, then the corresponding values in the outbound lines
are changed accordingly.

Solution: 125262
SITUATION IDENTIFIED IN:
"Wrong Account used during Write-off Currency Differences" (tfcorcont_ac05)
SITUATION DESCRIPTION:
In correction program the select statement for selecting the Open Items (receivable) is incorrect.
SOLUTION DESCRIPTION:
The select statement has been corrected.

Solution: 125271
SITUATION IDENTIFIED IN:
"Table: Integration References" (tfgld418)
SITUATION DESCRIPTION:
The labels for some fields in table "Integration References" (tfgld418) are missing.
SOLUTION DESCRIPTION:
The labels are present for the table "Integration References" (tfgld418). Also some labels which were missing in the GRNI
solution are also included in this solution.

Solution: 125272
SITUATION IDENTIFIED IN:
"Generate Invocies by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
Incase an Invoice could not be generated for a receipt line, because of some problems (like Missing control account in the
Bussiness partner group etc... ), for the subsequent receipt line when invoice is generated , the table Transaction Type Batch
Status ( tfgld101 ) is not populated. Because of this the Invoice could not be finalized.
SOLUTION DESCRIPTION:
Now the table Transaction Type Batch Status ( tfgld101 ) is populated correctly even when there is something wrong with
Invoice generation for a previous receipt line.

Solution: 125275
SITUATION IDENTIFIED IN:
"Shipment Lines" (whinh4531m000)
SITUATION DESCRIPTION:
When "New Bill of Lading Cluster" is selected for more than one shipment line, fatal error 206 (record is not locked) arises.
SOLUTION DESCRIPTION:
In session "Shipment lines" (whinh4531m000), if "New Bill of Lading Cluster" is selected via Specific for multiple Shipment
lines, the new cluster is created properly.

Solution: 125277
SITUATION IDENTIFIED IN:
"Display Selected Sales Contracts (Item Lines)" (tdsls3512s000)
SITUATION DESCRIPTION:
Define two contract lines for the same item in one special contract and enter for each line different texts, only the text of
the last contract line is displayed when you select the text button in the session "Display Selected Sales Contracts (Item
Lines)" (tdsls3512s000) for either contract line.
SOLUTION DESCRIPTION:
The correct text identification is now used when presenting the contract line text.

Solution: 125279
SITUATION IDENTIFIED IN:
"Posting Data of Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
It is not possible to enter/process a receipt transaction for an outgoing payment and to enter/process a payment transaction
for an incoming receipt in tfcmg5106s000 (Posting Data of Electronic Bank Statements).
This means that it is impossible to process credit notes if there are no separate receipts / payments for them.
SOLUTION DESCRIPTION:
After installing this solution it is possible to enter a receipt transaction for an outgoing payment and to enter a payment
transaction for an incoming receipt in tfcmg5106s000 (Posting Data of Electronic Bank Statements).
Credit notes can be entered and processed now.

Solution: 125302
SITUATION IDENTIFIED IN:
"Generate Cost Forecast by Cost Object" (tpppc2216m000)
SITUATION DESCRIPTION:
In build actual cost control surcharges are calculated on forecasts. And also on the budget side, surcharges are calculated.
So, when Forecast is filled taking budget as a base, Surcharges are calculated twice. To prevent this, Budget surcharge lines
should not be copied to forecast lines.
SOLUTION DESCRIPTION:
Now, the above mentioned problem is solved. From Budget tables, surcharges are now not copied to Forecast lines.

Solution: 125307
SITUATION IDENTIFIED IN:
"Generate EDI Messages " (ecedi7201m000)
SITUATION DESCRIPTION:
It was impossible to convert the Invoice-to Business Partner code (using the code from the original sales order header:
tdsls400.itbp). The conversion had been properly defined in "Conversion by Business Partner (out) (ecedi4168m000), but
the unconverted code appeared in the ASN.
SOLUTION DESCRIPTION:
The Business Partner type was not set for the Invoice-to Business Partner. The program script has been modified. The
converted code will now be written into the outgoing ASCII file.

Solution: 125317
SITUATION IDENTIFIED IN:
"Print WIP" (ticst0450m000)
SITUATION DESCRIPTION:
Very bad performance with a level-1 database-driver.
SOLUTION DESCRIPTION:
Several queries are improved to perform much better.

Solution: 125323
SITUATION IDENTIFIED IN:
"Schedule Lines" (tdpur3507m000)
SITUATION DESCRIPTION:
When attempting to confirm a receipt for a purchase schedule line, message "Some or All Quantities Invoiced for Schedule
Line" is returned and the session will not confirm the receipt.
This happens for the Schedule Lines, which has the same, start and finish dates and times and the first line is Received and
Invoiced.
SOLUTION DESCRIPTION:
The problem has occurred because of the reason that another schedule line with the same start date and time has been created
by the system when already a line exists for that Start Date and Time. System should not create the second line when already
a Schedule Line exists for that Start Date and Time.
Now changes are made such that system creates only a Planned Purchase Order and doesn't create a new Schedule Line if a
Schedule Line already exists for that Start Date and Time. This Planned Purchase Order can be transferred to Purchase
manually and then received.

Solution: 125324
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When reading a geo code (tccom130.geoc) from the incoming ASCII file, the code was not inserted in the specific
address, generated by EDI. The "Use Tax Provider" parameter (Tax Provider Parameters; tccom6150s000) was not checked.
SOLUTION DESCRIPTION:
Now the geo code is stored in the address table. No validation takes place when the tax provider is off (similarly as in the
manual order/address entry process).

Solution: 125326
SITUATION IDENTIFIED IN:
"Objects" (tscfg2100s000)
SITUATION DESCRIPTION:
When zooming from session Objects (tscfg2100s000), tab 'Site', field 'Tool number', the target session is incorrect, the
correct one must be session 'Tool numbers by tool type' (titrp0502m000).
SOLUTION DESCRIPTION:
Now, when zooming from the field 'Tool number', located on the session 'Objects' (tscfg2100s000), tab called 'site', the
target session is 'Tool numbers by tool type' (titrp0502m000).

Solution: 125328
SITUATION IDENTIFIED IN:
"Generate project structure for project variant" (tipcs2220m000 )
SITUATION DESCRIPTION:
When using a level 1 database driver, "Generate project structure for project variant (tipcs2220m000 )" takes a lot of time.
SOLUTION DESCRIPTION:
Query changed for better performance with a level 1 database driver

Solution: 125342
SITUATION IDENTIFIED IN:
"Transfer Order Manually " (cprrp1250s000)
SITUATION DESCRIPTION:
While transferring Planned Distribution Orders in a multisite scenario, system creates Purchase order with wrong order
series and Order type
SOLUTION DESCRIPTION:
The system creates purchase order with the order series and order type entered in the session.

Solution: 125344
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
The session simulate orders aborts with the message "Date to cannot be after scenario end date" or "Date from cannot be
before scenario start date".
SOLUTION DESCRIPTION:
These messages and aborts will not appear anymore when running sessions in EP. Instead of this a date beyond the scenario
boundaries is seen as the start or finish date of the scenario.

Solution: 125346
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Warehouse data corruption is caused in case "DIRECT PUT AWAY" is used in crossdocking with shipping constraint "ship
complete"
SOLUTION DESCRIPTION:
Direct put away is not allowed in case or partial receipts for cross docking with shipping constraint " Ship complete ". System
should allow to move the inventory to staging location and create shipment lines , but not confirm them untill the total
quantity is received. .

Solution: 125356
SITUATION IDENTIFIED IN:
"Print Purchase Order History by Supplier and Item" (tdpur5401m000)
SITUATION DESCRIPTION:
Project code is not printed on the report, when the selection is by any field other than 'Purchase Order' or 'Project'.
SOLUTION DESCRIPTION:
Now the Project code is printed correctly for all selections.

Solution: 125357
SITUATION IDENTIFIED IN:
"Generate Subcontracting Purchase Order" (tisfc2250m000)
SITUATION DESCRIPTION:
When generating the subcontracting Purchase Order for a Production order, the system is taking the Purchase office from
the Buy-from BP instead of Item supplier Information maintained for that Item. Also the wrong date was used for determination of the office.
SOLUTION DESCRIPTION:
When generating the subcontracting Purchase Order for a Production order, the system will take the Purchase Office from
Item supplier Information maintained for that Item. If Item supplier Information is not maintained then only it will take
the Purchase office from the Buy-from BP. The correct date will be used for determination of the office.

Solution: 125359
SITUATION IDENTIFIED IN:
"Purchase order lines/RFQ lines" (tdpur4101s000/tdpur1102s000)
SITUATION DESCRIPTION:
-1- The parameter for price search is by "Delivery Date". Price retrieved from Price Book is not recalculated in Purchase
Order lines after the Delivery Date is changed.
-2- Item Search is not possible when the item and comma is entered in the item field of RFQ lines.
SOLUTION DESCRIPTION:
-1- System picks the correct price from the Price Book when the Delivery date is changed.
-2- Item Search is possible now when the search key is entered in the RFQ lines.

Solution: 125361
SITUATION IDENTIFIED IN:
"Copy Company Data" (tccom0214m000)
SITUATION DESCRIPTION:
Info missing in help for copying enterprise units in Copy Company Data
SOLUTION DESCRIPTION:
Explanations added.

Solution: 125366
SITUATION IDENTIFIED IN:
"GRNI sessions" (Several)
SITUATION DESCRIPTION:
The following issues are solved:
- Fatal error message in tfacp1438m000 solved
- Activated the acceptance button again in session tfacp1535m000
- Added dimensions on the form for corrections done
(Dimensions are not filled by session tfacp1235m000 see solution 126055 for that)
- Activated the acceptance button in session tfacp1536s000 ("Display Manual Postings") and added more selection filters
- Improved Suppress Zero options for report 3, 4 and 5 for session tfacp1438m000.
- Added position number for session tfacp1438m000 on the form
- Improved the selection of tfacp1439m000 and tfacp1438m000 (if option based on logistics was selected)
- Reporting period in session tfacp1240m000 should be dimmed if it is not used
SOLUTION DESCRIPTION:
All options solved mentioned above

Solution: 125374
SITUATION IDENTIFIED IN:
"Global Update of Inventory Parameters" (whina2200m000)
SITUATION DESCRIPTION:
When "Item Data by Warehouse" is selected in session "Global Update of Inventory Parameters" (whina2200m000) then:
1) If the "Safety Stock" for an item located in more than one warehouse is actualized, the report generated only shows the
first warehouse per item.
2) In the second tab "Ranges", the field "Warehouse To" remains blank
SOLUTION DESCRIPTION:
1) The report prints every warehouse where the actualized item is located.
2) The field "Warehouse To" shows its maximum range.

Solution: 125381
SITUATION IDENTIFIED IN:
"Update Order Lead Times" (tirou1202m000)
SITUATION DESCRIPTION:
The Help text of the session Update Order Lead Times needs to be more clear and elaborate
SOLUTION DESCRIPTION:
The Help text of the session Update Order Lead Times made more clear and elaborate

Solution: 125383
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipt" (tdpur4122m000)
SITUATION DESCRIPTION:
1. There is a 'Collect Order' type Purchase Order with out the any value in the 'Warehouse' field and also a TP project is
entered in the 'Project' field.
2. When the 'Price' is changed for this order from the session "Change Prices/Discounts after Receipt" (tdpur4122m000),
the 'Hard Commitments' are not getting reversed in the session "Commitments (Materials)" (tpppc2510m000).
SOLUTION DESCRIPTION:
The 'Hard commitments' will get reversed now, when the 'Price' is changed after receipt for a 'Collect Order.'

Solution: 125390
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Sales Order Line's Details with different discounts are aggregated in same invoice line. Actually a seperate invoice line has
to be printed when the discount changes
SOLUTION DESCRIPTION:
Now the detail lines are not aggregated if discount changes. It is printed seperately

Solution: 125399
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst0101s000)
SITUATION DESCRIPTION:
When additional items are added/updated in the "Material to issue for production order" 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:
When additional items are added/updated in the "Material to issue for production order" session
with backflushing flag selected for a released production order with moments of freezing
estimates as "Before First WIP transaction" then, the system prevents the
addition of items and displays a message stating "Backflushing not possible for this new Material line, because Estimated
and Net Quantity = 0" .

Solution: 125402
SITUATION IDENTIFIED IN:
"Receipt Corrections" (whinh3121s000)
SITUATION DESCRIPTION:
Adjust approved inventory flag during receipt corrections doesn't work if warehouse is Location Controlled .
SOLUTION DESCRIPTION:
Adjust approved inventory flag is not standard functionality,so it is removed.

Solution: 125408
SITUATION IDENTIFIED IN:
"Transfer Plan/Order" (cppat1210m000)
SITUATION DESCRIPTION:
When transferring multisite planned distribution orders for which the Buy-from BP field is not filled, the Buy-from-BP on
the created purchase order is the BP defined in the item supplyer information instead of the BP which is linked to the
supplying site
SOLUTION DESCRIPTION:
If the Supplying Site for a Planned Distribution Order is different from Receiving Site, the Buy-from BP is selected from
affiliated site available in the Business Partner information. From Buy-from BP, the Ship-from BP is selected, being the
BP whose supplying warehouse is equal to the Supplying Item's default Warehouse (Plan Item Data) of the affiliated
company.
SOLUTION 125342 FOR AFTER INSTALLING THIS SOLUTION.
VERSION(S):
B50_b, B50_c

Solution: 125414
SITUATION IDENTIFIED IN:
"Selection Criteria" (tsclm8599s000)
SITUATION DESCRIPTION:
Three situations were identified in here:
1.- When changing from one form to other, the setting introduced by the user as a search criteria was override by the system
defaults.
2.- The search results sometimes were not the expected ones.
3.- The "save default" button is not working properly, to save the user defaults properly, it has to be clicked twice, one time
per form.
SOLUTION DESCRIPTION:
1. - The user settings for the search criteria are being kept, no matter if the user changes from one form to the other.
2. - About the search results, the system is now showing the correct selection that matches with the user defined criteria.
3. - The "Save default" button, can be clicked ones per session, and all the settings defined for the user as a search criteria,
in both forms will be saved.

Solution: 125426
SITUATION IDENTIFIED IN:
"Archive Projects" (tipcs2260m000)
SITUATION DESCRIPTION:
1. A project is archived from the session "Archive Projects" (tipcs2260m000).
2. The History of the Sales Orders linked to the project are archived to the archiving company. But the actual Sales Orders
are not archived.
3. The Purchase Orders linked to the project are archived. But the History data of the Purchase Orders are not archived.
4. Both the Purchase order data and Sales order data are not deleted in the original company.
SOLUTION DESCRIPTION:
Now, the following happens when the project is archived from the session "Archive Projects" (tipcs2260m000)
1. The Sales Order History and Purchase Order History of the orders linked to the project are archived.
2. Sales Orders and Purchase Orders are archived to the archiving company and also they are deleted in the original
company.

Solution: 125428
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
The Invoice is printed with same description for "Discount" both for the Line Discounts and the Cash Discounts in
German Language
SOLUTION DESCRIPTION:
Now the Cash discount and the Line Discounts are distinguished in German Language

Solution: 125436
SITUATION IDENTIFIED IN:
"Sales Invoice" (tfacr1110s000)
SITUATION DESCRIPTION:
When a sales credit note in "maintain transactions" or put in a manual sales invoice credit note to Central Invoicing, system
is picking up the terms of payment instead of the return terms of payment from the business partner
SOLUTION DESCRIPTION:
The return terms of payment is now defaulted in "Terms of Payment" field when the transaction type is Sales credit note OR
when the transaction type is Sales invoice and invoice amount is negative .

Solution: 125437
SITUATION IDENTIFIED IN:
"Purchase-Invoice Transactions" (tfacp1120s000), "Matched Purchase Invoice Transactions" (tfacp1133s000),
"Sales Invoice Transactions" (tfacr1111s000), "Cash Management Transactions" (tfcmg2120s000) and
"Cash Management Transactions (Anticipated Payments)" (tfcmg2140s000).
SITUATION DESCRIPTION:
The ledger account is checked for blocking using the document date, but this is not correct as the transaction date is used to
get the fiscal year and fiscal period which is then updated in the Finalization Transactions. And hence the finalization of the
transactions fails.
SOLUTION DESCRIPTION:
The transaction date is used to check the blocking for the ledger account and hence only valid ledger accounts with
transaction dates can be finalized. Hence no errors during finalization.

Solution: 125441
SITUATION IDENTIFIED IN:
-1- "Confirm Receipts" (whinh3520m000)
-2-"Confirm Shipments" (whinh4275m000)
SITUATION DESCRIPTION:
-1- When transferring items between warehouses with bilateral invoicing, if the issue quantity is greater than the receive
quantity, the message 'transfer price could not be retrieve for intra company invoicing' appears. The message appears when
confirming the receipt.
-2- In a triangular invoicing scenario and if a valutation price had been defined as
the "Price Type" , the following integrations were created with an incorrect
amount (due to an erroneous conversion of the valuation
price in the currency in which these
transactions are
booked):
Sales Invoicing (Triang.)/ Revenues Analysis
Sales Invoicing (Triang.)/Triangular Invoiced
SOLUTION
DESCRIPTION:
-1- The message will not appear anymore when confirming the receipt.
The transfer price will now be determined based on the ordered quantity (as defined in the outbound line of the warehouse
transfer order) instead of the delivered or received quantity.
-2- These Integrations are now created with the correct amount.

Solution: 125443
SITUATION IDENTIFIED IN:
"Receipts schedule" (tfacr1103m000)
SITUATION DESCRIPTION:
From session tfacr2520m000, when zoomed to Receipt Schedule, (tfacr1103m000) the system doesn't allow to exit session
unless schedule is entered for an amount equal to invoice amount. It doesn't even allow to exit when schedules are entered
for only open amout. It gets mandatory to enter for the whole invoice amount , even if the receipts are present.
SOLUTION
DESCRIPTION:
Now whenever the schedules are entered for an amount less than the
invoice amount , a warning is given & its now
possible to exit the session.

Solution: 125445
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. There is a Purchase Order Line with zero 'Quantity'.
2. For this order there is No Integration Transaction entry created in the session "Integration Transactions by
Project/Order" (tfgld4510m000).
SOLUTION DESCRIPTION:
Now the Integration Transaction postings in Finance are created for the purchase order lines with zero quantity.

Solution: 125447
SITUATION IDENTIFIED IN:
"Aging Analysis Data" (tfacp0140s000)
SITUATION DESCRIPTION:
While entering a new Aging Analysis Code or modifying an existing one in session "Aging Analysis Data" (tfacp0140s000),
the field Period Type was showing a new list value called "Japanese" in addition to "Days", "Months" and "Fiscal Periods".
SOLUTION DESCRIPTION:
Only list values "Days", "Months" and "Fiscal Periods" can be seen and selected for the field "Period Type" in the session
"Aging Analysis Data".

Solution: 125456
SITUATION IDENTIFIED IN:
"Copy Sales Orders " (tdsls4201s000)
SITUATION DESCRIPTION:
1. A Sales Order Line with manual entered 'Discount' is copied to a new order.
2. In "Copy Sales Orders (tdsls4201s000)", the checkbox "Calculate New Prices and Discounts" is checked.
3. The copied line still contains the manually entered discount.
4. This is wrong and the default discount should be applied in the new line and not the manually entered discount of the
original order.
SOLUTION DESCRIPTION:
Only the default discount corresponding to the time of copying would be picked up and used in the new copied Sales Order
Line. The 'Discount' of the original sales order line is not applied any more.

Solution: 125469
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
For a production order with no estimated materials and operations, the production order status remains "Released",even after
some quantities have been reported completed and put to stock.The order status should be changed to "Active" because there
has been a financial transaction created against the production order.
SOLUTION
DESCRIPTION:
Now for a given production order with no estimated materials and operations, the production order status will change to
"Active",if there is a financial transaction created against the produciton order.

Solution: 125471
SITUATION IDENTIFIED IN:
"Activity Progress" (tpppc1160s000)
SITUATION DESCRIPTION:
The cumulative Qty . is getting rounded to two decimals even when the unit of the charge element has rounding factor upto
four decimals and the cumulative percentage is also upto four decimals.
SOLUTION DESCRIPTION:
The qty. was getting rounded to two decimals only irrespective of anything because of the hard cording of the qty to be
rounded to two decimals when cumulative % is changed. Now this has been changed accordingly and above problem is
solved.

Solution: 125476
SITUATION IDENTIFIED IN:
"Change prices/discounts after receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
With the new GRNI solution it was important that with the "change prices/discounts after receipts" session, all the individual
receipts were corrected for a certain purchase order line - sequence number. This has to do with the fact that at least the
date of the resulting Purchase - Price Variance postings to the financial integration tables should be the same as the date of
each receipt. However it appears that this process now also creates multiple records in the warehousing variances table
(whinr116) in which this logic can't be dealt with, which result in wrong posting of inventory variances.
SOLUTION
DESCRIPTION:
Now the individual receipts are being processed for a certain purchase order line - sequence number, but the creation of the
inventory variance record will be done for the total.

Solution: 125478
SITUATION IDENTIFIED IN:
"Service Order Actual Labor Costs" (tssoc2131s000)
SITUATION DESCRIPTION:
The Sales Rate on the Service Order Actual Labor lines is not displayed correctly.
In the Sales Rate the Surchage specified in the Hourly Labor Type is taken into Account.
Surchage should only be calculated in the Total Sales Amount.
SOLUTION DESCRIPTION:
The Sales Rate on the Service Order Actual Labor Lines is displayed correctly.
In the Sales Rate the Surcharge is not taken into account.
This is consistent with the Cost Rate as well.

Solution: 125479
SITUATION IDENTIFIED IN:
"Print Budget Structures" (tipcs1411m000)
SITUATION DESCRIPTION:
If a budget structure is printed, not including the Product Variant Options, the structure is printed according to the
material sheet. When the Product Variant Options are included, all calculation parts are printed with the same components on
the report layout.
SOLUTION
DESCRIPTION:
When printing a budget structure, including the Product Variant options, the structure is printed according the material
sheet.

Solution: 125482
SITUATION IDENTIFIED IN:
"Copy Projects" (tppdm7840m000)
SITUATION DESCRIPTION:
In session 'Copy Projects' (tppdm7840m000) the user can select several options to copy different parts of the data. But in
some cases if not all checkboxes are checked, the top element, the leading plan or the actual cost calculation code are not
copied. The description for these fields in the project data then shows 'xxxxxxxxxxxx'.
SOLUTION
DESCRIPTION:
The top element, the leading plan and the actual cost calculation code are now always copied to the new project, irrespective
of the selected checkboxes.

Solution: 125486
SITUATION IDENTIFIED IN:
"Forms" (ttadv3500m000)
SITUATION DESCRIPTION:
Some forms in Dutch and German languages are not linked to English language. Due to this what ever change done in
English language, they are not getting reflected in Dutch and German.
SOLUTION DESCRIPTION:
For these Forms, the link has been re-defined.

Solution: 125489
SITUATION IDENTIFIED IN:
"Calculate sales Price by Item" (ticpr2250m000).
SITUATION DESCRIPTION:
Cost price of an Item is not calculated in job mode, while calculating sales price of the Item, even though 'Calculate cost
price' is checked as 'Yes' in "Calculate sales Price by Item". This works fine in normal mode.
SOLUTION DESCRIPTION:
The cost price of an Item is calculated in job mode,while calculating the sales price for the Item.

Solution: 125493
SITUATION IDENTIFIED IN:
"Invoice-To Business Partners Balances" (tccom4213m000)
SITUATION DESCRIPTION:
The order balance shown in "Sales Order Lines" (tdsls4501m000) differs from the order balance shown in "Invoice-To
Business Partners Balances" (tccom4513m000)
SOLUTION DESCRIPTION:
The order balance presented in tdsls4501m000 shows the total amount of goods.
The order balance presented in tccom4513m000 presents the total amount of goods including any surcharges and taxes.
The surcharge added to an order was not taken into account when session "Rebuild Customer Order Balance"
(tccom4213m000) was executed.
Modified this session so the surcharges are calculated as well when running tccom4213m000

Solution: 125496
SITUATION IDENTIFIED IN:
"Purchase Invoices by Business Partner" (tfacp2522m000)
SITUATION DESCRIPTION:
When selecting multiple records in the session "Purchase Invoices by Business Partner" (tfacp2522m000), an error comes up
"Selected X records, command not allowed". After pressing ok, if the records, which are displayed, are browsed, a runtime
error comes up "use of null pointer" and it aborts from the session.
SOLUTION
DESCRIPTION:
No runtime error comes when the records are browsed after selecting multiple records and getting the baan error message.

Solution: 125497
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
If a combination of lot code & item is repeated, Quantity to deliver is hung at warehouse module, waiting to confirm & no
message is displayed as to what is the problem. So the user is confused.
SOLUTION DESCRIPTION:
Now if a combination of given lot code & the item exists(in case of lot by unit), and the user tries to use the same lot again,
a message will be given saying this is not possible, so the user will understand what the problem is.

Solution: 125500
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
For a Production Order with Subcontracting and a Purchase Order is created then:
When the Purchase Order is received in session "Receipts" (whinh3520m000), a Financial Transaction is created in session
"Integration Transactions by Project/Order" (tfgld4510m000) (Production/subcontracting).
This Financial Transaction does not contain the Business Partner of the Purchase Order.
SOLUTION DESCRIPTION:
The Business Partner (of the Purchase Order) is now available in the Financial Transaction.

Solution: 125501
SITUATION IDENTIFIED IN:
"Delete forms/menu's/reports which don't have a source" (ttcor9211m000)
SITUATION DESCRIPTION:
When removing formdumps, menudumps or reportobjects the system did not check
if the remove action was succesfull. If not, the datadictionary was cleaned
up, but the formdumps, menudumps and report objects remained on the system.
SOLUTION DESCRIPTION:
Changes are implemented which result in an abort of the session in case the
removal of physical components is not possible. During the abort a message will be given showing the component that
cannot be removed.

Solution: 125504
T
OOLS VERSION(S):
B40_c, B50_b, 7.1_a
SITUATION IDENTIFIED IN:
"Dump Menu" (ttdlldumpmenu)
SITUATION DESCRIPTION:
When dumping an application menu containing tools sessions a index out of dims will occur.
SOLUTION DESCRIPTION:
This problem (error index out of dims) is now solved. (It will no longer occur when dumping an application menu containing
tools sessions)

Solution: 125506
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements/RMAs" (tdsls4401m000)
"Print Purchase Orders" (tdpur4401m000)
"Print Contract Quotation Documents" (tsctm2400m000)
"Print Service Contract Documents" (tsctm3400m000)
Print Service Order Quotation Documents (tssoc1400m000)
SITUATION DESCRIPTION:
Fatal error and error message "Index out of dims".
Occurs when printing report "Sales Order Acknowledgement/RMA" (tdsls440101000) from session "Print Order
Acknowledgements/RMAs" (tdsls4401m000).
The same happens when printing report "Proforma Purchase Invoice" (tdpur440401000) from session "Print Purchase
Orders" (tdpur4401m000).
SOLUTION DESCRIPTION:
Recompiled all reports that were delivered with solution 118646 although known problems until now only relate to reports:
- "Sales Order Acknowledgement/RMA" (tdsls440101000)
- "Proforma Purchase Invoice" (tdpur440401000).

Solution: 125511
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4501m300)
SITUATION DESCRIPTION:
1. There is a 'Purchase Order' with 'Quantity' zero. At the time the order line is created an Integration Posting is created of
type 'On Order'.
2. Now the Purchase Order Line is received.
3. At this time the originally created 'On Order' is reversed and a new 'Receipt' posting is created.
4. But also an extra 'On Order' posting is done that is same as the originally created 'On Order'
SOLUTION DESCRIPTION:
The extra "On Order' posting done at the time of making Receipts will not happen now.

Solution: 125513
SITUATION IDENTIFIED IN:
"Purge Sales Invoice Data" (cisli3210m000)
SITUATION DESCRIPTION:
Billing Requests printed wrongly in the report. The report shows just the Billing Request of the last purged invoice.
SOLUTION DESCRIPTION:
Now all the Billing Requests are printed correctly.

Solution: 125518
SITUATION IDENTIFIED IN:
"ATP Handling" (tdsls4899m000)
SITUATION DESCRIPTION:
When component requirement date becomes before current date (because of lead time offset in BCM) then ATP of that
component wasn't checked.
When End Items ATP is negative, then that value was subtracted from resulted CTP.
When using "Where Available Report" for a date outside CTP horizon, then Field Overflow sign is displayed in quantity
field (#####).
SOLUTION DESCRIPTION:
When component requirement becomes before current date, then ATP value is set to 0. Negative ATP values in ATP check
are set to 0.
When ATP date becomes outside CTP horizon then the maximum value is set according to domain, so no field overflow
occurs.

Solution: 125519
SITUATION IDENTIFIED IN:
"Commitments & Actual Costs" (tpppc2811m000)
SITUATION DESCRIPTION:
Sales price can be saved for a fixed price project, when it defaults from Finance in case of cost invoices.
So it gives a wrong impression that this cost can be invoiced.
SOLUTION DESCRIPTION:
Sales Price cannot be saved for a Fixed price project, even though it defaults. It will get a zero value while saving.

Solution: 125520
SITUATION IDENTIFIED IN:
"Equipment Costs" (tpppc2551m000)
SITUATION DESCRIPTION:
Start session tpppc2811m000 "Commitments and Actual Costs". Now choose Equipement Cost.
Go to the View-option in the menu bar and then choose the Sort-by-option.
The fourth index reads "cptf, Year(Fiscal), FisPer,Proj, Eqpmnt, Seq.". It is not clear what is meant by "cptf"
SOLUTION DESCRIPTION:
Changed the description of the index to "Cost Peri(Fiscal),Year(Fiscal), FisPer,Proj, Eqpmnt, Seq.".

Solution: 125522
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Invoice Report has wrong German Description for "Tax Total".
SOLUTION DESCRIPTION:
Now the Invoice is printed with correct German Description for Tax Total

Solution: 125527
SITUATION IDENTIFIED IN:
"Print Customerwise Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
Aging Analysis gives wrong report in the Following cases:
1. Negative Anticipated Receipt is linked to a Sales Invoice.
2. When a Negative Sales Invoice used as a credit note to link it to another sales invoice
SOLUTION DESCRIPTION:
Now the Aging Analysis shows correct amounts both in the balance column and gives correct classification of the age of the
invoices

Solution: 125535
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000)
SITUATION DESCRIPTION:
When creating job out of the sessions "Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000), "Print
Invoice-to Business Partner Aging Summary" (tfacr2411m000) and "Print Aging Analysis by Invoice-to Business Partner"
(tfacr2420m000), the company field is filled up with a single company. Now with rotate currency if jobs are created for
different currencies, the report is printed with only the first or local currency defined for all the different currencies.
SOLUTION
DESCRIPTION:
The sessions are printing the amounts correctly for different currencies when used in job.

Solution: 125540
SITUATION IDENTIFIED IN:
"Copy Sales Order" (tdsls4201s000)
SITUATION DESCRIPTION:
When a Sales Order is copied from History, the copied order does not have the Sales Office, Order Series and Order Type
that are entered in session "Copy Sales Orders" (tdsls4201s000). Instead they are retrieved from the source order.
SOLUTION DESCRIPTION:
Now, while copying Sales Orders, the input values from the session are passed to the target Order.

Solution: 125544
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
When printing a Purchase Order, the Tax Amount is determined and rounded just before printing. But the rounding was based
on the rounding factor of the Home Currency instead of the Purchase Order Currency and this is incorrect.
SOLUTION DESCRIPTION:
While printing a Purchase Order, the rounding of the Tax Amount is done based on the rounding factor of the Purchase
Order Currency.

Solution: 125547
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
When the session is run for second time, "without closing" and when the flag 'Print Packing Slip in Order Language' is
modified, the language in which the report is printed is wrong.
1. For example, when the session is run first time with the flag 'Print Packing Slip in Order Language' checked, and "without
closing" the session, when the flag 'Print Packing Slip in Order Language' is unchecked and run again, the report is still
printed in the Order language.
2. And, when the session is run first time with the flag 'Print
Packing Slip in Order Language' un-checked, and "without
closing" the session, when the flag 'Print Packing Slip in Order
Language' is checked and run again, the report is
still printed in the System
Language.
SOLUTION DESCRIPTION:
Now, when the flag 'Print Packing Slip in Order Language' is changed, and
when the session is run again "without closing", the
report is printed accordingly in the
correct language.
For example:
1. When the session is run first time with the flag 'Print
Packing Slip in Order Language' checked, and "without
closing" the session, when the flag 'Print
Packing Slip in Order Language' is
unchecked and run again, the
report now correcly
prints in the System
language.
2. And, when the session is run first time with the flag 'Print
Packing Slip in Order Language' un-checked, and "without
closing" the session, when the flag 'Print Packing Slip in Order
Language' is checked and run again, the report now
correctly prints in the Order
Language.

Solution: 125550
SITUATION IDENTIFIED IN:
"Purchase Contract Lines" (tdpur3102s000)
SITUATION DESCRIPTION:
When the item is searched with the item and followed by comma, an error message pops up saying that item not present in
item purchase data.
SOLUTION DESCRIPTION:
The changes have been done and if the item and followed by comma is entered, then the item purchase data will open and the
system searches with the search key field and not with the item.

Solution: 125554
SITUATION IDENTIFIED IN:
"Generate Purchase Subcontracting Orders" (tisfc2250m000)
SITUATION DESCRIPTION:
It is not possible to generate the subcontracting purchase orders when an internal error occurs in the system.
SOLUTION DESCRIPTION:
It is now possible, to generate the subcontracting purchase orders.

Solution: 125555
SITUATION IDENTIFIED IN:
"Purchase Order Headers" (tdpur4100s000)
SITUATION DESCRIPTION:
When we make certain changes (specifically buyer field ) in a Purchase Order Header, after the lines are created , the data
is not updated in the finance tables . As a result, finance may have the wrong data when trying to approve/process accounts
payable transactions.
SOLUTION
DESCRIPTION:
Like the other fields
Currency, Tax, Self billing etc
that are common to all the line,
the 'Buyer' field is
also be disabled once a line is created.

Solution: 125557
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
Not always the correct BP description of the "Buy-from Business Partner" is shown on the second form of session
tfacp1110s000.
SOLUTION DESCRIPTION:
This has to do with wrong SQL usage. This has now been corrected.

Solution: 125561
SITUATION IDENTIFIED IN:
"Periodical Depreciation and Revaluation Results " (tffas0520m000)
SITUATION DESCRIPTION:
When entering a new header in session tffas0520m000 (Periodical Depreciation and Revaluation Results) and not introducing a
Special Depreciation code, the system gives an error message "Special Depreciation not found" although the heather can be
saved. It is also not possible to create lines in this heather.
SOLUTION
DESCRIPTION:
In session tffas0520m000 (Periodical Depreciation and Revaluation
Results) the special depreciation code is checked. In case this
code was not found the system immediately generated an error message. This
should only occur when this field is filled with an unknow
depreciation code. Now it is also possible to create the lines.

Solution: 125567
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
The planned delivery date (tdsls401.ddta) on the sales order line was calculated as two days before the planned receipt
date (tdsls401.prdt – 2), using an assignment expression. When this order was received through EDI, the following error
occurred: "tdsls401.ddta 1024517805 Date Invalid".
SOLUTION
DESCRIPTION:
The error occurred because the Baan application handles dates as UTC numbers (number of seconds since 0:00 hour, January 1, 1970). The planned
receipt date is read before the planned delivery date. So the planned receipt date is internally represented by a number of seconds. Then
the planned delivery date is calculated as that UTC number minus 2 seconds. Subsequently, EDI expected a standard EDI date format on the
tdsls401.ddta field: CCYYMMDDHHMMSS, YYMMDDHHMMSS, CCYYMMDD, or YYMMDD. However, the date passed to the date check
functionality was a long number of 10 digits, resulting in an error. The program script has been modified to handle a date format of 10 digits,
representing an UTC date. Note that, if 2 days need to be subtracted from another date, the assignment expression needs to be set up as: "tdsls401.prdt
– 172800", since time needs to be expressed in seconds. The help text on the field "Assignment Expression" in session ecedi5111s000 has been
modified.

Solution: 125568
SITUATION IDENTIFIED IN:
"Tool Numbers by Tool Type" (titrp0102s000)
SITUATION DESCRIPTION:
When inserting a new tool in the session tool number by tool type, it is not possible to save the record if the linked
business partner has no purchase office filled in the session buy from business partner. This is introduced because of
solution 125099.
SOLUTION DESCRIPTION:
When inserting a new tool in the tool number by tool type session it is possible to save a record where the purchase office in
the buy from business partner is empty.

Solution: 125576
SITUATION IDENTIFIED IN:
"Budgets per Year" (tffbs0105s000)
SITUATION DESCRIPTION:
When a budget was entered in Budgets per year(tffbs0505m000) and zoomed to Budgets per year(tffbs0105s000), the rate
can be changed.
After saving and leaving the session, and entering again, the old values were there again. Only by tabbing through the
form, the new values can be showed.
SOLUTION DESCRIPTION:
Now, after saving and entering th e session again, the new entered values are shown

Solution: 125578
SITUATION IDENTIFIED IN:
"Project Status" (tipcs2502m000)
SITUATION DESCRIPTION:
When finishing or cancelling a project, the performance is bad
SOLUTION DESCRIPTION:
When finishing or cancelling a project, the performance is improved.
Note: It is impossible to estimate the performance gain as the improvement percentage basically depends on the size and
structure of a project. The query checking for negative stock has been improved approximately with a factor 6.

Solution: 125582
SITUATION IDENTIFIED IN:
"Write Off Currency Differences" (tfacp2240m000)
SITUATION DESCRIPTION:
The report from session "Write Off Currency Differences" (tfacp2240m000), is not printing the Invoice currency, hence it is
difficult to analyze the report.
SOLUTION DESCRIPTION:
The report is printing the invoice currency.

Solution: 125583
SITUATION IDENTIFIED IN:
"Print Packing Lists" (whinh4476m000)
SITUATION DESCRIPTION:
In all the following sessions
- whinh4470m000 "Print Bills of Lading"
- whinh4476m000 "Print Packing Lists"
- whinh4475m000 "Print Packing Slips"
when a report is generated for shipments, the carrier selection is ignored, having as a result that, if a carrier is selected,
some shipments that do not match the specified carrier are also printed.
SOLUTION DESCRIPTION:
If a carrier is specified, the report (of the three mentioned sessions) only prints the shipments that match the carrier.

Solution: 125585
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
1. The decimal values for the Discount are not displayed.
2. Description "Amount" missing in case of Swiss Invoices against the value shown.
SOLUTION DESCRIPTION:
Now the decimal values are correctly displayed and the description for the value is shown as "Amount"

Solution: 125586
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In session "Purchase Invoices - tfacp1110s000", when having several purchase invoices in the same batch, if the user
changes the Terms of payment of one invoice, then the batch becomes unbalanced.
SOLUTION DESCRIPTION:
The batch is no longer unbalanced.

Solution: 125589
SITUATION IDENTIFIED IN:
"Print Purchase Receipts" (tfacp1430m000)
SITUATION DESCRIPTION:
The report "Print Purchase Receipts" (tfacp1430m000) is not printing orders which are received and has ordered quantity as
zero.
SOLUTION DESCRIPTION:
The received orders with order quantity as zero are now printed on the report.

Solution: 125590
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
The Invoice-to address code on the sales order header (tdsls400.itad) is not supported via EDI. This field needs to be
supported because it is used in iBaan E-Sales.
SOLUTION DESCRIPTION:
The Invoice-to address code has been added a supported field. When added to the conversion setup (with or without
conversion), the code will be inserted on the sales order header.

Solution: 125596
SITUATION IDENTIFIED IN:
"Reminder Method" (tfacr3520m000)
SITUATION DESCRIPTION:
A reminder method is deleted even though it is attached to a business partner.
Need warning message in "Reminder method" and should not allow deleting the code.
SOLUTION DESCRIPTION:
A reminder method should not be deleted if it is attached to a business partner. It gives the warning message.

Solution: 125603
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
For a Generic item which has a phantom item in its BOM with planning percentage = 0% and valid routing operations, the
start and end date of the planned order are the same.
SOLUTION DESCRIPTION:
For a Generic item which has a phantom item in its BOM with planning percentage = 0% and valid routing operations, the
routing operations of the phantom are used in the calculation of the start and end date of the planned order.
SOLUTION 159242 IMMEDIATELY AFTER DOWNLOADING THIS SOLUTION.
VERSION(S):
B50_b, B50_c, B52_a

Solution: 125604
SITUATION IDENTIFIED IN:
"Process Hours Accounting" (tssoc2235m000)
SITUATION DESCRIPTION:
System is passing wrong integration entries while processing the hours accounting. For the labor rate $100 system is passing
the entry for $100.08 and for $200 it is pasing the entry for $199.87
SOLUTION DESCRIPTION:
BaanERP Service is now passing the correct cost amounts when creating financial transactions. The (small) differences occured
due to the fact that the total cost amount was calcutaled based on the cost rate and the actual time. As hours accounting lines
with the same significant properties are combined into one actual labor cost line the cost rate expresses the average cost rate.
Calculation using average rates can result in differences.
Now the total cost amount is calculated as the sum of all different cost amounts overwhich the amount is distributed.

Solution: 125605
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103m000)
SITUATION DESCRIPTION:
Journal lines were not dispalyed when you select the transactions through transaction schedule in the Journal voucher from
the Journal header.
SOLUTION DESCRIPTION:
Journal entries are displayed now.

Solution: 125621
SITUATION IDENTIFIED IN:
"Checks by checklist" (tsmdm0145m0001) (B50_c)
"Print Exceptions by Taxes for Service" (tsmdm0470m0001) (B50_b)
SITUATION DESCRIPTION:
When installing a solution with changes in version B50_c in form "Checks by checklist" (tsmdm0145m0001) or version
B50_b in form "Print Exceptions by Taxes for Service" (tsmdm0470m0001) it does not work as described in the Dutch
language (language1) or the German language (language 3)
SOLUTION
DESCRIPTION:
When installing solutions on form "Checks by checklist" (tsmdm0145m0001) or form "Print Exceptions by Taxes for
Service" (tsmdm0470m0001) it works correct in all maintained languages (Dutch (1), English(2) and German (3)).

Solution: 125629
SITUATION IDENTIFIED IN:
"Maintain and Confirm Back Orders" (tdsls4125m000)
SITUATION DESCRIPTION:
When trying to undo confirmation of a backorder that already was released to invoicing in "Maintain and Confirm Back
Orders" (tdsls4125m000), message "tdsls4125.unco ???????????" pops up.
SOLUTION DESCRIPTION:
From now on the right message that is called "Line already released to Central Invoicing. Unconfirming backorder not
allowed" (tdsls4125.unco), will be available.

Solution: 125630
SITUATION IDENTIFIED IN:
"OpenWorld"
SITUATION DESCRIPTION:
Openworld functionality is not available in B50b.
SOLUTION DESCRIPTION:
Openworld functionality backported. 6 objects.
Also the bic_include files are modified for it. Therefor solution 114812 should be installed.

Solution: 125639
SITUATION IDENTIFIED IN:
"Print Surveyor's Report" (tpppc4421m000)
SITUATION DESCRIPTION:
While running the session Print Surveyor's Report the system prints ############## for the fields Contract Amount , Amount
and Result . This is wrong .The system should print the correct values for these fields.
SOLUTION DESCRIPTION:
The above problem is solved.
Now the system prints the correct values for the fields Contract Amount, Amount and Result

Solution: 125645
SITUATION IDENTIFIED IN:
"Subcontracting Rates" (ticpr1160s000)
SITUATION DESCRIPTION:
Zero subcontracting rate is not allowed in Baan ERP. But zero value is allowed in Baan IV. This will be a problem for
customers who migrate from Baan IV to ERP.
SOLUTION DESCRIPTION:
Now, subcontracting rate can be zero.

Solution: 125649
SITUATION IDENTIFIED IN:
"Wrong account used during 'Write-off Currency Differences." (otfcorcont_ac05)
SITUATION DESCRIPTION:
If the correction program "Wrong account used during 'Write-off Currency Differences", if an invoice has multiple lines to be
corrected, even though all the lines are getting printed only the first line is corrected.
SOLUTION DESCRIPTION:
All the lines of the invoice are getting corrected.

Solution: 125652
SITUATION IDENTIFIED IN:
"Process Quotations" (tdsls1200m000)
SITUATION DESCRIPTION:
If a sales quotation is transfered to an actual sales order and a manufactured item is used on the quotation of which the main
item has a different inventory unit the the used parts in the Bill of Material, the session generates an error report saying: No
conversion factor found for unit X.
SOLUTION
DESCRIPTION:
Now it is possible to transfer the quotation to an actual order. The reason for the error was
tachnical. The inventory unit of main item in the Bill of Material was over written
by the Inventory unit of the component. While there was no conversion
factor between the two inventory units the system was not able to generate a sales order out of the quotation.

Solution: 125654
SITUATION IDENTIFIED IN:
"Batches for Electronic Statements" (tfcmg5500m000)
SITUATION DESCRIPTION:
There is no Save & Exit button (OK) on the form.
SOLUTION DESCRIPTION:
Now Save and Exit button is provided on the form

Solution: 125661
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements/RMAs" (tdsls4401m000)
SITUATION DESCRIPTION:
When printing the sales order acknowledgement/RMA (tdsls4401m000), the address information of the delivery address on the
header can have 8 lines (fixed) and the address information on the lines can have 4 lines (fixed). This discrepancy results in
to little address information on line level.
SOLUTION
DESCRIPTION:
The address information for the sales order line, printed on the report, has been extended to 8 lines. This information will
only be printed when the address information fields are filled: i.e. when the address information has only 5 lines, then only
5 lines are printed on the report. The information in those lines depends on the priorities defined in the Address Formats
session (tccom4535m000).

Solution: 125662
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (cisli2400m000/cisli2405m000)
SITUATION DESCRIPTION:
Tax number is derived directly from the table "tccom112" (Invoice-to BP). But if the user had changed the default Invoice-to
address during maintaining a sales line, then the tax number has to be derived from that particular address only.
SOLUTION DESCRIPTION:
Now the Tax number is derived and updated correctly in the Sales Listing Data .

Solution: 125665
SITUATION IDENTIFIED IN:
"Purchase-Invoice Transactions" (tfacp1120s000), "Journal Vouchers" (tfgld1103s000).
SITUATION DESCRIPTION:
In the session "Purchase-Invoice Transactions" (tfacp1120s000) or "Journal Vouchers" (tfgld1103s000), the ledger account
entered is related to Project Costs, and without saving, the option "Baan Project Transactions" is chosen from the specific
menu. The related information is entered and all the project-related sessions are saved and closed. The project-related
sessions that had been saved before opens again.
SOLUTION
DESCRIPTION:
The option "Baan Project Transactions" is opened only
once when adding a project-related transaction.

Solution: 125666
SITUATION IDENTIFIED IN:
"Print Cost Control" (tpppc4411m000)
SITUATION DESCRIPTION:
When Printing Cost Control a fatal error appeared ->
1 : process 12 - Fatal error : index 100 out of dims [1] 99
2 : process 12 - Fatal error : Can not continue in tpppc4411m000 ()[send.wait]
This is in case Element Budget has been selected as Control Type for the Project.
SOLUTION DESCRIPTION:
The fatal error has been solved. Printing Cost Control in situations with Element Budget as Control Type for the Project
won't cause errors anymore.

Solution: 125669
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
When we use the option 'Find->By description' with the option 'read before search' checked, then we get message
'tggbfs0041' many times.
We do not want to have to click away all those messages during the execution of the Find.
SOLUTION DESCRIPTION:
The messages appear, because in the menu tree of the end-user Business Processes are present, with in it not one activity for
which the end-user is authorized.
The showing of the message is correct functionality.
We can however imagine, that it can be confusing to get those messages during the execution of the Find. This because in
that case you also do not get to see the whole tree with the Business Processes for which the message is shown. You only get
to see the search result.
This is the reason, we changed the software, so that the messages will not be shown anymore during a Find with the option
'read before.search' checked.
The consequence of this is however that it also will not be shown anymore after execution of a Find with the option 'read
before.search',
when the end-user tries to open such a Business Process in the menu tree.

Solution: 125671
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When confirming a receipt for a lot item, if shipped from different lots, the final receipt flag is set to yes in a wrong line,
making impossible to confirm the rest of the lines.
SOLUTION DESCRIPTION:
Final receipt flag is set to true after shipped quantity, on all shipment lines, is checked, also when the lines are shipped from
different lots.

Solution: 125675
SITUATION IDENTIFIED IN:
"History - print Service Contracts" (tsctm8430m000)
SITUATION DESCRIPTION:
On the report 'History - Service Contracts' (tsctm843011000) which one can start through session 'History - Print Service
Contracts' (tsctm8430m000) the Sold-to BP number is not fully printed. The description overwrites the last two characters
of the Sold-to BP number.
SOLUTION
DESCRIPTION:
Both the Sold-to BP number and the description are now printed completely.

Solution: 125686
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When user defines the option "Collect Documents" as "Single Note by Invoice" in the "Invoicing Methods", seperate
invoices should be created if the document numbers are different between two Extension lines.
This is being done, if the document number is maintained as integers.
But if characters are used, then the document numbers are not considered during composing. A single invoice is being
created.
SOLUTION DESCRIPTION:
Now two invoices will be created even if characters differ between the document numbers entered.

Solution: 125695
SITUATION IDENTIFIED IN:
"Maintain and Confirm Backorders" (tdsls4125m000)
SITUATION DESCRIPTION:
When confirming a backorder for an ATP controlled Item the message "Quantity Exceeds 'available to promise' " might come
up. In case this happens when confirming a shipment and "Automatic Confirm Backorders" is set it is not possible to
confirm the shipment.
SOLUTION
DESCRIPTION:
When confirming the backorder an ATP check is done for the
backordered quantity. In case insufficient ATP is available on
the planned delivery date of the backorder a new date is determined
automatically. This is similar to the functionality provided
by the shortage menu in Sales Order
Lines
(tdsls4101s000)

Solution: 125702
SITUATION IDENTIFIED IN:
"TI and TC package" (ti and tc)
SITUATION DESCRIPTION:
Several forms in language 1 and 3 where not linked to base language 2.
Consequence can be that solutions which we create in US-English don't work for Dutch and German customers. Simply
because the forms and reports are not linked.
SOLUTION DESCRIPTION:
Forms and reports linked to language 2 (English)

Solution: 125710
SITUATION IDENTIFIED IN:
"Print Where Used Labels" (ttadv1445m000)
SITUATION DESCRIPTION:
When printing not found labels then empty label codes are printed.
SOLUTION DESCRIPTION:
Reason for this was that a form command with a empty label code exists on the form. Now these labels are not printed
anymore.

Solution: 125718
SITUATION IDENTIFIED IN:
"Process Transactions" (tpppc4802m000)
SITUATION DESCRIPTION:
Unable to close project. Error message : Project not reported completed, unprocessed purchase orders still exist", even
though all the purchase orders are processed.
SOLUTION DESCRIPTION:
Now the error message does not occur without valid reason and it is possible to Close Projects.

Solution: 125723
SITUATION IDENTIFIED IN:
"Initialize Roll and Update" (cprpd4200m000)
SITUATION DESCRIPTION:
After adding a new Resource and Updating the Scenario for a full item range (blank to ZZZ) the Resource Master Plan for
the new Resource is not updated, even when it is specified on the form
SOLUTION DESCRIPTION:
All Resource Master Plans are updated for the selected Resources

Solution: 125728
SITUATION IDENTIFIED IN:
"Purchase order Receipts" (tdpur4501m300)
SITUATION DESCRIPTION:
Creating 'Back Order' for purchase return orders is not possible.
SOLUTION DESCRIPTION:
It is possible to create Back Order for return purchase orders.

Solution: 125749
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
-1- * A purchase order is created and linked to a contract in "Purchase Order Lines" (tdpur4101s000)
* The 'Called Quantity' increases for this contract for this line.
* The above order is received by splitting up the receipt and the total received quantity is less than the ordered quantity.
* The back order is created automatically due to the parameter setting to 'Confirm the Back Order automatically'.
* At this time the 'Called Quantity' is reduced.
-2- * Purchase order type is 'Collect Order'
* One line is created with a 'Cost item' and negative 'Order Quantity' and the 'Purchase/General Cost' Integration
Transaction entry is created in "Integration Transactions by Project/Order" (tfgld4510m000).
* Another line is inserted now with positive 'Order Quantity' and the 'Purchase/General Cost' Integration Transaction created
for this line is with negative quantity and amount.
SOLUTION DESCRIPTION:
-1- The called quantity of the contract would not get reduced any more at the time of confirming the receipts.
-2- The quantity and amount in the new 'Purchase/General Cost' Integration Transaction entry will be correct.

Solution: 125753
SITUATION IDENTIFIED IN:
"Element Relationship" (tpptc1105s000)
SITUATION DESCRIPTION:
In tpptc1505m000, the budget status matches with the one of the parent element but looking at the details, the budget status is
within the child element details and the help text of the filed is misleading the user.
SOLUTION DESCRIPTION:
The field Buget status in the session "Element Relationship" is the status of parent-child element relationship and it is not
the status of the element. In real sense it has'nt got any significance. Hence the help text is now changed accordingly.

Solution: 125757
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120s000)
SITUATION DESCRIPTION:
In the session "Payment Advice", when the user changes the currency from invoice currency(e.g.ESB ) to any payment
currency(e.g. EUR) , the `amount to be paid´ field was not picking the correct amount .Also in the session "Payment
Advice"(tfcmg1501m000) , the "Amount in FC" was not displaying the decimal part of the amount.
SOLUTION
DESCRIPTION:
Now the field `amount to be paid´ is picking up the right amount , when the invoice currency is changed to any other payment
currency. In the session "Payment Advice"(tfcmg1501m000) , the "Amount in FC" is now displaying the
decimal part of the amount also.

Solution: 125758
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Unable to confirm shipment of transfer order with direct receipt and lot by unit item with more than 100 pcs.
SOLUTION DESCRIPTION:
The automatic processing of receipts is adapted and is now working like the manual receipt in building new sequence lines.

Solution: 125759
SITUATION IDENTIFIED IN:
"Regenerate Project Structure for Product Variant" (tipcs2220m000)
"Plan Item Data" (cprpd1500m000)
SITUATION DESCRIPTION:
After Regenerating a Project Structure for Product Variant (tipcs2220m000) or manually deleting a Plan Item, Plan Item
Codes for nonselected items are deleted.
As a result of this problem, no planned orders will be generated for the plan item.
SOLUTION DESCRIPTION:
Only data for selected item(s) is deleted

Solution: 125762
SITUATION IDENTIFIED IN:
"ttstpaudread" (ttstpaudread)
SITUATION DESCRIPTION:
NetList does not handle "drop/clear/create table" correctly
And
In version B50b the ostpaudread object does not exist.
SOLUTION DESCRIPTION:
Now the drop/clear and create table are correctly handled.
Ane the library is backported to B50b.

Solution: 125765
SITUATION IDENTIFIED IN:
"Print Business Partner wise Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
Aging Analysis gives wrong report in the Following cases:
1. When you receive the amount for the invoice before the due date and take the report is taken before due date.
2. Negative Anticipated Receipt is linked to a Sales Invoice.
3. When a Negative Sales Invoice used as a credit note to link it to another sales invoice
SOLUTION DESCRIPTION:
Now the Aging Analysis shows correct amounts When the report is taken before the due date and gives correct classification
of the age of the invoices

Solution: 125768
SITUATION IDENTIFIED IN:
"Copy Sales Order" (tdsls4201s000)
SITUATION DESCRIPTION:
When a sales order is copied to a new sales order and there are detail lines present having other ship to addresses, still the
session add all details together to one new sales order line without details. This is not correct since these ship to addresses
are changed in the details on purpose and this should be refelcted in the new order as well.
SOLUTION
DESCRIPTION:
This issue has been solved now. The following changes
are made to the copy sales
order session.
If a sales order line is entered and after
entry the order line is splitted to
change delivery details like:
Ship to Address, Warehouse the
changed data must be
taken into account while
copying.
The following has been done for this. Before
the actual copy starts all detail lines
are screened and there is check
which detail lines can be merged since
they have the same delivery data. If this
check is done the actual copy starts and new
order lines and details are created.
I will
try to
make
this more
clear
using
an
exam
ple:
Sales order ABC1 is created with 1 order line having 5 pcs of item iBaan-Saleskit on it. This sales order is raised by one Sold-to business Partner, but
delivey must be done at two different places. 2 iBaan-Saleskits must be delivered in Hannover (Germnay) and 3 iBaan-Saleskits must be delivered in
Paris (France). Two of the iBaan-saleskits will be shipped through mail and delivered at the Sales Office in Paris, the last one will be shipped with
United Parcel Service directly to the customer which is in Lyon.
So, what will be there in the sales
order is one total line with
5 pcs
iBaan-Saleskit
and three detail lines.
detail 1 2 pcs
iBaan-Saleskit
delivery address: Hannover
detail 2 2 pcs
iBaan-saleskit
delivery address: Paris
detail 3 1 pcs
iBaan-Sales
kit
delivery address:
Lyon
If we now copy this order into a new order we will get exactly the same order with the mentioned details. Before this solution you would have had only
one sales order line having 5 pcs iBaan-Saleskit without details.
There is an option on the form of copy sales orders with the label 'Use delivered quantities' If this field is ticked the delivered quantities of the copied
order lines will be taken instead of the ordered quantities. If you copy a
line without quantities delivered, you will recieve the message 'No suitable order lines found to be copied'. The reason for this is that no deliveries are
found for this order line. If we take the example described above and we asume that the iBaan-saleskits for Hannover are delivered, but the Frence ones
not. Now you copy the sales order ina new order with the field 'Use delivered quantities' ticked. This will result in one sales order line with 2 pcs
iBaan-saleskit with delivery address Hannover. The detail lines for France will not be copied, since no deliveries are done for these lines.
Order lines with quantity 0 (zero) but
which do have an amount will be copied always no matter whether
the field 'Use delivered quantities' is ticked on the form of sesion Copy Sales Orders (tdsls4201m000)
If a sales order line has a delivery scheme,
e.g. different delivery dates for several details
but the rest of the data is the same on
detail lines. The copy session will merge these
line into on new sales order line.
This situation is
described in
the
example
below:
Sales order ABC! with one order line with 10 pcs iBaan-saleskit. This order line is split in several
details since
not all
iBaan-Salesk
its must be
delivered on the same
date.
detail 1 3 pcs
iBaan-Salesk
it delivery date: 1
july
2002
detail 2 5 pcs
iBaan-saleski
t delivery date: 14
july
2002
detail 3 2 pcs
iBaan-Saleski
t delivery date: 20
july
2002
If this sales order is copied to a new sales order, this
will result in one new sales order having one
sales order line with 10 pcs
iBaan-saleskit and the delivery
date will be based on the order date of the new sales order.

Solution: 125774
SITUATION IDENTIFIED IN:
"Cycle Counting / Adjustment Order Lines" (whinh5501m000)
SITUATION DESCRIPTION:
The parameter 'Block During Warehouse Cycle Count' is checked in "Inventory Handling Parameters" (whinh0100s000).
The 'Stock Points' are blocked if the Cycle Counting order is generated from the session "Generate Cycle Counting
Orders" (whinh5200m000). But if a new stock point is added in "Cycle Counting / Adjustment Order Lines"
(whinh5501m000), it is not blocked.
SOLUTION DESCRIPTION:
The 'Stock Point' corresponding to the manually entered Cycle Counting Lines would also be blocked now.

Solution: 125779
SITUATION IDENTIFIED IN:
"Purchase Orders" (tdpur4100s000)
SITUATION DESCRIPTION:
When a series of Planned Purchase Orders are transferred at same time, the "Buyer" values in some of the generated
Purchase Orders have got incorrect values
SOLUTION DESCRIPTION:
Now, the "Buyer" values are inserted correctly when multiple Planned Purchase Orders are transferred at same time.

Solution: 125784
SITUATION IDENTIFIED IN:
"Close year" (tfgld6203m000)
SITUATION DESCRIPTION:
Transaction entry date was not defaulted in the session.The user can process the year without entering the date and which will
result in no transaction entry date in the opening balance transaction type.
SOLUTION DESCRIPTION:
The transaction entry date is defaulted.

Solution: 125785
SITUATION IDENTIFIED IN:
"Wrong account used during 'Write-off Currency Differences" (otfcorcont_ac05)
SITUATION DESCRIPTION:
If the invoice which has to be corrected has a currency difference line per currency, then only the first currency
difference line was getting corrected by the correction program "Wrong account used during 'Write-off Currency
Differences" (otfcorcont_ac05).
SOLUTION DESCRIPTION:
All the lines are getting corrected.

Solution: 125797
SITUATION IDENTIFIED IN:
"Release to Invoicing (Batch)" (tdsls4247m000)
SITUATION DESCRIPTION:
When Releasing a range of Sales Orders to Invoicing using session "Release to Invoicing (batch)" (tdsls4247m000), for which
the Sold-To Business Partners are in descending order, not all Sales Orders are printed on the report.
SOLUTION DESCRIPTION:
The selected range of Sales Orders are now being processed in the right order. It was assumed the order of the selected
Sales Order was ascending, which was not always the case.

Solution: 125798
SITUATION IDENTIFIED IN:
"Print Reminder" (tdpur4403m000)
SITUATION DESCRIPTION:
Reminder is printed for a purchase order line, even if a receipt is created in Baan Warehousing, but not yet confirmed.
This may be a problem for a Purchaser, because sometimes, the reminder might be sent to a supplier, even after goods are
received in warehouse, but receipt is not yet confirmed.
SOLUTION DESCRIPTION:
Now, a check box is provided on the form of the session.
The label of the check box is 'Print Lines with Unconfirmed receipt'.
If this check box is selected, Reminder will be printed for all Purchase order lines, including those lines for which a
unconfirmed receipt exists. (As it used to be).
If this check box is not selected, then Reminder will not be printed for those purchase order lines for which a receipt exists
in Warehousing, but not yet confirmed.
By default, this check box is selected by the system.

Solution: 125805
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2500m000)
SITUATION DESCRIPTION:
When setting a Service Order to costed sometimes message tssocs4019: Purchase Amount is not finalized in Finance is
coming, although the related invoice document is finalized. This situation only occurs when more then 1 line is entered in
session 'Matched Purchase Invoice Transactions' (tfacp1133s000).
SOLUTION
DESCRIPTION:
The message 'tssocs4019: Purchase Amount is not finalized in Finance' will only come when setting the Service Order /
Service Order Activity / Service Order Costline to status 'Costed' and the related document is not yet finalized.

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

Solution: 125815
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
System gives error 205 when the user runs Planning, "Simulate Orders (cprrp1210m000)", on table tdpur313. The problem is
reproducible only in the customer system but not in our internal system. System at any point of time shouldn't give any kind
of Fatal Errors.
SOLUTION
DESCRIPTION:
Now changes are made such that system doesn't give error 205 when user runs planning for a range of items.

Solution: 125821
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120m000)
SITUATION DESCRIPTION:
Field Total Amount by BP doesn't show the right amount in case of an 'Advance Receipt' in LOCAL CURRENCY and with
option 'Calculate Tax on Advance Payments/Receipts' ON.
SOLUTION DESCRIPTION:
Field Total Amount by BP shows the right amount in case of an 'Advance Receipt' in LOCAL CURRENCY and with or
without the option 'Calculate Tax on Advance Payments/Receipts' ON.

Solution: 125825
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4501m000)
SITUATION DESCRIPTION:
Modified amounts are not correctly updated in the Direct Debit Advice session.
SOLUTION DESCRIPTION:
Modified amounts are now correctly updated in the Direct Debit Advice session.

Solution: 125833
SITUATION IDENTIFIED IN:
"Print Supplier's Total Balance by Company" (tfacp2434m000)
SITUATION DESCRIPTION:
In sessions "Print Supplier's Total Balance by Company" (tfacp2434m000) and "Print Customer's Total Balance by Company"
(tfacr2434m000) it is not possible to print the report by Fiscal Period where the Fiscal year is earlier than the current
Fiscal year. When the fiscal year is changed to an earlier year, the error message "To Year cannot be less than Current
Financial Year" comes up.
SOLUTION DESCRIPTION:
It is now possible to print the report by Fiscal Period for a year, which is earlier than the current year.

Solution: 125834
SITUATION IDENTIFIED IN:
"whinh3520m000" (Receipts)
"whinh3201m000" (Generate Inbound Advice)
SITUATION DESCRIPTION:
Goods are not cross-docked in specific situations with split deliveries.
Example:
Sales order with linked purchase order.
On both orders the detail line is split as follows: Detail 1 has 6 pcs; detail 2 has 4 pcs
Sales order detail 1 is already completely delivered from stock.
Purchase detail 1 is received.
Now an inbound advice is generated.
Result:
4 pcs are advised to the staging location.
For the remaining 2 pcs no location can be found.
If the inbound advice is created again, the remaining 2 are correctly advised to the pick/bulk location.
This should have been done in the first run.
SOLUTION DESCRIPTION:
The inbound advice is generated properly.

Solution: 125837
SITUATION IDENTIFIED IN:
"Transfer Payments" (B40L_c_nc20: tfcmg1260s000 / B50_b & B50_c: tfcmg1260m000)
"Maintain Payment/Receipt Methods" (tfcmg0140m000)
"FIN, SYP (2499), Foreign" (B40L_c_nc20: tfcmg126020030 / B50_b & B50_c: tfcmgL2561100L)
"FIN, LUM2 (LUM2), Foreign" (B40L_c_nc20: tfcmg126020040 / B50_b & B50_c: tfcmgL2561200L)
SITUATION DESCRIPTION:
In the session "Transfer Payments" (tfcmg1260s000), the payment data is transferred to the chosen payment file. When
the Finnish bank file ULMP (tfcmg126020030, report group 30 / tfcmgL2561100L, report group 23) or LUM2
(tfcmg126020040, report group 33 / tfcmgL2561200L, report group 24) has been chosen, the IBAN code is not yet available.
SOLUTION DESCRIPTION:
With this solution, the IBAN functionality will come available for this report, when the field "Use IBAN account" in the
session "Payment/Receipt Methods"(tfcmg0140m000) has been set to 'Yes'.

Solution: 125841
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
2 problems occur when 'Transfer Payments' (tfcmg1260s000) in case of sales credit notes and negative sales invoices:
1st- invoice date is not printed on check reports.
Empty date on report groups: 3 (Checks), 10 (Checks, German Layout) and 15 (Checks, USA Layout).
2nd- (only for Checks, USA Layout)
Document number is printed as reference at the second column 'Reference', furthermore the same document number is printed,
again, on column 'Invoice'. Therefore, document number is printed twice right next to each other.
SOLUTION DESCRIPTION:
1st problem:
Invoice date is printed on the check on column 'Invoice Date'.
2nd problem:
Document number is not printed on column 'Reference'. Reference, in case of sales credit notes and negative sales invoice,
remains empty.
The document number is only printed once, on column 'Invoice'.

Solution: 125846
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
200225, 207485
Descriptions:
- Defect 200225 Synchronized child not started when no data found in child session
- Defect 207485 AFS After insert controll does not go back to parent.
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 125848
SITUATION IDENTIFIED IN:
"Print Control Account Checklist" (tfacp2415m000)/ tfacr2415m000.
SITUATION DESCRIPTION:
Incase of advance payments, when the document has been removed partially by " Remove Fully Paid Invoices " session, the
control account checklist shows differences even when there is no difference.
SOL 126782 has reversed SOL 125848
SOLUTION DESCRIPTION:
Now, when the Advance payment document has been removed, partially, those document lines will not be considered by this
session for printing.
SOL 126782 has reversed SOL 125848

Solution: 125853
SITUATION IDENTIFIED IN:
"Inventory by Warehouse, Item and lot" (whinr1540m000)
SITUATION DESCRIPTION:
1. Intra Warehouse - Transfer(Manual) order is created with a specific lot code entered in the "Outbound Order Lines"
(whinh2120s000).
2. The 'Allocated' quantity for the lot is increased in "Inventory by Warehouse, Item and lot" (whinr1540m000), at the time
the order line is created.
3. When the outbound advice is released, the 'Allocated' quantity is reversed back to the original quantity.
4. Again the 'Allocated' quantity is reduced by order quantity with the removal of warehousing order from the session
"Remove Closed Warehousing Orders" (whinh2250m000).
SOLUTION DESCRIPTION:
The 'Allocated' quantity in "Inventory by Warehouse, Item and lot" (whinr1540m000), will not be reduced when the
order is removed from "Remove Closed Warehousing Orders" (whinh2250m000).

Solution: 125854
SITUATION IDENTIFIED IN:
"Print Employees" (tccom0401m00)
SITUATION DESCRIPTION:
In "Print Employees" the employees, who are currently employed after the reference date should be printed. However,
system prints all the employees after reference date including the Employees, who are no longer employed.
SOLUTION DESCRIPTION:
List of Employees working after the reference date are printed. And the employees who are not working with the
Organization are excluded from the list.

Solution: 125857
SITUATION IDENTIFIED IN:
"Ledger Accounts by Business Partner Group" (tfacr0111m000)
SITUATION DESCRIPTION:
Error when defining same "Deductions Ant. Receipts" account for all B.P.Groups
SOLUTION DESCRIPTION:
Deduction anticipated was added as a Control account(by SOL 119656 )
In addition to that it is now possible to use the already existing control account as "Deduction anticipated". (except for the
current BP)

Solution: 125860
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A sales office specified in user defaults will override the sales office from the BP at sales header entry (tdsls4100s000).
However, you aren't warned of this difference on the sales side (a warning is given for this situation on the purchase side)
If you did not have a user default set up and entered the same sales office manually, you do get a message noting that this
sold-to business partner is linked to another sales office
This is not consistent.
SOLUTION DESCRIPTION:
A message is given for this condition

Solution: 125861
SITUATION IDENTIFIED IN:
"Update Customer Statistics" (tfcmg3200m000)
SITUATION DESCRIPTION:
If session 'Update Customer Statistics' is run for a customer who has negative sales invoices. Then, the 'Average Days
Outstanding' shows incorrect and unreliable values.
SOLUTION DESCRIPTION:
After running 'Update Customer Statistics' (tfcmg3200m000) the 'Average Days Outstanding' is showing correct figures.
Even, when negative sales invoices are involved on the average calculation.

Solution: 125870
SITUATION IDENTIFIED IN:
"Reminder Advice by Credit Analyst" (tfacr3116m000)
SITUATION DESCRIPTION:
In Reminder Advice by Credit Analyst, 'As On Date' and 'Until Due Date' are not disabled.
SOLUTION DESCRIPTION:
'As On Date' and 'Until Due Date' are disabled.

Solution: 125878
SITUATION IDENTIFIED IN:
"Print Reminder" (tdpur4403m000)
SITUATION DESCRIPTION:
Help text required for the field 'Print Lines with Unconfirmed receipt'.
SOLUTION DESCRIPTION:
Help text is now available for the field 'Print Lines with Unconfirmed receipt'.

Solution: 125882
SITUATION IDENTIFIED IN:
"Shift Production Planning" (tisfc1202m000)
SITUATION DESCRIPTION:
When the user Shift Production Planning, the delivery date is not updated in the outbound order line.
SOLUTION DESCRIPTION:
System will update the delivery date in Outbound Order Lines along with the Production Planning when the Production Plan
is shifted.

Solution: 125888
SITUATION IDENTIFIED IN:
"Process transactions" (tpppc4802m000)
SITUATION DESCRIPTION:
When revenues are booked to history during 'Process Transactions', an error 205 (Out of range) can occur if more than 9999
lines have been booked on the same revenue code for a project.
SOLUTION DESCRIPTION:
The domain for the sequence number was enlarged for the revenue history table and the table will now accept up to 999999
lines on the same revenue code for a project.

Solution: 125892
SITUATION IDENTIFIED IN:
"Purchase-Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
After entering a subconracting invoice of type "Cost Invoice" with level of tax transaction as "Invoice Header", then it was
not possible to save the Lines transaction. The error message "In case of subcontracting, only Tax code of type "shifted" is
allowed" comes up.
SOLUTION DESCRIPTION:
It is now possible to save the lines transactions when the level of tax transaction is "Invoice Header" and type
subcontracting.

Solution: 125894
SITUATION IDENTIFIED IN:
"Integration Transactions by project/order" (tfgld4510m000)
SITUATION DESCRIPTION:
Too many financial Transactions were posted in finance for a direct delivery sales order.
SOLUTION DESCRIPTION:
The financial transactions are correctly posted in finance for a direct delivery sales order

Solution: 125896
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
When reporting a production order completed and the sum of the quantity completed and the quantity rejected exceeds the
quantity ordered, materials are only backflushed for the ordered quantity.
SOLUTION DESCRIPTION:
Backflushing is now done for the total of completed and rejected quantity.

Solution: 125904
SITUATION IDENTIFIED IN:
"Calculate Demand Forecast by Item " (whina2202m000)
SITUATION DESCRIPTION:
Help Text is not available for the check box "Update" in the session "Calculate Demand Forecast by Item "
SOLUTION DESCRIPTION:
Helptext is added to the check box " Update " in the session "Calculate Demand Forecast by Item "

Solution: 125909
SITUATION IDENTIFIED IN:
"Posting data Standing order/Stand alone payments" (tfcmg1510m000 @ tfcmg1410m000)
SITUATION DESCRIPTION:
Digits after Dec. Point was not displayed in amount field when transaction currecy is foreign one
SOLUTION DESCRIPTION:
Now disgits after Dec.Point is displying in amount field when transaction currency is foreign one.

Solution: 125910
SITUATION IDENTIFIED IN:
"Subcontracting Invoice" (tfacp3160s000)
SITUATION DESCRIPTION:
While entering the subcontracting details for a credit note in session "Subcontracting Invoices" (tfacp3160s000), the error
message "Error 205 on tfacp303 in db.update(51) - can not continue in session" comes up and the session aborts if the field
"Number of Hours" is greater than zero.
SOLUTION
DESCRIPTION:
No error message comes when a credit note
subcontracting invoice is entered where the "Number
of hours" field is greater than zero.

Solution: 125917
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
Cost of Goods Sold amount (tdsls401.copr) are getting updated with incorrect values when session tdpur4223m000 is run for
a Purchase Order with links to multiple Direct Delivery Sales Orders.
This only applies in case the valuation method is FIFO and the Cost Price of the item has surcharges
SOLUTION DESCRIPTION:
The problem is caused by not initialized variables. Variables are now set correctly when determining the surcharges

Solution: 125919
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Purchase order not automatically generated for normal sales order (Cross Docking). Parameter descriptions not clear.
SOLUTION DESCRIPTION:
The parameter help texts within session "Sales Order Parameters" (tdsls0100s400) are completed for the folowing options :
Generation of Planned Purchase Order Advice
Generation of Purchase Order
The old help texts suggests that these options are also valid for non direct delivery orders.
This is not correct. In case an order type allows to generate purchase orders does not mean that all orders created for this
order type need to be linked to a purchase order for Cross Docking functionality.
Only in case an order line is set up for direct delivery it is sure that a purchase order (advice) needs to be created to complete
the process.

Solution: 125921
SITUATION IDENTIFIED IN:
"Print Quotations" (tdsls1401m000)
SITUATION DESCRIPTION:
Within a quotation line the product variant of a generic item is inserted.
After the line is saved an alternative line is created for the same item and a new product variant is created.
A budget structure for both lines needs to be generated.
When printing the quotation with use of session tdsls1401m000 (report rtdsls140102000) the components of the original and
the alternative are gathered to give two times the price of the variant. Alternative variants need not being gathered on a
quotation report as the customer should be able to distinguish between the options.
SOLUTION DESCRIPTION:
For each variant number a separate annex is printed

Solution: 125931
SITUATION IDENTIFIED IN:
"Process Inbound via DDC" (whinh3200b000)
"Approvals from Customers" (whinhl101m00l)
SITUATION DESCRIPTION:
The user is unable to compile the following program scripts:
- script used for receiving via DDC (B50_c and B50_b)
- script used for registering the Approvals from Customers. (only B50_b)
SOLUTION DESCRIPTION:
Both scripts can now be compiled.

Solution: 125932
SITUATION IDENTIFIED IN:
"Warehousing Easy Order Entry" (whinh2202m000)
SITUATION DESCRIPTION:
When entering an order through 'Warehousing Easy Order Entry' (whinh2202m000) with order origin "Production (manual)" ,
the workcenter (department) is not passed to the finance table 'Additions to Integration Transactions' (tfgld415).
Therefor this field cannot be used as key element in the integration for Warehousing (PRD Manual)/Issue .
SOLUTION DESCRIPTION:
Department is now passed to finance table 'Additions to Integration Transactions' (tfgld415), so this field can be used as
key element in the integration for Warehousing (PRD Manual)/Issue .
Note: in whinh2202m000 the department field is labeled 'Office' .

Solution: 125935
SITUATION IDENTIFIED IN:
"Match Purchase Receipt Lines" (tfacp2544m000)
SITUATION DESCRIPTION:
There is an order with 2 position lines. The first order/position is completely matched with an invoice using the option
"Match with Orders". For the second invoice the order number field on the purchase invoice is filled with the order number
and the option "Match with Receipts" is chosen. On the session "Match Purchase Receipt Lines" (tfacp2544m000) the first
matched order line is also displayed along with the second unmatched position line.
SOLUTION DESCRIPTION:
The completely matched order is now not shown when the option "Match with receipts" is chosen.

Solution: 125939
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120m000)
SITUATION DESCRIPTION:
1) Amount paid field of the standing order is not updated when you create the anticipated document.
2) It is selecting the paid standing order in the payment advice when you select it through manually.
SOLUTION DESCRIPTION:
Amount Paid filed of the standing order updated correctly and It is not possible to select already paid standing order in the
payment advice manually.

Solution: 125940
SITUATION IDENTIFIED IN:
"Qualified demand by period " (whinr1520m000)
SITUATION DESCRIPTION:
1. The value of 'Actual Issues' field in "Qualified demand by period " (whinr1520m000) is increased when the Item is
issued to the Shop floor from the Warehouse.
2. Again if goods are returned back from the Shop floor to the Warehouse, the value in this field is not decreased.
3. Due to this the 'Slow moving Analysis' could not be performed as the value of Actual issue in the system does not reflect
the real actual issue.
SOLUTION DESCRIPTION:
Now, the value of the 'Actual Issues' field in the session "Qualified demand by period " (whinr1520m000) would be
decreased by the amount of goods returned back from the shop floor.

Solution: 125942
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
Field "Overtime" (tssoc200.otim) on the Service Order Header is not filled with the contract data. When planning from a Call
to a Service Order this can even lead to Fatal error 205 (Out of range).
SOLUTION DESCRIPTION:
When creating a Service Order header field "Overtime" (tssoc200.otim) is filled with data from the Contract, if applicable.
If no Configuration is specified on the Service Order but on the first Service Order Activity a Configuraton is specified
during creation or update on this Activity, the Contract information will be updated on the Service Order Header. This
includes the "Overtime" field.

Solution: 125943
SITUATION IDENTIFIED IN:
"Convert Requisition Lines to RFQ/PO" (tdpur2201m000)
SITUATION DESCRIPTION:
Requisition status are not updated correctly for purchase requisition approval session
SOLUTION DESCRIPTION:
Now, the system updates the status correctly for the Purchase Requisition Approval session.

Solution: 125948
SITUATION IDENTIFIED IN:
"Generate Inbound Advice " (whinh3201m000)
SITUATION DESCRIPTION:
1. A receipt is made via "Packing Structure Receipt" (whinh3816m000) in a way that receipts are entered in various levels
of the package definition.
2. The 'Inbound Advise' is generated from the session "Generate Inbound Advice " (whinh3201m000) for this order.
3. The capacity check for the 'Location' fails and the quantity advised to location goes beyond the capacity limit of the
location.
SOLUTION DESCRIPTION:
The inbound advice would now get generated corresponding to the capacity of the location. If it exceeds the capacity it would
go and advice to the next location.

Solution: 125949
SITUATION IDENTIFIED IN:
""Aggregate Channels, Plans and Orders"" (cppat2210m000)
SITUATION DESCRIPTION:
When aggregating from a site in a different timezone, the quantities are distributed wrong. Period definitions in all sites are
equal, but due to the different timezones, the start/end times of the periods are different, causing the periods in the different
sites to overlap. Overlapping periods result in incorrect aggregation.
SOLUTION
DESCRIPTION:
When aggregating with
'overlapping'
periods, the distribution over
the overlapping periods
is
proportional
to the
'over
lap'.

Solution: 125956
SITUATION IDENTIFIED IN:
"Release to Central Invoicing (Batch)" (tdsls4247m000)
SITUATION DESCRIPTION:
The Sales Order Lines of a Sales Order of the Type Collect Order and Cost Order should automatically be processed in
Central Invoicing.
This is not always possible as, if the Cost or Service Item should not be released to Warehousing, the delivered quantity and
the delivery date must be filled in manually in the session tdsls4501m130 (Release Line to Central Invoicing).
SOLUTION DESCRIPTION:
If a Cost or Service Item should not be released to Warehousing, the delivery date and the delivered quantity will
automatically be filled in, when releasing the Sales Order Line to Central Invoicing.
If the Item's Cost Price has not be calculated, the Sales Order Line will not be released automatically to Central Invoicing as
the user should still fill in the cost price in the session tdsls4501m130 (Release Line to Central Invoicing).

Solution: 125960
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
When handling a list item (type kit) in an automatic return sales order, message "No data within selection" is displayed, and
the lines remain in status "Release to Warehousing".
This happens because the main item has outbound priority by location and at least one of the components has LIFO/FIFO,
causing that only the outbound priority of the main item is considered.
SOLUTION DESCRIPTION:
The outbound priority for the components is checked , and in case one of them has it LIFO/FIFO, the inventory date is
filled. The system can now continue processing the sales order.

Solution: 125969
SITUATION IDENTIFIED IN:
"Commitments (Material)" (tpppc2510m000)
SITUATION DESCRIPTION:
1. Some values is entered in the 'Discount' field of "Purchase Order Headers" (tdpur4100s000) session.
2. A line is created for this order with a Baan project.
3. The amount posted in "Commitments (Material)" (tpppc2510m000), does not consider the purchase order header
discount.
SOLUTION DESCRIPTION:
The project commitment created in "Commitments (Material)" (tpppc2510m000) would consider the purchase order header
discount percentage also now.

Solution: 125982
SITUATION IDENTIFIED IN:
"Finalization process" (tfgld1212s000)
SITUATION DESCRIPTION:
When a correction is done on the vatcode of an invoice by changing the normal vatcode to a vatcode of type on payment the
interim vat on payments account is not reversed when a payment or receipt is done and no posting is done on the actual vat
account.
SOLUTION DESCRIPTION:
Also when a correction is done the vat on payment is handled correctly now.

Solution: 125987
SITUATION IDENTIFIED IN:
"Sales-Order Lines" (tdsls4500m000)
SITUATION DESCRIPTION:
A generic item is entered on a sales order line. Instead of configuring the generic item, a zoom is done on the field "Product
Variant". The list shown contains only standard variants and variants related to the sales order one is zooming from. If a
variant is selected there is only the possibility to copy the standard variants.
SOLUTION DESCRIPTION:
A generic item is entered on a sales order line. Instead of configuring the generic item, a zoom is
done on the field "Product Variant". The list shown contains all variants related to the generic
item. If a variant is selected there is the possibility to copy the variant. The new variant
will have reference type "sales order". The reference order will be filled with the
sales order number. The reference position will be filled with the sales
order position number. The business partner of the
new variant is taken from the
sales order.
Similar functionality is availble for
sales
quotations
.

Solution: 125990
SITUATION IDENTIFIED IN:
"Copy Purchase Orders" (tdpur4201s000)
SITUATION DESCRIPTION:
1. A Purchase Order Line is created and a 'Discount' is entered manually in the line apart from the default discount
retrieved from Pricing module.
2. This purchase order line is copied to new order via the session "Copy Purchase Orders (tdpur4201s000)" with the check
box "Calculate New Price and discounts" selected.
3. The manual discount of the source order is still present in the new order, over and above the default discount at the time
of copying.
SOLUTION DESCRIPTION:
The manual discount of the source order will be overwritten by the default discount at the time of copy if the check box
"Calculate New Price and discounts" is selected in the session "Copy Purchase Orders (tdpur4201s000)".

Solution: 125992
SITUATION IDENTIFIED IN:
"Transfer Purchase Order Advice" (whina3212m000)
SITUATION DESCRIPTION:
1. There are Purchase Order Advices in "Purchase Order Advices" (whina3510m000) and the first one is for 'Direct delivery'
Sales Order and the second one is for 'Cross Docking' Sales Order.
2. Both the advices are confirmed together.
3. They are transferred together and the first advice (Direct Delivery) alone is getting converted to purchase order and the
second (Cross Docking) advice is not converted to Purchase Order.
SOLUTION DESCRIPTION:
Now both the 'Purchase Order Advices ' are getting converted to actual Purchase Orders when they are transferred together.

Solution: 126005
SITUATION IDENTIFIED IN:
"Global (Un)Block Lots" (whinh6220m000)
SITUATION DESCRIPTION:
Corrupt inventory after global blocking of lots without inventory.
SOLUTION DESCRIPTION:
Initializing new created records for 'lots by warehouse' table prevents from corrupt data.

Solution: 126013
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2500m000)
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
When setting a Service Order to Costed in session Service Orders (tssoc2500m000 or tssoc2100s000) which is transferred
from a Call and contains a Configuration Change defined on the Service Order Activity, the following error is given:
Error : Load DLL: Incompatible array subscripts in link external 'object.model' (dal.open.dal() in object ottstpamdll)
Error : Load DLL: Subscripts 1, source 50, external 100 (dal.open.dal() in object ottstpamdll)
Fatal error : Dynamic Link failure external symbol 'object.model' in DLL object 'otsclm100'
Fatal error : Can not continue in tssoc2500m000 in DLL: ottstpamdll (dal.open.dal)[exec_function]
SOLUTION DESCRIPTION:
When setting a Service Order to Costed which is transferred from a Call the process runs as should and the Service Order
status is set to Costed. No error messages appear.

Solution: 126015
SITUATION IDENTIFIED IN:
"Print Purchase Contracts Line Reports" (tdpur3411m000)
SITUATION DESCRIPTION:
When the selected contract number is marked and tried for printing the purchase contract line reports then the selected
contract number was not displayed in the print session.
SOLUTION DESCRIPTION:
The selected contract number will now be displayed on the print session.

Solution: 126024
SITUATION IDENTIFIED IN:
"Print Cost Control" (tpppc4411m000)
SITUATION DESCRIPTION:
While trying to print the report Cost Control by Project/Element the system is not aggregating the Revenues.This is wrong.
The system should aggregate and print the correct values for the revenues.
SOLUTION DESCRIPTION:
The above problem is solved.
Now when the system is printing the report for Cost Control by
Project/Element the system is aggregating the values of the Revenues .

Solution: 126030
SITUATION IDENTIFIED IN:
"Generate E-items by ECO" (tiedm3120m000)
SITUATION DESCRIPTION:
Generate E-item by ECO is linking the E-items to ECO in which a component that is to be replaced, even if the component to
be replaced is present in the Engineering Bill of Material of previous revision of the Engineering Item and not present in the
Engineering Bill of Material's latest revision.
SOLUTION
DESCRIPTION:
Generate E-item by ECO should link the E-items to ECO in which a component that is to be replaced, only if the component to
be replaced is present in Engineering Bill of Material of latest revision of the Engineering Item.

Solution: 126033
SITUATION IDENTIFIED IN:
"Maintain ECO Lines" (tiedm3120m000)
SITUATION DESCRIPTION:
Physical quantity fields(Number of units, length, width and Quantity ) in the Engineering Change Order (ECO) Lines are not
disabled correctly
SOLUTION DESCRIPTION:
The fields are disabled correctly

Solution: 126036
SITUATION IDENTIFIED IN:
"whinh5500m000" (Process Cycle Counting Adjustmemt Orders)
SITUATION DESCRIPTION:
-1- When processing a Cycle Counting Adjustment Order with a negative adjustment quantity (the adjustment will thus be
handled as an Issue) AND a negative surcharge (Issue or Receipt) had been calculated, the Inventory Receipt
Consumption Table (whinr114 B50_b, whinr115 B50_c) was incorrectly updated.
The negative surcharges were registered as
positive amounts instead of
beeing negative.
-2- Integration transactions of
the type Warehouse Order / Correction
should be generated, even
if the amount to be
posted to Finance is
zero.
(the transactions are thus created as long as the
quantities to be posted to Finance
are not
zero).
-3- Integration
transactions are created
with a zero amount for
the cost component of the
type "Operation Costs", even if
no cost price has been calculated for
the operation costs.
(this is the case of
Purchase Items)
SOLUTION
DESCRIPTION:
-1- Inventory Receipt Consumption Table (whinr114 B50_b, whinr115 B50_c) is now properly updated.
-2- Integration Transactions
will now be created
for this type
of
transactions.
-3- Non- required Integration Transactions with a
zero amount will not be
created anymore.

Solution: 126040
SITUATION IDENTIFIED IN:
"Print Item Revisions by Engineering Change Order" (tiedm3460m000)
SITUATION DESCRIPTION:
Zooming on revision field always go to the first item in the session Print Item Revisions by Engineering Change Order
SOLUTION DESCRIPTION:
System uses "From Item" for zooming to the revisions and the correct revision is displayed.

Solution: 126042
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
It is not possible after service pack 7 to enter a back order quantity during "Sales Order Entry" (tdsls4101s000)
SOLUTION DESCRIPTION:
In the past this functionality has been disabled. This was done because of numerous problems that could not be saved at that
time.
Because of several requests from customers who were using this functionality it is decided to re-install the functionality.
To do this Baan first defined the concept and implemented the functionality according to that functionality.
Part of the concept was the introduction of the name Hold Back Quantity.
Hold Back Quantity is the quantity of the total order quantity that you do not want to release to warehousing. This quantity
can be entered during order entry.
The main functionality is as follows :
The introduction of the Hold Back Quantity makes it possible to keep (a part of the) ordered quantity from being released to
warehousing. The delivered quantity is subtracted from the ordered quantity after the shipment is confirmed to determine the
back order quantity. By doing this the Hold Back quantity is replaced by the actual backorder quantity.
The Hold Back quantity must be available for both the line and the detail.
The Hold Back quantity must be available in case a backorder has been confirmed.
Several help texts are added to related fields (Hold Back Quantity, Back Order Quantity and Not Yet Confirmed quantity)
The functionality is available for the following situations :
The "Hold Back Quantity" functionality will only be available for:
· Items without commitment policy
· Order (lines) with no shipping constraints
· Non Cost Items
· Non Service Items
· Non List Items
· Non Subcontract Items
· Non Equipment Items
· Non Collect Orders
· Non Return Order Lines
· Non Total Order Lines
· Order line quantity <> 0

Solution: 126044
SITUATION IDENTIFIED IN:
"Purchase Corrections" (tfacp2110m000)
SITUATION DESCRIPTION:
Incase purchase corrections are done, after the calculation of currency difference for the Open entry, the following
situations were observed.
1. Even Incase of currency loss, the currency difference is booked to unrealized currency profit ledger account .
2. The dimensions were not picked up correctly for the control account posting for this currency difference.
3. When paying the invoice, where a purchase correction has been done after a Calculate currency difference, the reversal of
ther unrelaized currency profit/loss ledger account, and the booking of Realized currency profit/ loss ledger account is
done for a wrong amount ( twice the amount which needs to be booked )
SOLUTION DESCRIPTION:
All the above situations have been corrected with this solution.

Solution: 126050
SITUATION IDENTIFIED IN:
"Purchase Order Header" (tdpur4100s000)
SITUATION DESCRIPTION:
1. The Purchase Order Type has an Input Control defined in session "Purchase Order Input Controls" (tdpur0195m000).
2. The 'Text' and 'Save' buttons are not enabled during the 'Second Pass of Header'
SOLUTION DESCRIPTION:
The 'Text' and 'Save' buttons are enabled now during the Second Pass of Header.

Solution: 126051
SITUATION IDENTIFIED IN:
"Maintain Engineering Bill of Material" (tiedm1110s000)
SITUATION DESCRIPTION:
System is not allowing to enter Negative quantites in the field "Number of Units" and "Net Quantity" in the Engineering
BOM
SOLUTION DESCRIPTION:
The system allows to enter negative values.

Solution: 126052
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Inventory commitments based on order line entry is not working for a very specific situation involving contracts.
Situation is if a contract is set up based on a cost item specifying "apply to all items in price group" and then a purchased
item in a sales order which belongs to the same price group as the mentioned cost item is entered, the contract links but
inventory is not committed.
SOLUTION DESCRIPTION:
During this process data needed for the commitment was not available. The missing data is read and now commitment will
take place

Solution: 126054
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
Consignment Replenishment Orders was not getting linked to an active Contract. Hence it is not possible to update the
invoiced quantity for the contract though consignment goods have been used.
SOLUTION DESCRIPTION:
Consignment Replenishment Orders will get linked to Contract if one is active. However the Called Quantity and Called
Amount will not be updated to the Contract. After the Consignment Inventory is used Consignment payment Order is
generated. On processing this Payment Order, the Invoiced quantity and the Invoiced amount will be updated in the
Contract.

Solution: 126055
SITUATION IDENTIFIED IN:
"Fill dimensions in Interim table" (tfcor1241m000)
SITUATION DESCRIPTION:
By default the dimensions are not filled into the interim table
SOLUTION DESCRIPTION:
By default the dimensions are not filled into the interim table. There was however an request that the dimensions are filled.
The reports which are delivered for the GRNI solution do not use the dimensions but it is possible now to use a reporting tool
(like Crystal Reports) to print the financial details sorted on dimension.

Solution: 126060
SITUATION IDENTIFIED IN:
"Location Capacity Data" (whwmd3101s000)
SITUATION DESCRIPTION:
The 'Expected Decrease' field in "Location Capacity Data" (whwmd3101s000) does not increase when the outbound advice is
created with the 'Advise unit' being so small when compared to the 'Capacity unit' of the location.
SOLUTION DESCRIPTION:
Now the 'Expected Decrease' field in "Location Capacity Data" (whwmd3101s000) is increasing correctly when the
outbound advice is generated.

Solution: 126061
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
Wrong translation for the option of Linked Orderline Data in the German language.
SOLUTION DESCRIPTION:
Corresponding correct word is now present in the German language for Linked Orderline Data.

Solution: 126063
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
"Call Processing" (tsclm1118s000)
"Solve Calls" (tsclm1120s000)
SITUATION DESCRIPTION:
When working on a Call simultaneously with two or more users it is possible that one user changes the call status (for example
to "Solved") and an other changes it back (for example to "In Process") overwriting the first change. It is also possible to
transfer the call to a Service Order, or invoice the call in such a situation.
SOLUTION DESCRIPTION:
Before starting any of the possible commands on a Call or during processing a Call, a check is made on the current status.
When another user has changed the status of the Call to a status which should block further actions, (for example to "Solved"
when the first user is still processing the Call) then the message "Status has been changed by other user" is given and the
session will show the new values.

Solution: 126064
SITUATION IDENTIFIED IN:
"Build Actual Cost Control" (tpppc4803m000)
SITUATION DESCRIPTION:
Surcharge on Forecast Amount is not calculated correctly. It always shows as Zero
SOLUTION DESCRIPTION:
Now the above mentioned problem is solved. Surcharge on Forecast Amount is calculated correctly now.

Solution: 126068
SITUATION IDENTIFIED IN:
"Purge Device Queue" (ttaad3221m000)
SITUATION DESCRIPTION:
If you delete a big amount os data in this session then error ORA-1555 can occur.
SOLUTION DESCRIPTION:
AS PREPARED SET added to the sql statement. This does no longer bring up the error.

Solution: 126084
SITUATION IDENTIFIED IN:
"Price Calculator" (tdpcg0200m100)
SITUATION DESCRIPTION:
The 'Net Price' fields in the session "Price Calculator" (tdpcg0200m100) are displayed differently. One field value was
rounded but the other not rounded.
SOLUTION DESCRIPTION:
Now both the 'Net Price' field values in the session "Price Calculator" (tdpcg0200m100) are same.

Solution: 126087
SITUATION IDENTIFIED IN:
"Password Aging" (ttdllpwdaging)
SITUATION DESCRIPTION:
In case of a wrong entered password the following session error instead of an error message was coming up:
"Ask enum 'ttstppwdaging0' not found "
SOLUTION DESCRIPTION:
The message code had an error in the typing. The zero at the end had to be removed. This was done to fix the problem.

Solution: 126091
SITUATION IDENTIFIED IN:
"Activate Job" (ttaad5203m000)
SITUATION DESCRIPTION:
1) The messages are connected to the wrong jobstep if the sequence number is not equal to the session number.
2) If you are running a job that has several session connected to the job and you configure the job in the way that a session
is skipped then the session number does not reflect any longer the job definition.
3) If a job step creates a message then in the job session history (ttaad5511m000) you see the session number
(ttaad501.seri). In the session job history messages (ttaad5512m000) you see the step sequence (ttaad501.sequ). So it is hard
to get a direct connection between both session and the data.
SOLUTION DESCRIPTION:
While the job is running the tables ttaad511 and ttaad512 are filled with different kez values. The problem is the value sequ.
This field is filled in table ttaad511 with the value of field ttaad501.seri and in table ttaad512 with field ttaad501.sequ. So
the connection between these two tables cannot be made after the job was running.
This is corrected in the way that ttaad5203m000 is now using the field ttaad501.sequ for both tables.

Solution: 126096
SITUATION IDENTIFIED IN:
"Inventory Receipt Transactions" (whina1512m000)
SITUATION DESCRIPTION:
After installing the GRINI solutions; 124194, 124651, 125752, 125980 it could happen in some specific situations that the
receipt amount which is triggered upon confirming receipt does get corrupted. Due this error the receipt amount was
calculated as 'delivered qty. * ordernumber'.
To prevent corruption it is very important that in case one of above mentioned solutions is installed this solution will be
installed as well to prevent the data corruption.
SOLUTION DESCRIPTION:
This problem has been corrected and now the receipt amount is correctly calculated again.

Solution: 126099
SITUATION IDENTIFIED IN:
"Select Invoices for Reminder" (tfacr3210m000)
SITUATION DESCRIPTION:
Already paid invoices are selected for a range of Business Partners. It was wrong when the selection is based on the credit
analyst.
SOLUTION DESCRIPTION:
Paid Invoices are not selected for reminder.

Solution: 126101
SITUATION IDENTIFIED IN:
"Import / Export Statistics" (tccom7171s000)
SITUATION DESCRIPTION:
There could be an inconsistency between the Total Net amount from the sales order lines defined in the Sales Order Line
(session tdsls4101s000) and the goods value amount registered in the Import/Export Statistics (session tccom7171s000) for
EU reporting.
Example:A Sales Order Line is created for an Item with 2 levels of discounts:
- Level 1: 15% on the gross amount
- Level 2: 50% on the net amount
- Total Discount of 57.5% on the sales order lines (1-0.50*0.85).
- Import/Export Statistics shows an incorrect Goods Value Amount is wrong.
The system adds the 2 levels of discounts are added, which gives in total a discount of 65%.
SOLUTION DESCRIPTION:
The goods amount is now properly calculated.

Solution: 126110
SITUATION IDENTIFIED IN:
"Print Program Scripts / Libraries" (ttadv2431m000)
SITUATION DESCRIPTION:
When running the session Print Program Scripts / Libraries (ttadv2431m000) the error message: " index 529 out of dims [0]
528" appears, when in a program script a line contains more then 528 characters or tabs.
SOLUTION DESCRIPTION:
The problem has been solved in the DLL (dllstring) now the session Print Program Scripts / Libraries (ttadv2431m000) runs
properly.

Solution: 126117
SITUATION IDENTIFIED IN:
"Print Bills of Material (Multi-level)" (tibom1411m000)
SITUATION DESCRIPTION:
While printing Bills of Material (Multi-level), if the component item is having only routing not a BOM component under it,
system is printing the wrong description for routing Item.
SOLUTION DESCRIPTION:
Even though the component item is not having the BOM component under it, system will print the correct description for
routing Item.

Solution: 126118
SITUATION IDENTIFIED IN:
"Production Schedules" (tirpt1500m000)
SITUATION DESCRIPTION:
While searching for an item in Production Schedules session, system displays a Fatal error, aborts from the session and the
connection is lost with the server. This problem occurs only in a Multi-Byte environment.
SOLUTION DESCRIPTION:
While searching for an item in Production Schedules session in a Multi-Byte environment, system successfully searches the
item.

Solution: 126121
SITUATION IDENTIFIED IN:
"Finalize Engineering Data" (tiedm3240m000)
SITUATION DESCRIPTION:
Wrong Engineering Item / Item Relationship is created while finalizing the Engineering Item Data
SOLUTION DESCRIPTION:
The system checks the item data whether the item exists and then creates the relationship.

Solution: 126122
SITUATION IDENTIFIED IN:
"Print Invoice To Business Partner Aging Summary" (tfacr2411m000)
SITUATION DESCRIPTION:
Cannot have more than 3 reports. The new report (copy from standard) does not print any data The Error Message : "No Data In Selection " is displayed.
SOLUTION DESCRIPTION:
A new report can be added. And report is printed.

Solution: 126127
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
The session "Convert Electronic Bank Statements" (tfcmg5202m000) is used to convert and store EBS files inside the Baan
database. Each EBS file consists of one or more postings. A posting consists of one or more lines. In particular cases it is
possible that when a posting has more than one line, not all the data is included in one posting. A part is then stored in the
next posting.
Each line read from the EBS file must be identified before being processed. The identification is done with the "Record types", entered in session
"Maintain Record Types for Electronic Bank Statements" (tfcmg5104m000). Each "Record type" has a unique value by which a line can be identified. If
an EBS line cannot be identified, that line must be ignored. However, sometimes an unidentified line is inserted in the database.
SOLUTION DESCRIPTION:
The conversion process of reading an EBS file is modified. Therefore, the following guidelines now apply to an EBS file:
- Every EBS import line must have a "Record Type" so that is can be identified. If not, the line is ignored.

- Every posting in the EBS file must start with the same "Record Type".

Solution: 126128
SITUATION IDENTIFIED IN:
"Print Received Purchase Invoices" (tfacp1400m000)
SITUATION DESCRIPTION:
The session "Print Received Purchase Invoices" (tfacp1400m000) is running slow.
SOLUTION DESCRIPTION:
Performance of this session has been improved.

Solution: 126132
SITUATION IDENTIFIED IN:
"Print BaanProject Financial Reconciliation" (tcfin2400m000)
SITUATION DESCRIPTION:
When printing the BaanProject Financial Reconciliation, in case of a negative debit amount stored in the tables, this was
printed as a positive amount. This was incorrect.
SOLUTION DESCRIPTION:
The amounts are printed as stored in the tables. So printing the BaanProject Financial Reconciliation will print the correct
positive and negative values and they will be correctly aggregated to the respective totals on the report.

Solution: 126134
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
When inserting an outbound advice (session whinh2125s000), at the moment of filling a Storage Unit the message "Stock
point unknown" comes up.
SOLUTION DESCRIPTION:
The error was caused by a mismatch between dates, now the correct inventory date is selected, and it is also possible to
modify it manually in the session.

Solution: 126138
SITUATION IDENTIFIED IN:
"Audit Posting Data for Electronic Bank Statements" (tfcmg5203m000)
SITUATION DESCRIPTION:
All the subsequences of one statement are printed in the report after auditing the posting data for electronic bank statements.
SOLUTION DESCRIPTION:
Earlier, all the subsequences of one statement are printed in the report after auditing the posting data for electronic bank statements.
Now, only the first subsequence of the statement is printed instead of all the subsequences of one statement.

Solution: 126139
SITUATION IDENTIFIED IN:
"Print Currency Analysis" (tfacr2422m000)
SITUATION DESCRIPTION:
The amount under column OPEN ITEMS in invoice currency is wrongly printed for an invoice, which is fully reconciled.
This happens when the Invoice has Receipt Method attached to it with steps 2.
SOLUTION DESCRIPTION:
Now the report gives the right picture & it doesn't show any open balance for the invoice which is completely reconciled.

Solution: 126142
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
1. The Report of the session "Print Packing Slips" (whinh4475m000) is copied to a new report.
2. The session "Print Packing Slips" (whinh4475m000) is copied to a new session "Print Packing Slips" (whinh4475meds).
3. The above copied report is linked to the session "Print Packing Slips" (whinh4475meds).
4. When the session "Print Packing Slips" (whinh4475meds) is run, the report selection box is coming twice.
SOLUTION DESCRIPTION:
The 'Report Selection Box' would appear only once now.

Solution: 126146
SITUATION IDENTIFIED IN:
"Contract Installments" (tsctm4500m000)
SITUATION DESCRIPTION:
It is not possible to enter negative costs on a credit note installment.
SOLUTION DESCRIPTION:
For contract installments of type 'Credit' it is possible to enter a forecast percentage and a forecast cost amount, which can
lead to negative costs. Which is consistent with installments of type 'Invoice'.

Solution: 126149
SITUATION IDENTIFIED IN:
"Generate Outbound Advice " (whinh4201m000)
SITUATION DESCRIPTION:
1. There are 2 stock points present in the warehouse with 20 pcs and 83 pcs. The stock point has a package definition.
2. An outbound order line is created for 100 pcs.
3. When the 'Outbound Advice' is generated for the order, the system advises for 103 pcs where as the ordered quantity is
100 pcs and the following error message comes up.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++
Advised Quantity in Inventory Unit cannot be greater than Ordered Quantity in Inventory Unit + Rejected Quantity in
Inventory Unit
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++
SOLUTION DESCRIPTION:
Now the advised quantity will not be greater than the order quantity for the stock points having package definition.

Solution: 126153
SITUATION IDENTIFIED IN:
"Display Device Queue" (ttaad3520m000)
SITUATION DESCRIPTION:
If a normal user runs the session Display Device Queue (ttaad3520m000) and clicks the button "Disp.Request" (for a print
job of an other user) the message "You are only authorized to cancel your own print requests" (ttaad30021) pops up. This
message should be corrected to the situation at hand.
SOLUTION DESCRIPTION:
A new message has been created: "You are not authorized to display information of another user" (for Baan IV = ttaad30023 for BaanERP = ttaad30024)

Solution: 126156
SITUATION IDENTIFIED IN:
"Conditions" (tuxch0114m000)
SITUATION DESCRIPTION:
In session "Conditions" (tuxch0114m000), it is possible to copy a condition.
The parameters of the "source" condition however are not copied to the "new" condition.
SOLUTION DESCRIPTION:
When a condition is copied, all parameters of the "source" condition are now copied as well to the "new' condition.

Solution: 126160
SITUATION IDENTIFIED IN:
"Audit payments" (tfcmg1255m000)
SITUATION DESCRIPTION:
Solution 126338 has not been delivered for the Standard component in (B50 b).
SOLUTION DESCRIPTION:
Solution 126338 for the Standard component in (B50 b) has been delivered with this solution and with new idents.
Solution: 126167
SITUATION IDENTIFIED IN:
"Process Quotations" (tdsls1200m000)
SITUATION DESCRIPTION:
The inventory check was not properly executed when processing a quotation line.
This only applied to items for which an ATP (Available to Promise) did not need to be executed.
SOLUTION DESCRIPTION:
The inventory check is now properly executed.

Solution: 126168
SITUATION IDENTIFIED IN:
"Print Sales Order Acknowledgement" (tdsls4401m000)
SITUATION DESCRIPTION:
- If a Sales Order acknowledgement is printed for a sales order line having a specific delivery address and a text linked to the sales order line the specific delivery address is printed twice on the Acknowledgement.
- Another issue is that if you reprint the Sales Order Acknowledgement the device specified in the next step of the order type is picked up instead of the device specified for the step Print Order Acknowledgement.
SOLUTION DESCRIPTION:
- Now the specific delivery address will be printed correctly.
- The device will now be picked up from the order step Print Order Acknowledgement even if the current status of the order line is different. So, reprinting the Order Acknowledgement will now print to the same device as the original print.

Solution: 126169
SITUATION IDENTIFIED IN:
"Activity Budget (Material Lines)" (tpptc2110s000)
SITUATION DESCRIPTION:
Opening the first item in the session "Activity Budget (Material Lines)" (tpptc2510m000) (i.e. starting session
tpptc1110s000) took 2 minutes in some cases, depending on the number of records in tppdm005.
SOLUTION DESCRIPTION:
Opening the first item in session "Activity Budget (Material Lines)" (tpptc2510m000) is now done much faster. Reading of (referenced table) tppdm005 (Project Items) is included in the query.

Solution: 126173
SITUATION IDENTIFIED IN:
"Print Production-Order Documents" (tisfc0408m000)
SITUATION DESCRIPTION:
If we change (reduce) the Maximum Order Quantity on a Manufactured Item's Ordering Data, system is not allowing changing the Production Order status from Planned to Documents Printed even after the document is printed. The Production Order created before the modification of the MOQ and having an Ordered Quantity greater than the new MOQ.
SOLUTION DESCRIPTION:
Check on order quantity should be done only for orders, which has the status less than Documents Printed. While printing the documents also system should change the Production Order Status to Documents Printed.

Solution: 126174
SITUATION IDENTIFIED IN:
"Estimated Materials" (tisfc0110s000)
SITUATION DESCRIPTION:
System allows to enter an item without cost price structure in "Estimated Materials" for a production order with status released.
SOLUTION DESCRIPTION:
System does not allow to enter an item without cost price structure in "Estimated Materials" for a production order with status released.

Solution: 126206
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2121s000)
SITUATION DESCRIPTION:
It is possible to change the cost component on an actual material cost line. However, when for this actual line an estimation exists, the cost component can not be changed. This happens in both the products iBaan Service B50b and iBaan Service B50c.
The reason why it is not possible to change the cost component field when estimated quantity is present, is that estimation
data can be stored in history in this way.
In product iBaan Service B50b, also the following situation was found:
When changing the cost component on a service order actual material cost line, the material cost component amount is reversed but the operation cost component amount is not reversed.
SOLUTION DESCRIPTION:
It is possible to change the cost component can be changed on an actual material cost line for which an estimation exists.
The reason for allowing the cost component to be changed, is following:
Information about the cost component is not important on an estimation, but will be for an actual. By changing the cost
component one can change the coverage on this cost line if needed.
To have estimation data in history is meant to compare the estimates with the actuals. But for cost components one can not do
this because then 2 fields are necessary in history (one for estimates and one for actuals). In the current situation,
estimates and actuals have the same cost component.
In product iBaan Service B50b:
When changing the cost component on an service order actual material cost line, the material cost component amount as
well as the operation cost component amount will be reversed.

Solution: 126207
SITUATION IDENTIFIED IN:
"Planned Activities" (tsspc2500m000)
SITUATION DESCRIPTION:
When a Service Order, which is originated from a Planned Activity, is posted to history and deleted from the Actual
Service Orders with session 'Close Service Orders and Post to History' (tssoc2201m000), the Planned Activity is still
displayed in session Planned Activities (tsspc2100s000). On tab "Execution" the related Service Order and Activity line
is displayed but with activity description"***********************************". Furthermore this planned activity
can't be deleted anymore.
SOLUTION DESCRIPTION:
- After deleting a Service Order from the Actual Service Orders with session 'Close
Service Orders and Post to History' (tssoc2201m000), the related Planned Activity can be deleted with session Planned
Activities (tsspc2500m000) or with session 'Delete Maintenance Planning' (tsspc2202m000).
- In session Planned Activity (tsspc2100s000), the Service Order Activity
description on tab 'Execution' will display the real Service Order Activity description, either from the Actual Service Order
Activity or from the History Service Order Activity.
- The Planned Activity will not automatically be
deleted when the related Service Order is deleted to keep the Maintenance Planning as long as needed or wished.

Solution: 126208
SITUATION IDENTIFIED IN:
"Hours Accounting by Production Order" (tihra1503s000)
SITUATION DESCRIPTION:
In the sub session of Hours Accounting by Production Order, the employee code is getting truncated after fifth position, where
as it is fully displayed in the main session.
SOLUTION DESCRIPTION:
Employee code is not truncated anymore.

Solution: 126213
SITUATION IDENTIFIED IN:
"Execute Query" (ttadv3280m000)
SITUATION DESCRIPTION:
When accessing session 'Execute Query' through DEM, when the user has a specific query entered in his DEM setup, the user should not be able to access other queries.
SOLUTION DESCRIPTION:
Now, when a specific query is entered in the user's DEM configuration, when the session 'Execute Query' is started, the session runs the specific query and exits. If there is no specific query entered in the user's DEM setup, the system allows the user to find the query he wants to execute.

Solution: 126219
SITUATION IDENTIFIED IN:
"Update Actual Calender" (tcccp0230m000)
SITUATION DESCRIPTION:
When updating the Actual Calender with the option Process Child Calendar checked for a calendar with more than 100 children a fatal error message occurs.
SOLUTION DESCRIPTION:
There is no restriction in the number of children calendars anymore.

Solution: 126222
SITUATION IDENTIFIED IN:
"Import Data Non-Regular" (tuxch0223m000)
SITUATION DESCRIPTION:
If in the path for error logging in the exchange scheme data was specified # and import/export was done for another company, logfile was created for the current company while it should be done for company into which import is done [or from which export is done].
SOLUTION DESCRIPTION:
Few libraries were modified to take care that logfile path is properly expanded.

Solution: 126225
SITUATION IDENTIFIED IN:
"Print Control Account checklist" (tfacr2415m000)
SITUATION DESCRIPTION:
In "Print Control Account Checklist" and select " Print differences" only, Business Partners with no differences are printed.
SOLUTION DESCRIPTION:
In "Print Control Account Checklist" and select "Print differences" only, It prints " Total for Business Partner Group" and
"Total for Ledger Account " for the Business Partners with some differences.
Solution: 126226
SITUATION IDENTIFIED IN:
"Process EBOM changes" (tiedm3205m000)
SITUATION DESCRIPTION:
Float Exception Error occurs while processing the Engineering Bill of Materials
SOLUTION DESCRIPTION:
The system will not allow the user to enter the net quantity as zero when the replace type is division.

Solution: 126227
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Signal "Negative inventory on hand (on shop floor)" is generated when Inventory on hand is > 0
SOLUTION DESCRIPTION:
Signal "Negative inventory on hand (on shop floor)" is generated when:
- at the start of order planning the inventory on hand is less than zero or
- the inventory at the execution level falls below zero while traversing through the inventory movements within the order time fence
(The inventory at the execution level does not include the receipts or requirements of forecasts, planned orders and critical material requirements )
- the signal "Actual Demand Late" is not generated. The signal will be generated only for the first occurrence

Solution: 126228
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
1. Select all the lines for a Picking list sorted by 'Advised Quantity in Inventory Unit' in the session "Picking List"
(whinh2525m100)
2. When selecting the option of 'Confirm Advice Lines', Fatal Error 206 was popping up.
SOLUTION DESCRIPTION:
Actually Shipments lines were not getting confirmed because of some insufficient data , In such case system should pop up
an error message , but it was giving a Fatal error . Now the Fatal error will not come up and error message comes up when
the user tries to confirm shipment lines.

Solution: 126230
SITUATION IDENTIFIED IN:
"Machine Utilization by Day overview" (tisfc1505m000)
SITUATION DESCRIPTION:
In the session "Machine Utilization by Day overview", if there are several Production orders for different items then the first
routing description is displayed for all the lines.
SOLUTION DESCRIPTION:
Correct descriptions of the routings are displayed for all the lines.

Solution: 126231
SITUATION IDENTIFIED IN:
"Maintain Extensions" (tpptc0110s000)
SITUATION DESCRIPTION:
If for an Extension, some "To be Invoiced" lines are present , & for some reason we have to change the extension status back to "Free", all the "To be Invoiced" lines also have to be set to free. In this way the user will understand that the extension is currently not in use. But, that is not currently happening.
SOLUTION DESCRIPTION:
Now if the extension status is changed from "Invoicing Allowed" to any other status then a question will be asked to the user if he wants to set the "To be Invoiced"
lines to "No".Only if the user says "Yes", then the Extension status will be changed.Otherwise there will not be any change in the status.

Solution: 126240
SITUATION IDENTIFIED IN:
"Print Cheque Report" (tfcmg1271m000)
SITUATION DESCRIPTION:
In the Check Report, two labels are put immediately behind each other. There is no space between the labels.
SOLUTION DESCRIPTION:
Space is been provided in between the two labels in the Check Report.

Solution: 126242
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2120s000)
SITUATION DESCRIPTION:
1. There is a Transfer(Manual) order with the Ship to Location filled in "Warehouse Orders" (whinh2100s000).
2. In the "Outbound Order Lines" (whinh2120s000) a Non-location controlled item is entered.
3. After processing the outbound, it is observed that the stock point of the Non-location controlled item is moved to the
Ship to Location given in the in "Warehouse Orders" (whinh2100s000).
4. Hence this stock point is corrupted and can not be used again.
SOLUTION DESCRIPTION:
When the 'Ship from' or 'Ship to' location is filled in Warehouse Orders" (whinh2100s000), a Non-location controlled item
can not be entered in the outbound order lines.

Solution: 126244
SITUATION IDENTIFIED IN:
"Approvals" (whinh3522m000)
SITUATION DESCRIPTION:
In the approvals session , when rejecting an item, Inbound Advice is automatically generated if the approved and rejected quantities are equal.
SOLUTION DESCRIPTION:
Now the inbound is not generated automatically after approvals are done even if the approved and rejected quantities are same.

Solution: 126246
SITUATION IDENTIFIED IN:
"Inventory Handling Parameters" (whinh0100s000)
" Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
Help texts aren't adapted to the new situation of over deliveries being enabled (Solution 124852)
The help text for field "Over Delivery" in the Inventory Handling Parameters (whinh0100s000) session was missing.
The help text for field "Maximum Quantity" in the Warehousing Orders (whinh2500m000) session wasn't adapted to the new
situation.
SOLUTION DESCRIPTION:
Help texts are adapted to the new situation.

Solution: 126248
SITUATION IDENTIFIED IN:
"Transactions Purchase Invoices" (tfacp1120s000)
SITUATION DESCRIPTION:
The tax amount was not filled although the ledger a/c has a default tax code.
SOLUTION DESCRIPTION:
Now the tax amount is filled when the ledger a/c has a default tax code

Solution: 126263
SITUATION IDENTIFIED IN:
"Print Business Partner wise Aging Analysis" (tfacr2411m000)
SITUATION DESCRIPTION:
Error ACR1 - Index 100000 out of dims [1] 99999 appears when the report is printed for more than 99999 business partners
SOLUTION DESCRIPTION:
Now the report can be taken for more than 99999 Business partners

Solution: 126264
SITUATION IDENTIFIED IN:
"Release to Warehousing" (tdpur4246m000)
SITUATION DESCRIPTION:
1. There is a Purchase Order generated for a cross docking Sales Order.
2. The purchase order is Released to Warehousing from the session "Release to Warehousing" (tdpur4246m000) and the
Inbound Order Line is created.
3. Now the 'Split Delivery Lines' check box is selected in the "Purchase Order Lines" (tdpur4101s000) and the detail lines
are entered.
4. Now the order is Released to Warehousing again.
5. There is an inbound order line corresponding to the 'Total' line. There should be lines only for the detail lines.
SOLUTION DESCRIPTION:
At the time the when the 'Detail' line is split and made as Total line, the Inbound Order Line created earlier would be
deleted. When the 'Release to Warehousing' (tdpur4246m000) is run for the next time, the new Detail lines are released and
inbound lines are created for them.

Solution: 126265
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Headers" (cisli2520m000)
SITUATION DESCRIPTION:
When Manual sales orders are processed through "Direct processing" for more than 3 times without closing the header window
then the Invoice report is not printed.
SOLUTION DESCRIPTION:
Now the Invoice report is picked up correctly when Manual sales invoice are processed using "Direct Processing".

Solution: 126269
SITUATION IDENTIFIED IN:
"Copy Engineering Items to Items" (tiedm1202m000)
SITUATION DESCRIPTION:
System should ask to copy E-Item description to P-Item while copying E-items to existing P-Items.
SOLUTION DESCRIPTION:
Form field Copy E-Item Description (Check Box) is created in the form tiedm1201m000 (Copy engineering Items to Items). If
this Check Box is selected then only System will copy the E-Item Description, Search Key I and Search Key II to Item. If
This check Box is not selected, then the old Description, Search Key I and Search Key II of the Item is Retained

Solution: 126271
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Orders" (whinh5500m000)
SITUATION DESCRIPTION:
Unable to process cycle count order if 2 items, 1 with zero stock, at same not multi-item location.
SOLUTION DESCRIPTION:
If counted stock equals zero there is no location check executed.

Solution: 126282
SITUATION IDENTIFIED IN:
"Update Signals by Item" (cprao1210m000)
"Signals by Item/Planner" (cprao1125m000)
SITUATION DESCRIPTION:
When Update Signals by Item is executed with the checkboxes " Delete Signals" , " Delete Signals from Simulations " and " Delete Accepted Signals " checked, all Signals are deleted. No Signals are regenerated. When using the "update" function (Special menu - Update or Ctrl-F1) signals are deleted and not newly generated.
SOLUTION DESCRIPTION:
When Update Signals by Item is executed with the checkboxes " Delete Signals" , " Delete Signals from Simulations " and " Delete Accepted Signals " checked, all Signals are deleted. New Signals are generated. When using the "update" function (Special menu - Update or Ctrl-F1) signals are updated.

Solution: 126284
SITUATION IDENTIFIED IN:
"Assign unallocated / advance payments to invoices" (tfcmg2106m000)
SITUATION DESCRIPTION:
When you process the advance payment without any anticipated steps in the payment method, it is not possible to assign that
anticipated document to the invoice.
SOLUTION DESCRIPTION:
It is possible to assign the advance payment document to the Invoice.

Solution: 126291
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Details" (cisli2525m000)
SITUATION DESCRIPTION:
Invoice has a Business partner different from the one entered in the Manual sales invoice
SOLUTION DESCRIPTION:
Now the Invoice is printed with the Business partner entered in the Manual sales invoice

Solution: 126295
SITUATION IDENTIFIED IN:
"Purchase Order Line Details" (tdpur4501m200)
SITUATION DESCRIPTION:
1. The 'Lot Selection' is Specific and a lot code is filled in the "Purchase Order Lines" (tdpur4101s000).
2. This line is made as a total line and there are 3 Detail lines created for this Total line.
3. The 'Specific' lot is filled only in the first detail line and for the rest of the detail lines the Specific lot is not carried from
the Total line.
SOLUTION DESCRIPTION:
Now all the "Detail' lines would have the same Specific lot as that of the Total line.

Solution: 126296
SITUATION IDENTIFIED IN:
"Sales Budgets" (tdsst0550m000)
SITUATION DESCRIPTION:
Delete button was not working correctly. If a record is selected in the sales budget and deleted, then only one record is
deleted in the Actual sales budget session for the corresponding record.
SOLUTION DESCRIPTION:
Now the new user option is added to delete the selected record. If the user accepts to delete the record, then the
corresponding record in the actual sales budget session also gets deleted.

Solution: 126297
SITUATION IDENTIFIED IN:
"Export Language-Dependent Software Components" (ttadv6230m000)
SITUATION DESCRIPTION:
Session "Export Language-Dependent Software Components" exports the INFO message for comment lines.
For example: |# This is a comment line. SF@ttmanpagesmessage.
This will create the line : "#INFO SFttmanpagesmessage = message" in the export file.
This is not correct, these comment lines should be present in the export file.
SOLUTION DESCRIPTION:
An extra check is done during the export of hypertext lines.
If a comment line is found, this line is now skipped. It is no longer present in the export file.

Solution: 126298
SITUATION IDENTIFIED IN:
"Linked Orderline data" (tdpur4502s000)
SITUATION DESCRIPTION:
When the group buttons are used to find the next/previous records, then the record was not properly displayed in the
session.
SOLUTION DESCRIPTION:
It is now possible to find the required record even when the index keys are changed.

Solution: 126301
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
There is a main item which is lot controlled.
The main item has components and few of the components are lot controlled and few are not.
A purchase order is created with 'Post to Components' and while confirming the receipt the lot code entered for the main item
is allocated to the Non-lot controlled items also.
SOLUTION DESCRIPTION:
For the components that are not lot controlled, there would be no lot code assigned to the stock point now.

Solution: 126311
SITUATION IDENTIFIED IN:
"verify Labels" (ttadv8940m000)
SITUATION DESCRIPTION:
Following Tools labels are missing:
Confirmation (ttadv316.conf)
Confirmation Answer to continue (ttadv316.conf)
Default Label (ttadv316.deflabl)
Execution type (ttadv316.exec)
For multiple selection, execute (ttadv316.exec)
Question (ttadv316.ques)
Start mode Session (ttadv316.sesm)
Print form changes (ttpmc.formch)
SOLUTION DESCRIPTION:
The missing labels have been created.

Solution: 126326
SITUATION IDENTIFIED IN:
"Correction of inbound/outbound lines for production orders" (whcor0213m000)
SITUATION DESCRIPTION:
There are still open inbound/outbound lines for end items and materials of Production Orders which have the status
"Closed", "Completed", "to be Cancelled".
SOLUTION DESCRIPTION:
New program was created for correcting the inconsistent inbound/outbound lines for production orders.
Solution: 126329
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000 and tfacr2520m000)
SITUATION DESCRIPTION:
Fully paid invoices appear in the Open Entries.
SOLUTION DESCRIPTION:
Now the fully paid invoices didn't appear in Open Entries.

Solution: 126334
SITUATION IDENTIFIED IN:
"Select Invoices for reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
Invoices are not selected if a business partner has the "Invoice To" role in "Invoice-to Business Partners" and in "Pay -By
Business Partner" if there is a different "Pay by BP"
SOLUTION DESCRIPTION:
Invoices are selected if a business partner has the "Invoice To" role in "Invoice-to Business Partners" and in "Pay -By
Business Partner" if there is a different "Pay by BP"

Solution: 126335
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
It is possible to assign a service order to a service engineer who is no longer employed in the company.
SOLUTION DESCRIPTION:
It is not possible to assign a service employee who is no longer employed. When entering a service engineer to a service
order,the employee's first and last dates of employment are checked with the date of entry. When releasing an order, the
planned start time and planned finish time are used to check whether the employee is still employed. The planned start and
finish times are also used when scheduling the employee using Baan Service Scheduler.

Solution: 126347
SITUATION IDENTIFIED IN:
"Enter Payment Amounts for Assignment" (tfcmg2119s000)
SITUATION DESCRIPTION:
The remaining and balance amounts were displayed incorrectly when you assign the payment amount to the Invoice and this
is happening only when the payment amount is less than the invoice amount.
SOLUTION DESCRIPTION:
The remaining and balance amounts are displayed correctly.

Solution: 126348
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
Zero Invoices are printed even when the option "Suppress Zero Amounts" is opted in billing request addition.
SOLUTION DESCRIPTION:
Now Zero invoices are not printed in case the "Suppress Zero Amounts" is opted for.

Solution: 126350
SITUATION IDENTIFIED IN:
"Handling of fields containing a constant" (Library tudllconstfld)
SITUATION DESCRIPTION:
In session Field Relations (Import) (i.e. tuxch0122s000), it is not possible to select a multibyte string in the Constant field.
The following error message is displayed in japanese, tuxchs0015: Constant value is invalid.
SOLUTION DESCRIPTION:
Multibyte language take up more space for their characters. Some variables in library tudllconstfld were not large enough to hold the multibyte description.
Now the variables can hold the multibyte description.

Solution: 126352
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2400m000)
SITUATION DESCRIPTION:
No Item Customer Information text when printing invoices in "Print Invoices" (cisli2400m000).
SOLUTION DESCRIPTION:
Item Customer Information text is defined in "Item Customer Information" (tdisa0510m000).
This text should be displayed / printed when printing Invoices in "Print Invoices" (cisli2400m000).
The same information does appear when printing Order Acknowledgements and Packing Slips.

Solution: 126358
SITUATION IDENTIFIED IN:
"Confirm Shipments" (whinh4275m000)
SITUATION DESCRIPTION:
The user is not able to Confirm shipments in the case of Bilateral Invoicing. Error message is displayed that it is impossible
to change the Sales Representative
SOLUTION DESCRIPTION:
Now the user is able to confirm shipments.

Solution: 126361
SITUATION IDENTIFIED IN:
"Manual Invoice Headers" (cisli2120s000)
SITUATION DESCRIPTION:
Even when the user enters a BP not present in the Invoice-to BP table, the system does not give any error message. But when
composing the invoice, the system does not process the line.
SOLUTION DESCRIPTION:
Now an error message is displayed and the user has to enter the correct Invoice-to role for sure.

Solution: 126369
SITUATION IDENTIFIED IN:
"Search Label" (ttdllfindlabel)
SITUATION DESCRIPTION:
This problem occurred in a Japanese environment. When opening the first form of session "Cost Price by Project"
(tipcs3560m000) for the second time, in a multi-byte environment the BW-message "Grid selection out of range" is
displayed.
SOLUTION DESCRIPTION:
The problem was caused by a label on the first form of session "Cost Price by Project" (tipcs3560m000).
In multibyte languages a label needs more space (bytes) than in other languages. Now more space (bytes) is used for handling
labels in a multibyte language.

Solution: 126370
SITUATION IDENTIFIED IN:
"Confirm Shipments" (whinh4275m000)
SITUATION DESCRIPTION:
-1- In case of triangular invoicing, the IMPORT/EXPORT statistics (INTRASTAT) was not properly updated when
confirming a shipment.
-2- When returning a item that had been originally issued from consignment not-owned inventory, the MAUC value was set
to 0.
-3- The integration transactions of the type Warehouse(Order)/Correction and Warehouse(Order)/Cycle Counting Adjustment
Order should be created for both the Debit and the Credit lined in the Finance Company of the Warehouse.
If an adjustment was processed for a project, the Credit line was posted in the Finance Company of the Calculation Office
linked to the Project.
SOLUTION DESCRIPTION:
-1- The IMPORT/EXPORT statistics will be properly updating (according to the INTRASTAT regulations).
A triangular trade scenario could be described that way:
A = Customer in Belgium
C = Sales Office in Belgium
B = Warehouse in the Netherlands
The Sales Office in Belgium sells some goods to a Belgian Customer.
The goods are directly shipped from the Netherlands to the Belgian Customer.
The Belgian Sales Office invoices the Belgian Customer (for the commercial price).
The "Warehouse" in the Netherlands invoices the Sales Office in Belgium (for the transfer price).
This case could be described as follows (according to Baan's functionality):
The goods are shipped from an EU (Enterprise Unit) Country to another EU Country:
- Country of the Ship-To Address is and EU Country
- Country of the Ship-From Address is an EU Country
- The countries are different
1) Scenario
(all the countries are EU Countries)
a)
- Country linked to the Address of the Invoice-From BP C (Internal BP-SLS) is the SAME as
- Country linked to the Address of the Invoice-To BP A (Customer)
b)
- Country linked to the Address of the Invoice-To BP C (Internal BP-SLS) is NOT the SAME as
- Country linked to the Address of the Invoice-From BP B (Internal BP-WH)
**Goods Value (tccom710.gdam) and Statistical Value (tccom710.stam):
The Invoice amount of the Internal Sales Invoice (Transfer Price) should apply.
2) IMPORT/EXPORT Statistic records to be created:
**2 records should be created:
- RECORD 1:
The company of the record should be the Finance Company linked to the EU of the Sales Department.
The record should be of the type RECEIPT.
- RECORD 2:
The company of the record should be the Finance Company linked to the EU of the Warehouse.
The record should be of the type ISSUE
-2- The MAUC value is properly updated after receiving a return order.
-3- The integration transactions will be created in the correct Finance Company.

Solution: 126371
SITUATION IDENTIFIED IN:
"Print Key Entities" (tcemm1410m000)
SITUATION DESCRIPTION:
Printing Warehouses in Session "Print Key Entities" shows incorrect data for the column "Distribution Cluster".
For Warehouses which are not in a Distribution Cluster, the name of the previous printed Distribution Cluster is printed.
SOLUTION DESCRIPTION:
Printing Warehouses in Session "Print Key Entities" shows correct data for the column "Distribution Cluster".

Solution: 126377
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Warehouse and Item" (whina1210m000)
SITUATION DESCRIPTION:
1. The check boxes 'Also based on FTP' and 'Also based on MAUC' are selected in the session "Perform Inventory
Valuation by Warehouse and Item" (whina1210m000)
2. The amounts printed under the FTP and MAUC columns are not rounded in the report. Instead they are truncated as per
the display format of the currency.
SOLUTION DESCRIPTION:
The amounts are rounded according to the currency of the report and then printed under the columns FTP and MAUC.

Solution: 126381
SITUATION IDENTIFIED IN:
"Assembly Orders" (whinh2501m000)
SITUATION DESCRIPTION:
For an Assembly Order, it is not possible to change the assemble status to "Assembled" if the location is a bulk location.
Hence, it is not possible to inbound goods at this bulk location for this order.
SOLUTION DESCRIPTION:
Now, system allows the user changing the status of the Assembly Order to "Assembled". Hence, it is possible to inbound
goods at the bulk location for the assembly order.

Solution: 126384
SITUATION IDENTIFIED IN:
"Easy Warehousing Order Entry" (whinh2202m000)
SITUATION DESCRIPTION:
It is possible to start a zoom session via COMMA+TAB key combination: this functionality zooms to a session and displays
it by Search Key order.
But sessions whinh2202m000 "Easy Warehousing Order Entry" and whinh3100s000 "Shipment Notices" do not recognize
,+TAB as a search functionality.
Also when the zoomed session is whwmd4500m000 "Item Warehousing Data", the session displays the first item instead of
the item that matches the specified Search Key.
SOLUTION DESCRIPTION:
It is possible now to zoom from sessions "Easy Warehousing Order Entry" and "Shipment Notices" via "," and TAB.
And when zooming to session "Item Warehousing Data" the first displayed item is the one that matches the Search Key.

Solution: 126385
SITUATION IDENTIFIED IN:
"Report Operations Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
While completing a production order of a revision controlled item, the user is allowed to select a lot with a revision code
that differs from the revision code on the production order.
SOLUTION DESCRIPTION:
The system checks the particular item & lot & revision combination is available. When revision does not exist for Item and
lot combination a message is thrown and quantities will not be reported complete.

Solution: 126388
SITUATION IDENTIFIED IN:
"Print Product Variant Statistics" (tipcf6410m000)
SITUATION DESCRIPTION:
Running session "Print Product Variant Statistics" (tipcf6410m000) can result in an error message like "Illegal query......"
or "Syntax error.....". This problem is caused by a wrong query syntax. Problems can only occur with level 1 drivers.
SOLUTION DESCRIPTION:
Query syntax is adjusted so that it is supported by both level 1 and level 2 drivers.

Solution: 126402
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
In case of Sales Return order lines it is not possible to have an hold back quantity of 0.
SOLUTION DESCRIPTION:
The check if the hold back quantity is valid is adjusted

Solution: 126403
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
VERSION(S):
B50_b, B50_c
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
For a purchase return order, Order line inspection field is disabled.The inspection flag is disabled for the purchase order with
order quantity less then or equal to zero. Since it is a purchase return order, the quantity will be negative and the inspection
field will not be flagged and also grayed out.
SOLUTION DESCRIPTION:
Now the problem is solved, the user will have the option to check the inspection field for purchase return orders.

Solution: 126405
SITUATION IDENTIFIED IN:
"Audit Direct Debits" (tfcmg4255m000)
SITUATION DESCRIPTION:
After the introduction of IBAN the 'Receive from Bank' is always required for Direct Debits, even if the option "Bank
Account Required" in session "Payment/Receipt Methods" (tfcmg0140s000) is disabled.
SOLUTION DESCRIPTION:
Option "Bank Account Required" is working properly again. In case this option is disabled in session "Payment/Receipt
Methods" the 'Receive from Bank' in the Direct Debit batch can be left empty. Audit error "pay-by BP Bank not filled"
does not appear anymore.
Also improvements done related to the IBAN functionality both in sessions "Audit Direct Debits" (tfcmg4255s000) and
"Audit Payments" (tfcmg1255s000).

Solution: 126406
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2104s000)
SITUATION DESCRIPTION:
It is not possible to reconcile a credit note partially when the parameter "Credit Notes and Sales Interim Account" is set
and the field "Negative Payments allowed for Credit Notes" in the payment method is "Yes" The message "Amount not
allowed" appears because the amount is negative.
SOLUTION DESCRIPTION:
After installing this solution it is possible to reconcile a credit note partially
This is only possible when the parameter "Credit Notes and Sales Interim Account" is set and the field "Negative Payments
allowed for Credit Notes" in the payment method is "Yes"

Solution: 126413
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
1. There is a sales order and a cross docking purchase order is created for this sales order.
2. Both the sales order and purchase order are split in to details and they are released to warehousing.
3. The first sales order line is shipped by generating outbound advice and the status of the line is 'Shipped'
4. Now the purchase order is received and the inbound advice is generated and put away.
5. The status of the first outbound line that has already been shipped becomes 'Staged'
SOLUTION DESCRIPTION:
The correct outbound line for which the advice is created would be updated and not t he outbound line that has been already
shipped.

Solution: 126421
SITUATION IDENTIFIED IN:
"Calculate cost and Valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
If there are two items, the first one with a simulated price but with no conversion factor maintained for the 'Purchase unit'
and 'Simulated Purchase Price unit', and the second one without any simulated price and purchase price is equal to zero. While
running 'Cost price calculation' for both the Items, the report prints two error messages for the second Item, 'No conversion
factors found' and 'Purchase price of the Item is zero', even though there is no simulated purchase price for that item.
SOLUTION DESCRIPTION:
The report will print appropriate error messages of the Items.

Solution: 126423
SITUATION IDENTIFIED IN:
"Print Specifications Delivered, not yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
Erroneous translation of "order" in German Language
SOLUTION DESCRIPTION:
The label in the form tfacr1432m0001 is changed from "tdpur040.orno" to " tdsls040.orno"

Solution: 126424
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Even though dependent rough demand is covered by the stock of a manufactured item a CTP reservation for the component
is done.
SOLUTION DESCRIPTION:
No CTP reservation will be done when the dependent rough demand is covered by the stock of a manufactured item.

Solution: 126425
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
1. The default price matrix of an item has 'No Discounts' check box checked for it, meaning that the discount linked to the
Price book by means of the field 'Discount Schedule' alone would be applied and no further search would be done on
discount.
2. The 'Apply Total Discount' and 'Apply Cumulative Discount' fields are having the value 'Automatic' in the "Pricing
Parameter' (tdpcg0100s000) session.
3. The discount is not applied to the Sales Order Line when the line is created. This is because the 'No Discount' is read from
the price matrix.
4. When the session, "Sales Order Lines" (tdsls4501m000) is closed, the discount is applied to the lines. This is because at
this time, total discount is applied to the whole order and the 'No Discount' parameter is not read from the price matrix as
the system doing only the Rediscounting and not the repricing.
5. But, when there are more than one lines present to the order, the discount is not applied to the lines, when the session
"Sales Order Lines" (tdsls4501m000) is closed.
SOLUTION DESCRIPTION:
When there are more than one lines present, the both reprice and rediscount were done when the Total Discount was applied.
Due tot his the 'No Discount' got read and then the further discount from the Discount Schedules were not applied to the lines.
Now at the time the session "Sales Order Lines" (tdsls4501m000) is closed, only rediscount is done and not the combination of
reprice and rediscounts. So the discount is applied to all the lines, if there is an effective discount present for the line.

Solution: 126430
SITUATION IDENTIFIED IN:
"Material to issue for Production orders" (ticst0101s000)
SITUATION DESCRIPTION:
When doing Initiate Inventory Issue for a negative quantity, the handling of the warehouse orders were not correct in the
following situation:
- The material is lot controlled
- Quantity 'To Issue by Warehouse' (as seen in "Material to Issue for Production Orders") is not zero (e.g. because of
shortages on the lot)
- The negative quantity to issue exceeds the actual quantity ( 'To Issue' + ' Actual Qty' < 0)
- The flag 'Direct Process Outbound' (which implies also direct process inbound for negative quantities) is on.
SOLUTION DESCRIPTION:
A check has been added to the Initiate Inventory Issue function. Materials in the situation described above, are not Initiated
and the user will get a message on the error-report. The user has to clear the 'Direct Process Outbound' flag first and handle
the warehouse orders manually. This is standard procedure in case of shortages.

Solution: 126432
SITUATION IDENTIFIED IN:
"Generate Maintenance Planning" (tsspc2200m000)
SITUATION DESCRIPTION:
Performance problem while generating maintenance planning.
SOLUTION DESCRIPTION:
Performance improved by modifying a problem query.

Solution: 126438
SITUATION IDENTIFIED IN:
"Invoiced Sales-Order History by Item" (tdsls5504m000)
SITUATION DESCRIPTION:
No records found in case the project code is filled but the project segment of the item is empty.
SOLUTION DESCRIPTION:
The find option uses a certain logic to determine which fields are presented in the find window. Modifications are made so
the project field matches the logic.
Now the project field is available within the find window

Solution: 126441
SITUATION IDENTIFIED IN:
"Hours accounting transactions" (tphrs1100s000)
SITUATION DESCRIPTION:
For a closed fiscal period in baan the system allows to enter a hours accounting record .
SOLUTION DESCRIPTION:
When you enter hours in a period which is closed and when transactions are only for projects then the system gives the error
message saying that the period is not open in baan finance.

Solution: 126443
SITUATION IDENTIFIED IN:
"Print Item Revisions by ECO" (tiedm3460m000)
SITUATION DESCRIPTION:
Session tiedm3460m000 incorrectly named as "Print Item Revisions by ECO"
SOLUTION DESCRIPTION:
Session tiedm3460m000 had been renamed correctly as "Print Item Revisions by Order".

Solution: 126444
SITUATION IDENTIFIED IN:
"Print Service Finance Reconciliation" (tcfin3400m000)
SITUATION DESCRIPTION:
The 'To Year' can not be accessed and due to this the user is not able to print the data related to the 'Service Orders' that are
spread across the years.
SOLUTION DESCRIPTION:
The user can access the field 'To Year' and a value can be entered.

Solution: 126446
SITUATION IDENTIFIED IN:
"Notification" (tfcmgl201m00l)
SITUATION DESCRIPTION:
Inappropriate field label.
In the said session, currently there is a field label as "Due date of Trade Note". The same is not appropriate & should be
changed to "Maturity Date of Trade Note".
SOLUTION DESCRIPTION:
The label with description "Due date of Trade Note" is changed to "Maturity Date of Trade Note".
This new label is used to replace the old one in the sessions
1.Notification (Receipts)
2.Notification (Payments)
As the old label is not used any where it is expired.

Solution: 126447
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b
124592, 124931, 125715, 206419
Defects solved in 71a
124931, 206419
Descriptions:
- Defect 124592 AFS putting empty value to field with defaults not posible
- Defect 124931 Grid selection out of range when nr of occ's on the different forms are not equal
- Defect 125715 Check input for array fields only executed ones for check.all.input
- Defect 206419 Sorting in descending order via qbf was not correctly working
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 126449
SITUATION IDENTIFIED IN:
"Print Reminder Diary " (tfacr3430m000)
"Maintain Reminder Diary " (tfacr3130m000)
SITUATION DESCRIPTION:
Balance incorrect with trade notes in the reminder diary when status is "Document Sent To Customer"
SOLUTION DESCRIPTION:
Correct Balance is calculated when the status is "Document Sent To Customer"

Solution: 126451
SITUATION IDENTIFIED IN:
"Query by Form" (ttstpqbf)
SITUATION DESCRIPTION:
When using a mix of ascending and descending sort order then the navigation in the form will go wrong.
SOLUTION DESCRIPTION:
The filter functionality for sorting is now changed in such a way that you can only select an ascending or a descending order
for all the fields. Mixing is no longer possible.
Also the standard program is updated to handle the descending sort order correctly.

Solution: 126455
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
(1) In case of blocking an invoice after registering and using an non-deductible vat on line level (so the cost account is
used for vat) the system takes the purchase Vat account. The system overwrites the ledger account (cost account) of the vat
code with the Purchase vat account when a modification is done on session "Register Purchase invoices - tfacp1110s000".
(2) When a normal bank number is used at the factoring company then this bank number
is visible at tfacp1110s000. However when the IBAN bank number is filled in at the factoring companies bank then this
IBAN number is not visible at session "Register Purchase invoices - tfacp1110s000".
SOLUTION
DESCRIPTION:
(1) The vat ledger account determined in transaction line or the modified ledger account for the vat is not overwritten
anymore.
(2) When an IBAN number is available the IBAN bank number is displayed.

Solution: 126470
SITUATION IDENTIFIED IN:
"Purchase Order lines" (tdpur4101s000)
SITUATION DESCRIPTION:
Wrong Ledger account is picked for Project Subcontracting Item in Purchase Order lines when the Project is entered in the
Segmented field of Item.
SOLUTION DESCRIPTION:
Now, the Ledger account is defaulted correctly for the Project Subcontracting Items on entering the Project in Purchase Order
lines.

Solution: 126472
SITUATION IDENTIFIED IN:
"Print Posting Report" (tpppc4402m000)
SITUATION DESCRIPTION:
Alignment of the filed "Sequence Number" not correct.
SOLUTION DESCRIPTION:
Now the above-mentioned problem is solved. The field "Sequence Number" is aligned properly.

Solution: 126482
SITUATION IDENTIFIED IN:
"Tax Codes by Line" (tfgld1109s000)
SITUATION DESCRIPTION:
When using a "Mutiple Tax" code within session "Purchase Invoices - tfacp1110m000" and the user changes the "Tax
Amounts" within session "Tax Codes by Line - tfgld1109s000" the "Tax Amount" is not updated when the user does not save
before exiting.
SOLUTION DESCRIPTION:
When using a "Mutiple Tax" code within session "Purchase Invoices - tfacp1110m000" and the user changes the "Tax
Amounts" within session "Tax Codes by Line - tfgld1109s000" the "Tax Amount" is now updated when the user does not
save before exiting.

Solution: 126485
SITUATION IDENTIFIED IN:
"Repair Process Payments Run" (tfcor0111)
SITUATION DESCRIPTION:
When the "Post Payments" process (tfcmg1257m000) is canceled and the first composed payment of the batch is not posted,
the posting documents (tfgld102 and tfacp200) are not deleted when using correction program tfcor0111
SOLUTION DESCRIPTION:
When using correction program tfcor0111 the posting documents (tfgld102 and tfacp200) are also deleted when not all
composed payments are posted after canceling "Post Payments" (tfcmg1257m000).

Solution: 126491
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
Unnecessary integration transactions such as "Production/Price Variance" and "Production/Add.Calc. Office Variance" are
generated when a production order is closed in "Close Production Orders (ticst0201m000)".
SOLUTION DESCRIPTION:
All integration transactions generated are correct. Unnecessary Integration transactions no more gets generated.

Solution: 126497
SITUATION IDENTIFIED IN:
"Put Away Inbound Advice" (whina3203m000)
SITUATION DESCRIPTION:
In case of detail outbound lines and crossdock situation received/advised quantities incorrectly put away.
SOLUTION DESCRIPTION:
Generate and put away inbound advice for crossdocked orders adapted. Now, even if using additional manual outbound advice,
the correct values are stored at crossdocked outbound order lines.

Solution: 126504
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
1. When entering a Sales Order of type "Return Order", filling in a "Return Reason Code", was not mandatory (anymore).
This used to be standard functionality but it was changed in a way that when adding a Sales Order of type "Return Order",
having the "Original Document Number" (tdsls400.odno) filled in, the "Return Reason" (tdsls400.retr) was mandatory.
However, when leaving both fields empty, the order could be saved without any difficulties.
2. There was no check if an entered "Return Reason" was valid.
SOLUTION DESCRIPTION:
From now on filling in "Return Reason", is mandatory again when adding a Sales Order of type "Return Order".
(This should be done in the "Returns"-area on the "General" Tab.

Solution: 126505
SITUATION IDENTIFIED IN:
"Print Differences between COGS and Sales Issue" (cicor0113c000)
SITUATION DESCRIPTION:
Not able to execute the correction program in languages other than English
SOLUTION DESCRIPTION:
Now the correction program can be executed in all languages

Solution: 126512
SITUATION IDENTIFIED IN:
"Open Entries" (tfacp2520m000 and tfacr2520m000)
SITUATION DESCRIPTION:
After solution 125329 the functionality of list fully paid invoices was removed.
SOLUTION DESCRIPTION:
Now the functionality of list fully paid invoices is working properly

Solution: 126513
SITUATION IDENTIFIED IN:
"Business Partner Balances" (tccom4513m000)
SITUATION DESCRIPTION:
While the fields (tccom113.buor) "Order Balance" and (tccom113.buin) "Invoice Balance" are filled with gross amounts
(including tax) field (tccom113.obra) "Open Billing Request Amounts" is filled with the net amount. This is inconsistent as
these data are not reliable for a comparison.
SOLUTION DESCRIPTION:
Now the "Open Billing Request Amount" also is filled with gross amounts.

Solution: 126516
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4101s300)
SITUATION DESCRIPTION:
When Purchase Order Receipts are made for Cost Item or normal Purchase Item with Zero quantity, the actual Receipt number
is not updated in Finance. Instead the series number is updated.
SOLUTION DESCRIPTION:
Now, the actual Receipt number is updated correctly in Finance while receiving Cost Item or Purchased Item with zero
quantity.

Solution: 126517
SITUATION IDENTIFIED IN:
"Generate Project Structure for Product Variant" (tipcs2220m000)
SITUATION DESCRIPTION:
Unsuccessful regeneration of a project structure with message "Item with this generated item code already present" occurs
under following conditions:
* parameter "Identifying Item Code"(tipcf000.idic) is set to "yes".
* a customized item structure is generated on basis of a multi-generic structure.
* the customized item structure is copied to a new customized item structure (multilevel copy).
* the new customized item structure is being regenerated.
SOLUTION DESCRIPTION:
Regeneration of customized item structure with above conditions will not result in message "Item with this generated item
code already present". Cause of this problem was a query not accounting for the possibility of having a customized BOM
component, derived from a generic item, having no product variant (Engineering tab in "General Item Data"
(tcibd0501m000)).

Solution: 126520
SITUATION IDENTIFIED IN:
"Match Electronic Bank Statements" (tfcmg5212m000)
SITUATION DESCRIPTION:
When you enter reference field for more than 500 characters in an EBS file, while matching the EBS file, it is giving the
fatal error out of dimension.
SOLUTION DESCRIPTION:
While Matching the EBS file, which has reference field of more than 500 characters processed successfully without giving the
fatal error out of dimension.

Solution: 126523
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
At the moment of freezing estimates of a production order, if one of the components is not having a standard cost price,
then system pops up an error message "Cost price for item not present". This message does not show the component for which
the cost price is not present.
SOLUTION DESCRIPTION:
The new message contains the component for which standard cost price is not present.

Solution: 126526
SITUATION IDENTIFIED IN:
"Import Version Dump" (tgbrg1245m000)
SITUATION DESCRIPTION:
When we import our DEM dump into another version, we get a lot of errors on for instance AO-documents.
Sometimes we also get an error like "transaction is on, can't continue".
SOLUTION DESCRIPTION:
When there was for the database a need to retry the action to update the data, then the session did not handle this correct.
These so-called retry actions were causing unexpected errors during the import and also failed updates or a failed import.
The session is changed and is now capable of handling the retry actions in a correct way.

Solution: 126529
SITUATION IDENTIFIED IN:
"Rebuild Planned Inventory Transactions" (whinp1200m000)
SITUATION DESCRIPTION:
While running the 'Rebuild Planned Inventory Transactions', the Planned Inventory Transactions are not re-created for the
RFQ generated from planning that have no order type filled in it.
SOLUTION DESCRIPTION:
Now, the Planned Inventory Transactions are created properly for the RFQ generated from Planning, which don't have Order
type filled in.

Solution: 126535
SITUATION IDENTIFIED IN:
"Single Tax Rates" (tcmcs0132m000)
SITUATION DESCRIPTION:
When browsing through all the records in Single Tax Rates, the records where the VAT code was blank were skipped. This
was incorrect, because in the Single Tax Rates table (tcmcs032) these records could be found.
SOLUTION DESCRIPTION:
When browsing through all the records in Single Tax Rates, the records are displayed correctly, even when there is a blank
Tax code linked to a Country.

Solution: 126542
SITUATION IDENTIFIED IN:
"Maintain and Confirm Back Orders" (tdsls4125m000)
SITUATION DESCRIPTION:
When a back order line is confirmed the link to the purchase order line is lost for the new created back order detail. This
happens in case the sales order and the purchase order are linked using the Cross Dock functionality
SOLUTION DESCRIPTION:
When the new detail line is created the link to the purchase order line is copied from the original line

Solution: 126547
SITUATION IDENTIFIED IN:
"Release to warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
1. The 'Over Delivery' parameter has a non-zero value in "Inventory Handling Parameters" (whinh0100s000).
2. When 2 sales order lines are released together to warehousing, they are created under 2 separate warehouse order headers
with different order set.
3. They are created under the same warehouse order header if the 'Over Delivery' parameter has the value 0.00.
SOLUTION DESCRIPTION:
The Sales Order Lines will be created under the same warehouse order header when they are released to warehousing in
"Release to warehousing (Batch)" (tdsls4246m000).
Solution: 126548
SITUATION IDENTIFIED IN:
"Uninstall Solution" (ttpmc2208s000)
SITUATION DESCRIPTION:
The session "Uninstall Solution" (ttpmc2208s000) didn't uninstall the given solution, but no error message was given. This
happened when an application lock was set for the Package VRC table (ttadv111). In this case no uninstallation can be
done. This lock could have been set by another import process, a running "create runtime", maintenance on the Package
VRC table by session ttadv1111m000, etc.
SOLUTION DESCRIPTION:
When the Package VRC table (ttadv111) is locked, a proper message is given now and you can choose to stop or to try again.

Solution: 126554
SITUATION IDENTIFIED IN:
"Print Supplier Aging Summary" (tfacp3425m000)
SITUATION DESCRIPTION:
In other languages as English there are, due to length problems, missing labels in multiple forms and reports.
SOLUTION DESCRIPTION:
In other languages as English there are no more missing labels in multiple forms and reports.

Solution: 126561
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2400m000)
SITUATION DESCRIPTION:
Additional reports linked to session (cisli2400m000) "Print Invoices" lead to a duplicate appearance of the report select box.
SOLUTION DESCRIPTION:
Now the report selection box doesn't appear more than once.

Solution: 126563
SITUATION IDENTIFIED IN:
"Print references to Parent" (ttaad4229m000)
SITUATION DESCRIPTION:
When trying to run the session 'Print references to parent' (ttaad4229m000), when the table name, company number and the
key-field values are filled, and the user selects the 'Continue' option, message 'Description not allowed' is displayed and the
user cannot execute the session.
SOLUTION DESCRIPTION:
Now it is possible to execute the session successfully when all the mandatory fields are filled in.

Solution: 126565
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
It was impossible to receive an Advanced Shipment Notice (ASN) via EDI (or manually) for purchase order lines (without a
warehouse) for a Baan Project (Error: "Order ",,,," -0 is not present as warehouse inbound order line or as direct delivery
purchase order line"). The ASN cannot be received in Warehousing because these purchase order lines are not released to
warehousing.
SOLUTION DESCRIPTION:
There are now two ways available to receive an ASN for purchase order lines without a warehouse for a Baan Project:
1. EDI:
Import of Advanced Shipment Notices via EDI fills the ASN header and line data in warehousing and the Purchase Order
Receipts are automatically updated. The "Remarks in Copied Messages" report shows if the lines were successfully updated
or not.
2. Manual process:
An Advanced Shipment Notice can be entered in the session
Shipment Notice Lines (whinh3101s000). An extra form
option is created in session Shipment Notices (whinh3500m000) to receive the lines for the Baan Project. The user is notified
about the result.

Solution: 126568
SITUATION IDENTIFIED IN:
"Calculate cost and valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
In the BOM structure of an end item, a component is a phantom item with item surcharges. In the costing data of entire
structure, the surcharges by item and warehouse are not considered. Even then on cost price calculation, the surcharges of
phantom are getting added into end item.
SOLUTION
DESCRIPTION:
The surcharges of the phantom component will not be reflected in the end item, if the item / warehouse surcharges are not
considered in the costing data.

Solution: 126577
SITUATION IDENTIFIED IN:
"Planned PRP Purchase Orders" (tppss6810m000)
SITUATION DESCRIPTION:
Unable to create Planned PRP Purchase orders with an Intra EU Business Partner having the 'EU Tax Handling' defined. When
a purchase order is created manually, the tax is taken correctly from the 'EU Tax Handling', but when a PRP Planned
Purchase order is created with the same Business Partner, an error message pops up saying that 'Tax code of item not present
for country of buy from Business Partner'.
SOLUTION DESCRIPTION:
This message was coming because taking the tax code was being picked up from the item instead of taking it from the ones
defined in the 'EU Tax Handling' as it should be done for Intra EU Countries.

Solution: 126584
SITUATION IDENTIFIED IN:
"Print Production-Order Documents" (tisfc0408m000)
SITUATION DESCRIPTION:
If an estimated material of a production order is linked to a reference designator, and if the production order documents for
this production order is printed then the report ' Material List ' has the item printed twice.
SOLUTION DESCRIPTION:
The estimated materials for the production order is printed only once in report for Material List.

Solution: 126589
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
1. There is Phantom Item and it has got components.
2. A sales order is created for this item and 'Issue Components' is selected in the sales order lines.
3. There is not enough inventory for one of the components.
4. When the outbound advice is generated, the shortage message shows the same components code for all the components.
SOLUTION DESCRIPTION:
Now the error messages are displayed correctly showing the correct item and the correct shortage quantity and unit.

Solution: 126591
SITUATION IDENTIFIED IN:
"Confirm Purchase Order Advise " (whina3211m000)
SITUATION DESCRIPTION:
It is not possible to confirm the purchase order advice of a KIT item from the session "Confirm Purchase Order Advise "
(whina3211m000). The error report comes as
++++++++++++++++++++++++++++++++++++++
"Cost price structure not defined for date% time%"
++++++++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
It is possible to confirm the purchase order advice with out any error message.

Solution: 126593
SITUATION IDENTIFIED IN:
"Inbound Advice" (whinh2115s000)
SITUATION DESCRIPTION:
1. The item is attached to a 'Storage Condition'
2. There is a Location attached to the same storage condition mentioned above.
3. An Inbound Order Line is created for this item and the advice is created for the above location.
4. Now in the session "Inbound Advice" (whinh2115s000), the Destination Location is changed in such the way that the
storage condition of the new location does not match with the item.
5. The system gives the error
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
"Storage condition YANN01 Item YANN21 does not match with warehouse/location YLP/B02. Location not allowed"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++
6. But the when the new location is entered and the Revert button is pressed twice, the system allows to Save the record with
out doing the Storage Condition check of the destination location.
SOLUTION DESCRIPTION:
Now the system would not allow the user to save the Inbound Advice unless the correct location that matches the storage
condition is filled.

Solution: 126600
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2120s000)
SITUATION DESCRIPTION:
Mentioned situations are only happening for delivery types:
'From Warehouse in Car' and 'From Warehouse by Transport'.
-> Situation 1:
From within service it is possible to change an outbound line by changing the delivered quantity or the subsequent delivered
quantity. In warehousing this is only allowed until there is a released quantity. When changing in service the to be
delivered or the subsequent delivery quantity, error message "Warehouse order line In0000226/50 with order origin service
has not been deleted because of status" will popup, if the issue warehouse order is not modifiable anymore.
-> Situation 2:
Modifying the delivered or subsequent delivered quantity will result
in double transfer orders. This situation would
only occur when an estimate
existed.
-> Situation 3:
Modifying either the 'Subsequent delivery' quantity or the 'To be Delivered' quantity to a
higher value (summarized) then the estimated quantity, would lead to inconsistency
between the open outbound issue order line in warehousing and the subsequent delivery quantity in Service, when the issue
button was hit, without saving first.
Example:
start situation:
Estimated Quantity: 3
Subsequent Delivery 3
To Be Delivered quantity 0
Actual quantity 0
- modify the to be delivered quantity to 2 and the subsequent delivery quantity to 2 and hit the issue button.
result values in service:
Estimated Quantity: 3
Subsequent Delivery 1
To Be Delivered quantity 0
Actual quantity 2
whereas an open outbound order line of 2 would still exist in warehousing.
SOLUTION
DESCRIPTION:
-> Solution 1
For delivery types 'From Warehouse in Car' and 'From Warehouse by Transport' the 'To be delivered' quantity field and the
'Subsequent delivery' quantity fields will be disabled when it is not allowed anymore to modify the corresponding warehousing orders. Same
functionality already existed for delivery type 'From Warehouse'.
-> Solution 2:
-For delivery type 'From Warehouse in Car' and 'From Warehouse by Transport' transfer orders are created when the order / activity is released. Changing the total required quantity (to be delivered + subsequent delivery + actual quantity) will only have effect on the transfer order, as long
as the warehouse procedure did not start yet for the outbound of the transfer order. When the transfer order procedure did not start yet, the quantity on the
transfer order will be equalized to total required quantity (to be delivered + subsequent delivery + actual quantity).
Note that normally the transfer order will always be processed before the engineer will go onsite. In these cases, no change will be made on the transfer order
anymore, as explained
.
- Situation 3:
The open outbound issue order in warehousing will correspond with the sum of
the 'To Be Delivered' quantity and the 'Subsequent Delivery' quantity, no matter in what order actions are executed on the service side.

Solution: 126602
SITUATION IDENTIFIED IN:
"Generate Bills of Critical Material" (tibom2220m000)
SITUATION DESCRIPTION:
System is considering the Expired components also while Generating the Bills of Critical Material.
SOLUTION DESCRIPTION:
System will not consider the Expired Components while Generating the Bills of Critical Material.

Solution: 126610
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1. For the Integration Transaction 'Purchase/General Cost', the Dimension is defined for the 'Series' of the Purchase Order.
2. A Cost item is entered in the "Purchase Order Lines" (tdpur4101s000) session .
3. The Dimension that has been defined for the 'Series' is not retrieved to the "Purchase Order Lines" (tdpur4101s000).
SOLUTION DESCRIPTION:
The Dimension code that has been defined for the Series of the Purchase Order, would be retrieved to the session "Purchase
Order Lines" (tdpur4101s000).

Solution: 126613
SITUATION IDENTIFIED IN:
"Print Specifications Delivered, not yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
Erroneous translation of "order" in German Language
SOLUTION DESCRIPTION:
The label in the form tfacr1432m0001 is changed from " tdpur040.orno" to " tdsls040.orno"

Solution: 126619
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
After saving a record, when amounts are changed in a customer transaction, the defaulted discount amounts are wrongly
populated.
SOLUTION DESCRIPTION:
After saving a record, when amounts are changed in a customer transaction, the defaulted discount amounts are populated
correctly now.

Solution: 126625
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501)
SITUATION DESCRIPTION:
Calculation of "Open Balance" not correct. Calculation does not include unpaid Invoices and Open Billing Requests (as it
should be according to the definition in the accompanying help text).
SOLUTION DESCRIPTION:
Adjusted the selection of records for which the Open Balance is calculated.
The Open Balance for a given BP is now calculated as the total of:
- Billing Request Amount
- Invoice Balance
- Open Order Balance (optional; dependent of parameter setting 'Include Open Sales Order in Financial Risk Calculation'
that can be set in session "Credit Rating" (tcmcs0164s000)).
The balances are summarized over all companies and all departments.

Solution: 126636
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Option "Adjust Hold Back Quantity" missing in the shortage menu for the Dutch en German language
SOLUTION DESCRIPTION:
Translations added to the menu

Solution: 126638
SITUATION IDENTIFIED IN:
"Select Values for GRNI Reconciliation" (tfacp1235m000)
SITUATION DESCRIPTION:
When selecting records for GRNI reconciliation using session "Select Values for GRNI Reconciliation" (tfacp1235m000), the
service orders are selected as manual orders.
SOLUTION DESCRIPTION:
The service related GRNI records are selected correctly with the correct purchase order numbers linked to it.

Solution: 126645
SITUATION IDENTIFIED IN:
"Release to warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
1. The 'Over Delivery' parameter has a non-zero value in "Inventory Handling Parameters" (whinh0100s000).
2. When 2 sales order lines are released together to warehousing, they are created under 2 separate warehouse order headers
with different order set.
3. They are created under the same warehouse order header if the 'Over Delivery' parameter has the value 0.00.
SOLUTION DESCRIPTION:
The Sales Order Lines will be created under the same warehouse order header when they are released to warehousing in
"Release to warehousing (Batch)" (tdsls4246m000).

Solution: 126655
SITUATION IDENTIFIED IN:
"Purchase Order Headers" (tdpur4100s000)
SITUATION DESCRIPTION:
Change in the Pay-To BP address on a Purchase Order Header, is not reflected in the Payment Check.
SOLUTION DESCRIPTION:
Allowing modifications in Pay-To BP, and the related fields - Address and Contact, in the 'Paying' tab, for reflection in
Payment Checks would bring in lot of complexities.
So, the fields 'Business Partner', 'Address' and 'Contact' in the 'Paying' tab in the Purchase Order Header have been disabled
for input. The fields can only be changed in the 'Business Partners' Master data now.
This change has been done as these fields are present in the Purchase Order Header only for information purposes, and it is
not used as input in the finance module.

Solution: 126657
SITUATION IDENTIFIED IN:
"Print Hours Control" (tpppc4414m000)
SITUATION DESCRIPTION:
In the second form of this session , there are options to choose which type of charge elements are to be printed. But this
selection is ignored and always all the charge elements in the range specified are printed.
SOLUTION DESCRIPTION:
Now the print options on the type of the charge elements are correctly considered and only the charge elements of the type,
which are chosen to print only are printed.

Solution: 126668
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: 126674
SITUATION IDENTIFIED IN:
"Process Transactions" (tpppc4802m000)
SITUATION DESCRIPTION:
If we have a transfer (manual) order and only a part of it is released and shipped, when trying to close the project linked
to this order (using session tpppc4802m000 (Process transactions), the following message arises: "Project not reported
completed, planned warehouse order still present XXX"
SOLUTION
DESCRIPTION:
Two different situations are considered now:
1) The origin order is a Transfer (manual) order: it will be possible to close the project if all the order lines have status "Shipped" even
if not all the quantities are shipped (status is checked).
2) In any other case: It will be only possible to close the project if the whole quantity specified for the order is shipped (quantity is checked).

Solution: 126678
SITUATION IDENTIFIED IN:
"Dynamic Menu Browser" (tgbrg4260m000)
SITUATION DESCRIPTION:
When our end-user is logged in using the Dynamic Menu Browser and then switches to another company, another Dynamic
Menu Browser is started.
He can however not see any session in that one, there is always the message 'You have no authorizations for activities in
this Business Process' popping up.
The DEM data for that end-user is in both companies the same.
SOLUTION DESCRIPTION:
The check, we did to look if roles (linked to users) have authorization for activities in a Business Process, was not using the
right variables.
We changed this and now also a second Dynamic Menu Browser works normal.

Solution: 126679
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
When creating a Purchase Correction the lines are being created with the date of the Purchase Invoice, instead of the date of
the Batch header.
SOLUTION DESCRIPTION:
When creating a Purchase Correction the lines are being created with the date of the Batch header, instead of the date of the
Purchase Invoice.

Solution: 126685
SITUATION IDENTIFIED IN:
"Archive Hours History" (tihra3250m000)
SITUATION DESCRIPTION:
Some hours are entered for an Employee for a period in the operational company. These hours are processed and then
Archived to an Archive company through "Archive Hours History". Now user enters again some hours for the same Employee
and against the same (archived) period in the Operational Company. If user process and Archive these new hour's, then
system is not updating these hour's in the Archive company for that period and the old Archived date remains the same.
SOLUTION DESCRIPTION:
This is standard functionality of the session. Hence the functional explanation is added in the session help Text.
The hours history is stored in the tables by period. Hence, archived hours history data is also archived by period. Once the user archives the hours
history from the current (operational) company to the archive company, the hours history is deleted from the current (operational) company and stored in the archive company, by period. If the user wants to add additional data to the archived period for an employee, he or she can do that in the current (operational) company. If that hours history period is archived again, the existing data archived for that period will not be updated.

Solution: 126686
SITUATION IDENTIFIED IN:
"whltc1505m000" (Lots by Warehouse)
SITUATION DESCRIPTION:
The field "Lot Inventory on Order" in the table "Lots by Warehouse" (whltc105) can get a wrong value when material is
returned from production. The value can even become negative.
SOLUTION DESCRIPTION:
The field "Lot Inventory on Order" is updated properly.

Solution: 126696
SITUATION IDENTIFIED IN:
"table boosters" (tccomdll0201)
SITUATION DESCRIPTION:
Sometimes (batch)job hangs due to table-caching.
SOLUTION DESCRIPTION:
Caching-mechanism improved.

Solution: 126704
SITUATION IDENTIFIED IN:
"Match / Approve Purchase Invoices" (tfacp2507m000)
SITUATION DESCRIPTION:
Incase the surcharge method is defined as based on added cost, when booking the Price variance, surcharges were not
calculated on the Price variance. This happened only when the surcharge method is based on Added cost. When it is not
based on added cost, a surcharge was calculated, and additional bookings made for Price Variance - Item Surcharge
SOLUTION DESCRIPTION:
Now, irrespective of the surcharge method (added or total or fixed),
surcharge on Price variance is calculated. Additional bookings are made, as described in solution 116329 .

Solution: 126706
SITUATION IDENTIFIED IN:
"Print Costs by Periods" (tpppc4416m000)
SITUATION DESCRIPTION:
Report does not show the values correctly. Many places Hashes are printed.
SOLUTION DESCRIPTION:
Now, the above mentioned problem is solved. The length of the report fields is increased.

Solution: 126713
SITUATION IDENTIFIED IN:
"Copy Engineering Items to Items" (tiedm1201m000)
SITUATION DESCRIPTION:
While copying the Engineering Items to Item, the search Key in Item Production data and Item Purchase data updated as
Item Description instead of Search Key maintained in Engineering Item.
SOLUTION DESCRIPTION:
If user maintains the Search key in Engineering Item, while copying the E-Item to Item, the search key in Item Production
data and Item Purchase data will be updated as Search Key maintained in Engineering Item.

Solution: 126715
SITUATION IDENTIFIED IN:
"Print Purchase Invoices" (tfacp2421m000)
SITUATION DESCRIPTION:
When running session "Print Purchase Invoices" tfacp2421m000 with the field "Invoices to be Printed" set to "Approved
Invoices" the report prints also the purchase credit notes which has the status "Registered".
SOLUTION DESCRIPTION:
When running session "Print Purchase Invoices" tfacp2421m000 with the field "Invoices to be Printed" set to "Approved
Invoices" the report prints only the purchase credit notes which has the status "Approved".

Solution: 126716
SITUATION IDENTIFIED IN:
"Replace Items in Bills of Material" (tibom1212m000)
SITUATION DESCRIPTION:
Problem 1:
When a range of Items are given in the session "Replace Items in Bills of Material", If any error occurs while processing a
record, system aborts the whole transaction of the process.
Problem 2:
While Replacing the Item in Bills of Material, when the field Retain original Item is selected, system will expire the
component under customized Item, even though the Project has the status greater than active.
SOLUTION DESCRIPTION:
Solution 1:
When a range of Items are given in the session "Replace Items in Bills of Material", If any error occurs while processing a
record, system will aborts the transaction of that particular record only.
Solution 2:
While Replacing the Item in Bills of Material, when the field Retain original Item is selected, system will not expire the
component under customized Item, when the Project has the status Finished, Canceled, Closed and Archived.

Solution: 126722
SITUATION IDENTIFIED IN:
"Business Process Diagram" (EME)
SITUATION DESCRIPTION:
We have a situation, that we work in the same DEM environment in two languages.
When we attach a description to a relation in a Business Process in language 1 and not in language 2, then after closing a
changed Business Process in language 2, the description of the relation in language 1 is disappeared.
SOLUTION DESCRIPTION:
Descriptions within DEM are stored as labels. When writing the Business Process in language 2 with no description, the
label for language 1 was deleted.
This mechanism is changed and now it is possible to work with a description in one language attached to the relation and have
no description linked to that same relation in the other language.

Solution: 126729
SITUATION IDENTIFIED IN:
"Generate Configuration Structures" (tscfg2210m000)
SITUATION DESCRIPTION:
In B50b: No help available on field: Order Delivery Date.
In B50c: Helptext on field Order Delivery Date is only in dutch.
SOLUTION DESCRIPTION:
In both versions the helptext is available and translated. Available languages are English, Dutch and German.

Solution: 126730
SITUATION IDENTIFIED IN:
"Print Service Financial Reconciliation" (tcfin3400m000)
SITUATION DESCRIPTION:
1. The Currency of the report printed under the column 'Financial Amounts' corresponds to the first record.
2. For the following records, the amount is printed under the same Currency even if the Currency of the particular record is
different.
3. The amount is not converted to the currency of the report.
SOLUTION DESCRIPTION:
1. Now, the user has the provision of mentioning the currency with which he wants to print the report.
2. The report currency is one of the 'Home currencies', which the user can select by the 'Rotate Currency' option.
3. The amount in the specified currency would be picked and then printed.

Solution: 126732
SITUATION IDENTIFIED IN:
"Maintain indices" (ttadv4121m000)
SITUATION DESCRIPTION:
When adding fields by index, during the save, the error "message field not found" is always given.
SOLUTION DESCRIPTION:
The checkinput was also done for the empty fields. This is now corrected
Solution is marked with DF125715-2

Solution: 126735
SITUATION IDENTIFIED IN:
"Print Reminder Diary" (tfacr3430m000)
SITUATION DESCRIPTION:
Due date is missing for some invoices in the Reminder Diary
SOLUTION DESCRIPTION:
Due date is displayed for All Invoices.

Solution: 126739
SITUATION IDENTIFIED IN:
"Handel Parallel processes" (tccomdll0200)
SITUATION DESCRIPTION:
For a job designated to run multiple bshells (Simulate Orders), we are trying to increase the MAX_RETRY value that the
server bshells uses. The documentation indicated that setting the MAX_RETRY in the env.shell file located in
$BSE/lib/defaults would get picked up by comdll0200 and passed on to the servers. Unfortunately the servers never receive
the new value.
SOLUTION DESCRIPTION:
Exporting of variables from env.shell
file will be done.

Solution: 126748
SITUATION IDENTIFIED IN:
"Copy BOM Components to Quotation" (tdsls1812s000)
SITUATION DESCRIPTION:
English translation missing regarding help text on formfield 'number of BOM levels'
SOLUTION DESCRIPTION:
Translation made available

Solution: 126762
SITUATION IDENTIFIED IN:
"Export Data Dictionary" (ttiex1280m000)
SITUATION DESCRIPTION:
When session "Export Data Dictionary" (ttiex1280m000) is added to a job, it is not possible to change the parameters of this
session. When a parameter is changed on the "environment" tab and the "change job" button is pressed, the focus moves to the
"components 1" tab. When the button "change job" is pressed again, nothing happens. The form is not refreshing correctly, and it is not possible to save the changed job parameters.
SOLUTION DESCRIPTION:
In session "Export Data Dictionary" several checks were done before this session could be added to a job.
Now the program checks if the session is run to change its job parameters, and some of the checks are skipped.

Solution: 126766
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
System gives the error "Index out of dims" when running the simulate orders session for Generic Items which has many
phantom items in the BOM Structure.
SOLUTION DESCRIPTION:
The problem is solved and system will simulate the orders correctly.

Solution: 126770
SITUATION IDENTIFIED IN:
"Accept Values of GRNI Reconciliation " (tfacp1535m000)
SITUATION DESCRIPTION:
Session "Accept Values of GRNI Reconciliation - tfacp1535m000" has a poor performance on starting up.
SOLUTION DESCRIPTION:
Performance is improved for the opening of the session.

Solution: 126775
SITUATION IDENTIFIED IN:
"Inventory by Item and Warehouse" (whwmd2515m100)
SITUATION DESCRIPTION:
1. A Sales Order is created for 10 pcs and the 'Allocated Quantity' goes up by 10 in the session "Inventory by Item and
Warehouse" (whwmd2515m100).
2. For this sales order a quantity more than the Order Quantity is shipped (Say 12 pcs).
3. When the Shipment is confirmed, the Allocated Quantity becomes -2 pcs.
SOLUTION DESCRIPTION:
When the Over Delivery is done with the shipped quantity being more than the order quantity, the reduction of the
Allocated Quantity would be equal to the Order Quantity and not more than that.

Solution: 126782
SITUATION IDENTIFIED IN:
"Print control account check list" (tfacr2415m000)
SITUATION DESCRIPTION:
Wrong data in Print Control account check list, when unallocated /advance payments are involved.
Reversal of solution 125848
SOLUTION DESCRIPTION:
Correct data is printed in Print Control account checklist, when unallocated /advance payments are involved.
Reversal of solution 125848

Solution: 126786
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
If the Supplier Bank Account contains the letter 'E,' in session 'Maintain Banks by Supplier' (tccom2105m000); when
'Transfer Payments' (tfcmg1260s000) to this bank account, a float exception error message pops up and the transfer of
payments is aborted.
The same float exception error occurs, only for French customers, when the Bank Account defined in session 'Maintain Bank
Relations' (tfcmg0110m000) has the letter 'E' on it.
SOLUTION DESCRIPTION:
When the supplier bank account has the letter 'E' on it, no float exception error occurs anymore during 'Transfer Payments'
(tfcmg1260s000) and the payment batch can be transferred.
The float exception error does not occurs anymore, for French customers, when the Bank Account in session 'Maintain Bank
Relations' contains an 'E'.

Solution: 126793
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" (whinh4201m000)
SITUATION DESCRIPTION:
1. The item is a Lot-by-Unit item.
2. The ordered quantity is very high for the outbound order line.
3. When the outbound advice is generated for this order, system gives the fatal error
+++++++++++++++++++++++++++++
Duplicate value 100 on table whinh225
+++++++++++++++++++++++++++++
This is not happening every time and only for few orders.
SOLUTION DESCRIPTION:
The above mentioned fatal error does not appear any more.

Solution: 126796
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
If in session "Outbound Advice" (whinh2125s000 and whinh2125s100), the Storage Unit for the outbound advice is changed,
message "When following the outbound procedure for this advice negative inventory can occur" is always displayed, even
when no negative inventory is created.
Also, when the outbound advice is released, the system checks if the quantity released will create negative inventory or not. But if already some
negative inventory exists in that stock point, the quantity is wrongly assumed to be negative inventory too
SOLUTION DESCRIPTION:
Items with package definition or without were handled in the same way, causing the message to show up wrongly.
The message will not be displayed if the unit is changed to inventory unit or if available inventory exists (for instance, if we have one pallet (1 pallet
=10 boxes = 100 pieces) and we change the advice from one pallet to nine boxes, for an item with package definition no message will be shown, nor negative inventory will be created, but for an item without package definition the message will be shown and 90 pieces of negative inventory will be created)
And when checking if negative inventory needs to be created, if some negative inventory already exists, it is not assumed to be also negative, and
the full check is done.

Solution: 126803
SITUATION IDENTIFIED IN:
"Report Layouts" (tdsmi0181s000)
SITUATION DESCRIPTION:
In session "Report Layouts" (tdsmi0181s000) user is allowed to change the description. When the user modifies this
description and saves the record, changes are lost.
SOLUTION DESCRIPTION:
Now the changes will not be lost. The modified description will be saved.

Solution: 126814
SITUATION IDENTIFIED IN:
"Installments" (tppin4551m000)
SITUATION DESCRIPTION:
During creating an installment the session tppin4151s000 doesn't take into account if there is a relation between an element
and a charge element. If a relation exists between an element and a charge element & if you select the element the related
charge element should be defaulted by the session.
SOLUTION DESCRIPTION:
Now if there is a relation between an element & a charge element & if that element is selected, the related charge element
will be defaulted.

Solution: 126815
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
1. The 'Shipped Quantity' in the Packing Slip is always printed in the Shipping Unit. If the Order unit is different from the
Shipping Unit, the shipped quantity can be printed in the Order Unit as well.
2. a) There is an Outbound Line for 10 pcs. The Outbound Advice is generated from two different stock points for this line.
b) Due to this, two shipment lines are created.
c) When the Packing Slip is printed for this order line, the same data is printed for the two shipment line separately.
d) The shipment lines showing the same data can be cumulated and printed as a single line in the report
SOLUTION DESCRIPTION:
-1- When the Shipped Quantity is different from the Order Quantity, the Packing Slip would be printed in the Shipping Unit
as well as in the Order Unit
-2- The Shipment Lines that contain the same details would be clubbed together and printed in the same report.

Solution: 126826
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements/RMAs" (tdsls4401m000)
SITUATION DESCRIPTION:
Print Order Acknowledgement" is the first activity of a sales order type used for a sales order. The device for printing
order acknowledgments is left blank in session "Activities by order type" (tdsls0560m000), but a default device is defined
for the next activity "Release to Warehousing" (tdsls4246m000). The default device in session "Print Order
Acknowledgements/RMA" (tdsls4401m000) is set to a different device.
When the order acknowledgement is printed for the first time for the given SO, the alternative device saved as a default in
session tdsls4401m000 is used, because the device in session tdsls0560m000 is not filled. Now if the order acknowledgment
has to be printed another time or more for the same order, the device of the following activity (release to warehousing) is
used instead of the alternative device.
SOLUTION DESCRIPTION:
In case the activity "Print Order Acknowledgement" is no part of the used Sales Order Type or the printer defined for this
activity is empty the printer defined in tdsls4401m000 is used. Otherwise the defined printer for this activity within the used
order type is selected

Solution: 126829
SITUATION IDENTIFIED IN:
"Element Progress" (tpppc1550m000)
SITUATION DESCRIPTION:
Element Progress should be allowed enter in case "Budget Type Project Budget" is "Element Budget" and "Budget Type
Project Ctrl" is "Activity Budget" since we can set Element Cost Control to "Yes" in this case.
Currently we are not able to enter Element Progress.
SOLUTION DESCRIPTION:
Now, even when "Budget Type Project Budget" is "Element Budget" and "Budget Type Project Ctrl" is "Activity Budget",
we can enter Element Progress.
So the above problem is solved.

Solution: 126834
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In case a cost invoice is entered for a supplier (with Factoring Company) with a payment method, and the country of the
company, factory company, business partner and bank are all the same, the message: "Payment method cannot be used:
different countries" pops up.
SOLUTION DESCRIPTION:
In case a cost invoice is entered for a supplier (with Factoring Company) with a payment method, and the country of the
company, factory company, business partner and bank are all the same, there is no message anymore.

Solution: 126842
SITUATION IDENTIFIED IN:
"User Data" (ttams1100s000)
SITUATION DESCRIPTION:
In session User Data (ttaad2500m000) select any of the existing users, session User data (ttams1100s000) will appear.
When you zoom in the field "Templates - User Data" on the formtab "Defaults" the following message appears:
"No permission for ttams1510s0001"
The situation will only occur for users of type "Normal"..
SOLUTION DESCRIPTION:
The zoom function has been modified, the user is now able to zoom to session "User Data Template" (ttams1510s000).

Solution: 126844
SITUATION IDENTIFIED IN:
"Compose Loads" (whinh4134m000)
SITUATION DESCRIPTION:
When a load id is not present in the session " Loads" (whinh4540m000) and if no other open loads are present, and if new
shipment is added to this id, the system pops up an error message. It is because, when there are other open loads, the same
Load ID is retained. When the user tries to add shipment to this Load ID, it doesn't find any reference, and so pops up an
error message.
SOLUTION DESCRIPTION:
The unnecessary error message has been removed. But the error message "Load does not exist" is displayed, if the load does not exist.

Solution: 126845
SITUATION IDENTIFIED IN:
"Print Reminders" (tdpur4403m000)
SITUATION DESCRIPTION:
-1- The information related to the Purchase Order Header are printed only once per a supplier. If there are many orders that
are printed for a single Supplier, the header data like Buyer, Supplier Order number etc are to be printed for all the orders.
-2- When the user tabs through the session, the control comes to 'Print Lines with Unconfirmed Receipts' check box after
the Buy-From-BP field. The field that are in between are skipped.
SOLUTION DESCRIPTION:
-1- The data related to the header are printed per every order now.
-2- The control to the fields in the session would go in the order in which the fields are located.

Solution: 126847
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
Cost Component is not populated to the Additions table(tfgld415) for the debit side. Also Enterprise units of the Sales
Office and the Warehouse were also not filled.
Because of that if any dimension has been defined using these data as the relations, then they were not getting filled while
posting the Integration Transactions.
SOLUTION DESCRIPTION:
Now the logistic data is correctly populated into the Additions table. And so the dimensions were picked up correctly.

Solution: 126852
SITUATION IDENTIFIED IN:
"Item Surcharges" (ticpr111s000)
SITUATION DESCRIPTION:
The translation of label "Surcharge Amount" is wrong in German language.
SOLUTION DESCRIPTION:
The label for "surcharge amount" is translated as "Zuschlagsbetrag" in German language.

Solution: 126854
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Descriptions:
- Defect 125699 attr.textfield$ not set in after.choice text manager
- Defect 126678 Session with start option last.set will not show data if not enough available to fill the form
- Defect 208803 Zoomlist not displayed at right place if the list contains to many elements
- Defect 208926 Sort order not restored when windows defaults are restored.
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 126865
SITUATION IDENTIFIED IN:
"Element Relationship" (tpptc1105s000)
SITUATION DESCRIPTION:
For Top element also the error message 'Define a parent element for this element' comes up this is wrong.
SOLUTION DESCRIPTION:
Now a check for the top element is been built and hence the above problem is now solved.

Solution: 126869
SITUATION IDENTIFIED IN:
" Process Solutions" (ttpmc2101m000)
SITUATION DESCRIPTION:
PMC solutions may contain forms with changed references to help topics for the form fields. These references to help topics
were not correctly updated during the installation of the PMC-solution.
SOLUTION DESCRIPTION:
The references to help topics for the form fields are correctly updated.

Solution: 126872
SITUATION IDENTIFIED IN:
"Confirm Shipments/ Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When a bulk of more than 1000 orders is confirmed, an error occurs in the system and the shipments are not able to
confirm.
SOLUTION DESCRIPTION:
It is now possible to confirm more than 1000 orders altogether and all the shipments are confirmed correctly.

Solution: 126873
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
If the planned delivery date is changed for a "Backward" planned production order in "Production Orders" (tisfc0101s000),
then the planning is not changed accordingly.
SOLUTION DESCRIPTION:
If the planned delivery date is changed for a "Backward" planned production order in "Production Orders" (tisfc0101s000),
then the planning is changed accordingly.

Solution: 126875
SITUATION IDENTIFIED IN:
"Sales Order Lines " (tdsls4501m000)
SITUATION DESCRIPTION:
Additional Costs could not be added to Sales Order if a Purchase Order had been generated for Direct Delivery Sales Order
Line.
SOLUTION DESCRIPTION:
The additional costs will now be added to the Sales Orders after a Purchase Order has been generated.

Solution: 126882
SITUATION IDENTIFIED IN:
"Desktop Program Manager" (ttdskprogman)
SITUATION DESCRIPTION:
Using a Desktop as User Interface, errors are coming up in the Eventviewer:
"Error during sopen(${BSE}/gif/desktop2.gif/;${BSE_REM}!${BSE}/gif/desktop2.gif/, )"
SOLUTION DESCRIPTION:
On a desktop you can add an item to a group. For a desktop-item an icon can be used, but this is optional.
When no icon is used, the errors come up in the Eventviewer, because Baan is trying to open a non-existing icon-file.
An extra check is now done: if a desktop-item has no icon, the program will no longer try to open an icon-file.

Solution: 126883
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
The tax code is incorrect when the Ship-to business partner is not a member of the EU.
SOLUTION DESCRIPTION:
Now the right tax code is returned.

Solution: 126885
SITUATION IDENTIFIED IN:
"Advance Payment Requests" (tppin4510m000)
SITUATION DESCRIPTION:
During creating an Advance Payment Request, the session tppin4110s000 doesn't take into account if there is a relation
between an element and a charge element. If a relation exists between an element and a charge element & if that element is
selected, the related charge element should be defaulted.
SOLUTION DESCRIPTION:
Now if there is a relation between an element & a charge element & if that element is selected, the related charge element
will be defaulted.

Solution: 126887
SITUATION IDENTIFIED IN:
"ticst0201m000" (Close Production orders)
SITUATION DESCRIPTION:
Work center of Integration transaction "Production / Efficiency Variance" is not empty in "Additions to Integration
Transactions" (tfgld415) for the first 'FROM' transaction of Efficiency Variance and Price Variance, when the inventory
valuation method of the Item is not FTP (Fixed Transfer Price) and the SFC (Shop Floor Control) Parameters are as follows:
SFC Parameters (tisfc0100s000)
Production Results per Work Center: Yes
Posting Method Efficiency Variances: On Work Center
Posting Method Price Variances: On Work Center
SOLUTION DESCRIPTION:
The first "FROM " transaction of the "Production / Efficiency Variance" will be empty.

Solution: 126895
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4101s300)
SITUATION DESCRIPTION:
-1- When the back order is saved financial transactions were posted. And if the backorder is confirmed manually, then
during this instance also, the same transactions were posted again.
-2- a. A purchase order line is created with a TP project entered in it.
b. The 'Baan Project' is YES in 'Maintain Order Data for Approval' in Finance for this order line.
c. Then, at a later point of time a PCS project is entered in the purchase order line.
d. Now, the value in the 'Baan Project' field is not changed to NO from YES.
e. Due to this, it is not possible to approve the Purchase Invoice for this order line.
SOLUTION DESCRIPTION:
-1- The General costs transactions are now posted correctly even after confirming the backorder.
-2- The 'Baan Project' field would read the value NO now when the project is changed in the Purchase Order Line.

Solution: 126900
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is not possible to handle 'Menu' and 'Option' items in the Purchase Order Lines. But the KIT items of type List can be
handled.
SOLUTION DESCRIPTION:
1. Now, the Menu and Options can be handled in the Purchase Order Lines.
2. The session that shows the components of the List item would appear once the List item is entered in the Purchase Order
Line.
3. If the user does not select any of the components, then the system would not allow proceeding further until some
component(s) is selected.
Solution: 126901
SITUATION IDENTIFIED IN:
"Match Electronic Bank Statements" (tfcmg5212m000)
SITUATION DESCRIPTION:
When you enter reference field for more than 500 characters in an EBS file, while matching the EBS file, it is giving the
fatal error out of dimension.
SOLUTION DESCRIPTION:
The EBS file matched successfully without giving the fatal error out of dimension, which has the reference field of more
than 500 characters.

Solution: 126913
SITUATION IDENTIFIED IN:
"Flexible Printing" (tdsmi2410m100)
SITUATION DESCRIPTION:
When the user is using the session "Flexible Printing (tdsmi2410m100)" to print the report for the full range of Business
Partners, system doesn't print any report and the session hangs.
SOLUTION DESCRIPTION:
Now the problem is solved, the system will print the report for the full range of Business Partners.

Solution: 126914
SITUATION IDENTIFIED IN:
"Approve Purchase Invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
A "Float Exception" error was generated when approving purchase invoices linked to the in the following receipt:
- the Item on purchase receipt is a phantom item.
- the is a Price Difference (Variance between invoice amount and receipt amount).
- the purchase price entered in Purchase Item data for all the components of the phantom item is set to 0 or no Purchase
Item Data has been defined.
SOLUTION DESCRIPTION:
No float exception will be generated anymore.
The price difference will now be spread among the components based on the required quantities of the components as
specified in the Bill of Material of the phantom item (if no purchase price or Purchase Item Data has been specified for the
components).

Solution: 126917
SITUATION IDENTIFIED IN:
"Booked Price Variance Analysis" (tfacp1460m001)
SITUATION DESCRIPTION:
In session "Booked Price Variance Analysis" (tfacp1460m001), there is no grand total present for the report.
SOLUTION DESCRIPTION:
A grand total has been added to the report. Only the fields "Receipt Amount", "Expected Price Variance", "Unexpected Price
Variance" and "Total Price Variance" are present in the grand total.

Solution: 126925
SITUATION IDENTIFIED IN:
"Process Transactions" (tpppc4202m000)
SITUATION DESCRIPTION:
During processing of transactions the program searches the highest serial number in use. The system could give the error
message 205 - Out of Range.
SOLUTION DESCRIPTION:
Solved this by increasing the length of the serial number.

Solution: 126928
SITUATION IDENTIFIED IN:
"Print Receivable Invoice Specifications - Financial" (tfacp1435m000)
SITUATION DESCRIPTION:
In session "Print Receivable Invoice Specifications - Financial" (tfacp1435m000), when the report is printed where the same
supplier is present across different logistic companies under the same finance company, the following values are printed
incorrect. In the report "Balance per order line (on supplier)" the field "Total amount per supplier" and in report "Balance per
order line (on project)", the field "Total amount per project" are printed incorrect.
SOLUTION DESCRIPTION:
The totals in both the reports are getting printed correctly when the supplier/project data is present in different logistic
companies.

Solution: 126940
SITUATION IDENTIFIED IN:
"Print Multi-level Cost Price Calculation " (ticpr2420m000)
SITUATION DESCRIPTION:
Session help text for customized items in session "Print Multi-level Cost Price Calculation" (ticpr2420m000) is incomplete,
if the bom structure is standard and non phantom.
SOLUTION DESCRIPTION:
The help text is modified to give clear explanation of printing multi-level cost price calculation of customized items with
standard bom structure.

Solution: 126944
SITUATION IDENTIFIED IN:
"Match Electronic Bank Statements" (tfcmg5212m000)
SITUATION DESCRIPTION:
When amount is received/paid in full, ignoring discount, payment differences are occurred. And after posting, 'open balance'
remains in the 'Open Entries' for the invoice.
SOLUTION DESCRIPTION:
Now, when amount is received/paid in full ignoring discount, no discount, payment differences are occurred. And after
posting no 'open balance' remains in the 'Open Entries' for the invoice.

Solution: 126945
SITUATION IDENTIFIED IN:
"Calendar Codes" (tcccp0110s000)
SITUATION DESCRIPTION:
When changing the start date or end date in a calendar code and trying to save the record the connection with server gets
lost.
SOLUTION DESCRIPTION:
All related variables have been made dynamic, which will prevent the connection with server lost problem.

Solution: 126954
SITUATION IDENTIFIED IN:
"Booked Price Variance Analysis" (tfacp1460m001)
SITUATION DESCRIPTION:
After GRNI solution, the session "Booked Price Variance Analysis" (tfacp1460m001) has been rewritten to print correct
information.
SOLUTION DESCRIPTION:
The basic aim of this report is
- The report is not calculating amounts but only picking up data from the tables
- This report has not the intention to build the balance on the price difference ledger accounts
The information on the report can be divided in the following information groups:
- Receipt information
This is the information of the received goods by purchase order / position. Data is picked up from "Integration References".
- Expected price variance information
This is the information of the difference between the amounts of the order and the costprice of item. Data is picked up from
"Integration References".
- Invoice information
This is the information of the invoices, which are matched/Approved with the order/position. Data is picked up from table
"Invoices related to purchase order lines" (tfacp250).
- Unexpected price variance information
This is the information of the difference between the amounts of the matched invoices with the receipt amounts. Data is
picked up from "Integration References".

Solution: 126956
SITUATION IDENTIFIED IN:
"Form Editor" (ttadvformedit)
SITUATION DESCRIPTION:
When in the form editor with a width of 255 a form field was moved to the right border, a fatal error "index out of dims"
occurred.
SOLUTION DESCRIPTION:
An array, which is used internally by the program is enlarged from 255 to 257 bytes. This solves the problem.

Solution: 126961
SITUATION IDENTIFIED IN:
"Payment Schedules" (tfacp1103m000)
SITUATION DESCRIPTION:
In session "Payment schedules - tfacp1103m000", when zooming from session "Purchase Invoice Details - tfacp2500m000", if
the user browses from one invoice to another, the amount paid and amount to be scheduled get wrong values. Besides, if an
invoice has been paid but no payment schedule has been maintained, the amount paid is shown as zero.
SOLUTION DESCRIPTION:
-It is no longer allowed to browse in session tfacp1103m000 if the session is open from session tfacp2500m000.
-The amount paid is correctly updated (as well as the amount to be scheduled), if the invoice has been paid and there is no
payment schedule.

Solution: 126971
SITUATION IDENTIFIED IN:
"Maintain Labor costs" (tpppc2131s000)
SITUATION DESCRIPTION:
If we try to enter hours for a period, which is closed we get the message "Period is not open in Baan Finance". Now if we
manually change this to a period, which is open and go to form 2 and tab back, the original closed period is displayed again.
SOLUTION DESCRIPTION:
This problem was happening as the form was getting refreshed when tabbed back. This problem is now solved and the period
value will not change back.

Solution: 126972
SITUATION IDENTIFIED IN:
"Confirm Shipments" (whinh4275m000)
"Print Sales Order Lines" (tdsls4409m000)
SITUATION DESCRIPTION:
1. When confirming a shipment (session whinh4275m000), which causes overdelivery, the sales order line details (as in session
tdsls4501m200) are incorrect. In some cases the order quantity of a detailline became negative. In other cases the ordered
quantity of a new detail line was the sum of all deliveries.
2. When printing report "Sales Order Lines" (session tdsls4409m000) for an overdelivered sales order line, the outstanding
quantity is negative.
SOLUTION DESCRIPTION:
1. The Sales Order Detail Lines reflect the several shipments correct now. This means that when a shipment causes
overdelivery, the ordered quantity of the Detail Line for this shipment is equal to the shipped quantity of this shipment. The
ordered quantity on the total line for this Sales Order Line is not changed. The original ordered quantity is thus still visible.
2. When printing the report "Sales Order Lines" (session tdsls4409m000)
for an overdelivered sales order line with option
"Outstanding Quantity", the
outstanding quantity is
zero.

Solution: 126979
SITUATION IDENTIFIED IN:
"Reminder Advice" (tfacr3110m000)
SITUATION DESCRIPTION:
The message "Invoice belongs to different Customer / Business partner " appears wrongly in the following situations:
1. When an Invalid invoice is entered manually
2. When a valid invoice belonging to different transaction type, other than the one defaulted, is selected through zooming
SOLUTION DESCRIPTION:
Now the wrong message "Invoice belongs to different Customer / Business partner " does not appear.

Solution: 126983
SITUATION IDENTIFIED IN:
"Print Session Information" (ttstpsessinfo)
SITUATION DESCRIPTION:
Session "Print Session Information" (ttstpsessinfo) does not print the runtime path from where form and report are taken.
It only gives the VRC the form and report are picked from.
SOLUTION DESCRIPTION:
The report is modified as follows:
If Runtime info is not set then the session prints as before.
If Runtime info is set then:
· For the Form not only the VRC found via the tools tables but also the path of the dump found on runtime is printed
· For Reports not only the VRC found via the tools tables but also the path of the object found on runtime is printed
For objects the runtime path is shown in general info.
Runtime flag can only be set if the package combination is equal to the current package combination.

Solution: 126986
SITUATION IDENTIFIED IN:
"Print Production-Order Documents" (tisfc0408m000)
SITUATION DESCRIPTION:
Problem 1:
If there are user defaults present in tab "Documents" of session "Print Production-Order Documents" (tisfc0408m000), and if
the session is called from session "Material to Issue for Production Orders" (ticst1501m000), then on selecting tab
"Documents" in session "Print Production-Order Documents", it is found that all the check boxes that were saved as default
are selected instead of selecting only one check box "Material Issue Note".
Problem 2:
When using Letter Landscape
format paper size (US standard), the reports does not fit on the
paper. The paper width is not big enough to print all the characters.
SOLUTION DESCRIPTION:
Problem 1:
If there are user defaults present in tab "Documents" of session "Print Production-Order Documents" (tisfc0408m000), and
if the session is called from session "Material to Issue for Production Orders" (ticst1501m000), then on selecting tab
"Documents" in session "Print Production-Order Documents", system selects only one check box "Material Issue Note".
Problem 2:
The report fits into Letter Landscape format paper size.

Solution: 126989
SITUATION IDENTIFIED IN:
"Compose Loads" (whinh4134m000)
SITUATION DESCRIPTION:
The message was not clear while trying to add a new shipment when the load does not exist in the " Loads "
(whinh4540m000) session.
SOLUTION DESCRIPTION:
The message is now clear and it will be shown when the load does not exist.

Solution: 126992
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When PCS Project is used in a Bilateral Invoicing Transaction, and if the Calculation office of the PCS Project is linked to a
different finance company other than the supplying warehouse, then the "Credit" line of the COGS booking is wrongly booked to the finance
company of the warehouse. It has to be the finance company of the Calculation Office. Also, the Enterprise units are populated wrongly in the Integration Tables.
SOLUTION DESCRIPTION:
Now the COGS Bookings are posted correctly
Solution: 127000
SITUATION IDENTIFIED IN:
"Print Sales Contract Acknowledgements" (tdsls3405m000)
SITUATION DESCRIPTION:
Contract line text is not printed in case contract line applies to all items in price group
SOLUTION DESCRIPTION:
The printing of contract line texts was determined based on the field "Apply Contract for all Items in Price group" in session Sales-Contract Lines (tdsls3101s000).
Contract texts are now printed (when available) for all lines regardless if the contract line applies to all items in the
pricgroup or not.

Solution: 127001
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1. A List item is entered in the Purchase Order Line.
2. No list components are selected.
3. When the user tabs from the session, an error message comes as
++++++++++++++++++++++++++++++++++++++++++
??????????????????????????????????????
++++++++++++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
Now the error message would pop up as
+++++++++++++++++++++++++++++++++++++++++
Component(s) must be selected for the List Item.
++++++++++++++++++++++++++++++++++++++++

Solution: 127008
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4101s3000)
SITUATION DESCRIPTION:
1. There is a Cost item and for this Item the Receipt is made in "Purchase Order Receipts" (tdpur4101s3000).
2. The Quantity Tolerance defined is defined for this item.
3. When the receipt is made, the user is not informed if the received quantity is outside the quantity tolerance as defined
above.
SOLUTION DESCRIPTION:
The Maximum allowed tolerance and the Minimum allowed tolerance are taken in the following order
1. From Item Supplier Information
2. Item Purchase Data.
The Received Quantity is checked with the percentage applied to the order quantity. If it fall above/below the upper/lower
tolerances respectively, the user would prompted the warning message
+++++++++++++++++++++++++++++++++++++++
Total received quantity now exceeds order tolerance.
+++++++++++++++++++++++++++++++++++++++

Solution: 127010
SITUATION IDENTIFIED IN:
"Process Delivered Sales Orders" (tdsls4223m000)
SITUATION DESCRIPTION:
It is not possible to mark 'Delete Cancelled Order Data' separately. Only if 'Delete Order Data' is selected, it is possible to
mark this option.
SOLUTION DESCRIPTION:
The option 'Delete Cancelled Order Data' can be selected irrespective of the selection of 'Delete Order Data' option.
It is now possible to delete cancelled orders alone, without deleting the actual orders.

Solution: 127012
SITUATION IDENTIFIED IN:
"Purchase Order History by Order" (tdpur5505m000)
SITUATION DESCRIPTION:
In German language the order is reading as "Verkaufsauftrag" (Sales Order). But the session is actually for the History of
Purchase Orders
SOLUTION DESCRIPTION:
The Order would be read as 'Auftr' in German Language now. In English, it would read as 'Order No'. Earlier it was 'Order'

Solution: 127026
SITUATION IDENTIFIED IN:
"Transactions Purchase Invoices" (tfacp1120s000)
SITUATION DESCRIPTION:
When entering Purchase Invoice Transactions (session tfacp1120s000) with on the invoice header the Level of Tax
Calculation is on Invoice Header and Tax country/Code is filled, but there is no blank Tax code within the Tax country,
by saving the Lines the error message is shown: "Tax code by country not found", can not save lines.
SOLUTION DESCRIPTION:
When entering Purchase Invoice Transactions (session tfacp1120s000) with on the invoice header the Level of Tax
Calculation is on Invoice Header and Tax country/Code is filled, but there is no blank Tax code within the Tax country, by
saving the Lines there are no error messages.
Checks on vat are not done anymore because when the vat is on header no checks have to be done.

Solution: 127028
SITUATION IDENTIFIED IN:
"Initialize Roll Update Scenario" (cprpd4200m000)
SITUATION DESCRIPTION:
Run "Initialize Roll and Update Scenario" (cprpd4200m000) session will fail
with Fatal Error "cprpddll1015.per.start.date index 0 out of dims [1] 122" in only one situation explained below.
1. The Scenario should be a Rolling Scenario (frequency can be 1 day or 7 days)
2. A Plan Item should have BCM (Bill of Critical Material) with Lead Time offset.
3. Scenario should have plan periods.
4. Run Initialize Scenario. (It goes smooth)
4. Item should have an Item Master Plan with "Production Plan" in first two periods.
5. Run Initialize Scenario again on the next day or after 7 days (Rolling Frequency). Here it fails with Fatal error.
SOLUTION DESCRIPTION:
The solution to this problem is handled in cprpddll1015. Don't send zero back
to calling DLL in case the offset.start date falls below the scenario start.
Instead it should send 1st period. The same with the last period also.
No Fatal error is coming now

Solution: 127033
SITUATION IDENTIFIED IN:
"Process transaction" (tpppc4802m000)
SITUATION DESCRIPTION:
Projects gets closed even when transaction in later period is present.
SOLUTION DESCRIPTION:
Porting of solution 115867 solves the problem.

Solution: 127044
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" (whinh4201m000)
SITUATION DESCRIPTION:
It is possible to Generate Outbound for the List Item, even when the stock of the components is less than the number of
quantities required for assembling a main item.(i.e. even when the component is not available in the ratio to assemble main
item).
SOLUTION DESCRIPTION:
It would no more be possible to generate outbound for a List item, for which the components are not available in the required
ratio.

Solution: 127050
SITUATION IDENTIFIED IN:
"Calculate Demand Forecast by Item" (whina2202m000)
SITUATION DESCRIPTION:
Forecasting is calculated incorrectly if the Forecasting Method used is "Previous Year Calculation".
SOLUTION DESCRIPTION:
Now, forecasting for "Previous Year Calculation" is done correctly taking into consideration, the Number of Periods
Forward & Number of Periods Backward as defined in Forecast Methods.

Solution: 127054
SITUATION IDENTIFIED IN:
"ATP - Handling" (tdsls4899m000)
SITUATION DESCRIPTION:
Several problems occured all related to the component and capacity check together:
Problem 1:
When doing component and capacity check when the item has no stock the capacity is wrong in the first period when the
component gets available, because cumulative capacity is taken and this than is higher than the capacity available. So this
has been corrected so only the capacity is displayed which is available.
Problem 2:
When there is a change in period length for the plan periods, the cumulative capacity is used to calculate the capacity, but this is comparing for instance days
by weeks, because of the BCC LTO, so there has been done a correction for those periods that have a period length switch.
SOLUTION DESCRIPTION:
When Components CTP and Capacity CTP both checked the correct result is given for the available quantity when component ctp becomes
available while capacity already was available. Also the availability is adjusted when the period length is changing for the plan
periods and a BCC LTO is set.

Solution: 127060
SITUATION IDENTIFIED IN:
"ECO lines" (tiedm3120s000)
SITUATION DESCRIPTION:
While maintaining "ECO lines" (tiedm2130m000), the field "Replace Type" defaults to "* (Multiplication)" even if ECO
Activity Type is "ADD" or "Delete".
SOLUTION DESCRIPTION:
While maintaining "ECO lines" (tiedm2130m000), the field "Replace Type" will not be visible when the ECO Activity Type
is "ADD" or "Delete". This is because the Replace Type is needed only for Activity Type Replace.

Solution: 127061
SITUATION IDENTIFIED IN:
"Hours accounting transactions" (tphrs1100s000)
SITUATION DESCRIPTION:
While entering a record in a closed fiscal period in the hours accounting session an error message is displayed saying the
fiscal period is not open in baan finance. Instead the system should give a question asking "Fiscal period is not open, do u
want to post it next open period" and then let the user to decide for next step.
SOLUTION DESCRIPTION:
The solution is now build this way : When a corresponding fiscal period is closed then a message is displayed saying "fiscal
period is not open in baan finance, transaction will be posted to next open period" and the cost line genarated will hve the
next open period as the fiscal period.

Solution: 127062
SITUATION IDENTIFIED IN:
"Tool numbers by Tool type" (titrp0502m000)
SITUATION DESCRIPTION:
The function group copy through 'Duplicate' option in 'GROUP' menu is not copying the records as expected. An error
message " 0 records copied; records skipped" will pop up and the copy function fails.
SOLUTION DESCRIPTION:
The 'DUPLICATE' option is disabled in the "GROUP" menu of the session "Tool numbers by Tool type" (titrp0502m000). It is
not possible to do a group copy of the selected records, as reference exists between the tool number and tool type, hence the
option is disabled.

Solution: 127063
SITUATION IDENTIFIED IN:
"Select Invoices for Reminders" (tfacr3210m000)
SITUATION DESCRIPTION:
Invoices are not selected if a business partner has only the "Invoice To" and the "Pay By" role. And "Sold To" BP is not
defined.
SOLUTION DESCRIPTION:
Invoices will be selected for Reminder even if "Sold To" BP is not defined.

Solution: 127070
SITUATION IDENTIFIED IN:
"Compose Loads" (whinh4134m000)
SITUATION DESCRIPTION:
1. Select the 'New Group' button of the session "Compose Loads" (whinh4134m000)
2. Insert a Load that has been already confirmed.
3. Now, use the 'Add Shipment' option in the Specific menu.
4. The user is able to add a shipment to a load that has been already confirmed.
5. This means that the Load has moved out of the warehouse and it should not be possible to add a shipment to this Load.
SOLUTION DESCRIPTION:
Now when the user is trying to link a Shipment to an already confirmed Load, the system would give an error message
saying
+++++++++++++++++++++++++++++++++
Load XXXX has already been confirmed.
++++++++++++++++++++++++++++++++++

Solution: 127073
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b
126678-2, 127082
Defects solved in 71a
126678-2, 127082, 208667
Descriptions:
- Defect 126678-2 AFS fix 126678 caused the afs call for last set to fail.
- Defect 127082 Refresh problem in switch form during modify job parameters
- Defect 208667 When zoom returns a blank value, the previous value was being reset
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 127077
SITUATION IDENTIFIED IN:
"Direct Debit Advice and Payment Advice" (tfcmg4120s000 and tfcmg1120s000)
SITUATION DESCRIPTION:
If a payment/direct debit advice is created in the invoice currency and the currency rate is changed, then the system doesn't
take into account the new currency in the recalculation of the discount.
SOLUTION DESCRIPTION:
Now the discount is recalculated with the already changed rate.

Solution: 127085
SITUATION IDENTIFIED IN:
"Sales Invoice Receipts" (tfacr2523m000)
SITUATION DESCRIPTION:
Wrong Description for a Business Partner is been displayed. It displays the name of a Business Partner form the Address
table (tccom130) instead of Business Partner table (tccom100).
SOLUTION DESCRIPTION:
Correct Description for a Business Partner is displayed.

Solution: 127097
SITUATION IDENTIFIED IN:
"Print Sales Order Lines" (tdsls4409m000)
SITUATION DESCRIPTION:
Outstanding Order amount for delivered sales order line is printed incorrect.
In case an order line for a cost item (no release to warehousing) with an order quantity of 0 is released to invoicing it
should not give an outstanding amount.
SOLUTION DESCRIPTION:
During the "Release to Invoicing" (tdsls4501m130) a delivery date is added to the order line and therefore the delivery for
the item is done. Outstanding amount (what is yet to delivered) is now 0.

Solution: 127105
SITUATION IDENTIFIED IN:
"Enter Amounts for Assignment" (tfcmg2107s000)
SITUATION DESCRIPTION:
When the unallocated receipt (or advance receipt) amount is less than the sales invoice one, after 'Automatic Assignment'
the received, remaining and balance amounts are wrongly displayed.
SOLUTION DESCRIPTION:
The received, remaining and balance amounts are correctly displayed after 'Automatic' assignment.

Solution: 127106
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
An orderline is created for Direct Delivery. If now 2 receipts are maintained for that orderline and one invoice is matched to
the first receipt with a price difference and if afterwards a second invoice is matched to the second receipt then it appears
that the mapping for the integration transactions originating from the second invoice is not correct.
SOLUTION DESCRIPTION:
Before modifications to the Direct Delivery process were done, no 2 integration records could exist for both Purchase - Direct Delivery and Purchase - General
Costs. Now they can exist together, so the logic to determine the transaction origin and financial transaction of the receipt had to be changed.

Solution: 127107
SITUATION IDENTIFIED IN:
"Fill dimensions in Interim table" (tfcor1241m000)
"Accept values of GRNI Reconciliation" (tfacp1535m000)
SITUATION DESCRIPTION:
- Only for Unaccepted values the dimensions were filled.
- Print option on session tfacp1535m000 was active but not working
SOLUTION DESCRIPTION:
- For all entries the dimensions are filled
- Print option is inactive now on session tfacp1535m000

Solution: 127112
SITUATION IDENTIFIED IN:
"Word Count for PMC Service Packs" (ttcor6230m000)
SITUATION DESCRIPTION:
A auxiliary session has been created to do the wordcount of service packs that are being created by means of PMC.
This session must be delivered.
SOLUTION DESCRIPTION:
The wordcount session has been included in this solution.

Solution: 127113
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
1. The "Response Time" code (tsclm100.crtc on the "Details" tab) is only obtained when inserting a new Call and when saving
the Call. This means that during the process of filling in the Call details it is not possible to see which Response time Code
is current.
2. The description of the Response Time code is not refreshed when saving the Call. Only after a refresh the correct
description is displayed.
3. When copying a Call the Call Group is not copied.
4. When filling in the Call starting with the Serial Number the correct Object,
Configuration and Sold-to Business Partner are retrieved but the serial number field is cleared.
5. When creating a Call for an Object, which is not derived from an Item, the Item field (tsclm100.item) is filled with the previous value and cannot be changed anymore because the field is disabled.
SOLUTION DESCRIPTION:
1. The Response Time code is retrieved according to the following hierarchy:
A- the Contract
B- the Sold-to Business Partner
C- the Call parameters
Initially the Response Time code is retrieved from the Call parameters but when the Business Partner and/or Contract are
getting defined during the filling of the Call, the program will immediately retrieve the correct Response Time code
according to above mentioned hierarchy.
2. As soon as the Response Time code changes the description also changes.
3. When copying a Call the Call Group is also copied.
4. The Serial Number will remain after filling it.
5. When creating a Call for an Object, which is not derived from an Item, the
Item field is not filled.

Solution: 127118
SITUATION IDENTIFIED IN:
"Hours Accounting History" (tssoc8520m000)
SITUATION DESCRIPTION:
1. There are many records in the session "Hours Accounting History" (tssoc8520m000).
2. The user goes to the second form and then scrolls down.
3. Then again if he navigates to the first form, the data corresponding to the previous time is displayed and not the same
data that was displayed in the second form.
SOLUTION DESCRIPTION:
Now, the data is consistent in all the three forms of the session "Hours Accounting History" (tssoc8520m000), irrespective
of navigation between the forms.

Solution: 127119
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (tfacr2421m000)
SITUATION DESCRIPTION:
When printing sale invoices with "Print Text" set to "yes", empty text boxes appear on the report for few invoices.
SOLUTION DESCRIPTION:
Empty text boxes do not appear on the report.

Solution: 127121
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When the sales order is having an order type of return and collect and for this order, if the original sales order is copied by
selecting the order from the header session, then in the Sales order lines, Sales Order Quantity field cannot be modified as it
was disabled.
SOLUTION DESCRIPTION:
Now, till the Sales return/ collect order is processed, the Sales Order Quantity field will be enabled for the user to modify.

Solution: 127128
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Warehouse and Item" (whina1210m000)
SITUATION DESCRIPTION:
This situation applies if the valuation method is FIFO (First In First Out).
The inventory valuation report gives incorrect output when:
- a part of the received quantity for a purchase order is rejected , and
- preceding inventory receipt transactions exist which have not been consumed.
The rejected part is included in the inventory value, while previous (not consumed) receipts are considered to be consumed.
A similar situation occurs in case a receipt is done for which the receipt date is changed into a date in the past, so that this
receipt is registered before other consumed receipts.
SOLUTION DESCRIPTION:
These situations are corrected. The actual consumption dates are taken into account and the correct values are reported

Solution: 127129
SITUATION IDENTIFIED IN:
"Maintain Activity Budgets" (tpptc2110s000)
SITUATION DESCRIPTION:
When we try to customize a revision controlled item by clicking the "make customized" button, the system copies the standard
structure to customized Item without the relevant engineering revisions. This is not correct since the relevant engineering
revisions also have to be copied.
SOLUTION DESCRIPTION:
The above problem is corrected and now if an item is customized, all the relevant engineering revisions will also be copied.

Solution: 127134
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Tax is calculated for an exempt customer / tax authority.
SOLUTION DESCRIPTION:
Tax won't be calculated for an exempt customer / tax authority now.

Solution: 127136
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When an unallocated receipt is linked to a sales credit note using the option "Assign Automatic", balance of unallocated
receipt is zero instead of sales credit note.
SOLUTION DESCRIPTION:
Earlier, balance of sales credit note is updated instead of unallocated receipt while using "Assign Automatic" option.
Now, while linking an unallocated receipt to the sales credit note, balance of sales credit note is made zero, incrementing the
unallocated receipt.

Solution: 127143
SITUATION IDENTIFIED IN:
"Remove Fully Paid Sale Invoices" (tfacr2260m000)
SITUATION DESCRIPTION:
Failure to remove few fully paid Sale Invoices.
SOLUTION DESCRIPTION:
Able to remove fully paid Sale Invoices.

Solution: 127148
SITUATION IDENTIFIED IN:
"Pay to business partner 1099 details" (tccom4126s000)
SITUATION DESCRIPTION:
From the Business Partners session select a business partner with the 'Pay to Business partners role' and then choose the
button '1099-Misc' to see the "Pay to business partner 1099 details" (tccom4126s000) session. If there is no record
information for the existing customer and the customer selects 'Delete' button, then system offers to delete the next available
record.
SOLUTION DESCRIPTION:
If there is no record available for '"Pay to business partner 1099 details" , then the 'Delete' button is disabled.

Solution: 127149
SITUATION IDENTIFIED IN:
"Generate EDI Messages" (ecedi7201m000)
SITUATION DESCRIPTION:
Generate EDI Messages, session ecedi7201m000, is running slow.
This caused for about 20% by collecting the Business Partner information.
If this part of the software is designed for a better performance, this will contribute positively to the overall performance.
SOLUTION DESCRIPTION:
The Business Partner data will now be faster collected.

Solution: 127150
SITUATION IDENTIFIED IN:
"Delete Change Elements" (tppss2200m000)
SITUATION DESCRIPTION:
While trying to delete Charge Elements system shows an error report saying that "Reference exists so the Charge Element
can not be deleted "even when the budget lines for that Charge Element are deleted.
SOLUTION DESCRIPTION:
The above problem is solved. Now the system allows the user to delete the Charge Elements without any problems.

Solution: 127151
SITUATION IDENTIFIED IN:
"Release to warehousing (batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
A sales order line with a cost item with quantity =0 is not transferred to the warehouse by session Release to Warehousing
(batch).
SOLUTION DESCRIPTION:
Functionnality for Cost and Service Item is slightly different than for a normal Item. Now, in case of Cost or Service Item,
Sales Order Line will be transfer to warehouse.
Solution: 127161
SITUATION IDENTIFIED IN:
"Extension" (tpptc0110m000)
SITUATION DESCRIPTION:
Having an extension with Extension Type 'Variations', if the contract amount is bigger than 0, it's not possible to set the
status to Final directly becasue an error message pops up saying that 'the extension hasn't been invoiced. Document number
must be defined to finalize'. This is right. Now the extension is invoiced and the Document number is filled in the
extension. When trying to set the status to Final now the following error message pops up 'Not allowed. Invoice data already
present for the extension'.
Moreover if the contract amount is bigger than 0 the status can be set to Final directly
SOLUTION DESCRIPTION:
On the contrary to the situation description If extension is of type - variation and invoicing method is 'Contract amount' then the extension can be
invoiced only once and When we try to make the status from actual to final system giving the error message "the extension hasn't been invoiced.
Document number must be defined to finalize" is wrong. This change of status should be allowed. While when the user changes from invoicing
allowed to final system giving the message ''Not allowed. Invoice data already present for the extension' is right since here decreasing the status is not
possible and not correct also functionally.

Solution: 127166
SITUATION IDENTIFIED IN:
"Budgeted Projects Cost" (tpptc3801m000)
SITUATION DESCRIPTION:
The Label Project Amount in the session Budget Cost Analysis Reports is confusing (most of the customers assume it as
Contract Amount) so it has to be changed.
SOLUTION DESCRIPTION:
The above problem is solved.
The Label in the session Budget Cost Analysis is changed from Project Amount to Budget Amount.

Solution: 127169
SITUATION IDENTIFIED IN:
"Print Where-used Lots" (whltc3400m000)
"Print Origin by Lot" (whltc3401m000)
"Print Origin by Order" (whltc3402m000)
SITUATION DESCRIPTION:
Session: "Print Where-used Lots" (whltc3400m000)
* Same record is printed more than once.
* When 'Last level report' is printed, intermediate level data were also printed.
Session: "Print Origin by Lot" (whltc3401m000)
* 'All level report' does not print complete data. Some records in the last level are not printed.
* 'Last level report' does not print complete data. Some records in the last level are not printed.
* When 'Last level report' is printed, intermediate level data were also printed.
* Same record is printed more than once.
Session: "Print Origin by Order" (whltc3402m000)
* Same record is printed more than once.
SOLUTION DESCRIPTION:
Session: "Print Where-used Lots" (whltc3400m000)
* Printing of same record more than once is prevented in the case of 'Last level report'.
* Now, when last level report is printed, intermediate level data are NOT printed. Only last level data is printed.
Session: "Print Origin by Lot" (whltc3401m000)
* 'All level report' now prints complete data.
* 'Last level report' now prints complete data.
* Now, intermediate level records are not printed, when 'Last level report' is printed.
* Printing of same record more than once is prevented in the case of 'Last level report'.
Session: "Print Origin by Order" (whltc3402m000)
* Printing of same record more than once is prevented in the case of 'Last level report'.

Solution: 127171
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
It is possible to plan or release a service order/activity which has no duration specified.
SOLUTION DESCRIPTION:
When a service order/activity is planned using Global SRP, a warning message is given which indicates that the service order
or one of its activities has no duration.Similarly,releasing an order/activity using the Release button or Baan Service
Scheduler/Graphical Planning Board also gives a warning message.It is possible to continue or stop the release process after
seeing the message.
Detail SRP does not release a service order/activity if it has no duration.

Solution: 127179
SITUATION IDENTIFIED IN:
"Print Cost-Plus Transactions To Be Invoiced" (tppin4457m000)
SITUATION DESCRIPTION:
When a cost plus transaction is transferred to SLI, but not yet invoiced (there is no invoice document linked to it) it's getting
printed on the report "cost plus transactions to be invoiced by activity", when the selection is on "Invoiced".
This is wrong. Not Invoiced lines should not get printed with this option.
SOLUTION DESCRIPTION:
The Print option is now corrected & now with the option "Invoiced" on Invoiced Transaction, only transactions that are
transferred to SLI as well as posted to finance will be printed.

Solution: 127181
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Checklist" (tfacp1438m000)
SITUATION DESCRIPTION:
When running report "Print Receivable Invoices Checklist" (tfacp1438m000) for the full range, Error 506 (table tfgld005000
not present) comes and the session is aborted.
SOLUTION DESCRIPTION:
The error was because in some cases in table "Interim table receivable invoices" (tfacp135), for Manual Orders (tfacp135.orno
= 0 and tfacp135.pono = 20), the field tfacp135.srno should be equal to zero. In cases where the field was not zero, the
record was not getting processed correctly.
This has been taken care now.

Solution: 127182
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice-to Business Partner" (tfacr2420m000)
SITUATION DESCRIPTION:
When a Receipt transaction is linked to a Zero Invoice, then there is a difference between the aging report and the Open
entries.
SOLUTION DESCRIPTION:
Now the Aging report and the Open entries report are correct.

Solution: 127185
SITUATION IDENTIFIED IN:
"Print Fixed Assets - General Ledger Reconciliation" (tffas0442m000)
SITUATION DESCRIPTION:
A new report is required to reconcile the FAS (Fixed Assets) transactions that have been posted to GLD (General Ledger).
SOLUTION DESCRIPTION:
The report "Print Fixed Assets - General Ledger Reconciliation" (tffas0442m000) has been created. It is placed under the
menu.
BAAN Finance / Fixed Assets / Depreciation Transactions.
The processing logic of the report is present in the Help Text.

Solution: 127190
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
In the German language (language 3), the session 'Bank Transactions' (tfcmg2100s000) contains incorrect translations for
'Business Partner'. On the form the phrase 'Übergeordn Kreditor' is used, which is wrong. Another incorrect item is the name of
the first tab. It is called 'Barzahlungsdetails', although it rather reflects the details of the bank than the cash transactions.
SOLUTION DESCRIPTION:
The label 'Übergeordn Kreditor' in the German languge (language 3) has been corrected into 'Handelspartner' and the name of the first tab
is now 'Zahlungsdetails' instead of 'Barzahlungsdetails'.

Solution: 127199
SITUATION IDENTIFIED IN:
"Remove Posted Direct Debit Batches" (tfcmg4259m000)
SITUATION DESCRIPTION:
Records in the table " Maintain Direct Debit Documents" are not getting deleted when running the session "Remove Posted
Direct Debit Batches".
SOLUTION DESCRIPTION:
Records in the table " Maintain Direct Debit Documents" are now getting deleted when running the session "Remove Posted
Direct Debit Batches".

Solution: 127200
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
It is not possible to re-simulate orders in Enterprise Planning for changed orders, from "Sales-Order
Lines"(tdsls4501m000).
SOLUTION DESCRIPTION:
An option has been added under 'Specific' in the Menu bar, 'Simulate Orders in Enterprise Planning'. With this it would be
possible to re-simulate the orders in Enterprise Planning, any number of times.
** Note: When this option is clicked all the Sales Order Lines for the Sales Order are taken (not just the selected lines), and
are passed for simulating in Enterprise Planning.

Solution: 127203
SITUATION IDENTIFIED IN:
"Approve Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When a project related purchase order is matched and approved with an Invoice, and there is is currency rate difference
between the time of Receipt and Approval, the currency difference is not posted as a Purchase price variance.
SOLUTION DESCRIPTION:
Now, when a project related order line is matched totally and all other invoices linked with the order have been approved,
the difference in home currency between the Receipt and Approval, coming out of Currency rate change is posted as
Purchase price variance.
This posting will be done directly by the Approval process, to the Integration Transactions. The transaction will have the
transaction Origin : Project cost and Commitment and Financial Transaction : Purchase Price Variance.

Solution: 127204
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. The receipt procedure of the Inbound Order does not have Generate Inbound and Put away Inbound as activities, meaning
that the inbound would be done automatically when the receipt is confirmed.
2. There is a lot-controlled item.
3. Many unit of this item is entered in the Purchase Order Lines.
4. It is released to Warehousing and the order is linked to a Receipt.
5. While confirming the linked receipt, it takes lot of time.
SOLUTION DESCRIPTION:
The changes have been made in such a way that time taken for the complete process of confirming the receipt is reduced
considerably. Even in cases where the Generate Inbound is a separate activity, the changes will be applicable and the
performance of the advice generation.

Solution: 127206
SITUATION IDENTIFIED IN:
"Print Fixed Assets - General Ledger Reconciliation" (tffas0442m000)
SITUATION DESCRIPTION:
When the report "Print Fixed Assets - General Ledger Reconciliation" (tffas0442m000) was printed, for a disposed asset,
where the disposed year <> acquisition year, then the Profit/Loss column was printing wrong values.
The session name was not present in other languages (1,3,4).
SOLUTION DESCRIPTION:
The report is printing correct values now. Also the session name is present in various languages.

Solution: 127207
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Simulate Order does not take into account the operation linked to the BOM line of the phantom item when computing the
requirement date.
SOLUTION DESCRIPTION:
The operation linked to the BOM line of the phantom will be taken into account during the planning run.

Solution: 127209
SITUATION IDENTIFIED IN:
"BOI Builder for OW2.3" (ccboi)
SITUATION DESCRIPTION:
BaanERP5.0b had a BOI Builder included that is based on the previous middleware technology
BCBE. No BOI Builder was available for the new middleware technology iBaan Open World.
SOLUTION DESCRIPTION:
The current solution contains the BOI Builder for BaanERP5.0b based on the OpenWorld2.3 version.

Solution: 127210
SITUATION IDENTIFIED IN:
"Print Control Account Check List" (tfacr2415m000)
SITUATION DESCRIPTION:
The column Difference not correct in case of a Credit Note linked to an Anticipated receipt.
SOLUTION DESCRIPTION:
The column Difference is displayed correctly in case of a Credit Note linked to an Anticipated receipt.

Solution: 127214
SITUATION IDENTIFIED IN:
"BOI Builder for OW2.3" (ccboi)
SITUATION DESCRIPTION:
BaanERP5.0b had a BOI Builder included that is based on the previous middleware technology
BCBE. No BOI Builder was available for the new middleware technology iBaan Open World.
SOLUTION DESCRIPTION:
The current solution contains the Common Components for BOI Builder for BaanERP5.0b based on the OpenWorld2.3
version.

Solution: 127216
SITUATION IDENTIFIED IN:
"Delete Quotations" (tdsls1410m000)
SITUATION DESCRIPTION:
Total of Quotations amount is doubled in case option Text is checked in session "Delete Quotations" (tdsls1410m000). This
happens when report "Print and Delete Quotations (Detailed)" is used.
SOLUTION DESCRIPTION:
The condition for accumulating the lines was incorrect.
In case texts should be printed each line was added twice to the total

Solution: 127218
SITUATION IDENTIFIED IN:
"Warehousing Inbound Lines" (whinh2510m000)
SITUATION DESCRIPTION:
Three or more lots are issued to production. Then 2 lots are send back in session "Issue Materials for Production Orders"
(ticst0501m000). Now the system generates too much inbound lines, because the already created receipt lines are not taken
into account.
SOLUTION DESCRIPTION:
When inbound lines are created, the quantity of materials on these lines is calculated. Only for the difference a new inbound
line is created, if needed.

Solution: 127224
SITUATION IDENTIFIED IN:
"Calculate Sales Prices by Item" (ticpr2250m000)
SITUATION DESCRIPTION:
While calculating the sales price of an item, the system returns fatal error "ERROR 205 (Out of Range)". This error appears
when the calculated sales price is negative.
SOLUTION DESCRIPTION:
The sales price can not be negative. If the calculated sales price is negative, then the system will make the sales price as
zero.

Solution: 127225
SITUATION IDENTIFIED IN:
"Elements" (tpptc1500m000)
SITUATION DESCRIPTION:
While trying to delete Element the system deletes the relevant Budget Lines (if it exists) but not the Control Data (if it
exists) for that particular Element .This is wrong the system should also delete Control Data along with the Budget Lines.
SOLUTION DESCRIPTION:
The above problem is solved.Now the system deletes Control Data along with the Budget Lines for that Element .

Solution: 127226
SITUATION IDENTIFIED IN:
"Installments" (tppin4451m000)
SITUATION DESCRIPTION:
Print installment's report is not printing records in the selection range.
SOLUTION DESCRIPTION:
The checks on the selection fields is now done in a proper way and so all the records of the selection range are now printed.

Solution: 127227
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
The description of the Ledger Account is not cleared when the ledger account field is cleared.
SOLUTION DESCRIPTION:
Now, the description of the Ledger Account is cleared, when the existing Ledger Account is cleared.

Solution: 127236
SITUATION IDENTIFIED IN:
"Print Purchase Invoices" (tfacp2421m000)
SITUATION DESCRIPTION:
When printing purchase invoices with "Print Text" set to "yes", empty text boxes appear on the report for few invoices.
SOLUTION DESCRIPTION:
Empty text boxes do not appear on the report.

Solution: 127241
SITUATION IDENTIFIED IN:
"Import" (ttiex1288m000)
SITUATION DESCRIPTION:
Questions are not imported. Specially in dumps which contains domains and questions. If a dump only contains questions then
it is correctly imported.
SOLUTION DESCRIPTION:
Questions are now correctly imported.

Solution: 127242
SITUATION IDENTIFIED IN:
"Compose/Print/post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Gross amount and tax amount are not correct on sales invoice if tax code of type "Gross" is used.
This is applicable only for Manual Sales.
SOLUTION DESCRIPTION:
Now the tax amounts are calculated and printed correctly.

Solution: 127250
SITUATION IDENTIFIED IN:
"Print Purchase Invoices" (tfacp2421m000)
SITUATION DESCRIPTION:
When running session "Print Purchase Invoices" tfacp2421m000 with the field "Invoices to be Printed" set to "Approved
Invoices" the report prints also the purchase credit notes which has the status "Registered".
SOLUTION DESCRIPTION:
When running session "Print Purchase Invoices" tfacp2421m000 with the field "Invoices to be Printed" set to "Approved
Invoices" the report prints only the purchase credit notes which has the status "Approved".

Solution: 127251
SITUATION IDENTIFIED IN:
"Print Advance Payments Requests" (tppin4410m000)
SITUATION DESCRIPTION:
Some of the Print options of "Invoiced Transaction" and "To Be Invoiced" are not working correctly.
Some options are giving inconsistent results with their selected options.
SOLUTION DESCRIPTION:
Selection criteria have been corrected and now all the Print Option combinations will give correct results.

Solution: 127254
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Descriptions:
- Defect 126202 AFS Batch update does not work for form 3 sessions.
- Defect 127264 AFS Using the optional parameter of functions of the created dll results in null pointer error
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 127265
SITUATION IDENTIFIED IN:
"Print Claims" (tdpur4420m000)
SITUATION DESCRIPTION:
1. A subcontracting purchase order is generated from the sub contracting operation of a production order.
2. While receiving the subcontracting item of this purchase order, the received quantity is less than the packing slip
quantity.
3. But it is not possible to print the claims even if the activity "Print Claims" (tdpur4420m000) is part of the order step.
SOLUTION DESCRIPTION:
It is possible to print the claim for the subcontracting item when the packing slip quantity is greater than the received
quantity.

Solution: 127266
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
"Purchase- Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
In Purchase Order lines, for cost or service items, while user is modifying 'Ordered Quantity' field to set units, the system
does not return correct units.
SOLUTION DESCRIPTION:
Now, System zooms to the correct session from the Ordered Quantity field in Purchase Order lines and also returns correct
unit.

Solution: 127267
SITUATION IDENTIFIED IN:
"Print Installments" (tppin4451m000)
SITUATION DESCRIPTION:
Transactions transferred to SLI or posted to finance are not printed with options "Invoiced Transaction" as "Both" & "To be
Invoiced" as "To be Invoiced". Only Not Invoiced Transactions are printed.
SOLUTION DESCRIPTION:
Selection criteria were not working correctly for some of the option combinations of "Invoiced Transaction" and "To be
invoiced" fields. This is corrected & now all the option combinations are working correctly.

Solution: 127272
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
The price of an item is wrongly rounded in the Purchase Requisition Lines. It is rounded to two digits after decimal point,
even if the price has been defined with 4 digits after the decimal point.
SOLUTION DESCRIPTION:
Now the price is rounded according to the rounding factor of the Currency of the requisition header.

Solution: 127273
SITUATION IDENTIFIED IN:
"Copy Routing" (tirou2201m000)
SITUATION DESCRIPTION:
When a tool is blocked temporarily for maintenance, system stops copying the routing operations in the session Copy
Routing ("tirou2201m000")
SOLUTION DESCRIPTION:
When a tool is blocked temporarily for maintenance, system will allow copying the routing operations along with the tool.
But the system will not allow to insert a blocked tool through the session Tooling per operation ("tirou1510m000").

Solution: 127274
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
In Sales Order Header, it is not possible to change the tax code country in the 'Invoicing' tab from the default to any other
country.
SOLUTION DESCRIPTION:
It is now possible to change the tax code country, to other countries, apart from the default one in Sales Order Header.

Solution: 127275
SITUATION IDENTIFIED IN:
"Print Control Account checklist" (tfacr2415m000)
SITUATION DESCRIPTION:
In "Print Control Account Checklist" and select " Print differences" only, Business Partners with no differences are printed.
SOLUTION DESCRIPTION:
In "Print Control Account Checklist" and select "Print differences" only, It prints " Total for Business Partner Group" and
"Total for Ledger Account " for the Business Partners with some differences.

Solution: 127278
SITUATION IDENTIFIED IN:
"Generate Cycle Counting Orders" (whinh5200m000)
SITUATION DESCRIPTION:
1. There are 3 stock points in a particular Warehouse.
2. A cycle Counting Order is created for these stock points and the counted data are processed.
3. For the third stock pint the quantity is made as 0 with an Adjustment Order.
4. Now a new Cycle Counting Order is generated with the Warehouse mentioned above with Maximum number of Lines per
order kept as two.
5. The system gives the following fatal error and it is not possible to proceed further.
++++++++++++++++++++++++
Fatal error 206 (record not locked)
+++++++++++++++++++++++++
SOLUTION DESCRIPTION:
The above-mentioned fatal error doesn't appear now, while creating the Cycle Counting Order Line for a non-existing stock
point.

Solution: 127286
SITUATION IDENTIFIED IN:
"Inventory Variances" (whina1516m000)
SITUATION DESCRIPTION:
1. The session "Inventory Variances" (whina1516m000) is opened.
2. Now, the Inventory Variance is processed from the session "Process Inventory Variances" (whina1200m000). All these
time, the session "Inventory Variances" (whina1516m000) remains open.
3. Now, the 'Toggle consumption' option in the specific menu is not disabled for this processed variance. This happens even
if the user does 'Refresh' the session manually.
SOLUTION DESCRIPTION:
1. The 'Toggle consumption' option in the specific menu would be disabled if the particular variance record were processed.
2. If more than one record is marked, then the 'Toggle consumption' option would be enabled/disabled based on the values of
the last record that is marked. While selecting the 'Toggle consumption' option, only the correct records would be processed.

Solution: 127298
SITUATION IDENTIFIED IN:
"Production orders" (tisfc0101s000)
SITUATION DESCRIPTION:
While generating a Production order for an Item having signal code, the signal code will not pop up. But signal code will
pop up while generating sales and purchase orders for the same Item.
SOLUTION DESCRIPTION:
Always the signal code will pop up while generating Production order for a signal code Item. Also in "Material to Issue for
Production order", when signal code Items are inserted system pops up the signal code.

Solution: 127331
SITUATION IDENTIFIED IN:
"History Service Orders Header" (tssoc8551s000)
SITUATION DESCRIPTION:
BW message: 1 : process 11 - Warning : Overflow: format='0' value='1' (() in object ottadv3101) arises for the last
form (tssoc8551s0006) of session tssoc8551s000 "History Service-Orders Header" in the following situations:
- When opening session ttadv3501s000 "Form Fields" for field tssoc850.htim (History Time) or changing from one tab to
another in that session.
- When compiling the form in session "Forms" ttadv3500m000.
- When using session ttadv5214m000 "Create Runtime Data Dictionary (Forms and Menus)" for the form.
SOLUTION DESCRIPTION:
The format for displaying field History Time (tssoc850.htim) was defined as empty, causing the message to display. Now it
is defined to be displayed in a format According to Domain.

Solution: 127339
SITUATION IDENTIFIED IN:
"Payment Advices" (tfcmg1120s000)
SITUATION DESCRIPTION:
Within session Payment Advices (tfcmg1501m000) no check is available on existence of Posting Data of Stand-alone
payments. Since session Posting Data (tfcmg1515s000) cannot be accessed directly from session Payment Advices
(tfcmg1120s000) entering posting data can easily be forgotten.
SOLUTION DESCRIPTION:
When closing session 'Payment Advice' (tfcmg1501m000) warning message 'Posting data for Stand-alone
Payment not found' will be given in case no Posting Data has been defined for the Stand-alone payment within the payment advice.

Solution: 127340
SITUATION IDENTIFIED IN:
"Maintain Item Data" (tiitm0101m000)
"General Item Data" (tcibd0101s000)
SITUATION DESCRIPTION:
System takes long time to display the Engineering Revisions in the session "Maintain Item Data" (tiitm0101m000).
SOLUTION DESCRIPTION:
The performance of the session "Maintain Item Data" while displaying the revision is improved.

Solution: 127343
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
SITUATION DESCRIPTION:
When calling 'Sales Orders' session from an external application using API or Application Function Server(AFS), the
session pops up on the screen instead of running in the background.
SOLUTION DESCRIPTION:
Now the problem is solved. If the user calls the session "Sales Orders (tdsls4500m000)" from an external application using
API or Application Function Server (AFS), the session will not pop-up on the screen any more and will run only in the
background.

Solution: 127349
SITUATION IDENTIFIED IN:
"Options by Integration elements" (tfgld4121m000)
SITUATION DESCRIPTION:
when we are trying to change the method field from by elements to by ranges, fatal error was occurring and elements were
not copied to ranges.
SOLUTION DESCRIPTION:
Now the fatal error is not occurring and elements are copied to ranges.

Solution: 127358
SITUATION IDENTIFIED IN:
"Print Project Control" (tpppc4420m000)
SITUATION DESCRIPTION:
When Printing Project Control for Project/Activity selection, the printed WIP values are different from the actual WIP.
SOLUTION DESCRIPTION:
The above problem is now corrected and now correct WIP values will be printed.

Solution: 127364
SITUATION IDENTIFIED IN:
"Generate Self Billed invoices" (tfacp2290m000)
SITUATION DESCRIPTION:
If in the common parameters "Destination Sales Tax" is set to applicable and the user processes a selfbilled order in session
tfacp2290m000 then whenever the debit receipt account is mapped to enterprise unit and the receipt integration transaction is
not yet posted, the user receives the error message that the debit expense account could not be determined.
SOLUTION DESCRIPTION:
Whenever an integration transaction is posted the ledger account and dimensions are determined by the posting process and they can be used
immediately. If however the receipt integration transaction is not yet posted, the program tries to find the debit ledger account from the mapping
scheme. The user is able to map to Enterprise Unit, Department and Warehouse. It appears that for the debit mapping this is filled with the enterprise
unit of the warehouse and not with the enterprise unit of the purchase office. This same logic is now also used, so the enterprise unit of the warehouse
is used to search the mapping scheme.

Solution: 127372
SITUATION IDENTIFIED IN:
"Print Customer wise Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
When the period for the invoice and the receipt are different then the Aging report is printed wrongly
SOLUTION DESCRIPTION:
Now the Aging Analysis report is printed correctly even when the periods for the invoice and the receipt are different

Solution: 127373
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
A)
1. There is an item with the purchase unit measured in length.
2. This item is entered in the purchase order lines, the 'Inspection' flag is not defaulted to the order line, when the
dimensions are entered.
B)
1. There is high conversion factor between the purchase unit and the price unit of the item.
2. A purchase order line is created with that item.
3. The order line amount of the Purchase Order Line and the amount shown in the session "Integration Transactions by
Project/Order" (tfgld4510m000) are different.
C)
1. The parameter 'Automatic confirmation of back orders' is YES in "Purchase Order Parameters" (tdpur0100s4000). There is a
Purchase Order Line with Inspection. The receipt is made for quantity lesser than ordered qty, with the 'Final receipt' flag
YES. This confirms the back order for the balance quantity. In the back order line the quantity is changed. Again, some
quantity is rejected in the approvals and the reduced quantity in the back order line is not considered and the quantity is
updated as a whole.
2. The back order line is created in the same way as it was done above. The back order line is cancelled and then some
quantity is rejected in the approvals and the rejected quantity is added in the cancelled back order line. Instead, it should
create a new back order line with sequence no 2. (Similar to the case where the original back order line has been deleted)
SOLUTION DESCRIPTION:
A)
The 'Inspection' flag would be defaulted once the item dimensions are entered.
B)
The difference between the amounts was due to the rounding of the received quantity in to the inventory unit of the item.
This has been solved and the amounts at both the places are same.
C)
1. The quantity to update in the back order line is determined as the difference between the current back order qty and the
original back order qty.
2. A new back order line with sequence number 2 is created now.

Solution: 127376
SITUATION IDENTIFIED IN:
"Run Detail SRP" (tssoc2265m000)
SITUATION DESCRIPTION:
The 'Make Job...' button should be removed in the session "Run Detail SRP"(tssoc2265m000) as it is not possible to run this
session as a job.
SOLUTION DESCRIPTION:
The 'Make Job...' button has been removed in the session "Run Detail SRP"(tssoc2265m000).

Solution: 127381
SITUATION IDENTIFIED IN:
"Password Aging" (ttstppwdaging)
SITUATION DESCRIPTION:
If you are using the DEM browser then the question of the Password Aging is in the background and overlapped by the
browser. This only happend in B50_b.
SOLUTION DESCRIPTION:
For other environments then B50_b there was a suspend of 2 seconds before bringing up the question. This suspend is now
also implemented in the B50_b object of the ttstppwdaging.

Solution: 127382
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1220m000)
SITUATION DESCRIPTION:
1) When user runs planning for an item after changing the Safety Time in the Item Supplier Information for that item, system
gives fatal error 606 and fails. No fatal error should be given when running planning.
2) When user runs planning, system creates planned purchase orders with a link to cancelled schedule lines. System should
not link a cancelled schedule line for a planned purchase order.
SOLUTION DESCRIPTION:
Now changes are done such that system runs planning with out any fatal error 606 and also doesn't create any planned orders
with a link to cancelled schedule lines.

Solution: 127390
SITUATION IDENTIFIED IN:
"Planned PRP Purchase Orders(Materials)" (tppss6110s000)
SITUATION DESCRIPTION:
While trying to create Planned RPR Purchase Order system is not allowing the user to enter Price manually it always picks
the Price from Purchase Data.
SOLUTION DESCRIPTION:
The above problem is solved. Now the system allows the user to enter the Price manually.

Solution: 127391
SITUATION IDENTIFIED IN:
"Update Sales Statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
When running the partial update in Sales Statistics, then the turnover figures are exceeding the actual turnover figures.
SOLUTION DESCRIPTION:
Now, when running partial update in Sales Statistics, turnover figures will tally with the actual figures.

Solution: 127398
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When adding sales order lines with the order change message, and the warehouse code on the line was empty, an error
message was generated: "Warehouse not allowed". When inserting new lines via the order message, an empty warehouse code in
the file results in the default warehouse on the sales order line.
SOLUTION DESCRIPTION:
The program script has been corrected. In case of adding lines to an existing sales order, a blank warehouse code in the ASCII file now gives the default warehouse on the sales order line, similarly as in the normal order message.

Solution: 127403
SITUATION IDENTIFIED IN:
"Change Price/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
An extra Receipt record with zero quantity is inserted in Finance table " Receipts by Packing Slip" table, if
Prices/Discounts are changed after Receipts through the session "Change Price/Discounts after Receipts".
SOLUTION DESCRIPTION:
Now, extra Receipt records with zero quantity are not generated if the prices/discounts are changed after Receipts.

Solution: 127405
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Notes II" (tfacr2121m000)
SITUATION DESCRIPTION:
The invoice, which has Advance Receipt Request (ARR) as yes, is not displayed in the session "Link Invoices to Credit Notes
II ". Hence it's not possible to assign a credit note to it when required.
SOLUTION DESCRIPTION:
Now the invoice with Advance Receipt Request (ARR) is also displayed if it has open balance & it is now possible to assign a
credit note to it from this session.

Solution: 127413
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. In the session "Master Data Parameters" (whwmd0100s000), the parameter "Only Unoccupied Locations" is set to NO.
2. All the bulk/pick locations of the warehouse are occupied with some quantity and due to the parameter setting the
occupied location could also be advised.
3. The Receipt procedure has only one the activity "Receipt" (whinh3520m000).
4. The inbound should be done automatically, at the time the receipt were confirmed. The inbound is not made and the item is
left in receiving location.
SOLUTION DESCRIPTION:
The goods are advised to the Bulk or Pick location at the time the receipt is confirmed.

Solution: 127419
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
"Process Delivered Sales Orders" (tdsls4223m000)
SITUATION DESCRIPTION:
System allows the user to delete the purchase and sales orders created for PCS Project Items, even though the status of the
Project is not "Archived".
SOLUTION DESCRIPTION:
Now, changes are made such that system doesn't allow the deletion of purchase and sales orders if the corresponding linked
Projects don't have the status of "Archived". Only when the status of the PCS Project is "Archived", system allows the
deletion of the purchase and sales orders.

Solution: 127429
SITUATION IDENTIFIED IN:
"General Table Maintenance" (ttaad4100)
SITUATION DESCRIPTION:
When the DAL is active in GTM, and the user selects option 'Print Report' from the option menu, for a table whose primary key
contains fields with Enumerated domains, and the user enters a range of values for the field with the enumerated domain, the
value entered in the 'to' field is displayed in place of the value for the 'from' field and the 'to' field is blanked out.
SOLUTION DESCRIPTION:
Now the values are displayed correctly as entered by the user when entering ranges of values for selection of records for
printing.

Solution: 127430
SITUATION IDENTIFIED IN:
"Copy Budgets" (tffbs1202m000)
SITUATION DESCRIPTION:
When a budget with a percentage of 100 for 1 period has been copied via the session Copy Budgets (tffbs1202m000), the
percentage for that 1 period is 100% devided by 12. This is not correct because the 100 % should be the same
SOLUTION DESCRIPTION:
Now the copy budget session is working, as it should

Solution: 127432
SITUATION IDENTIFIED IN:
"Purchase Contracts" (tdpur3100s000)
SITUATION DESCRIPTION:
New contract could not be inserted when a Purchase contract header - detail session is already open.
SOLUTION DESCRIPTION:
It is possible to insert a new contract / contract line even when header/ details session is already open.

Solution: 127433
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40c
127412
Defects solved in B50b
125883, 127014, 127272, 209122
Defect solved in 71a
125319, 125883, 127067, 127272, 209122
Descriptions:
- Defect 125319 Session type 3 with 1 occurrence fields got disabled
- Defect 125883 After starting QBF twice with a selection on a field the firs and last record is not working right.
- Defect 127014 Click on a field after undo should result in modify/add depending on the filled occurrences.
- Defect 127067 View field enabled but input not possible
- Defect 127272 AFS put functions for segmented fields updated.
- Defect 127412 AFS Continue process made available for BaanIV
- Defect 209122 QBF descend sorting on non key fields corrected
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 127434
SITUATION IDENTIFIED IN:
"Sales Change Order Sequence Numbers" (tdsls0153m000)
SITUATION DESCRIPTION:
When zooming from the sales order header to the session "Sales Change Order Sequence Numbers" (tdsls0153m000), this
session comes up in display mode. When pressing the "new" button, another occurrence is started and a new record can be
entered. However, when returning from this occurrence to the previous one (in display mode), the newly entered record is not
visible. It is only visible after refresh.
SOLUTION DESCRIPTION:
The program script has been corrected. The display session (the parent) is now automatically refreshed after saving a new
record.

Solution: 127449
SITUATION IDENTIFIED IN:
"Copy Item Data" (tcibd0205m000)
SITUATION DESCRIPTION:
When copying an item to a new item, the Item Production text is not copied to the new item
SOLUTION DESCRIPTION:
The system will copy the Item Production Text to the new item while copying the item.
While copying the item to a new Item, the system will copy the Item Production Text to the new Item.

Solution: 127450
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000)
SITUATION DESCRIPTION:
In the session "Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000), the Business Partner name was
missing on all the reports.
SOLUTION DESCRIPTION:
The Business Partner name has been included in all the reports of the session "Print Aging Analysis by Invoice-from
Business Partner".

Solution: 127460
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When receiving an order acknowledgment with a different item for a direct delivery purchase order line, the item was being
updated. This is not allowed, even if the "Field Action" in the conversion setup is set to "Update".
SOLUTION DESCRIPTION:
In case of direct delivery purchase orders, it is not allowed to change the item code, similarly as in the manual order entry
process (in the user interface, the item field is disabled). This has been corrected. The "Differences between Purchase
Order and Order Acknowledgment" report shows that the incoming data is different from the existing item code, but the item
code is not being updated on the order. Some other purchase order line fields could also be updated in case of direct
delivery, which is also impossible in the user interface. Corrections have been made for the following fields: Ordered
Quantity (tdpur401.oqua), Purchase Unit (tdpur401.cuqp), Lot Selection (tdpur401.lsel) and Lot (tdpur401.clot).

Solution: 127469
SITUATION IDENTIFIED IN:
"Create Table from Sequential Dump" (ttaad4227m000)
SITUATION DESCRIPTION:
Session allowed "Name of Dump File" and "Name of Error File" to be identical which lead to overwriting the dump file.
SOLUTION DESCRIPTION:
Error file name check added and when user tries to enter the same name like dump file has, error message is given.

Solution: 127470
SITUATION IDENTIFIED IN:
"Print Reminder Diary" (tfacr3430m000)
SITUATION DESCRIPTION:
Invoices fully settled with receipt steps "Document accepted by customer" or "Document sent to bank" are showing Zero
balance.
SOLUTION DESCRIPTION:
Invoices fully settled with receipt steps "Document accepted by customer" or "Document sent to bank" are not printed in
Reminder Diary.

Solution: 127477
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s100)
SITUATION DESCRIPTION:
An Outbound Order line is created for some quantity and advice is done. Then, the quantity is reduced and "Re-advise
Remaining" is done. The system goes into loop and hangs.
SOLUTION DESCRIPTION:
Now, on invoking the "Re-advise Remaining" option system doesn't hang and quantities are advised properly.

Solution: 127478
SITUATION IDENTIFIED IN:
"Service Order Activities" (tssoc2110s000)
SITUATION DESCRIPTION:
When adding an activity to a service order for a configuration which is not covered by a contract the following message
appears: "Service Order not found in table Service Orders".
The activity should be created for this service order.
SOLUTION DESCRIPTION:
The problem is caused by the way the records are retrieved from the database. Here, it has been expected that the contract
should be present, although that is not always required in this case. This behavior is also dependent on the database driver.
The way in which the records are retrieved has been changed, so that it is not required that a contract exists for a
configuration on an activity line.

Solution: 127480
SITUATION IDENTIFIED IN:
"Networks" (ecedi0120s000)
SITUATION DESCRIPTION:
The field "Suppress Standard Communication" (ecedi020.scon) in the Networks session (ecedi0120s000) is set to Yes for
multi company EDI networks. Since it is also disabled for this network type (which is correct), it cannot be changed and
hence the semaphore logic cannot be used.
SOLUTION DESCRIPTION:
The "Suppress Standard Communication" field is now set to NO for multi company networks. Hence the semaphore
functionality works properly.

Solution: 127482
SITUATION IDENTIFIED IN:
"Contract Changes" (tsctm3520m000)
SITUATION DESCRIPTION:
1. A service Contract is created and there are two coverage terms of type 'Other Cost' and they are in the same time period.
Also they are attached to the same Cost Component.
2. The system does not block the user by saying
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++
" Coverage terms are not unique. Please check the related object/activity, the other Cost Terms and the Threshold"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++
3. This can be observed when the Recalculate Prices is done from the session "Recalculate Prices" (tsctm1201m000) or when
the contract is Activated.
SOLUTION DESCRIPTION:
The check for the uniqueness has been created for the Other Cost coverage terms with out an object/activity as well.

Solution: 127484
SITUATION IDENTIFIED IN:
"Import Reference Model" (tgbrg4205s000)
SITUATION DESCRIPTION:
When we import our Reference Model for the second time into our Project Model with the option "Delete existing Roles"
checked, then we get an error 206 "Record not locked".
SOLUTION DESCRIPTION:
We found, that the deleting of the existing roles was done in an incorrect way.
We changed this and the second import of a Reference Model into a Project Model gives no problems anymore.

Solution: 127487
SITUATION IDENTIFIED IN:
"Projects" (tipcs2101m000)
SITUATION DESCRIPTION:
When 'Search Key' and other fields of "Projects" (tipcs2101s000) session are modified, then the system saves only the 'Search
Key' whereas the other fields value are defaulted to their previous values.
SOLUTION DESCRIPTION:
The system saves all fields which have been modified when the 'Search Key' is modified.

Solution: 127489
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
When split deliveries are present the system removes the COGS for those lines, which are not selected within the given range
of invoice date.
SOLUTION DESCRIPTION:
Now the user can specify the range for posting date ("Transaction Entry Date") also. And COGS will be deleted within this
range only.
The reason for having a different range for "Transaction entry Date" is because of the fact that users can compose invoices
in one date and post them in another date.

Solution: 127490
SITUATION IDENTIFIED IN:
"Aspect Values" (tigrt0281m000)
SITUATION DESCRIPTION:
While entering "Aspect Values" in the session tigrt0281m000, if the user presses undo button, the lines get disappeared. but
then "New" button is not enabled to add new values .
SOLUTION DESCRIPTION:
The "New" button is not enabled to add new values in the session "Aspect Values".

Solution: 127492
SITUATION IDENTIFIED IN:
"Assignments on Advance / Unallocated Receipts" (tfacr2530m000)
SITUATION DESCRIPTION:
When the session "Assignments on Advance / Unallocated Receipts (tfacr2530s000)" is zoomed to, through the session
"Advance / Unallocated Details (tfacr2529s000)", the session comes up blank & no details are displayed.
The same session shows right details when zoomed from "Receipt Details (tfacr2524s000)".
SOLUTION DESCRIPTION:
Because of technical reasons the problem of the session coming up blank cannot be solved & hence details cannot be seen
through the session "Advance / Unallocated Details (tfacr2529s000)"
To view the details of Assignments made, the session "Assignments on Advance / Unallocated Receipts (tfacr2530s000)"
may be zoomed from "Receipt Details (tfacr2524s000)".

Solution: 127502
SITUATION IDENTIFIED IN:
"Query Data" (ttadv3180m000)
SITUATION DESCRIPTION:
When a report layout (width 255 characters, locale ISO_BIN) was edited in session "Maintain Report Layouts" (ttadv3131s000),
and a label field was moved to the right as far as possible and one position up, the fatal error index out of dims occurred.
SOLUTION DESCRIPTION:
During the generation phase of a wide report not all "empty" positions in the report were filled with space characters. As a
result of the presence of these really empty positions shifting of label fields over these positions resulted in errors. A fix
is made in the generating of reports. Now no empty positions are present in the report and the index out of dims error no
longer occurs.

Solution: 127503
SITUATION IDENTIFIED IN:
"whinh3520m000" (Receipts)
SITUATION DESCRIPTION:
In case of an Intra Warehouse Item Transfer, which is created via a planned distribution order via Enterprise Planning, the
goods are received on a location of type 'receiving'. Since the inbound procedure cannot be executed for these kinds of
orders the inventory is stuck on the receiving location and can't be moved.
SOLUTION DESCRIPTION:
In case of an Intra Warehouse Item Transfer, which is created via a planned distribution order via Enterprise Planning, the
receipt step is made mandatory. This is only applicable when both the 'to' item as well as the receiving warehouse are location
controlled. In this scenario now the user can define the receipt location on the receipt line. This location should be of type
'pick'/'bulk'. After confirming the receipt the rest of the inbound process will be performed automatically and the inventory
will be stored on the chosen 'pick'/'bulk' location.
The same functionality was already applicable in case of an item transfer (both transfer as well as transfer manual orders) to
a lot controlled item. In this scenario the maintain receipt step was already mandatory. This to be able to define the lot code
upon receipt.

Solution: 127510
SITUATION IDENTIFIED IN:
"Update Sales Statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
When a sales order line is cancelled and if the updates are done for the same. Then while printing the sales statistics, the
quantity and amounts values are getting doubled.
SOLUTION DESCRIPTION:
Now the values are shown correctly and the sales updating also done correctly.

Solution: 127514
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
Shipment lines get sometimes a wrong weight when confirming several lines from picking list with different items.
SOLUTION DESCRIPTION:
Before creating a new shipment line the related item base data is re-read.

Solution: 127517
SITUATION IDENTIFIED IN:
"Budget cost analysis" (tpptc3200m000)
SITUATION DESCRIPTION:
Prior to solution 125482 it was possible that budgets were created with a wrong cost analysis code.
Solution 125482 solved this but the customer has budgets in his system with the wrong code.
There should be a possibility to delete these budgets from session tpptc3540m000.
SOLUTION DESCRIPTION:
Instead of providing a button for deleting the corrupted budgets a correction program is been written to first print a report of
such records by setting the field 'test.run' to yes in the new session generated 'tpcor3200m000' and then if user wants them to
be deleted then the system would delete them by setting the field 'test.run' to no .

Solution: 127521
SITUATION IDENTIFIED IN:
"Planning Board" (ttpcm1100m000)
SITUATION DESCRIPTION:
On the planning board, item descriptions were truncated at 50 characters.
SOLUTION DESCRIPTION:
The maximum size of a description is now enlarged to 80 characters.

Solution: 127522
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
If there are more than one advance payment lines present & when the amount of first advance payment request is greater than
the first installment, then while settling the second installment, both, partial amount of first advance payment and full
amount of second advance payment should be considered. But, presently second advance payment is not being considered.
SOLUTION DESCRIPTION:
The above problem is solved & now, all the unsettled advances will be checked before posting the installments to revenue.

Solution: 127525
SITUATION IDENTIFIED IN:
"Print Goods Received Note" (whinh3412m000)
SITUATION DESCRIPTION:
Receipt of cost/service item gets stuck if order step "Print Goods Received Note" and parameter for inventory handling is set
to not printing cost/service items.
SOLUTION DESCRIPTION:
When inserting new inbound record for cost or service item and mandatory order step is 'print goods receipt note' and
parameter for inventory handling states this kind of item won't be printed then automatically next activity 'receipts' is
inserted and procedure mask also updated.

Solution: 127526
SITUATION IDENTIFIED IN:
"Shift Production Planning" (tisfc1202m000)
SITUATION DESCRIPTION:
A range of production orders are entered in session "Shift Production Planning" for shifting the order dates. Within that
range there are production orders, which have all operations, completed. System should not shift such orders. Shifting such
orders does not make sense. But system wrongly shifts the receipt date when an order has all operations already completed.
SOLUTION DESCRIPTION:
When executing session "Shift Production Planning", if the system encounters a production order, which has all operations "completed", the system will not
process this order. The system will give an error message in the report saying, "All operations of this production order are completed, shifting not
allowed". When given in a range, it gives the message and continues with next order
.

Solution: 127527
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0501m000)
SITUATION DESCRIPTION:
System gives compilation errors when compiling the dll tcibddll0010.
SOLUTION DESCRIPTION:
Now modifications are done such that system doesn't give any compilation errors when compiling the dll tcibddll0010.

Solution: 127533
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
Checks should be present to prevent the user from accidentally entering dates belonging to 'closed' periods.
SOLUTION DESCRIPTION:
Some more additional checks built in the program.
1. If 'from' dates in the form are left blank, then an error message is displayed.
2. If within the range of dates, any of the period is not open, then also an error message is displayed.

Solution: 127553
SITUATION IDENTIFIED IN:
Baan OpenWorld Common Components :
BaanERP5.0b : ccboidllowxlfn, ccboihandletxt
SITUATION DESCRIPTION:
In above mentioned components, reference of some includes is made which should be removed because from BOI Builder 2.2
onwards, includes are not used.
SOLUTION DESCRIPTION:
1. All includes are replced with their respective DLLs. So just replace function calls of includes with function calls of DLL

Solution: 127554
SITUATION IDENTIFIED IN:
"Item Surcharges" (ticpr111s000)
SITUATION DESCRIPTION:
For an independent currency company, if the surcharge amount is modified and does the currency rotation, the amount in
other home currencies will not be calculated based on the new amount.
SOLUTION DESCRIPTION:
The surcharge amount in other home currencies will be calculated, whenever the amount is changed in one of the home
currencies, in an independent currency company.

Solution: 127556
SITUATION IDENTIFIED IN:
"Material costs" (tpppc2110s000)
SITUATION DESCRIPTION:
The actual costs and reversal of hard commitment are not being posted into the correct periods in projects. There is a
difference in periods in finance and periods in projects.
SOLUTION DESCRIPTION:
Now directly from finance tables the periods are obtained instead of calculating the periods from registration date.

Solution: 127560
SITUATION IDENTIFIED IN:
"Activity Progress" (tpppc1560m000)
SITUATION DESCRIPTION:
The inventory unit in the general item table is not mandatory for cost items. Due this functionality, when we try to copy
progress from "Activity Progress" to "Copy Progress to Activity/Cost Type/ Cost Object", a fatal error comes up.
SOLUTION DESCRIPTION:
It is mandatory to have an Item unit in the session "Progress by Activity/Cost Object". So when unit is not present, fatal
error comes up. Functionally also, it is necessary to have a unit. So a message will appear if item unit for control code is
not found and progress will not be copied.

Solution: 127564
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000).
SITUATION DESCRIPTION:
Consignment Replenishment Orders could be linked to Sales Contracts.
Afterwards several problems would occur.
When for example the ordered quantity (tdsls401.oqua) was changed, message "Price cannot be changed" (tdisa001.00)
appeared and saving of the record was impossible.
SOLUTION DESCRIPTION:
From now on Consignment Replenishment Orders cannot be linked to Sales Contracts anymore. This type of order was never
meant to be used this way.
According to the concept, the only purpose of this type of order is to transfer goods from one warehouse to another. Note that
this transfer does not affect the ownership of the goods.
As a consequence no financial transactions should take place, like for example linking to sales contracts.
When goods are actually issued from a replenished warehouse, a Consignment Invoicing Order should be used. This type of
order can actually be linked to a Sales Contract. That way the financial transactions are handled the right way.

Solution: 127567
SITUATION IDENTIFIED IN:
"Inbound Order Lines" (whinh2510m000)
SITUATION DESCRIPTION:
When an order line is tried to block/unblock an unnecessary error message pop up saying that "Order line not found ".
SOLUTION DESCRIPTION:
The error message will not pop up and blocking / unblocking operation will be performed and a message will also be shown
saying that " Line is blocked " or Line is unblocked" depending upon the operation.

Solution: 127568
SITUATION IDENTIFIED IN:
"Simulate orders" (cprrp1210m000)
SITUATION DESCRIPTION:
"Index out of dims" occur while running the Enterprise Planning and planned orders are not generated.
SOLUTION DESCRIPTION:
The arrays are handled correctly and Planned orders will be generated.

Solution: 127569
SITUATION IDENTIFIED IN:
"dm package" (dm)
SITUATION DESCRIPTION:
Compilation Errors in various libraries of 'ODM' (Object Data Management) and 'EDM"(Engineering Data Management)
package
SOLUTION DESCRIPTION:
The errors are being solved and hence runtime errors will not occur.

Solution: 127572
SITUATION IDENTIFIED IN:
"Production Planning" (tisfc1500m000)
SITUATION DESCRIPTION:
When a Subcontracted Operation in Production planning is having a purchase order active, then system is allowing the user to
delete all the selected operations including the sub-contracted one, when the records are selected in range.
SOLUTION DESCRIPTION:
When a Subcontracted Operation in Production planning is having a purchase order active, then system will not delete the
Subcontracting operation in production planning even when the records are selected in the range.

Solution: 127574
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
"Report & Remittance Bank File for Belgian Banks" (rtfcmgL2571300L)
SITUATION DESCRIPTION:
The report "Report & Remittance Bank File for Belgian Banks" (report 42, rtfcmgL2571300L) cannot handle bank accounts that
consist of more than 17 positions. In France, for instance, the bank accounts have 23 positions. This cannot be printed on
the report and the account number will be truncated.
The value for 'Total Credit Bank Accounts' does not summarize correctly. This is because the value is outside the system boundaries.
SOLUTION DESCRIPTION:
The field in the column 'Bank Type' has been adjusted to display these accounts also. The value in the field 'Total Credit Bank Accounts' is now also
visible.

Solution: 127578
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b
124002, 203206
Descriptions:
- Defect 124002 When New button in Multi occ list session is pressed then the new added records are not returned
- Defect 203206 Limitation of 4K messages for oledaemon removed.
If you are using oledaemon then you also need a portingset 7.1c or newer. And BWversion 7.1.x or newer.
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 127579
SITUATION IDENTIFIED IN:
"Budget Amounts and Quantities per Year" (tffbs1500m000)
"Budget Amounts and Quantities per Year" (tffbs1100s000)
"Budget Amounts and Quantities per Year" (tffbs1101m000)
SITUATION DESCRIPTION:
When the session Budget Amounts and Quantities per Year (tffbs1500m000) is started, and a rebuild Sublevels has been done,
it is not possible to see, which ledger accounts on the form have a sublevel 0 or a sublevel 1.
This is important for the calculation of the total.
SOLUTION DESCRIPTION:
A new checkbox has been added on the form that has the check if the ledger account has been created on the background or
not

Solution: 127583
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Enter a Sales Order Line with a specific revision of an Engineering Item. When the line a split delivery line, the E-revision
field is disabled, and it is not possible to change the e-revision for the item.
SOLUTION DESCRIPTION:
Since, e-item revision can become outdated, change in e-revision is necessary.
Change has now been made to allow change the e-revision till one of the detail line is advised. Changing the e-revision would
be applicable to all the detail lines.

Solution: 127586
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
Language of Supplier was not taken into account when printing the Remittance Advice.
SOLUTION DESCRIPTION:
The Problem is solved now and the Language of Supplier will be taken into account when printing the Remittance Advice.
Solution: 127595
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
The netchange flag will not be reset for project items for which the project has been closed. This means that these items will
be selected in every net change run.
SOLUTION DESCRIPTION:
The netchange flag for project items is reset after a net change run.
Solution: 127598
SITUATION IDENTIFIED IN:
"Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
When the user is maintaining Sales quotation line and save the record. Without closing the session user press 'ctrl n', to
maintain another Quotation line for the same item. Here the system is not picking the correct price.
SOLUTION DESCRIPTION:
The system will pick the correct price even if the user maintains the new Quotation line for the same item by pressing 'ctrl n'.

Solution: 127610
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The following situation were identified.
1. The check on batch balnce was done for each invoice created by this process. This caused performance problem due to
multiple reading of the same documents in the Nonfinalized transaction table (tfgld102 )
2. The error message when the ledger account was not maintained for the accrual account in teh Mapping scheme was
misleading in B50_b versions. The error message used to be "Ledger Account for the Expense Tax from the integration
mapp", whereas it should be " The ledger account for %s( Receipt / Direct delivery ) cannot be found in the integration
mapping scheme."
3. It was only possible to display error messages of upto 60 characters by the error report.
SOLUTION DESCRIPTION:
1. Now the batch balance, and the resetting of transaction type status are checked only when the transactions are written onto
the database.
2. The error message has been corrected to display the actual error.
3. The length of the error messages displayed on the error report has been increased ( to 136 characters , atleast ).

Solution: 127613
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When entered from the session 'Assign unallocated /advance receipts to invoices (tfcmg2130s000)', document date is not
saved properly.
SOLUTION DESCRIPTION:
Earlier, wrong Document date was saved in the tables.
Now, Document date is saved properly in the tables.

Solution: 127619
SITUATION IDENTIFIED IN:
"Print Purchase Receipts" (tfacp1430m000)
SITUATION DESCRIPTION:
The session performance of "Print Purchase Receipts" is slow.
SOLUTION DESCRIPTION:
The performance of the session has been improved and the report comes fast.

Solution: 127627
SITUATION IDENTIFIED IN:
"Maintain and Confirm Back Orders" (tdsls4125m000)
SITUATION DESCRIPTION:
A)
1. A sales direct delivery order line is maintained and purchase order is generated.
2. This purchase order is received partially. Purchase order is then processed.
3. Sales and Purchase backorder are created. The sales backorder is removed.
4. When this backorder is confirmed again, backorder is not created.
B)
1. There is cost item with the 'Release to Warehousing' option selected in the "Item Purchase Data" (tdipu0101s000).
2. This item is entered in the purchase order line and also a TP project is also entered along with Warehouse.
3. Then, there are many partial receipts are made in "Receipts" (whinh3520m000).
4. The creation and reversal of soft commitment and hard commitments in Projects is not consistent.
SOLUTION DESCRIPTION:
A)
It is possible to re-confirm the back order of a direct deliver sales order. At this time, the back order of the corresponding
purchase order is also created.
B) When the partial receipt s are made for a Cost item for a TP project in Warehousing, the creation and the reversal of the
soft and hard commitments are created correctly in Projects.

Solution: 127629
SITUATION IDENTIFIED IN:
"Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
Using session "Purchase Invoice Corrections" (tfacp2110s000), it is not possible to correct multiple tax lines for an invoice
with level of tax calculation as "Invoice Header".
SOLUTION DESCRIPTION:
It is now possible to make correction to multiple tax lines for an invoice with level of tax calculation as "Invoice Header".

Solution: 127633
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
A Sales Order is raised with a line which has a Contract attached to the Business Partner and Item. A second line is raised
with a different Item that is not linked to any contract.
When the Shipment is confirmed, the second Order line which does not have any contract attached is also attached to the
contract, which is attached to the first line.
SOLUTION DESCRIPTION:
Now, the link is made to only to the Sales Order lines, which have Contracts, attached.

Solution: 127637
SITUATION IDENTIFIED IN:
"Service Order: Actual Other Costs" (tssoc2141s000)
SITUATION DESCRIPTION:
During the completion of the service order, the travel cost is not billed when the total travel cost line is linked to an acitivity
rather then then to the order header. The total travel cost should be calculated based on the detail travel lines.
SOLUTION DESCRIPTION:
When the total travel cost line is linked to an activity line, then the detail travel lines will be linked as well.
During the completion of the service order, the total travel cost will be calculated correctly based on the detail travel lines.

Solution: 127641
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
Two issues were discovered when receiving an incoming purchase order acknowledgment via EDI (Field Action set to
Update):
1. When purchase order lines had items for a Baan Project, and the items on the incoming message were different (but for the
same project), the item of the first line was not updated.
2. The item could be changed on purchase order line details via the incoming order acknowledgement. This is not allowed.
SOLUTION DESCRIPTION:
The program script has been corrected.
1. The project information was not read properly, so the update of the Baan Project item went wrong. Now all items are
updated.
2. There was no check if a normal line was going to be changed or a detail line. Such a check has been introduced, in order
to make sure that only those fields can be updated, which can be updated in the User Interface, like Ordered Quantity. Item
cannot be changed on the details.

Solution: 127647
SITUATION IDENTIFIED IN:
"Sales Quotations" (tdsls1100s000)
"Sales Contracts" (tdsls3100s000)
SITUATION DESCRIPTION:
When entering the Sold To Business Partner on a new Sales Quotation (session tdsls1100s000) or Sales Contract header (session
tdsls3100s000), the default sales office is picked up. But the default quotation or contract series for this sales office is not
picked up.
SOLUTION DESCRIPTION:
The way of defaulting the order series for Sales Orders (tdsls4100s000), Sales Quotations (tdsls1100s000)
and Sales Contracts (tdsls3100s000) is the same now.
First the default series of the order type (session tdsls0194s000) is read. If there is no default, the series of
the user profile (session tdsls4123s000) is read. If empty, finally the series of the sales office is taken (session tdsls0212s000).

Solution: 127652
SITUATION IDENTIFIED IN:
"Update Order Lead Times" (tirou1202m000)
SITUATION DESCRIPTION:
Order Lead Time calculated is wrong, when the Transfer Lot quantity maintained for Operation and the proceeding operation
is having the less cycle time.
SOLUTION DESCRIPTION:
While calculating the Order lead Time if the transfer lot is maintained for an operation and the proceeding operation has the
operation time less than the operation time of the current operation. If the calculated Order Lead time is less the
operation time, then will consider maximum operation time as Order Lead Time.

Solution: 127653
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (Manufacturing/Distribution)" (tfgld4101s000)
SITUATION DESCRIPTION:
The user was allowed to save complementary ledger account in the integration-mapping scheme
SOLUTION DESCRIPTION:
Now the system is not allowing the user to save complementary ledger account in the integration-mapping scheme

Solution: 127656
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
When changing the sales order type to consignment invoicing the warehouse is changing immediately but the warehouse
name is not.
SOLUTION DESCRIPTION:
The name of the warehouse is now updated as well when in case the warehouse changes because of a change of sales order
type

Solution: 127657
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice to Business partner" (tfacr2420m000)
SITUATION DESCRIPTION:
If you print the aging analysis report with the option based on 'due date' , Report is giving the error message "No data with in
selection" even though there is a valid data.
SOLUTION DESCRIPTION:
Report selects and puts the balance amount in right aging buckets as per the due date of the receipt schedule.

Solution: 127661
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
When new text is created for a Sales Order Detail line (in session tdsls4101s200) and the detail session is closed, a
"recursion not yet implemented" fatal error can pop up when many lines already exist for the same Sales Order Line
Position.
SOLUTION DESCRIPTION:
Sales Order Detail Lines with text can be added and saved without fatal errors now. Session Sales Order Line Details
(tdsls4501m200) gets correct refreshed.

Solution: 127663
SITUATION IDENTIFIED IN:
"Confirm Planned PRP Purchase Order" (tppss6220m000)
SITUATION DESCRIPTION:
When trying to confirm a Planned PRP Purchase Order, fatal error (unknown table 936) comes up.
SOLUTION DESCRIPTION:
The table 936 is for localization parameter set up. Since standard co. set up does not have this table, this error comes up.
The problem is now solved & this error will not come up.

Solution: 127669
SITUATION IDENTIFIED IN:
"Transfer Plan/Order" (cppat1210m000)
SITUATION DESCRIPTION:
- Planned purchase orders for the same business partner are transferred into more than one purchase order.
- When an item has multiple orderlines, the sequence isn't chronological.
SOLUTION DESCRIPTION:
Planned purchaseorders are sorted by Business Partner, Item, orderdate and planned ordernumber before transferring.
This means that planned purchase orders for one Business Partner are transferred into one order. The orderlines are sorted
by Item and multiple orderlines for the same item are ordered by date.
Multiple orderlines for the same item on the same date (caused by e.g. lotsizing rules) are ordered by their (initial) planned
ordernumber.
Solution: 127673
SITUATION IDENTIFIED IN:
"Integration transactions to finance transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
If the user has posted price variances originating from BAAN Project, which occurred because in finance the invoice price
differed from the ordered price, then in the GRNI-reconciliation these records are not recognized and not selected with
tfacp1235m000 "Select Values for GRNI Reconciliation".
SOLUTION DESCRIPTION:
If a price variance occurred on a purchase order for BAAN Project then this is
posted with transaction origin - financial transaction "Project Costs &
Commitments - Purchase Price Variance". The mapping for this transaction is that the credit
side (just as with the receipt) posts to invoice accrual. In the posting process in
finance however it thinks that the debit side is the invoice accrual
side, which results in a wrong line number in the interim table. This has now been solved.

Solution: 127680
SITUATION IDENTIFIED IN:
"Archive/Purge Finance Transactions" (tfgld6205m000)
SITUATION DESCRIPTION:
Fatal error "Snap shot too old" occurred while archiving the finance transactions.
SOLUTION DESCRIPTION:
Now the error does not occur

Solution: 127681
SITUATION IDENTIFIED IN:
"Revenue History" (tpppc3505m000)
SITUATION DESCRIPTION:
When installments are settled against advances, where installments are not linked to advances and the first installment amount
is less than the first advance value, the amount of revenues posted are different than the actual value.
SOLUTION DESCRIPTION:
The revenue value was going wrong, because in case of partial settling of an installment, the whole installment amount was
posted instead of only a partial amount.
The above problem is now solved.

Solution: 127687
SITUATION IDENTIFIED IN:
"Purchase requisition lines" (tdpur2102s000)
SITUATION DESCRIPTION:
1. The purchase office is left empty in the 'Purchase Requisitions" (tdpur2101s000).
2. A cost item is entered in the Requisition Lines and the Ledger Account is manually entered there.
3. But the description of the ledger account is not displayed.
SOLUTION DESCRIPTION:
The description of the ledger account is retrieved and displayed similar to the case when the Purchase Office is present in the
requisition header.

Solution: 127693
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When entering lot controlled items to Collect Return Orders, the system would automatically create a lot number, without
notifying the user about it.
SOLUTION DESCRIPTION:
A message is implemented that informs users that they may provide a lot number.
If no lot number is provided the system will automatically generate one.
This only applies when adding a lot controlled item to a Sales Order of type 'Collect Return Order'.

Solution: 127694
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
When changing the Payment/Receipt method with the option "Planned Payment Date = Due Date" is checked "ON" to a
Payment method with the option "Planned Payment Date = Due Date" is checked "OFF", the Planned Debit Date remains the
Due date of the Previous payment method and not the date on which the Direct Debit Advice is created.
SOLUTION DESCRIPTION:
When changing the Payment/Receipt method with the option "Planned Payment Date = Due
Date" is checked "ON" to a Payment method with the option "Planned Payment Date =
Due Date" is checked "OFF", the Planned Debit Date won't remain the Due
date of the Previous payment method and now the date on which the Direct Debit Advice is created will be filled correctly.

Solution: 127701
SITUATION IDENTIFIED IN:
"Trade Relations " (tdsmi1500s000)
SITUATION DESCRIPTION:
For a Business Partner if the "Invoice-From" role is not defined, then some of the values like "Sales Price List", "Internal
Sales Representative" and "Contact" maintained in other roles like "Sold-To" and "Buy-From" are not displayed in the
session "Trade Relations (tdsmi1500s000)". The same values are displayed when the user defines the "Invoice-From" role for
that Business Partner.
SOLUTION DESCRIPTION:
Now the problem is solved. Even if the user not maintains the "Invoice-From" role for the Business Partner, the system will
pick all the relevant information from the "Sold-To" and "Buy-From" roles maintained for that Business Partner and will
display in the session "Trade Relations (tdsmi1500s000)".

Solution: 127702
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When using "customized plan items" derived from "standard clustered plan item" then in internal table (cprpd120) "Plan
Item Codes" records will be created for a "non clustered standard plan item" during run of session (cprrp1210m000)
"Simulate Orders" for "customized clustered plan item". Sometimes this can result in an endless looping program when
session runs in multi bshell mode.
SOLUTION DESCRIPTION:
Software is changed so the right records of internal table (cprpd120) "Plan Item Codes" will be used or created and the
program will not run in to endless loop.

Solution: 127704
SITUATION IDENTIFIED IN:
"Global Update of Discounts via Price Matrices" (tdpcg0230m100)
"Global Update of Prices via Price Matrices" (tdpcg0230m300)
SITUATION DESCRIPTION:
System doesn't enable the fields defined for the Matrix Definition in the session's "Global Update of Discounts via Price
Matrices (tdpcg0230m100)" and "Global Update of Prices via Price Matrices (tdpcg0230m300)" if the user starts these sessions
after saving the defaults and closing them. Even, tabbing through the Matrix Definition field doesn't enable these fields.
SOLUTION DESCRIPTION:
Now the fields defined for the Matrix Definitions, which are retrieved as defaults when the sessions are started, will be
enabled even with out tabbing through the Matrix Definition field.

Solution: 127705
SITUATION IDENTIFIED IN:
"Inventory by Warehouse and Item" (whwmd2515m000)
SITUATION DESCRIPTION:
When a completion for an order is over-reported and the over-reported quantity is returned back to the shopfloor, the
"On Order" value in the session "Inventory by Warehouse and Item" (whwmd2515m000) and the "Planned Inventory
Transactions by Order"(whinp1501m000) becomes incorrect.
SOLUTION DESCRIPTION:
The "Planned Inventory Transactions by Order"(whinp1501m000) and "Inventory by Warehouse and Item" (whwmd2515m000)
are updated correctly when a completion for an order is over-reported and the over-reported quantity is backed out.

Solution: 127707
SITUATION IDENTIFIED IN:
"Scan Solution File" (ttpmc2200m000) for Baan IV, "Scan Solution/Patch File" (ttpmc2200s000) for BaanERP 5.0 b/c
SITUATION DESCRIPTION:
When a solution is scanned with session "Scan Solution File" (ttpmc2200m000), it can happen that the solution is already
present in the PMC Registry (the PMC-tables in the data dictionary), but that the physical solution file (the dump to be
imported) is not present. This file could be deleted accidentally on operating system level, or the file is deleted in a planned
action to save disk space.
When the field "Overwrite" is set to "no", nothing is scanned and the dump file is not put in the "Directory for Individual
Solution Dumps" (see the parameter session ttpmc0100m000). When the field "Overwrite" is set to "yes" the dump file is put
in the directory, but only when the solution has not been installed already in any Update VRC.
The checking of solutions returns the message "Solutio n file 'xxx' could not be found".
The Multi-level Download Tool (ttpmc2210m000) uses also the scan functionality. Because the scan session is called with
"Overwrite" set to "no", missing dump files are never restored.
SOLUTION DESCRIPTION:
The session "Scan Solution File" (ttpmc2200m000) has been changed. Regardless of the value of the "Overwrite" field, the
dump file is put in the directory when it is not present. The Multi-level Download Tool (ttpmc2210m000) automatically
picks up this changed functionality.

Solution: 127714
SITUATION IDENTIFIED IN:
"Inventory Variance" (whina1516m000)
SITUATION DESCRIPTION:
1. There is a KIT item and a purchase order is created and received for this KIT item.
2. The price is changed after the receipt for this order in "Change Price/Discounts after receipt" (tdpur4122m000).
3. The quantity posted for the KIT components are the BOM quantity factor and not multiplied by the order quantity of the
main item.
SOLUTION DESCRIPTION:
The quantity of the KIT components posted in "Inventory Variance" (whina1516m000), would be the order quantity of the
KIT item, multiplied by the BOM quantity factor of the component.

Solution: 127715
SITUATION IDENTIFIED IN:
"Initialize Parameters" (tcmcs0295m000)
SITUATION DESCRIPTION:
The End User was not updated on the current progress of this (process) session. Therefor it was difficult to see if the
process was hanging or still runing in the background.
SOLUTION DESCRIPTION:
A progress bar has been added to the session, so that the End User stays updated on the current progress of this (process)
session.

Solution: 127720
SITUATION IDENTIFIED IN:
"Archive Product Variants" (tipcf5290m000)
SITUATION DESCRIPTION:
When running the "Archive Product Variants" session, variants of type "Standard Variants" are deleted.
SOLUTION DESCRIPTION:
An option is provided in the session so that the user can select whether to archive Product Variants of Reference Type
"Standard Variant" or not.

Solution: 127721
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When a user maintains an installment line for a sales order and then releases the installment line to invoicing, he is still
allowed to delete the sales order header. Because of this, the released installment line remains forever in Central Invoicing.
It cannot be posted or purged. This problem is applicable both to B50_b and B50_c
Moreover when the user tries to post that installment line, the open batch created for that day consisting of the transactions
of previous billing requests posted, gets the status of 'deleted'. So the batch cannot be finalized. This problem is applicable
to B50_c only.
SOLUTION DESCRIPTION:
Now the user will not be able to delete the header, if the installment linked to it is already released to Central Invoicing.
Also, the batch will never be set to 'deleted' in B50_c as it can be re-used by a Billing Request processed later.

Solution: 127723
SITUATION IDENTIFIED IN:
"Aspect Value" (tigrt0281m000)
SITUATION DESCRIPTION:
While searching for items by family, for the aspect value of second feature, system is giving the message "Record already
exists", and it is not possible to continue.
SOLUTION DESCRIPTION:
While searching for items by family, for the aspect value of second feature, system will not give the message "Record already
exists", and it is allowing continue search.

Solution: 127725
SITUATION IDENTIFIED IN:
"Print Actual Cost Price by Item/Print Actual Cost Price by Project" (tipcs3452m000/tipcs3462m000)
SITUATION DESCRIPTION:
The subcontractor name is not printed in the 'Subcontracting Costs" of the report generated, when the sessions "Print
Actual Cost Price by Item" (tipcs3452m000) and "Print Actual Cost Price by Project" (tipcs3462m000) are started.
SOLUTION DESCRIPTION:
System prints the subcontractor name in the 'Subcontracting Costs" of the report generated, when the sessions "Print Actual
Cost Price by Item" (tipcs3452m000) and "Print Actual Cost Price by Project" (tipcs3462m000) are started.

Solution: 127727
SITUATION IDENTIFIED IN:
"Print Bills of Lading" (whinh4470m000)
SITUATION DESCRIPTION:
-1- The Volume printed in the Bill of Lading is wrong. The system prints the unit volume of the item and it is not total
volume of the goods shipped.
-2- The Alternative item code of the Sales Order Line is not printed in the Bill of lading.
SOLUTION DESCRIPTION:
-1- The Volume printed in the report is the total volume of the goods shipped and it is not the unit volume of the item.
-2- The alternative item code of the item from the Sales Order is printed in the Bill of Lading now.

Solution: 127732
SITUATION IDENTIFIED IN:
"Generate Picking List" (whinh4415m000)
SITUATION DESCRIPTION:
For a Warehouse using Zones but not locations, it is not possible to sort the Picking List using Zones.
SOLUTION DESCRIPTION:
Now, the user can add one more Sort option. That is "Zone" mentioned in Item Data by Warehouse. This option can be
included in the Sort list & System sorts the Picking List by Zone as mentioned in Item Data by Warehouse.

Solution: 127737
SITUATION IDENTIFIED IN:
"Alphanumeric Answers" (tigrt0127m000)
SITUATION DESCRIPTION:
When a new answer is added to an Answer group, recoding of previously classified item is mandatory.
SOLUTION DESCRIPTION:
When a new answer is added to an Answer group, the system will ask the question, Mark Classified Items for recoding. If the
user selects the answer as 'Yes' for marking, the system will mark the classified items and if the user selects the answer as
'No' the system will not mark the classified items but will add the answer to the Answer group.

Solution: 127741
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103m000)
SITUATION DESCRIPTION:
1. While entering dimensions for a ledger account in "Journal Vouchers" (tfgld1103m000) the dimension description is only
displayed in a flash and disappears from the form.
2. On the header tab user is not able to override document date.
3. Reporting year is user accessible
SOLUTION DESCRIPTION:
1. The description of a latest entered dimension is displayed correctly.
2. User is able to override the document date.
3. Reporting year is not user accessible

Solution: 127742
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
Wrong total amount is been displayed in the session "Selection for Automatic reconciliation's" Form.
SOLUTION DESCRIPTION:
This problem is solved now and the Correct Total amount will be displayed in the session "Selection for Automatic
reconciliation's" Form.

Solution: 127743
SITUATION IDENTIFIED IN:
"Print Cost Price Calculation by Item" (ticpr2410m000)
SITUATION DESCRIPTION:
When running the session "Print Cost Price Calculation by Item" (ticpr2410m000) more than once, without leaving the
session, the printed report gives wrong values.
SOLUTION DESCRIPTION:
The results of the report will be same for an item, even when it is run more than once without leaving the session.

Solution: 127750
SITUATION IDENTIFIED IN:
"Create Tables" (ttaad4230m000)
SITUATION DESCRIPTION:
When tables are created for a range of companies, the count of tables created is wrong.
It takes into account only the tables that were created for the last company from the selected range.
For example, when create table is run for a range of 5 companies, it shows "1 Table(s) Created" though it created 5.
SOLUTION DESCRIPTION:
The message is corrected. Now it shows the exact number of tables created

Solution: 127752
SITUATION IDENTIFIED IN:
"Print Packing Slip" (whinh4475m000)
SITUATION DESCRIPTION:
1. There are 2 outbound lines of two different Sales Orders.
2. They are shipped with the same shipment.
3. When the packing slip is printed, the data for the two lines are printed in two separate pages and the Shipment Header data
is printed twice.
4. They have to be printed one by one in the same page with the header data printed only once.
SOLUTION DESCRIPTION:
Now the Shipment header is not printed in two separate pages and the shipment header data is not printed twice.

Solution: 127763
SITUATION IDENTIFIED IN:
"Post Integration transactions to Finance" (tfgld4201m000)
SITUATION DESCRIPTION:
Session tfgld4201m000 "Post integration transactions to Finance" was creating finance transactions with different fiscal and
reporting year in case when transaction date is fall in last reporting and fiscal periods and one of these periods is closed.
SOLUTION DESCRIPTION:
Now when reporting and fiscal years are different program will create an error message tfglds2099 "Fiscal and reporting years
are inconsistent, please check session tfgld0107m000 "Period status" in the "Error log". User will have to close or open both
reporting and fiscal periods.

Solution: 127765
SITUATION IDENTIFIED IN:
"Print Specifications Delivered, Not yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
In Job, Current year and period values are not taken, instead the values saved during creation of the job are picked.
SOLUTION DESCRIPTION:
Current year and period values are picked when the session is used in the Job.

Solution: 127766
SITUATION IDENTIFIED IN:
"Item Sales Data" (tdisa0101s000)
SITUATION DESCRIPTION:
1. Item defaults are maintained for an item group with item type 'List.
2. The 'Release to Warehousing' check box is not selected in the default Item Sales Data.
3. A KIT item is created for this item group and the Release to Warehousing field in the "Item sales Data" (tdisa0101s000)
is NO for this item.
4. Due to this it is not possible to release the sales order of a KIT item to warehousing.
SOLUTION DESCRIPTION:
The Release to Warehousing field in the "Item sales Data" (tdisa0101s000) is YES for KIT items irrespective of the value in
the Item Data Defaults. This would enable the user to release the KIT items to warehousing.

Solution: 127771
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A Sales Order has 2 lines. The lines are released to Warehousing & Outbound advice has been created. Now, if user tries to
cancel the Header, system gives error that position 1 cannot be modified. User doesn't press OK to this error and goes and
deletes the outbound advice for this position. Now, on saying OK to the error, system cancels that position and header also.
SOLUTION DESCRIPTION:
Now, on following the above procedure system doesn't cancel the Header and lines. It gives the error
corresponding to the next position.

Solution: 127774
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Linking a credit note to a sales invoice by filling in the "original invoice" field when creating the credit note causes the
credit note to appear on the "Print Control Account Checklist" by the amount of the currency difference.
The credit note also appears on the aging report as having a balance when it does not.
SOLUTION DESCRIPTION:
Credit note is not displayed in the "Print Control Account Check list" and "Aging Report".

Solution: 127788
SITUATION IDENTIFIED IN:
"Purchase Order Receipts" (tdpur4101s3000)
SITUATION DESCRIPTION:
The Back Order quantity is enabled even after the back order is confirmed.
SOLUTION DESCRIPTION:
Once the back order is confirmed, the Back Order quantity fields would be disabled.

Solution: 127789
SITUATION IDENTIFIED IN:
"Update Vendor rating" (tdpur8850m000)
SITUATION DESCRIPTION:
A few Purchase Order lines for a Supplier have zero amounts. The Weighting method used is "Turnover". While updating the
Vendor Rating, the values are incorrectly calculated. There is a possibility that Float error may also occur.
SOLUTION DESCRIPTION:
Now, the Vendor rating calculation is done correctly and the possibility of Float error is prevented.

Solution: 127794
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When a purchase order line is having detail line and if any one of the detail line is received with zero quantity, then the
total line become enabled and it is possible to save the data by changing the item.
SOLUTION DESCRIPTION:
Now it is not possible and the total line will be disabled even after the zero quantity line is received at the receipts session.

Solution: 127795
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
When running Calculate Cost and Valuation Prices (ticpr2210m000) and Actualize Cost and Valuation Prices (ticpr2220m000),
the system created more than 32000 sequence numbers for the items that were included in the update. This caused the process
to fail since the domain for tfgld.sern is defined as an integer, and limited to a range of 0 to 32000.
SOLUTION DESCRIPTION:
Actualizing is now done per 400 items. Then a new revaluation order and new transaction date/time is set. This prevents
the seq. nr for overflow.

Solution: 127804
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
When creating
- Sales Orders (tdsls4500m000)
- Manual Sales Invoice Lines (cisli2525m000)
- Purchase Orders (tdpur4500m000)
- Sales Invoices (tfacr1110s000)
the Tax Exceptions (if any) are not always retrieved correctly, mainly due to incorrect or not enough information send from
the packages (ci, td or tf) to the Generic Tax determination procedure.
SOLUTION DESCRIPTION:
When creating
- Sales Orders (tdsls4500m000)
- Manual Sales Invoice Lines (cisli2525m000)
- Purchase Orders (tdpur4500m000)
- Sales Invoices (tfacr1110s000)
the Tax Exceptions (if any) are retrieved correctly. However, not in every situation the "Tax Exceptions" Logic is
applicable.
Example; when goods and invoice are both flowing from Spain to Portugal (both EU members), the Tax Exceptions routine
will not be used as it is part of the "Destination Sales Tax Logic" and not a part of the "EU Tax Handling".
Three functional situations could apply;
1) Your country has nothing to do with EU Tax Laws
2) Your country has to do with EU Tax Laws.
3) Your country has to do with EU Tax Laws, but because EU Tax is not applicable or when the Tax rules are Domestic,
the Destination Sales Tax Logic (and consequently the Tax Exceptions Logic) may apply, depending on the setting of the
parameter "Destination Sales Tax Applicable" in session tccom0000m000 (COM Parameters).
Summarized; Entering a "Tax Exception" in tcmcs1138m000 (Exceptions for Taxes) does not mean that always this Tax
Exception Code will be used. Please refer to the specific laws of your country to see whether Tax Exceptions are applicable
for your specific situation or not.

Solution: 127820
SITUATION IDENTIFIED IN:
"Calculate cost and valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
An error report with message "Quantity of component is zero in the Bill of Materials of item" is printed, even though the
calculated net quantity of the component is not zero.
SOLUTION DESCRIPTION:
If the calculated net quantity of BOM component is not zero, then no error report will be printed for that item.

Solution: 127823
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Checklist" (tfacp1438m000)
SITUATION DESCRIPTION:
Receipts (not for BAAN Project) for purchase orders are in finance posted with the internal rate type and with the rates of
each individual receipt. The session tfacp1438m000 does not take this into account. In this session every receipt and approval
is valuated with the rate information of the purchase order header. Because of this when there are only receipts for a certain
purchase orderline this session shows a difference between the financial and logistical values. This difference is not for real,
as the logistical values are wrongly calculated.
SOLUTION DESCRIPTION:
Now the receipts do take the reality into account that receipts are calculated with the internal rate type and the rates of each
individual receipt.

Solution: 127835
SITUATION IDENTIFIED IN:
"Configurations" (tscfg2120s000)
SITUATION DESCRIPTION:
The priority on the "Sold to Business Partners" (tccom4110s000) is defaulted when making a configuration.
When making a call the priority defined on both entities are used to calculate the response times. It is not logic to use 2 times
the same priority. As it results in a response time which is to early.
SOLUTION DESCRIPTION:
The priority is not defaulted in to the Configuration from the Sold-to Business partner.
It is still possible to define on both the "Sold to Business Partner" and the "Configuration" a priority, even the same priority.

Solution: 127836
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
While approving purchase invoices from session "Purchase Invoices" (tfacp1110s000), where the document date is different
from today's date, the approval transactions are created with document date set to today's date.
SOLUTION DESCRIPTION:
The approval document date is updated correctly with the document date of the invoice, when the purchase invoice is
approved from the session "Purchase Invoices".

Solution: 127848
SITUATION IDENTIFIED IN:
"Anticipated Payments (details)" (tfcmg2116s000)
SITUATION DESCRIPTION:
Anticipated unallocated payment record is updated with incorrect values and this leads to differences in control account
checklist after reconciliation.
SOLUTION DESCRIPTION:
Anticipated unallocated payment record updated with correct amounts and now there is no difference in control account
checklist after reconciliation.

Solution: 127849
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
In session Sales Order Lines, no message appears for a dimension item when the quantity entered in Sales Order Lines is
less than quantity entered in session Sales Item Data ("Order quantity less than minimum quantity of item")
SOLUTION DESCRIPTION:
For a dimension item the check on quantity was missing in the Sales Order Lines session. This function follow the quantity
entered in the Sales Order Lines and display the existing warning message ( Note: order quantity less than minimum order
quantity of item is less than the quantity entered in the Sales Item Data session) if quantity is less than the minimum ordered
quantity store in Maintain Item Data.

Solution: 127865
SITUATION IDENTIFIED IN:
"Reconciliation Payments/Receipts" (tfcmg2103s000)
SITUATION DESCRIPTION:
Reconciliation Aborts with the message "Out of dimension" when trying to reconcile the anticipated document of a Purchase
Invoice which has more than 10 lines and having a Vat code for each of them
SOLUTION DESCRIPTION:
Now the reconciliation is completed successfully

Solution: 127869
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Notes" (tfacr2120m000)
SITUATION DESCRIPTION:
The session takes lot of time to open.
SOLUTION DESCRIPTION:
Now the performance is improved.

Solution: 127870
SITUATION IDENTIFIED IN:
"Print Control Account Checklist" (tfacp2415m000)
SITUATION DESCRIPTION:
On the reports of session "Print Control Account Checklist" (tfacp2415m000) and (tfacr2415m00), the input criteria is not
getting printed.
SOLUTION DESCRIPTION:
The input criteria on the form get printed on the first page of the report.

Solution: 127876
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2521m000)
SITUATION DESCRIPTION:
On actual cost lines, the warranty amount (or contract amount, FCO amount, etc) and the invoice amount are calculated
incorrectly due to rounding.
Calculated amounts differ slightly from the amounts which should have been calculated.
As a result, the customer may be billed for costs which should have been covered fully.
SOLUTION DESCRIPTION:
The warranty amount (or contract amount, FCO amount, etc) and invoice amount will be correctly rounded. The invoice
amount will reflect the total sales amount minus the discount (the contract amount, warranty amount, order quotation
amount, FCO amount and other amount).

Solution: 127879
SITUATION IDENTIFIED IN:
"Settlement by Installment" (tdsls4513s000)
"Process Delivered Sales Orders" (tdsls4223m000)
"Installment Orders" (tdsls4506m000)
SITUATION DESCRIPTION:
A. The settlement is incorrect when a sales order is returned in the same order.The settlement becomes negative when the
following procedure is followed:
1. A sales order line (session tdsls4101s000) is entered for amount 1000
2. The first installment (session tdsls4506m000) for amount 100 is entered, processed and invoiced
3. The sales order line is processed and invoiced
4. The installment is settled with an amount of 100 which is correct
5. A second installment of 100 is made and invoiced
6. A second orderline is created to return the goods of orderline one. The amount is -1000
7. This orderline is processed and invoiced
8. The second orderline is settled with an amount of -1000 which is incorrect.
B. When an installment line is already invoiced, but the sales order line is not, the installment line cannot be processed
with session 'Process Delivered Sales Orders' (tdsls4223m000).
C. An installment is already invoiced and processed. Then the goods are shipped and the sales order line is invoiced and
processed. The installment is not counter booked, giving incorrect sales statistic data. Normally when an installment is
processed a record is entered in the Sales Order Line History of type 'Turnover'. When the goods are invoiced a settlement is
created. When the order is processed, this settlement is written to the Sales Order Line History with negative amount and of
type 'Turnover'. This 'settlement history line' is not entered in the History as the procedure as above is followed.
SOLUTION DESCRIPTION:
A. When following the procedure as described in the situation description, the second installment is now settled with an
amount of 100 which is correct.
B. Installments can be processed although the Sales Order itself is not ready for processing yet.
C. All settlement records are correct entered in the Sales Order Line History. Total turnover amounts for a sales order line are
correct now, giving correct sales statistics.

Solution: 127882
SITUATION IDENTIFIED IN:
"Copy Purchase Orders" (tdpur4201s000)
SITUATION DESCRIPTION:
-1- It is not possible to copy any order in to a return order type.
-2- When the copy to order type is changed to non return order from a return order, the buy from BP field is not enabled.
SOLUTION DESCRIPTION:
-1- When the order type coped to is a Return Order, the user is prompted to enter the return reason code and the session for
the Return Reason pops up and the user can select the Return Reason from it.
-2- When the order type copied to is changed from a return order type to a non-return order type, the Buy-from BP is
enabled.

Solution: 127885
SITUATION IDENTIFIED IN:
"Confirm Planned PRP Purchase Order" (tppss6220m000)
SITUATION DESCRIPTION:
When trying to confirm an Equipment PRP planned order trough session tppss6220m000 the following error message comes up:
Enterprise Unit not found for purchase office ' ' . The purchase office has been left blank in the PRP planned order because
it isn't compulsory, and it is possible to confirm manually in session tppss6810m000.
SOLUTION DESCRIPTION:
The above message comes up as system tries to determine the Enterprise Unit of Purchase Office. But, since Purchase Office
can be left blank, correct Enterprise Unit cannot be determined & this error comes up.
Now, if the Purchase Office is not found, Project Enterprise Unit will be found.
In addition to that, for sub contracting orders, EU tax handling functionality (as per solution no 126577) is added.

Solution: 127889
SITUATION IDENTIFIED IN:
"Audit Payments" (tfcmg1255s000)
SITUATION DESCRIPTION:
Two Problems are solved:
1. When 2 sub-contracting invoices are paid, then bank account of the first supplier's invoice is used for the second
supplier's invoice
2. When 'Bank Account Required' is set to 'yes' in Payment Method and the Supplier's Bank is empty in the Payment Advice,
no audit error is shown for the sub-contracting invoice
SOLUTION DESCRIPTION:
Earlier,
1. Wrong Bank Account is used while paying the second sub-contracting invoice
2. Even when supplier's bank is not filled in the payment advice, sub-contracting invoice can be paid
Now,
1. Correct Bank Account is used while paying any number of sub-contracting invoices
2. Audit error 'Bank of Business Partner not filled' is given and the invoice cannot be paid

Solution: 127890
SITUATION IDENTIFIED IN:
"Copy ranges of locations" (whwmd3200m000)
SITUATION DESCRIPTION:
When a range of locations with Row , Level , Bin are copied , the system insert new records with the fields Level and Bin
right aligned .
SOLUTION DESCRIPTION:
Now the fields Level and Bin are left aligned

Solution: 127893
SITUATION IDENTIFIED IN:
"Attached Files" (dmdoc4540m000)
SITUATION DESCRIPTION:
When the user open the attached file for editing and tries to delete the attached file, then system is giving the message
"Transaction is on, can't continue". System is not giving the proper message.
SOLUTION DESCRIPTION:
When the user open the attached file for editing and tries to delete the attached file, then system will give the error message
"File is already locked for change".

Solution: 127894
SITUATION IDENTIFIED IN:
"Post/Print Financial Transactions" (ticstdll0015)
SITUATION DESCRIPTION:
Zero-orders from Shopfloor should not result in inventory-variances.
SOLUTION DESCRIPTION:
No inventory-variance is created if the quantity-completed on the order is zero.

Solution: 127895
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When the option "Inventory by Item and Warehouse" (whwmd2515m100) is activated from the shortage menu and a different
warehouse is selected the tax country and code is not updated correctly.
SOLUTION DESCRIPTION:
The functionality similar to manually changing the warehouse of the sales order line is also implemented in case the
warehouse is changed when handling the shortage.

Solution: 127899
SITUATION IDENTIFIED IN:
"Charge Elements" (tppss2100s000)
SITUATION DESCRIPTION:
If "Use Charge Element Type" is not checked in session tppdm0100s000 "General Parameters", then session tppss2100s000
"Charge Elements" doesn't work properly:
the fields "Earned Value Method" and "Linked Charge El." are always disabled.
This is not correct, because the parameter "Use Charge Element Type" has nothing to do with Earned Value Method.
SOLUTION DESCRIPTION:
Do not disable the fields "Earned Value Method" and "Linked Charge El." if "Use Charge Element Type" is not checked.

Solution: 127901
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. The Rounding factor of the currency used is 1.
2. A purchase order is created. The ordered quantity of the purchase order is very precious in terms of number of digits after
the decimal point.
3. The purchase order is received and the amount posted as the Purchase/Receipt entry in "Integration Transactions by
Project/Order" (tfgld4510m000) is slightly wrong due to the rounding.
SOLUTION DESCRIPTION:
The amount posted to "Integration Transactions by Project/Order" (tfgld4510m000) is correct.

Solution: 127902
SITUATION IDENTIFIED IN:
"Report Input Fields" (ttadv3532m000)
SITUATION DESCRIPTION:
When you open the Report input fields it is having Sort sequences more than 99. But the domain is of format Z9. So bshell is
filling up with the error messages like :
2002-08-23[09:09:35(UTC+08:00)]:E:d96502db: Errno 0 bdb_errno 0
2002-08-23[09:09:35(UTC+08:00)]:E:d96502db: Log_mesg: Overflow: format='Z9' value='127'
SOLUTION DESCRIPTION:
Form display format for the field Sort sequence is changed to 'ZZ9'.

Solution: 127905
SITUATION IDENTIFIED IN:
"Run Global SRP" (tssoc2260m000)
SITUATION DESCRIPTION:
"Transaction is on;cannot continue" or "A not terminated transaction is aborted" error comes when closing "Run Global
SRP"(tssoc2260m000) session.This happens only when a Service/Cost item attached with an activity does not have a cost
component.
SOLUTION DESCRIPTION:
If a Service/Cost item attached with a service order activity does not have a cost component, then the error message "Cost
Component Mandatory for Service Order Other Cost Line" will be displayed in the error report. Closing the "Run Global
SRP"(tssoc2260m000) session does not result in an error anymore.

Solution: 127908
SITUATION IDENTIFIED IN:
"Invoiced Sales-Order History by Business Partner and Item" (tdsls5502m000).
SITUATION DESCRIPTION:
Field "Item Description" (tcibd001.dsca) is not always displayed, although an item description is available in "General
Item Data" (tcibd0501m000).
SOLUTION DESCRIPTION:
Fetching the description of an item sometimes failed.
From now on if an Item description is available it will be shown.

Solution: 127909
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting multiple period transactions like "Sales Invoicing (Service)- Revenue Service Contract", a fatal error occurs.
And moreover this happens only if the Integration Parameter "Compression" is defined as
"Compr. by Trans. Origin" and "Handling of Document numbers" is defined as "Document Number by Date"
SOLUTION DESCRIPTION:
Now the fatal error does not arise while posting the integration transactions.

Solution: 127911
SITUATION IDENTIFIED IN:
"Service Order Activities" (tssoc2110s000)
SITUATION DESCRIPTION:
1. When changing the Planned Start Date on a released Activity which has material requirements linked to it, the
Delivery Date and/or Transaction Date (sessions "Outbound Order Lines"(whinh2120s000) and "Planned Inventory
Transaction by Order" whinp1501m000)) of the "allocated" item in the Warehousing package is updated.
However when doing this when also another Activity is present for the same Service Order which also has Material
requirements linked to it but which has a status lower then released (so free or planned), Error message "Address not
found for Warehouse ." (whinhs0113) is presented when the data should be updated in the Warehousing package.
2. When the planning method is "By Service Order Activity" (you can set this in the Service Order Parameters (tssoc0100s000), field "Planning Method"
(tssoc000.srpm)) then when changing the Planned Dates on the Activity the related Delivery Date on the Warehousing
"allocation" (as explained at point 1.) is not updated.
3. Inventory commitment for a Item of a material requirement linked to a Service Order Activity is not generated when the
"Outbound Lead time" of this Item is shorter then the time from the moment of releasing the activity to the desired
delivery date. (see session "Inventory Commitments" (whinp2500m000)) This is correct. If this occurs when releasing a single activity from session "Service Order Activities" (tssoc2110s000) question "Activity is Planned. Unprocessed Estimated Cost Lines will be deleted. Continue?" comes up. Pressing the yes button in
this case results in deletion of the Material requirement line for this Activity.
SOLUTION DESCRIPTION:
1. The Delivery Date of session "Outbound Order Lines" is now only updated for those Material Lines which are not linked to
an Activity or which are linked to Activities which have no lower status then status "Released".
The Transaction Date of session "Planned Inventory Transaction by Order" (whinp1501m000) is updated for Material lines
which are not linked to an Activity or which are linked to Activities which have no lower status then status "Planned".
2. When changing the Planned Dates on an Activity when the planning method is "By Service Order Activity" the related
Delivery Date or Transaction Date in the Warehousing package is updated as mentioned at point 1.
3. When releasing a single Activity from the Service Order Activity session which has material requirements linked to it,
the Activity is released and in case there is no Inventory Commitment generated, this is specified on the process report.
It is possible to manually create Inventory commitments via session "Inventory Commitments" (whinp2500m000) by
doubleclicking on the desired line and filling in the "Committed" field..

Solution: 127913
SITUATION IDENTIFIED IN:
"Copy Purchase Contracts" (tdpur3801m000)
SITUATION DESCRIPTION:
1. There is a Purchase Contract and in the contract lines, there is a valid Contact filled in.
2. This contract is copied to a new contract for another Business Partner and the Ship-from Business partner of the new
contract does not have the Contact mentioned in the source contract.
3. The system gives the following fatal error and it is not possible to copy the contracts.
++++++++++++++++++++++++++++++++++++++++++++++
Error 606 (Reference does not exist) on tdpur301300 in select
++++++++++++++++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
The Contact of the new Contract lines is taken from the Ship-from Business partner of the new contract and the fatal error
no more pops up.

Solution: 127916
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
The tab description on the first form of the session "Sales Order Line Details" (tdsls4101s200) is Dates_Quantities instead
of Dates & Quantities.
SOLUTION DESCRIPTION
The tab description is changed into Dates and Quantities.

Solution: 127920
SITUATION IDENTIFIED IN:
"Generate Order Advice" (whina3200m000)
SITUATION DESCRIPTION:
When running session whina3200m000 ("Generate Order Advice") for a SIC item assigned to a signal that is blocked for
Requisition (and free for everything else), the following message is returned "Item is blocked for production issue".
SOLUTION DESCRIPTION:
A new message has been created with the following text: "Item is blocked for requisition from production".
Session whina3200m000 ("Generate Order Advice") now shows "Item is blocked for requisition from production" instead of
"Item is blocked for production issue"

Solution: 127925
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
In the following situation, the warehouse code on an existing sales order line is blanked out by the order change message:
A sales order has been created via EDI. Subsequently, an order change message comes in with a change for the existing line
and adding a new line with a cost item (Release to Warehouse not checked in Item Sales Data (tdisa0101s000)). This results
in a blank warehouse on the changed line (with the normal item).
SOLUTION DESCRIPTION:
The warehouse code was blanked out in the situation described above due to an incorrect check on the "Release to Warehouse"
flag in Item Sales Data. The program script has been modified. Now the warehouse code remains unchanged if this is not an intended change.

Solution: 127934
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
When printing Project WIP by order, the financial transaction "Warehousing (transfer) / Issue to Project" is not considered
for the report, thus prints wrong WIP.
SOLUTION DESCRIPTION:
When project WIP is printed by order, the financial transaction "Warehousing (transfer) / Issue to Project" will be
considered.

Solution: 127935
SITUATION IDENTIFIED IN:
"Manual Invoice Lines" (cisli2125s000)
SITUATION DESCRIPTION:
When the user tries to enter a blank tax code in the Manual sales line and if a tax code has been defined for a geocode of the
ship-to address, then the tax code will always be defaulted, even if the user does not want it.
SOLUTION DESCRIPTION:
Now the tax code will be defaulted only for the first time. When the user changes it, then it will remain so.

Solution: 127939
SITUATION IDENTIFIED IN:
"Copy Contract to RFQ" (tdpur3210m000)
SITUATION DESCRIPTION:
A)
1. There is a purchase contract present for a cost item with release to WH YES in the tdipu001 record.
2. There is no Wh filled in the contract lines.
3. This contract is copied to a RFQ and as the WH is empty the RFQ line is created and the error report comes as "Release
to WH is YES and hence the warehouse has to be present".
4. Thus the RFQ line is not created. But the RFQ header is created.
B)
The series for generating the RFQ from the User Defaults should be defaulted to "Copy Contract to RFQ (tdpur3210m000)"
SOLUTION DESCRIPTION:
A)
The RFQ header is not created when there is an error at the time of RFQ lines creation.
B)
The RFQ series is defaulted to the session "Copy Contract to RFQ (tdpur3210m000)" from the User Defaults.

Solution: 127940
SITUATION IDENTIFIED IN:
"tdsls4247m000" (Release to Invoicing (batch))
SITUATION DESCRIPTION:
Amounts in home currency are incorrect in case of COGS transaction.
SOLUTION DESCRIPTION:
Amounts requested from "Get Costs Of Goods Sold" are rounded in Warehousing before returning to Sales.

Solution: 127941
SITUATION IDENTIFIED IN:
"Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000)
SITUATION DESCRIPTION:
When the report of session "Print Aging Analysis by Invoice-from Business Partner" (tfacp2420m000) was printed, the default
font on the report is being shown as "Near letter quality" which is a bigger font, hence the report doesn't fit on A4 paper.
SOLUTION DESCRIPTION:
The default font of all the reports of session "Print Aging Analysis by Invoice-from Business Partner" has been changed to
Small 17.1cpi.

Solution: 127943
SITUATION IDENTIFIED IN:
"Remove Contracts Incorrectly linked to Sales Orders" (tdcor0011m000)
SITUATION DESCRIPTION:
A Sales Order is raised with a line which has a Contract attached to the Business Partner and Item. A second line is raised
with a different Item that is not linked to any contract.
When the Shipment is confirmed, the second Order line which does not have any contract attached is also attached to the
contract, which is attached to the first line.
Correction Program requested for the correction of the corrupted data, due to this Software error.
SOLUTION DESCRIPTION:
Correction Program available to correct the contracts incorrectly linked to the Sales Orders (tdcor0100m000).
The correction program is used to remove the contracts that are incorrectly linked to the Sales Order.
The fields Table Updated : Link Order Line Data (tdsls402)
Fields Updated : Contract Number (tdsls402.cono)
: Position Number (tdsls402.posi)
How to use the session
===================
Give the range of all the records for which the Linked Order Data might have gone wrong.
1. Run the session with option 'Test Run', checked.
2. After checking the correctness of the Data, Run the session with the option 'Test Run', unchecked.
The correction program should be run in each operational company.
After running the Correction Program, it should be ensured that the Solution 127633 available for solving the problem, is
installed.

Solution: 127945
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When both net change flags in ordering item data and plan item data are set and the project for the project item is closed, the
session will hang.
SOLUTION DESCRIPTION:
When both net change flags for a closed project item have to be reset in a net change run, the program updates both these
records in a correct way.

Solution: 127949
SITUATION IDENTIFIED IN:
""Print Invoice-to Business Partner Balance Report" " (tfacr2424m000)
SITUATION DESCRIPTION:
In Print Business Partner's Balance (tfacr2424m000) the column "Advance/Unallocated Receipts" is wrongly updated.
SOLUTION DESCRIPTION:
In Print Business Partner's Balance (tfacr2424m000) the column "Advance/Unallocated Receipts" is correctly updated.

Solution: 127952
SITUATION IDENTIFIED IN:
"Schedule for Automatic Transactions" (tfgld0130s000)
SITUATION DESCRIPTION:
When a Service Integration transaction of type "Operation Cost" is linked to a schedule for automatic transactions, the
amounts of the automatic transaction lines in home currency are zero.This happens only for Single Currency system.
SOLUTION DESCRIPTION:
The amounts are correctly shown in the automatic transaction lines in home currency for Single Currency system when the
service integration transaction is of type "Operation Costs".

Solution: 127957
SITUATION IDENTIFIED IN:
"Bank Transaction" (tfcmg2100s000)
SITUATION DESCRIPTION:
Not able to reverse the reconciliation of an Advance/Unallocated receipt when different transaction types are used in the
same batch.
SOLUTION DESCRIPTION:
Now the Reconciliation can be reversed.

Solution: 127958
SITUATION IDENTIFIED IN:
"ATP Handling" (tdsls4899m000)
SITUATION DESCRIPTION:
Not able to change the Warehouse and Order Quantity in the session "ATP Handling " (tdsls4899m000) , when zoomed
from "Item Master Plan session " (cprmp2101m000) , as they are disabled.
SOLUTION DESCRIPTION:
The fields have been enabled for Input/Changing the data, if called from the "Item Master Plan session " (cprmp2101m000)
.

Solution: 127962
SITUATION IDENTIFIED IN:
"Patterns by Pattern Codes" (tdipu0120s100)
SITUATION DESCRIPTION:
Copy a pattern code of one pattern type (say Schedule Regeneration) to a different pattern type ( Say Shipping Schedule)
with the same pattern code. After saving the record, system displays the Pattern Type wrongly as "Schedule Regeneration"
even though the Pattern Code is correctly copied with the correct Pattern Type.
SOLUTION DESCRIPTION:
Now the system displays the correct pattern type even after saving the Pattern Code.

Solution: 127964
SITUATION IDENTIFIED IN:
"Purchase Order Change Code History" (tdpur5506m000)
SITUATION DESCRIPTION:
1. A purchase order is selected in the session "Purchase Orders" (tdpur4500m000).
2. With the specific menu option the user goes to "Purchase Order Change Code History" (tdpur5506m000) and the record
displayed there is the record seen when the session was opened last time and it does not correspond to the order selected
now.
SOLUTION DESCRIPTION:
The order displayed in "Purchase Order Change Code History" (tdpur5506m000) is the same as the one selected in
"Purchase Orders" (tdpur4500m000).

Solution: 127965
SITUATION IDENTIFIED IN:
"Manual Sales Invoice Headers" (cisli2120s000)
SITUATION DESCRIPTION:
When zooming on payment method, session displays both Receipt method and Payment method. But the session accepts
only Receipt methods.
SOLUTION DESCRIPTION:
Now instead of showing both Payment methods and the Receipt methods, the zoom shows only the Receipt methods.

Solution: 127966
SITUATION IDENTIFIED IN:
"Simulated Purchase Prices" (ticpr1170s000)
SITUATION DESCRIPTION:
For an independent currency company, if the simulated purchase price is modified and does the currency rotation, the price
in other home currencies will not be calculated based on the new price.
SOLUTION DESCRIPTION:
The simulated purchase price in other home currencies will be calculated, whenever the price is changed in one of the home
currencies, in an independent currency company.

Solution: 127968
SITUATION IDENTIFIED IN:
"Print Aging Analysis for customer" (tfacr2420m000)
SITUATION DESCRIPTION:
Some Receipts are not shown in aging analysis.
SOLUTION DESCRIPTION:
All valid Receipts are shown in aging analysis.

Solution: 127976
SITUATION IDENTIFIED IN:
"Planned PRP Warehouse Orders" (tppss6115s000)
SITUATION DESCRIPTION:
When we try to customize a revision controlled item by clicking the "make customized" button, the system copies the standard
structure to customized Item without the relevant engineering revisions. This is not correct since the relevant engineering
revisions also have to be copied.
SOLUTION DESCRIPTION:
The above problem is corrected and now if an item is customized, all the relevant engineering revisions will also be copied.

Solution: 127983
SITUATION IDENTIFIED IN:
"Ratings" (tdpur8106m000)
SITUATION DESCRIPTION:
The Overall Rating calculated as a consequence of manually changing the objective ratings in the session "Ratings"
(tdpur8106m000) and the rating actually calculated by running the session "Update Vendor Ratings" (tdpur8850m000) are
not the same. The one calculated in "Ratings" (tdpur8106m000) is always less than the one calculated from "Update
Vendor Ratings" (tdpur8850m000).
SOLUTION DESCRIPTION:
The rounding problems in the calculation of Overall Rating is solved now. Both the sessions would display the same Overall
Rating, when the same objective rating values are present.

Solution: 127989
SITUATION IDENTIFIED IN:
"Export Data Dictionary" (ttiex1280m000)
SITUATION DESCRIPTION:
Session "Export Data Dictionary" (ttiex1280m000) can export modified components from the current VRC, compared to a VRC
that can be filled in on the form. When components for the dump are selected NOT depending on a session, session "Export
Data Dictionary" (ttiex1280m000) can create a component list (files with names dump.l and dump.e) of the exported
components. Problem: the created component lists contain incorrect information. This occurs when the session displays the
following error message: "File ${BSE}// not present!"
The correct modified components are present in the created dumps, but the component list contains incorrect
information. In the dump.e file (errorfile), the information of the object is present. The object is correctly exported.
In the dump.l (list of components), the information of the source is present. The source is however not exported, because it could not be
found in the directory (as was mentioned in the error message).
SOLUTION DESCRIPTION:
The correct components were exported, but the component lists were not correct. When the source was not found, this error was added to the incorrect
component (the object). Now the correct component is first found before error information is added. The component for which the error was given is now present in the created dump.e file, and the correctly exported components are now present in the created dump.l file.

Solution: 127991
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
When transferring a call to a service order,the Address on the call is not being transferred as the Location Address of the
service order.This happens when the Address field is changed to something other than the address of the configuration
entered on the call.
SOLUTION DESCRIPTION:
The Address on a call will be transferred as the Location Address of the service order when a call is transferred to a service
order.

Solution: 127993
SITUATION IDENTIFIED IN:
"Copy Purchase Contracts" (tdpur3801m000)
SITUATION DESCRIPTION:
When a Purchase Contract is copied from one supplier to another. The ship from address is taken from the source contract
rather than taking the default address of the new ship from BP.
SOLUTION DESCRIPTION:
Now the problem is solved, the system will pick up the correct address when the user is coping the contracts from one
business partner to another.

Solution: 127999
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Item and Warehouse " (whina1210m000)
SITUATION DESCRIPTION:
System gives the float exception fatal error when running the Inventory valuation for a warehouse with negative stock.
SOLUTION DESCRIPTION:
The float exception does not come now.

Solution: 128001
SITUATION IDENTIFIED IN:
"Purchase Change Order Sequence Numbers (tdpur4114m000)" (tdpur4114m000)
SITUATION DESCRIPTION:
When user zooms from "Purchase Orders (tdpur4500m000)" session to the session "Purchase Change Order Sequence
Numbers (tdpur4114m000)", system doesn't zoom to the correct purchase order number.
SOLUTION DESCRIPTION:
Now, system zooms to the session "Purchase Change Order Sequence Numbers (tdpur4114m000)" from "Purchase Orders
(tdpur4500m000)" session and displays the correct purchase order number and its details.

Solution: 128003
SITUATION IDENTIFIED IN:
"Print Purchase Orders" (tdpur4401m000)
SITUATION DESCRIPTION:
When we create a back order and print the back order , an EDI message is created for the original order along with the back
order
SOLUTION DESCRIPTION:
Now the EDI message is created for the original line with sequence 0 only once and when we print the back order , EDI
message for back order was only created

Solution: 128019
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
When Journal transactions involving bank or unallocated receipts transactions between two companies are posted, they are
posted to wrong Contra account
SOLUTION DESCRIPTION:
Now correct contra account is picked up

Solution: 128026
SITUATION IDENTIFIED IN:
"Posting Data of Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
Amount field in session 'Posting Data of Electronic Bank Statements' (tfcmg5106s000) is disabled at first entry of posting
data although user should be able to maintain this field when creating posting data.
SOLUTION DESCRIPTION:
Amount field can be accessed at first entry of posting data.

Solution: 128031
SITUATION IDENTIFIED IN:
"Classify Items" (tigrt0180m000)
SITUATION DESCRIPTION:
When using "answer groups" of type "Answer & Follow-up", the return values of the original question and sub-sequent
follow-up questions stay blank during classification of a part.
SOLUTION DESCRIPTION:
The return value is filled as per the return value of the answers

Solution: 128035
SITUATION IDENTIFIED IN:
"Contract Coverage Terms" (tsctm1120s300)
SITUATION DESCRIPTION:
When copying coverage terms for a service contract from a contract template or a contract quotation,the effective date and
expiry date are not being copied to the contract coverage terms.
SOLUTION DESCRIPTION:
When copying from a template to a service contract, the effective and expiry dates are copied from the service contract
header to the contract coverage terms.
When processing a contract quotation to a service contract, the effective and expiry dates on the contract quotation coverage
terms are copied to the service contract coverage terms.

Solution: 128036
SITUATION IDENTIFIED IN:
"Transaction Sales Invoices" (tfacr1111s000)
SITUATION DESCRIPTION:
When the "Level of Tax calculation" is set on the Transaction line, the default vat code is not displayed
SOLUTION DESCRIPTION:
Now the default vat code is picked up and displayed.

Solution: 128038
SITUATION IDENTIFIED IN:
"PRP Warehouse Orders" (tppss6115s000)
SITUATION DESCRIPTION:
The date below Planned Order time and Planned delivery time does not have a proper attribute name
SOLUTION DESCRIPTION:
The label Transaction time is missed while exporting the solution 114943.Now the form is proper

Solution: 128039
SITUATION IDENTIFIED IN:
"Print Reminder Letters" (tfacr3420m000)
SITUATION DESCRIPTION:
No Reminder letter number is printed for Negative unallocated receipts and Negative advance receipts
SOLUTION DESCRIPTION:
Reminder Letter is printed for Negative unallocated receipts and Negative advance receipts

Solution: 128041
SITUATION IDENTIFIED IN:
"Financial interim results" (tpppc2560m000)
SITUATION DESCRIPTION:
Even when a finacial results in later period is present for a project system allows to close the project in the current period.
SOLUTION DESCRIPTION:
While processing the transaction there is already a check on all cost types ...now a check on financial results is also been
built which solves the above problem.

Solution: 128044
SITUATION IDENTIFIED IN:
"whinh4275m000" (Confirm Shipments/Loads)
SITUATION DESCRIPTION:
-1- When confirming an over-delivery shipment (the quantity shipped is greater than the ordered quantity of the outbound line
linked to the warehouse order), the following data should have been updated as well so that the over-delivered quantity
(over-delivered quantity = delivered quantity - original order quantity) could be taken into account:
- the sales order history
- the contract called quantity
- the order balance
-2- When running the session "Process Delivered Sales Orders" (tdsls4223m000) with the option "Delete Order Data" ON,
some Sales Order Line Records for a specific Sales Order Line could be deleted even if some of the records linked to the
same Sales Order Line had not yet been processed in the session "Process Delivered Sales Orders" (tdsls4223m000).
-3- When a Sales Order Line is split when processing a partial shipment (in this case the status of the corresponding
Outbound Line remains "Adviced/Staged" as an Outbound Advice Line should still be shipped), the Sales Order History is
not updated.
The following updates would then be expected :
Sales Order Line Order Quantity
Sequence Number (tdsls401.sqnb) (tdsls401.oqua)
0 10 (inserted when creating the Sales Order Line)
0 -10 (when the Detail line becomes a Total line due to the "Split Sales Order Line")
1 4 (when inserting the Sales Order Line with the sequence 1 --> if 4 has been delivered)
2 6 (for the remaining order quantity)
SOLUTION DESCRIPTION:
-1- The sales order history, the contract called quantity and the the order balance will now be properly updated.
-2- A Sales Order Line can only be deleted if ALL the Sales Order Line Records linked to a specific Sales Order Line have
been processed in the session "Process Delivered Sales Orders" .
-3- The Sales Order History will now be properly updated (according to the above example).

Solution: 128046
SITUATION IDENTIFIED IN:
"Maintain Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
System gives error message "Net quantity of phantom component may not be zero" when creating the Production Order and it
is not possible to create a production order. This happens when the bom unit or the bom quantity is huge and net quantity is
very small.
SOLUTION DESCRIPTION:
System allows creating a production order even when the bom unit or the bom quantity is huge and the net quantity of the
component is very small.

Solution: 128047
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
When the changed amount is more than the defaulted amount, no warning message is given.
SOLUTION DESCRIPTION:
Earlier, no warning message was given.
Now, a warning message is given if the changed amount is more than the defaulted amount

Solution: 128049
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
1. A Sales return order is created.
2. The order quantity of the sales order is equal to the negative inventory present for the item in that warehouse.
3. Also the Warehouse Order type attached to the Sales Return order has "Approvals" (whinh3522m000) as an activity.
4. The Sales order is received in the warehouse and the Delivered quantity and the status of the Sales Order Line are not
updated due to this receipt.
SOLUTION DESCRIPTION:
Generally the Delivered quantity of the Sales order line would be updated at the time the Approval is done. In this case all
the received quantity has been consumed by the Negative Inventory that was already present. In this case no Inspection
record was created and hence the status of the Sales Order Line was not also updated. In such cases where the received
quantity is consumed by negative inventory, the delivery quantity and the status of the Sales Order Line is updated at the
time of Receipts confirmation.

Solution: 128050
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
If a bilateral invoicing relation is set up between the warehouses of a Manual Transfer Order and the transfer price is
defined as the Commercial Price, it is not possible to add more than 1 Outbound Order Line to the Warehouse Order (even if
the Transfer Price in the Warehouse Order Header is set to 0).
SOLUTION DESCRIPTION:
It is now possible to add a more than 1 Outbound Line to the Manual Warehouse Transfer Order, as long as the Transfer
Price in the Warehouse Order Header is not filled in.

Solution: 128052
SITUATION IDENTIFIED IN:
"Purchase Change Order Sequence Numbers (tdpur4114m000)" (tdpur4114m000)
SITUATION DESCRIPTION:
When user zooms from "Purchase Order Lines (tdpur4501m000)" session to the session "Purchase Change Order Sequence
Numbers (tdpur4114m000)", system doesn't zoom to the correct purchase order number.
SOLUTION DESCRIPTION:
Now, system zooms to the session "Purchase Change Order Sequence Numbers (tdpur4114m000)" from "Purchase Order
(tdpur4501m000)" session and displays the correct purchase order number and its details.

Solution: 128058
SITUATION IDENTIFIED IN:
"Create Sequential Dump of Table" (ttaad4226m000)
SITUATION DESCRIPTION:
Strange text (the three characters: @#$) was added in error file field of session "Create Sequential Dump of Table"
(ttaad4226m000) when running the session more then once.
SOLUTION DESCRIPTION:
The characters "@#$" are only added once to the name of the error file. When the session is executed a second time a test
is done on the presence of "@#$". If these characters are present, they are not added anymore. In the name of the error file,
which is dumped to the file system, these three characters are replaced with the company number.

Solution: 128060
SITUATION IDENTIFIED IN:
"Financial Interim Results" (tpppc2160s000)
SITUATION DESCRIPTION:
Cost Control Year/Period & Fiscal Year/Periods are defaulted based on the Registration date when the session opens. But, if
we change the Registration to a date in another Period, the Cost Control Year/Period & Fiscal Year/Periods are not changed.
These year & periods are expected to change as date changes, as in cost sessions.
SOLUTION DESCRIPTION:
The script has been modified to change the Cost Control Year/Period & Fiscal Year/Periods as soon as the date is changed.

Solution: 128065
SITUATION IDENTIFIED IN:
"Currency Rates" (tcmcs0108m000)
SITUATION DESCRIPTION:
In a Multi Site setup when table tcmcs008 (Currency Rates) is shared a problem may arise when the End User is trying to insert
new currency rates with an effective date before the last Cost Price calculation date.. This is due to the fact that the general
item data tables (tcibd001/tcibd007) are not shared over the same set of companies.
SOLUTION DESCRIPTION:
From now onwards, the check for the last performed Cost Price Calculation will not only check Item Costing Data (tcibd007) in
the current company, but also the other logistical companies in which tcmcs008 (Currency Rates) is shared.

Solution: 128070
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
The label of the form field "Hold Back Quantity" is missing for the following forms in GERMAN:
- tdsls4101s0001 (General)
- tdsls4101s0007 (Inventory)
SOLUTION DESCRIPTION:
The label is now properly appearing in the forms mentioned above.

Solution: 128071
SITUATION IDENTIFIED IN:
"Item Purchase Data" (tdipu0101s000)
SITUATION DESCRIPTION:
The Buy-From Business partner in the session "Item Purchase Data" (tdipu0101s000) is a mandatory field. But the system
allows the user to save the record with out filling this field.
SOLUTION DESCRIPTION:
The user should enter the Buy-from BP. Other wise, the system is not allowing the user to save the record.

Solution: 128077
SITUATION IDENTIFIED IN:
"maintain address info" (tccom4130s000)
SITUATION DESCRIPTION:
Extra fields required for local Tax number for Germany and Swift-nr + Bankid
SOLUTION DESCRIPTION:
New table defined (Extra address info (tccom133)) and software is modified/added to handle this new table and fields.

Solution: 128086
SITUATION IDENTIFIED IN:
"General Actual Project Costs" (tipcs3540m000)
SITUATION DESCRIPTION:
When the session "General Actual Project Costs" (tipcs540m000) is called from sessions "Purchase-Invoice Transactions"
(tfacp1120s000) or Journal Vouchers (tfgld1114s000) , the session defaults with the data of the last project defined by the user
and if not available, it defaults with the first pcs project with status active even when no project data is defined for that
particular purchase invoice.
SOLUTION DESCRIPTION:
When the session "General Actual Project Costs" (tipcs540m000) is called from session "Purchase-Invoice Transactions" (tfacp1120s000) or Journal Vouchers (tfgld1114s000), the session defaults with the project defined for that particular purchase invoice. And if there is no project data defined for that particular purchase invoice then, the system defaults with a blank screen indicating that no project data had been defined.

Solution: 128088
SITUATION IDENTIFIED IN:
"Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
For generic item, system is giving the message "Configure product variant now?" twice.
SOLUTION DESCRIPTION:
Now the problem is solved, the system will give the message "Configure product variant now?" only once.

Solution: 128090
SITUATION IDENTIFIED IN:
"Export Financial Statement Values" (tffst1205m000)
SITUATION DESCRIPTION:
A new statement account is created with 35-character description. But after running 'Process Financial Statement Values'
session, the description is cut to 30 characters.
SOLUTION DESCRIPTION:
Earlier, the whole description of the 'Statement Account' was not stored in the table 'Financial Statement Values'.
Now, the whole description (with 35 characters) is stored in the table 'Financial Statement Values'.

Solution: 128095
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
The Balance amount is being calculated incorrectly once the user assigns Unallocated Receipt to an Invoice.
SOLUTION DESCRIPTION:
Now the user can assign an invoice to an Unallocated Receipt and the balance amount is being calculated perfectly

Solution: 128099
SITUATION IDENTIFIED IN:
"Assign unallocated / Advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
The control account checklist showed a difference when an unallocated receipt in home currency was linked to an invoice
with reference currency
SOLUTION DESCRIPTION:
No difference on the control account checklist when an unallocated receipt in home currency is linked to an invoice with
reference currency

Solution: 128104
SITUATION IDENTIFIED IN:
"Billing Request Template" (cisli2101s000)
SITUATION DESCRIPTION:
"Record Already Exists" error, while saving a Billing Request Template.
It happens in the following situation.
1. The user copies an existing template to a new template and clicks the 'Save' button.
2. A question is asked whether the user wants to change the priority or not.
3. The user selects the option 'Yes', and then select the 'Priority' field and change it.
4. Now if he saves the record, the error message appears.
SOLUTION DESCRIPTION:
Now the error message does not appear.

Solution: 128106
SITUATION IDENTIFIED IN:
"Purchase Contracts" (tdpur3500m000)
SITUATION DESCRIPTION:
1. The language of the User and the language of the Buy-from Business partner of the contract are different.
2. The contract header text entered in "Purchase Contracts" (tdpur3100s000) is not seen in the multi occurrence session
"Purchase Contracts" (tdpur3500m000), when the user presses the text button. The text editor window is displayed with out
any text.
SOLUTION DESCRIPTION:
The text in the multi occurrence session "Purchase Contracts" (tdpur3500m000) can be viewed now. The text that is entered
in the single occurrence is displayed.

Solution: 128107
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When the amount in the sales credit note is modified, Wrong message "Credit note amount should not be greater than the
Original Invoice Amount" even though it is less than the original invoice amount
SOLUTION DESCRIPTION:
Now the message is not displayed if the Credit note amount is less than Original invoice amount

Solution: 128109
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Receipt schedules gets deleted when the user changes the due date for the invoice
SOLUTION DESCRIPTION:
Now the schedules are not deleted when the due date of the invoice is modified

Solution: 128120
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Specifications" (tfacp1432m000)
SITUATION DESCRIPTION:
In session "Print Receivable Invoices Specifications" (tfacp1432m000) a new option is required to select the "Approval
Date" range.
SOLUTION DESCRIPTION:
A new option has been added on the form to enter the approval date range. Because of this new modification, orders are
printed which are in the receipt date range but which are not completely approved in the approval date range.

Solution: 128122
SITUATION IDENTIFIED IN:
"Bills of Material" (tibom1110m000)
SITUATION DESCRIPTION:
System is not displaying the standard routing operations, when the routing code is linked to standard routing, if the user
zooms to the session "Routing Operation", from the field "operation" in the session "Bills of Material".
SOLUTION DESCRIPTION:
System will display standard routing operations only, when the routing code is linked to standard routing, if the user zooms
to the session "Routing Operation", from the field "operation" in the session "Bills of Material".

Solution: 128126
SITUATION IDENTIFIED IN:
"Inventory By Production order" (tisfc0516m000)
SITUATION DESCRIPTION:
Operations are linked to the materials in BOM (Bill of Materials ) for an Item. The planning method for a Production order of
the Item is backward and if the delivery date is changed, then the allocation dates (or transaction dates) of the materials are
not changed accordingly.
SOLUTION DESCRIPTION:
The dates of the materials linked to Operations are changed accordingly, if the dates of the backward planned Production
order are changed.

Solution: 128129
SITUATION IDENTIFIED IN:
"Print Project Costs and Revenues" (tipcs3490m000)
SITUATION DESCRIPTION:
When changing the price of a customized item after delivery, but before invoicing the delivery, the changed price was not
reflected when running session "Print Project Costs and Revenues" (tipcs3490m000).
Instead the calculation would always be based on the item 's price as it was at order entry.
SOLUTION DESCRIPTION:
When calculating and printing the Project Costs and Revenues the calculation was done on the total ordered amount of a
particular order line.
When partially delivering a given order line, and changing the involved item 's price afterwards, before the order was
released to invoicing, this changed price would not be reflected by a changed expected revenue.
From now on the calculation will be done per order line detail. When a given order had not been released yet to invoicing the
price will be updated on the order line detail. As a result the calculation of the project costs and revenues now will reflect
this changed item price.

Solution: 128132
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
The system takes very long time to confirm the shipments.
SOLUTION DESCRIPTION:
The performance has been improved now and the time taken for the shipment confirmation is reduced now.

Solution: 128139
SITUATION IDENTIFIED IN:
"Maintain Dependencies" (ttpmc1140s000)
SITUATION DESCRIPTION:
In the session "Maintain Dependencies" (ttpmc1140s000) it was possible to define dependencies between two released PMC
solutions. This should never be allowed, because this dependency data will never be exported to a customer system.
A second problem was that it was not possible to add a post-requisite dependency to a solution, which belongs to an already
released patch (Service Pack). There is no reason why this should not be allowed.
Finally, co-requisite dependencies to a released solution could be deleted even when that solution also pointed back to the
current solution.
SOLUTION DESCRIPTION:
The problems mentioned are solved:
- No dependency can be created anymore between two released solutions.
- Post-requisite dependencies can be added to a solution, although it belongs to a released patch.
- Co-requisite dependencies cannot be deleted when the other (released) solution points also to the current solution.
Note that this solution only applies to the distributor side of PMC. No modifications have been made in PMC Recipient.

Solution: 128140
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation " (tfcmg2123s000)
SITUATION DESCRIPTION:
Auto Payment Reconciliation form gets the wrong total amount.
SOLUTION DESCRIPTION:
Now the Total Amount will be displayed correctly when saving the form and usage of the "Refresh (F5)" option is
recommended once after the "Saving" operation is carried out in the form.

Solution: 128141
SITUATION IDENTIFIED IN:
"Generate Configuration Structures" (tscfg2210m000)
SITUATION DESCRIPTION:
BOM items of item type purchased are not copied to the new or existing configuration when generating a configuration
structure from a sales order.
SOLUTION DESCRIPTION:
BOM items of item type manufactured and purchased are copied to the configuration structure.

Solution: 128145
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Several Forms were not properly delivered with the SOLUTION 126042.
As a consequence, some of the labels did not appear on the forms.
SOLUTION DESCRIPTION:
The forms have been delivered again.

Solution: 128156
SITUATION IDENTIFIED IN:
"Clear Corrupted Inventory" (whcor0200m000)
SITUATION DESCRIPTION:
When running session "Clear Corrupted Inventory" (whcor0200m000), for all lot controlled items a check was performed on the
allocated and on order quantity. A message is displayed if one of these quantities is greater then 1.
The following message is printed: 0030 "Lot size of lot XXXX is not allowed to be greater then 1.0".
SOLUTION DESCRIPTION:
This check is now only executed for lot-by-unit items.

Solution: 128160
SITUATION IDENTIFIED IN:
"Object Relations" (tscfg2510m000)
"Service BOM's" (tscfg1510m000)
SITUATION DESCRIPTION:
In the specific menu the options "Zoom Up" and "Zoom Down" are missing.
SOLUTION DESCRIPTION:
"Zoom Up" and "Zoom Down" are available.

Solution: 128161
SITUATION IDENTIFIED IN:
"Archive Inventory Transactions by Item and Warehouse" (whinr1210m000)
SITUATION DESCRIPTION:
When archiving/deleting is done, inventory receipt transaction consumptions with a date greater than the entered date can be
deleted.
This is because only the date of the inventory receipt transactions is checked and not the date of the related inventory
receipt transaction consumptions.
Example:
100 Pieces of item A are received on 31-12-2000 Complete consumption of this receipt takes place on 01-01-2002
If session "Archive Inventory Transactions by Item and Warehouse" (whinr1210m000) is executed for this item with cutoff
date 01-01-2001, both the inventory receipt transaction and the inventory receipt transaction consumption are deleted despite
of the fact that the consumption date is greater then the cutoff date. This is wrong, in this case nothing must be deleted.
SOLUTION DESCRIPTION:
The date of the inventory receipt transaction consumptions is checked properly, so that only inventory transactions within
the date boundary are deleted.

Solution: 128166
SITUATION IDENTIFIED IN:
"Price Calculator" (tdpcg0200m100)
SITUATION DESCRIPTION:
1. The 'Update Default Price Book' is NO in "Pricing Parameters" (tdpcg0100s000)
2. Due to this the default price book is not created when an item is created.
3. The price calculator displays the default price book when calculated for the above item, even though the price is not
retrieved from the default price book. The price is actually retrieved from the "Item Purchase Data" (tdipu0501m000)
SOLUTION DESCRIPTION:
When the 'Update Default Price Book' is NO in "Pricing Parameters" (tdpcg0100s000) and there is no other price book for the
item, then the Price book and Price book description are shown as blank in the Price Calculator.

Solution: 128167
SITUATION IDENTIFIED IN:
"Generate Inventory Commitments" (whinp2200m000)
SITUATION DESCRIPTION:
After generating an outbound advice , if we generate inventory commitment for a service order , duplicate commitments are
generated
SOLUTION DESCRIPTION:
Now the system checks for the existing outbound order line in warehousing and finds the related line with correct sequence
number and doesn't generate duplicate commitments

Solution: 128168
SITUATION IDENTIFIED IN:
"Purchase Requisitions" (tdpur2501m000)
SITUATION DESCRIPTION:
When we select a record in the session tdpur2501m000 and hit the print button , the record is not defaulted to the print
session .
SOLUTION DESCRIPTION:
Now the record is defaulted to the print session .

Solution: 128172
SITUATION IDENTIFIED IN:
"Interest Invoice details" (cisli2110s000)
SITUATION DESCRIPTION:
Zooming on the Payment method displays both the receipt methods and the Payment methods.
SOLUTION DESCRIPTION:
Now the zooming displays only the receipt methods.

Solution: 128175
SITUATION IDENTIFIED IN:
"Print Vendor Ratings" (tdpur8402m000)
SITUATION DESCRIPTION:
When session "Print Vendor Ratings (tdpur8402m000)" invoked from session "Vendor Ratings by Periods (tdpur8102m000)",
some of the relevant information is not defaulted.
SOLUTION DESCRIPTION:
Now the problem is solved, the relevant information will be defaulted if the session "Print Vendor Ratings
(tdpur8402m000)" is invoked from session "Vendor Ratings by Periods (tdpur8102m000)".

Solution: 128187
SITUATION IDENTIFIED IN:
"Maintain Lots" (whltc1100s000)
SITUATION DESCRIPTION:
The lot Date could not be calculated under a very specific condition.
If the item is :
-1- lot controlled and
-2- has a shelf life that is in MONTHS or YEARS and
the date on which the lot is created is the 29th, 30th or 31st (of any month) and
the number of months or years ( in the field "shelf life") would make the calculated month equal to February,
then the date field is cannot be calculated
SOLUTION DESCRIPTION:
The lot date will now be properly calculated.

Solution: 128189
SITUATION IDENTIFIED IN:
"Copy RFQ lines to Contracts/Orders" (tdpur1202m000)
SITUATION DESCRIPTION:
1. A RFQ line is created and then linked suppliers to that.
2. The RFQ is printed and sent to the suppliers.
3. Instead of the quotation asked for, the supplier sends an alternative quotation. This is done by adding new record in
"Supplier Quotation" (tdpur1506m000).
4. This line is set to the status Returned.
5. After this when the RFQ is copied to purchase order, the system gives "No data within Selection"
SOLUTION DESCRIPTION:
The Alternate Supplier quotation is now copied to purchase order.

Solution: 128193
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
Document number was not printed on the posted EBS bank Statement Report after posting the EBS batch.
SOLUTION DESCRIPTION:
Now Document number is printed on the posted EBS bank Statement Report after posting the EBS batch.

Solution: 128197
SITUATION IDENTIFIED IN:
"Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
When transactions are maintained (Batch and transaction keys and the transaction lines) in financial company, it allows
deleting the transaction type, even though there are transactions present, when a Non-Finalized transactions (tfgld102) is
not shared between the Group Company and the financial company.
SOLUTION DESCRIPTION:
When transactions are maintained (Batch and transaction keys and the transaction lines) in financial company and if one of the transaction keys is deleted, then the system pops up a error message, "Transactions present; first delete all transactions", when a Non-Finalized transactions (tfgld102) is not shared between the Group company and the financial company.

Solution: 128213
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is possible to use a General Ledger account for which Integration Indicator is set to PCS Cost / Sales for Cost Item. This
should not be possible, as this will pose problems while posting the Integration Transactions. An Error Log "GL account is
set to PCS project cost' will be logged.
SOLUTION DESCRIPTION:
Now it is not possible to add a General Ledger Account for which Integration Indicator is set to PCS Cost / Sales for Cost Item.
An Error Message "Ledger account may not have projects" is displayed and it is not possible to enter such General Ledger Account.

Solution: 128227
SITUATION IDENTIFIED IN:
"Print Purchase order receipt data" (tdpur4431m000)
SITUATION DESCRIPTION:
The user could be given the option to select the receipt for printing based on the Delivery Date of the purchase order lines.
SOLUTION DESCRIPTION:
The Delivery date selection range is inserted in the session and based on the values entered in these fields, the receipts
would be selected and printed.

Solution: 128229
SITUATION IDENTIFIED IN:
"Report Operations Completed" (tisfc0130s000)
SITUATION DESCRIPTION:
When a reversal is made to an order to correct an over-reported quantity using session "Report operations
completed"(tisfc0130s000), the 'On Order' value becomes negative/incorrect in the session "Inventory by Warehouse and
Item" (whwmd2515m000).
SOLUTION DESCRIPTION:
The 'On Order' quantity of an item will never be a negative value at any point of time.

Solution: 128243
SITUATION IDENTIFIED IN:
"Generate Bills of critical capacities" (tirou2230m000)
SITUATION DESCRIPTION:
When the user save the defaults for the session Generate Bills of critical capacities, While running the session Generate Bills
of critical capacities via Bills of critical capacities, System will show the default From and To Plan Item instead the Plan
Item in the parent session.
SOLUTION DESCRIPTION:
When the user save the defaults for the session Generate Bills of critical capacities, While running the session Generate Bills
of critical capacities via Bills of critical capacities, System will show From and To Plan Item as Plan Item in parent session.

Solution: 128250
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When "Customer Order number" field is filled in the sales order and when the invoice prints this data, then some junk value
is printed in the invoice along with the customer order number.
SOLUTION DESCRIPTION:
Now the invoice is printed correctly.

Solution: 128251
SITUATION IDENTIFIED IN:
"Hours Accounting by Employee" (tihra1501m000)
SITUATION DESCRIPTION:
While modifying records in "Enter Hours accounting by Employee", Week Seq. number increases when parameter "Hours
Accounting Type=Day/Employee".
SOLUTION DESCRIPTION:
Week Seq. number will not increase while modifying records in "Enter Hours accounting by Employee", increases when
parameter "Hours Accounting Type=Day/Employee".

Solution: 128252
SITUATION IDENTIFIED IN:
"Maintain Quotation Lines" (tdsls1101m000)
SITUATION DESCRIPTION:
It is not possible to create a quotation line without item.
SOLUTION DESCRIPTION:
It is now possible to create a quotation line without an item.
The message "Item not filled. Please enter a text for this quotation line" will appear.

Solution: 128254
SITUATION IDENTIFIED IN:
"Display Payment Details" (tfacp2524s000)
SITUATION DESCRIPTION:
Session "Display Payment Details" (tfacp2524s000) is displaying a wrong value of check number, and is inconsistent with
the display of check number in session "Display Payments on Purchase Invoices" (tfacp2523s000) which is displaying a
correct value.
SOLUTION DESCRIPTION:
The session "Display Payment Details" displays correct value of check number and is consistent with the session "Display
Payments on Purchase Invoices".

Solution: 128258
SITUATION IDENTIFIED IN:
"Journal Voucher" (tfgld1103s000)
SITUATION DESCRIPTION:
1) Local currency rate was not picked up at the JV header transaction and due to this user can't add the records.
2) When you add the second line in the JV transaction lines, dimension description was not refreshed.
SOLUTION DESCRIPTION:
1) Local currency rate picked up correctly and user can add the records.
2) Dimension description was refreshed properly when you add the new line in Journal voucher.

Solution: 128262
SITUATION IDENTIFIED IN:
"Service-Order Quotations" (tssoc1100s000)
SITUATION DESCRIPTION:
There are 2 "Recalculate" buttons present in this session. Both have the same behaviour when pressed.
SOLUTION DESCRIPTION:
It is quite confusing having 2 "Recalculate" buttons present in this session. The button "Recalculate" on the right (below
the button "Appointment...") is superfluous and therefore it has been removed.

Solution: 128265
SITUATION IDENTIFIED IN:
"Enterprise Planning"
SITUATION DESCRIPTION:
Within Baan IV and Baan ERP the 'infinite planning' and workload control' is available.
'Cyclic planning' is not and will not be available for customers, and will not be supported.
SOLUTION DESCRIPTION:
Option 'Cyclic Planning' is removed from menu and EP parameters.
For customers insisting to use 'cyclic planning' we would like to encourage them to investigate together with their Baan
representative to take a critical look at their business requirements if 'infinite planning' and/or 'workload control' can be
alternative solutions.
If 'cyclic planning' is the only possible solution to meet the business requirements of customers we advise to investigate
alternative Baan Products, such as Supply Chain Solutions.

Solution: 128267
SITUATION IDENTIFIED IN:
"menu browser" (ttdskmbrowser)
SITUATION DESCRIPTION:
The online help for contents is not available when using ASCII help.
SOLUTION DESCRIPTION:
When using ascii help now correct help is displayed

Solution: 128272
SITUATION IDENTIFIED IN:
"Archive Cycle Counting History" (whinh5250m000)
SITUATION DESCRIPTION:
When selecting the option "both" (archive and delete), the cycle counting headers are all archived and deleted correctly but
only the lines of the first order are archived and deleted. The lines for the following orders stay in the source company and
are not present in the archive company. Result : in the archive company, the cycle counting order headers without lines are
present and in the source company, the lines are still present.
SOLUTION DESCRIPTION:
The lines of the cycle counting order headers will now be properly archived as well.

Solution: 128273
SITUATION IDENTIFIED IN:
"Select values for GRNI reconciliation" (tfacp1235m000)
SITUATION DESCRIPTION:
Depending on the wideness of the selection range of year and periods the process ends often with a "Connection lost".
SOLUTION DESCRIPTION:
Although the error is also sometimes received on the development machine, it is still not clear why the connection with the
database got lost.
However the user indicates that SL125366 has caused this problem and that is why this SL has been programmed in a
different way and the error could not be reproduced any more on the development machine.

Solution: 128276
SITUATION IDENTIFIED IN:
"Print BaanProject Financial Reconciliation" (tcfin2400m000)
SITUATION DESCRIPTION:
When printing the BaanProject Financial Reconciliation, the report with "totals by Ledger Accounts" turned out to be
incorrect. The root cause was the debit record printed twice, in stead of both the debit and credit part of the transaction.
SOLUTION DESCRIPTION:
When printing the BaanProject Financial Reconciliation, the report with "totals by Ledger Accounts" is now printed correctly.
First the debit part of the transaction will be printed, and after this the credit part of the transaction will be printed.

Solution: 128282
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40c
127106, 127830, 127874
Defects solved in B50b
127763, 209308, 209564, 209851
Defect solved in 71a
123192, 127763
Descriptions:
- Defect 123192 Don't raise multi occ when refresh from single occ
- Defect 127106 Busy cursor should be displayed during first event
- Defect 127763 AFS second synchronize dialog fails
- Defect 127830 AFS Insert of multiple records fails
- Defect 127874 AFS put fields did not arrive in session
- Defect 209308 Empty occurrences where displayed as enabled for input
- Defect 209564 QBF sorting caused fatal error during last set.
- Defect 209851 Grid data not correct after scrolling and switch form
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 128283
SITUATION IDENTIFIED IN:
"Display Ishikawa Diagram" (tgeis0521m000)
SITUATION DESCRIPTION:
When I want to look at the Chart with a Node, for which no data is present, then I get a float-exception.
SOLUTION DESCRIPTION:
The internal function used for calculating the data could not handle a zero value. We changed this and now it works good.

Solution: 128285
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When running "Register Purchase Invoices (tfacp1110s000)"
The system allows user to save duplicate "Business Partner Invoice number".
SOLUTION DESCRIPTION:
When running "Register Purchase Invoices (tfacp1110s000)"
The system does not allow user to save duplicate "Business Partner Invoice number" anymore.

Solution: 128288
SITUATION IDENTIFIED IN:
"Print Fixed Asset - General Ledger Reconciliation report" (tffas0442m000)
SITUATION DESCRIPTION:
If the setup has been executed in FAS, then the FAS transactions are posted to finance up to the setup executed year and
period. But document numbers are not updated in the FAS transactions, hence these records are not getting considered on the
"Print Fixed Asset - General Ledger Reconciliation report".
SOLUTION DESCRIPTION:
If the setup has been executed, which can been seen in the FAS parameters (form 5), then up to the setup executed year and period, the document number
check is not done for posted transactions to finance. Hence these FAS transactions will be considered on the report.

Solution: 128298
SITUATION IDENTIFIED IN:
"Copy Purchase Orders" (tdpur4201s000)
SITUATION DESCRIPTION:
1. There is a Purchase Order Line with back orders.
2. This Order is copied to a new order with the 'Cumulate Receipts' check box selected. The Detail line and the Back order
line are selected.
3. The Order Quantity of the newly copied line adds the order quantity of the Detail line and the Back order line.
SOLUTION DESCRIPTION:
The Quantity of the copies line is correct now.

Solution: 128303
SITUATION IDENTIFIED IN:
"Maintain Posting Data of Approved Invoices" (tfacp1141s000)
SITUATION DESCRIPTION:
When approving the average last purchase price is updated using the rate applicable at the date of approving. This is wrong
because the date of the invoice should be used.
SOLUTION DESCRIPTION:
When approving the date of the invoice is used determining the rate used for updating that average last purchase price.

Solution: 128309
SITUATION IDENTIFIED IN:
"Archive Warehousing Order History" (whinh2255m000)
SITUATION DESCRIPTION:
1. The Production order had Warehousing orders of transaction type Issue and Receipt.
2. While Archiving the history of such Warehouses orders, the history of the Inbound Data is not archived.
SOLUTION DESCRIPTION:
Now both the Inbound Data and the Outbound Data are archived.

Solution: 128316
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements/RMAs" (tdsls4401m000)
SITUATION DESCRIPTION:
If the Alternative Item Code is filled, that is, the name of the Alternative Item Code extends till the last character of the
field, then the Alternative Item Code is not fully printed, the last character is lost. It is overlapped with the Item description.
SOLUTION DESCRIPTION:
The overlapping has been avoided now, and the Alternative Item Code is fully printed.

Solution: 128320
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
The item revisions are incorrectly updated in the production order, when a revision control item is changed to another
revision control item in a production order with status 'Planned'.
SOLUTION DESCRIPTION:
The item revisions are updated correctly with the revisions of the changed revision control item in the production order.

Solution: 128328
SITUATION IDENTIFIED IN:
"Generate Bills of critical Material" (tibom2220m000)
SITUATION DESCRIPTION:
Calculated Quantity required is wrong in Bills of Critical Material when the scrap percentage is maintained in the Generic
BOM, while Generating Bills of Critical Material for Generic Item.
SOLUTION DESCRIPTION:
While calculating the Quantity required, system would consider only Planning Quantity and Planning Percentage. System
will not consider the Scrap Percentage maintained in BOM again, because Planning quantity is calculated from Net Quantity
considering Scrap quantity.

Solution: 128345
SITUATION IDENTIFIED IN:
"Service Order Actual other cost" (tssoc2141s000)
SITUATION DESCRIPTION:
If the user changes the actual cost for the subcontracted cost type, the Integration Transaction entry that had been already
present in "Integration Transactions by Project/Order" (tfgld4510m000) is not reversed. This is present along with the new
entry that is getting created.
SOLUTION
DESCRIPTION:
Now, the old integration entry is reversed and the new entry is created.

Solution: 128352
SITUATION IDENTIFIED IN:
"Maintain Element Budget" (tpptc1110s000)
SITUATION DESCRIPTION:
When budget quantity is entered for the first time, Price Matrix is taken into account. But, if we change the quantity to some
other quantity, the price matrix is not called again, so if for the second quantity, there is a different price that will not be
considered.
SOLUTION DESCRIPTION:
There was a check to determine the price matrix only if the previous quantity was zero. That check is now removed. So every time quantity is changed, price will be determined.

Solution: 128373
SITUATION IDENTIFIED IN:
"Lots" (whltc1500m000)
SITUATION DESCRIPTION:
Negative material issue overwrites a lot price of zero in the session Lots with standard cost.
SOLUTION DESCRIPTION:
Now the Lot price is not over written with the standard cost price when the Lot is received with zero prices.

Solution: 128374
SITUATION IDENTIFIED IN:
"Online help" (ttstphelp)
SITUATION DESCRIPTION:
When contens help is started from "Menu Browser" or "Desktop Browser" Using ASCII help and then in the helpviewer
again selecting contens help will show wrong help.
SOLUTION DESCRIPTION:
Contents help (in the helpviewer) should be disabled when contents help is shown by the helpviewer. This was not the case
and is now corrected.

Solution: 128375
SITUATION IDENTIFIED IN:
"Payment Schedule" (tfacp1103m000)
SITUATION DESCRIPTION:
1) Unable to close session "Payment Schedules - tfacp1103m000" when a Purchase-Invoice is overpaid.
2) While zooming from the Invoice to the Payment schedule, the schedule of another
invoice is shown.
SOLUTION DESCRIPTION:
1) When running session "Payment Schedules - tfacp1103m000" with an overpaid Purchase-Invoice the user is able to close
this session without changing anything.
2) While zooming from the Invoice to the Payment schedule, the schedule of the
invoice is shown.

Solution: 128377
SITUATION IDENTIFIED IN:
"Audit Posting Data of Electronic Bank Statement" (tfcmg5203m000)
SITUATION DESCRIPTION:
EBS batch reference and Bank Relation description was not printed correctly on the "Audited Electronic Bank Statements"
Report when more than one EBS batch or bank relation was audited.
SOLUTION DESCRIPTION:
Now EBS batch reference and Bank Relation description is printed correctly on the "Audited Electronic Bank Statements"
Report when more than one EBS batch or bank relation is audited

Solution: 128380
SITUATION IDENTIFIED IN:
"Item Purchase Data" (tdipu0101s000)
SITUATION DESCRIPTION:
Calculation of the Average Purchase Price values goes wrong when the system takes return purchase orders into account when
calculating the Average Purchase Price for an item. This is incorrect
SOLUTION DESCRIPTION:
Return Purchase Orders will not be considered when calculating the Average Purchase Price

Solution: 128381
SITUATION IDENTIFIED IN:
"Print Receipts" (tdpur4431m000)
SITUATION DESCRIPTION:
When printing Receipts by Receipt Number, each Receipt should be printed on a new page.
SOLUTION DESCRIPTION:
Report has been modified to print each Receipt on a new page.
Also the Receipt Number has been made as a view field.

Solution: 128384
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101m200)
SITUATION DESCRIPTION:
When a subcontracting purchase order line is split into two detail deliveries the price is recalculated.
SOLUTION DESCRIPTION:
Now the system does not recalculate prices and discounts for subcontracting purchase orders

Solution: 128386
SITUATION IDENTIFIED IN:
"Payment Advices" (tfcmg1120s000)
SITUATION DESCRIPTION:
Error message not given when an excess amount is entered the second time in the Payment Advice.
SOLUTION DESCRIPTION:
The reported problem is solved now and the Error message will be given even when an excess amount is entered the second
time in the Payment Advice.

Solution: 128394
SITUATION IDENTIFIED IN:
"Performance Boosters" (tcmcs0197s000)
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: 128397
SITUATION IDENTIFIED IN:
"Write of Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
When Currency Rate is "fixed" for invoice, currency difference is written off.
SOLUTION DESCRIPTION:
If Currency Rate is "fixed" for the invoice, then message "no data within selection" appears.

Solution: 128398
SITUATION IDENTIFIED IN:
"Copy RFQ Lines to Contracts/Orders" (tdpur1202m000)
SITUATION DESCRIPTION:
While Copying two RFQs at a time one to contract another to purchase order, a report is printed in which purchase order
details are shown under the heading of purchase contract
SOLUTION DESCRIPTION:
Now the Purchase order and purchase contract details are printed in two separate pages under correct headings

Solution: 128399
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When the same level has more than one sequence with the different percentages and if the option is to find the "Best
discount ", then the system picks up the wrong percentage.
SOLUTION DESCRIPTION:
In this situation, now the system works perfectly finding the best discount percentage.

Solution: 128406
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
When the user uses the sales order type as automatic, and maintains a detail line for existing position, which has been
already processed, then system is not processing the newly entered detail line automatically.
SOLUTION DESCRIPTION:
Now, when the user uses the sales order type as automatic, and maintains a detail line for an existing position, which has
been already processed, then system will process the new entered detail line automatically.

Solution: 128408
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When the user re-enters the session for modifying and if he changes the amount, then the system gives an error message
"Terms of Payment not found". This is when the localization Parameter "Receipt schedule" is ON. If it is OFF, no error
message is displayed, but the terms of payment becomes blank.
SOLUTION DESCRIPTION:
Now the error message does not appear.

Solution: 128413
SITUATION IDENTIFIED IN:
"Print Multi-Level Cost Price Calculation" (ticpr2420m000)
SITUATION DESCRIPTION:
1. The flag "Economic Order Quantity Sub Items" is enabled for customized items, when price calculation code is not
standard. For customized items, this flag should be disabled and unchecked irrespective of price calculation code.
2. The flag is enabled when a standard item is entered. By default the flag should be disabled and checked for a standard
item. This should be enabled and unchecked if the price calculation code is not standard.
SOLUTION DESCRIPTION:
The existing inconsistency has been corrected.

Solution: 128414
SITUATION IDENTIFIED IN:
"Release to Warehousing (batch)" (tdpur4246m000)
SITUATION DESCRIPTION:
1. There are many lines in a purchase order.
2. All the lines of this order are copied to a new order.
3. When this new order is Released to Warehousing, all the lines are released under different warehousing order.
SOLUTION DESCRIPTION:
The problem was the Planned Delivery date of all the purchase order lines of the copied order were not the same. Now, the
Planned Delivery Date would be same for all the lines of the copied order.

Solution: 128415
SITUATION IDENTIFIED IN:
"Interest Invoice Lines" (cisli2110s000)
SITUATION DESCRIPTION:
User can change the Pay-from BP in the interest invoice lines even though there is no relation between the new pay-from BP
and the Invoice-to BP.
SOLUTION DESCRIPTION:
Now a warning message will appear if the Pay-from and the Invoice-to BP's are not related to each other.

Solution: 128417
SITUATION IDENTIFIED IN:
"Generate Progress by Activity/Cost Object" (tpppc1148m000)
SITUATION DESCRIPTION:
Message 12453 ???????? Comes up when we try to copy progress from "Activity Progress" to "Copy Progress to Activity/Cost
Type/ Cost Object", where inventory unit of control code item is not filled up.
SOLUTION DESCRIPTION:
Proper message code is exported. So clear message code will come now.

Solution: 128420
SITUATION IDENTIFIED IN:
"General Actual Project Costs" (tipcs3140s000)
SITUATION DESCRIPTION:
Erroneous postings to finance for 'Project (PCS)/Costs Goods Sold (General)' combination, when the Key Definition in the
integration mapping scheme is set as 'Financial Business Partner Group' and the same business partner is attached to the
project. This is because, the 'Financial customer group PCS' will not be considered as the Key Definition 'Financial
Business Partner Group' in the finance integration mapping scheme for the above combination.
SOLUTION DESCRIPTION:
The Financial Customer Group PCS will be considered as Financial Business Partner Group in the Integration mapping
scheme for Project (PCS)/Costs Goods Sold (General) combination.

Solution: 128426
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
Consignment replenishment sales orders are not processed automatically when returning goods from consignment (owned)
warehouse to own warehouse.
The flow stops at Receipts step, waiting for a receipt to be created manually.
SOLUTION DESCRIPTION:
This situation is corrected. Processing is done automatically if the warehouse procedure is set up that way.

Solution: 128428
SITUATION IDENTIFIED IN:
"Purchase order Receipts" (tdpur4101s300)
SITUATION DESCRIPTION:
The 'Automatic Confirmation of Back orders' is YES. In combination with multiple receipt and Approval, the 'Confirm Back
Order' button is enabled in the session "Purchase order Receipts" (tdpur4101s300). When the button is pressed, system
creates some wrong back orders.
SOLUTION DESCRIPTION:
The 'Confirm Back Order' button is not enabled now.

Solution: 128434
SITUATION IDENTIFIED IN:
"Commitments and actual costs" (tpppc2110s000)
SITUATION DESCRIPTION:
The date in the reversed soft commitment entry is wrong when the purchase order is received.
SOLUTION DESCRIPTION:
Now the registration date for the reversed soft commitment during receipts is filled with the receipt date

Solution: 128435
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Payment difference not calculated when amount is changed after saving record.
SOLUTION DESCRIPTION:
The reported problem is solved now and the Payment difference will be calculated when amount is changed after saving
record.

Solution: 128436
SITUATION IDENTIFIED IN:
"Update the Effective Date and Expiry Date in Service Contract Coverage Terms (tsctm120)" (tscor0004m000)
SITUATION DESCRIPTION:
When copying coverage terms for a service contract from a contract template or a contract quotation, the effective date and
expiry date are not being copied to the contract coverage terms. Solution 128035 was created for solving this defect.
It should be possible to automatically update all the service contracts which have a coverage term without an effective and
expiry date.
For this purpose, a correction program is needed.
SOLUTION DESCRIPTION:
For updating the effective and expiry dates of service contract coverage terms, a correction program has been made.
This correction program updates the effective date(tsctm120.stdt) and expiry date(tsctm120.endt) of service contract
coverage term when they are empty.
The correction program provides following selection ranges and options:
- Service Contract from/to
- Option to select if test run or definite run should be performed
One single report is provided to print the service contracts that have a coverage term with effective and expiry dates
empty. The updated effective and expiry dates of the contract terms will be shown in bold in the report.
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.
Note:
Service Order Actual Costlines will not be updated by this correction program.

Solution: 128440
SITUATION IDENTIFIED IN:
"Correct Customer Turnover/Open Billing Request Amount" (cicor0112m000)
SITUATION DESCRIPTION:
Correction program needed to recalculate Open Billing Request Amount.
SOLUTION DESCRIPTION:
Correction Program is built to re-calculate the Open Billing Request Amount.

Solution: 128441
SITUATION IDENTIFIED IN:
"Transfer Planned PRP Purchase Order" (tppss6230m000)
SITUATION DESCRIPTION:
While transferring the purchase order, in the report, the "Planned Quantity" unit field shows the purchase unit & not the
inventory unit. If the inventory unit & purchase unit of an item are different, the report will show a different unit & this
gives a wrong picture of the ordered quantity.
Always the inventory unit needs to be shown.
SOLUTION DESCRIPTION:
Now, the "Planned Quantity" unit field will show the inventory unit & not the purchase unit.

Solution: 128444
SITUATION IDENTIFIED IN:
"Engineering BOM" (tiedm1510m000)
SITUATION DESCRIPTION:
System is allowing customized items as E-BOM components for E-Items when it is linked to a project.
SOLUTION DESCRIPTION:
System will not allow customized items as E-BOM components for any E-Item.

Solution: 128445
SITUATION IDENTIFIED IN:
"Print Open Entries" (tfacr2421m000)
SITUATION DESCRIPTION:
The session does not default the "To" date for the Invoice date range selection
SOLUTION DESCRIPTION:
Now session defaults the current date in the "To" date for the Invoice date range selection

Solution: 128447
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A return sales order is created and the line is copied from the original order. This line has a to-order item (make customized
= yes). The order line is not copied.
SOLUTION DESCRIPTION:
When the sales order line quantity is negative, the make-customized checkbox cannot be on yes. When entering a normal sales
order line for a customized item, and making the quantity negative, the 'make customized' checkbox is set to 'no'. This was
not done when copying such a sales order line to a return order.
Now the copied line has a negative order quantity and the 'make customized' checkbox is set to 'no'.

Solution: 128448
SITUATION IDENTIFIED IN:
"Mateiral cost" (tpppc2111s000)
SITUATION DESCRIPTION:
When the price policy of the item is cost price and the cost price is maintained as zero then system for purchase price and
fills it with that. This is wrong, cost price should remain as zero only.
SOLUTION DESCRIPTION:
Now system generates a question asking " cost price is zero , retrieve the purchase price?". If the user says yes then it would
get the purchase price and if no then it would keep the cost price as zero only.

Solution: 128450
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When creating a Purchase Invoice related to orders and if the Purchase Invoice and the Order has different "Terms of
Payment", then the "Terms of Payment" should default to the one defined at Purchase Order Header. But after entering the
amount, the "Terms of Payment" was changing to the one defined for Business Partner.
When a Cost Purchase Invoice is created with "Level of Tax Calculation" as Header level, a temporary tax transaction is created in table "Tax transactions" (tfgld107). If no transactions is entered and the level of tax calculation is changed to "Transaction Line", the tax transaction record in the Header Level is not
deleted.
For the following Tax Localization parameters setting (Generic Taxes = "Yes, Singular Tax = "No"), a Purchase cost invoice is entered with tax
calculation at the header level. After the Tax amount is filled, when the form is changed, the amount gets reset to zero.
SOLUTION DESCRIPTION:
The "Terms of Payment" on the invoice defaults to the one that is defined at the Purchase Order Header. And it doesn't change when the amount field is updated.
When the tax transaction changes from header to transaction line level and there is no transactions present, the records from table tfgld107 is deleted.
The tax amount doesn't change when the form is changed; hence it has the correct value always.

Solution: 128457
SITUATION IDENTIFIED IN:
"Planned material transaction" (tppss6510m000)
SITUATION DESCRIPTION:
The field unit in multi occurrence session does not get updated for all projects!
SOLUTION DESCRIPTION:
Now the unit is properly displayed for all the projects.

Solution: 128462
SITUATION IDENTIFIED IN:
"Generate Inventory Commitments" (whinp2200m000)
SITUATION DESCRIPTION:
After generating an outbound advice, if we generate inventory commitment for a production order, duplicate commitments
are generated this was because of the difference in the sequence numbers between warehousing and production.
SOLUTION DESCRIPTION:
Now the system checks for the existing outbound order line in warehousing and finds the related line with correct sequence
number and doesn't generate duplicate commitments

Solution: 128465
SITUATION IDENTIFIED IN:
"Sales Corrections" (tfacr2110m000)
SITUATION DESCRIPTION:
BP Balance getting wrongly updated in tfacr2533m000 (BP totals) when Sales Invoice is corrected through tfacr2110m000
(Sales Correction).
SOLUTION DESCRIPTION:
BP Balance getting correctly updated in tfacr2533m000 (BP totals).

Solution: 128471
SITUATION IDENTIFIED IN:
"Print Remittance Letters" (tfcmg1270m000)
SITUATION DESCRIPTION:
The IBAN number is not printed although "IBAN" is specified in the payment method and the Business Partner has an
IBAN account.
SOLUTION DESCRIPTION:
The IBAN functionality has been included in the "Print remittance Letter" session (tfcmg1270m000).
When "IBAN" is specified in the payment method and the Business Partner has an IBAN account this account is printed in
the "Bank Account" column..

Solution: 128475
SITUATION IDENTIFIED IN:
"BOI Modeler" (BOI Modeler)
SITUATION DESCRIPTION:
Baan tables without descriptions were not visible in the BOI modeler. The object ottstptableinfo ("Get table information
ins XML format") retrieved the table description from the Baan database. Only when the description was found the table
was added into XML, which is used by the BOI modeler.
SOLUTION DESCRIPTION:
The changed object adds the table to the XML list when the table definition is present in the Runtime Data Dictionary. If the table
description is found, this description is added as well, but tables without description are not skipped anymore.

Solution: 128476
SITUATION IDENTIFIED IN:
Print Payment Advice (tfcmg1401m000)
SITUATION DESCRIPTION:
IBAN: Wrong Account is printed on the Report "Print Payment Advices by Pay - to Business Partner" (tfcmg140117000)
SOLUTION DESCRIPTION:
The reported problem is solved now and now the correct bank account will get printed on the Report. (Either IBAN or the
Normal Bank Account depending on the option chosen)
Solution: 128483
SITUATION IDENTIFIED IN:
"Generate Control Data" (tpptc1230m000)
SITUATION DESCRIPTION:
Wrong and unclear error messages are printed in the report when Generate control data session is run. The element and
activity codes are not printed.
SOLUTION DESCRIPTION:
Now the error messages printed in the report is correct and clear. The correct element and activity codes are printed clearly.

Solution: 128489
SITUATION IDENTIFIED IN:
"Accept Values of GRINYA Reconciliation" (tfacp1535m000)
SITUATION DESCRIPTION:
While choosing option "Accept Order" in session "Accept Value of GRINYA Reconciliation" (tfacp1535m000), the error
message "no permission for tfacp1136s0001" pops up.
SOLUTION DESCRIPTION:
No error message comes up when choosing the option "Accept Order" and the zoom session starts successfully.

Solution: 128491
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
In session "Sales Order Lines" (tdsls4501m000), there is inconsistency in enabling - disabling mechanism of the specific
menu option "Recalculate Price/Discounts Entire Order".
When starting the session the option is disabled and no lines are marked.
When any order line is marked, this option is be disabled.
If an empty order line is selected, this option should also be enabled because the same situation is created as when starting
the session.
SOLUTION DESCRIPTION:
The enabling and disabling of the option is correctly executed

Solution: 128494
SITUATION IDENTIFIED IN:
"Generic BOMs" (tipcf3110s000)
SITUATION DESCRIPTION:
The 'Planning Quantity' is correctly calculated if the 'Net Quantity' is modified but, it is not calculated if the fields
'Length', 'Width' or 'Number of Units' are modified in session "Generic BOMs" (tipcf3110s000) and when the physical quantity
of the inventory unit is 'Length', 'Volume' or 'Area'.
SOLUTION DESCRIPTION:
The 'Planning Quantity is calculated based on the changed 'Net Quantity' when the fields 'Length', 'Width' or 'Number of
Units' are modified in session "Generic BOMs" (tipcf3110s000).

Solution: 128500
SITUATION IDENTIFIED IN:
"Purchase-Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
Error Message "Ledger Account may not have projects" is popped up, when a Ledger Account having the Integration
Integrator as 'Not Applicable' is added to the Purchase Order line (Finance Tab).
SOLUTION DESCRIPTION:
The message does not appear for a 'Ledger Account' with Integration Integrator or Fixed Asset Integrator as 'Not
Applicable'.

Solution: 128511
SITUATION IDENTIFIED IN:
"Components by Solution" (ttpmc1120s000)
SITUATION DESCRIPTION:
When a component of type 'help text' is connected to a PMC solution, the default languages are not always filled. This is the
case when the help text code is longer than 30 characters. The help text codes may have a length of 32 characters.
SOLUTION DESCRIPTION:
The default languages are determined correctly now for long help text codes and displayed on the screen.

Solution: 128513
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
The specific option "Receipt Correction" in the Receipts session (whinh3520m000) was enabled for sales return orders for a
very short time due to slow performance of the system or long client-server response times. However, during this short
period of time, the option could be used for this type of orders, which is not allowed. Under normal conditions, this
phenomenon would not have been noticed.
SOLUTION DESCRIPTION:
The "Receipt Correction" must always be disabled for a sales return order. The enabling/disabling of this specific option
has been modified to avoid the enabling of this option under a scenario of slow performance or long response times.

Solution: 128516
SITUATION IDENTIFIED IN:
"Maintain Texts" (tttxt1100m000)
SITUATION DESCRIPTION:
When deleting a text, using a standard Baan session, there is a log message added to the log file. Even though the message
says it cannot delete the text, the text has been deleted.
SOLUTION DESCRIPTION:
If the text has been correctly deleted, the log message will not appear in the log file.

Solution: 128517
SITUATION IDENTIFIED IN:
"Assign unallocated / Advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When more than one unallocated receipt was used within the same transaction to be linked to invoices, the balance amounts
went wrong.
Problems in balances were also encountered when trying to assign one unallocated receipt to another using the same
transaction type in the same batch.
SOLUTION DESCRIPTION:
Now there are no problems with balances on assigning unallocated receipts to invoices.
Problems with balances when trying to assign two unallocated receipts with each other are also taken care of.
It is not possible to directly allocate two unallocated receipts now (using "Bank Transactions"). A separate transaction type
needs to be used for allocating unallocated receipts to each other. This restriction has been implemented to prevent problems
in balances while linking unallocated receipts to invoices.

Solution: 128519
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
The Tax country in the Sales Invoice Transactions (tfacr1111s000) becomes zero once the Invoice date is changed in the
Sales Invoices. (tfacr1110s000)
SOLUTION DESCRIPTION:
The Tax country in the Sales Invoice Transactions does not become blank even though the Invoice date is changed in the
Sales Invoices.

Solution: 128522
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
The processed invoice balance of the Related Business Partner is going wrong when 'Process Assignments' is done again,
even without making any changes, after re-entering the session "Assign unallocated /advance receipts to invoices".
The reason is - already processed invoices of the Related Business Partner are not displayed automatically while re-entering
the session "Assign unallocated /advance receipts to invoices"
SOLUTION DESCRIPTION:
Earlier, the balance of the already processed invoice of the Related Business Partner was going wrong while re-entering the
session 'Assign unallocated /advance receipts to invoices' and pressing 'Process Assignments', even without making any
changes.
Now, balance of the invoice is correct and that invoice is displayed automatically after re-entering the session "Assign
unallocated /advance receipts to invoices"

Solution: 128525
SITUATION IDENTIFIED IN:
"Generate element progress" (tpppc1128m000)
SITUATION DESCRIPTION:
Fatal error 205 when we generate a element progress for an item whose control code's inventory unit is not maintained.
SOLUTION DESCRIPTION:
Now a check is built for inventory unit and if it empty then a message would be diplayed for that item, saying the unit is not
maintained.

Solution: 128526
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
When a sales Invoice is posted in Central Invoicing and when no PCS item is used, then the sales office is not populated to
the Integration tables.
SOLUTION DESCRIPTION:
Now the Sales Office is populated correctly.

Solution: 128532
SITUATION IDENTIFIED IN:
"Assign Credit Notes to Invoices" (tfacr2121m000)
SITUATION DESCRIPTION:
The document number of the Assignment document created when a credit note is linked to an invoice is not shown after the
assignment is done.
SOLUTION DESCRIPTION:
A message is displayed with the document number after a credit note is linked to an invoice.

Solution: 128534
SITUATION IDENTIFIED IN:
"Sales-Quotation Lines" (tdsls1501m000)
SITUATION DESCRIPTION:
This is a problem that needs to be solved on behalf of the BOI Builder.
In that the view fields needs to be determined. So we first check form type of entered session and if its Type 3 then go for
that session's index field(s).
But since session "Sales Quotation Lines" is defined as Form Type 2, we cannot go ahead for index field. Logic does not
work.
SOLUTION DESCRIPTION:
Form type is adjusted according to the actual working of the session.

Solution: 128535
SITUATION IDENTIFIED IN:
"Remove Fully Paid Sales Invoices" (tfacr2260m000)
SITUATION DESCRIPTION:
Cannot archive the data for the Receipt Document after Archiving the Sales Invoices.
SOLUTION DESCRIPTION:
Now the Receipt transactions can be archived

Solution: 128538
SITUATION IDENTIFIED IN:
"Recalculate Business Partner Balances" (tfacr2245m000)
"Recalculate Business Partner Balances" (tfacp2245m000)
SITUATION DESCRIPTION:
In the session, value entered in fifth Financial Company is getting defaulted to sixth Financial Company.
SOLUTION DESCRIPTION:
Value entered in fifth Financial Company does not default to sixth Financial Company.

Solution: 128543
SITUATION IDENTIFIED IN:
"Sales Credit Note" (tfacr1110m000)
SITUATION DESCRIPTION:
Late Payment Surcharge Code and Payment Method Code are wrongly defaulted for Sales Credit Note.
SOLUTION DESCRIPTION:
Correct Late Payment Surcharge Code and Payment Method Code are defaulted for Sales Credit Note.

Solution: 128550
SITUATION IDENTIFIED IN:
"Assign Credit Notes to Invoices" (tfacp2120m000)
SITUATION DESCRIPTION:
The sessions "Assign Credit Notes to Invoices" (tfacp2120m000) and "Assign Invoices to Credit Notes" (tfacp2121s000) take
a long time to start.
SOLUTION DESCRIPTION:
The performance of the above sessions has been improved.

Solution: 128553
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
When trying to complete a rework production order for an item having 'Lot control- By Unit', an error message "Lot %s for
item %s already exists" pops up and it is not possible to complete the order. This happens if the initial lot code and the
rework order's lot code are the same.
SOLUTION DESCRIPTION:
Users can now close the rework production order with the same lot code as the original production order's lot code.

Solution: 128556
SITUATION IDENTIFIED IN:
"Estimated vs. Actual Material Costs" (ticst0501m000)
SITUATION DESCRIPTION:
Unable to issue material, the following message pops up "Released quantity cannot be greater then advised quantity."
SOLUTION DESCRIPTION:
The advised quantity in inventory was wrongly taken from Outbound order lines, causing that when comparing this quantity
with the released quantity, the message was arising. Now the right value for advised quantity is taken, so no message pops
up.
Also message has been changed to "Released quantity cannot be greater than advised quantity."

Solution: 128561
SITUATION IDENTIFIED IN:
"Print Payment Advice" (tfcmg1401m000)
SITUATION DESCRIPTION:
'Reason for Payment' is not printed in any of the 'Detailed Reports' because that field is not present in those reports
SOLUTION DESCRIPTION:
Earlier, 'Reason for Payment' is not printed in the 'Detailed Reports'
Now, new field is added to the report so that 'Reason for Payment' is also printed in the Reports

Solution: 128563
SITUATION IDENTIFIED IN:
"Database Definitions" (ttaad4110s000)
SITUATION DESCRIPTION:
In the time of Bisam databases the flag "Force to Read" was used for mirroring purposes. With modern databases this flag
has come obsolete. There for it will be removed.
SOLUTION DESCRIPTION:
The flag "Force to Read" will be automatically unset when an database entry is being saved. For new records the field is
disabled to prevent setting this flag.

Solution: 128566
SITUATION IDENTIFIED IN:
"Properties of GRNI Reconciliation entry" (tfacp1135s000)
SITUATION DESCRIPTION:
In session "Properties of GRNI Reconciliation entry" (tfacp1135s000), when any of the field is changed for documents which
are not created by correction and if the ledger account has dimensions linked to it, then the error message "Dimension of
Ledger Account must be filled" pops up.
SOLUTION DESCRIPTION:
The check on dimension is only done when a correction document is created. Changing the properties of other documents
doesn't check the dimension; hence no error message pops up.

Solution: 128567
SITUATION IDENTIFIED IN:
"Transfer planned purchase orders" (tppss6230m000)
SITUATION DESCRIPTION:
The filed "Position number" is not displayed in the report generated after transferring the planned purchase order.
SOLUTION DESCRIPTION:
Now the Position number is properly displayed.

Solution: 128569
SITUATION IDENTIFIED IN:
"Anticipated Payments(Details)" (tfcmg2116s000)
SITUATION DESCRIPTION:
Error message displayed when entering Journal check.
SOLUTION DESCRIPTION:
The reported problem is solved now and now the Error message won't get popped up when entering Journal check

Solution: 128580
SITUATION IDENTIFIED IN:
"update element progress" (tpppc1128m000)
SITUATION DESCRIPTION:
Fatal error 205 while generating progress for elements when the date field is not filled.
SOLUTION DESCRIPTION:
Now a error pops saying 'invalid date' if the date field is kept blank. So fatal errors are now generated while updating the
progress.

Solution: 128587
SITUATION IDENTIFIED IN:
"ATP-Handling" (tdsls4899m000)
SITUATION DESCRIPTION:
Because of solution 127054 Capacity ATP check has become too restrictive, during the combination of component and capacity
check. It tries to retrieve a connection between item and work center which is not necessarily there in the Bill of Material.
Also it assumes that Materials are leading over Capacity.
SOLUTION DESCRIPTION:
During the combination of component and capacity CTP, both capacity CTP and component CTP are checked and the highest of the two is taken as
capable to produce. The limitation over here is that components and capacity are checked independent from each other. This implies that you might
have the situation that item planning and resource planning don't match. So in the new situation it can be that based on the capacity CTP an item is
capable to promise, but that it doesn't take into account that the component CTP is lower than required.

Solution: 128589
SITUATION IDENTIFIED IN:
"ATP Handling" (tdsls4899m000)
SITUATION DESCRIPTION:
The fields Quantity and Warehouse are not enabled when the user accesses the session "ATP Handling" (tdsls4899m000)
from "Critical Material Requirements by Period" (cprmp2505m000).
SOLUTION DESCRIPTION:
The Quantity and Warehouse are now enabled and the user can enter the value in these fields.

Solution: 128593
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. There are two purchase order lines and the first order line is created from a Sales Order, while the second one is manually
created.
2. While deleting the second line, the system asks the following question
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
"The purchase order line is linked to a sales order line. This link will be disconnected. Continue?"
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
The question will not pop up when the Purchase order line is not linked to any sales order.

Solution: 128599
SITUATION IDENTIFIED IN:
"Compose Payments" (tfcmg1240m000)
SITUATION DESCRIPTION:
The IAB and PAYE numbers are currently printed at the end of the 'Reference' field, for the report group selected in
'Payment Methods' (tfcmg0140m000). The social contribution and tax authorities are only reading the first 30 characters of
this 'Reference'; therefore, these numbers are not read completely.
SOLUTION DESCRIPTION:
The order of the 'Reference' field has been changed. The IAB and PAYE subcontracting numbers are printed at the beginning of
the 'Reference' to be properly read by the social contribution and tax authorities. The IAB- and PAYE- subcontracting numbers is actually filled at the first 30 positions.

Solution: 128601
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
(1) When entering a multiple vatcode in session "Purchase Invoices - tfacp1110s000" the total vat amount is not displayed
and stored incorrectly.
(2) When entering a vatcode (single) on transaction line level and the amount is devided against more that one line the total
vat amount only displays the vat amount entered on the last line
SOLUTION DESCRIPTION:
(1) The vatamount is displayed now and stored corectly.
(2) The total vat amount is displayed and stored corectly now.

Solution: 128602
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
SITUATION DESCRIPTION:
A Non-Warehouse Item is used in Sales Order lines. It doesn't have valid Cost structure. If this Sales Order line is to be
released to invoicing, the "Release to Invoicing (batch)" session doesn't serve the purpose as delivered quantity & Cost Of
Goods Sold have to be entered while releasing to Invoicing. Hence, the session "Release to Invoicing"(tdsls4501m130) has to
be used. How ever, this session is not accessible from the Sales Order Header.
SOLUTION DESCRIPTION:
Since the Delivered Quantity and Cost of Goods Sold for the Non-Warehouse Items need to be entered in "Release to Invoicing"(tdsls4501m130)
session, the zoom to this session is provided from Sales Order Header via the Specific menu.

Solution: 128603
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When Service contract invoices are printed, the Installment dates are not printed correctly in the detail line.
SOLUTION DESCRIPTION:
Now the dates are correctly printed.

Solution: 128604
SITUATION IDENTIFIED IN:
"Match Purchase Receipt Line" (tfacp2544m000)
SITUATION DESCRIPTION:
In session "Match Purchase Receipt Line" (tfacp2544m000), the "Sort By" option under "View" in the main menu is not
clear.
SOLUTION DESCRIPTION:
The "Sort By" option has been changed to give a more meaningful explanation.

Solution: 128606
SITUATION IDENTIFIED IN:
"Transfer payments" (tfcmg1260m000)
SITUATION DESCRIPTION:
1) It is displaying Payer's bank country instead of Supplier's bank country in the position no 23 of the report.
2) Record length was not correct (It is 191 instead of 192 characters) at line no 23 and position 192
SOLUTION DESCRIPTION:
1) Now it is displaying supplier bank account
2) Record length is correct now.

Solution: 128607
SITUATION IDENTIFIED IN:
"Check Anticipated Tables (tfcmg110/tfcmg111/tfcmg112)" (tfcor0270m000)
SITUATION DESCRIPTION:
Missing label in correction program tfcor0270m000
SOLUTION DESCRIPTION:
Label displayed in the session properly

Solution: 128608
SITUATION IDENTIFIED IN:
"Generate Invoice by Self Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
It was not possible to generate the self-billing invoice, as the system shows the below fatal error.
FATAL ERROR: Illegal number of args (11) for function tfint.dlltdpur.update.average.purchase.price expected 12.
it appears because of the reason that an argument was missing
SOLUTION DESCRIPTION:
The argument is added for the called function. Now, it is possible to process the self-billing invoice.

Solution: 128613
SITUATION IDENTIFIED IN:
"Bills of Material" (tibom1510m000)
SITUATION DESCRIPTION:
System is not zooming to the correct Routing Operations for a Main Item, after zooming from the field Operation in the
session Bills of Material.
SOLUTION DESCRIPTION:
System will zoom to the routing operation of the Item if the routing code is equal to the routing parameter. If the routing
code is not equal to routing code maintained in the routing parameter, then system will zoom to first Routing Operations
maintained for that Item.

Solution: 128614
SITUATION IDENTIFIED IN:
"Copy Requisitions" (tdpur2204s000)
SITUATION DESCRIPTION:
When a Requisition is copied to another requisition with a future date, it is not copied and the system gives the error report
""Delivery date cannot be earlier than requisition date".
SOLUTION DESCRIPTION:
It is possible to copy a requisition to another requisition in a future date.

Solution: 128616
SITUATION IDENTIFIED IN:
"Maintain Element Budget (Material lines)" (tpptc1110s000)
SITUATION DESCRIPTION:
Purchase price retrieval from the price matrix is not always correct. When the unit in the budget line differs from the unit in
the price matrix , then the purchase price retrieved is incorrect.
SOLUTION DESCRIPTION:
Now the purchase price retrieval from the price matrix is working correctly.

Solution: 128617
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
It is not possible to process the Direct Delivery purchase order received with zero quantity. The system gives the error
report "No linked Purchase Order found for Sales Order".
SOLUTION DESCRIPTION:
It is possible to process the purchase order and the back order is also confirmed.

Solution: 128621
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
1. The commitment policy of the item is 'Line Entry'. The Inventory on hand is less that the Minimum Quantity to commit. A sales order is created for this item with a quantity higher than the on hand and minimum quantity to commit. The line can be saved and the user gets the message
+++++++++++++++++++++++++++++++++++++++++++++
"Cannot commit less than minimum allocation quantity: XX pcs"
+++++++++++++++++++++++++++++++++++++++++++++++++
After this is order quantity is reduced and saved. At this time, the line cannot be saved with the system giving the error message "Back order quantity
not possible"
2. At Order Entry is was possible to end up with a Sales Order Line with a different Sold-to Business Partner then on the Sales Order Header it belongs to.
As a result changing the Ship-to Business Partner on the Line afterwards is not possible, since no relation exists between the Line' s and Header' s business partner.
Also the wrong Business Partner would be invoiced.
4. For Cost Items with No Release to Warehousing, the Warehouse gets defaulted in Sales Order lines, if the "Split Deliveries" box is checked.
5. Alternative Item that is already expired can also be chosen, without any problem.
SOLUTION DESCRIPTION:
1. The order quantity can be reduced and the line can be saved.
2. From now on it is impossible to enter different Sold-to Business Partners on Line and Header at order entry.
A check was built in that compares both Sold-to Business Partners of Line and Header.
When a difference is found, the user will be notified by a message "Sold-to Business Partner of Line does not match with Sold-to Business Partner of Header." (tdslss401.4).
4. If Items do not have Release to Warehousing mentioned in Item Sales Data, the Warehouse doesn't get defaulted in Sales Order lines.
5. Check has now been added to check whether the Alternative Item chosen is expired on the Order Date. If the expiry date falls before the Order Date, then a warning message "Alternative Item Expired" is popped up.
If the Order Date falls before the Introduction date of the alternative item, a warning "Alternative Item not yet introduced" is popped up, and it is
not possible for the user to choose alternative items that are 'Expired' or 'Not Introduced' anymore.

Solution: 128625
SITUATION IDENTIFIED IN:
"Item Costing Data" (tdisa0107s000)
SITUATION DESCRIPTION:
When Standard Cost Price is calculated for a new item the fatal error "Index out of dimension" occurs.
SOLUTION DESCRIPTION:
The fatal error doesn't occur now.

Solution: 128631
SITUATION IDENTIFIED IN:
"Generate Configuration Structures" (tscfg2210m000)
SITUATION DESCRIPTION:
When generating a configuration structure from a customized item, many sub items are skipped in case the configuration
structure is generated from a sales order for a customized item.
These missing items are items defined on one level deeper in the P-Bom then an item that was not included in the configuration
structure in service for a valid reason, as reported in the error report.
SOLUTION DESCRIPTION:
Following information can also be found in the help text.
If the items on the order lines are customized, the customized BOMs are the basis from which the new configuration
structure is generated.
For standard items, the service BOM will act as a repository.
Generation of a Configuration is allowed for a customized item that is derived from a Generic item. Mandatory object data
from Objects (tscfg200) will be retrieved from Service Item Data (tsmdm200) or from Service Item Defaults Data
(tsmdm205).
When generating a configuration structure for a customized item the following
situations are recognized:
1) Service Item Data (tsmdm200.item) is available for the customized item (tcibd001.item):
Project segment will be included in object identification (tscfg200.crob)
Project segment will be filled in the derived from item field (tscfg200.item)
When Service Item Data is not available for the customized item....
2) Service Item Data (tsmdm200) is available for the derived from item (tcibd001.dfit):
Project segment will not!! be included in object identification (tscfg200.crob).
Project segment will not!! be filled in the derived from item field (tscfg200.item).
When Service Item Data is not available for the derived from item (tcibd001.dfit)....
3) Service Default Item Data (tsmdm205), using item type and item group of the
customized item (tcibd001.item) is available:
Project segment will be included in object identification (tscfg200.crob)
The derived from item field (tscfg200.item) will be kept empty.
Note: If the derived from item field remains empty, then diagnostics (in CLM) and Preventative maintenance (in SPC) cannot
be applied to this object.
If diagnostics and preventative maintenance are wished for, the user can add data for this item in Service Item Data
(tsmdm200)
and subsequently fill this derived from item field (tscfg200.item).
When Service Default Item Data (tsmdm205) are not available no object will be generated.
For the 'Top Object' this means that no Configuration Structure will be generated.
For a Child Item this means that it will be skipped in the generation of Configuration Structure.

Solution: 128633
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40c
128444, 128785
Defects solved in B50b, 71a
123192, 127031, 209523, 209564
Descriptions:
- Defect 123192 Don't raise multi occ when refresh from single occ
- Defect 127031 FS find() non-existing blank record returns 1
- Defect 128444 FS find() non-existing blank record returns 1
- Defect 128785 MB long labels on form causing index out of dims in ba.
- Defect 209523 Returning of zoom value goes wrong
- Defect 209564 QBF sorting caused fatal error during last set.
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 128634
SITUATION IDENTIFIED IN:
"Installment Orders" (tdsls4506m000)
SITUATION DESCRIPTION:
When a sales order is maintained with indirect settlement type and having multiple sales order lines and one of the line is
having details lines. Now, Installments orders are not getting closed though all lines are delivered and there are no back
orders existing.
SOLUTION DESCRIPTION:
Now the problem is solved, Installments orders will be closed once all lines are delivered and there are no back orders
existing.

Solution: 128635
SITUATION IDENTIFIED IN:
"Item Costing Data" (tdisa0107s000)
SITUATION DESCRIPTION:
When Standard Cost Price is calculated for a new item the fatal error "Index out of dimension" occurs.
SOLUTION DESCRIPTION:
The fatal error doesn't occur now.

Solution: 128637
SITUATION IDENTIFIED IN:
"Purchase Order lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1) When the Purchase order is generated for a Sales Order, the unit in the purchase order line is always in the Inventory unit
of the item. Instead, it should be converted and created in the Purchase unit of the item.
2) Suppose that there are two planned purchase orders in Projects. When these two planned orders are transferred together
to Purchase Orders for the same Buy-from-BP, they are created under two different Purchase Orders
SOLUTION DESCRIPTION:
1) Now, the purchase order would be generated in the Purchase Unit of the item.
2) The two planned orders will be clubbed together in a single purchase order.

Solution: 128643
SITUATION IDENTIFIED IN:
"Print Receipts" (tdpur4431m000)
SITUATION DESCRIPTION:
Packing slip was not printed on the report. And the form field's navigation over the session was not correct.
SOLUTION DESCRIPTION:
The Packing slip is printed on the report only when the option for printing the report with the receipt number.
And also, the form field's navigation is also corrected.

Solution: 128647
SITUATION IDENTIFIED IN:
"Finalization Run Numbers" (tfgld1110m000)
SITUATION DESCRIPTION:
Automatic transactions added to postings of opening balance batch and to the transaction type of "Automatic balancing of
P&L Accounts"
SOLUTION DESCRIPTION:
Automatic transactions are not added to postings of opening balance batch and to the transaction type of "Automatic
balancing of P&L Accounts"

Solution: 128648
SITUATION IDENTIFIED IN:
"Service Material Cost Lines" (tssoc2121s000)
SITUATION DESCRIPTION:
1. When saving a Service Order Material Cost line with an Item with Delivery Type "From Warehouse", a Warehousing Order is
generated. This is correct. When doing this for a Service Order where no Configuration is defined and no Ship to Business
Partner is defined the following Fatal Error is presented:
-Error 205 (Out of Range) on whinh200XXX in db_insert(51) -Can not continue in tssoc2121s000 in DLL: ottstpamdll (g.dal.in sert) [exec _function ]
The Service Package passes the wrong ship to code to Warehousing.
2. When creating a new Service Order without defining a Configuration and a Sold to Business Partner it is not possible to
save the Service Order. Message: "Currency not allowed" is presented. No Currency is defined and the Currency field is
disabled.
SOLUTION DESCRIPTION:
1. When saving Actual Material Cost Lines for external Service Orders, the Ship to
Business Partner is passed as ship to code for Warehousing. When there is no Ship to Business Partner the Sold to Business
Partner is used instead. For Internal Service Orders without Business Partner the Service Center is passed as ship to code.
2. When creating a new Service Order without defining a Configuration and Sold to Business Partner the Currency is
defaulted from the financial company of the Service Center.

Solution: 128649
SITUATION IDENTIFIED IN:
"Transfer Planned PRP Purchase Orders" (tppss6230m000)
SITUATION DESCRIPTION:
When Transfer Planned PRP Purchase Orders sessions is run with "Round Purchase Unit" option set to "yes", after
transferring the order the Planned PRP Orders are deleted. But the Planned Cost Object Transactions are not completely
deleted.
SOLUTION DESCRIPTION:
Now the above-mentioned problem is solved. Planned Cost Object Transactions are correctly deleted now.

Solution: 128655
SITUATION IDENTIFIED IN:
"Print Statements of Account" (tfacr3440m000)
SITUATION DESCRIPTION:
When anticipated receipts with step "Doc sent to customer" were attached to an invoice, the invoice amounts and receipt
amounts were not being calculated correctly for such invoices in the statement of account .
SOLUTION DESCRIPTION:
Now the invoice and receipt amounts for such invoices are correctly calculated in the statement of account .

Solution: 128657
SITUATION IDENTIFIED IN:
"Complete Production Orders" (tisfc0520m000)
SITUATION DESCRIPTION:
1. There are two operations attached to the production order and the operations are carried out in work centers that belong
to different Financial Companies.
2. While completing the order in partial quantities, the fatal error "Duplicate value 100" occurs.
SOLUTION DESCRIPTION:
The error 100 no longer appears and the Production order can be completed.

Solution: 128662
SITUATION IDENTIFIED IN:
"Select Invoices for Reminder" (tfacr3210m000)
SITUATION DESCRIPTION:
1. Invoices getting selected without Reminder Method attached to Business Partner
2. Default not working for representative.
3. Though Business Partner balance is negative, Reminder are sent to customer when range of sale representatives are
entered.
SOLUTION DESCRIPTION:
1. Business Partner without Reminder Methods is not selected.
2. Proper defaults of Representatives are done.
3. If BP balance is negative and Parameter "Do Not Send" is ON then reminders are not sent to the Business Partner.

Solution: 128665
SITUATION IDENTIFIED IN:
"Copy Scenario Data" (cprpd4201m000)
SITUATION DESCRIPTION:
When copying scenario data with option special demand checked a fatal error: Use of NULL pointer on '' occurs.
SOLUTION DESCRIPTION:
The initialization for special demand has been changed to avoid the fatal error.

Solution: 128666
SITUATION IDENTIFIED IN:
"Netlist" (ttstpaudread)
SITUATION DESCRIPTION:
E-Services has developed a NetList BOI for Priorities (table - tssma304, Baan4c4), whose Primary key(prno) is of type integer
and length 3. When we retrieve a record having priority length 3, then its value is retrieved properly.
In case if the priority length was less than 3, '0' is returned to the Client.
Values were not getting retrieved properly at client side.
SOLUTION DESCRIPTION:
While filling primary key values in xml tree, they were not stripped. Which was causing the above problem.
The code is modified, so that primary key values are now stripped before filling up the tree.

Solution: 128667
SITUATION IDENTIFIED IN:
"Release to Central Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
When releasing a Sales Order Line to Central Invoicing the Cost of the Goods Sold was set to 0.0 if the corresponding
Warehousing Order Outbound Line had been removed.
SOLUTION DESCRIPTION:
1. It will not be possible to remove the Warehousing Order Outbound Line as long as the Sales Order Line has not be fully
processed.
2. In case the corresponding Shipment Line or Warehousing Order Outbound Line has been removed, it will not be possible to
release the Sales Order Line to Central Invoicing.

Solution: 128668
SITUATION IDENTIFIED IN:
"Maintain and confirm backorders" (tdsls4125m000)
SITUATION DESCRIPTION:
Performance problems occur when starting the session 'Maintain and confirm backorders' (tdsls4125m000)
SOLUTION DESCRIPTION:
The trace information indicated that there were two queries in the program script which showed poor performance. These
queries have been adjusted. Some statements were added and the structure was changed so the performance was improved.

Solution: 128673
SITUATION IDENTIFIED IN:
"Reminder Advice" (tfacr3420m000)
SITUATION DESCRIPTION:
Reminder Advice does not include Interest if the reminder advice is printed for the first time with the option "Update
Letter number" = No.
SOLUTION DESCRIPTION:
Now the interest is calculated when the reminder advice is printed for the first time with the option "Update Letter number"
= No

Solution: 128674
SITUATION IDENTIFIED IN:
"Program Scripts / Libraries" (ttadv2530m000)
SITUATION DESCRIPTION:
The content of the manual pages is not present in ASCII help, but the form command "Manual Pages" is shown both when
Windows help is being used and when ASCII help is being used.
SOLUTION DESCRIPTION:
The Form Command "Manual Pages" is disabled when the user is not using Windows help.

Solution: 128675
SITUATION IDENTIFIED IN:
"Print sales statistics" (tdsst0401m000)
SITUATION DESCRIPTION:
Label is wrong in the German version
SOLUTION DESCRIPTION:
The initials in the label are adjusted in the German version

Solution: 128683
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
According to the calendar the warehouse is closed every Saturday and Sunday.
Entering an ATP controlled item on a sales order.
When accepting an ATP-Schedule proposal that resulted in a delivery date on Saturday or Sunday the order line details are
inserted with the suggested delivery dates without a warning. It should the calendar attached to the warehouse and adjust the
delivery date according to that calendar if needed
SOLUTION DESCRIPTION:
When accepting the proposal the delivery date is checked to see if it fits the calendar linked to the delivery warehouse. If the
suggested date is incorrect automatically the first possible delivery date is calculated based on the calendar.

Solution: 128685
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
A sales order line is delivered from more than one stock point. This results in splitting of the sales order line into several
details. This order is returned back. The original order is linked to this new return order. Now the button "Select Orig.
Lines is pressed and all order lines are selected via session "Select Sales Order Lines for Copying" (tdsls4535m000). When
the copying process is executed two new lines are added but with the total order line quantity for each new line. This is
incorrect because the return order quantity is now doubled.
SOLUTION DESCRIPTION:
Modifications inserted to make sure the copying will result in two lines with the correct quantity and with the correct link to
the original sales order.

Solution: 128688
SITUATION IDENTIFIED IN:
"Accept Values of GRNI reconciliation" (tfacp1535m000)
SITUATION DESCRIPTION:
The rotate currency option does not work for the amounts displayed in the header of session "tfacp1535m000 - Accept
Values of GRNI Reconciliation"
SOLUTION DESCRIPTION:
The rotate currency option works now for all displayed amounts on the form.

Solution: 128691
SITUATION IDENTIFIED IN:
BSS
SITUATION DESCRIPTION:
The Overtime Spent Information form does not show the units for Spent Normal,Spent Overtime and Total Overtime fields.
SOLUTION DESCRIPTION:
The time unit for the Spent Normal and Spent Overtime fields is now displayed by getting the value from the Labor Rate
Time Unit field in the General Service Parameters(tsmdm0100s000) session in BaanERP.The Total Overtime field is always
shown in hours.

Solution: 128694
SITUATION IDENTIFIED IN:
"Generate Connect Times by Network" (ecedi0225m000)
SITUATION DESCRIPTION:
When running the session "Generate Connect Times by Network (ecedi0225m000), the days calculated are incorrect when
the first day of the week (defined in "Companies; ttaad1100m000) is not Sunday.
SOLUTION DESCRIPTION:
The program script has been corrected. The company's first day of the week was not taken into account. Now the days are
calculated correctly.

Solution: 128704
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
1. There is an Outbound Order Line for an item with issue status 'Issue Components'.
2. From the specific menu option of the session "Issue Components" (whinh2520m000), the session "Outbound Advice by
Order Line" (whih2525m200).
3. A new advice is created here for the component, which is a LOT controlled item. The Lot field is enabled for input.
4. With out closing the item, one more advice line is created for the same item and now, the lot field is not enabled.
SOLUTION DESCRIPTION:
The Lot field is enabled now even if the user creates a new advice for the same item with out closing the session.

Solution: 128709
SITUATION IDENTIFIED IN:
"History" (tpppc2850m000)
SITUATION DESCRIPTION:
If a purchase order is unapproved, a hard commitment line is created in commitments. Correspondingly a cost line (with
negative amount) is also created in costs session. Now, if periods have been closed before posting these lines, the costs are
correctly posted in the next open period, but the hard commitment line in history appears in the same old period that is
closed. This should not happen.
SOLUTION DESCRIPTION:
Now, the hard commitment line formed due to unapproval of invoice will also be posted to the next open period along with
cost line, if the given period is closed.

Solution: 128710
SITUATION IDENTIFIED IN:
"Element budget(material)" (tpptc1110s000)
SITUATION DESCRIPTION:
Even when there is no price book by item maintained for a item for a specific date system gets the purchase price from the
price book by item which is actually maintained for another date. The value of date is not at all considered.
SOLUTION DESCRIPTION:
Now the price retrieved from price book by item is based on the budget date only.

Solution: 128716
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
The materials retuned from service to warehousing are logged with the FTP price in "Integration Transactions by
Project/Order" (tfgld4510m000). This should be done with the actual inventory value depending on the 'Inventory
Valuation Method' for the Item and Warehouse combination.
SOLUTION DESCRIPTION:
The return Service/Issue type of integration is logged with the actual inventory value and not the with the FTP price of the item.

Solution: 128717
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
While EBS batch posting was done, it was posting the GLD batch transaction type with a new document number for every
document in the EBS batch.
SOLUTION DESCRIPTION:
Now the new document number will be created only when there is a change in the Bank transaction type or EBS batch.

Solution: 128718
SITUATION IDENTIFIED IN:
"Pay-to Business Partners" (tccom4124s000)
SITUATION DESCRIPTION:
A Business partner (child BP) is linked to a Parent Business partner in "Business Partners"(tccom 4110s000) and Pay-to Business
partner role of the child BP is set to 'Inactive'. Now in "Purchase Invoices" (tfacp1110s000), in 'Invoice data', if 'Business
partner' is filled with child BP, then the 'Pay-to BP' in 'Payment data' is defaulted as child BP even though the 'Pay-to' role
of the child BP is set to inactive. System is not picking the BP defined in 'Invoice-from' role of the child BP.
SOLUTION DESCRIPTION:
When pay-to role of the child Business Partner is 'Inactive', then the system will ignore the 'Pay-to role' and picks up the 'Pay-to B.P' defined in the 'Invoice-from' role of the child BP.

Solution: 128727
SITUATION IDENTIFIED IN:
"Purchase Order Lines Overview" (tdpur4501m500)
SITUATION DESCRIPTION:
The Business Partner's Name is not displayed in the session "Purchase Order Lines Overview (tdpur4501m500)". This is
unhandy and makes it difficult for the user, as the user needs to remember the BP Code.
SOLUTION DESCRIPTION:
Now the Business Partner's name is displayed in the third form of the above session.

Solution: 128730
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Enterprise Planning generates rescheduling IN/OUT messages on Holidays.
SOLUTION DESCRIPTION:
The system generates rescheduling messages to working days.

Solution: 128738
SITUATION IDENTIFIED IN:
"Aspect Values" (tigrt0281m000)
SITUATION DESCRIPTION:
In session "Aspect Values" (tigrt0281m000), the default values in 'From' field and 'To' fields are not correct.
SOLUTION DESCRIPTION:
In session "Aspect Values" (tigrt0281m000), the default values will be displayed in 'From' field as empty and 'To' field as "zzzzzzz".

Solution: 128741
SITUATION IDENTIFIED IN:
"Bills of Material" (tibom1510m000)
SITUATION DESCRIPTION:
When duplicating a BOM line having Text, the target BOM line has the same BOM text number as the original BOM line. The
problem that exists is that if user changes the text on the newly created BOM line (i.e. the copied line), it will also change
the text on the original BOM line.
SOLUTION DESCRIPTION:
While Duplicating the BOM line, text will be copied to new text number so that if the user changes the text on one BOM line
will not reflect in other BOM line.

Solution: 128749
SITUATION IDENTIFIED IN:
"Generate Inbound Advice " (whinh3201m000)
SITUATION DESCRIPTION:
Inbound Advice line with the line status " Put away " gets deleted by doing "Undo" in session whinh3201m000 (Generate
Inbound Advice)
SOLUTION DESCRIPTION:
System will not delete lines that are already put away while doing Undo advice.

Solution: 128752
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
After entering the original invoice in the credit note, the Late Payment Surcharge, Terms of Payment and Due date are
defaulted as that of the original invoice and are able to modify.
SOLUTION DESCRIPTION:
After entering the original invoice in the credit note, the Late Payment Surcharge, Terms of Payment and Due date are
defaulted as that of the original invoice and are not allowed to modify.

Solution: 128754
SITUATION IDENTIFIED IN:
"Generate Progress by Extension/Cost Object" (tpppc1188m000)
SITUATION DESCRIPTION:
The inventory unit in the general item table is not mandatory for cost items. Due this functionality we get a fatal error if
we try to generate progress by extension. Now a check is done on the inventory unit & a message will be given if inventory
unit is not found.
Note: Same problem was there for many "Generate Progress" Sessions. They have been corrected in this solution.
SOLUTION DESCRIPTION:
Now if the control code of item does not have a unit, a message to this effect will come in place of a fatal error.

Solution: 128758
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: 128760
SITUATION IDENTIFIED IN:
"EDI Interchange Controller" (ecedi7210m000)
SITUATION DESCRIPTION:
When running the EDI Interchange Controller (ecedi7210m000), a file can be specified as device, and the path (including the
file) can be filled in the field "Output File". However, no output is found in the path specified.
SOLUTION DESCRIPTION:
The system did not use the output file specified. If a path was specified in "Device Data" (ttaad3100s000), that file was
being used. The program script has been corrected. Now the system always defaults the path specified in "Device Data". This
default path can be overwritten by the user. The output is now correctly written to the file specified by the user.

Solution: 128763
SITUATION IDENTIFIED IN:
"Print Service Order History" (tssoc8450m000)
SITUATION DESCRIPTION:
The reports of session "Print Service Order History" don't show the business partner codes and business partner descriptions
completely.
SOLUTION DESCRIPTION:
The reports of session "Print Service Order History" show the business partner codes and business partner descriptions
completely. On these reports, enough space has been reserved for these codes and the descriptions.
Solution: 128764
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1111s000)
SITUATION DESCRIPTION:
Default tax code not displayed when the tax is defined based on GEO Codes in the session "Tax Codes by GEO Code"
(tcmcs1136m000).
SOLUTION DESCRIPTION:
Now Tax code is defaulted if defined based on GEO Codes

Solution: 128766
SITUATION IDENTIFIED IN:
Print Payment Advice(tfcmg1401m000)
SITUATION DESCRIPTION:
IBAN: Wrong Account is printed in the report "Payment Advice by Pay-To Business Partner" (tfcmg140117000).
SOLUTION DESCRIPTION:
The reported problem is solved and now the correct bank account will get printed on the Report. (Either IBAN or the
Normal Bank Account depending on the option chosen)

Solution: 128771
SITUATION IDENTIFIED IN:
"form editor" (ttadvformedit)
SITUATION DESCRIPTION:
When opening and closing a form field when on the left hand of this field a Multibyte label is present then the field will
move.
SOLUTION DESCRIPTION:
The opening and closing of the field details is now handled correctly

Solution: 128772
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Wrong starting value of total quantity.
SOLUTION DESCRIPTION:
Starting value adapted.

Solution: 128783
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
It was not possible to view the configuration entered for a call graphically in the "Calls"(tsclm1100s000) session.
SOLUTION DESCRIPTION:
It is now possible to view the graphical display of the configuration on a call by choosing the option "Graphical
Configuration..." under the specific menu in the "Calls"(tsclm1100s000) session.

Solution: 128784
SITUATION IDENTIFIED IN:
"Remove Fully Paid Sales Invoices" (tfacr2260m000)
"Remove Fully Paid Purchase Invoices" (tfacp2250m000)
SITUATION DESCRIPTION:
No session available to archive the Anticipated Payment/Receipts tables (tfcmg110 till tfcmg112).
SOLUTION DESCRIPTION:
Via session(s) "Remove Fully Paid Sales Invoices" and "Remove Fully Paid Purchase Invoices" , all Anticipated
Payments/Receipts (including Cash Journals) can be archived and deleted from Anticipated Payments/Receipts tables
(tfcmg110 , tfcmg111 and tfcmg112) .

Solution: 128785
SITUATION IDENTIFIED IN:
"Projects" (tipcs2501m000)
SITUATION DESCRIPTION:
The description of the project is not correct , when project selected in session "Projects" (tipcs2501m000) is entered new or
if the description of the project is modified.
SOLUTION DESCRIPTION:
The descriptions of the project are displayed correctly

Solution: 128787
SITUATION IDENTIFIED IN:
"Finalize Engineering Data" (tiedm3240m000)
SITUATION DESCRIPTION:
Fatal Error "Record is not locked" while finalizing an Engineering Change Order.
SOLUTION DESCRIPTION:
The system finalizes the Engineering change order correctly.

Solution: 128791
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When session "Confirm Shipments/Loads" (whinh4275m000) is run for shipments having multiple shipment lines for the same
item, having inventory valuation method as "LIFO" and the Order is a transfer order from warehouse to project, then the
actual cost booking is booked incorrectly in Projects. This happens when the item has different order price in the orders.
SOLUTION DESCRIPTION:
The price is updated correctly in Projects based on the inventory valuation method used.

Solution: 128792
SITUATION IDENTIFIED IN:
"Service Order Actual Material Costs" (tssoc2121s000)
SITUATION DESCRIPTION:
An estimated material line 'From Warehouse' is created and released. The price for this line is not retrieved from the price
book. Instead this is retrieved from the Item Service Data. If the price in Item Service Data is 0, then no price is retrieved.
The above only happens with the following parameter settings:
1. The parameter 'Service price Search Method' in "General Service Parameters" (tsmdm0100s000) is Price books
Service/Sales.
2. The field Price Date Type' is 'Delivery Date' in Pricing Parameters (tdpcg0100s000).
SOLUTION DESCRIPTION:
The item price will be retrieved from the price books, with the parameter settings as described in the situation description.
The delivery date will be determined as follows:
A) If Planning method in "Service Order Parameters" (tssoc0100s000) is 'By Service Order' and the Earliest Start Time is
present in "Service Orders" (tssoc2100s000), then this date will be used. Otherwise, the 'Planned Start Time' of the service
order will be used.
B) If Planning method in "Service Order Parameters" (tssoc0100s000) is 'By Service Order Activity' and the Earliest Start
Time is present in "Service Orders Activities" (tssoc2110s000), then this date will be used. Otherwise, the 'Planned Start
Time' of the service order activity will be used.

Solution: 128794
SITUATION IDENTIFIED IN:
"Business Partner Invoices In a Company" (tfacr2535m000)
SITUATION DESCRIPTION:
Rotate currency not displaying the consistent values for the amounts.
SOLUTION DESCRIPTION:
Rotate currency displays consistent values for the amounts.

Solution: 128802
SITUATION IDENTIFIED IN:
"Purchase-Order Parameters" (tdpur0100s400)
SITUATION DESCRIPTION:
Help Text missing for the Purchase Order parameter "Prompt for Change Codes" (Form 2).
SOLUTION DESCRIPTION:
Help Text is available now for the Purchase Order parameter "Prompt for Change Codes".

Solution: 128805
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
The record length of the record 21 was 191 instead of 192.
SOLUTION DESCRIPTION:
The record 21 has been extended with one character. Now it will always be 192 long.

Solution: 128806
SITUATION IDENTIFIED IN:
"Archive Production orders" (ticst0250m000)
SITUATION DESCRIPTION:
When archiving production orders by "Archive Production orders" (ticst0250m000), the records of the order in "Breakdown
of Actual hours" (ticst004) are NOT archived in the Archive Company. But these records in the original Company are
deleted.
SOLUTION DESCRIPTION:
If production orders are archived through "Archive Production orders" (ticst0250m000), the records of the order in
"Breakdown of Actual hours" for that order are archived in the archive Company. And these records in the original Company
are deleted.

Solution: 128812
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220s000)
SITUATION DESCRIPTION:
Incorrect message that the selection is complete when invoice has not been selected
SOLUTION DESCRIPTION:
The reported problem is solved and now a correct message "No Invoices Selected" will be given when the Invoice has not
been selected.

Solution: 128814
SITUATION IDENTIFIED IN:
"Help Viewer" (ttstphelp)
SITUATION DESCRIPTION:
Comment lines in help text, which are marked with '|#' are shown when displaying the help text.
When help text is changed, the reason for the change can be explained with comments in the help text.
These comment lines start with "|#". Sometimes these comment lines are shown in the help text.
SOLUTION DESCRIPTION:
Help text in Baan is saved in buffers of a certain size. The problem occurred when the last characters of such a buffer was the
End-of-line character, followed by the first character of a comment line, so "\n|".
An extra check in the program solves the problem.

Solution: 128815
SITUATION IDENTIFIED IN:
"Print Solutions by Update VRC" (ttpmc2401m000)
SITUATION DESCRIPTION:
The status of PMC solutions was not always printed correctly. This only happened when the option to print also the
dependencies was selected. In this case the printed status was taken from a dependent solution.
SOLUTION DESCRIPTION:
The correct status is printed now.

Solution: 128817
SITUATION IDENTIFIED IN:
"Warehouse Orders" (whinh2500m000)
SITUATION DESCRIPTION:
1. There is a Manual (Transfer Order) Order present in the system.
2. This order is copied to a new order. If the sum of the Maximum Quantity percentage of the source order and the Over
Delivery percentage defined in "Inventory Handling Parameter" (whinh0100s000) exceeds 999.99, the system gives 'Fatal
error 205 in insert'.
SOLUTION DESCRIPTION:
The Maximum Quantity percentage of the source order would be simply copied to the new order and the Over Delivery
percentage is not added to that. It is possible to save the copied orders.

Solution: 128823
SITUATION IDENTIFIED IN:
"Purchase Order Header" (tdpur4100s000)
SITUATION DESCRIPTION:
A Purchase Order type has input controls. When the user comes from lines to header by clicking the "Header" button, the
'Save' and 'Text' buttons are not enabled.
SOLUTION DESCRIPTION:
Now, during the Second Pass of the Header the 'Save' and 'Text' buttons will be enabled though the Order type has Input
Control defined.

Solution: 128825
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
1. When registering a purchase invoice of an order the actual currency rate is taken and can only be adjusted to the original
rate of the order by manually changing the currency rate.
2. Project transactions are not removed even when after the question "Remove existing transactions?" "YES" is pressed.
3. When changing the amount in an Invoice header to the amount of the Invoice lines after entering a cost invoice, with an
amount of 0.00 in the Invoice header and an amount <> 0.00 in the Invoice lines the invoice status never changes to
"transactions entered".
SOLUTION DESCRIPTION:
1. When registering a purchase invoice of an order the original rate of the order is taken in account.
2. Project transactions are removed after the question "Remove existing transactions?" "YES" is pressed because a matched
order has to be unmatched before changes can be made.
3. When changing the amount of an Invoice header to the amount of the Invoice lines after entering a cost invoice, with an
amount of 0.00 in the Invoice header and an amount <> 0.00 in the Invoice lines the invoice status will change to
"transactions entered".

Solution: 128831
SITUATION IDENTIFIED IN:
"Session Authorizations by Session" (ttams3132m000)
SITUATION DESCRIPTION:
When using the zoom function on the Field "Module" in session "Session Authorizations by Session" (ttams3132m000) the
field doesn't show the return value.
SOLUTION DESCRIPTION:
When using the zoom function on field "Session Authorizations by Session" (ttams3132m000) the field now shows the
return value.

Solution: 128846
SITUATION IDENTIFIED IN:
"Planned material transaction" (tppss6110m000)
SITUATION DESCRIPTION:
The price matrix is not taken into account when we change the quantity again
SOLUTION DESCRIPTION:
Now purchase price is updated properly when qty. is changed.

Solution: 128850
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B40c
127407, 128704, 209385
Defects solved in B50b, 71a
127407, 209385
Descriptions:
- Defect 127407 hanging sessions when and end() is encountered
- Defect 128704 "Not authorized" character not printed
- Defect 209385 fixed by 127407
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 128851
SITUATION IDENTIFIED IN:
"Print Multi-level cost price calculation" (ticpr2420m000)
SITUATION DESCRIPTION:
When printing Multi-level cost price calculation of an item by 'Details by cost component' flag checked, the operation time
is printed wrongly if man time or machine time is zero for the operations.
SOLUTION DESCRIPTION:
When printing the operation costs for an item in session "Print Multi-level cost price calculation" (ticpr2420m000), if man
hours or machine hours for an operation are zero, then system will consider the non zero hours for printing operation time.

Solution: 128857
SITUATION IDENTIFIED IN:
"Text Editor" (tttxt2210s000)
SITUATION DESCRIPTION:
When using MS Word as the text editor, when changing text language from the menu options, a BW error is generated.
SOLUTION DESCRIPTION:
Now it is possible to change the language in the text editor, and save text records in multiple languages, without errors

Solution: 128869
SITUATION IDENTIFIED IN:
"Labor Costs" (tpppc2531m000)
SITUATION DESCRIPTION:
Performance of the session needs to be improved. Takes more time when we start the session
SOLUTION DESCRIPTION:
Performance of the session is improved by stopping the repeated calculation of "Normal Hours", "Over Time". This will
improve the performance of the session.

Solution: 128879
SITUATION IDENTIFIED IN:
"Print Service Order History" (tssoc8450m000)
SITUATION DESCRIPTION:
The report "Service Orders History (Detailed)" of session "Print Service Order History" doesn't show the business partner
codes and business partner descriptions completely.
SOLUTION DESCRIPTION:
The report "Service Orders History (Detailed)" of session "Print Service Order History" shows the business partner codes and
business partner descriptions completely. On this report, enough space has been reserved for these codes and the descriptions.
Solution: 128880
SITUATION IDENTIFIED IN:
"Subcontracting Invoices" (tfacp3160s000)
SITUATION DESCRIPTION:
For a subcontracting invoice, the wage part in invoice currency is getting calculated using the purchase rate, instead of the
rate type used in the purchase invoice.
SOLUTION DESCRIPTION:
For a subcontracting invoice, the wage part in invoice now is getting calculated using the rate type used in the purchase
invoice.

Solution: 128889
SITUATION IDENTIFIED IN:
"Print Inventory by Item and Package Information" (whinr1441m000)
SITUATION DESCRIPTION:
Wrong column title in report "Inventory data by item and warehouse"
SOLUTION DESCRIPTION:
Column title was changed from 'Inventory Allocated' to 'Inventory Available'.

Solution: 128893
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The session Generate Invoices by selfbilling was designed as one huge logical transaction because which the following
problems were noticed.
1. The batch number was locked too long , because which other process trying to create batch numbers resulted in Fatal
error.
2. Performance loss due to retries.
3. When something goes wrong with the particular receipt ( for example missing ledger account in mapping scheme for invoice
accrual account ), then all the previously processed receipts were reverted back.
SOLUTION DESCRIPTION:
Now the session is designed into smaller logical transaction.
1, Batch is created in the beginning of process. If no transaction is created in the batch, then the batch status set to deleted.
2. The transactions are committed into the tables after each Invoice is created.

Solution: 128895
SITUATION IDENTIFIED IN:
"Currency Rates" (tcmcs0108m000)
SITUATION DESCRIPTION:
In a Multi Site setup when table tcmcs008 (Currency Rates) is shared a problem may arise when the End User is trying to insert
new currency rates with an effective date before the last Cost Price calculation date. This is due to the fact that the general
item data tables (tcibd001/tcibd007) are not shared over the same set of companies.
SOLUTION DESCRIPTION:
From now onwards, the check for the last performed Cost
Price Calculation will not only check Item Costing Data (tcibd007) in
the current company, but also the other logistical companies in which tcmcs008 (Currency Rates) is shared.

Solution: 128897
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
SITUATION DESCRIPTION:
When creating a Sales Order Line with these properties;
Invoice goes: from the Netherlands to the Netherlands (or any other EU member), and
Goods go: from Switzerland to Switzerland (or any other NON EU member),
a message "EU tax code not defined." could appear. However, as Switzerland is the leading country for Tax determination
but not part of the EU, this message is not correct. The result was that the wrong VAT country was shown on the form
"Invoicing".
SOLUTION DESCRIPTION:
The situation when a Sales Order line is created and the;
Invoice goes: from the Netherlands to the Netherlands (or any other EU member), and
Goods go: from Switzerland to Switzerland (or any other NON EU member),
the correct default VAT country is derived and shown on the form "Invoicing" in case of a Sales Order Line.

Solution: 128901
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Order Lines" (whinh5101s000)
SITUATION DESCRIPTION:
If an adjustment order is created (in session whinh5500 "Cycle-Counting/Adjustment Orders") with two different lines and
the second line:
1) is created in session whinh5501m000 "Cycle-Counting/Adjustment Order Lines" without closing whinh5101s000
"Cycle-Counting/Adjustment Order Lines" session
2) same item as first line is used
then all the fields are enabled for this second line in session whinh5101s000, allowing for instance:
a) to enter an inventory date when outbound priority of the item is by location
b) to enter a location when item is not location control...
SOLUTION DESCRIPTION:
Now fields in session whinh5101s000 are enabled/disabled depending on the characteristics of the item per every line.

Solution: 128902
SITUATION IDENTIFIED IN:
"Print WIP" (ticst0450m000)
SITUATION DESCRIPTION:
Performance problem
SOLUTION DESCRIPTION:
Improved 2 queries

Solution: 128909
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
No VAT Postings are found for Journal Transactions When EBS batch is posted.
SOLUTION DESCRIPTION:
Now VAT postings are posted for Journal Transactions when EBS batch is posted.

Solution: 128910
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
Error message "Transaction is on, can't continue" occurs when configuring a generic item.
This error message can occur when having defined constraints with syntax: "...display = false" or "...input = false".
SOLUTION DESCRIPTION:
Error message no longer occurs. Problem was located in incorrect program flow, trying to perform an update of the wrong
table.

Solution: 128914
SITUATION IDENTIFIED IN:
"Copy Company Data" (tccom0214m000)
SITUATION DESCRIPTION:
When we create Sequential Dump of Tables using bdbpre with option -M, multiple dumps are created. e.g.: ttdsls400560.S,
ttdsls400560.S.1, ttdsls400560.S2
Using the session Copy Company Data (tccom0214m000), we can change the company number by reading the table tccom990.
The session doesn't have the functionality of reading multiple dumps. It could only read the file ttdsls400560.S.
SOLUTION DESCRIPTION:
Now session Copy Company Data (tccom0214m000) can read multiple dumps and change the company numbers
successfully.

Solution: 128921
SITUATION IDENTIFIED IN:
"Print Installments" (tppin4451m000)
SITUATION DESCRIPTION:
When a text is added to an installment, by default this text is entered in the language of the 'Invoice-to' business partner for
this installment.
However, when printing a list of installments with "Print Installments" (tppin4451m000) the whole report is in the language of
the user. If that language differs from the language of the business partner, the texts that were entered will not be printed.
SOLUTION DESCRIPTION:
When printing a list of installments with "Print Installments" (tppin4451m000) the report is in the language of the user, but
the texts on the installments will be printed in the language of the 'Invoice-to' business partner.

Solution: 128937
SITUATION IDENTIFIED IN:
"Release To Invoicing" (tdsls4501m130).
SITUATION DESCRIPTION:
Error: "Combination of Country ... and Tax Code ... not found; please add this combination" can occur when releasing Sales
Orders to Invoicing.
This can happen when the Ship-to Address on a detail is changed and tax of the current detail line is recalculated.
Although the calculated country / tax combination may be invalid, the record can can be saved and released to Warehousing
without any problem.
When the order is released to Invoicing the error will occur.
SOLUTION DESCRIPTION:
A check is implemented that assures a valid tax code / country combination is available for a given destination, after the
Ship-to Address of an Order line Detail has been changed and the tax code has been recalculated.
Composing of invoices in Central Invoicing is done using the following fixed aggregation criteria: (see session help-text of session: "Global Confirmation of Future Invoices" (cisli2219m000). invoice-to bp sold-to bp ship-to bp pay-from bp invoice-to addresss rate determinator sold-to address ship-to address
pay-from address invoice currency terms of payment late-payment surcharge tax country financial company
As a consecuence of this it is checked from now on that for a given order number, position number, ship-to business partner,
ship-to address, country combination all detail lines contain the same vat code.
(Note that of all the above mentioned fields only these can be changed manually when entering sales order line details,
therefore the other fields are irrelevant with respect to this issue).
Otherwise, although a certain country / tax combination itself could be valid, when composing / printing the invoices, due to
the fixed aggregation criteria, there would not be a breakdown per vat code.
The form, used to enter Sales Order Line Details (tdsls4101s200) is modified in a way that from now on it is possible to
enter / change the country and vat code manually.

Solution: 128949
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Payments to Invoices" (tfcmg2105s000, tfcmg2106s000, tfcmg2107s000, tfcmg2119s000 )
SITUATION DESCRIPTION:
1.The assignment of an unallocated or advanced receipt to an invoice or a credit note does not work correctly.
2. Impossible to unlink a negative unallocated payment to a Credit Note once the allocation has been processed
SOLUTION DESCRIPTION:
Now the assignment works properly and it is possible to unlink a negative unallocated payment to a Credit Note once the
allocation has been processed .

Solution: 128959
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When entering sales order line for an item that is linked to a contract it can take up to 10 seconds before the correct price
appears.
SOLUTION DESCRIPTION:
The method of searching the valid contracts for this order line is improved.

Solution: 128964
SITUATION IDENTIFIED IN:
"Select Device" (ttstpsplopen)
SITUATION DESCRIPTION:
When the package combination of the user as entered in the 'user data' is different from the current package combination of the
user as set in the BW configuration, then the report defaults for the report, like font, width, etc. are not picked from the
correct VRC of the report.
SOLUTION DESCRIPTION:
Now the search for the report defaults is carried out correctly starting from the VRC based on
the current package combination of the user. Report width and font etc are retrieved correctly .

Solution: 128984
SITUATION IDENTIFIED IN:
"Correct COGS Intgrations" (cicor0111m000)
SITUATION DESCRIPTION:
User needs the flexibility to correct transactions even present in the closed period.
SOLUTION DESCRIPTION:
The user is now given the flexibility to correct the transactions booked in a closed period also.
Now if the option "Correct transactions of Closed Period" is enabled, then the user can give the date range falling in the
closed periods also.
So the wrong transactions booked in those periods will be deleted and new transactions will be booked in the next available
open period.

Solution: 128987
SITUATION IDENTIFIED IN:
"Integration transaction" (tfgld4510m000)
SITUATION DESCRIPTION:
-1- Using triangular invoicing, the amount of the generated transaction "Warehouse order" "Transfer price" is not
correctly rounded.( DF 129291)
-2- When the transaction origin is "sales" the amount of the general costs is always "0" ,even though the cost of good sold
(general) appear correctly as in the item master data (DF 129306)
-3- Amount are posted with Wrong transaction origin and financial transaction for production return when more than
issued quantity is returned ( DF 129377)
SOLUTION DESCRIPTION:
-
-1- Now the amounts are correctly rounded before generating the invoice
-2- This problem used to occur Localisation ( B50_C_bgl0 ) only , Now the general cost are correctly posted with the
cost price of the cost item
-3- Now the correct transaction origin and finacial tranasactions are posted in finance .
Solution: 128990
SITUATION IDENTIFIED IN:
"Payment Advice" (tfcmg1120s000)
SITUATION DESCRIPTION:
In Dependent Currency System, currency rate was picked up from the currency rate table when you gave ' Fixed hard' rate
determiner in the invoice.
SOLUTION DESCRIPTION:
In Dependent Currency System, currency rate is picked up from the invoice when you give ' Fixed hard' rate determiner in
the invoice.

Solution: 128996
SITUATION IDENTIFIED IN:
"Process Solutions" (ttpmc2101m000)
SITUATION DESCRIPTION:
When a PMC solution is installed and the B-Language Support was implemented, not all components were copied to the
B-Language. This happened when the component was delivered in language 2 (English) only, so when also other languages
were delivered in the solution, the B-Language component was created or updated.
It was intended functionality to ignore components for the B-Language processing when they were delivered in
English only; it was considered as a spelling correction for the English component when the other A-Languages were not delivered. However, several
localizations are maintained by Baan for the English language only. So for these components the B-Language variants were never created or updated.
SOLUTION DESCRIPTION:
When a component is sent in English only, it is considered now as a normal change, so the B-language components will be
created or updated always.

Solution: 129000
SITUATION IDENTIFIED IN:
"Item surcharges" (ticpr1510m000)
SITUATION DESCRIPTION:
When duplicating the surcharges of an item or copying surcharges of one item into other (global copy), the surcharge bases
are wrongly getting copied.
SOLUTION DESCRIPTION:
The surcharge bases are getting copied correctly, when surcharges are copied to the same item or to the different item.

Solution: 129004
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
When a purchase requisition is maintained for an item and a project is attached, then the related ledger account will be
defaulted. When we modify the purchase requisition line and change the project then the related ledger account is defaulted
but the description is not changing.
SOLUTION DESCRIPTION:
Now the problem is solved, when the project is changed in the purchase
requisition lines then the correct leger account will be defaulted, and also the ledger account description will be change.

Solution: 129009
SITUATION IDENTIFIED IN:
"Create Runtime Data Dictionary" (ttadv5210m000)
SITUATION DESCRIPTION:
When tables are reconfigured, there should be log-information in the file $BSE/log/log.reconfig.
On Windows systems, the file $BSE\log\log.reconfig is filled with time-stamps.
So, there is no way to tell on a Windows OS which tables were reconfigured.
Example of contents of file $BSE/log/log.reconfig on a system with UNIX Operating System:
02/03/16 2218
Table D Old New Messages
----------- - -------- -------- ----------------------
tdsls910710 * 100 200 300 400 498 100
200 300 400 498 Adding indexes ... done.
Example of contents of file $BSE\log\log.reconfig on a system with Windows Operating System:
02/08/21 0926
02/08/21 0926
SOLUTION DESCRIPTION:
To reconfigure tables, the Baan bdbreconfig command is used. With this bdbreconfig command several options can be used.
On Windows systems, option -E and -O are now used to save the errors and other output of the bdbreconfig command to
temporary files.
These files are afterwards added to file $BSE\log\log.reconfig.
In the $BSE\log\log.reconfig, information about reconfigured tables is now present.

Solution: 129023
SITUATION IDENTIFIED IN:
"Copy Table Data Authorizations to Childs" (ttaad4234s000)
SITUATION DESCRIPTION:
The first time session "Copy Table Data Authorizations to Childs" is used it works fine. When the authorizations of the
master-table are changed and the user wants to 'update' those changes to the child tables, this is not done correctly.
SOLUTION DESCRIPTION:
A checkbox "Overwrite" is introduced. When this checkbox is checked existing authorizations for a combination of Baan
User, Company, Table, Table Authorization and Data Authorization in session "Maintain Table Data Authorizations" will be
deleted, before the new authorizations are inserted. When the checkbox is not checked, the authorizations for an already
existing combination are left unchanged when the copy is done.

Solution: 129024
SITUATION IDENTIFIED IN:
"Help Viewer" (ttstphelp)
SITUATION DESCRIPTION:
Comment lines in help text, which are marked with '|#' are shown when displaying the help text.
When help text is changed, the reason for the change can be explained with comments in the help text.
These comment lines start with "|#". Sometimes these comment lines are shown in the help text.
SOLUTION DESCRIPTION:
Help text in Baan is saved in buffers of a certain size. The problem occurred when the last characters of such a buffer was the
End-of-line character, followed by the first character of a comment line, so "\n|".
Previous solution 128814 did not completely solve the problem: When the last two characters of a text-buffer were : "\n|", the
next line was seen as a comment line. This has been extended: now also the first character of the next text-buffer needs to be
the "#" character for the next line to be seen as a comment line.

Solution: 129026
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
In Dependent Currency System, currency rate was picked up from the currency rate table when you gave ' Fixed hard' rate
determiner in the invoice.
SOLUTION DESCRIPTION:
In Dependent Currency System, currency rate is picked up from the invoice when you give ' Fixed hard' rate determiner in
the invoice.

Solution: 129028
SITUATION IDENTIFIED IN:
"Purchase Order Header" (tdpur4100s000)
SITUATION DESCRIPTION:
When the 'Delivery Date' field is changed in the purchase order header, the price is recalculated for the cancelled purchase
order lines also.
SOLUTION DESCRIPTION:
The Price of the cancelled order lines would remain the same and it is not recalculated now.

Solution: 129034
SITUATION IDENTIFIED IN:
"ascii help" (ttstphelp)
SITUATION DESCRIPTION:
When starting contents help from menu browser/desktop browser or asking help topics from a tools session or pressing the
contents button in the help viewer results in help that contains Baan 4 issues. These and other links do not have help info
and the user gets the message No Help Available.
SOLUTION DESCRIPTION:
The contents help in the menu browser/desktop browser not jumps to an other help. The contens button in the help viewer also jumps
to that help. And the help where help topics jumps to is corrected so that is does not show Baan 4 related help.
In BaanERP, it is necessary to get help
from within sessions

Solution: 129056
SITUATION IDENTIFIED IN:
"Generate Project Structure for Product Variant" (tipcs2220m000)
SITUATION DESCRIPTION:
When a project structure is generated for a product variant of a generic item, if the component is also generic item, then the
sales price of the customized component is getting updated with purchase price of the original generic item.
SOLUTION DESCRIPTION:
The customized item derived from a generic item, which is a component of another generic item, will have the default sales
price.

Solution: 129058
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is not possible to go to Detail session once the single occurrence session is closed and opened again as the Detail button
is removed from the form during this condition.
SOLUTION DESCRIPTION:
Now it is possible to go to detail line session even from the first form of the purchase order line session.

Solution: 129063
SITUATION IDENTIFIED IN:
"Copy Range Of Lots" (whltc1201m000)
SITUATION DESCRIPTION:
When copying lots using session whltc1201m000 "Copy Range of Lots" the new lots get the following information copied
from the original lot:
lot size, first issue date, first receipt date, lot date and order number.
(It causes, for instance, that a newly generated lot cannot be used for a new SFC order)
SOLUTION DESCRIPTION:
This information it is not copied from the original lot any more, instead lot size, first issue and receipt date are initialized
to zero, lot date with the current date and order number is blank.

Solution: 129073
SITUATION IDENTIFIED IN:
"Generate EDI Messages" (ecedi7201m000)
SITUATION DESCRIPTION:
According to a new German requirement, the local tax number needs to be included in the outgoing EDI invoice. A new
table (Additional Address Info; tccom133) has been created via solution 128077.
SOLUTION DESCRIPTION:
The program script has been modified to support the additional address info in the outgoing EDI invoice. The field "Local
Tax Number" (tccom133.vatl) can be added to the header level of the conversion setup for the outgoing invoice. The local
tax number will be retrieved based on the address code of the company in which the messages are generated (defined in
the session "Companies"; tccom0100s000).

Solution: 129087
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 business partner
have 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:
No tax amounts are calculated if the tax flags are deactivated.

Solution: 129097
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4500m000)
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
1. Having a Sales Order (tdsls4500m000) with more lines. One line is advised. When changing the Ship To Address on the
Sales Order header, the Ship To address on the advised line is not changed and no message is shown.
2. B50_c_bgl0 environment only.
For the following set up a Cost / Service Item can not be released to Invoicing
"whinh0100s000" (Inventory Handling Parameters) "cost/service item on packing slip" Both
"tdisa0101s000" (Item Sales Data) "release to Warehouse" No
The message "'Packing slips should be printed before releasing to invoicing" comes up. This cannot be correct because the
Item is never released to warehousing so no Packing slip could have been printed
3. The sales price is not adjusted when linking a sales order line to a contract which conversion factor differs from the
current conversion factor.
4. When a Cross Docking Sales Order is over delivered, the new created detail line does not have the link to the Purchase
Order.
SOLUTION DESCRIPTION:
1. When a change is made on the header and a line cannot be changed, a correct error message is shown. The way of giving
through modifications from header to lines is restructured.
2. B50_c_bgl0 environment only.
For the mentioned set-up no longer the message appears and the order line is released to Invoicing
3. A check has been added which will allow the system to adjust the sales price by using the current conversion factor. A new
message called has been created to indicate the user that the sales order line has been linked to a contract and that he must
be aware that the sales price will be adjusted since the current conversion factor has been changed.
4. An over delivered Cross Docking Sales Order has the correct link to the Purchase Order. This can be seen in the Linked
Order Line Data.

Solution: 129098
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Receipt cannot be made for an item that is blocked for purchase in the time interval between the order line creation and
receipts.
SOLUTION DESCRIPTION:
The receipts can be maintained now even if the item is blocked for purchase after the purchase order line entry.

Solution: 129101
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
When printing the packing slip from session "Print Packing Slip" (whinh4475m000), if the "Ship to" language of the business
partner is not English and if a unit description is maintained in the "Ship to" language, then a float exception error occurs and
the report is not printed.
SOLUTION DESCRIPTION:
The report prints data correctly without any errors.

Solution: 129103
SITUATION IDENTIFIED IN:
"Sales Contract Lines" (tdsls3101s000)
SITUATION DESCRIPTION:
The help text corresponding to field 'Price Group' is incorrect. The system doesn't work according to the following two
statements:
- You can leave the Price field empty
- You can leave the Sales Price Unit field empty
SOLUTION DESCRIPTION:
The help text has been adjusted as follows:
- Price and Price Book fields cannot be both empty when the contract is activated
- The Sales Price Unit field needs to be entered
Either the price or the price book cannot be both zero or empty if the contract is activated. Contracts are agreements for a
determined price and/or discount. The sales price unit cannot be empty in case the contract applies for a price group since
this unit will be used for conversion purposes while linking the contract to a sales order line.

Solution: 129111
SITUATION IDENTIFIED IN:
"Items - Service" (tsmdm2100m000)
SITUATION DESCRIPTION:
When entering prices in the Item Service Data of an Item (session "Items - Service (tsmdm2100m000)") the prices are
converted to the Reference Currency and stored in the default Service Price Book as specified in parameters (session
"Pricing Parameters (tdpcg0100m000)"). Unfortunately, the conversion is done using the Purchase Rate (as specified in
session "Companies (tcemm1170m000)") instead of the Sales Rate. Particularly as the Service Price Book is considered a
Sales Price book, this is clearly incorrect. The results of this conversion can be seen in session "Price Book
(tdpcg0131m000)". The problem occurs for default sales price book also.
SOLUTION DESCRIPTION:
Now, the Sales Rate will be used to update the price for the default sales and service price books.

Solution: 129134
SITUATION IDENTIFIED IN:
"Process Inspection Orders" (qmptc1204m000)
SITUATION DESCRIPTION:
While processing an inspection order in QMS Module for Sales origin, the system gives a fatal error "Index out of range".
SOLUTION DESCRIPTION:
The inspection orders can be processed and the order can be closed.

Solution: 129136
SITUATION IDENTIFIED IN:
"Print Specifications delivered but not invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
Report shows a delivered quantity of zero (0) even though there is a delivered quantity
SOLUTION DESCRIPTION:
Report does not show a delivered quantity of zero (0) if there is a delivered quantity

Solution: 129139
SITUATION IDENTIFIED IN:
"Project Surcharges" (tipcs3120s000)
SITUATION DESCRIPTION:
Entry of 'Surcharge Bases' not possible and error " Starting session only possible from 'Project Surcharges!" (tipcs00003) is
displayed, when trying to access "Surcharge Bases" for a surcharge that is not project specific (project field left blank)
and with surcharge method as '% of Selective Costs' in session "Project Surcharges" (tipcs3520m000/tipcs3120s000) .
SOLUTION DESCRIPTION:
Entry of 'Surcharge Bases' is possible and no error message will be displayed, when trying to access "Surcharge Bases" for a
surcharge that is not project specific (project field left blank) and with surcharge method as '% of Selective Costs' in
session "Project Surcharges" (tipcs3520m000/tipcs3120s000).

Solution: 129152
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
It is not possible to add new Detail lines in the sales order, if some other Detail line of the same position has been already
been delivered. The system gives the error message "Delivery date not allowed"
SOLUTION DESCRIPTION:
It is possible to create new detail lines.

Solution: 129154
SITUATION IDENTIFIED IN:
"Delete Projects" (tipcs2270m000)
SITUATION DESCRIPTION:
When error occurs while deleting a project, system gives the message "No data found for report; no report is printed" and
the error message is not displayed.
SOLUTION DESCRIPTION:
The system gives the error message mentioning why the project is not deleted.

Solution: 129155
SITUATION IDENTIFIED IN:
"Transfer Direct Debits" (tfcmg4260s000)
SITUATION DESCRIPTION:
No company name is getting printed in the Direct Debits Bank File (Clieop EUR/NLG)
SOLUTION DESCRIPTION:
Now the company name is getting printed correctly in the Direct Debits Bank File (Clieop EUR/NLG)

Solution: 129158
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Order Lines" (whinh5101s000)
SITUATION DESCRIPTION:
If an adjustment order is created (in session whinh5500 "Cycle-Counting/Adjustment Orders") with two different lines and
the second line:
1) is created in session whinh5501m000 "Cycle-Counting/Adjustment Order Lines" without closing whinh5101s000
"Cycle-Counting/Adjustment Order Lines" session
(by using CTRL N, for instance)
2) same item as first line is used
for an item lot controlled by unit, then field storage unit is not filled with the default value causing that it stays empty AND
disabled, not being possible to change it manually.
SOLUTION DESCRIPTION:
Now fields in session whinh5101s000 fills the field storage unit with its default value.

Solution: 129174
SITUATION IDENTIFIED IN:
"Copy Table Data Authorizations to Childs" (ttams3247s000)
SITUATION DESCRIPTION:
When two conditions are copied to child tables, they are combined into one with an increasing serial number.
SOLUTION DESCRIPTION:
Condition and serial numbers are copied without changes to child table authorizations.

Solution: 129179
SITUATION IDENTIFIED IN:
"Correct Inventory Ledger accounts" (wh0201m000)
SITUATION DESCRIPTION:
The correction program with the session "Correct Inventory Ledger accounts" (whcor0201m000) is present to correct the
erroneous records related to the following problem:
- Inventory Valuation Method of the Item is Fixed Transfer Price (FTP)
- The item is issued to the Shop Floor for the Production Order.
- Then the 'Cost Price' of the item is changed.
- Now, when the goods are returned from the Shop Floor to the Warehouse, the 'Warehousing (valuation) - Revaluation'
posting is done with wrong sign.
Due to this, the value of the Inventory account was going wrong.
This correction program can be used to correct the Warehousing (valuation)/(Revaluation postings done wrongly, due to the
Return Issue posting of the following Order origins.
- Production
- Service
- Sales
If the Transaction were not yet posted in Finance module, the sign of the Transaction amount would be reversed. Otherwise,
if the posting has been done, a new Transaction would be created with an amount equal to two times the original entry and
with opposite sign. When this new Transaction is posted, it would yield the same effect as reversing the sign of the original
posting.
The user wants to run the correction program for the wrong records created in a time span and the session should have the
provision to enter the time range.
SOLUTION DESCRIPTION:
The correction program is provided with the option to select the Transaction Time range and thus only the records in the
given time frame can be corrected.

Solution: 129180
SITUATION IDENTIFIED IN:
"Message code " (ticsts02011)
SITUATION DESCRIPTION:
In the message code ("ticsts02011") description, "Order has been processed succesfully", the word 'succesfully' had been
incorrectly spelled.
SOLUTION DESCRIPTION:
The message code ("ticsts02011") description is correctly displayed as , "Order has been processed successfully".

Solution: 129197
SITUATION IDENTIFIED IN:
"Transfer Order" (cppat1210m000)
SITUATION DESCRIPTION:
While transferring planned orders, if the user cancels the report, the system only cancels the printing of the report instead of
stopping the transfer.
SOLUTION DESCRIPTION:
When the user cancels the printing, the system will stop transferring the order.

Solution: 129213
SITUATION IDENTIFIED IN:
"Lots by warehouse" (whltc1505m000).
SITUATION DESCRIPTION:
Performance problem due to huge number of empty records in the table whltc105 ( Lots by Warehouse )
SOLUTION DESCRIPTION:
A correction program whcor1405m000 is created to delete empty records and also a solution is created in the standard program
itself to delete empty records while updating the table .

Solution: 129216
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
Session reconciles the document that has not been selected for Automatic Reconciliation.
SOLUTION DESCRIPTION:
Session won't reconcile the document that has not been selected for Automatic Reconciliation and only the documents that
are selected for Automatic Reconciliation will be reconciled now.

Solution: 129223
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When confirming receipt in session "Receipts" (whinh3520m000) for a zero quantity order with inventory valuation method as
"Lot Price" and if the order amount is different from the lot amount then the error message 'Price in CPR does not match lot
price' pops up and it is not possible to confirm the receipt.
SOLUTION DESCRIPTION:
No error message comes up when confirming a receipt of zero quantity.

Solution: 129228
SITUATION IDENTIFIED IN:
"spool open" (ttstpsplopen)
SITUATION DESCRIPTION:
When (after printing ones from a session with a left margin set >0 and save defaults done) printing again then the left
margin will increase when you tab through the fields
SOLUTION DESCRIPTION:
Left margin will no longer increase when tabbing through the fields.

Solution: 129240
SITUATION IDENTIFIED IN:
"Cycle-Counting/Adjustment Order Lines" (whinh5101s000)
SITUATION DESCRIPTION:
When creating an adjustment order for an item not location controlled and not lot controlled, quantity present at the stock
point is not found, giving the following message "Order Line can not be processed. On hand on stock point has been
changed." at the time of processing the line.
SOLUTION DESCRIPTION:
The quantity present at the stock point is filled properly, so no changes on stock point happen, therefore the order line can
be processed.

Solution: 129246
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
When correcting a Purchase Invoice for the amount in sesison "tfacp2110s000 - Maintain Purchase Invoice Corrections" and
the session is closed and saved by the x-button. The amounts in home currecny are changed on the screen but the table is
not updated.
SOLUTION DESCRIPTION:
The amounts are updated correctly now

Solution: 129247
SITUATION IDENTIFIED IN:
"Help Viewer" (ttstphelp)
SITUATION DESCRIPTION:
Help text shows '|' symbol from comments (marked with characters "|#") in the help text.
SOLUTION DESCRIPTION:
Help text in Baan is saved in buffers of a certain size. The problem occurs when the last characters of such a buffer is the
End-of-line character, followed by the first character of a comment line: "\n|". When the first character of the next
text-buffer is the "#" character, this help text line is a comment line. The line that will be displayed in the help text now
already contains the "|" character.
The line to be displayed in the help text will be reset to an empty line when the situation described above occurs.

Solution: 129266
SITUATION IDENTIFIED IN:
"Select Values for GRNI Reconciliation" (tfacp1235m000)
SITUATION DESCRIPTION:
While selecting GRNI inter-company integration transactions using session "Select Values for GRNI Reconciliation"
(tfacp1235m000), the error message "Integration Transactions (tfgld418) not found" comes for these integration transactions
and they appear in the error report.
SOLUTION DESCRIPTION:
The inter-company integration transactions are selected without any error
messages.

Solution: 129272
SITUATION IDENTIFIED IN:
"Print Cost Control" (tpppc4411m000)
SITUATION DESCRIPTION:
In Print cost control session, if the currency rate is "0", then the actual cost that is printed in terms of reference currency is
not correct.
SOLUTION DESCRIPTION:
The above problem is solved and now, even if the currency rate is "0", correct actual costs in terms of reference will be
printed.

Solution: 129274
SITUATION IDENTIFIED IN:
"Select Device" (ttstpsplopen)
SITUATION DESCRIPTION:
After installing solution 128964 tools reports are not printed correctly.
SOLUTION DESCRIPTION:
In solution 128964 the search for report defaults was optimized but tools reports where not handled correctly.
This is now corrected.

Solution: 129276
SITUATION IDENTIFIED IN:
"Generate Order Advice" (whina3200m000)
SITUATION DESCRIPTION:
When a Transfer (manual) order is created using session "Generate Order Advice" (whina3200m000), the field "Route" does
not get defaulted in the newly generated warehousing order.
SOLUTION DESCRIPTION:
The value of field "Route" is defaulted in the warehousing order.

Solution: 129278
SITUATION IDENTIFIED IN:
"Export Financial Statement Account Structure" (tffst1220m000)
SITUATION DESCRIPTION:
The description of the sub-level more than zero (i.e., parent) Statement Account is not stored fully (i.e., 35 characters). Only
30 characters are stored in the table tffst310 (Financial Statement Account Structure).
SOLUTION DESCRIPTION:
Earlier, only 30 characters of the description of the parent Statement Account (of sub-level greater than zero) are stored.
Now, 35 characters of the description of the parent Statement Account (of sub-level greater than zero) are stored.

Solution: 129279
SITUATION IDENTIFIED IN:
"Print Activities" (tipcs4401m000)
SITUATION DESCRIPTION:
In the session "Print Activities" (tipcs4401m000), the default value of "to" field of Project Manager (pemp.t) is 999999,
which is wrong. This should be ZZZZZZ. According to Baan standards the default value of "to" fields of Project manager
(pemp.t) should be ZZZZZZ.
SOLUTION DESCRIPTION:
The default of " to" field of 'Project manager' is made as "ZZZZZZ".

Solution: 129281
SITUATION IDENTIFIED IN:
"Print Where-Used Lots" (whltc3400m000)
SITUATION DESCRIPTION:
When tracking the lot usage for a particular lot with session whltc3400m000 "Print Where-Used Lots" it is necessary to know
the order origin of this lot. As the order origin is not always known it has to be determined first by printing the lot origin
first (via session whltc3401m000 "Print Origin by Lot"). This is however not preferable.
SOLUTION DESCRIPTION:
The functionality of the session whltc3400m000 "Print Where-Used Lots" has been
extended so that now it is possible to track the lot usage without
necessarily knowing the order origin. Due this functional change now an order origin range has to be defined on the form.

Solution: 129283
SITUATION IDENTIFIED IN:
"Handle Cache memory" (tccomdll0201)
SITUATION DESCRIPTION:
There are 2 possible fatal errors due to the usage of table-boosters:
- Fatal error bis_alloc_mem (many idb.init call's)
- index 48139 out of dims [1] 48138 in otccomdll0201 (many idb.change.order call's)
SOLUTION DESCRIPTION:
Both errors are prevented now by taking appropriate actions in the table-booster coding.

Solution: 129284
SITUATION IDENTIFIED IN:
"Payment details" (tfacp2524s000)
SITUATION DESCRIPTION:
When in session "Payment details" (tfacp2524s000), on clicking option "Check Doc. Data" the error message "Fatal Error
506" appears and the session doesn't open.
SOLUTION DESCRIPTION:
No error messages appear on choosing the option "Check Doc. Data" and the session opens properly.

Solution: 129286
SITUATION IDENTIFIED IN:
"Receipt Correction" (whinh3121s000)
SITUATION DESCRIPTION:
Corrupt inventory after receipt correction, especially when changing from original receipt unit to another unit.
SOLUTION DESCRIPTION:
New structure for receipt corrections prevents data corruption.
Changing the receipt unit while correcting the quantity is only possible when total stock is still available.

Solution: 129293
SITUATION IDENTIFIED IN:
"Create GRNI Correction Batch" (tfacp1240m000), "Global Acceptance of GRNI Reconciliation" (tfacp1237m000)
SITUATION DESCRIPTION:
1. When using real time transaction type for a correction batch in session "Create GRNI Correction Batch" (tfacp1240m000),
the correction transactions were not getting finalized as the background process was not yet invoked.
2. In GRNI, for an order if part of the transactions are already accepted, then when the session "Global Acceptance of GRNI
Reconciliation" (tfacp1237m000) is run with the option "Only Orders with Debit and Credit Balanced" these transactions are
accepted again, and hence the acceptance description previously entered gets overwritten.
SOLUTION DESCRIPTION:
1. The background process is invoked automatically now; hence the transactions can be finalized.
2. Only the non-accepted transactions are accepted and printed when the "Global Acceptance of GRNI Reconciliation"
(tfacp1237m000) is run with the option "Only Orders with Debit and Credit Balanced".

Solution: 129296
SITUATION IDENTIFIED IN:
"Release to warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
Create a sales order where the Shipping Constrain is set to "Order Complete"
Create two order lines
Process the order lines until the status within Warehousing is "Staged"
Now add a new line to this sales order.
In this situation it is not possible to release the newly created line to warehousing. The message "Set Could not be released
completely" appears.
It is possible to ship the two lines within warehousing. This is not correct because there is still another order line present
that should be part of the shipment because of the shipping constraint "Order Complete"
After the two lines are shipped it still is not possible to release the new line to warehousing.
SOLUTION DESCRIPTION:
For shipping constraint "Order Complete" a check is done when confirming the shipment to see if there still are lines within
sales that are not yet released to warehousing.
If there are still lines present within sales the order lines within warehousing are not shipped.
New order lines can be released to warehousing even if there are other lines for the same order that are already released to
warehousing.

Solution: 129300
SITUATION IDENTIFIED IN:
"Matched Purchase Invoice Transactions" (tfacp1133s000)
SITUATION DESCRIPTION:
When on the second form of session "tfacp1133s000 - Matched Purchase Invoice Transactions" the reporting period is changed
this is not updated. When you get into the session again you can see the old value is displayed again.
SOLUTION DESCRIPTION:
The transaction is updated with the changed value now

Solution: 129305
SITUATION IDENTIFIED IN:
"Generate FTP-script" (ttpmc2211m000)
SITUATION DESCRIPTION:
The FTP-server of Baan for downloading solutions (ftp.support.baan.com) used to be a non-secure server. Anonymous
logins were allowed.
Baan changed the server to a secure server. No anonymous logins are allowed anymore. For the Multilevel Download Tool the
userid and password are stored in $BSE/lib/ftpbaan. Because the password needs to be protected it should not be stored in
$BSE/lib/ftpbaan.
SOLUTION DESCRIPTION:
The userid and password need not to be entered anymore in the session "Generate FTP-Script" (ttpmc2210m000/ttpmc2210s000).
You still can do it, then the situation remains the same as it is and the userid and password are stored in $BSE/lib/ftpbaan.
When the userid and password are not stored in $BSE/lib/ftpbaan you will be asked for it just before the session
"Download, Scan and Connect Solution" (ttpmc2210m000/ttpmc2210s000) will download a solution.
Entered passwords will not be displayed.

Solution: 129317
SITUATION IDENTIFIED IN:
"Transfer Plan/Order" (cppat1210m000)
SITUATION DESCRIPTION:
Sorting of planned purchase orders does ignores the startdate of planned purchase order. Effective sorting is on BP, Item
and ordernumber.
SOLUTION DESCRIPTION:
Startdate of planned purchase order is included in sorting. The effective sorting is on BP, Item, startdate and ordernumber

Solution: 129325
SITUATION IDENTIFIED IN:
"Copy Received Purchase Invoices" (tfacp1210s000)
SITUATION DESCRIPTION:
After solution 119986, when the session "Copy Received Purchase Invoices" (tfacp1210s000) is started the order of the data
displayed is using index 2 (supplier, document). It is now not possible to customize the default order of the index during
startup of the session as the changes are in the script.
SOLUTION DESCRIPTION:
It is now possible to customize the session, so that the starting "sort by" of session can be changed.

Solution: 129328
SITUATION IDENTIFIED IN:
"Actualize Cost and Valuation Prices" (ticpr2220m000)
SITUATION DESCRIPTION:
Actualize cost price failed but no report is printed with the reason why.
SOLUTION DESCRIPTION:
In some cases actualizing the cost price failed due to a timing problem caused by sol 127795. Besides, an error report was
missing so problems were never showed to the user, giving a lot of confusion. Now both the timing problem and the report
handling have been solved.

Solution: 129335
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
The Name of the Business Partner is not displayed in the session and only the Business Partner title is displayed.
SOLUTION DESCRIPTION:
Now, the name of the Business Partner is correctly displayed.

Solution: 129340
SITUATION IDENTIFIED IN:
"Commitments(material)" (tpppc2110s000)
SITUATION DESCRIPTION:
Soft Commitments generated in Project for cost items always gets quantity 0 and unit has an empty value when inventory
unit of that item is empty.
SOLUTION DESCRIPTION:
Now purchase unit would be used instead of inventory unit if inventory unit is blank in item data. So now correct quantity
and unit would be displayed.

Solution: 129352
SITUATION IDENTIFIED IN:
"Release to Invoicing (batch)" (tdsls4247m000)
SITUATION DESCRIPTION:
When releasing an orderline without quantity to invoicing, error "cannot determine COGS" appears.
SOLUTION DESCRIPTION:
System was trying to read the cost of goods sold for such a line. But, because the sales order line with qunatity zero is not
known in Warehousing, the error appears.
Now a sales order line without quantity can be released to invoicing without errors.

Solution: 129359
SITUATION IDENTIFIED IN:
"Write off Currency Differences" (tfacp2240m000)
SITUATION DESCRIPTION:
After running session "Write off Currency Differences" (tfacp2240m000) for Unallocated Payments, the new rate and the new
balance in home currency is not updated for the Unallocated Payments, even though the currency difference transaction is
created correctly.
SOLUTION DESCRIPTION:
The rates and new balance in home currency is updated correctly for the Unallocated Payment document.

Solution: 129362
SITUATION IDENTIFIED IN:
"Planned PRP Purchase Orders" (tppss6810m000)
SITUATION DESCRIPTION:
Purchase office field blanks out the moment we save or we go to the next tab in the Planned PRP Purchase Order (Equipment
and Subcontracting). The same works properly in Material Order. Then, after transferring the order to "Order Management", it
picks up the purchase office from user profiles. So the user is unable to specify desired purchase office.
SOLUTION DESCRIPTION:
Every time we change the Purchase office, the system tries to find contract linked to that purchase office and if contract is
not found, the Purchase office field is reset. So, it was getting blanked out. Now, the Purchase office field will not be reset.
So the user can mention desired purchase office.

Solution: 129367
SITUATION IDENTIFIED IN:
"Maintain revenues for final results" (tpppc3106s000)
SITUATION DESCRIPTION:
Activity not defaulted as per the element - activity relations.
SOLUTION DESCRIPTION:
Now activity is defaulted as per relation maintained for element and activity.

Solution: 129371
SITUATION IDENTIFIED IN:
"Inspections by Warehousing Order" (whinh3522m200)
SITUATION DESCRIPTION:
In session "Inspections by Warehousing Order" (whinh3522m200) it is not possible to search on fields
Origin/Order/Set/Position Number. It is only possible to search on fields Sequence Number/Advice Number/Approval
Sequence Number.
SOLUTION DESCRIPTION:
It is now possible to search on all mentioned fields: Origin/Order/Set/Position Number/Sequence Number/Advice
Number/Approval Sequence Number

Solution: 129374
SITUATION IDENTIFIED IN:
"Match Purchase Order Lines" (tfacp2541m000)
SITUATION DESCRIPTION:
In session "Match Purchase Order Lines" (tfacp2541m000), the option "Match All" is chosen. Now if there are many items
still not received in the warehouse then the error message "Received quantity 0 of order minus quantity already matched 0 is
less than or equal to zero" appears, as many times as there are non-received orders in the warehouse.
SOLUTION DESCRIPTION:
When the option "Match All" is chosen, the message comes up
once. And then a question is asked, whether the user wants to continue
running the session. If the option "Yes" is chosen then no more messages pops up, but further orders are processed.

Solution: 129378
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
Consignment replenishment sales orders are not processed automatically when returning goods (using a negative quantity)
from consignment (owned) warehouse to main warehouse, even when process direct is set to true.
SOLUTION DESCRIPTION:
Processing is done automatically if process direct is set to true (for this situation, a receipt needs to be created manually
only when process direct is set to False and Receipt is an activity included in the warehouse procedure).

Solution: 129383
SITUATION IDENTIFIED IN:
"Generate Purchase Order Advice for Sales Order" (tdsls4240m000)
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
It is not possible to create a Purchase Order Advice for a Direct Delivery Sales Order although the parameter "Refuse
Blocked Direct Deliveries" is set to no. The option "Generate Purchase Order Advice for Sales Order" in session "Sales
Order Lines" (tdsls4501m000) is disabled for all blocked orders. Session "Generate Purchase Order Advice for Sales Order"
(tdsls4240m000) cannot be run for blocked orders.
SOLUTION DESCRIPTION:
For Direct Delivery Sales Order Lines that are blocked, a Purchase Order Advice can be generated (session tdsls4240m000). Also the option in the
Specific menu of "Sales Order Lines" (tdsls4501m000) is enabled. During the Transfer of the Purchase Order Advice the parameter "Refuse Blocked
Direct Deliveries" is checked. If 'yes', no Purchase Order is generated. If 'no' a Purchase Order is generated.
For cross docking orders that are blocked no Purchase Order Advice can be generated.

Solution: 129393
SITUATION IDENTIFIED IN:
"Release to Warehousing" (tdsls4501m140)
SITUATION DESCRIPTION:
After installing solution 128621 the message "tdslss401.4 ???????????????????????????????" comes up.
SOLUTION DESCRIPTION:
The message was not added properly to the solution. The needed message is available after installing this solution

Solution: 129394
SITUATION IDENTIFIED IN:
"Print Warehousing Order History" (whinh2450m000)
SITUATION DESCRIPTION:
1) When option "Order lines" alone is chosen, the transaction date is printed incorrectly in the line records.
2) When Order set range is given, the details of the first Order set is not printed.
SOLUTION DESCRIPTION:
1) Now, the Transaction date is printed correctly when the option "Order lines" alone is chosen.
2) The information about all the Order sets are printed including the first Order set when a range of Order sets are specified.

Solution: 129397
SITUATION IDENTIFIED IN:
"Planned PRP Warehouse Order" (tppss6115s000)
SITUATION DESCRIPTION:
After saving a planned WH order it is possible that some messages are displayed, but these messages are displayed 3 times.
This is the case if TEST_RETRY=2.
SOLUTION DESCRIPTION:
Test if db.retry.hit is applicable. If so, then reset error messages.

Solution: 129399
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
After automatic reconciliation via session "Selection for Automatic Reconciliation" (tfcmg2123s000), the reconciliation
batch cannot be finalized when both a purchase invoice and a standing order for advance payment with VAT are included
within this batch. An error report has been created about wrong balances on the VAT account.
SOLUTION DESCRIPTION:
The reconciliation batch with both a purchase invoice and a standing order for advance payments with VAT can be finalized
successfully.

Solution: 129401
SITUATION IDENTIFIED IN:
"Business Functions" (tgbrg2100s000)
SITUATION DESCRIPTION:
When we enter a new Business Function in this session and typed a description in, this description is disappeared when we
switch to the second form and come back to the first form.
SOLUTION DESCRIPTION:
The description was not saved in the right way.
We changed this and now the description stays even after switching between the two forms.

Solution: 129402
SITUATION IDENTIFIED IN:
"Print Receivable Invoices up to Period" (tfacp1439m000)
SITUATION DESCRIPTION:
A new report required in session "Print Receivable Invoices up to Period" (tfacp1439m000), to print the totals per logistic
company.
SOLUTION DESCRIPTION:
A new report has been added which prints the totals per logistic company.

Solution: 129403
SITUATION IDENTIFIED IN:
"Sales Invoice Transactions" (tfacr1111s000)
SITUATION DESCRIPTION:
If VAT amount is changed in the transaction line level, batch is not in balance; Maintain Interim Tax table (tfgld107) is
not updated with the new changed amount
SOLUTION DESCRIPTION:
If VAT amount is changed in the transaction line level, Maintain Interim Tax table (tfgld107) is updated with the new
changed amount.

Solution: 129407
SITUATION IDENTIFIED IN:
"Maintain Query Data" (ttadv3180m000)
SITUATION DESCRIPTION:
When executing a query, created in EasySQL, containing in the where-clause the function date() that is followed by a
condition with string field,
the following error messages are given :
"Illegal date format (Y:1, M:2002, D:08)"
"Syntax error: ',' not expected"
"Found 2 errors during scanning/parsing .. Stopped."
"Error 302 (SQL syntax not correct) on SELECT"
"Can not continue in ottadv3180parse ()"
When, instead of function date(), the function date.to.num() is used, the query is executed without the error 302.
Example of a query that gives the mentioned problem:
select tdpur045.orno
from tdpur045
where tdpur045.date >= date(2002,08,01)
and tdpur045.date <= date(2002,08,31)
and tdpur045.item = "LOHNARBEIT"
SOLUTION DESCRIPTION:
The function date() was seen as an array, causing an incorrect modification in the parameters of function date().
There already was a check for function date.to.num(), and this check has been extended to check for function date() as well.
Now function date() is not seen as an array anymore.

Solution: 129410
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
When running the session "Process Delivered Purchase Orders" (tdpur4223m000), some times a message appears as
++++++++++++++++++++++++++++++++
tdsls00044 ???????????????????????????
++++++++++++++++++++++++++++++++
SOLUTION DESCRIPTION:
Now the message will pop up as
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Sales order line XXXXXXXXX/10/0 not found or invoice to BP-sales office combination not found for this order line
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Solution: 129412
SITUATION IDENTIFIED IN:
"Warehouse Tools Transfer" (titrp0108m000)
SITUATION DESCRIPTION:
It is not possible to transfer tools within session "Warehouse Tools Transfer" (titrp0108m000) in case the parameter
"Over Delivery" in session "Inventory Handling Parameters" (whinh0100s000) is set lower than 100%.
The message " Advised quantity in Inventory Unit cannot be greater than Ordered quantity in Inventory Unit + Rejected
Quantity in inventory UNIT" occurs.
SOLUTION DESCRIPTION:
Changes made so the functionality of Parameter "Over Delivery" is handled correctly.

Solution: 129419
SITUATION IDENTIFIED IN:
"Close Service Orders and Post to History" (tssoc2201m000)
SITUATION DESCRIPTION:
A) When the Purchase Order Line generated from Service order is split, the service order can not closed by running the
session. The system gives the error report
+++++++++++++++++++++++++++
Active Purchase Orders are present
+++++++++++++++++++++++++++
B) When the planned purchase order is transferred as purchase order, the order quantity is not converted in to the Purchase
Unit of the item. But, it is creating in the inventory unit.
SOLUTION DESCRIPTION:
A) It is possible to close the production order, which has split purchase order lines attached to that.
B) The order quantity is converted to the purchase unit of the item and it is no longer in the inventory unit.

Solution: 129420
SITUATION IDENTIFIED IN:
"Print Subsequent Material Deliveries" (tisfc0404m000)
SITUATION DESCRIPTION:
Item descriptions are printed as asterisks (descriptions are printed as ***********) in the report, instead of the Item
description defined in "General Item data" (tcibd0501m000). This happens if there is no production data present for the
Item.
SOLUTION DESCRIPTION:
The Item descriptions are printed correctly as defined in the "General Item data" (tcibd0501m000).

Solution: 129422
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
In case the order line Ordered Quantity contains a decimal zooming to the details causes an incorrect value of the original
quantity and the current quantity.
Total order quantity = 0,9 ---> Original Quantity on the detail overview shows 0
Total order quantity = 2,9 ---> Original Quantity on the detail overview shows 2
The values on the total and the detail overview should be the same
SOLUTION DESCRIPTION:
Now the Original Quantity and the Actual Quantity are correctly filled when zooming from the Order Line (Overview) to
the Order Line Detail Overview

Solution: 129424
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Message tdsls4102b.1 is not translated for the German Language.
The message shows "Order line linked to contract ... Note: Item conversion factor has changed. Price will be adjusted."
SOLUTION DESCRIPTION:
The message is translated :
"Auftragsposition ist mit Vertrag .... verknüpft. Hinweis: Umrechnungsfaktor wurde geändert. Preis wird angepaßt."

Solution: 129446
SITUATION IDENTIFIED IN:
"Integration Transactions by Project / Order" (tfgld4510m000)
SITUATION DESCRIPTION:
Postings in finance were done with wrong 'Transaction origin' and 'Financial transaction', when more than the issued
quantity is returned to warehouse for a production order and meanwhile FTP has changed.
SOLUTION DESCRIPTION:
Now the postings are done with correct 'Transaction origin' and 'Financial transaction' for the extra returned quantity.

Solution: 129447
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" (whinh4201m000)
SITUATION DESCRIPTION:
This situation only applies in case a package definition is involved and the requested unit is not "binding".
Different outbound advices are generated for corresponding quantities/units of the same item.
In case a package definition is involved and the requested unit is not "binding", the outbound advice should be similar for
corresponding quantities.
Example:
Item "A" has inventory unit "pcs" and package definition "B".
Levels of package definition "B":
Level 1 pcs
Level 2 box = 10 pcs
Level 3 pal = 10 box = 100 pcs
Generating an outbound advice for 10 "box" and generating an advice for 1 "pal" does not always give the same result, even
though the quantities are corresponding (100 "pcs").
The outbound advice for 10 "box" sometimes advises picking from different stock points, while the outbound advice for 1
"pal" would advise to pick 1 "pal".
The outbound advice for 10 "box" should also advise to pick 1 "pal".
SOLUTION DESCRIPTION:
In case a package definition is involved and the requested unit is not "binding", the same logic is used for every requested
unit. This results in identical outbound advices.

Solution: 129453
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
When a service order which has a 'To Warehouse'/ 'To Warehouse by Transport' line with invoicing cost amount as zero is
costed,it creates a financial transaction of type 'Approved for Invoicing' with transaction origin 'Service' in "Integration
Transactions by Project/Order"(tfgld4510m000) session.When the invoicing amount is zero,there should not be any 'Approved
for Invoicing' transaction.
SOLUTION DESCRIPTION:
When the invoicing cost amount is zero on a 'To Warehouse'/ 'To Warehouse by Transport' line,no 'Approved for Invoicing'
financial transaction is created when the service order or the cost line is costed.

Solution: 129460
SITUATION IDENTIFIED IN:
"Correct COGS Integrations" (cicor0111m000)
SITUATION DESCRIPTION:
If the correction program is run from a different company other than the logistic company in which the sales order was
raised, then the correction program did not pick up the order.
SOLUTION DESCRIPTION:
Now the program works correctly in a multi-site environment

Solution: 129461
SITUATION IDENTIFIED IN:
"Report Orders Completed Globally" (tisfc0206m000)
SITUATION DESCRIPTION:
Antedating functionality is not correct while using the session "Report Orders Completed Globally". The session has a user
input field, 'Completion Date'. As per the functionality, this user input date field should be used as the completion date.
But the functionality is not working this way; instead the completion data is always current date.
SOLUTION DESCRIPTION:
The antedating functionality is working correctly for the session. The user input completion date is the completion date of
the production order.

Solution: 129465
SITUATION IDENTIFIED IN:
"Print Approvals" (whinh3422m000)
SITUATION DESCRIPTION:
When a sales order is released to warehouse ,outbound advice is released and tried to print the approval from session
Print Approvals (whinh3422m000) system prompts a message box with "No data within selection".
SOLUTION DESCRIPTION:
System prints the Approvals records even for the outbound order lines

Solution: 129468
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the user tries to terminate the composing process by clicking 'Stop' button, he gets a fatal error "Error 506 (Table does
not exist).
SOLUTION DESCRIPTION:
Now the fatal error does not occur. The process gets terminated correctly.

Solution: 129472
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
If the warehouse field is filled for the ship-to BP (tccom4111s000) the defaulting of the Warehouse on the order lines is
incorrect for Consignment Invoicing orders. It defaults with the warehouse set in the Ship-To BP data and not with the
Consignment Owned Warehouse
SOLUTION DESCRIPTION:
The process of determining the default warehouse is adjusted. In case of Consignment Invoicing always the Consignment
Owned warehouse is selected.

Solution: 129479
SITUATION IDENTIFIED IN:
"Engineering BOM" (tiedm1510m000)
SITUATION DESCRIPTION:
Signal codes linked to engineering items / standard items do not function, while selecting the engineering item / standard
item as a component in an Engineering BOM.
SOLUTION DESCRIPTION:
Signal codes linked to engineering items / standard items signal correctly, while selecting the engineering item / standard
item as a component in an Engineering BOM.

Solution: 129484
SITUATION IDENTIFIED IN:
"Initiate Inventory Issue" (tisfc0207m000)
SITUATION DESCRIPTION:
The session "Initiate Inventory issue" has a field 'Issue Date'. This date field is an input field. The date can be an earlier
date (Antedate) also. This date should be used, as the issue date for the components, while initiating inventory and all
planned stock transactions of the component should be updated with this date. But the planned inventory transaction always
shows the current date.
SOLUTION DESCRIPTION:
The planned stock transactions are updated with the issue date input by the user in the session "Initiate Inventory Issue"
(tisfc0207m000).

Solution: 129497
SITUATION IDENTIFIED IN:
"Print goods received note" (whinh3412m000)
SITUATION DESCRIPTION:
The problem occurs when there are more than one operation linked to the routing and the first operation is not the
subcontracting operation. For example, if the second operation is a subcontracted operation and there is a Purchase order
generated for this subcontracted operation and the purchase order is processed. Now if user tries to 'Print goods received
note' (whinh3412m000) for the Purchase order, then the report does not print the subcontracting details of the order.
SOLUTION DESCRIPTION:
The subcontracting details of the production orders are printed in the report, when 'Print goods received note'
(whinh3412m000) for the Purchase order are printed.

Solution: 129501
SITUATION IDENTIFIED IN:
"tisfc0220m000" (Backflush Materials and Hours)
SITUATION DESCRIPTION:
A component in the bom with a zero quantity is allowed. This facilitates the user to decide the quantity at the order level.
When a production order is raised for the main item, the component comes in the estimated materials with zero quantity and
is flagged for backflushing. When backflushing this item, the system gives the error message "Backflushing not possible for
this new Material line, because Estimated and Net Quantity = 0". This stops the system from backflushing the components
that do have a quantity.
SOLUTION DESCRIPTION:
Consider a production order has a set of components, among which one component has a zero quantity and backflushing as 'yes'.
When backflushing is done for this order, system performs backflushing for all components that have a net quantity other
than zero and skips the component that has a zero net quantity.

Solution: 129503
SITUATION IDENTIFIED IN:
"Application Function Server" (AFS Integration)
SITUATION DESCRIPTION:
When using Application Function Server for entering projects in Baan, the AFS can call the program logic of session
"Project Status" (tppdm6107m000).
However, that program uses a dll which in it's turn causes an Error 206 (Record is not locked) .
SOLUTION DESCRIPTION:
Record locking has been changed. AFS can now use program logic from session "Project Status" (tppdm6107m000).

Solution: 129507
SITUATION IDENTIFIED IN:
"Booked Price Variance Analysis" (tfacp1460m001)
SITUATION DESCRIPTION:
When starting the session "Booked Price Variance Analysis" (tfacp1460m001) in German language (3), the error message
unknown form field "prnv" comes up.
SOLUTION DESCRIPTION:
The form in languages 1 and 3 has been corrected.
A new option has been provided on the form to print only the variances above the entered value on the form. This option
works only with summary report.

Solution: 129518
SITUATION IDENTIFIED IN:
"Sales Order Lines Overview" (tdsls4510m000)
SITUATION DESCRIPTION:
Cannot start session "Print Sales Order Lines" (tdsls4409m000) from the Shipping tab within session "Sales Order Line
Overview (tdsls4510m000)
SOLUTION DESCRIPTION:
The option to start session "Print Sales Order Lines" is made available on the Shipping tab.

Solution: 129519
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
When an invoice (for part amount) was already in 'audited' status and is selected again in the same or another batch
for 'maintaining posting data', message 'Document already selected in company , batch '
was shown (For example, for company 550, Batch 100, Message was 'Document already selected in company 550, batch
100'), which was confusing.
SOLUTION DESCRIPTION:
Now, message is changed as 'Document was already selected in batch . Post batch to finance, remove posted data and
try again.' For the above example, if invoice ACR 19980172 is selected again, the message would be - 'Document ACR 19980172 was already
selected in batch 100. Post batch 100 to finance, remove posted data and try again.'

Solution: 129520
SITUATION IDENTIFIED IN:
"Change password" (ttstppwdaging)
SITUATION DESCRIPTION:
The retry mechanism for the password change was not working for an AS400 environment. You had only one try to change
the password.
SOLUTION DESCRIPTION:
With this solution the retry mechanism is corrected and you have now up to 3 tries to change the password.

Solution: 129527
SITUATION IDENTIFIED IN:
"Display History Job" (ttaad5511m000)
SITUATION DESCRIPTION:
Sequence numbers in "Display History Job" (ttaad5511m000) do not correspond with sequence numbers in "Display
Session by Job" (ttaad5501m000).
SOLUTION DESCRIPTION:
In the session "Display History Job" (ttaad5511m000) not the Sequence number was displayed but the Session number.
Now the label is changed, so the user knows it is the session number and not the sequence number.

Solution: 129530
SITUATION IDENTIFIED IN:
"Maintain Currency Rates" (tcmcs0108m000)
SITUATION DESCRIPTION:
It was possible that a currency rate was entered on the form with more than 6 decimals. Example, an End User could enter
"1,23456789012" on the form as the currency rates. When tabulating over this field, the newly entered rate was shown as
"1,234568". This was due to the fact that this formfield was displayed according its format; 6 digits. However on Database
level still the "1,23456789012" was stored. When calculating with large amounts, these 7th-11th decimals could lead to
differences in Finance, which is incorrect.
SOLUTION DESCRIPTION:
It is still possible that a currency rate on the form is entered with more than 6 decimals, but only the first rounded 6
decimals will be stored in the Database. If the 7th-11th digit are still important, the field "Rate Factor" should be used. In
this way, the currency rate "1,23456789012" will be stored as "123456,789012" with rate factor "100000".

Solution: 129532
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When creating a Purchase Order Line, the VAT Country was determined incorrect in this case;
When both Goods and Invoice are flowing from one EU country to another (f.i. from the Netherlands to Germany) this
situation can be characterized as an ICT; Intra Community Transaction. In this ICT situation, the country where the
Ship-From Business Partner is located, is leading for VAT determination. It was based, however, on the Ship-To country.
This was incorrect.
SOLUTION DESCRIPTION:
In an ICT Situation, where both Goods and Invoice flow from one EU country to another (f.i. from the Netherlands to
Germany) the default VAT country will be the country of the Ship-From Business Partner.

Solution: 129533
SITUATION IDENTIFIED IN:
"Remove Fully Paid Purchase Invoices" (tfacp2250m000)
SITUATION DESCRIPTION:
When running session "Remove Fully Paid Purchase Invoices" (tfacp2250m000) it doesn't archive the data from table "One
time supplier address" (tfacp202).
SOLUTION DESCRIPTION:
The data from table "One time supplier address" (tfacp202) is archived in the history company, but the data is not deleted
as many other modules make use of the information from this table.

Solution: 129535
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When user terminates the Composing process in the middle of it's run, the status of the Billing Request remains as "Posted"
even though only one of the order line has been posted.
The user will not be able to use that Billing Request again.
SOLUTION DESCRIPTION:
Now the process is terminated immediately and the status of the Billing Request remains as "Composed" only. So the user
can process the remaining order lines easily.

Solution: 129541
SITUATION IDENTIFIED IN:
"Buy from Business partners" (tccom4120s000)
SITUATION DESCRIPTION:
In "Buy-from Business Partners" (tccom4120s000) in 'Pricing' tab for the field "Fixed Rate Method" the enumerated field
displays only 'Delivery date'. But in the help text the help for 'Delivery date' explains that the rate method is applicable for
sales order and sales invoices and 'Receipt date' is applicable for Purchase orders and invoices, this confuse the user as he
has to select here in 'Buy- from Business partners' the method as 'Receipt date' but the enumerated fields has only 'Delivery
date'. Hence user is not sure whether selecting the 'Delivery date' as listed is correct or not.
SOLUTION DESCRIPTION:
The 'Fixed rate method' field should be selected here as "Delivery date" only. But in this session/ field, the delivery date
means the date on which goods are received. But to have consistency across all the modules the field is listed as 'Delivery
date'. The help text is now appropriately changed and the user can understand the usage of field 'Delivery date' here.

Solution: 129542
SITUATION IDENTIFIED IN:
"Document Revisions" (dmdoc1520m000)
SITUATION DESCRIPTION:
System is giving the fatal error 205 while submitting the documents for review.
SOLUTION DESCRIPTION:
The fatal error is solved and the documents can be submitted for review.

Solution: 129543
SITUATION IDENTIFIED IN:
"Projects" (tipcs2501m000)
SITUATION DESCRIPTION:
Float exception error (Fatal Error) occurs, while copying an existing project to a new/existing project. This error occurs only
when the target project code starts with "E". Also, after successful copying of a project, the target project is
not displayed as the first project.
SOLUTION DESCRIPTION:
Copying of project is done without any fatal errors even when the target project code starts with "E". Also,
after successful copying of a project, the target project is displayed as the first project.

Solution: 129547
SITUATION IDENTIFIED IN:
"Print Inventory by Item and Company" (whwmd2440m000)
SITUATION DESCRIPTION:
Report is not printed if cursor is not tabbed through the fields in the session.
SOLUTION DESCRIPTION:
Form field was not defaulted with Initial values, so it was not getting printed. Now the report is printed even without tabbing
through all the fields.

Solution: 129553
SITUATION IDENTIFIED IN:
"Approve purchase invoices" (tfgld1110s000)
SITUATION DESCRIPTION:
When a purchase order is partially approved , and the rates of the invoice currencies change during the partial approve
process , the created reverse hard commitment amounts are not correct.
SOLUTION DESCRIPTION:
Now the reverse hard commitments amounts are correctly created.

Solution: 129555
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When the 'Rounding factor' of the Purchase Order Currency is very high, there is a difference between Invoice Accrual
amount and the amount posted with 'Purchase/result' integration transaction entry.
SOLUTION DESCRIPTION:
The difference has been eliminated and both the amounts are same now.

Solution: 129563
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In session "tfacp1110s000 - Purchase Invoices" it is possible to link an invoice to a credit note with a bigger amount. This
will create a negative balance on the invoice.
This happens when a negative invoice is entered to be used as a credit note.
SOLUTION DESCRIPTION:
It's impossible to link an invoice with a lower balance than the credit note to this credit note.

Solution: 129564
SITUATION IDENTIFIED IN:
"Release to Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
When user processes a collect order with more than one line, the tax calculated is wrong. It gets rounded for each line. The
rounding has to be for the entire order.
SOLUTION DESCRIPTION:
Now the tax is calculated correctly.

Solution: 129565
SITUATION IDENTIFIED IN:
"Budget Amounts and Quantities by Period" (tffbs1101m000)
SITUATION DESCRIPTION:
For a budget with equal distribution mode which is not linked to a ledger account when zooming from session
tffbs1500m000 (Budget amount and quantities by year) to tffbs1101m000 (Budget amount and quantities by period) the amount is not equally distributed over each period.
SOLUTION DESCRIPTION:
Now when zooming from session tffbs1500m000 (Budget amount and quantities by year) to tffbs1101m000 (Budget amount and
quantities by period) the amount is equally distributed over each period. Because when no ledger account for the budget has
been defined the data for the ledger should not be read.

Solution: 129578
SITUATION IDENTIFIED IN:
"Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
In session "Invoices for Payment - tfcmg1220m000", in case payments are done in "Group Company" (tfcmg000.pall set to
"yes"), the original companies of the invoices should be printed.
SOLUTION DESCRIPTION:
Now the original companies of the invoices are printed.

Solution: 129582
SITUATION IDENTIFIED IN:
"Item Purchase Data" (tdipu0101s000)
SITUATION DESCRIPTION:
When the session "tipcs2220m000" (Generate Project structure for Product Variant) is run, error message "Buy From
business Partner not present".
It is not possible to generate the product structure for a product variant for a generic item. You are forced to enter a Buy -
From business partner.
The same applies when copying a standard product structure to customized structures.
Customer will be forced to enter Buy-from BP's in all their manufactured and generic components to carry on with these and
related process.
It should be possible for generic and manufacturing item project structures to be created without entering a value in the Buy
from Business Partner as they are usually manufactured internally.
SOLUTION DESCRIPTION:
Now the above-mentioned problem is solved when generating project structure or when copying a standard product structure
to a customized structure.

Solution: 129587
SITUATION IDENTIFIED IN:
"Display Purchase Invoices" (tfacp2520m000)
SITUATION DESCRIPTION:
When running session "Display Purchase Invoices - tfacp2520m000" the displayed due date is not the same as the last date
of the payment schedules when there are payment schedule lines present.
SOLUTION DESCRIPTION:
When running session "Display Purchase Invoices - tfacp2520m000" the displayed due date is the same as the last date of
the payment schedules when there are payment schedule lines present.

Solution: 129589
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
Cannot confirm a Purchase Receipt cross-docked to a Sales Consignment Replenishment Order.
The Confirmed flag of the Purchase Receipt remains to "No" whereas the Purchase/Receipt Integration Transactions are
being created.
When confirming the Purchase/Receipt for the second time, the Confirmed flag of the Purchase Receipt is properly set to
"Yes" and the Purchase/Receipt Integration Transactions are created.
As a consequence, the Purchase/Receipt Integration Transactions are created twice.
SOLUTION DESCRIPTION:
The Purchase Receipts cross-docked to a Sales Consignment Replenishment Order can now be properly confirmed.

Solution: 129596
SITUATION IDENTIFIED IN:
"Inbound Advice" (whinh2515m000)
SITUATION DESCRIPTION:
When compiling any of the following scripts: whinh2515 whinh3122 whinh3200 and whinh3520, following error appears:
Error: 5 arguments expected for function 'whinh.dll4275.confirm.shipment'.
SOLUTION DESCRIPTION:
Number or arguments has been corrected.

Solution: 129597
SITUATION IDENTIFIED IN:
"BOI Builder" (ccboi0104m000)
SITUATION DESCRIPTION:
The BOI Builder generates imcomplete source code that needs to be edited before it can be used.
Some functions like "ccboidllxmlfun.boi.format.string.domain()" are not present or at the wrong position in the source code.
This problem does not occur when no changes are made to the table field settings in ccboi0104m000.
SOLUTION DESCRIPTION:
Proper "if tag.present(X) then....." conditions in the assign.values.struc.to.table(..) function are now generated in the
source code of the BOI DLL.
The functions "ccboidllxmlfun.boi.format.string.domain()" are now at the right position in the source code.

Solution: 129598
SITUATION IDENTIFIED IN:
"Statement Ledger / Dimension Accounts" (tffst1121s000)
SITUATION DESCRIPTION:
The defaults while opening the session "Statement Ledger / Dimension Accounts" (tffst1121s000) should have 'blank to
blank' instead of 'blank to ZZZZZZ' for every dimension.
The Maximum range value of the dimensions should not be "ZZZZZZ"
SOLUTION DESCRIPTION:
The Maximum range value of the dimensions is changed from "ZZZZZZ" to ""

Solution: 129599
SITUATION IDENTIFIED IN:
standard program.
SITUATION DESCRIPTION:
Defects solved in B50b, 71a
209692
Descriptions:
- Defect 209692 Date not accepted when it is at the DST moment
DF209692:
When the Daylight Saving Time is at 0:00 then the user was not able to enter the date field for that moment.
Example in Timezone America/Sao_Paulo the DST is on october the 6th 2002 at 0:00
When the user enters on a UTC Date/Time field the date oct 6th 2002 then the date is not accepted.
The validation should only be done when the time field is filled. This is now corrected.
SOLUTION DESCRIPTION:
These defects are solved in the standard program

Solution: 129604
SITUATION IDENTIFIED IN:
"Prices per Supplier per RFQ Line" (tdpur1806m000)
SITUATION DESCRIPTION:
The total scores calculated for the suppliers, who's quoted price is same, is different when the quantities quoted by these
suppliers are different and the criterion used is only based on Price.
SOLUTION DESCRIPTION:
Now the total scores calculated will be correct when the criterion for comparison of quotations is based only on price.

Solution: 129605
SITUATION IDENTIFIED IN:
"Audit posting Data of Electronic Bank Statements" (tfcmg5203m000)
SITUATION DESCRIPTION:
Decimal amount value is not displaying on the report for the transaction amount.
SOLUTION DESCRIPTION:
Now Decimals value is correctly displaying on the report for the transaction amount.

Solution: 129611
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
When a receipt is flagged as final receipt is made, and the backorder is changed and then confirmed, a receipt line with zero
quantity is recorded in Finance. Because of this, during the selfbilling process, only the zero receipt line is invoiced, and the
original receipt is not invoiced.
SOLUTION DESCRIPTION:
Now, a check is also done on the receipt sequence number, to make sure all the receipt lines belonging to a receipt are
invoiced.

Solution: 129622
SITUATION IDENTIFIED IN:
"Maintain Posting Data of Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
In session "Maintain Posting Data of Electronic Bank Statements - tfcmg5106s000", when the user exits without saving, the
record is wrongly updated and inserted. (Respectively in tables tfcmg502 and tfcmg503).
SOLUTION DESCRIPTION:
If the user exits the session without saving, no record is updated nor inserted.

Solution: 129623
SITUATION IDENTIFIED IN:
"Print Specification Delivered Not Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
When user selects "Sales" transaction origin, "Warehousing (consignment)" transactions are printed along with "Sales"
orders.
SOLUTION DESCRIPTION:
When "Sales" transaction origin is selected, only sales order details are printed.

Solution: 129629
SITUATION IDENTIFIED IN:
"Copy Sales Orders" (tdsls4201s000).
SITUATION DESCRIPTION:
When copying a sales order to another Sold-to Business Partner, the country field (tdsls401.ccty) of the new Sales Order Line
is the same as on the original line.
SOLUTION DESCRIPTION:
When copying a Sales Order to another Sold-to Business Partner the country field (tdsls401.ccty) will be filled with the
right value. The value will be the same as when a line is added to the new created Sales Order manually.
During copy, the right country is determined when defaulting the country field belonging to the Sold-to Business Partner
that is on the new created Order Header. The same country will be used on the lines.
When the original lines are split, (so details exists), the details are all totalized per line. Although the original details
may have different Ship-to Addresses and therefore different countries, when copying them to another Sold-to Business
Partner (having another Ship-to Address) this is not relevant anymore.

Solution: 129630
SITUATION IDENTIFIED IN:
"Confirm Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When receiving a Sales Return Order, the Financial Integration created for the Sales Item or Warehouse Issue Surcharges and
the Inventory Receipt Transactions (as registered in the table whinr112) could be created with an incorrect amount.
This happens when a Variance (as registered in the table whinr116) was assigned to the original Receipt (from which the
returned Issue was consumed) after the Issue had been processed.
This only happens if the Item Valuation Method if FIFO or LIFO.
The Inventory Receipt Transactions and the Surcharges included the assigned Variances. This is not correct.
Example:
01-01-2002
Receipt created for 19 pcs.
02-01-2002
Issue 11 pcs (that will consume the receipt above)
03-01-2002
Match and Approve the Receipt in Finance.
A Variance is created for the price difference
04-01-2002
Assign the variance to the Receipt.
05-01-2002
Return the Sales Order.
SOLUTION DESCRIPTION:
The assigned Variances will be deducted from the Receipt Amounts.

Solution: 129637
SITUATION IDENTIFIED IN:
"Generate Picking List" (whinh4415m000)
SITUATION DESCRIPTION:
1. Revision number not printed on Picking list.
2. When multiple sequence number exists for the same position of a warehouse order outbound line, and for each sequence
number
if different text is maintained, only the last text is printed and only once per position number.
SOLUTION DESCRIPTION:
1. Now Revision number is printing in both the reports of picking list.
2. Now text is correctly printed for each sequence number.

Solution: 129640
SITUATION IDENTIFIED IN:
"User Data" (ttaad2500m000)
SITUATION DESCRIPTION:
In session "User Data (ttaad2500m000)", change the sort key to "Company and User", and use "find" option. The zoom is not
present for field "company".
The same problem occurs for fields "Package Combination" and "Language".
SOLUTION DESCRIPTION:
Now we can zoom to all these fields.

Solution: 129645
SITUATION IDENTIFIED IN:
"Approve Purchase Invoices" (tfacp1140s000)
SITUATION DESCRIPTION:
The creation of costs and commitment lines in projects for project-related Purchase-Invoices are depending, during the
approval, on the fact if the
last invoice is processed. Sometimes this is NOT coming to projects. So the projects cann't be processed.
SOLUTION DESCRIPTION:
The determination, in the approval-process, if it is the 'last'-invoice (for project related Purchase Orders) is changed in such a
way that there is not looked at the 'order'-quantity but at the 'approved'- AND the 'rejected'-quantity.

Solution: 129647
SITUATION IDENTIFIED IN:
"Copy Labels between Packages" (ttadv1240m000)
SITUATION DESCRIPTION:
When copying labels between packages, expired labels are also copied.
SOLUTION DESCRIPTION:
Now an additional check box option has been provided, to enable the user to choose whether or not to copy expired labels.
Usage:
When the check box 'Also copy expired labels' is checked, then expired labels are also copied to the destination package.
When the check box is unchecked, then the expired labels are not copied.

Solution: 129653
SITUATION IDENTIFIED IN:
"Generic Routing" (tipcf3120s000)
SITUATION DESCRIPTION:
1) Fatal Error: "Index out of Dims..." appears when generating a product variant structure. This fatal error occurs when
operation text on generic routings exceeds 999 lines.
2) In multi occurrence overview of "Generic Routing" (tipcf3520m000), the text editor is accessible with write
authorizations.
SOLUTION DESCRIPTION:
1) A maximum of only 999 lines of operation text is allowed. If this number is exceeded, then an error message will be given
and consecutively the text editor will be started again in order to enable the user to decrease the number of text lines.
2) In multi occurrence overview sessions, text should not be editable. Text is accessible, but only with read authorizations.
Text can be edited in single occurrence sessions.

Solution: 129659
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
1.When copying a Call the Invoice Interval is not copied.
2.When copying a Call the Duration is not updated from the required activity.
3.When copying a newly created Call without closing the session the Call group is not copied.
SOLUTION DESCRIPTION:
1. The Invoice Interval is also copied when copying a Call.
2. When copying a Call the Duration will also be copied. It will not be determined from the required activity.
3. When copying a Call the Call Group is always copied.

Solution: 129661
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
For a Collect Return Purchase Order, user is not able to change the warehouse in case of insufficient inventory because the
warehouse field is disabled. Also, the warehouse is not defaulted for this type of Purchase Order.
SOLUTION DESCRIPTION:
Now the default warehouse is found and defaulted on to the purchase order line even for a collect return purchase order. Also,
the warehouse field is enabled so that user can change it to a different warehouse in case of insufficient inventory.

Solution: 129669
SITUATION IDENTIFIED IN:
"Confirm Shipment" (whinh4275m000)
SITUATION DESCRIPTION:
-1- A shipment line with a Cost Item (that is thus released to Warehousing) and an Ordered Quantity and a Shipped Quantity
of 0.0 could not be confimed.
The session Confirm Shipment (whinh4275m000) displayed the error message "Confirm Shipment Failed".
-2- When Sales Order Lines were split when confirming a shipment, an Order Header Discount could be calculated for a
Cost Item.
SOLUTION DESCRIPTION:
-1- It is now possible to confirm the shipment
-2- No Order Header Discount will be calculated for a Cost Item.

Solution: 129679
SITUATION IDENTIFIED IN:
"Cycle Counting Data" (whinh5140s000)
SITUATION DESCRIPTION:
In "Cycle Counting Data" when we enter a record manually, after entering Warehouse, Location, Item, Lot, Inventory Date, if
we use 'TAB', the Field 'Force Cycle count' gets disabled and we can't use it any more.
This is happening only in B50_b but not in B50_c
SOLUTION DESCRIPTION:
Now the field is enabled even if we use TAB after entering all the data.

Solution: 129686
SITUATION IDENTIFIED IN:
"Maintain Statement Ledger/Dimension Accounts" (tffst1104m000)
SITUATION DESCRIPTION:
Blocking Error Message "No dimensions found in given range" pops up when entering a dimension range which is not
specified for a particular Ledger account or a range of Ledger accounts.
SOLUTION DESCRIPTION:
"No dimensions found in given range" won't pop up now as a Blocking Error Message and its been converted into a Warning
message when entering a dimension range which is not specified for a particular Ledger account or a range of Ledger
accounts.

Solution: 129701
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
An item on the Sales Order Line (tdsls4101s000) has the same price group as an item that is on a Sales Contract Line
(tdsls3101s000).
When the option 'apply contract for all items in price group' is checked on the Sales Contract Line, the price out of the price
book as is on the contract should be used. However, for this line the price of the item on the contract line is taken.
SOLUTION DESCRIPTION:
When the option 'apply contract for all items in price group' is checked on the Sales Contract Line the price is taken out of
the price book as is on the Sales Contract Line using the correct item.

Solution: 129708
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When an invoice with subcontracting and shifted vat was directly linked to a credit note in session "Purchase Invoices -
tfacp1110s000" the approval batch got unbalanced when you have to set the field subcontracting to "yes" and the vat code to
shifted after saving. This could happen when entering the credit note a mistake was made regarding those fields..
SOLUTION DESCRIPTION:
The batch is now balanced also when the subcontracting field is changed to yes and the vat code is changed to shifted on the
credit note.

Solution: 129711
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: 129716
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
When the weight unit for an item is different from the base weight unit, the additional costs based on weight are not
calculated correct.
If a weight unit different from the base weight unit (as in session tcmcs0100s000) is used for the item weight, the total weight
of a sales order is not correctly calculated. This means that additional costs of the type weight are not correct calculated.
SOLUTION DESCRIPTION:
For every Order Line the weight is now converted to the base weight unit. Then the total weight is compared with the
additional cost set based on weight and cost lines are correct added.

Solution: 129717
SITUATION IDENTIFIED IN:
"Copy Ranges of Lots." (whltc1201m000)
SITUATION DESCRIPTION:
When copying lots using session whltc1201m000 "Copy Ranges of Lots" and option "Generate Lot Code" is selected, newly
generated lots have: - lot size, - first issue date, - first receipt date, - lot date and - order number filled with data from the original lot.
(It causes, for instance, that a newly generated lot cannot be used for a new SFC order)
SOLUTION DESCRIPTION:
This information it is not copied from the original lot any more, instead lot size, first issue and receipt date are initialized
to zero, lot date with the current date and order number is blank.

Solution: 129720
SITUATION IDENTIFIED IN:
"Reconciliation of Receipts/Payments" (tfcmg2103s000)
SITUATION DESCRIPTION:
In session "Reconcile Receipts/Payments - tfcmg2103s000", when rejecting a partial reconciliation, the batch is not in
balance. Furthermore, the part of the payment that is still open cannot be reconciled either.
SOLUTION DESCRIPTION:
A partial reconciliation can now be rejected without creating an unbalanced batch. The part of the payment that remains open
can also further reconciled.
Reconciliation batch not is balanced after rejecting a partial payment

Solution: 129728
SITUATION IDENTIFIED IN:
"Print Control Account Checklist" (tfacr2415m000)
SITUATION DESCRIPTION:
Totals are not printed when no records are present with "No differences". When no records are present with differences, at
least totals need to be printed, with difference amount as zero.
SOLUTION DESCRIPTION:
When no records are present with difference amount, totals are made to print with the difference amount zero.

Solution: 129729
SITUATION IDENTIFIED IN:
"Print Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
Wrong Assigned documents for unallocated receipts are shown.
SOLUTION DESCRIPTION:
Correct Assigned documents for unallocated receipts are shown.

Solution: 129731
SITUATION IDENTIFIED IN:
"Print Extensions " (tpptc0410m000)
SITUATION DESCRIPTION:
Print selection on "Business Sector" not working. When we give a specific "Business Sector" and run the session, all the
records are printed.
SOLUTION DESCRIPTION:
The above-mentioned problem is solved. Now, when we give a specific "Business Sector" and run the session, only records of
the selected "Business Sector" are printed.

Solution: 129744
SITUATION IDENTIFIED IN:
"Display Customer Invoices in a company" (tfacr2535m000)
SITUATION DESCRIPTION:
Invoice amount is not shown correctly
SOLUTION DESCRIPTION:
Invoice amount is shown correctly

Solution: 129745
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Report BTL-9, line 21, is always printing the payment date determined on field 'Planned Payment Date', in session
'Select Invoices for Payment' (tfcmg1220m000) or 'Maintain Payment Advice' (tfcmg1120m000).
This is incorrect when field 'Planned Pmt Date = Due Date' is set to 'NO', on session 'Maintain Payment Methods'
(tfcmg0140m000).
In this case, the payment date printed on report BTL-91 must be the one entered in session 'Transfer Payments'
(tfcmg1260s000) on field 'Payment Date'.
SOLUTION DESCRIPTION:
The payment date printed on report BTL-91, line 21, is set as follows depending on the value of field 'Planned Pmt Date =
Due Date' (session 'Maintain Payment Methods'):
- If 'Planned Pmt Date = Due Date' is set to 'YES', the payment date must be the one determined on field 'Planned Payment
Date', in session 'Select Invoices for Payment' (tfcmg1220m000) or 'Maintain Payment Advice' (tfcmg1120m000).
- If 'Planned Pmt Date = Due Date' is set to 'NO', the payment date must be the one entered in session 'Transfer Payments'
(tfcmg1260s000) on field 'Payment Date'.

Solution: 129748
SITUATION IDENTIFIED IN:
"Business partner's invoices in a company" (tfacr2535m000)
SITUATION DESCRIPTION:
The footer fields are overlapped in detail lines if the window size is changed.
SOLUTION DESCRIPTION:
Now footer is moved to the top of the detail lines. Hence the date and period line is not overlapping on the details.

Solution: 129749
SITUATION IDENTIFIED IN:
"Sales Quotation Price Inquiry" (tdsls1501s110)
SITUATION DESCRIPTION:
When zooming from session "Sales Quotation Lines" (tdsls1501m000) to session "Sales Quotation Price Inquiry"
(tdsls1501s110), the Gross Margin Percentage is incorrect calculated.
The same happens with session "Sales Contract Price Inquiry" (tdsls3501s110)
SOLUTION DESCRIPTION:
To make sessions "Sales Quotation Price Inquiry" (tdsls1501s110) and "Sales Order Price Inquiry" (tdsls4501s110) more
comparable the cost price is displayed in the sales price unit now.
The Gross Margin is displayed as Gross Profit as that is what is calculated. The Gross Profit is calculated correct.
The same is done with session "Sales Contract Price Inquiry" (tdsls3501s110)

Solution: 129760
SITUATION IDENTIFIED IN:
"Process Periodical Depreciation Calculation" (tffas2200m000)
SITUATION DESCRIPTION:
If a disposal journal entry which is not posted is deleted, it is no longer possible to depreciate the asset further in session
"Process Periodical Depreciation Calculation" (tffas2200m000).
SOLUTION DESCRIPTION:
It is now possible to depreciate the asset further, if the asset disposal is reversed.

Solution: 129764
SITUATION IDENTIFIED IN:
"Generate FTP Script" (ttpmc2211s000)
SITUATION DESCRIPTION:
For customers, who have access to the internet from behind a firewall, the Multilevel Download Tool of PMC doesn't work,
because the user id field is too short to hold e.g. 'ecommerce/1234567a@ftp.support.baan.com'.
For users, who are using the Baan IV c ASCII-interface (BA), there was a problem when they used the new functionality
offered in solution 129305. Instead of storing the password for the Baan FTP server in $BSE/lib/ftpbaan, it is asked just
before downloading a solution. For ASCII-users however, the login screen was not shown on top of the other windows, but
was hidden behind the other windows and the user needed to switch manually to the login screen.
SOLUTION DESCRIPTION:

The user id field has been extended from 32 to 60 characters.
Baan IV c ASCII users will see the login screen now on top of the other windows.

Solution: 129766
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
When a selection is processed twice, during the second processing a message "tcempty" is displayed. This doesnt create any
additional problem otherwise.
SOLUTION DESCRIPTION:
This message is no longer displayed.

Solution: 129769
SITUATION IDENTIFIED IN:
"Report Operations Complete" (tisfc0130s000)
SITUATION DESCRIPTION:
In 'General Item data' (tcibd0101s000), an item signal is entered with production issue 'blocked' for an item. This
component item is to be backflushed for a production order after completing an operation for the order. While backflushing,
though the component is not issued, no error message or report appear stating that the component has not been issued.
SOLUTION DESCRIPTION:
When backflushing an item that is blocked for production issue, a message (Material %s on line %d is blocked for issue:
Signal code) will be printed on the 'Backflush error report'.

Solution: 129778
SITUATION IDENTIFIED IN:
"Graph Vendor Ratings" (tdpur8701m000)
SITUATION DESCRIPTION:
Fatal Error occurs when running the session "Graph Vendor Ratings" (tdpur8701m000), for one Business Partner, for just
one Period.
SOLUTION DESCRIPTION:
An appropriate Error message 'Graph cannot be drawn - Range for Period required' is popped up.

Solution: 129801
SITUATION IDENTIFIED IN:
"Maintain Posting Data for Electronic Bank Statements" (tfcmg5106s000)
SITUATION DESCRIPTION:
Fatal error when selecting an invoice, which was already selected in another batch, in the payment advice.
It is because same message code with different parameters is used in Electronic Bank Statements (EBS)
SOLUTION DESCRIPTION:
Now, fatal error doesn't occur in the payment advice even when an invoice is reselected again. A message "Document
already selected in company %s, batch %d" is given.

Solution: 129802
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1. A the Purchase Order Line is created.
2. The order line is received.
3. The price of the Purchase Order Line changes if the Recalculate Price and Discounts is done for this purchase order line.
4. The price should not be recalculated if the order line has been received already.
SOLUTION DESCRIPTION:
The Price and Discount of the purchase order line will not be recalculated, if the order line has been partially (or) fully
received already.

Solution: 129806
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
Some Purchase Order Lines that are received, and not processed are not displayed in the above session.
SOLUTION DESCRIPTION:
All the relevant Purchase Order Lines are displayed, now.

Solution: 129811
SITUATION IDENTIFIED IN:
"Quotations" (tdsls1100s000)
SITUATION DESCRIPTION:
For languages 1 and 3 the description of the second sales representative is missing
SOLUTION DESCRIPTION:
Enlarged the available space of the label on the form so now a description is available for all 3 main languages.

Solution: 129815
SITUATION IDENTIFIED IN:
"Process Quotations to Service Orders" (tssoc1200m000)
SITUATION DESCRIPTION:
When a service order quotation which has a reference activity is processed to a service order, the efficiency rate mentioned in
the labor requirements of the reference activity are not copied to service order estimated labor cost lines.
SOLUTION DESCRIPTION:
When a service order quotation is processed to a service order, the efficiency rate of the reference activity attached to the
quotation is copied to the service order estimated labor cost lines.

Solution: 129820
SITUATION IDENTIFIED IN:
"Print Solutions by Update VRC" (ttpmc2401m000)
SITUATION DESCRIPTION:
Some solutions were printed twice. A solution was printed as the last one of a page and the first one of the next page. This
only happened when the page was full exactly after printing the solution header.
SOLUTION DESCRIPTION:
Solutions are not printed twice anymore. However, when you select to print the components, solutions and/or dependencies,
the solution header will still be repeated on the next page.

Solution: 129821
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
During conversion of an Electronic Bank Statement (EBS) file, the "Reference" and the "Description" text is not put in the
first line, but in the second line.
SOLUTION DESCRIPTION:
The "Reference" and the "Description" text are stored, starting from the first line.

Solution: 129834
SITUATION IDENTIFIED IN:
"Scan Solution File" (ttpmc2200s000)
SITUATION DESCRIPTION:
In session "Scan Solution File" (ttpmc2200m000/ttpmc2200s000) it is possible to scan a complete directory. However, when
you run the session directly with the saved defaults of the last time, error messages were shown, like:
"Error -13 during seq.open file ...." or "Header ... not expected"
Also, when you have scanned a directory successfully and you want the scan a single file after that, an error message was given.
SOLUTION DESCRIPTION:
With this solution you can scan directories and files after each other and you can also run the session directly from the saved
defaults. Also a possibility to stop the scanning of the directory after an error message has been given.

Solution: 129835
SITUATION IDENTIFIED IN:
"Print Open Entries" (tfacp2421m000)
SITUATION DESCRIPTION:
On form 3 of session "Print Open Entries" (tfacp2421m000), a label is missing in German language.
SOLUTION DESCRIPTION:
The label is present in form 3 for German language.

Solution: 129847
SITUATION IDENTIFIED IN:
"Print Sales Contract Reminders" (tdsls3406m000)
SITUATION DESCRIPTION:
When printing the reminder during the effective period no output will be created.
SOLUTION DESCRIPTION:
The calculation needed when checking the percentage of the elapsed period with the "Minimum Time Required for
Evaluation" was incorrect. Changed the calculation to make the comparison working correctly.

Solution: 129850
SITUATION IDENTIFIED IN:
"Reprint Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
When printing a Sales Invoice in case of a Bilateral or Triangular setting, the message "Do Not Print" is printed on the Inv.
Header.
SOLUTION DESCRIPTION:
This message will not appear on the Invoice Header anymore.

Solution: 129851
SITUATION IDENTIFIED IN:
"Check and Install Solutions" (ttpmc2204s000)
SITUATION DESCRIPTION:
When you start this session directly from the menu and you have no saved defaults, then the solution range is displayed as
'blank' to '9999999999999'. When you tab in the Solution From field, an error message 'not allowed' is given.
SOLUTION DESCRIPTION:
The Solution From field is not mandatory anymore. Also the default for the Solution To has been changed to
'zzzzzzzzzzzzzz' to support also non-numeric solution numbers.

Solution: 129863
SITUATION IDENTIFIED IN:
"Import Actual Costs from GLD" (tfcat2210m000)
SITUATION DESCRIPTION:
When the data, required for the session "Import Actual Costs from GLD" is very high, the session will abort with a
Roll-back Error. This has to be changed.
SOLUTION DESCRIPTION:
Now the transaction handling has been changed, so that very large amounts of data can be handled by the system

Solution: 129873
SITUATION IDENTIFIED IN:
"Generate Configuration Structures" (tscfg2210m000)
SITUATION DESCRIPTION:
System is giving fatal error index out of dims, cannot continue, in session "Generate Configuration
Structures"(tscfg2210m000).
SOLUTION DESCRIPTION:
System will not give the index out of dims error while generating configuration structure.

Solution: 129876
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
A)
1. The Order Balance of a purchase order increases in "Purchase Order Lines" (tdpur4501m000) when the order line is
created.
2. It comes down once the invoice of the purchase order line is approved. This does not happen to the cost items.
3. The Order Balance does not reduce for the cost items, even when the invoice is approved.
B)
1. A self-billing subcontracting purchase order is partial received with out 'Final Receipt' check box selected in
"Receipts" (whinh3520m000)
2. Self-billing invoice for this receipt is generated in Finance package.
3. Now the Final Receipt for the purchase order is done with zero quantity.
4. While trying to close the production order, it is not possible, as the linked purchase order is not, considered to be fully
invoiced.
C)
1. A self-billing purchase order is partially received.
2. The back order quantity is changed for this line.
3. When the self-billing invoice is generated for this order, two invoices are generated while the second invoice is for zero
quantity and zero amounts.
SOLUTION DESCRIPTION:
A) The Order Balance will come down for the Invoice From Business Partner once the purchase invoice is approved. The sum
of the Order Balances displayed for the all the orders in "Purchase Order Lines" (tdpur4501m000) is the total Order
Balance of the Invoice From BP.
B) It is possible to close the production orders even when the Final Receipt of the linked purchase order is for zero quantity.
C) The extra self-billing invoice for zero amounts is not generated while changing the back order quantity of the purchase
order line.

Solution: 129883
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
The backorder of a consignment replenishment order cannot be deleted. whinhs0458 "Deleting an inbound order line can
only be done by deleting the outbound order line." comes up.
SOLUTION DESCRIPTION:
The problem was caused by an incorrect check on existing outbound lines. The check is corrected.

Solution: 129884
SITUATION IDENTIFIED IN:
"Replace Items in Bills of Material" (tibom1212m000)
SITUATION DESCRIPTION:
System should ask a question to the user when replace items in bills of material whether to continue or not, when the units
of item to replace and replacement items are different
SOLUTION DESCRIPTION:
System will ask the question (e.g. Units of Item 'X' and Item 'Y' do not match, continue?) to user to continue when the units
of Item to replace and replacement items are different when replace items in bills of material. If the user says 'NO' to the
question, the control will go to the replacement item.

Solution: 129888
SITUATION IDENTIFIED IN:
"Write off Currency Differences" (tfacr2250m000)
SITUATION DESCRIPTION:
Even though nothing is found to write off, batch and document number are created, the status of the document is deleted,
but locking status of document is IN USE -instead of changing it to FREE.
SOLUTION DESCRIPTION:
Even though nothing is found to write off, batch and document number are created, but locking status of document should
be FREE -instead of IN USE. Where the status of the document is deleted

Solution: 129904
SITUATION IDENTIFIED IN:
"Print sales contract reminders" (tdsls3406m000)
SITUATION DESCRIPTION:
Item Sales Text added in Item Sales Data (tdisa0101s000) and contract lines linked to sales orders cause the report details
from 'Print Contract Reminders' (tdsls3406m000) to be moved up. This occurs when the report is printed the second time,
without closing the session.
SOLUTION DESCRIPTION:
The variable used for printing the report details: item code, description, text, etc. is being used for sorting the report. The
program script as well as the report has been modified so this variable will get the right value so it can used to sort the data.

Solution: 129905
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the "Amounts Entered" option for the tax code is defined as "Gross Over Hundred", then the tax is calculated
wrongly when a 100% tax rate is defined. Also the Goods Amount has to be zero, but the invoice shows some value.
SOLUTION DESCRIPTION:
Now the tax is calculated correctly and the invoice is printed correctly.

Solution: 129908
SITUATION IDENTIFIED IN:
"Reprint Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
It was not possible to reprint the sales invoice from archiving company and it is giving an error message stating that ' No
Data within selection'.
SOLUTION DESCRIPTION:
It is reprinting the sales invoice from archiving company.

Solution: 129909
SITUATION IDENTIFIED IN:
"Service Order Actual Other Costs" (tssoc2141s000)
SITUATION DESCRIPTION:
When the user changes the 'Actual Cost' for the subcontracted cost generated by receiving a purchase orders in the session
"Service Order Actual Other Costs" (tssoc2141s000), there will some extra entry to the accrual account, which cannot be
cleared in finance. If there is any change to the Actual Cost, it should be carried out by changing the price of the Purchase
Order Price in the session "Change Price/Discounts after Receipts" (tdpur4122m000) session.
SOLUTION DESCRIPTION:
The fields 'Cost Price, Quantity and Cost Type have been disabled so that the user will not be able to change the value in
these fields.

Solution: 129911
SITUATION IDENTIFIED IN:
"Update purchase statistics" (tdpst0201m000)
"Update sales statistics" (tdsst0201m000)
SITUATION DESCRIPTION:
Statistics are incorrectly updated in case customized items are present in a particular order.
SOLUTION DESCRIPTION:
The function where the item data is read has been adjusted to allow system to update the statistics for customized items in
the following way:
- If the value of the derived from item field in the general item data table of the 'general item data' session is an existing
standard item code, the customized item data is stored in the statistics under the standard item
- If no value is specified in the derived from field, you must enter a standard item code in the parameters where you want to
store the data. This code can be used in the statistics to cumulate any customized item that are not specified as deriving from
a standard item.
When the parameter "Item customized items" is not filled and the customized item is not derived from a standard item, the
error message 'Parameter "Item customized items" not filled' will be printed in the error report when updating the statistics.

Solution: 129925
SITUATION IDENTIFIED IN:
"Release to Warehousing (Batch)" (tdsls4246m000)
SITUATION DESCRIPTION:
When releasing a range to warehousing with in the range one borderline cannot be released because the quantity is partially
committed and the Shipping Constraint is 'Ship Complete, an error message is given and nothing is released.
SOLUTION DESCRIPTION:
For the line that cannot be released to Warehousing a line is printed on the error report ("Quantity not yet fully committed.
Release to warehousing not allowed"), the other lines in the range that can be released to Warehousing are released.

Solution: 129929
SITUATION IDENTIFIED IN:
"Print Fixed Assets - General Ledger Reconciliation" (tffas0442m000)
SITUATION DESCRIPTION:
For a disposed asset the report "Print Fixed Assets - General Ledger Reconciliation" (tffas0442m000) was printing the
value of "Accumulated Depreciation" on the report.
SOLUTION DESCRIPTION:
A new option is provided on the form to print the accumulated depreciation for a disposed asset.

Solution: 129941
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
In case the order has a fixed rate the current rate is used when entering the order in an invoice. The order rate should be
used.
SOLUTION DESCRIPTION:
After installing this solution the fixed rate of the order is used when entering the order in an invoice.

Solution: 129942
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2100s000)
SITUATION DESCRIPTION:
When outbound lines or inbound lines for a Production (manual) order are released, the system seems to be busy for a
moment but does nothing.
SOLUTION DESCRIPTION:
One of the dll's that is used returned an incorrect value.
Lines can now be released.

Solution: 129946
SITUATION IDENTIFIED IN:
"Financial Values(Actual)" (tffst1204m000)
SITUATION DESCRIPTION:
For general ledger accounts with type "intercompany", opening balances are not filled where as the opening balances are
filled correctly for the general ledger with type "Balance sheet".
SOLUTION DESCRIPTION:
For general ledger accounts with type "intercompany", opening balances should be filled, the way it is filled for the ledger
accounts with type "Balance sheet".

Solution: 129951
SITUATION IDENTIFIED IN:
"Item Warehousing Data" (whwmd4500m000)
SITUATION DESCRIPTION:
When zooming from any session to session "Item Warehousing Data" (whwmd4500m000), always the search on the search key of
the item is performed. This should only be done if that is decided in the zoom from session. In that situation the user enter
the first part of the search key, followed by a comma (,) and press the tab button.
SOLUTION DESCRIPTION:
This solution restores the old situation for zooming from an item field to the session "Item Warehousing Data". That means, when using the
binocular (or Ctrl-B) that the system go to whwmd4500m000 ordered on item code.
Only when a user zooms to whwmd4500m000 with the comma preceded by a tab, that whwmd4500m000 is sorted on search
key.
NOTE. When zooming via the binoculars, not always the matching item is found. In some sessions the first item is shown, without taking into
account the zoom-from item. This is a known issue and will not be solved in the current releases.

Solution: 129953
SITUATION IDENTIFIED IN:
"Sales Orders below/above allowed margin" (tdsls4518m000)
SITUATION DESCRIPTION:
Cancelled sales order lines still appear in "Sales orders below/above Margin" (tdsls4518m000) mixed with active sales
orders that are below or above the margin.
SOLUTION DESCRIPTION:
It is preferred to see the cancelled lines in the session "Sales orders below/above Margin" (tdsls4518m000). But to make the
session more user friendly two specific options are introduced that gives the user the possibility to show all the lines or to
see the not cancelled order lines only.
Also the deleted order lines were visible in session tdsls4518m000. This is of no use so these lines are no longer visible.
This also applies to the session "Quotations below/above Margin" (tdsls1518m000)

Solution: 129954
SITUATION IDENTIFIED IN:
"Maintain Posting Data For Electronic Banks Statements" (tfcmg5106m000)
SITUATION DESCRIPTION:
Amount in home currency is wrongly calculated for unallocated Receipts or unallocated payments.
SOLUTION DESCRIPTION:
Now, home currency amount is calculated correctly for unallocated Receipts or payments.

Solution: 129956
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
Running a job with session 'Select Invoices for Payment' (tfcmg1220m000) on daily basis is not possible. When activating
the job again the system tries to use same batch number again.
SOLUTION DESCRIPTION:
When an already created job with session 'Select Invoices for Payment' is activated again, a new batch number has been
created.

Solution: 129967
SITUATION IDENTIFIED IN:
"Import Actual Costs from GLD" (tfcat2210m000)
SITUATION DESCRIPTION:
When the data, required for the session "Import Actual Costs from GLD" is very high, the session will abort with a
Roll-back Error. This has to be changed. New changes were added because of the large amount of data
SOLUTION DESCRIPTION:
Now the transaction handling has been changed, so that very large amounts of data can be handled by the system

Solution: 129989
SITUATION IDENTIFIED IN:
"Release to Invoicing" (tdsls4247m000)
SITUATION DESCRIPTION:
Error message "Error 205 (Out of range)", when "Release to Invoicing" is done. This happens when the cost price holds more
than 13 digits.
SOLUTION DESCRIPTION:
Now the error does not occur.

Solution: 129991
SITUATION IDENTIFIED IN:
"Calculate Sales Prices by Item" (ticpr2250m000)
SITUATION DESCRIPTION:
Fatal error "ERROR 205 (out of range)" on Sales price calculation, if the calculated sales price is having a very small
negative number (like -0.00000001).
SOLUTION DESCRIPTION:
The system will make the calculated sales price as zero, if it is negative.

Solution: 129996
SITUATION IDENTIFIED IN:
"Element Budget (Material Lines)" (tpptc1510m000)
SITUATION DESCRIPTION:
In Element Budget (Material Lines), the "Text" column is not present. So, it is difficult for the user to know if text is present
for the budget line or not. The same is present for all other cost types.
SOLUTION DESCRIPTION:
The "Text" column is added to the form like other cost types & the column will indicate whether or not the text is present.

Solution: 129997
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When entering an invoice with shifted vat in session "Register Purchase Invoices - tfacp1110s000" the shifted vat amount in
home currency isn't filled.
SOLUTION DESCRIPTION:
The shifted vat amount in home currency is filled now when a shifted vat code is entered.

Solution: 130002
SITUATION IDENTIFIED IN:
"Print Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
When aging analysis code with type days is changed to months.
Re-initialization of values have been taken care, But the re-enabling and disabling of the fields is not done.
When Aging Analysis code with period type "month" is used, "as on year/period" fields are disabled.
SOLUTION DESCRIPTION:
When aging analysis code with type days is changed to months.
Re-initialization of values and the re-enabling and disabling of the fields is done.
When Aging Analysis code with period type "month" is used, "as on year/period" fields should be enabled.

Solution: 130010
SITUATION IDENTIFIED IN:
"Import Data Dictionary" (ttiex1288m000)
SITUATION DESCRIPTION:
The problem occurs when an export dump is imported in another VRC, and the dump contains an object and no program script
for this object.
In this dump, information is present for the Baan tables, about the program script and the object that are imported.
An import is done into another VRC.
When a program script for the imported object can be found in the Baan tables, using the VRC derivation structure, and the
program script is present on the system, then no information is added to the Baan table for the program scripts.
The information about the imported object contains information about the VRC of the program script for this object.
After the import, the information in the imported object is not correct.
The VRC of the program script for this object is the same as the VRC of the object, being the VRC into which the dump
was imported.
The program script does not exist in that VRC. It was not added in this VRC during the import because a program script
could be found using the derivation structure.
SOLUTION DESCRIPTION:
When no information is added to the Baan table for program scripts, the information of the object needs to modified.
The correct VRC for the program script of the imported object is found by following the VRC derivation structure.
The VRC-information of the found program script is placed in the object-record.
The information of the imported object now contains the correct VRC of its program script.

Solution: 130027
SITUATION IDENTIFIED IN:
"Print Service-Order Quotation Documents" (tssoc1400m000)
SITUATION DESCRIPTION:
The label 'Final Document' is missing in Dutch on first form of session.
SOLUTION DESCRIPTION:
On the first form, enough space is reserved for the label 'Final Document' so that the label is shown in Dutch on first form of
session.

Solution: 130032
SITUATION IDENTIFIED IN:
"Product Variants" (tipcf5501m000)
SITUATION DESCRIPTION:
When a sales price structure for a variant is generated, a fatal error pops up, complaining about tipcf530.dsca. The field is
empty whereas it should be filled (table definition gives mandatory).
Problem only occurs when no generic price list for the generic item is defined AND when the item description of the sub
item is empty.
Next to that the language of the company was not read, causing a wrong comparison with the text language.
SOLUTION DESCRIPTION:
It's checked if the description of the sub item is empty. If so, the description of the product variant sales price structure is
filled with the item code of the subitem.
Company language is read so that a good check is done with the language of the text.

Solution: 130043
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
This situation can occur when the functions "Generate Outbound Advice" and "Confirm Shipment" are executed
simultaneously for the same item.
Message "Error 107 (Record is locked) on whinr140 (Max retries exceeded)" is shown and the process "Generate Outbound
Advice" is aborted.
SOLUTION DESCRIPTION:
The process is adapted so that this specific lock situation is avoided.

Solution: 130045
SITUATION IDENTIFIED IN:
"Direct Network Communication" (tcedi7205m000/ecedi7205m000)
SITUATION DESCRIPTION:
When reading an order acknowledgment and an order change acknowledgment in one run, no differences report is generated
for the order change acknowledgment. When these message are processed in different processes, a is generated properly,
for both messages being the "Differences Between Purchase Order and Order Response" (B40_c) or "Differences Between
Purchase Order and Order Acknowledgment" (B50_b/c)".
SOLUTION DESCRIPTION:
Due to incorrect initialization, the report was not generated in the described situation. In order to be able to distinguish
between the order acknowledgment and the order change acknowledgement, a new report has been created for the
latter message: "Differences Between Purchase Order & Order Change Response" (B40_c) and "Differences Between Purchase Order & Order
Change Acknowledgment" (B50_b/c)".

Solution: 130054
SITUATION IDENTIFIED IN:
"Print Sales Statistics" (tdsst0401m000)
SITUATION DESCRIPTION:
When printing the statistics report in german language, the label in the footer says: "I = Auftragserf. C = Storn. T =
Umsatz B = Budget" instead of "A = Auftragserf. S = Storn. U = Umsatz B = Budget".
SOLUTION DESCRIPTION:
Correct label is shown for all langauges on all reports.

Solution: 130068
SITUATION IDENTIFIED IN:
"Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
When canceling a consignment replenishment backorder in sales the incorrect error message "Warehouse
order/pos.number.seq.number "XX/YY/Z" of origin Sales not found." is shown
SOLUTION DESCRIPTION:
A consignment replenishment backorder can be cancelled or deleted without error messages if the advice for this backorder
is not yet released. The inbound and outbound order line for the corresponding transfer order in warehousing are deleted.

Solution: 130071
SITUATION IDENTIFIED IN:
"Print Control Account Checklist" (tfacp2415m000)
SITUATION DESCRIPTION:
Totals are not printed when no records are present with "No differences". When no records are present with differences, at
least totals need to be printed, with difference amount as zero.
SOLUTION DESCRIPTION:
When no records are present with difference amount, totals are made to print with the difference amount zero.

Solution: 130074
SITUATION IDENTIFIED IN:
"Print Work-in-Process" (ticst0450m000)
SITUATION DESCRIPTION:
Session "Print Work-in-Process" (ticst0450m000) incorrectly displays the session defaults, instead of retaining the modified
values, when switching from one form to other. In other words, if the data on first tab 'Selection Range' is modified and then
the data on second tab 'Settings' are modified, both form tabs are reset with the stored session defaults. This problem occurs
only when there are default settings present for the session.
SOLUTION DESCRIPTION:
Session "Print Work-in-Process" (ticst0450m000) will display the default settings only when the session is opened if there
are any defaults present for the session, and the system will retain the data if any modifications are made while switching
over from one form to other.

Solution: 130085
SITUATION IDENTIFIED IN:
"Sales and Warehouse Order Invoice Lines" (cisli2545m000)
SITUATION DESCRIPTION:
For bilateral or triangular invoicing a price type is defined in session "Entity-Entity relationship" (tcemm2510m000). If the
price type is "Commercial Price", the invoice amount is not rounded according to the rounding of the invoice currency.
If the price type is "Transfer Price", the amounts are calculated and rounded correctly.
SOLUTION DESCRIPTION:
Before assigning the amounts to session "Sales and Warehouse Order Invoice Lines" (cisli2545m000), the amounts are rounded
according to the invoicing currency. A check is inserted to perform this only in case the price type is 'Commercial Price".

Solution: 130098
SITUATION IDENTIFIED IN:
"Match/Approve purchase invoices" (tfacp2107s000)
SITUATION DESCRIPTION:
The problem occurs when destination sales tax is applicable in the common parameters and an invoice related to orders is
entered with on header level an expensed tax code If not any orderline is matched but the entire amount is posted as costs
in tfacp1133s000 to a ledger account with integration's to for example project, the total cost posted as an integration is
the amount without VAT however the vat is expensed. This creates a difference between Finance and Project for the
expensed VAT amount.
SOLUTION DESCRIPTION:
The handling is as follows:
In case of an expensed vat with an invoice related to orders and no match is done then if the entire amount is added as a
cost, Baan is posting all expensed VAT to the cost account. In general Baan is posting all vat to the Tax Variance account in
case of an invoice related to order. Now in case a cost account with integrations is used Baan should also post the VAT to the
tax variance account. If the total expensed vat should also be posted to the integrations, a cost invoice should be created.

Solution: 130109
SITUATION IDENTIFIED IN:
"Ledger Accounts By Business Partner Group" (tfacr0111m000)
SITUATION DESCRIPTION:
The session does not allow using the Same Ledger Account for more than one time even though it is not defined as Control
account
SOLUTION DESCRIPTION:
Now the Same General Ledger can be used more than once if not defined as a Control Account

Solution: 130115
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
Enter a sales order (tdsls4100s000). Change the order type so the BP/Order type combination triggers input control. The field
"Sales Office" (tdsls400.cofc) is in the Sales Input Control fields (tdsls0195m000). The user is not automatically taken to
the Sales Office field, the Order Lines session (tdsls4101s000) will not open and user seems stuck on last form.
SOLUTION DESCRIPTION:
The above situation happens because after the input control is triggered (after changing the Sales Order Type) the field "Sales Office" is not visited
again. When the Sales Office field is not empty it will now not be necessary to visit this field again. The Order Lines session (tdsls4101s000) will
automatically open when all other Sales Input Control fields are visited.

Solution: 130120
SITUATION IDENTIFIED IN:
"Maintain Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Calculation and the posting of VAT are wrong. Wrong VAT code is picked up during Receipt Transaction with Discount.
SOLUTION DESCRIPTION:
The system will now pick up the correct VAT code and so the calculation and posting of VAT will be correct during
Receipt Transaction with Discount.

Solution: 130121
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2102s000)
SITUATION DESCRIPTION:
1. A requisition line without a specified item is submitted for multiple approvers.
2. The very first approver does not populate the item.
3. The item-related fields are disabled for all subsequent approvers.
4. Due to this it is impossible to convert the requisition to a Purchase Order
SOLUTION DESCRIPTION:
When the requisition line is created with out a specific item, any approver can fill the item and approve the requisition.

Solution: 130125
SITUATION IDENTIFIED IN:
"Maintain and Confirm Backorders" (tdsls4125m000)
"Release to Warehousing" (tdsls4501m140)
"Release to Invoicing" (tdsls4501m130)
SITUATION DESCRIPTION:
When 'new group' button is used to search for an order in session "Maintain and Confirm Backorders" (tdsls4125m000) the
message "Sold-to-Business Partner of Line does not match with Sold-to-Business Partner of Header" is displayed.
This also happens in session "Release to Invoicing" (tdsls4501m130) and "Release to Warehousing" (tdsls4501m140)
SOLUTION DESCRIPTION:
When searching for a Sales Order no incorrect messages are shown.

Solution: 130127
SITUATION IDENTIFIED IN:
"Remove Confirmed Shipments" (whinh4250m000)
SITUATION DESCRIPTION:
Run session "Remove Confirmed Shipments" (whinh4275m000) with checkbox "Print error report" checked. When one of the
shipments in the range cannot be removed the job fails in a runtime error whereas a report should be printed.
SOLUTION DESCRIPTION:
When an error occurs in session "Remove Confirmed Shipments" (whinh4275m000) when this session is placed in a job, the
functionality is as follows:
1. The checkbox "Print error report" is checked on session "Remove Confirmed Shipments" (whinh4275m000): the job is
completed and an error report is printed.
2. The checkbox "Print error report" is not checked on session "Remove Confirmed Shipments" (whinh4275m000): the job
fails in a runtime error.

Solution: 130145
SITUATION IDENTIFIED IN:
"Sales-Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
The option "After Sales" in the specific menu does not function correct. It starts an empty browser without menu.
SOLUTION DESCRIPTION:
The option "After Sales" in the specific menu works correctly. The "Service Control" menu is started.

Solution: 130154
SITUATION IDENTIFIED IN:
"Compose/Post/Print Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Page number is not correct, if you take the copy of the original invoice.
SOLUTION DESCRIPTION:
Page number is printing correctly, while printing the copy of the original invoice.

Solution: 130155
SITUATION IDENTIFIED IN:
"Cycle Counting/Adjustment Order Lines" (whinh5501m000)
SITUATION DESCRIPTION:
Adjustment Order Lines (whinh5101s000) can be made for project items for which the project status is 'closed'.
SOLUTION DESCRIPTION:
When on an Adjustment Order Line a project item is entered for which the project status is 'closed', the following error
message is given: "Project not allowed because the project has the closed status."
The line cannot be saved. The same happens for project items for which the project status is 'free'.

Solution: 130157
SITUATION IDENTIFIED IN:
"Business Partners by Project" (tppdm6101s000)
SITUATION DESCRIPTION:
When a Business Partner by project is created, the currency rate is taken automatically from the exchange rate type defined
in the parameters as Default Exchange Rate Type for Budget.
SOLUTION DESCRIPTION:
When a Business Partner by project is created, the currency rate is now taken from the exchange rate type defined in the
Invoice-To Business Partner role.
Also the default currency comes from that role.

Solution: 130167
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
SITUATION DESCRIPTION:
Technical solution when external applications are used. The session type of "Sales Order Lines" (tdsls4501m000) is
"Maintain" but should be "Display".
SOLUTION DESCRIPTION:
Changed the session type from "Maintain" to "Display"

Solution: 130201
SITUATION IDENTIFIED IN:
"Post Sales/Warehouse Order Invoice Data" (cisli3200m000)
SITUATION DESCRIPTION:
Two Problems:
1. In a single currency system, wrong rate is filled in the General Ledger for the Integration transactions "Cost of Goods
sold"
2. When a single order has many lines (> 15,000) then fatal error "Out of range" occurs while posting the invoice.
SOLUTION DESCRIPTION:
The rates are filled correctly in the General Ledger. Also the Fatal Error Out of Range does not occur

Solution: 157147
SITUATION IDENTIFIED IN:
"Resource Master Plan" (cprmp3501m000)
SITUATION DESCRIPTION:
When resource utilization existed because of existing shop floor orders for past/historical periods (ie. periods that have a
finish date that is less than the current date), this utilization was not considered during the calculation of the resource master
plan.
SOLUTION DESCRIPTION:
When resource utilization exists because of existing shop floor control (SFC) orders for past/historical periods (ie. periods that
have a finish date that is less than the current date), this utilization is considered in the calculation of the resource master
plan. The SFC resource utilization for past periods appears in the current period (ie. the first period having a finish date
greater than the current date) of the resource master plan.

Solution: 157178
SITUATION IDENTIFIED IN:
"Receipts via DDC" (whinh3520b000)
SITUATION DESCRIPTION:
The user is unable to compile the script used for receiving via DDC.
SOLUTION DESCRIPTION:
Solution 122071 changes needed to be added to DDC script. This eliminates an unresolved reference.

Solution: 157494
SITUATION IDENTIFIED IN:
"Select Data for Production Planning Board" (tisfc1120m000)
SITUATION DESCRIPTION:
When starting session 'Select Data for Production Planning Board' (tisfc1120m000) by itself, not zooming from session
'Production Orders' (tisfc0501m000), the production order range was not defaulting to the saved values.
Some operations on the planning board were displayed several times after refreshing or changing the selection of the
planning board.
SOLUTION DESCRIPTION:
When starting session 'Select Data for Production Planning Board' (tisfc1120m000) by itself, not zooming from session
'Production Orders' (tisfc0501m000), the production order range is now defaulting to the saved values.
Operations are not shown several times anymore after refreshing or changing the selection of the planning board.

Solution: 157501
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
When completing production orders, Production/Price Variance currency amounts of zero were being posted to finance
although these transactions should be suppressed.
SOLUTION DESCRIPTION:
Production/Price Variance transactions of currency amount zero are no longer posted to finance.

Solution: 157576
SITUATION IDENTIFIED IN:
"Print Unbalanced Legder Accounts during Year End" (tfgld6403m000)
SITUATION DESCRIPTION:
The session tfgld6403m000 (Print Unbalanced Ledger Accounts during Year End), available in Baan IV is very useful in
analysing the cause of problems reported during the year end procedures is not available in Baan V.
SOLUTION DESCRIPTION:
The session has been ported from Baan IV to Baan V. Functionality has been added in Baan V to compare the Opening
Balances tables as well.

Solution: 157751
SITUATION IDENTIFIED IN:
"Validate Product Variants" (tipcf5200m000)
SITUATION DESCRIPTION:
When validating EDI variants having option values that are to be changed by constraint logic, the changed options are not
reported to the user, and the variant is incorrectly validated.
SOLUTION DESCRIPTION:
Now when validating EDI variants with option values that are to be changed by constraint logic, the option values that have
to be changed are reported to the user and the variant is not validated.

Solution: 157754
SITUATION IDENTIFIED IN:
"Aggregate Channel, Plan & Orders" (cppat2210m000)
SITUATION DESCRIPTION:
Assembly part demand, Dependent Material demand, Dependent Distribution demand and distribution customer orders were
not aggregated from child to family parent based on aggregation relationships.
SOLUTION DESCRIPTION:
Assembly part demand, Dependent Material demand, Dependent Distribution demand and distribution customer orders will
be aggregated based on the aggregation relationships defined in Aggregation Relationships (tibom2510m000)

Solution: 157851
SITUATION IDENTIFIED IN:
"Reprint Journal Report" (tfgld1410m000)
SITUATION DESCRIPTION:
When running the session in an archive company, the error message 'No Data Within Selection' was always given.
SOLUTION DESCRIPTION:
A new form field 'Original Company' has now been added to the session so that data can be found when running the session
in an archive company. When running the session in an archive company, this field needs to be filled with the live company
number where the transaction originated.

Solution: 157949
SITUATION IDENTIFIED IN:
"Print Sales Order Acknowledgment" (tdsls4401m000)
SITUATION DESCRIPTION:
When printing the sales order acknowledgement with the flag "Option Descriptions" selected, the process run time is taking
much too long.
SOLUTION DESCRIPTION:
Now when printing the sales order acknowledgement with the flag "Option Descriptions" selected, the process run time has
been reduced.

Solution: 157952
SITUATION IDENTIFIED IN:
"Delete WIP Transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
When deleting Work in Process (WIP) transactions using deleting method 'horizon' the session performance was not good.
SOLUTION DESCRIPTION:
When deleting WIP by horizon, the program checks to make sure all the transactions for the project/order are within the
year/period range entered by the user. If any transactions for the project/order lie outside the user entered period range then
the transactions related to it cannot be deleted. This check has been changed to work more efficiently.
It is recommended that deleting method 'project, order' be used whenever possible as this will be faster than using deleting
method by 'horizon'.

Solution: 157961
SITUATION IDENTIFIED IN:
"Print Finalized Transactions by Ledger Account" (tfgld1406m000)
"Reprint Journal Report" (tfgld1410m000)
"Print Finalized Transactions by Date" (tfgld1440m000)
"Print Journal" (tfgld1441m000)
SITUATION DESCRIPTION:
The Reference column on the report was not wide enough to display the entire reference text.
SOLUTION DESCRIPTION:
The Reference column has been widened so all of the reference text will be displayed. This problem also existed in other
sessions. The sessions which have been corrected are listed above this section.

Solution: 157973
SITUATION IDENTIFIED IN:
"Intergroup Transactions" (tfgld2102s000)
SITUATION DESCRIPTION:
If journal transaction changes from debit to credit the intergroup transaction doesn't change automatically. Moreover, error
message doesn't appear and transaction can be finalized. The remaining amount is calculated incorrectly and that's why error
doesn't occur when original transaction changes from debit to credit.
SOLUTION DESCRIPTION:
The calculation of the remaining amount has been changed. If original transaction changes from debit to credit or from credit
to debit intergroup transaction has to be changed as well. Otherwise, error message appears. The debit/credit field of
intergroup transaction has been changed from Display field to Input field. Now user doesn't have to delete and insert new
intergroup transaction if the posting of the original transaction was changed.

Solution: 157979
SITUATION IDENTIFIED IN:
"Rebuild Ledger / Dimension History of Period" (tfgld3206m000)
SITUATION DESCRIPTION:
Ledger account history was not being updated correctly for parent accounts. If a ledger account contained both a statutory
and complementary parent, history was only rebuilt for one of the parent accounts. Also in the same case the dual accounting
indicator was sometimes filled incorrectly.
SOLUTION DESCRIPTION:
The program has been changed so that: #1 dual accounting indicator is always filled correctly
#2 processing will now be done for both parent accounts and their parents as well all the way up until
the highest level.

Solution: 157983
SITUATION IDENTIFIED IN:
"Background Process For Real-Time Document Level Update" (tfgld1201s000)
"Background Process For End Of Session Update" (tfgld1203s000)
"Termination Mode Update (Background)" (tfgld1201s000)
"Rebuild Opening Balance/History from Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
History tables are updated in transaction currency although the currency analysis of the ledger account is "not required".
According to the table field help text, when a ledger account has currency analysis 'not required' history is only stored in
home currency.
SOLUTION DESCRIPTION:
The programs that update ledger account and dimension history have been modified to store history only in home currency if
the ledger account has currency analysis 'not required'. This will help reduce the size of history tables and improve the
performance of sessions that use history information.

Solution: 157985
SITUATION IDENTIFIED IN:
"Standard Subcontracting Items" (tppdm0513)
SITUATION DESCRIPTION:
When adding a new standard subcontracting item and then deleting it, the same item in the general item data was not
removed.
SOLUTION DESCRIPTION:
Now when adding a new standard subcontracting item and then deleting it, the same item in the general item data is
removed.

Solution: 157994
SITUATION IDENTIFIED IN:
"Copy Sales Budget to Demand Forecast" (cpdsp1280m000)
SITUATION DESCRIPTION:
The session "Copy Sales Budget to Demand Forecast" (cpdsp1280m00), takes relatively long time even for a small range of
items. The program was reading the table Sort Code (tdsst094), a number of times, thus leading to a performance problem.
SOLUTION DESCRIPTION:
The table Sort Code (tdsst094), is read only once for a single run, as the sort code never changes during the run. This
will lead to a performance improvement in the session "Copy Sales Budget to Demand Forecast".

Solution: 158006
SITUATION IDENTIFIED IN:
"Display Ledger History - Dim Type Wise Distribution" (tfgld3507m000)
SITUATION DESCRIPTION:
When a ledger account was linked to a multi-dimension budget, and one drilled down from session tfgld3501s000 (Ledger
History) to tfgld3507m000 (Distribution by Dimension type for Ledger Account) one could only see data for one of the
ledger's dimensions. Even though there was data for other dimensions, it was not displayed. This generally happened when
one changed the default selection range values in the session tfgld3503s000 (Change Default Values).
SOLUTION DESCRIPTION:
This problem happened because of incorrect usage of memory within the program. Each time the defaults were changed more
memory was used up. Also, when the budget data was read the dimension type for which it was read was incorrect.
Therefore, between the two problems the session sometimes failed to show any data for a dimension type. Both problems
have been corrected.

Solution: 158011
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
When configuring a new product variant with inputs being determined by before input constraints, an incorrect message is
displayed for each feature. The message is "Default option value is __; Overwrite option value?". This should only be
displayed when a previous option value exists.
SOLUTION DESCRIPTION:
A new product variant can now be configured with inputs coming from before input constraints without any default
override message.

Solution: 158033
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Orders" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating a product variant structure for sales order, the session run time still takes too long.
SOLUTION DESCRIPTION:
Additional performance improvements have been made when generating a product variant structure for sales order.

Solution: 158036
SITUATION IDENTIFIED IN:
"Print Sales Orders" (tdsls4405m000)
SITUATION DESCRIPTION:
The amounts shown in the report aren't always correct for a certain combination of parameters and if the amount is based on
either 'Delivered quantity' or 'Outstanding quantity' and backorders exist for an order line.
SOLUTION DESCRIPTION:
When the amount is based on 'Delivered quantity' or 'Outstanding quantity' and a backorder exist for the order line the
amounts displayed in the report are correct.
Solution: 158038
SITUATION IDENTIFIED IN:
"Print Mapping Information" (ecedi5415m000)
SITUATION DESCRIPTION:
When printing mapping information for EDI conversion setups; certain overhead fields are being printed with the wrong
positions or not being printed at all on the Print Mapping Information Report.
SOLUTION DESCRIPTION:
The Print Mapping Information script has been modified to print all of the overhead fields in each level and in the correct
positions.

Solution: 158056
SITUATION IDENTIFIED IN:
"Generate Network Planning" (tipcs4210m000)
SITUATION DESCRIPTION:
When generating network planning with routing parameter 'Used Calendar Type' set to 'Work Center', and different work centers
with different calendars are assigned to the activities, the start dates and end dates are shown not in sync between the
activities.
SOLUTION DESCRIPTION:
The generating network planning session is modified to always use the company calendar, thus to allign the start and finish
dates between the activities.

Solution: 158081
SITUATION IDENTIFIED IN:
"Process Import/Export Statistics" (tccom7271m000)
SITUATION DESCRIPTION:
When printing the report 'Import/Export Statistics (Sequential File)', the item weight is converted from the weight unit in
the parameters to the unit of the item, e.g., from kg to g. If the resulting number was bigger than 9999999.999 (7+3), the
weight was shown as '############'.
SOLUTION DESCRIPTION:
The field size for the weight was too small and has been extented. It used to allow numbers up to 7+3 digits and can now display up to 8+4 digits. This
field size should be sufficient for most cases. As the line of a report is limited to 254 characters, which has been reached with this extension, the field
cannot be enlarged more without reducing the size of other fields.

Solution: 158095
SITUATION IDENTIFIED IN:
"Print Production Orders on Priority" (tisfc1410m000)
SITUATION DESCRIPTION:
When zooming to this session, e.g., via 'Production Planning Overview' (tisfc1507m000), the production order range was
always defaulting back to the imported production order, which made it impossible to print a range.
SOLUTION DESCRIPTION:
When zooming to this session, e.g., via 'Production Planning Overview' (tisfc1507m000), the production order range is now
defaulting once to the imported production order, but can be changed afterwards to a range, which can then also be printed.

Solution: 158098
SITUATION IDENTIFIED IN:
"Outbound Order Lines" (whinh2520m000)
SITUATION DESCRIPTION:
In case of warehouse transfer orders with no shipment procedures, when generate outbound advice is done, the confirm
shipment is done automatically. If there is shortage on outbound quantity during generation of outbound advice, the error
messages are not displayed.
SOLUTION DESCRIPTION:
Now, the error messages are not suppressed. When there is a
shortage on outbound quantity, the error messages are displayed.

Solution: 158100
SITUATION IDENTIFIED IN:
"Production Planning Board" (tisfc1120m000)
SITUATION DESCRIPTION:
The error message, "Plan board cannot be loaded due to fatal error," is generated in the Planning Board (tisfc1120m000)
session, when an availability type is defined for a work center calendar (with ROU Parameters 'Used Calendar Type' set to
'Work Center' and 'Availability Type' set to that type) and when the type is not defined for the company's calendar. The
session incorrectly processes production orders using the company's calendar, and not the work center calendar.
SOLUTION DESCRIPTION:
The session has been corrected and now the proper work center calendar is used when running the Planning Board session
with ROU Parameter "Used Calendar Type" set to "Work Center".

Solution: 158104
SITUATION IDENTIFIED IN:
"Rebuild Ledger/Dim History - Final/Non Final Trans." (tfgld3203m000)
SITUATION DESCRIPTION:
When using 'Rebuild Ledger/Dim History - Final/Non Final Trans' session (tfgld3203m000), the session does not support the
rebuilding of the general ledger history for individual periods types (fiscal and reporting) independently of each other's period
status. If a fiscal period(s) is 'finally' closed and the reporting period is open - the session does not allow the individual
rebuilding of only the reporting period.
SOLUTION DESCRIPTION:
The 'Rebuild Ledger/Dim History - Final/Non Final Trans" session (tfgld3203m000) has been enhanced to support the
individual rebuilding of fiscal or reporting periods independent of their closing status.

Solution: 158110
SITUATION IDENTIFIED IN:
"Installation" (ttiex1289m000)
SITUATION DESCRIPTION:
install6.2 is hanging on AIX4.3 OS platform
SOLUTION DESCRIPTION:
Verify that the files that are having a manual chmod done to them exist before processing them.

Solution: 158115
SITUATION IDENTIFIED IN:
"Query Data" (ttadv3580m000)
SITUATION DESCRIPTION:
The wrong query is displayed in Query by Easy SQL subsession (ttadv3181m000)
SOLUTION DESCRIPTION:
The correct query is retrieved by making sure that control is not returned to the main session until the subsession is
retrieved.

Solution: 158120
SITUATION IDENTIFIED IN:
"Generate Demand Forecast and Inventory Plan" (cpdsp1210m000)
SITUATION DESCRIPTION:
When the end date of the current period is one day after the current date and the scenario is a weekly period, the forecast is
not calculated for the current period and thus the subsequent forecasts are calculated incorrectly.
SOLUTION DESCRIPTION:
The forecast will be calculated starting with the current period and thus the subsequent forecasts will be calculated correctly.

Solution: 158121
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
After installing solution 157433, the user may need to clean up duplicate commission lines.
This correction program will facilitate such a clean-up. Once the correction program has been run. The user will then
have to calculate the commissions again using session tdcms0240m000 Calculate Commissions/Rebates.
SOLUTION DESCRIPTION:
This correction program will allow the user to run in non-update mode. The program will print or display a report which will
inform the user of the updates which will take place. The user can review the report and decide if they indeed want to run
in update mode.
A mistake was made and the label for the last form field was not included in this solution for the German language.
See solution 158506.
See solution 159776 (helptext fix).

Solution: 158127
SITUATION IDENTIFIED IN:
"Maintain Sales Orders" (tdsls4101m000)
SITUATION DESCRIPTION:
When a process tried to create a new message queue for calculating third party tax, it was possible for the message queue ID
that was returned to be identical to a message queue ID in use by another process. This caused the process that originally
had this message queue ID to hang.
SOLUTION DESCRIPTION:
A check has been introduced so a process will not use a
message queue ID that is already in use by another process.

Solution: 158135
SITUATION IDENTIFIED IN:
"Automatic Balancing of Profit and Loss Accounts" (tfgld6202m000)
SITUATION DESCRIPTION:
The session generates an error message, showing that Ledger Account is not in balance, while actually Ledger Account is
in balance. This problem occurs because Opening Balances distributed among Dimensions have not been considered during
checking of Ledger Account.
The session generates a float exception error. The reason why this error occurs is a division by zero during calculation of
currency rate.
SOLUTION DESCRIPTION:
Opening Balances distributed among Dimensions have been included in the checking of Ledger Account.
Calculation of currency rate has been changed to exclude situation of division be zero.

Solution: 158139
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
Item receipt surcharges are posted incorrectly resulting in a positive Work-in-Process under the following conditions:
- The production order was created before the installation of solution 157837 (NB B50_b and B50_c only)
- Item receipt surcharges are added to the ordered item (after order completion and prior to closing).
- The Reset Production-Order Status and the Close Production Orders sessions are then run for the order.
SOLUTION DESCRIPTION:
The session has been corrected and now production orders created with the above conditions are reset and re-closed with
item receipt surcharges posted properly.

Solution: 158151
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When simulating orders, via cprrp1210m000 session, a float exception condition occurs causing the process to terminate (ie. a
fatal error). One condition that can cause a float exception error is division by zero. The float exception error occurs in
this process when trying to plan a shop floor order for an item with the following conditions:
- the item is using a routing with more than one operation
- the first operation has a work center with a Critical Capacity Type as man critical (found in the Work Center session, tirou0101s000)
- the second operation has a work center with a Critical Capacity Type as machine critical (found in the Work Center session,
tirou0101s000) and the man occupation field for the operation set to zero (found on the Routing Operations session, tirou1102s000)
When this situation exists, the system is using the information from the first operation to calculate the production run time
for the second operation. Since the two operations are different (one is man critical and the other is machine critical), the
calculation for the production run times are slightly different (ie. the calculation for the man critical operation uses the
man to machine ratio value in determining the production run time). Since the man occupation of the second operation is
zero, the man to machine ratio value is zero causing a float exception condition to be raised when calculating the production
run time for the second operation.
SOLUTION DESCRIPTION:
When simulating orders for an item with the conditions as described above, the process is changed to verify that the correct work center information is
being used to calculate the production run time for each operation. If the process does not have the correct work center information for the current
operation, the work center information for that operation is read so that the production run time is calculated correctly. By calculating the production run time with the correct work center information, the condition which causes the float exception error to occur is avoided.

Solution: 158154
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
System allows the receipt of more quantity than was shipped when performing an item-transfer.
SOLUTION DESCRIPTION:
System changed to ensure receipt quantity cannot exceed the shipment quantity.

Solution: 158166
SITUATION IDENTIFIED IN:
"Print Intergroup Transactions" (tfgld2402m000)
SITUATION DESCRIPTION:
The Ledger Account printed on the report of session Print Intergroup Interim Transactions (tfgld2402m000) is not correct.
The ledger account printed on the report is the Intergroup Account defined in the Intergroup Relations. This should be the
Ledger Account for the Target company.
SOLUTION DESCRIPTION:
The above mentioned have been changed.
Printing the Intergroup ledger account on the report is non-information.
Also, the title of the column in the report has been altered to reflect the usage of the correct ledger account.

Solution: 158168
SITUATION IDENTIFIED IN:
"Global Selection of Batches for Finalization" (tfgld1210m000)
SITUATION DESCRIPTION:
If a user runs the session tfgld1210m000 (Global Selection of Batches for Finalization) and aborts at the device acceptance
screen and then attempts to finalize the created run number in tfgld1111s000 "Select Batches for Finalization", the batch or
batches attached to the run number created from the global finalization will show as selected i.e. the check box "Selected
for Finalization" against these batches will be checked. But if one tabs through the check boxes without doing anything these
boxes get un-checked even though the batches are still selected for finalization in that run number.
SOLUTION DESCRIPTION:
This problem occurred because when placing the selected batches within a run, the table field to
indicate the batch is 'selected' was not changed to 'yes' by the global finalization session.
Thus when a user tabbed thorugh the form, the displayed value got reset to the value in the table. To correct this problem, now when attaching batches
to a run number in the global finalization process the batches will now have the 'selected' field = 'yes'. Thus the flag will correctly display when
looking/tabbing through the screen containing the batches selected for finalization in (tfgld1111s000) "Select Batches For Finalization"

Solution: 158174
SITUATION IDENTIFIED IN:
"Baan Open World" (Baan 5 BOIs)
SITUATION DESCRIPTION:
When data is sent to Baan through Open World, item fields are not aligned correctly according to the segmentation of the
fields.
SOLUTION DESCRIPTION:
Data sent to Baan via Open World is now aligned correctly by segment for item fields.

Solution: 158180
SITUATION IDENTIFIED IN:
"GL Account Matching- Automatic" (tfgld1216m000)
"Close Year" (tfgld6203m000)
SITUATION DESCRIPTION:
When running the session "GL Account Matching Automatic" (tfgld1216m000), it would abort with an error message if a
complementary matching ledger account was not defined in the company parameters even though the company does not use
Complementary ledger accounts.
When running the session (tfgld6203m000) "Close Year", it would give an error message if the complementary currency
translation account was not filled in the company parameters even though the company does not use Complementary ledger
accounts.
SOLUTION DESCRIPTION:
Use of complementary accounts is an option used for accounting for management information. It is not mandatory to use complementary accounts
so the error checks should only be done if complementary accounts are used.
The error checks for complementary ledger accounts from the company parameters are now only done if there are complementary accounts defined in the chart of accounts that will be processed by the session.

Solution: 158192
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When simulating orders for generic item, the program is aborting with a fatal error, which has been determined to be
"Transaction on, cannot continue". Program aborts to an icon which must be killed via a shell session.
SOLUTION DESCRIPTION:
The simulate orders session can now be run for generic items without a fatal error.

Solution: 158193
SITUATION IDENTIFIED IN:
"Delete WIP Transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
WIP transactions are left behind when archiving shopfloor production orders. This is inconvenient and causes excess storage
of unnecessary data.
SOLUTION DESCRIPTION:
WIP transactions for archived shopfloor production orders are now deleted using the session "Delete WIP Transactions by
Project/Order(tcfin1200m000)".

Solution: 158195
SITUATION IDENTIFIED IN:
"Print Trial Balance" (tfgld3402m000)
"Print Trial Balance by 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:
Session and form field help texts were not present in some cases and inadequate in some cases. This caused confusion about
the functionality of some of the form options and the report output.
SOLUTION DESCRIPTION:
For the trial balance sessions, field and session help texts have been refined/added.

Solution: 158203
SITUATION IDENTIFIED IN:
"Release Production Orders" (tisfc0204m000)
SITUATION DESCRIPTION:
When releasing a production order, the allocation dates in the session "Planned Inventory Transactions by Order
(whinp1501m000)" are made blank. This is incorrect, and therefore causes incorrect allocation times.
SOLUTION DESCRIPTION:
The production start date on the production order was made available to calculate the allocation dates so they are now
correct.

Solution: 158207
SITUATION IDENTIFIED IN:
"Maintain Commission Calculated by Order" (tdcms0150m000)
SITUATION DESCRIPTION:
A deleted commission appears again as calculated
SOLUTION DESCRIPTION:
Created user help text to make this process more user friendly.

Solution: 158211
SITUATION IDENTIFIED IN:
"Tool Numbers by Tool Type" (titrp0502m000)
SITUATION DESCRIPTION:
When copying a tool number that has text linked to it, the new tool number was linked to the original text. This resulted
that changing the text for one tool number also changed the text of the other tool number.
SOLUTION DESCRIPTION:
When copying a tool number that has text linked to it, its text is now also copied and the new tool number linked to it. This
makes sure that each tool number has its unique text.

Solution: 158225
SITUATION IDENTIFIED IN:
"Constraints by Generic Item" (tipcf2110m000)
SITUATION DESCRIPTION:
When zooming from a constraint field into maintaining constraints by generic items, automatically a constraint code ID is made
and if user decides not to use that constraint ID, then the constraint ID table is full of unused IDs.
SOLUTION DESCRIPTION:
Now when zooming from a constraint field into maintaining constraints by generic items, the user is asked whether to make
a new constraint ID or not.

Solution: 158228
SITUATION IDENTIFIED IN:
"Time Phased Planning Overview" (cprrp0520m000)
SITUATION DESCRIPTION:
The cost price of the item is not shown on the form for "Time Phased Planning Overview".
SOLUTION DESCRIPTION:
The cost price and currency are shown in the form "Time Phased Planning Overview".

Solution: 158230
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst1501m000)
SITUATION DESCRIPTION:
When adding materials to a production order, which has been closed and reset, item warehouse allocated inventory is not
updated.
SOLUTION DESCRIPTION:
Item warehouse allocated inventory is now updated correctly when adding materials to a reset production order.

Solution: 158233
SITUATION IDENTIFIED IN:
"Nonfinalized Transaction Lines" (tfgld1508m000)
"Finalized Transaction Lines" (tfgld1509m000)
"Nonfinalized Transaction" (tfgld3508m000)
"Finalized Transaction" (tfgld3509m000)
SITUATION DESCRIPTION:
The text button was disabled on some forms and enabled in read-write mode on others.
SOLUTION DESCRIPTION:
The text buttons that were disabled have been enabled. Since all the sessions in this solution are display only sessions, all
text buttons have been set to read only mode.

Solution: 158244
SITUATION IDENTIFIED IN:
"Print Chart of Accounts" (tfgld0408m000)
SITUATION DESCRIPTION:
The headings for the columns "Currency Analysis" and "Fixed Asset Integration" are printing too high on the report. They
are printing above the box set up for the column headings.
SOLUTION DESCRIPTION:
The text for the column headings for "Currency Analysis" and "Fixed Asset Integration" have been moved so that they will
print within the box set up for the column headings.

Solution: 158247
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
When reading in an EDI sales order acknowledgement(855) the warehouse field on the Direct Delivery purchase order line is
updated. It should not be updated since this is a direct delivery purchase order.
SOLUTION DESCRIPTION:
The EDI script has been modified to not update or fill the warehouse field on a direct delivery purchase order. If the
purchase order is direct delivery then the purchase order lines warehouse field should remain blank.

Solution: 158249
SITUATION IDENTIFIED IN:
"Print Non-Finalized Transactions" (tfgld1401m000)
SITUATION DESCRIPTION:
When running the session in a company that does not use reporting periods, the report header printed a reporting year.
SOLUTION DESCRIPTION:
The report header has been modified so that no reporting year or period will be printed in companies where reporting periods
are not used.

Solution: 158254
SITUATION IDENTIFIED IN:
"Rebuild Sublevels" (tffbs1204s000)
SITUATION DESCRIPTION:
After running session tffbs1204s000 "Rebuild Sublevels" the last period of budget of dimension with sublevel greater then 0
was not correct.
SOLUTION DESCRIPTION:
Now session tffbs1204s000 "Rebuild Sublevels" properly rebuilds sublevels.

Solution: 158258
SITUATION IDENTIFIED IN:
"Module Planning" (tipcs4120s000)
SITUATION DESCRIPTION:
When adding a new module, the new module number defaults to already existing numbers.
SOLUTION DESCRIPTION:
When adding a new module, the new module number is now defaulting to the next available number.

Solution: 158259
SITUATION IDENTIFIED IN:
"Process NA Tax Provider Adjustments" (tccom6214s000)
SITUATION DESCRIPTION:
When zooming from the session "Tax Provider Calculation Utility" to the session "Process NA Tax Provider Adjustments",
the same record can be processed more than once without error.
SOLUTION DESCRIPTION:
Now after the user has processed the adjustment, they are brought back to the main session. This insures that the user does
not accidentally process the same adjustment more than one time.

Solution: 158260
SITUATION IDENTIFIED IN:
"Material Transactions to be Invoiced" (tppin4457m000)
SITUATION DESCRIPTION:
Maximum number of digits for sales price and amount on the forms in several project invoicing sessions like "Maintain
Material Transactions to be Invoiced" are different from some production control sessions like "Material costs".
SOLUTION DESCRIPTION:
Changed the display format on several forms and reports for the sales price to 11 digits and 2 decimals and for the sales
amount to 12 digits and 2 decimals.

Solution: 158261
SITUATION IDENTIFIED IN:
"Planned Orders" (cprrp1100s000)
SITUATION DESCRIPTION:
When creating a lead-time in a planned order, which is different than based on the routing, the start or end date was being
changed even if the order was firm planned. This was contradicting to the helptext.
SOLUTION DESCRIPTION:
When backward planning, the start date has to change to be reflective of the routing, while when forward planning an order,
the end date has to change. This is to allow for time-phased planning for its components. The helptext has been changed to
explain this.

Solution: 158263
SITUATION IDENTIFIED IN:
"Archive/Purge Finance Transaction" (tfgld6205m000)
SITUATION DESCRIPTION:
When running the session, a rollback segment error could occur because a large volume of data was being processed without
updating the database as frequently as necessary.
SOLUTION DESCRIPTION:
The program has been changed to update the database more frequently so that rollback segment errors do not occur.

Solution: 158266
SITUATION IDENTIFIED IN:
"Conversion Factors" (tcibd0103m000)
SITUATION DESCRIPTION:
When adding a new conversion factor to an item with inventory, the user cannot change or delete this newly added conversion
factor, even though there have been no transactions on this conversion factor.
SOLUTION DESCRIPTION:
New conversion factors can now be added to an item with inventory and then changed or deleted, if there is no inventory
structure on the item and unit combination.

Solution: 158270
SITUATION IDENTIFIED IN:
"Select Device" (ttstpsplopen)
SITUATION DESCRIPTION:
Report description is being saved with Save Default and then restored when pressing GetDefaults.
SOLUTION DESCRIPTION:
After loading defaults restore the original report description.

Solution: 158271
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
1- When configuring a new variant and the remaing features on the screen are changed from input to display via the
constraints, the input focus is lost.
2- When configuring a variant and defaults are set in display features, then when navigating to the next record set and then
back to the previous record set, the defaults are lost.
SOLUTION DESCRIPTION:
1- Now when configuring a new variant and the remaining features on the screen are changed from input to display via the
constraints, the input focus is transferred back to the first input feature on the screen.
2- Now when defaults are set in display fields in the configurator, navigating through the record sets will not cause the
display defaults to be lost.

Solution: 158284
SITUATION IDENTIFIED IN:
"Validate Product Variants" (tipcf5200m000)
SITUATION DESCRIPTION:
When validating product variants in session "Validate Product Variants", the variant is validated even though error messages
are reported.
SOLUTION DESCRIPTION:
Now when validating product variants in session "Validate Product Variants", the variant will not be validated if any error
messages are reported.

Solution: 158286
SITUATION IDENTIFIED IN:
"Report Library" (ttstprepdll)
SITUATION DESCRIPTION:
Errors in reports with layouts set to mutlicolons vertical
SOLUTION DESCRIPTION:
If a report isn't sorted the variable r.reccount is never incremented and we cannot split the records over multiple columns
properly. Therefore, if the report isn't sorted we now print all records into a single column.

Solution: 158304
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst1501m000)
SITUATION DESCRIPTION:
The item description field is not displayed for material lists in the "Materials to Issue for Production Order" and "Estimated
Materials" sessions.
SOLUTION DESCRIPTION:
The Item Description field has been added and is now displayed in these sessions.

Solution: 158305
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2420m000)
SITUATION DESCRIPTION:
When printing a commission invoice. The total field for Total Net Amount is missing.
SOLUTION DESCRIPTION:
Added the field Total Net Amount to the report.

Solution: 158307
SITUATION IDENTIFIED IN:
"Restart Finalization Run" (tfgld1119s000)
SITUATION DESCRIPTION:
After restarting an interrupted finalization run, the finalization run status was left at 'errors' even though all the transactions
within the run finalized successfully.
SOLUTION DESCRIPTION:
The program has been modified so that the finalization status will be put to 'finalized successfully' if all transactions get
finalized.

Solution: 158309
SITUATION IDENTIFIED IN:
"Functions for logging" (tudlllogging)
SITUATION DESCRIPTION:
Characters are garbled when converting multibyte with exchange.
SOLUTION DESCRIPTION:
Altered the logging function so that it uses multibyte strings properly.

Solution: 158310
SITUATION IDENTIFIED IN:
"Generic Price List Descriptions" (tipcf4102s000)
SITUATION DESCRIPTION:
When printing the annex for sales orders and quotations, the variant pricing structure descriptions are not printed in the
customer's language.
SOLUTION DESCRIPTION:
Now when printing the annex for sales orders and quotations, the variant pricing structure descriptions are printed in the
customer's language.

Solution: 158311
SITUATION IDENTIFIED IN:
"Print Trial Balance - Dimension Code/Ledger Accounts" (tfgld3406m000)
SITUATION DESCRIPTION:
--Parent level ledger accounts have been included in the "Budget Variances" reports grouped by dimensions. Parent ledger
accounts can not have dimensions and thus they can not have actual amounts linked to a specific dimension. But parent
ledger account can have a budget that is distributed among dimensions. Therefore, on the reports grouped by dimensions,
the variance between actual and budgeted amounts of the parent ledger account is always 100%. Moreover, budgeted amounts
of the parent ledger accounts have been added to the totals thus making budgeted totals incorrect.
--On the form there are fields named "Sublevel from" and "Sublevel to" which are used to enter a range of dimension
sublevels. Dimension sublevels can only be one digit long (0-9) but these form fields were two digits in length which gives
users the impression that these fields are ledger account sublevels.
--The Grand Totals of the report "Budget Variances (Dimension/Ledger Account)" (tfgld340612000) were incorrect.
SOLUTION DESCRIPTION:
--Now parent ledger accounts will not be included in the reports, which are grouped by dimensions. However, actual and
budgeted amounts of the parent level ledger account can be seen and compared using the report "Print Trial Balance"
(tfgld3402m000) that is not grouped by dimensions.
--Form fields for dimension sublevels have been changed to contain one only digit.
--Calculation of the dimension totals have been changed on the report "Budget Variances (Dimension/Ledger Account)"
(tfgld340612000) so that the Grand Totals of the report are correct.

Solution: 158322
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
An Out of Range error (error number 205) occurred when simulating orders in a multi-site environment. This error occurred
because incorrect date values (ie. values that the system could not convert to a correct date) were attempted to be stored in
Planned Order Line table (cprrp110). The date fields where a problem existed were the Order Line Start Date (cprrp110.olsd)
and Order Line Finish Date (cprrp110.olfd) fields.
SOLUTION DESCRIPTION:
When storing the Planned Order Line table (cprrp110) a special check is performed for the invalid
date situation. When the invalid date situation is discovered, the Order Line Start Date and Order Line Finish Date are set to the current date.

Solution: 158328
SITUATION IDENTIFIED IN:
"Plan Item Data" (cprpd1101s000)
SITUATION DESCRIPTION:
In case Maintain Master Plan is no in Plan Item Data (cprpd1101s000), field 'Planning Horizon' is disabled. The value then
should be set equal to the Order Horizon. Having a planning Horizon of less then the order horizon could prevent some
transactions from being seen.
SOLUTION DESCRIPTION:
If Maintain Master Plan is set to no or Order Horizon changed and Maintain Master Plan is no, then Planning Horizon equals
to order horizon, in Plan Item Data as well as in Plan Item Defaults.

Solution: 158330
SITUATION IDENTIFIED IN:
"Close Year" (tfgld6203m000)
SITUATION DESCRIPTION:
If a ledger account has a credit balance then the quantity stored on the ledger account is reported as a negative figure. When
the year is closed and again the quantity on the ledger account is checked it is now reported as a positive figure.
SOLUTION DESCRIPTION:
When writing the opening balance of ledger accounts with a credit balance, the year end session wrote the quantity
incorrectly in the non-finalized transactions table (tfgld102). Thus, wrong figures got stored in the history tables of the
GLD module which would cause financial reports to display the wrong quantity. This has been corrected.

Solution: 158331
SITUATION IDENTIFIED IN:
"Cancel Production Orders" (tisfc0203m000)
SITUATION DESCRIPTION:
When cancelling production orders, instead of being cancelled and deleted, production orders were left with status 'To Be
Deleted'.
SOLUTION DESCRIPTION:
When cancelling production orders, production orders are now correctly cancelled and deleted.

Solution: 158343
SITUATION IDENTIFIED IN:
"Process Import/Export Statistics" (tccom7271m000)
SITUATION DESCRIPTION:
When printing the report 'Seq. Im/export File IRIS', the weight is supposed to be converted from the item unit
(tcibd001.cwun) to the unit in the 'Intra EU Transaction Parameters' (tccom999.uwgt.7), but the conversion was done with
the inverse factor. This resulted that a weight of 25110 gr was shown as 25110000 kg.
SOLUTION DESCRIPTION:
When printing the report 'Seq. Im/export File IRIS', the weight is now correctly converted from the item unit (tcibd001.cwun) to the unit in the 'Intra EU Transaction Parameters' (tccom999.uwgt.7).

Solution: 158345
SITUATION IDENTIFIED IN:
"Audit Batches" (tfgld1211s000)
"Maintain Journal Vouchers" (tfgld1103s000)
"Maintain Journal Vouchers (Multiple Lines)" (tfgld1115s000)
SITUATION DESCRIPTION:
While finalizing a batch, the check to make sure no blocked dimensions are used in the document, is carried out on the wrong
date. The document date is used to make the check instead of the batch transaction entry date.
SOLUTION DESCRIPTION:
The transaction entry date is now used to check for blocked dimension. This date was already used correctly to check for
blocked ledger accounts.
The same problem existed in the Journal Vouchers sessions. This too has been corrected.

Solution: 158356
SITUATION IDENTIFIED IN:
"Conversion to File Word Processor" (ttstpconv)
SITUATION DESCRIPTION:
Extra characters showing up in RTF files
SOLUTION DESCRIPTION:
Corrected the report stream processing to remove all escape codes.

Solution: 158357
SITUATION IDENTIFIED IN:
"Backflush Materials and Hours" (tisfc0220m000)
SITUATION DESCRIPTION:
A Shopfloor Control Production Order will not be backflushed via the session "Backflush Materials and
Hours(tisfc0220m000)" where the main item is Standard-To-Order. This occurs because no routing can be found. Instead, the
routing that the Standard-To-Order item's derived item should be used.
SOLUTION DESCRIPTION:
For Standard-To-Order main items, the routing of the derived item will be used during backflushing.

Solution: 158371
SITUATION IDENTIFIED IN:
"Change Access Mode by Batch" (tfgld1108m000)
SITUATION DESCRIPTION:
An invalid user-id can be entered in the user field. This can lead to the batch been inaccessible to any user.
SOLUTION DESCRIPTION:
Check has been added on the user field and an invalid user will not be allowed.

Solution: 158382
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions to finance, negative amounts are posted to non-finalized transactions when the
transaction type does not allow negative amounts. This happens when posting intercompany integration transactions, where
the two companies have different number of currencies.
SOLUTION DESCRIPTION:
When posting intercompany transactions, the correct number of home currencies for each company is now determined.
Transactions that do not allow negative amounts now get converted properly in all home currencies.

Solution: 158391
SITUATION IDENTIFIED IN:
"Menu Browser" (ttdskmbrowser)
SITUATION DESCRIPTION:
Under the "Help" menu option of the Menu Browser is the Contents help menu option.
In BaanIV and iBaanERP when Windows help is suppressed, this Contents menu shows Baan Business Objects.
In iBaanERP, Business Objects are no longer used. This leads to outdated and irrelevant information in the Contents index.
SOLUTION DESCRIPTION:
The Contents index was designed to bring up Business Objects. Since they are no longer used in iBaanERP, this option is
now disabled when Windows help is suppressed or when no Windows help is defined for a user in iBaanERP. It is enabled
when Windows help is being used.

Solution: 158397
SITUATION IDENTIFIED IN:
"Time Phased Planning Overview" (cprrp0520m0000)
SITUATION DESCRIPTION:
The cost price and currency is displayed in Form 1(Overview), but not displayed in Form 2 (Detail) and Form 3 (Detail 2)
SOLUTION DESCRIPTION:
The cost price and currency is displayed in all forms.

Solution: 158401
SITUATION IDENTIFIED IN:
"Post Integration Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions with session (tfgld4201m000) within a company that is setup to not use reporting
periods and is setup to use transaction compression, posted transactions are not compressed in the non-finalized transaction
table tfgld102 (Non-finalized Transactions).
SOLUTION DESCRIPTION:
The session "tfgld4201m000" (Post Integration Transactions) was erroneously populating the reporting year on the transaction with the fiscal year. If a company does not use reporting periods, the reporting year should be 0. This caused a mismatch when determining if transactions could be compressed as reporting year is part of the compression criteria. The result was that transactions would never compress. To correct this situation the reporting year will now be written correctly in tfgld102 (Non finalized transactions) if the company does not use reporting periods.

Solution: 158406
SITUATION IDENTIFIED IN:
"Address Jurisdiction Verification Utility" (tccom6210m000)
SITUATION DESCRIPTION:
The session "Address Jurisdiction Verification Utility" needed several improvements. One improvement needed was a change
of the program flow for the session because the non-interactive session was not always getting the correct geo code. Also the
correct information was not always printing to the report.
SOLUTION DESCRIPTION:
The session "Address Jurisdiction Verification Utility" has been improved in many ways. One example is the program flow
has been changed to eliminate waste and become more progressive. Another example of improvement is that all
necessary records are printing to a report.

Solution: 158414
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
When calculating commissions for orders that were delivered from multiple lots within warehousing, the commissions are
not being calculated.
SOLUTION DESCRIPTION:
When delivering a single sales order from multiple lots in warehousing, new sales order lines are added in the system to
handle the individual deliveries. When this happened, the commission relations linked to the original sales order line were
not getting linked to the new lines. Because of this, the commissions were not being calculated completely.

Solution: 158422
SITUATION IDENTIFIED IN:
"Version Scan Tool" (ttaad0500m000)
SITUATION DESCRIPTION:
Customers who had more than 10 database definitions in table ttaad410 were receiving an index out of dims when running
the Version Scan Tool.
SOLUTION DESCRIPTION:
The number of database definitions has been increased to accommodate a much larger number.
In addition, the functionality to read existing VST output files has been removed. This will make certain that only current
information is present on-screen.

Solution: 158423
SITUATION IDENTIFIED IN:
"Archive / Purge Vat Transactions" (tfgld6207m000)
SITUATION DESCRIPTION:
The session Archive / Purge Vat Transaction (tfgld6207m000) lacks an option to execute the session a background job in Baan
4c. In Baan 5c, 5b this session does not validate the user input before scheduling a job.
SOLUTION DESCRIPTION:
The ability to execute the session Archive / Purge Vat Transaction (tfgld6207m000) as a job has been implemented in 4c. In all
versions, the user input will be validated before allowing this session to be scheduled as a job.

Solution: 158430
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
When the Print Project Work In Process session is run either for 'By Project' or 'By Project / Department' retroactive
warehouse value adjustment transactions posted against either the project calculation office or against a department were
ignored. Additionally when running the session for 'By Project / Order', price variances posted against a warehouse (in the
case of actual costing) were ignored. Both of these situations resulted in an incorrect amount work in process on the report.
SOLUTION DESCRIPTION:
The session has been corrected so that all relevant transactions are included in the session's reports.

Solution: 158435
SITUATION IDENTIFIED IN:
"tfgld1440m000" (Print Finalized Transactions by Date)
"tfgld1441m000" (Print Journal)
SITUATION DESCRIPTION:
When printing reports, the total amounts are not printed if they are amounts greater than 16 digits in length . The reports,
instead, print a format overflow sign like "################" for total amounts.
SOLUTION DESCRIPTION:
The totals have been extended to now print 18 digits.

Solution: 158436
SITUATION IDENTIFIED IN:
"Project Parts & Budget Parts" (tipcs2411m000)
SITUATION DESCRIPTION:
When printing "Project Parts" or "Budget Parts", the warning message "Report does not fit on paper" is displayed. However,
the report is designed properly to fit on standard A4 paper size.
SOLUTION DESCRIPTION:
Now when printing "Project Parts" or "Budget Parts", there is no warning displayed and the report prints correctly.

Solution: 158452
SITUATION IDENTIFIED IN:
"Inventory Commitment" (whinp2100s000)
SITUATION DESCRIPTION:
Inventory commitment acts as though the full amount has been committed from previous, partial commitments.
SOLUTION DESCRIPTION:
Changed Inventory Commitments not to consider backorder quantities when determining the amount that can be committed.

Solution: 158460
SITUATION IDENTIFIED IN:
"Maintain Production Planning" (tisfc1101s000)
SITUATION DESCRIPTION:
When changing the work center to subcontracting work center on a operation in production planning, the system gives an
error message " Backflush employee is not filled for work center". The same error message is given when SCS Scheduler
changes the machine and work center to a subcontracting work center and the operation is transferred to Baan ERP.
SOLUTION DESCRIPTION:
The session will not give the error message "Backflush employee is not filled for work center", when the work center is
changed to Subcontracting Work Center, as the backflushing field will be set to "No".

Solution: 158461
SITUATION IDENTIFIED IN:
"Calculate Currency Differences" (tfgld5201m000)
SITUATION DESCRIPTION:
While running the session Calculate Currency Differences, it was possible for transactions to be created in the
Non-finalized Transactions table (tfgld102) for GL accounts and dimensions which have a blocking status of "blocked for all
purposes." This should not be possible as the created batch will give errors when attempting to finalize.
SOLUTION DESCRIPTION:
Checks have been added in the session "Calculate Currency Differences" so that no transactions will be created for any
ledger accounts/dimensions that are blocked for all purposes. An error message will be displayed on the report for these
ledger accounts/dimensions that are blocked.

Solution: 158465
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When a production order operation is subcontracted after materials/hours have been posted to the original planned internal
workcenter of the operation, the Amount Work in Process for the internal workcenter and the order are not zero after the
order is closed.
SOLUTION DESCRIPTION:
The session has been corrected to account for and clear the amount Work in Process for workcenters that have been detached
from a production order via subcontracting.

Solution: 158467
SITUATION IDENTIFIED IN:
"Conversion to File Word Processor" (ttstpconv)
SITUATION DESCRIPTION:
Postscript documents were being created with illegal syntax. Also, an extra page was generated at the end of every
document.
SOLUTION DESCRIPTION:
Changed the 'attend' instruction to the proper 'atend'. Also, rewrote logic so that new page instructions are only entered if
there is more data to be processed.

Solution: 158478
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
When configuring a product variant, and the focus is on the last visible feature and then new features are displayed via
constraint logic, the focus is moved back to the first feature on the screen, and not to the new features.
SOLUTION DESCRIPTION:
Now when configuring a product variant, and the focus is on the last visible feature and then new features are displayed via
constraint logic, the focus is moved to the next visible feature.

Solution: 158493
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance" (tfgld4201m000) and "Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
When posting integration transactions to finance using sessions "Post Integration Transaction to Finance" (tfgld4201m000)
or "Transactions" (tfgld1101m000), sometimes the integration transactions are posted into a non-integration batch.
SOLUTION DESCRIPTION:
The solution prevents the session "Post Integration Transaction to Finance" (tfgld4201m000) from using batch number not
created by integrations in Baan 5c and 5b. In Baan 4c, an additional check has been added to prevent users sharing a
common login from acquiring the same batch number.

Solution: 158497
SITUATION IDENTIFIED IN:
"Report Production Schedules Complete" (tirpt1201m000)
SITUATION DESCRIPTION:
For each completion of a SFC production order, there will be two inbound lines. When printing the inbound lines at the
time of completing a SFC production order, both inbound lines were printing confusing the user.
SOLUTION DESCRIPTION:
Only the last inbound line of the sequence is important for the report. Therefore, only the last record of each sequence is
printed on the inbound report.

Solution: 158526
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
In cases where more than one transaction schedule is used per batch in session Journal Vouchers (Multiple Lines), the user
is always taken back to the first journal after transactions have been created with session Create Transactions from Schedule
(tfgld1204s000).
SOLUTION DESCRIPTION:
Journal Vouchers (Multiple Lines) has been modified to display the newly created transactions.

Solution: 158529
SITUATION IDENTIFIED IN:
"Simulate Order/Simulate Master Plan" (cprrp1210m000/cprmp1203m000)
SITUATION DESCRIPTION:
1. Signal "Negative Inventory Level" is generated when Order Time Fence is zero and the projected inventory level is not
negative (Happens only if Simulate Master Plan within time fence)
2. Signal "Negative Inventory Level" is not generated when Order Time Fence is zero and the projected inventory level is
negative (happens when NOT Simulating within time fence)
SOLUTION DESCRIPTION:
Signal "Negative Inventory Level" is only generated when the inventory level truly goes negative.

Solution: 158535
SITUATION IDENTIFIED IN:
"Delete WIP Transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
When deleting WIP transactions for already archived production orders and projects, the project and production order
numbers do not appear on the report.
SOLUTION DESCRIPTION:
For all projects and production orders where WIP transactions are being deleted, the production order and project numbers
will appear on the report.

Solution: 158536
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When an item receipt surcharge is added to a production item, after a production order is created for the item and materials
are issued for the order without backflushing, the surcharge is incorrectly posted for a quantity of one instead of the entire
ordered quantity upon closing the order. This results in incorrect variance postings during closing.
SOLUTION DESCRIPTION:
The Close Production Orders session has been corrected and item receipt surcharges are now posted for the entire quantity
ordered, providing correct variance postings.

Solution: 158551
SITUATION IDENTIFIED IN:
"Update Purchase Statistics" (tdpst0201m000)
SITUATION DESCRIPTION:
The Purchase statistics was not getting updated when the ship-from is blank in the Purchase order header. The system gives
an error message saying "Ship-to Business Partner not present for this order".
SOLUTION DESCRIPTION:
The purchase statistics is now updated correctly with the ship-from of the purchase order lines. The error message "Ship-to
Business Partner not present for this order" doesn't occur any more.

Solution: 158555
SITUATION IDENTIFIED IN:
"Calculate Commissions / Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
The "No errors found" message is misleading if data range doesn't include valid orders.
When commissions are calculated for a range of orders and no orders are found in the range. The system returns a mesasge of
"No errors found for report, no report is printed".
This is the same message which prints when the commissions process correctly.
This is misleading to the user.
SOLUTION DESCRIPTION:
Added a new warning message:
"Commissions not calculated, No orders were found"
This should let the user know there were no orders found for the range they entered.

Solution: 158569
SITUATION IDENTIFIED IN:
"Update Last used batch number" (tfcor0006s000)
SITUATION DESCRIPTION:
This session correction exists in B50_b but not in B05_c. It is needed in B50_c too.
SOLUTION DESCRIPTION:
The correction session has been ported to B50_c. A restriction has been added to the session. Earlier whenever the session was
run, it just incremented the last used batch number by 1 every time the user ran it, in the Last Used Batch Number table
(tfgld014). Now this session will only synchronize the Last Used Batch Number table with the Batch table (tfgld100). Thus only
if the last used batch number in table tfgld014 is less than the biggest number existing in table tfgld100 for that year, this
session will update table tfgld014 to match the value in table tfgld100. In all other circumstances, this session will do
nothing.

Solution: 158575
SITUATION IDENTIFIED IN:
"Print Finalized Transactions by Dimension/Ledger" (tfgld1407m000)
SITUATION DESCRIPTION:
Report totals are not printed according to the correct currency format. The report was printing according to a default
format instead of the format of the home currency that the report was being printed for.
Thus if one home currency has decimals like 100.25 while another HC is only in whole numbers like Japanese Yen or Belgian
Francs, the report would not print the totals in correct format for one home currency or the other.
Also the 'Total To Period' total for dimensions would not print credit amounts.
SOLUTION DESCRIPTION:
Changes have been made to the report to print the totals in the format of the report currency (Home currency chosen on the
form). A field has been added to the report to print the credit side of the dimension 'Total To Period'.

Solution: 158581
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When composing or posting invoices with tax calculated using Vertex, the invoice document number is not being passed to
Vertex correctly. This causes the Vertex variable "InvNo" to be populated incorrectly. Currently the Vertex variable "InvNo"
contains only the invoice transaction type. This makes it impossible to sort the data in the Vertex reports based on the
invoice.
SOLUTION DESCRIPTION:
The correct value for the invoice document number is now being passed
to Vertex, so that the InvNo variable contains the invoice transaction type and invoice document number.

Solution: 158584
SITUATION IDENTIFIED IN:
"Availability Check for Tools" (titrp0213m000)
SITUATION DESCRIPTION:
For all lines printed during the "Availability Check for Tools", the date is the operation start date. This shows no difference
between all the lines of the report and therefore makes the report unusable.
SOLUTION DESCRIPTION:
For all lines printed during the "Availability Check for Tools", the date has been changed to show the day the tool is
available from the table "Availability Planning(titrp013)".

Solution: 158589
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
Although a Production/Price Variance transaction of amount zero is not posted to the finance Integration Lines Debit table
(tfgld410), a posting is incorrectly made to the Additions to Integration Transactions table (tfgld415) with errant data.
SOLUTION DESCRIPTION:
The financial integration between manufacturing and finance has been corrected and now Production/Price Variance
transactions of amount zero do not result in an incorrect finance record in the Additions to Integration Transactions table
(tfgld415).

Solution: 158590
SITUATION IDENTIFIED IN:
"List Components" (tcibd3100m000)
SITUATION DESCRIPTION:
The user could assign a negative quantity for a list component with the anticipation that when the list item was used on a
sales order, the list components with a negative quantity would be re-added to inventory. However, the system has not been
setup to handle sales orders for a list item which has components with negative quantities in this manner (the current system
ignores those list components with a negative quantity).
SOLUTION DESCRIPTION:
Entering a negative quantity for a list component is no longer allowed. When a negative
quantity is attempted to be entered, the message "List Components cannot have a Negative Quantity" is issued and the user is
required to change the quantity on the list component (ie. the record is not saved with a negative quantity).

Solution: 158596
SITUATION IDENTIFIED IN:
"Display Ledger History - Dim Type Wise Distribution" (tfgld3507m000)
SITUATION DESCRIPTION:
The session tfgld3507m000 (Display Ledger History - Dim Type Wise Distribution) is not displaying budget information.
SOLUTION DESCRIPTION:
The session had a problem while querying for budget data. It has been corrected.

Solution: 158599
SITUATION IDENTIFIED IN:
"Inventory-Inspection Data" (whinh3122s000)
SITUATION DESCRIPTION:
Unable to reject part of receipt quantity for project warehouses
SOLUTION DESCRIPTION:
System no longer requires that approved and rejected quantites comprise the entire receipt.

Solution: 158603
SITUATION IDENTIFIED IN:
"Recreate Warehouse Outbound Lines" (ticor0002m000) (B50_c only)
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
The session 'Recreate Warehouse Order Lines' (ticor0002m000) (B50_c only) used a label 'Continue' (tiFStisfc.init), which
had never been delivered.
The report 'Print Actual Cost-Price by Project' (tipcs3462m000) is using a label 'Serial Number' (tipcs340.fili), which had a
German translation that was too long to be displayed.
SOLUTION DESCRIPTION:
The session 'Recreate Warehouse Order Lines' (ticor0002m000) (B50_c only) is now using a label 'Continue'
(tigen.continue), which is available.
The report 'Print Actual Cost-Price by Project' (tipcs3462m000) is using a label 'Serial Number' (tipcs340.fili), which has
now a German translation that is displayed correctly.

Solution: 158604
SITUATION IDENTIFIED IN:
"Change Access Mode by Batch" (tfgld1108m000)
SITUATION DESCRIPTION:
Get error Invalid User when access is changed from "Individual User" to "All Users". Check on Valid user id is only
needed when access = "Individual User"
SOLUTION DESCRIPTION:
Check on Valid user id will only be done when access = "Individual User"

Solution: 158611
SITUATION IDENTIFIED IN:
"Archive / Purge Finance Transactions" (tfgld6205m000)
SITUATION DESCRIPTION:
The session purged the table Finalization Run Number status (tfgld109) but did not archive it even when the flag "Archive
to History Company?" on the form was set to "Yes".
SOLUTION DESCRIPTION:
The archiving part was missed out from the session. It has been added and so when the archiving flag is "Yes", the table will
be archived first and then purged.

Solution: 158620
SITUATION IDENTIFIED IN:
"Maintain Sales Order Line Details" (tdsls4101s200)
SITUATION DESCRIPTION:
When using commissions and having a default relation set up for a business partner, the session gets an error 100 when the user
tries to enter detail lines for a sales order.
SOLUTION DESCRIPTION:
When entering detail lines for a sales order line, the default commission/rebate relations where not being linked correctly.
This caused the fatal error to occur. The linking will now be done correctly and no errors will result.

Solution: 158621
SITUATION IDENTIFIED IN:
"Print Finalized Transactions by Ledger Account" (tfgld1406m000)
"Print Finalized Transactions by Dimension/Ledger" (tfgld1407m000)
"Print Finalized Transactions by Date" (tfgld1440m000)
"Print Journal " (tfgld1441m000)
SITUATION DESCRIPTION:
When the session is run as a Job, the rotate currency functionality does not work. The reports are printed in the home
currency instead of the currency set when creating the job.
SOLUTION DESCRIPTION:
Changes have been made to get the proper currency when printing in job mode.

Solution: 158641
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
When trying to confirm a picking list for an item transfer within the same warehouse, we get message: "Some of the selected
lines have not been confirmed." followed by: "Received quantity should not exceed shipped quantity for a transfer order"
SOLUTION DESCRIPTION:
System now allows the picking list to be processed for item transfers within the same warehouse.

Solution: 158645
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (Service)" (tfgld4103s000)
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When setting up Integration Mapping Scheme (Service) for Sales Invoicing (Service) / Revenues Analysis using the session
"Integration Mapping Scheme" (tfgld4103s000), the combination of Financial Business Partner Group A/R and Cost
Component is not allowed. When this combination is entered the system gives error message "Invalid combination of
selected fields for Key Definition". This new combination should be allowed.
SOLUTION DESCRIPTION:
This combination is now added as one of the valid combinations for Key Definition. The system now accepts this
combination.
Further, when Integration Transactions are posted to Finance using the session "Post Integration Transactions to Finance
Transactions" (tfgld4201m000), system obtains the ledger account set up for the combination and posts the integration
transaction to finance.
Help text is updated showing the latest search priorities for Service.

Solution: 158658
SITUATION IDENTIFIED IN:
"Cumulative Sales for Commissions" (tdcms1500m000)
"Cumulative Sales for Rebates" (tdcms1505m000)
SITUATION DESCRIPTION:
The "Cumulative Sales for Commissions"(tdcms1500m000) and the "Cumulative Sales for Rebates"(tdcms1505m000) session
both display an incorrect currency code for the amounts that are displayed. This only happens when using dependent
currency system.
SOLUTION DESCRIPTION:
Changed the session to display the correct currency in the column headers of the cumulative sales sessions mentioned above.
Now the proper currency code will be listed regardless of the currency system that is used.

Solution: 158666
SITUATION IDENTIFIED IN:
"Process Commission/Rebate" (tdcms2201m000)
SITUATION DESCRIPTION:
When running session "Process Commission/Rebate"(tdcms2201m000) getting the following:
FATAL ERROR: Illegal number of args (48) for function tfint.dlltfgld.write.integr.transactions.easy expected 57.
SOLUTION DESCRIPTION:
Changed the integration librarys to send the necessary number of arguments between functions. This will stop the Fatal
Error from happening.

Solution: 158667
SITUATION IDENTIFIED IN:
"Winhelp Functions" (ttdllhelp)
SITUATION DESCRIPTION:
When converting help text to windows helpfile format, cyrilic text was not being converted properly.
SOLUTION DESCRIPTION:
During the conversion process the text needed to be converted from TSS to windows format (similar to what BWPrint does)
so when the locale is ISO8859-5 the text is converted to CP1251.

Solution: 158675
SITUATION IDENTIFIED IN:
"Purchase Statistics Layout Codes" (tdpst0196s000)
SITUATION DESCRIPTION:
The session Purchase Statistics Layout Codes could not be run under webtop 1.1.
SOLUTION DESCRIPTION:
The session Purchase Statistics Layout Codes can now be run under webtop 1.1

Solution: 158678
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
When configuring a variant in "object mode", initial values for integer and fractional type features are initialized to zero in
the constraints. This causes an overwrite question when before input constraint logic sets the option to a non-zero value. When
configuring in the "interpreter mode", this question is not asked, which is the desired functionality. Also when the variant is
saved, any non-input feature that was initialized to zero will cause the variant to be not validated, if there is no zero option
defined.
SOLUTION DESCRIPTION:
Configuring a variant in "object mode" will only ask the overwrite question if there exists a zero option value defined in the options for
that feature. And the variant will be properly validated.

Solution: 158683
SITUATION IDENTIFIED IN:
"Print Trial Balance - Dimension Code/Ledger Accounts" (tfgld3406m000)
SITUATION DESCRIPTION:
Problem # 1: Reports have been ordered neither by ledger account sequence number nor by dimension sequence number.
Problem # 2 (Only in Baan5c):During running of the session "Print Trial Balance - Ledger Account/Dimensions"
(tfgld3404m000) progress indicator has never reach 100%.
SOLUTION DESCRIPTION:
Problem # 1: Reports are ordered by sequence numbers.
Problem # 2: Maximum value of the progress indicator is set to 100%.

Solution: 158684
SITUATION IDENTIFIED IN:
"Trial Balance - currency wise" (tfgld3403m000)
SITUATION DESCRIPTION:
The report printed foreign currency (FC) amounts in the format of the home currency (HC). Thus if the FC has decimals
like 100.25 while the HC is only in whole numbers like Japanese Yen or Belgian Francs, the FC amount would print as a
whole number too. Thus, instead of 100.25 it would print 100.
SOLUTION DESCRIPTION:
This problem happened because the report fields, which printed the FC amounts, were associated with the print format of the
HC. This association has been corrected so that the FC amounts will print in the format associated with that currency.

Solution: 158687
SITUATION IDENTIFIED IN:
"Menu Browser" (ttdskmbrowser)
SITUATION DESCRIPTION:
Due to a bad fix for defect 207122, users were not able to access Help Contents when Windows Help was defined
SOLUTION DESCRIPTION:
Users who have Windows Help defined can now use the Contents option under the Help menu in the Menu Browser.

Solution: 158692
SITUATION IDENTIFIED IN:
"Integration Transactions by Document Line" (tfgld4512m000)
"Non-Finalized Transations" (tfgld3508m000)
"Finalized Transations" (tfgld3509m000)
SITUATION DESCRIPTION:
When running the session Ledger History (tfgld3501s000) in a company and on the default parameters one specifies a
different company, then it is not possible to mark a finalized line in session Finalized Transactions (tfgld3509m000) or
Non-Finalized Transactions (tfgld3508m000) and view the integration details in session Integration Transactions by
Document Line (tfgld4512m000).
SOLUTION DESCRIPTION:
This problem happened because the current company number was sent to the session Integration Transactions by Document Line
(tfgld4512m000) instead of the one specified by the user in the defaults session (tfgld3503s000). Thus, the session was not
able to retrieve the correct data for display. This has been corrected.

Solution: 158704
SITUATION IDENTIFIED IN:
"Global Approval of Commissions/Rebates" (tdcms0250m000)
SITUATION DESCRIPTION:
Progress Indicator does not update past the first order. This makes it look as though the program is hung.
SOLUTION DESCRIPTION:
Changed the program script to properly update the progress indicator as the order changes when running "Global
Approval of Commissions/Rebates" (tdcms0250m000)

Solution: 158706
SITUATION IDENTIFIED IN:
"DDC Server" (tuddc1203s000)
SITUATION DESCRIPTION:
Last solution caused excessive logging to occur in the ddc server.
SOLUTION DESCRIPTION:
Removed most of the logging that was added with last solution.

Solution: 158722
SITUATION IDENTIFIED IN:
"Receipts via DDC" (whinh3520b000)
SITUATION DESCRIPTION:
When you have an item that is fifo and you recieve first item through DDC then receive the second item. It will keep the
inventory date of the first item that was received
SOLUTION DESCRIPTION:
Any previous date is now cleared durring receiving.

Solution: 158723
SITUATION IDENTIFIED IN:
"Print Conversion Factors by Item" (tiitm0421m000/tcibd0403m100)
SITUATION DESCRIPTION:
The form input field "errors only" on printing conversion factors by item is misleading. When "errors only" is YES, it actually
prints only the units of the unit set for the item that have no conversion factor defined for the inventory unit of the item. This
is not actually an error.
SOLUTION DESCRIPTION:
The form label for field "errors only" has been changed to "undefined conversion factors only", which more accurately reflects the reported data.

Solution: 158734
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When a shipment with multiple lines is being confirmed all the shipment lines after the first line were doing the check on
the parameter "Central Invoicing Implemented" on the the wrong company.
SOLUTION DESCRIPTION:
Problem was caused because a read on the table tccom000 done by a dll was causing the company number to be changed. The
script has now been changed to read a standard dll to check company data.

Solution: 158757
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0101s000)
SITUATION DESCRIPTION:
When changing the item group in "General Item Data", the item group is not updated in the "Item Supplier Info". This is
working correctly in standard, but is not working in the Japanese Localization.
SOLUTION DESCRIPTION:
The Japanese Localization of "General Item Data" is now properly working, such that when the item group is changed, it is
also updated in the "Item Supplier Info".

Solution: 158773
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
When printing commission invoices for a sales order line with multiple details, only the first detail line is included on the
invoice.
SOLUTION DESCRIPTION:
The session has been modified to print all detail lines on the invoice. The totals will also be updated correctly.

Solution: 158776
SITUATION IDENTIFIED IN:
"Process Calls by Support Engineer" (tsclm1116m000)
SITUATION DESCRIPTION:
A serious performance problem occurs when attempting to open session "Process Calls by Support Engineer". In some
instances, 10-20 min. is used to open session.
SOLUTION DESCRIPTION:
The performance issue has been addressed. The session will now open within a reasonable time frame.

Solution: 158792
SITUATION IDENTIFIED IN:
"Currency Differences for Ledger Account" (tfgld5201m000)
SITUATION DESCRIPTION:
The amount fields on this report are not being displayed according to the currency format.
SOLUTION DESCRIPTION:
Now the amounts will be displayed according to the currency formats.

Solution: 158794
SITUATION IDENTIFIED IN:
"Import Data Dictionary 2" (ttiex1288m000)
SITUATION DESCRIPTION:
Importing changed help text didn't always work.
SOLUTION DESCRIPTION:
If the help text existed in another language, the original text wasn't getting deleted. Now it is.

Solution: 158799
SITUATION IDENTIFIED IN:
"Compile Constraints by Generic Item" (tipcf2201m000)
SITUATION DESCRIPTION:
When compiling constraints by generic item, the server name was stored in the path for the object and source directories.
The server name is required to access the objects in a client/server environment with a remote bshell setup (BSE_REM). When
having a shared directory setup between several servers, the server name was possibly incorrect and causing error messages in
the log files at the time of accessing the constraint objects.
SOLUTION DESCRIPTION:
Changes have been made that the server name is now not stored anymore in the path for the object and source directories. In case of a client/server environment
with a remote bshell setup, the server defined in the BSE_REM system variable is now added at the time of executing the constraint.

Solution: 158811
SITUATION IDENTIFIED IN:
"Ledger Accounts by Bussiness partner Group" (tfacp0111m000) / (tfacr005m000 )
SITUATION DESCRIPTION:
Even when the dimensions are present in tfacp005, they were not visible in this session , when the dimension usage is
switched off in Maintain Ledger Accounts.
SOLUTION DESCRIPTION:
Now, when the dimension usage is switched off in the Maintain Ledger Accounts ( tfgld008 ), then the dimensions present in
the Bussiness partner group table will still be visible, but will not be accessible.

Solution: 158813
SITUATION IDENTIFIED IN:
"Global Approval of Commissions/Rebates" (tdcms0250m000)
SITUATION DESCRIPTION:
Global Approval of Commissions/Rebates (tdcms0250m000) is not working correctly when trying to approve commissions is a
multi-site environment and the commission flag is set to Paid Invoice. If the invoice is in another company other than the
logistic company the session will not find it and the commission will not get approved.
SOLUTION DESCRIPTION:
Change the program script to correctly check the financial company associated with the sales office for the Paid Invoice.
This will correct the error that occurred above and allow the commission to be approved.

Solution: 158814
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
The following errors are displayed when running the session "Print Commission/Rebate Invoices" (tdcms2402m000):
- unable to determine invoice number for relation 005
- no data within selection
SOLUTION DESCRIPTION:
Problem is due to having the "link with Finance" flag set to no withing the commission parameters. The "Print
Commission/Rebate Invoices" (tdcms2402m000) session has been modifed to correctly determine the next invoice number. This
will stop the error message from being displayed and allow the process to continue. If the "link with Finance" flag is set to
yes everything functions as it did before.

Solution: 158818
SITUATION IDENTIFIED IN:
"Export Language Dependent Components" (ttadv6230m000)
SITUATION DESCRIPTION:
Hypertext links in Japanese were not being exported properly. Non-keyword characters such as "#" and "(" would be
translated as keywords.
SOLUTION DESCRIPTION:
Non-keyword characters are being parsed out and are distinguished from actual keywords.

Solution: 158826
SITUATION IDENTIFIED IN:
"Imported Journals" (tfgld2513m000)
SITUATION DESCRIPTION:
The session "Imported Journals" (tfgld2513m000) does not allow the deletion of successfully imported journals. Successfully
imported journals are those batches with the status "Processed".
SOLUTION DESCRIPTION:
The session now allows the deletion of a successfully imported journal batch. The user needs to mark an imported journal
batch with the status "Processed" and click on the "Delete" button. The batch is then deleted.
The session gives the error message 'Only "Processed" journal batches can be deleted', if the user selects a batch with a
different status other than the status "Processed".

Solution: 158829
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When simulating orders, the planned finish date on the planned order generated never gets planned in the past, even though the
requirement date on the order is in the past. Moreover, the planned finish date on the planned order header (cprrp100) is in the
past, but the finish date on the planned order line (cprrp110) was always, either equal to the current date or the future date,
but never in the past.
SOLUTION DESCRIPTION:
If the requirement date is in the past, then the finish date on the planned order will also be in the past. (However, the
planned finish date may never be before the scenario start date).

Solution: 158838
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
The form field "D/C" (Debit/Credit) did not get updated automatically while working with BI interface. Because of this, the
user had to select the correct value manually. This problem occurred because BAAN changed the value of the field but did
not refresh the form.
SOLUTION DESCRIPTION:
Now the form field "D/C" (Debit/Credit) is updated explicitly each time its value changes.

Solution: 158839
SITUATION IDENTIFIED IN:
"Help Groups" (ttadv8540m000)
SITUATION DESCRIPTION:
Exporting Cyrillic help text to windows help-file format was not working completely.
SOLUTION DESCRIPTION:
The solution moved the translation of ISO88595 to CP1251 from ttdllhelp, which addressed only one type of help, to
ttdllrtf, which addresses all types of help. The change made to ttdllhelp was removed.

Solution: 158845
SITUATION IDENTIFIED IN:
"Archive / Purge VAT Transactions" (tfgld6207m000)
SITUATION DESCRIPTION:
It was possible to archive and purge VAT transactions from the Tax Analysis table tfgld110 even though they existed in the
Finalized Transactions table tfgld106. This makes it impossible to reconcile supplier/customer transactions.
SOLUTION DESCRIPTION:
A new check has been added into the session to make sure that the record does not exist in the Finalized Transactions table.
Only if the record has been archived/purged from there will the archiving/purging of the Tax Analysis table record will be
done.

Solution: 158846
SITUATION IDENTIFIED IN:
"select device" (ttstpsplopen)
SITUATION DESCRIPTION:
Save/Get Defaults not working properly for "margin" and "preview" when selecting a device (ttstpsplopen)
SOLUTION DESCRIPTION:
Defaults for "margin" and "preview" are now retrieved properly after being set.

Solution: 158849
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When running the Compose/Print/Post Invoices session (cisli2200m000) for Service-Material, the source type for the invoice
was being set to Sales rather than to Service when updating the Vertex register. This led to incorrect tax amounts being
written to the register.
SOLUTION DESCRIPTION:
The source type for the invoice is now being set correctly to Service so that the Vertex register is updated correctly.

Solution: 158868
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
When configuring a variant and the situation is such that the focus on is the third to last feature, and the next feature is
input disabled and the last feature is input enabled, then when tabbing through the current feature and the input conditions of
the last two features are reversed due to constraints, the focus is lost and cannot be retrieved.
SOLUTION DESCRIPTION:
Now when configuring a variant where the input conditions are reversed on the last two features as described in the "situation description", the
focus is now transferred properly to the next feature, which has been input enabled.

Solution: 158872
SITUATION IDENTIFIED IN:
"Conversion to File Word Processor" (ttstpconv)
SITUATION DESCRIPTION:
Single page postscript reports were not being printed.
SOLUTION DESCRIPTION:
Moved the 'p' (showpage) command processing back to where we handle linefeed characters from where it had been moved
with the rest of the newpage processing.

Solution: 158877
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme" (tfgld4103s000)
SITUATION DESCRIPTION:
User was not able to define Item Group during setting up of Credit side of the integration-mapping scheme for
Sales Invoicing (Service)/Revenue Analysis. Program was generating an error "Reference not found".
SOLUTION DESCRIPTION:
Now user will be able to define Item Group.

Solution: 158878
SITUATION IDENTIFIED IN:
"Archive Project" (tipcs2260m000)
SITUATION DESCRIPTION:
When tabbing through the fields on the form and the checkbox "Financial Project Data" is disabled, a warning message
"Note: Project data will be deleted" was given. However, since the session "Archive Project" does not remove the "WIP
and Inventory Transactions (PCS/PCF)" anymore, the warning message is not needed.
SOLUTION DESCRIPTION:
When tabbing through the fields on the form and the checkbox "Financial Project Data" is disabled, no warning message
"Note: Project data will be deleted" is given anymore.

Solution: 158890
SITUATION IDENTIFIED IN:
"Item Segmentation" (tcibd0500m000)
SITUATION DESCRIPTION:
The item segmentation should not be set to have item code first and the project code second, as this will casue all items to
be scanned when sessions are run for project only data.
SOLUTION DESCRIPTION:
The help text for the "Item Segmentation" session has been updated to note, that the project code should be first, then the
item code to be second in the segmentation structure.

Solution: 158900
SITUATION IDENTIFIED IN:
"Archive Project" (tipcs2260m000)
SITUATION DESCRIPTION:
In the session "Archive Project", the help text on the form field "Project Structure" is the same as the form field "Project
Calculation". This is incorrect, as it should be describing the project structure.
SOLUTION DESCRIPTION:
Now in the session "Archive Project", the help text on the form field "Project Structure" correctly describes the archiving of
the project structure and the related data.

Solution: 158916
SITUATION IDENTIFIED IN:
"Global Approval of Commissions/Rebates" (tdcms0250m000)
SITUATION DESCRIPTION:
Poor performance has been found in the "Global Approval of Commissions/Rebates" (tdcms0250m000) session. This due to
the way the history records are updated/created.
SOLUTION DESCRIPTION:
The "Global Approval of Commissions/Rebates" (tdcms0250m000) session has been modified to more efficently update the
history records, therby increasing the overall performance of the session.

Solution: 158920
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When running the Compose/Print/Post Invoices session (cisli2200m000) for a billing request which contains both sales and
service orders, the source type for the sales order will be incorrect if the Vertex register is updated for the service order
first. This led to incorrect tax amounts being written to the register for the sales order.
SOLUTION DESCRIPTION:
The source type for the invoice is now being set correctly for both types of orders, so that the Vertex register is updated
correctly.

Solution: 158924
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When running the Compose/Print/Post Invoices session (cisli2200m000) for a range of billing requests, the processing of the
orders ends if a Vertex error occurs within a single billing request. The remaining unprocessed billing requests should be
processed. The cause of the problem is that the variable indicating an error had occurred in a billing request was not being
reset for the next billing request.
SOLUTION DESCRIPTION:
The variable indicating that a Vertex error has occurred is now being reset, so subsequent billing requests can be processed.

Solution: 158928
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Order" (tdsls4244m000)
SITUATION DESCRIPTION:
There is a performance issue when generating project structure for sales order during the process of checking for standard
items. This was verified via a SQL trace during the generation process.
SOLUTION DESCRIPTION:
Now when generating project structure for sales order, the performance has been improved.

Solution: 158944
SITUATION IDENTIFIED IN:
"Rebuild Opening Balance/History from Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
The non-finalized credit amount in home currency was not being updated correctly in the History - Dimension/Ledger Account
Totals table (tfgld202). The debit amount was being updated when the transaction line was a debit or a credit.
SOLUTION DESCRIPTION:
The non-finalized amount in home currency is being updated correctly in the History - Dimension/Ledger Account Totals
table (tfgld202) for both debits and credits.

Solution: 158955
SITUATION IDENTIFIED IN:
"Imported Journals" (tfgld2513m000)
SITUATION DESCRIPTION:
It was only possible to delete imported journal records with status "Processed". It should be possible to delete an imported
journal regardless of its status.
SOLUTION DESCRIPTION:
The check on the status of an imported journal has been removed, so that an imported journal record can be removed
regardless of its status.

Solution: 158961
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0101s000)
SITUATION DESCRIPTION:
>>Problem: The item signal is not displayed.
>>Location: In the single occurrence session of "General Item Data".
>>Conditions: While accessing general item data from DEM (dynamic enterprise modeler) in "display only" mode.
>>Cause: Signals are only displayed in "maintain" mode for general item data. There is no provision for displaying item
signals when in "display only" mode.
SOLUTION DESCRIPTION:
>>Resolution: The item signal is now shown properly in either "maintain" or "display" mode.
>>Location: In the single occurrence session of "General Item Data".
>>Conditions: While accessing general item data from DEM (dynamic enterprise modeler) in "display only" mode.

Solution: 158971
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103s000)
SITUATION DESCRIPTION:
When searching for a dimension in session tfgld1103s000 (Journal Vouchers) by entering a "," in the dimension field -
the zoom session tfgld0510m000 (Dimension Master) only shows information for dimension type 1.
SOLUTION DESCRIPTION:
When searching for a dimension via "," in a dimension field the correct dimension information will be displayed.

Solution: 158977
SITUATION IDENTIFIED IN:
"Tax Code Lines" (tfgld1109s000)
SITUATION DESCRIPTION:
1) The ledger account and dimension fields are disabled if Destination Tax (tccom999.dstx) = No.
2) If the tax amount is changed in the Tax Code Lines (tfgld1109s000) then the Tax amount in Purchase Invoice Transaction
Lines (tfacp1120s000) was getting set to zero.
The second issue is only valid for the localization VRC's where the parameter "Generic Taxes" (tccom936.gtcd.l) is turned
on.
SOLUTION DESCRIPTION:
1) The session has been changed to allow the user to edit the Ledger Account field irrespective of the Destination tax
parameter value.
2) If the user changes the tax amount in the tax code lines then the change will be reflected in the calling session.

Solution: 158979
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
The following applies to a company having a dependent currency system with the local currency not equal to the reference
currency and a rate factor not equal to 1. When a journal voucher is entered in the local currency, an error message
(Document Currency and Home Currency are the same, so Rate must be 1.0) is displayed saying that when the document
currency and the home currency are the same, the rate factor should be 1.
SOLUTION DESCRIPTION:
The check on the rate factor is now performed only when the currency system is not dependent.

Solution: 158989
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
When a production order is released, the direct initiate inventory issue flag for an existing estimated material record was
reset. This occurred when one of the previous material lines had the direct process outbound flag set and had sufficient
inventory to meet the demand for the SFC order (ie. the material was issued immediately upon the release of the SFC order).
Subsequent material records that had the direct initiate inventory issue flag set would have the flag reset.
SOLUTION DESCRIPTION:
When a production order is released, the direct initiate inventory issue flag is not reset due to the processing of previous
material lines (ie. those lines with direct process outbound flag set). NOTE: The direct initiate inventory issue flag is set to
"No" when a record is added to the estimated material list for a SFC order and the order has already been released (ie. when
the order is in "Released" status).

Solution: 158996
SITUATION IDENTIFIED IN:
"Print Opening Balance by Ledger Account/Currency" (tfgld3401m000)
SITUATION DESCRIPTION:
Report amounts are not displayed according to currency format.
SOLUTION DESCRIPTION:
Amount fields on report were missing the Language/Currency expression. Amounts will now be printed according to the
currency format.

Solution: 159008
SITUATION IDENTIFIED IN:
"Generate Product Variant Structure for Sales Orders" (tipcf5260m000)
SITUATION DESCRIPTION:
When generating the product variant structure for sales orders, the product feature option descriptions in the generated item
text were in the incorrect language. For example, the Dutch item text was using the English product feature option
description, because the sales order was for an English-speaking customer.
SOLUTION DESCRIPTION:
When generating the product variant structure for sales orders, the product feature option description in the generated item text is now in the
correct language. Item text is generated for all languages that are defined in the generic item data. If a product feature option description has been
defined for the customer's language, then this description will be used, otherwise, the default description will be taken. The parameter "PCF in
Customer's language" (tipcf000.clan) is only used in the product configurator to display the product feature options in the customer's language; it is not used for the item text generation.

Solution: 159013
SITUATION IDENTIFIED IN:
"Archive/Purge Finance Transactions" (tfgld6205m000)
SITUATION DESCRIPTION:
When selecting the option "Archive to History Company" in session tfgld6205m000 (Archive/Purge Finance Transactions) the
session enters into an infinite loop.
SOLUTION DESCRIPTION:
This situation has been has been corrected.

Solution: 159031
SITUATION IDENTIFIED IN:
"Copy Project" (tipcs2210m000)
SITUATION DESCRIPTION:
>>Problem: The project details of the source project overwrites the project details of the existing target project.
>>Location: In the "Copy Project" session.
>>Conditions: When copying to an already existing project with the form input button "Project Master Schedule" set to
YES.
>>Cause: The copy of the project details is not conditioned by the fact of an already existing target project.
SOLUTION DESCRIPTION:
>>Resolution: The copy process of the project details of the source project is now conditioned by a check for the existence of
the target project. Thus when the target project already exists, the project details will not be copied.
>>Location: In the "Copy Project" session.
>>Conditions: When copying to an already existing project with the form input button "Project Master Schedule" set to
YES.

Solution: 159033
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
>>Problem: The option of calculating the sales price structure from within the product configurator should not be allowed, as
the variant needs to be validated on exiting the configurator before calculating the price.
>>Location: In the specific menu of the session "Product Configurator".
>>Conditions: During the process of configring the product variant.
>>Cause: The specific menu option of "calculating sales price structure" is available in the product configurator, and should
not be.
SOLUTION DESCRIPTION:
>>Resolution: The option of calculating the sales price structure is removed from the specific menu of the session "Product
Configurator".
>>Location: In the specific menu of the session "Product Configurator".
>>Conditions: During the process of configring the product variant.

Solution: 159037
SITUATION IDENTIFIED IN:
"Create Transactions from Schedule" (tfgld1204s000)
SITUATION DESCRIPTION:
Documents are not balanced when generating transactions using a transaction schedule. The message: "Document not
balanced" is given when attempting to exit the session.
SOLUTION DESCRIPTION:
Rounding was not being done when there were multiple lines on the transaction schedule and the total for these lines was less
than the entered transaction amount. Rounding was only being done if the total of the lines was greater than the entered
transaction amount and was ignoring if the total was less than the transaction amount. Now amounts will be rounded in both
cases (where the total of the lines is either greater than or less than the entered transaction amount) to ensure the document is
balanced.

Solution: 159080
SITUATION IDENTIFIED IN:
"Product Configurator" (tipcf5120m000)
SITUATION DESCRIPTION:
Certain feature defaults are not retained during the configuration process of a product variant.
When before input constraints are setting defaults to certain features and making them display only, the defaults are not
retained when returning back through the features after making them input ready.
SOLUTION DESCRIPTION:
The feature defaults are now retained during the configuration process of a product variant.

Solution: 159091
SITUATION IDENTIFIED IN:
"Version Scan Tool" (ttaad0500m000)
SITUATION DESCRIPTION:
NT batch files generated by VST would not execute properly.
SOLUTION DESCRIPTION:
The problem has been caused by a file-naming problem. The batch files generated by VST are now executing properly.
In addition, several fixes have been made to enhance the appearance and function of VST, including:
Correction of form field labels.
Messages for easier debugging of VST.
The ability to save and exit on every form of VST.
The previous output file is now read (this functionality had been removed earlier).
The IP address of application and database servers was not properly retrieved if VST was run on an HP server. This has been
corrected. As a result, the location of the output file has been hard coded into the program as $BSE/scan/output.vst

Solution: 159092
SITUATION IDENTIFIED IN:
"Tax Provider Calculation Utility" (tccom6212m000)
SITUATION DESCRIPTION:
When calculating tax rates via the session "Tax Provider Calculation Utility", the user is frequently prompted for the GEO
code even though it is not necessary.
SOLUTION DESCRIPTION:
When calculating tax rates, the addresses are checked to see if they have a valid city, state, postal code, and GEO code
combination. If so, then the tax is calculated provided no other errors are incurred. If the combination is incorrect, a message
is printed letting the user know which address is incorrect so it may be fixed.

Solution: 159093
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (Service)" (tfgld4103s000)
SITUATION DESCRIPTION:
The financial supplier group field in session "Integration Mapping Scheme (Service)" was not accessible or available for
Service Subcontracting records. Thus it was not possible to set up mapping to specific ledger accounts within finance.
SOLUTION DESCRIPTION:
The financial supplier group is now derived and passed to Finance for use in the Service mapping scheme session.
The financial supplier group field in the session "Integration Mapping Scheme (Service)" is now accessible for Service
Subcontracting records.

Solution: 159095
SITUATION IDENTIFIED IN:
"Remove Outbound Advice" (whinh4260m000)
SITUATION DESCRIPTION:
Session runs slowly for large whinh225 table.
SOLUTION DESCRIPTION:
Select outbound advice lines in a different manner.

Solution: 159099
SITUATION IDENTIFIED IN:
"Project Activity Network Planning" (tipcs4210m000)
SITUATION DESCRIPTION:
When network planning is run after the project plan start date and after hours have been logged against the project, the
reduced capacity is not shown to be realistic as compared to the rough capacity plan. The reduced capacity is proportionally
spread against the remainder of the project plan and does not show what actually is needed or not needed to be done in order
for the project to be back on schedule.
If the hours logged already against the project are under the required capacity, the reduced capacity is shown to be
over the planned capacity. If the hours logged are over the required capacity, the reduced capacity is shown to be under the planned capacity.
SOLUTION DESCRIPTION:
The reduced capacity is now shown to be realistic as compared to the rough capacity plan.
Any additional or reduced capacity required to re-align the needed work with the rough capacity plan will be shown in the week period following the run date.

Solution: 159108
SITUATION IDENTIFIED IN:
"Global Approval of Reserved Commissions/Rebates" (tdcms2202m000)
SITUATION DESCRIPTION:
The selection of reserved commissions for approval based on invoice date is not working. No matter what invoice date range
is entered in the session, all reserved commissions that meet the other selection criteria get approved, regardless of when
they were invoiced.
SOLUTION DESCRIPTION:
The program has been modified so that the invoice date range will be correctly considered while selecting reserved
commissions for approval.

Solution: 159115
SITUATION IDENTIFIED IN:
"Purchase-Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
When trying to delete a PO line with status 'Awaiting Receipts' in warehousing, fatal error 111 is generated.
SOLUTION DESCRIPTION:
Altered the manner in which deletions of the order advice line is handled to ensure proper deletion without errors.

Solution: 159128
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
Transactions with multiple tax were not printed correctly on the reports. A single line was being printed for the total of the
taxes and the net amount in home currency was incorrectly printed as zero.
SOLUTION DESCRIPTION:
The report layout has been modified so that transactions with multiple tax will generate a separate line for each tax and the
correct amount in home currency will be displayed.

Solution: 159129
SITUATION IDENTIFIED IN:
"Global Approval of Reserved Commissions/Rebates" (tdcms2202m000)
"Commissions Calculated by Order" (tdcms0150s000)
"Commissions Calculated by Order" (tdcms0550m000)
"Commissions Calculated by Relation" (tdcms1150s000)
"Commissions Calculated by Relation" (tdcms1550m000)
"Rebates Calculated by Order" (tdcms2150s000)
"Rebates Calculated by Order" (tdcms2550m000)
"Rebates Calculated by Relation" (tdcms3150s000)
"Rebates Calculated by Relation" (tdcms3550m000)
SITUATION DESCRIPTION:
Commissions/Rebates cannot be calculated/approved in a Multisite setup when the Commission/Rebate Calculation parameter
is set to "Paid Invoice". The following messages are received:
"No data within selection"
"Unable to determine invoice number for relation ****"
Where **** is the relation the commission/rebate is for.
SOLUTION DESCRIPTION:
Multiple sessions within CMS have been adjusted to align the multisite functionality with the rest of Baan. The CMS module
was not properly checking the financial company related to the sales orders when checking to see if the invoice has been
paid. This has now been corrected.

Solution: 159134
SITUATION IDENTIFIED IN:
"Report Library" (ttstprepdll)
SITUATION DESCRIPTION:
Printing a report setup as multicolumn vertical was not working correctly.
SOLUTION DESCRIPTION:
Changes were made so that we know how many rows should be printed for each record. This gives us better control over
positioning records on the page when printing multicolumn vertical.

Solution: 159136
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130m000)
SITUATION DESCRIPTION:
When using a tax provider, the user was constantly prompted to provide a valid GEO code even if a valid one was already
present.
SOLUTION DESCRIPTION:
When using a tax provider, a user is only prompted for a GEO code if the country, city, state or postal code is changed or if
the user chooses to change.

Solution: 159138
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
Duplicate commission records are created for already processed commissions during calculation on a range of sales orders.
SOLUTION DESCRIPTION:
The session has been modified so that commissions that have already been processed will not be calculated on subsequent
calculation runs.

Solution: 159139
SITUATION IDENTIFIED IN:
"Chart of Accounts" (tfgld0108s000)
SITUATION DESCRIPTION:
Problem #1- The user is unable to change the sublevel of a ledger account once the account has been used. This
functionality was present in prior BAAN versions (B40_c).
Problem #2- There was an error message that indicated that a parent and child ledger account can not have the same sublevel
but the program was allowing this.
Problem #3- There was an error check to make sure that a ledger account can not have its sublevel changed to be less than any
of its children's sublevel. There was no check to make sure that an account sublevel can not be changed to greater than its
parent.
SOLUTION DESCRIPTION:
-Changes have been made to allow ledger account sublevels to be changed if the account is used. It is not allowed to change
a 0 level account or change a parent to a 0 level if the account has been used. Also extra checks have been added so that
this process will work with complementary accounts.
-Programming has been added so it is no longer allowable to put a parent and its child with the same sublevel.
- A check has been added to make sure that when changing an account sublevel that the new sublevel can not be more than or
equal to its parent's sublevel.

Solution: 159215
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Order" (tdsls4244m000)
SITUATION DESCRIPTION:
On entering a generic item on a sales order line and then generating the project structure for this item, and then deleting
this sales line and re-entering another generic item and generating project structure for this item; the error message 'Project
X exists without being used in Sales Order X.' is received which blocks the entry of this new item.
This functionality as described above would effectively be the same as entering a second line on the sales order for another
generic item and then generating project structure for the second item, this second method is allowed.
SOLUTION DESCRIPTION:
The process of entering a new generic item on a sales order, generating structure, removing the item and re-entering the item
again on the same sales order and again generating project structure is now allowed.

Solution: 159224
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions, using the session "Post Integration Transactions to Finance Integrations"
(tfgld4201m000), some transactions erred with messages "Dimension XXX must be filled for ledger account YYYYYY" or
"Ledger Account not defined".
SOLUTION DESCRIPTION:
Integration transactions are now posted successfully .
After installing this Solution, install the solution 159697. Then, post integration transactions using the session "Post
Integration Transactions to Finance Transactions" (tfgld4201m000).

Solution: 159227
SITUATION IDENTIFIED IN:
"Print Goods Received Note" (whinh3412m000)
SITUATION DESCRIPTION:
Request for a more convenient way to display the appropriate variant information when receiving goods.
SOLUTION DESCRIPTION:
Option added to the Print Goods Received Note Session to allow for the printing of a new report that displays the variant
product information appropriate for an Inbound document

Solution: 159231
SITUATION IDENTIFIED IN:
"Recompute Phase Numbers" (cprpd6200m000)
SITUATION DESCRIPTION:
When running Recompute Phase Numbers in regenerative mode, the process encounters a Fatal Error 107 - Record is locked
error.
SOLUTION DESCRIPTION:
Made changes to the Recompute Phase Numbers process to avoid the Fatal Error 107. These changes corrected a problem
that was created by the solution 125054. When running Recompute Phase Numbers (including regenerative mode), items are
handled in sequence of generic, manufacturing and purchase items.

Solution: 159233
SITUATION IDENTIFIED IN:
"Unfinalize batches" (otfcor0313)
SITUATION DESCRIPTION:
The business partner and type of cash transaction fields are not filled when this correction program is run to un-finalize a
batch.
SOLUTION DESCRIPTION:
Changes have been made in the script to fill in the Business Partner (tfgld102.bpid) and Type of Cash Transaction
(tfgld102.tcsh) fields when the batches are un-finalized.

Solution: 159239
SITUATION IDENTIFIED IN:
"Price-List Matrices" (tipcf4120m000)
SITUATION DESCRIPTION:
When trying to find a specific record in Price-List Matrices, the user is only able to enter the price list matrix and not the
sequence number. This results in the first sequence number always being retrieved.
SOLUTION DESCRIPTION:
Now when finding a specific record in Price-List Matrices, the user is able to enter the price list matrix and the sequence
number.

Solution: 159242
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Even when the Planning Quantity or Planning Percentage for a Phantom Item in a Generic BOM is zero, the requirements are
still exploded to the components of the Phantom Item.
SOLUTION DESCRIPTION:
When the Planning Quantity or Planning Percentage for a Phantom Item in a Generic BOM is zero, the requirements will
not be exploded to the components of the Phantom Item.

Solution: 159244
SITUATION IDENTIFIED IN:
"Archive Costing History" (ticst2250m000)
SITUATION DESCRIPTION:
When re-opening a closed shop order of which the costing history data had been previously archived, and then logging
additional materials and hours to the shop order; and if the shop order is archived again, the newly created costing history
is not updated in the archived company. This results in erroneous costing history data.
SOLUTION DESCRIPTION:
Now when re-archiving the costing history data for a re-opened shop order, the newly created costing history data will be
correctly updated in the archive company.

Solution: 159248
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Erroneous financial integration entry was created for a cost component of type operation when shipping more than one line
for consignment inventory.
SOLUTION DESCRIPTION:
Changes made so that only the proper financial integration entries are create for type operation.

Solution: 159254
SITUATION IDENTIFIED IN:
"Correct Project and Financial Customer Group (tfgld415)" (tfcor4215m000)
SITUATION DESCRIPTION:
When posting integration transactions, using the session "Post Integration Transactions to Finance Integrations"
(tfgld4201m000), some transactions erred with messages "Dimension XXX must be filled for ledger account YYYYYY" or
"Ledger Account not defined".
This solution corrects the data related to these integration transactions so that they can be posted successfully .
SOLUTION DESCRIPTION:
After installing and running the Solution, Integration transactions can be posted
correctly
.
Please follow the following steps:
1. Before installing this Solution, install the Solutions
159224 and 159697. Solutions 159224 and 159697 fix
the problem so that the new integration transactions are
created correctly. Note the installation date
and time of Solution 159224. This will be required in
Step 3, to correct older integration transactions.
2. Run the session, "Post Integration Transactions to Finance Transactions" (tfgld4201m000) to post the integration
transactions.
3. Install the Solution 159254. Run the correction program "Correct Project and Financial Customer Group (tfgld415)"
(tfcor4215m000), up to the installation date and time in the step 1. That is, "Transaction
Date-To" must be equal the to installation date
and time. This will correct all the old integration transactions, prior to the installation of the Solution 159224.
4. Run session "Post Integration Transactions to Finance Transactions" (tfgld4201m000) to post the integration
transactions.

Solution: 159263
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When the order system is "Replenish to Maximum Inventory", the orders generated does not replenish to maximum inventory
when the maximum order quantity is less than the maximum inventory. For example: If the Maximum Order Quantity is 600
pcs and maximum Inventory is 1000 pcs and there is a demand for 10 pcs, then a supply is generated only for 550 pcs
instead of a supply of 1010 pcs.
SOLUTION DESCRIPTION:
When the order system is "Replenish to Maximum Inventory", orders are generated so that it is replenished to maximum
inventory even when the maximum order quantity is less than the maximum inventory. For example: If the Maximum Order
Quantity is 600 pcs and maximum Inventory is 1000 pcs and there is a demand for 10 pcs, then a supply is generated for 1010
pcs, but there are 2 orders, one for 600 pcs and another for 410 pcs.
NOTE: THIS BEHAVIOUR OF ORDER SPLITTING IS ONLY FOR PURCHASED ITEMS. FOR MANUFACTURED ITEMS (OR PRODUCTION
ORDER GENERATION), THE SYSTEM ONLY CREATES ONE ORDER, BUT GIVES A SIGNAL THAT THE ORDER QUANTITY IS
GREATER THAN THE MAXIMUM ORDER QUANTITY.

Solution: 159265
SITUATION IDENTIFIED IN:
"Global Approval of Reserved Commissions/Rebates" (tdcms2202m000)
SITUATION DESCRIPTION:
The selection of reserved rebates for approval based on invoice date is not working if the commission parameters are set for
commissions to be paid on order, rather than after invoicing or invoice payment.
SOLUTION DESCRIPTION:
The session was looking at the payment method for commissions and applying it to the rebates as well. If the commission
payment method was set to order, the invoice date was being ignored for rebates, even if the rebate payment method was set to
invoice or paid invoice. This has been corrected, so the rebate parameters will be used for rebates.

Solution: 159274
SITUATION IDENTIFIED IN:
"Tax Positions" (tfgld0120m000)
SITUATION DESCRIPTION:
When zooming to session tfgld0120m000 (Tax Position) the user must select save and close to get a value from the session.
SOLUTION DESCRIPTION:
If a session zooms to the session tfgld0120m000, a value is now correctly selected and returned.

Solution: 159288
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst0101s000)
SITUATION DESCRIPTION:
Under the following conditions:
1. The Inventory Handling Parameter, 'Correct SFC Production Order till' is set to 'Generate Outbound Advice' or 'Release
Outbound Advice'
2. In the Material to Issue for Production Orders (ticst0101s000) session the 'To Issue' field is updated to a negative value.
A Planned Inventory Receipt line for the material is created when the Planned Inventory Issue line should be updated
instead.
SOLUTION DESCRIPTION:
Under the above conditions, if a negative 'To Issue' quantity is processed, the Planned Inventory Issue line will be updated
accordingly.

Solution: 159292
SITUATION IDENTIFIED IN:
"Process Calls by Support Engineer" (tsclm1116m000)
SITUATION DESCRIPTION:
A serious performance problem occurs when attempting to open session "Process Calls by Support Engineer". In some
instances, 10-20 min. is used to open session.
SOLUTION DESCRIPTION:
The performance issue has been addressed. The session will now open within a reasonable time frame.

Solution: 159294
SITUATION IDENTIFIED IN:
"Archive Project" (tipcs2260m000)
SITUATION DESCRIPTION:
When archiving a project with related shop floor control data, and the input option "Project History" is not set, the shop
floor control related data is archived anyway. The session is ignoring the setting of the input option.
SOLUTION DESCRIPTION:
The session "Archive Project" now properly respects the setting of the input option "Project History".

Solution: 159295
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
When using agreements which have different commission percentages, based on grade, and calculating commissions for a sales
order line with split deliveries, the commission percentages are not correct.
SOLUTION DESCRIPTION:
The session was treating each split delivery detail as a separate line, rather than grouping them together. Because of this,
it was selecting commission percentages from the wrong grade categories. The commissions are still calculated individually
for the different split delivery detail lines, but the commission percentages used are based on the entire sales order line
amounts.

Solution: 159297
SITUATION IDENTIFIED IN:
"Production Planning Board" (tisfc1120m000)
SITUATION DESCRIPTION:
The item and project and their descriptions were possibly truncated on the planning board.
SOLUTION DESCRIPTION:
The item and project and their descriptions are now completely displayed on the planning board.

Solution: 159298
SITUATION IDENTIFIED IN:
"Finalization Run number" (tfgld1519m000)
SITUATION DESCRIPTION:
In case when transaction type update mode is "Real time" or "End of session" and document contains Tax, it was not
possible to finalize the batch because document was not balanced in one of the home currencies.
SOLUTION DESCRIPTION:
Now user will be able to finalize batch and finalization process will generate the correct rounding difference lines to
balance document in all home currencies.

Solution: 159302
SITUATION IDENTIFIED IN:
"ATP Handling" (tdsls4899m000)
SITUATION DESCRIPTION:
When two sales orders are made and the second sales order is split into 2 delivery lines (one with a delivery date within
the CTP time fence and another moved outside the family CTP time fence), the first sales order can no longer be moved to
a later date within the CTP Time fence and an error message is given "Quantity exceed Available ATP".
SOLUTION DESCRIPTION:
When the sales order is split based on the schedule proposal, the order detail line with a delivery date outside the Family CTP time fence period has a delivery date, which falls within the Family CTP Time Fence Period. Now, when the schedule proposal is done in ATP Handling, the system will move the sales order to the next period after the period in which Family CTP Time Horizon. The reason for this is that all ATP/CTP checks in Baan ERP are done based on periods for master planned items.

Solution: 159334
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130m000)
SITUATION DESCRIPTION:
When there is only one GEO code for a country, city, postal code, and state, no check is done to see if the GEO code is for
sales and use.
SOLUTION DESCRIPTION:
When only one GEO code exists for a country, city, postal code, and state, a check is done to see if the GEO code is fro
sales and use. If the GEO code is not valid for sales and use, the record cannot be saved.

Solution: 159348
SITUATION IDENTIFIED IN:
"Print References to Parent" (ttaad4229m000)
SITUATION DESCRIPTION:
In some cases an error 302 (Invalid SQL statement) occurs in session "Print References to Parent" (ttaad4229m000) due to
the length of the where clause generated.
SOLUTION DESCRIPTION:
This particular problem was fixed by increasing the variable LENGTH_WHERE_CLAUSE to 2048 from 1024.

Solution: 159354
SITUATION IDENTIFIED IN:
"Automatic Balancing of Profit and Loss Accounts" (tfgld6202m000)
SITUATION DESCRIPTION:
#1- Error messages were given when attempting to balance profit & loss accounts because there were opening balance
transactions to these accounts.
#2- If the process aborted because of errors, there was no way to run the session again without the use of general table
maintenance to remove the batch created before the errors were encountered.
SOLUTION DESCRIPTION:
#1 Profit & Loss accounts should never have an opening balance. It was found that if there was a rounding difference on an
opening balance batch that this rounding difference was posted into the account specified in the company parameters which is
a P&L account. Now the rounding difference account will not be used for opening balance transactions instead the last account
of the transaction will be used to store the rounding difference.
#2- Changes have been made to the session (tfgld6202m000) "Autobalancing of profit and loss" so that if the program errors
out that it can be rerun and the prior aborted batch will be removed automatically.

Solution: 159355
SITUATION IDENTIFIED IN:
"Change Default Values for Finalization" (tfgld1113s000)
SITUATION DESCRIPTION:
When finalizing a batch using a run number it is not possible to include the text in the journal output. A facility similar
to the one when re-printing journals (tfgld1410m000) should be made available.
SOLUTION DESCRIPTION:
After selecting a batch for finalization in session Select Batches for Finalization (tfgld1111s000) the user has the option to
over-ride the default values by zooming to session Change Default Values for Finalization (tfgld1113s000). In this session, a
new field has been added to the form to accept the user option of whether the text is to be printed in the journal report or not.
The default value of this field is "No". The user has the option of changing it to "Yes" and saving defaults if they always want
to print the associated text at finalization time.

Solution: 159356
SITUATION IDENTIFIED IN:
"Calculate Currency Differences" (tfgld5201m000)
SITUATION DESCRIPTION:
When running the session tfgld5201m000 (Calculate Currency Differences) if the report is executed a second time without
exiting and re-entering the session, the ledger account description may be incorrect.
SOLUTION DESCRIPTION:
The session will now produce the correct ledger account description with multiple runs.

Solution: 159360
SITUATION IDENTIFIED IN:
"Planned Orders" (cprrp1410m000)
SITUATION DESCRIPTION:
When entering the print Planned Orders session, cprrp1410m000, the system defaults the Start Date to field to the maximum
date value. When entering the print Planned Orders session from the Planned Orders session, cprrp1500m000, the system
assigns the start date of the scenario into the the Start Date to field. When this occurs, the system generally returns the
message "No Data within Selection" message.
SOLUTION DESCRIPTION:
When executing the print Planned Orders session for a single scenario (ie. for a scenario range of 'AAA' to 'AAA'), the system uses the scenario start
date in the Start Date from field and uses the scenario finish date in the Start Date to field. Similarly, the From Date from field is updated with the
scenario start date and the From Date to field is updated with the scenario finish date.
When executing the print Planned Orders session for a range of scenarios (ie. for a scenario range of 'AAA' to 'BBB'), the system leaves the Start Date
from field blank and uses the maximum date value in the Start Date to field. Similarly, the system leaves the From Date from field blank and uses the maximum date value in the From Date to field. In either situation, the user can change the dates for a specific date range.

Solution: 159363
SITUATION IDENTIFIED IN:
"Version Scan Tool" (ttaad0500m000)
SITUATION DESCRIPTION:
While running version scan tool on an NT system, two significant problems occurred: The NT version was only retrieved
properly for Windows 2000; and the Oracle version was not retrieved.
SOLUTION DESCRIPTION:
A condition statement checks the output of the "ver" and determines NT version based upon the amount of output given.
The Oracle version was not being checked because the "export" command was being used instead of the "set" command.
This caused ORACLE_HOME not to be set, and therefore sqlplus could not be found.

Solution: 159371
SITUATION IDENTIFIED IN:
"Delete Integration transactions" (tfcor0223/tfcor1223)
SITUATION DESCRIPTION:
Correction program (tfcor0223 - B40, tfcor1223 - B50) deletes transaction lines, which are present in the same batch with
the same document number but with a different transaction type. This happens only when user selects to delete transaction
from Non-Finalized Transactions (tfgld102) table.
SOLUTION DESCRIPTION:
The selection criteria on the data from the non-finalized table was wrong. This led to the above error. Now the program only deletes transactions which are in the user entered range, defined on the form.

Solution: 159391
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
When printing the summary report by fiscal period the report fails to print the amounts in "Net Amnt." and "Net Amnt in
HC" for transactions of type "Cash".
SOLUTION DESCRIPTION:
The report was suppressing the "Cash" type records. This has been corrected.

Solution: 159394
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
Unable to print all lines on Packing Slip
SOLUTION DESCRIPTION:
Due a technical problem sometimes not all lines where printed on a packing slip which has been adapted.

Solution: 159407
SITUATION IDENTIFIED IN:
"Archive Projects" (tipcs2260m000)
SITUATION DESCRIPTION:
The production costing history data for a project related shop floor order is not being archived or deleted when the project is
archived. This is where the costing history data should be archived and deleted, so as to properly control the volume of this
data.
SOLUTION DESCRIPTION:
The production costing history data is now being properly archived and removed during the process of archiving projects.
The form input "Project History" button now controls the archiving part of the costing history, and the data is always
removed (from the source company) during project archiving.

Solution: 159412
SITUATION IDENTIFIED IN:
"Integration Transactions by Project/Order" (tfgld4510m000)
SITUATION DESCRIPTION:
Service item and service item group cannot be mapped to the debit side of a transaction when a subcontracting item is used
on the service order.
SOLUTION DESCRIPTION:
When the user has a subcontracting cost on a service order, a mapping scheme can now be created where service item and
service item group are on the debit side of the transaction and regular item and item group is on the credit side.

Solution: 159413
SITUATION IDENTIFIED IN:
"Check/change Rounding of Amounts" (tfcor9996s000)
SITUATION DESCRIPTION:
Several problems have been fixed in the correction program that rounds finance amounts according to domain.
Problem #1-(All versions)- After running this program it is possible that finalized transactions are out of balance due to
rounding. It has been requested that a report be created to identify these transactions so that they can be adjusted before the
problems are discovered while closing periods or years.
Problem #2(B50_c only)- The report printed after running the correction program did not print transaction type.
Problem #3(B50__c only)- Whenever you print the report
the old amount and new amount are always the same.
Problem #4 (B50_b and B50_c)- When running the report for
finalized transactions in print only mode the report does display the period status.
Problem #5-(B50_b)- The report would always print in English even when running the session in other languages.
Problem #6-(B50_c) Some labels in the report header do not print in languages other than English.
SOLUTION DESCRIPTION:
#1- A new report is now generated by the session that displays what documents are out of balance after rounding. This should
be looked at closely as these transactions need to be fixed manually.
#2 Problems on the report have been corrected so that transaction type is now printed.
#3- Due to a formatting problem the old amount and new amount were always shown as the same. This has been changed to
show the correct old and new amounts.
#4- The period status is now shown when running the program in report only mode.
#5- The report has been changed (in B50_b) to print in languages other than English.
#6- Some labels that existed in English only have been translated to the other A-languages and included as part of this
solution.

Solution: 159421
SITUATION IDENTIFIED IN:
"Insert Missing tfgld109 records in Archive Company" (tfcor6205m000)
SITUATION DESCRIPTION:
The Archive and Purge Session tfgld6205m000 had a problem wherein the Finalization Run Number Status table (tfgld109)
was purged but not archived. This problem was corrected by SOL 158611. A correction program is now needed to create the
missing records in table tfgld109 in the archive company.
SOLUTION DESCRIPTION:
A correction session tfcor6205m000 is being delivered in this solution. This correction program reads data from the Batch
Status table (tfgld100) and populates the Finalization Run Number Status table (tfgld109). Not all fields will have values in
the recreated records. Please read the session help for further information. Please run this session only in an archive
company.

Solution: 159428
SITUATION IDENTIFIED IN:
"Global Selection of Batches for Finalization" (tfgld1210m000)
SITUATION DESCRIPTION:
Focus is missing after the start-up of the session. A mouse click on an input field is required to enable processing in this
session.
SOLUTION DESCRIPTION:
The cursor defaults to the "Year" field when the session is started.

Solution: 159433
SITUATION IDENTIFIED IN:
"Print Sales Statistics" (tdsst0401m000)
SITUATION DESCRIPTION:
The print statistics report cumulated the quantity or the amount instead of printing in different lines. This happened when
printing for a range of items whose item code length were greater than 16 characters.
SOLUTION DESCRIPTION:
The report now correctly prints in different lines for all items irrespective of their length.

Solution: 159439
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 integration parameter (tfgld4150s000) "Posting to Next Open Period Allowed" is set -
transactions can be posted into closed periods.
SOLUTION DESCRIPTION:
The process tfglddll4010 (Write transactions in integration tables) has been modified to properly handle posting transactions to the correct period.

Solution: 159446
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000)
"Sales Order Line Details" (tdsls4501m200)
SITUATION DESCRIPTION:
It is not possible to link manually a relation "Relations by Order Line" (tdcms041m000) to a sales order detail line
(tdsls4501m200) via specific from the menu bar.
SOLUTION DESCRIPTION:
In the session "Sales Order Lines" (tdsls4501m000), the zoom option for the session "Relations by Order Line"
(tdcms0141m000) will be disabled if the sales order line is a split delivery line. In this situation, the zoom option for
"Relations by Order Line" (tdcms0141m000) is added to the session "Sales Order Line Details" (tdsls4501m200).

Solution: 159452
SITUATION IDENTIFIED IN:
"Sales Statistics(Graphical)" (tdsst0701m000)
SITUATION DESCRIPTION:
The period numbers with 3 digits were displayed as # in the third form of the session Sales Statistics (Graphical).
SOLUTION DESCRIPTION:
The period numbers are now correctly displayed.

Solution: 159467
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
The Simulate Orders has to run twice for Master Planned Items, before planned orders could be generated. Running
simulate orders the first time updates the "Non Consumed Demand Forecast" and running a second time generates planned
orders.
SOLUTION DESCRIPTION:
Simulate Orders will consume demand forecast and generate planned orders during the first run.

Solution: 159491
SITUATION IDENTIFIED IN:
"Version Scan Tool" (ttaad0500m000)
SITUATION DESCRIPTION:
Due to the method in which environment variables were set, the Informix version was not properly retrieved.
SOLUTION DESCRIPTION:
The Informix variables are now explicitly set.

Solution: 159507
SITUATION IDENTIFIED IN:
"Print Integration Transactions" (tfgld4410m000)
SITUATION DESCRIPTION:
The following problems were reported in the session.
1. (B40c only) If a non-existing company is entered in the session and one tries to zoom on the order field then a
runtime BW error 506 Table tfgld000XXX does not exist is given where XXX is the company entered.
2. When (Graphical User Interface only) no 'from' and 'to' Transactions Origin are specified and a user tries to zoom on the
order field, a message is given saying "No Zoom Session defined". After the "OK" button is clicked, the mouse pointer
remains at hourglass indicating that the system is busy when actually it is waiting for customer input.
3. When zooming on order number, orders for the wrong company were displayed. This happens when the original company
specified is not the company from which the session is being run in.
SOLUTION DESCRIPTION:
1. A check has been added to the program to make sure a valid company is entered by the user. If the user does not have
authorizations to the company or the company does not exist then an error message is displayed.
2. It is only possible to zoom on the order field of this session if the from original company = to original company and from
transaction origin = to transaction origin. When these conditions are not satisfied, the session will not zoom.
3. Changes have been made to the program so that it will now display orders/projects from the 'from company' on the form.

Solution: 159509
SITUATION IDENTIFIED IN:
"Check/change rounding of Amounts" (tfcor9996s000)
SITUATION DESCRIPTION:
When running the session the values for 'new amount' did not always print correctly even though the rounding was done
correctly. For example, the report could display 104 when the actual new amount was 104.02.
SOLUTION DESCRIPTION:
The problem occurred because the report field for new amount did not specify which currency format should be used. Thus
the default currency format was always used which could result in the value being printed with too few or too many decimal
places. Now depending the currency being printed for new amount (transaction currency or home currency) is being used by
the report to determine the correct currency format.

Solution: 159510
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates on Cumulative Sales" (tdcms1200m000)
SITUATION DESCRIPTION:
When calculating commissions the sales invoice number is being update in the Cumulative Sales (tdcms100) and the
Commissions/Rebates (tdcms050) tables but the invoice date is not being added until the commission is being set to
approved. This should be done when the invoice number is inserted/updated.
SOLUTION DESCRIPTION:
The commissions libraries have been modified to update the Cumulative Sales (tdcms100) and the Commissions/Rebates (tdcms050) tables with the Invoice Date at the same time that the invoice number is added.

Solution: 159525
SITUATION IDENTIFIED IN:
"Archive Projects" (tipcs2260m000)
SITUATION DESCRIPTION:
A project with parameter "engineering allowed" set to NO, is not archived properly. The status of the project is not set to
archived even though an archived record for the project does exist, and the original project is not removed.
SOLUTION DESCRIPTION:
Now a project with parameter "engineering allowed" set to NO, is archived properly and the original project is also kept and
not removed. This is the desired functionality.

Solution: 159526
SITUATION IDENTIFIED IN:
"Import Journal Vouchers by Batch ID Number" (tfgld2215m000)
SITUATION DESCRIPTION:
When importing journal vouchers with session tfgld2215m000 (Import Journal Vouchers by Batch ID Number), if any of the
transaction lines have errors, then only lines which do not have errors are imported into the General Ledger. In such a
situation the interim tables were also cleared forcing the user to re-import data into Baan and cleaning up the data which
was successfully imported into the General Ledger.
SOLUTION DESCRIPTION:
An audit capability has now been implemented in this session. The audit will allow users to validate an import batch before the journal voucher transactions are actually loaded into the General Ledger. The audit will produce a detailed error report and allow users to make corrections to import data. Further, a progress indicator has been added to provide visual feedback on the import process.

Solution: 159528
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
Erroneous financial integration entry was created for a cost component of type operation when shipping more than one line
for consignment inventory.
SOLUTION DESCRIPTION:
Correction program whcor2204m000 written to identify erroneous transactions. Transactions which have cost components of
type operation for a receipt transaction are flagged for manual correction.

Solution: 159546
SITUATION IDENTIFIED IN:
"Print Trial Balance" (tfgld3402m000)
SITUATION DESCRIPTION:
Additional flexibility is needed in the Trial Balance session to allow the user to input both a complementary and statutory
sublevel print range.
SOLUTION DESCRIPTION:
With Solution 159546, modifications have been made to the sessions Print Trial Balance (tfgld3402m000) and Print Trial
Balance by Currency (tfgld3403m000), which will increase the flexibility of the reports. These modifications will only
directly impact those customers that are utilizing the dual accounting functionality in their general ledger set up. This
functionality allows users to define their accounts as either statutory(for fiscal reporting) or complementary(for management
reporting).
The following are the characteristics of these accounts: complementary accounts defined as sublevel 0 can only be linked to a complementary parent. Statutory accounts defined as sublevel 0 can be linked to either a complementary or a statutory parent (or both). This means that a parent level complementary account can carry a balance that is made up of both complementary and statutory activity.
When running these sessions, it is possible for the user to indicate that they want to print statutory balances, complementary balances, or both balances for specified ledger accounts. With this enhancement, when the user specifies that they want to print both, it is now possible for them to specify a sublevel range for both complementary and statutory accounts. The link below is to an Excel document that contains examples of the output you can expect when printing both, complementary only, or statutory only.
ftp://ftp.support.baan.com/updates/Documents/SOL159546Examples

Solution: 159554
SITUATION IDENTIFIED IN:
"Generate Network Planning" (tipcs4210m000)
SITUATION DESCRIPTION:
When generating project network planning for a project with activities that have different work centers, which also are linked
to different calendars, and there exist activity relationships; the planning does not consider the differences between the
calendars with respect to the activity relationships.
Though the project network planning functionality had included the use of multiple work center calendars, as opposed to just using a single company calendar, the internal logic did not take into account the actual work time differences within the calendars.
SOLUTION DESCRIPTION:
Generating project network planning now considers differences between work center calendars with respect to the activity relationships. This solution basically applies new functionality within the project network planning logic.
The new functionality being that when multiple calendars are used in the project network planning (via work centers), the difference between the
calendars is taken into account when the planning dates are determined. Prior to this new functionality, only a single company calendar was able to be used in the network planning.
Also as part of this solution, the time was added to the project start and end dates on project details form to further allow for a more precise control in the network planning process.
Solution: 159578
SITUATION IDENTIFIED IN:
"DDC Monitor" (tuddcmonitor)
SITUATION DESCRIPTION:
The ddc monitor was not shutting down when the function server went away.
SOLUTION DESCRIPTION:
Changed how monitor was processing events along with how function servers sent events to the monitor.

Solution: 159592
SITUATION IDENTIFIED IN:
"Create Session DLL" (ttstpcreatdll)
SITUATION DESCRIPTION:
Non-standard function names were being generated causing user to have to go in and change them manually.
SOLUTION DESCRIPTION:
If a label isn't associated with a form field and the field is a table field then we can also check the table for a description.
If after replacing invalid characters all we have left is spaces, then just use the field name. Lastly, use the package of the
form when grabbing labels.

Solution: 159600
SITUATION IDENTIFIED IN:
"Production Orders" (tisfc0101s000)
SITUATION DESCRIPTION:
When creating a production order for an item with a unit type of pieces, the scrap factor percentage got incorrectly rounded
to the whole value. For example, a scrap factor percentage of 26.75% got rounded to 27% for the estimated materials.
SOLUTION DESCRIPTION:
The scrap factor percentage is now not rounded anymore to the whole value.

Solution: 159608
SITUATION IDENTIFIED IN:
"Simulate orders" (cprrp1210m000)
SITUATION DESCRIPTION:
Problem: With only inventory on hand, a signal, "Order not Multiple of" is generated.
Location: Signals generated while running Simulate orders "cprrp1210m000"
Condition: A Closed inventory-adjustment putting stock in for the item, which not a multiple of quantity stated for that
warehouse.
SOLUTION DESCRIPTION:
Order signals will not be generated if no order exist.

Solution: 159610
SITUATION IDENTIFIED IN:
"Production Planning" (tisfc1500m000)
SITUATION DESCRIPTION:
When starting the 'Production Planning' (tisfc1500m000) session from the 'Production Order' (tisfc0501m000) session and the
order does not have any operations, then the button to add a new operation was not correctly disabled/enabled. As a result,
after entering the new operation data and trying to save the record the following error message was displayed "The Data
Access Layer does not allow the operation New on table tisfc010".
SOLUTION DESCRIPTION:
The button to add a new operation is now correctly disabled/enabled in the 'Production Planning' (tisfc1500m000) session.

Solution: 159615
SITUATION IDENTIFIED IN:
"Period Status" (tfgld0107m000)
SITUATION DESCRIPTION:
When using session tfgld0107m000 (Period Status) to modify a period status, it was possible to set the status of ACR, ACP,
CMG, or INT to "open" and then set the status of GLD to "closed " and save. The session allowed this if the module status
was not saved between individual module status changes.
SOLUTION DESCRIPTION:
The session tfgld0107m000 (Period Status) will now prevent a module status from being set to "open" if the GLD status has
been set to "closed".

Solution: 159621
SITUATION IDENTIFIED IN:
"Backflush Materials and Hours" (tisfc0220m000)
SITUATION DESCRIPTION:
When the program is selecting records to backflush, an Oracle error 1719 occurs.
SOLUTION DESCRIPTION:
The portion of the code that selected the records to backflush, was not compatible with all versions of Baan. This was
changed to produce the same results in backflushing as well as be compatible with all versions of Baan.

Solution: 159624
SITUATION IDENTIFIED IN:
"Global Selection of Batches for Finalization" (tfgld1210m100)
SITUATION DESCRIPTION:
When zooming on Batch Number field, the session gives the error message 506 (Table does not exist). This happens when
the session is run from the Menu: 'File-Run Program'.
SOLUTION DESCRIPTION:
This session is meant to be started from another session, namely, "Finalization Run Numbers" (tfgld1519m000). The session
cannot be started as an independent session.
If the session is now started from the Menu: 'File-Run Program', the error message "This session can only be started via
another session" is given.

Solution: 159625
SITUATION IDENTIFIED IN:
"Business Partners" (tccom4500m000)
SITUATION DESCRIPTION:
In the specific multi company setup, where the 'Business Partners' (tccom100) table is shared between the logistical and
finance companies and some or all of the roles by business partner tables are not shared, the 'Search Key' (seak) field was
not updated in all linked companies in the roles by business partner tables when changing it for a business partner.
SOLUTION DESCRIPTION:
The 'Search Key' (seak) field is now updated in all linked companies in the role by business partner tables when changing it
for a business partner.

Solution: 159632
SITUATION IDENTIFIED IN:
"Version Scan Tool" (VST)
SITUATION DESCRIPTION:
When exporting help text SEaad0500m000 from a Japanese system, the "bullet" characters in the text cause an error, since
they are illegal characters outside the ISO8859-1 character set.
SOLUTION DESCRIPTION:
The bullets have been replaced by legal characters.

Solution: 159635
SITUATION IDENTIFIED IN:
"Chart Of Accounts" (tfgld0108s000)
SITUATION DESCRIPTION:
It was not possible to change the print sequence for parent ledger accounts when transactions existed for the account. An
error was given 'Ledger account present in history'.
The error was given because of an incorrect check on sublevel even though the account sublevel was not changed.
SOLUTION DESCRIPTION:
It its now possible to change print sequence even if there are transactions made to the ledger account.

Solution: 159638
SITUATION IDENTIFIED IN:
"Generate Subcontracting Purchase Orders" (tisfc2250m000)
SITUATION DESCRIPTION:
When processing a production order for an item, that includes in its bill of materials a phantom item with a subcontracted
operation, the session Generate Subcontracting Purchase Orders (tisfc2250m000) incorrectly creates a purchase order for
the quantity of the end item and not the quantity of the phantom component.
SOLUTION DESCRIPTION:
Now when the Generate Subcontracting Purchase Orders session is run under the conditions above, the resulting purchase order is correctly created for
the quantity of the phantom item in the production item's bill of materials. Additionally, estimated end item unit costs, operation costs, completion and
variance posting calculations have been modified to reflect the correct subcontracting quantity.

Solution: 159646
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When Vertex is unable to calculate tax during the compose process, no exception report is given or the error message given
in the exception report is incorrect. This was due to the error message not being populated when tax cannot be calculated.
SOLUTION DESCRIPTION:
The error message is now populated with a message indicating tax cannot be calculated, so the exception report is generated
with the correct message.

Solution: 159647
SITUATION IDENTIFIED IN:
"Resource Master Plan" (cprmp3501m000)
SITUATION DESCRIPTION:
When attempting to start the Resource Master Plan session, cprmp3501m000, using a scenario that is expired (the finish date
of the scenario is in the past), the system displays the error message "Error in cprmpdll0001: Date to cannot be greater
than plan end date". The system is issuing this message while attempting to recompute the capacity available to promise
quantity. When the user clicks OK, the system closes the session without completely opening the session.
SOLUTION DESCRIPTION:
When the Resource Master Plan session is being opened using a scenario with a finish date in the past, the finish date of the
scenario is used by planning to recompute the capacity available to promise quantity. By using the finish date of the scenario,
the error situation is avoided and the session is allowed to open correctly.

Solution: 159650
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130s000)
SITUATION DESCRIPTION:
For North American Taxware users who modify the city, state, zip code, or country, they are not prompted to select a new
geo code.
SOLUTION DESCRIPTION:
Now when the city, state, zip code, or country, is changed in the session "Addresses", the user is forced to enter a new geo
code.

Solution: 159652
SITUATION IDENTIFIED IN:
"Simulate Orders" (cprrp1210m000)
SITUATION DESCRIPTION:
When running the session 'Simulate Orders' (cprrp1210m000) with 'Parallel Processing', it was possible that the session
never ended when one of the additional bshells (servers) stopped responding.
SOLUTION DESCRIPTION:
When running the session 'Simulate Orders' (cprrp1210m000) with 'Parallel Processing', the additional bshells (server) are
now checked for timeouts. In case that an additional bshell (servers) stops responding, an error message is issued and the
session ends. The error message is also logged in the 'Job History Messages' (ttaad5512m000).

Solution: 159655
SITUATION IDENTIFIED IN:
"Select Batches For Finalization" (tfgld1111s000)
SITUATION DESCRIPTION:
The session starts very slowly. This is caused by an inefficient query on the Batch Status (tfgld100) and the Transaction
Type Batch Status (tfgld101) tables when initializing the form.
SOLUTION DESCRIPTION:
The inefficient query has been rewritten.

Solution: 159663
SITUATION IDENTIFIED IN:
"Object Relations" (tscfg2510m000)
SITUATION DESCRIPTION:
When "zooming down" an object relation where a child exists, the find selection does not have the correct default
information and the "zoom up" selection is not available.
SOLUTION DESCRIPTION:
When "zooming down" an object relation where a child exists, the find selection now defaults the correct information and the
"zoom up" selection is available.

Solution: 159667
SITUATION IDENTIFIED IN:
"Service Orders: Actual Other Costs" (tssoc2141s000)
SITUATION DESCRIPTION:
When processing service order integrations the user finds that the country of the invoice-to business partner is being used
instead of the country entered on the service order header.
SOLUTION DESCRIPTION:
Now when a service order is being processed through integrations, the country on the service order header is being used.

Solution: 159685
SITUATION IDENTIFIED IN:
"Print and/or Delete Cumulative Sales for Comm./Rebts" (tdcms1400m000)
SITUATION DESCRIPTION:
When printing cumulative commissions/rebates, it was not possible to select on a range of business partners, because the
fields would only allow the user to input up to six characters. The input length should be nine for business partner. Also,
even if a specific range of commissions/rebates is specified, the session prints all commissions/rebates.
Finally, the customer would like to be able to zoom to this print session from the sessions tdcms1500m000 and tdcms1505m000.
SOLUTION DESCRIPTION:
The session was modified to allow nine characters of input for the business partner range fields. It was also modified to
correctly print the selected range of commissions/rebates, rather than printing all of them.
The requested zoom option has been added. It will now be possible to zoom to tdcms1400m000 from either session tdcms1500m000 or tdcms1505m000, by using the zoom option from the special menu at the top of the form.

Solution: 159693
SITUATION IDENTIFIED IN:
"Service Orders" (tssoc2100s000)
SITUATION DESCRIPTION:
The sales representative on service quotations, service contracts, and service orders is not being properly defaulted when
entering a new quotation/contract/order or making changes to existing one where the sales representative might be changed
by default.
SOLUTION DESCRIPTION:
When entering a new quotation/contract/order or modifying an existing one, the sales representative is now being properly
defaulted. The derivation structure is as follows:
For quotations/contracts:
The sales rep on the Service User Defaults is used. If sales rep is not found, the external sales rep on the sold-to business
partner is used. If sales rep is still not found, the internal sales rep on the sold-to business partner is used.
For service orders:
The sales rep on the Service User Defaults is used. If sales rep is not found, check the service order for contract and use the
sales rep on the contract. If sales rep is still not found, the external sales rep on the sold-to business partner is used. If sales
rep is still not found, the internal sales rep on the sold-to business partner is used.

Solution: 159695
SITUATION IDENTIFIED IN:
"Archive Project" (tipcs2260m000)
SITUATION DESCRIPTION:
When archiving projects, the sales and purchasing orders related to the project are automatically removed. This is
incorrect. The removal of the sales and purchasing project related orders should be handled within "Process Delivered
Sales Orders" and "Process Delivered Purchase Orders".
SOLUTION DESCRIPTION:
Now sales and purchasing orders are not automatically removed when archiving projects.
The reason for not removing sales and purchase orders via session "Archive Project" is the fact that those orders might be
needed for analysis of GRINYA (Goods Received, Invoice Not Yet Approved) or for reconciliation of logistical and
financial data.

Solution: 159715
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When a mapping scheme is defined in session Integration Mapping Scheme (CMS) (tfgld4104s000) and one of the key
definitions is for field "Relation", the posting program is not able to use this mapping scheme. This happens when the field
"Relation" contains a value 9 characters in length.
SOLUTION DESCRIPTION:
This problem happened because one of the internal variables in the program could only receive values up to 8 characters in
length. Thus the value of "Relation" got truncated and when reading the mapping scheme the truncated value was being
checked for, leading the posting session to believe that no mapping was defined. The program variable has been corrected to
receive 9 character values.

Solution: 159718
SITUATION IDENTIFIED IN:
"Select Device" (ttstpsplopen)
SITUATION DESCRIPTION:
When a default margin had been saved, leaving the device field would reset the margin.
SOLUTION DESCRIPTION:
Made it so we will only reset the margin if the device changes.

Solution: 159719
SITUATION IDENTIFIED IN:
"Print Service Order History" (tssoc8450m000)
SITUATION DESCRIPTION:
A blank page was printing in advance of service order history report.
SOLUTION DESCRIPTION:
The report definition has been modified so that every service order in history is printed on a new page.
The blank page will not be printed at the beginning of the report anymore.

Solution: 159724
SITUATION IDENTIFIED IN:
"Shift Production Planning" (tisfc1202m000)
SITUATION DESCRIPTION:
The help text for the session 'Shift Production Planning' (tisfc1202m000) was incorrectly explaining that the 'Moving
Method Operations' from the session 'Production Orders' (tisfc0101s000) would be used when shifting a production order.
The 'Moving Method Operations' is only used when shifting on the operations level and not when shifting on the production
order level.
SOLUTION DESCRIPTION:
The help text for the session 'Shift Production Planning' (tisfc1202m000) has been corrected to explain the use of the
'Moving Method Operations'.

Solution: 159735
SITUATION IDENTIFIED IN:
"Saes-Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Allocated quantity for item with lot by unit allow to exceed one.
SOLUTION DESCRIPTION:
Changed to reject order lines that would increase either the allocated or on order values beyond one for an item which is lot
controlled by unit.

Solution: 159737
SITUATION IDENTIFIED IN:
"Geenrate Project Structure for Sales Order" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating project structure for sales order for a non generic, to order phantom item, the error "Product variant 0 does
not exist" is encountered.
SOLUTION DESCRIPTION:
Project structure for sales order can now be generated for a non generic, to order phantom item without error.

Solution: 159743
SITUATION IDENTIFIED IN:
"tfgld2102s000" (Maintain Intergroup Transactions )
SITUATION DESCRIPTION:
When creating intergroup transactions if the user does not have permission in the target company the following errors
occurred:
#1- The created transactions use the currency rates from the source company instead of target company. (B40_c Only)
#2- The dimension type description displayed on the form was for the source company instead of target company.
#3- The group company of the target company was not read correctly.
#4- The session would give a no permission error when zooming to display a ledger account but would allow zooming ( to
the wrong company) on select dimensions types.
SOLUTION DESCRIPTION:
Changes have been made to get the correct currency rates, dimension type descriptions, and target group company when the
user does not have permissions in the target company. Also the zoom functionality for selecting dimensions has been
modified to work the same as on ledger account in that the zoom will be done in the target company and an error 'no
permission' will be given if a user attempts to zoom when having no permission in the target company.

Solution: 159762
SITUATION IDENTIFIED IN:
"Print Trial Balance" (tfgld3402m000)
SITUATION DESCRIPTION:
When printing quantities in the trial balance report, the complementary and statutory sublevel ranges entered in the selection
criteria are not printed in the report header.
SOLUTION DESCRIPTION:
Modifications have been made so that the complementary and statutory sublevel ranges entered by the user will be printed in
the header of the report.

Solution: 159765
SITUATION IDENTIFIED IN:
"Report Orders Completed" (tisfc0120s000)
SITUATION DESCRIPTION:
The default answer to the question 'Total Qty Reported is more than...' (tisfc012001) was hard coded to 'Yes'. The
default value should be taken from the question definition.
SOLUTION DESCRIPTION:
The default answer to the question 'Total Qty Reported is more than...' (tisfc012001) is now taken from the
question definition.

Solution: 159767
SITUATION IDENTIFIED IN:
"Item Master Plan" (cprmp2101m000)
SITUATION DESCRIPTION:
Demand forecast for a main item is causing CTP reservations for the components.
SOLUTION DESCRIPTION:
Only actual demand should cause the CTP reservations for components.

Solution: 159775
SITUATION IDENTIFIED IN:
"Print References to Parent" (ttaad4229m000)
SITUATION DESCRIPTION:
In the session Print References to Parent, invalid SQL queries were being generated. This caused error 302 in the session.
SOLUTION DESCRIPTION:
The amount of space allocated for the where clause in the generated query has been extended, resulting in a valid query.

Solution: 159785
SITUATION IDENTIFIED IN:
"Execute Query" (ttadv3280m000)
SITUATION DESCRIPTION:
When a user zooms to ttadv3280m000 from ttadv3580m000, the company number in ttadv3280m000 is set to 000, regardless
of the user's current company number.
SOLUTION DESCRIPTION:
While there is an option to change the company number in ttadv3280m000, it is more convenient for the user if their default
company is set automatically. This solution provides a fix that will set the company number to the user's current company
on zoom.

Solution: 159806
SITUATION IDENTIFIED IN:
"Conversion Factors" (tcibd0103m000)
SITUATION DESCRIPTION:
Instead of displaying the conversion factor between the base unit and the unit in the status line of the session, the text 'sfs'
was shown for the Dutch language.
SOLUTION DESCRIPTION:
This solution delivers the Dutch message to correctly display the conversion factor between the base unit and the unit in the
status line of the session.

Solution: 159808
SITUATION IDENTIFIED IN:
"Maintain Planned Orders/Simulate Orders" (cprrp1110s000/cprrp1210m000)
SITUATION DESCRIPTION:
If the main item has a different routing unit from its sub-item, which is a phantom, the production time for the operation of
the phantom item is calculated incorrectly. The routing unit of the main item is incorrectly used when planning for the
phantom item.
SOLUTION DESCRIPTION:
If the main item has a different routing unit from its sub-item which is a phantom, the production time for the operation of
the phantom item is calculated based on the routing unit of the phantom item. Thus the production time will be calculated
correctly.

Solution: 159816
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
In finance you can choose which ledger accounts you want to map your financial integrations to. It is possible to map the
production/completion integration to the warehouse. The warehouse is not being populated when logging financial
integrations for production/completion. Therefore, the user receives and error message when posting to finance.
SOLUTION DESCRIPTION:
The warehouse is now being populated with the main warehouse of the SFC production order on the integration. This allows
for proper mapping when posting to finance.

Solution: 159840
SITUATION IDENTIFIED IN:
"Print Goods Received Note" (whinh3412m000)
SITUATION DESCRIPTION:
No helptext for new checkbox 'Print Variant Option Descriptions'
SOLUTION DESCRIPTION:
Linked new helptext to the form.

Solution: 159847
SITUATION IDENTIFIED IN:
"Integration Relations by Range" (tfgld4124s000)
SITUATION DESCRIPTION:
When the session "Integration Relations by Range" (tfgld4124s000) is launched from the session "Options by Integration
Element" (tfgld4121m000), a format overflow error is issued and this error is logged to the file log.bshell. The specific
error message is "Overflow: format='ZZZZ9' value='-32768'". This is caused by incorrect initialization of the variable
tfgld424.sern.
SOLUTION DESCRIPTION:
The problem is now solved and the error is message is not issued anymore.

Solution: 159887
SITUATION IDENTIFIED IN:
"General Item Data Defaults" (tcibd0502m000)
SITUATION DESCRIPTION:
When copying the general item data defaults, the existing sub entity defaults are not copied.
SOLUTION DESCRIPTION:
Now when copying the general item data defaults, the existing sub entity defaults are copied.

Solution: 159888
SITUATION IDENTIFIED IN:
"Maintain Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
Batch numbers are not incremented correctly which can lead to a couple of problems
1. Batches belonging to different users could get combined into a single batch.
2. Error message "Transaction already finalized" is given while trying to insert a transaction type for a new batch.
This problem would occur if a user enters a batch header then chooses to change to a different batch header, but does not
have permissions for any other batch. The control would stay with the newly entered batch header. If the user creates
transactions in this batch, the system does not recognize it as a new batch.
SOLUTION DESCRIPTION:
Changes have been made in the program so that batch numbers are incremented correctly.

Solution: 159889
SITUATION IDENTIFIED IN:
"Print Tax Summary by Tax Authorities" (tfgld8401m000)
SITUATION DESCRIPTION:
Transactions with multiple shifted tax are not printed properly on the report. The amount in home currency is sometimes
showing as a negative, and the transaction lines are not sorted correctly by tax authority.
SOLUTION DESCRIPTION:
Made modifications to ensure that the amounts are written as positive in the tax analysis table (tfgld110) and have added logic
to find the correct tax authority for each transaction line. Also added a field to enable the user to specify whether or not they
want to see the contra for shifted tax in the report.

Solution: 159911
SITUATION IDENTIFIED IN:
"Calls" (tsclm1100s000)
SITUATION DESCRIPTION:
When a warranty is registered on a call, the user should expect that clicking on the button to see warranty information will
show those terms linked to the object via the warranty. Instead, the user is seeing only the warranty details as defined apart
from the object, which is incorrect and misleading to the user.
SOLUTION DESCRIPTION:
When the user clicks on the warranty button, the warranty terms linked to the object are displayed. If no such terms exist,
then the details of the warranty are displayed.

Solution: 159943
SITUATION IDENTIFIED IN:
"Print References to Parent" (ttaad4229m000)
SITUATION DESCRIPTION:
The rep.detail line was exceeding it's 132 char limit, causing an index out of dims
SOLUTION DESCRIPTION:
A check is now performed on the components of rep.detail, to ensure that the sum of these parts do not exceed the length of
rep.detail.

Solution: 159946
ITUATION IDENTIFIED IN:
"Find and Remove Duplicate +/- Reocrds In tdcms050" (tdcor0014m000)
SITUATION DESCRIPTION:
After running the session, "Calculate Commissions/Rebates (tdcms0240m000)" in certain situations would cause the table
tdcms050 to fill with duplicate positive/negative commissions adjustments.
SOLUTION DESCRIPTION:
After the installation of Solution 159138, a correction program was created to match the duplicate positive/negative
records in tdcms050 and remove them.

Solution: 159957
SITUATION IDENTIFIED IN:
"Print Machine Utilization per Day" (tisfc1408m000)
SITUATION DESCRIPTION:
When printing the report 'Machine Utilization per Day' (tisfc1408m000), the fields after the production start date and time
were overlapped by the time and garbled characters were shown.
SOLUTION DESCRIPTION:
The print format used to show the production start date was incorrect; it also printed the time, which was then overlapping
with the day of the week. It has now been corrected to only print the date.
The print format to show the production start time is not supposed to show seconds. This format is defined in the session
'Time Formats' (ttadv4586m000). If the time display format '002' (Time without seconds) is specified to use seconds, then
this needs to be manually corrected.

Solution: 159958
SITUATION IDENTIFIED IN:
"Archive / Purge Finance Transaction " (tfgld6205m000)
SITUATION DESCRIPTION:
The internal memory of session "Archive / Purge Finance Transaction" (tfgld6205m000) may become full and cause the session
to hang. This can occur when a large number of transaction lines are processed within a single batch. The session held the
entire batch in memory until the archive / purge process was complete before doing a database update.
SOLUTION DESCRIPTION:
The session now updates the archived / purged transactions more frequently within the database. This reduces the amount of memory required by the archiving
process and allows large batches to be archived successfully.

Solution: 159970
SITUATION IDENTIFIED IN:
"Material to Issue for Production Orders" (ticst1501m000)
SITUATION DESCRIPTION:
When making multiple material issues of an item to a production order for which the valuation price of the item changes
between the material issues, the actual cost price of the material line is not always calculated correctly.
SOLUTION DESCRIPTION:
The calculation of actual cost price for a material line has been modified so that the material line price is now always
correct when the valuation price changes between material issues.

Solution: 159975
SITUATION IDENTIFIED IN:
"Rebuild Opening Balance/History From Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
When rebuilding history the following problems occurred:
Problem #1 (Japanese Specific)- When rebuilding finalized transactions, the history tables for "Daily Balance Monitoring"
were updated without filling the date.
Problem #2(Japanese Specific)- When rebuilding non-finalized transactions the history tables for "Daily Balance
Monitoring", were updated with the wrong date. Records were created based on the batch date when history should be
based on the document date.
Problem #3 (Japanese Specific)- History tables for 'Inventory Ledger Management' were updated without filling fields
warehouse, item, and department.
Problem #4- The session displays information on the screen to indicate to the users what information is being processed.
When processing finalized transactions, the batch number was always printed on the screen as 0 .
SOLUTION DESCRIPTION:
#1- Localization specific history tables for daily balance monitoring are now updated with the correct date when rebuilding
history.
#2- Non-finalized transactions are now placed in the daily balance history tables based on the document date and not the
batch date.
#3- Inventory Ledger history is now created with the warehouse, item, and department.
#4- Batch number is now displayed correctly on the screen when rebuilding finalized transactions.

Solution: 159984
SITUATION IDENTIFIED IN:
"Recurring Transaction Details" (tfgld1517s000)
SITUATION DESCRIPTION:
When creating Recurring Transaction Instructions in a multi-site environment, the check for whether a period is defined
and not finally closed is done for the group company. The check should be done for the current company.
SOLUTION DESCRIPTION:
The check is now performed for the current company.

Solution: 160016
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
When calculating commissions on a cumulative agreement for a sales order line for which multiple separate deliveries were
made, extra commission lines were being created. This causes the commission amount to be too large.
SOLUTION DESCRIPTION:
The program has been modified to add the correct number of commission records when multiple deliveries have been made
for an order line. The total commission amount will now be correct.

Solution: 160017
SITUATION IDENTIFIED IN:
"Calculate Commission / Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
Three possible problems may exist with a commission and rebate relation status after installation of solution 159138.
Scenario 1: The status of the "Relation by Order" (tdcms040) or "Relation by Order Line" (tdcms041) is 'Recalculate' but the
commission/rebate has already been invoiced. In this scenario, a "Commissions / Rebate" (tdcms050) record with a status of
either 'Ready' or 'Closed' will exist.
Note! In certain situations it is proper for Commissions or Rebates to have this status. READ THE SOLUTION
DESCRIPTION FOR MORE DETAILS!
Scenario 2: The status of the record in the "Relation by Order" (tdcms040) or "Relation by Order Line" (tdcms041) is
'Free', even though the commission/rebate has already been calculated. In this scenario, a "Commissions / Rebate" (tdcms050)
record exists for a commission/rebate that the system does not think has been calculated yet.
Scenario 3: The status of the record in "Relation by Order" (tdcms040) or "Relation by Order Line" (tdcms041) is
'Recalculate', but commissions/rebates have not yet been calculated. In this scenario, no "Commissions / Rebate" (tdcms050)
record exists for a commission/rebate that the system thinks has been calculated already.
SOLUTION DESCRIPTION:
Session "Correct Commissions Relation Status" (tdcor0141m000) will correct all three scenarios identified above.
Scenario 1 corrections are identified with the following action text (in English): "Changing Status from Recalculate to
Processed". When run in update mode, the program will change the status of the "Relation by Order" (tdcms040) or
"Relation by Order Line" (tdcms041) record to 'Processed'.
Please note! commissions or rebates identified with this action text in the report may be right! It is possible for an
invoiced commission/rebate to have a 'Recalculate' status if the ordered quantity or price is changed after the commissions
have been processed. There was a problem in the past when old commissions/rebates were set to this status incorrectly.
This scenario must be carefully corrected. Take care when running this program. Cautiously correct records found in this
scenario because they may not be erroneous. As always, Baan Support should be consulted before running the correction
program in update mode, especially in this case.
Scenario 2 corrections are identified with the following action text (in English): "Changing Status from Free to
Processed". When run in update mode, the program will change the status of the "Relation by Order" (tdcms040) or
"Relation by Order Line" (tdcms041) record to 'Processed'.
Scenario 3 corrections are identified with the following action text (in English): "Resetting Status from Recalculate to
Free". When run in update mode, the program will change the status of the "Relation by Order" (tdcms040) or "Relation by
Order Line" (tdcms041) record to 'Free'.
Remember, records found through the Scenario 1 check can be correct. Session "Correct Commissions Relation Status"
(tdcor0141m000) provides an option to avoid searching for Scenario 1 corrections. This option is provided to allow a faster
correction for errors found in Scenario 2 and Scenario 3.

Solution: 160033
SITUATION IDENTIFIED IN:
"Item Ordering Data" (tcibd2100s000)
SITUATION DESCRIPTION:
In item ordering data, when entering a 'fixed order quantity' amount that is an even multiple of the 'order quantity multiple
of', there is an incorrect error message given, indicating that the 'fixed order quantity' is not an even multiple.
SOLUTION DESCRIPTION:
Now within item ordering data, it is allowed to enter all values into the field 'fixed order quantity' that are even multiples of
the 'order quantity multiple of', without an incorrect error message.

Solution: 160040
SITUATION IDENTIFIED IN:
"Item Code Systems" (tcibd0106m000)
SITUATION DESCRIPTION:
It is possible to change the item code system TYPE, when item codes already exist for the specified item code system. This
should not be allowed.
SOLUTION DESCRIPTION:
Now it is not possible to change the item code system TYPE, when item codes already exist for the specified item code
system.

Solution: 160046
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
The report totals for some of the layouts for "Tax Analysis by Tax Authority", "EU Tax Handling by Tax Period", "EU Tax
Handling by Fiscal Period" and "EU Tax Handling by Tax Authority" were printing incorrect values.
SOLUTION DESCRIPTION:
The "aggregate conditions" on the reports has been changed so that all the total fields have consistent conditions. The totals
will print correct values.

Solution: 160050
SITUATION IDENTIFIED IN:
"Report Library" (ttstprepdll)
SITUATION DESCRIPTION:
In certain multicolumn verticle reports, while printing, an index out of dims error would occur.
SOLUTION DESCRIPTION:
Fixed the problem that was resulting in an index of zero being used.

Solution: 160056
SITUATION IDENTIFIED IN:
"Saved Message Data to be Received" (ecedi7151s000)
SITUATION DESCRIPTION:
Incorrect message "tdslss0140 ????????????????" displays in session "Saved Message Data to be Received"
(ecedi7151s000).
SOLUTION DESCRIPTION:
Message was created in B5b but never delivered. Message tdslss0140 states "Method not allowed; sales order '%s' already
cancelled". This solution will contain no changes, only the message to be delivered.

Solution: 160057
SITUATION IDENTIFIED IN:
"Print Fields by Functions / Function Server" (tuddc0430m000)
SITUATION DESCRIPTION:
Report length was not conforming to device page length. Also, fieldname data was bleeding into the domain data column.
SOLUTION DESCRIPTION:
Changed the report's page length to -1 so that it would conform to the device. Also, redesigned the report layout so that
fieldname has enough space.

Solution: 160059
SITUATION IDENTIFIED IN:
"Rebuild Ledger/Dimension History of Period" (tfgld3206m000)
SITUATION DESCRIPTION:
When running the rebuild session, unnecessary history records are being created for the tax period type.
SOLUTION DESCRIPTION:
The functionality to rebuild tax period history has been removed. History is not stored for tax period types, it is only stored
for Financial and Reporting period types. Unnecessary records will no longer be created in the history tables by this session.

Solution: 160061
SITUATION IDENTIFIED IN:
"Estimated Materials" (tisfc0110s000)
SITUATION DESCRIPTION:
The allocation dates for estimated materials were incorrect for overlapping operations.
SOLUTION DESCRIPTION:
The allocation dates for estimated materials are now correct for overlapping operations.

Solution: 160072
SITUATION IDENTIFIED IN:
"Maintain Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
When the session is started but there is not a batch in the current fiscal year to display, the session automatically begins the
process of creating a new batch header. If the user hits the previous group key at this point, the header of a new batch is
created rather than displaying an existing batch in the previous year should one exist. The group keys are not functioning
properly.
SOLUTION DESCRIPTION:
If the user hits a group action key when starting the session with no batches to display for the current fiscal year, the group
action key will work as it should.

Solution: 160073
SITUATION IDENTIFIED IN:
"Run Global SRP" (tssoc2260m000)
SITUATION DESCRIPTION:
Using the session 'Run Global SRP' (tssoc2260m000) reports an incorrect error message "Tool usage is not allowed as tool
life is based on "Number of Hours Used"".
SOLUTION DESCRIPTION:
The session 'Run Global SRP' (tssoc2260m000) is now not incorrectly reporting the error message "Tool usage is not
allowed as tool life is based on "Number of Hours Used"" anymore.

Solution: 160094
SITUATION IDENTIFIED IN:
"Purge Audit Files" (ttaad4261m000)
SITUATION DESCRIPTION:
When entering a wide range of companies, the error log would fill up with a large amount of errors due to the fact that the
session was trying to process tables in companies that didn't exist.
SOLUTION DESCRIPTION:
Made it so the session will now skip over companies that don't exist. Also, in B50_c and B52_a, don't try to open the aud file
if it doesn't exist.

Solution: 160122
SITUATION IDENTIFIED IN:
"Maintain Customers" (tccom1101m000)
SITUATION DESCRIPTION:
The Canadian province code for Newfoundland has changed from 'NF' to 'NL' for Newfoundland and Labrador. The new code
has become effective on October 21, 2002, and the old code will still be accepted for a period of six months. Baan did not
accept the new code before.
SOLUTION DESCRIPTION:
Baan is now accepting the new Canadian province code 'NL' for Newfoundland and Labrador. The old code 'NF' can still be
used until April 20, 2003.

Solution: 160130
SITUATION IDENTIFIED IN:
"Version Scan Tool" (ttaad0500m000)
SITUATION DESCRIPTION:
Certain messages in VST are unclear as to the source of the message. For example, if a message indicating a temporary file
cannot be created appears, often the task that this file was trying to perform is not obvious.
SOLUTION DESCRIPTION:
New messages have been added to replace the old. These messages give a clearer indication as to the source of the
problems encountered when running VST.

Solution: 160132
SITUATION IDENTIFIED IN:
"Direct Network Communication" (tcedi7205m000)
SITUATION DESCRIPTION:
In EDI, when header text is included in multiple purchase orders and the middle purchase order header text is made to be null,
the system will attempt to place a text value in all of the subsequent sales order headers.
SOLUTION DESCRIPTION:
The header text is now correctly carried through from purchase orders to sales orders when multiple orders are included in
the same batch via EDI.

Solution: 160149
SITUATION IDENTIFIED IN:
"Intergroup Transactions" (tfgld2102s000)
SITUATION DESCRIPTION:
1. While maintaining the intergroup transactions, the transaction reference of the document in the source company is not
copied to the transaction reference of the document being created in the target company. It is, instead, left blank.
2. After creating the document in the target company, if the user tries to modify the document (without re-starting the
session), the data just created disappears. The only way the user can modify the information is to exit and re-start the
session.
SOLUTION DESCRIPTION:
1. The transaction reference of the document in the source company is now copied into the transaction reference of the
document in the target company.
2. User is now able to modify the data without re-starting the session.

Solution: 160167
SITUATION IDENTIFIED IN:
"Global Approval for Commissions / Rebates" (tdmcs0250m000)
SITUATION DESCRIPTION:
It is not possible to zoom from the 'Invoice From' or 'Invoice To' fields in "Global Approval of Commissions / Rebates" to
choose a Sales Invoice. A user must know or guess what range of Invoices to process.
SOLUTION DESCRIPTION:
This solution allows a user to zoom from the 'Invoice From' or Invoice To' field to session "Invoice - Source Relation"
(cisli2505m100) and select from any Invoice Document in the session.

Solution: 160172
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
1) If the report "Print Tax Analysis by Tax Authority" is printed for a multiple tax code only the first line prints the "Net
Amount in HC". All the subsequent lines print 0.
2) The tax authority field was not printing in reports Print Tax Analysis by Tax Code, Print Tax Analysis by Fiscal Year and
Print Tax Analysis by Tax Authority in case of multiple tax codes.
3) In report Print Tax Analysis by Fiscal Period, the Grand Total was not printing the correct total for the field "Net
Amount in HC". This problem was only in B50_b version.
SOLUTION DESCRIPTION:
1)The net amnt in HC will now be printed for all the tax code lines, but only the first line (tfgld110.sern = 1) amount will be
included in the total. The other lines will be marked with an asterisk (*) on the report and a note will be added in the footer
denoting that those lines are not included in the calculation of the total.
2) The tax authority will print correctly on all the reports.
3) Necessary changes have been made to calculate the grand total correctly.

Solution: 160175
SITUATION IDENTIFIED IN:
"Module Planning" (tipcs4520m000)
SITUATION DESCRIPTION:
The functionality to duplicate a group of modules between two projects was previously disabled.
SOLUTION DESCRIPTION:
The functionality to duplicate a group of modules between two projects has been enabled. It is now possible to copy modules
between two projects, if the items and activities exist for the target project. Non-existing target items or activities will not
be automatically created!

Solution: 160210
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
When the Commission Parameter, Exchange Rate Type has been entered in session "Commissions/Rebates Parameters"
(tdcms0100s000), it is not used to convert the Business Partner's currency to the company's reference currency.
SOLUTION DESCRIPTION:
When the Commission Parameter, Exchange Rate Type has been entered in session "Commissions/Rebates Parameters"
(tdcms0100s000), it will be used to convert the Business Partner's currency to the company's reference currency.

Solution: 160213
SITUATION IDENTIFIED IN:
"Plan Items" (cprpd1101s000)
SITUATION DESCRIPTION:
When removing an item from being Master base planned, ATP and CTP checks were still being done.
SOLUTION DESCRIPTION:
Order based items will not have access to the flags of field "Online ATP Update" and will be unchecked when unchecking
field "Maintain Master plan". Field "Critical in CTP" will be accessible and checked even for order based items during CTP
checks.

Solution: 160218
SITUATION IDENTIFIED IN:
"Calculate Commissions/Rebates" (tdcms0240m000)
SITUATION DESCRIPTION:
When calculating commissions for a sales order line with multiple details, the commission for the first detail gets duplicated
for each subsequent detail line.
SOLUTION DESCRIPTION:
The session has been modified to no longer duplicate the commission for the first detail line. The calculated commissions
should now be correct for all details.

Solution: 160223
SITUATION IDENTIFIED IN:
"Test Function Server" (tuddc2530s000)
SITUATION DESCRIPTION:
When leaving the Test Function Server session, the function server that had been started was not shutting down.
SOLUTION DESCRIPTION:
Added some code to shutdown the function server that had been started.

Solution: 160229
SITUATION IDENTIFIED IN:
"Shift Production Planning" (tisfc1202m000)
SITUATION DESCRIPTION:
When shifting the production planning for a range of orders, it was possible that some orders were not shifted. The new start
date can change for each order due to already started operations, but it was not set back to the original choice of the user.
This resulted that the process tried to shift the following orders incorrectly to the changed date.
SOLUTION DESCRIPTION:
When shifting the production planning for a range of orders, the chosen new start date is now correctly applied to the
shifting process of each production order planning.

Solution: 160245
SITUATION IDENTIFIED IN:
"Audit Batches" (tfgld1211s000)
SITUATION DESCRIPTION:
#1- When closing the year (tfgld6203m000) if the created batch contained an entry to a dimension that was blocked for all
input, the created opening balance batch would give an error 'dimension is blocked' when attempting to finalized the batch.
#2- When closing the year (tfgld6203m000) if the update mode of the transaction is 'real time' or 'end of session' and the
year-end-close batch contained an entry to a ledger account that was blocked for all input, the created opening balance
batch could not be finalized as the message 'background process not complete' was given when selecting the batch. This
occurred because the background program would not finish due to the blocked ledger account.
#3- Transactions created by the "Automatic Balancing of Profit and Loss Accounts" (tfgld6202m00) could not be finalized if
the created batch contained entries to ledger accounts or dimensions that were blocked for all input.
SOLUTION DESCRIPTION:
#1- The audit program that is run when finalizing batches (tfgld1211s000) has been changed so that the error check for
blocked dimensions is not done for opening balance transactions. The reasoning behind this is that these entries are simply
transfering the existing balances to the new year, and are not a result of any new activity on the dimension.
#2- The background programs called for update mode "end of session" (tfgld1203s000) and update mode "real
time"(tfgld1201s000) have been modified so that error checks for blocked ledger accounts are no longer done for opening
balance transactions.
#3- The audit program that is run when finalizing batches (tfgld1211s000) has been changed to not check for ledger account or
dimension blocking when the transaction type is equal to the transaction type for autobalancing in the company parameters
(tfgld004.taut). This part of the solution does not apply to versions lower than B40_c as this field did not exist prior to
B40_c.

Solution: 160271
SITUATION IDENTIFIED IN:
"Print Periodic Journal Report" (tfgld1411m000) in B40_c, B50_b, B50_c
"Print Journal Report - Belgium" (tfgld1442m000) in B52_a
SITUATION DESCRIPTION:
When printing Journal Report for Belgium, it is not possible to print the report for more than one finance company
belonging to the same finance group.
SOLUTION DESCRIPTION:
Now it is possible to print the Journal Report for Belgium either for the current company or for all companies belonging to
the same finance group, with the new option "Print All Companies". The reports print the finance company number on the
detail line.

Solution: 160278
SITUATION IDENTIFIED IN:
"Select Device" (ttstpsplopen)
SITUATION DESCRIPTION:
After installing solution 129274 the current VRC is not found in ttstpsplopen.
SOLUTION DESCRIPTION:
Changed the select to use index1 in the where clause.

Solution: 160280
SITUATION IDENTIFIED IN:
"Generate Invoice by Self Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
When generating self-billed invoices for a packing slip range, if one of the orders in the range has an error no invoices are
generated for the orders without errors.
SOLUTION DESCRIPTION:
Now invoices will be generated for the orders in the range which do not have errors.

Solution: 160302
SITUATION IDENTIFIED IN:
"Commissions Calculated by Order/Schedule" (tdcms0550m000)
SITUATION DESCRIPTION:
When deleting a record in "Commissions Calculated by Order/Schedule" (tdcms0550m000) after saying "yes" to the question "Set
the relation status to free or not?" and deleting the record, the status stays in "processed" rather than being set to "free".
This only happens when the "Relation" field (tdcms050.reln) is the full 9 characters in length. If it is less than 9 characters
it works fine.
SOLUTION DESCRIPTION:
The relation field(s) size has increased between BaanIV and iBaanERP versions. The CMS and Finance areas of iBaanERP have been updated to correctly use the new domain.

Solution: 160358
SITUATION IDENTIFIED IN:
"Rebuild Sublevels" (tffbs1204m000)
SITUATION DESCRIPTION:
The budget session Rebuild Sublevels (tffbs1204m000) can potentially lock an excessive number of records in a database
during a rebuild - this processing can consume a substantial amount database resources.
SOLUTION DESCRIPTION:
The record processing in the Rebuild Sublevels (tffbs1204m000) session has been modified to be less database resource
intensive.

Solution 160544

SITUATION IDENTIFIED IN:

"Maintain Original Sales Schedules" (tdssc1102m000)

SITUATION DESCRIPTION:

In Supply Chain AGS only, Outstanding quantities are recalculated via session "Maintain Original Sales Schedules" (tdssc1102m000) which can lead to the situation that the schedule requirements are not equal to Planned Inventory Transactions by Item.

SOLUTION DESCRIPTION:

For Supply Chain AGS only, modified session so that the schedule requirements correspond to the Planned Inventory Transactions by Item after running session "Maintain Original Sales Schedules" (tdssc1102m000).

# Solution 160559

SITUATION IDENTIFIED IN:

"Purge Audit Files" (ttaad4261m000)

SITUATION DESCRIPTION:

When in any company but 0, starting the purge caused a fatal error.

SOLUTION DESCRIPTION:

Fixed session so that it will switch to company 0 before doing anything else.

# Solution 160500

SITUATION IDENTIFIED IN:

"Execute Query" (ttadv3280m000)

SITUATION DESCRIPTION:

When zooming to ttadv3280m000 from ttadv3580m000, the company number is switched to company 000, forcing the user to manually switch his company before executing a desired query.

SOLUTION DESCRIPTION:

Now, the user's current company number is set in the Execute Query session, so that the user does not have to manually change it.

# Solution 160752

SITUATION IDENTIFIED IN:

"Version Scan Tool" (ttaad0500m000)

SITUATION DESCRIPTION:

The DB version was not showing up on form 3. Also, no error was given if the password failed for the database.

SOLUTION DESCRIPTION:

For Unix, a chunk of code was missing for this process. Replaced the appropriate code.

# Solution 130502

SITUATION IDENTIFIED IN:

"Calls" (tsclm1100s000)

SITUATION DESCRIPTION:

When copying a Call on which the Currency, Country or Language are changed on the details tab, the changed value is not copied to the new Call but it is defaulted.

SOLUTION DESCRIPTION:

The Currency, Country and Language are now copied from the original Call and not defaulted when copying a Call.

# Solution 130577

SITUATION IDENTIFIED IN:

"Quotation Coverage Terms " (tsctm1120s000)

SITUATION DESCRIPTION:

1. When creating a new Coverage Term the effective date is defaulted from the Quotation Date of the Contract Quotation Header. When this falls before the Contract Effective Date, also defined on the Quotation Header, the Coverage term cannot be saved with the defaulted dates. Message: "Effective Date of Coverage Term cannot be earlier then the Effective Date of the Contract." (tsctms0738) pops up.

2. When filling the Billing Start Date there is no check on this whether it is correct in relation to the "Installment Variant" defined on the installment template as it is done in Service Contracts. (session "Service Contracts" tsctm3100s000)

SOLUTION DESCRIPTION:

1. When creating a new Coverage Term the effective date is defaulted from the Contract Effective Date on the Contract Quotation Header.

2. The Billing Start Date is checked in relation with the "Installment Variant" defined on the installment template. This can be "In Advance" or "Afterwards". When the variant is "In Advance", the Billing Start Date has to be before or equal to the Contract Effective Date. When it is "Afterwards" it has to be later or equal to the Contract Effective Date. When an Installment Template is filled, it is mandatory to fill the Billing Start Date as well.

# Solution 130818

SITUATION IDENTIFIED IN:

Maintain Samples (qmptc2110s000)

SITUATION DESCRIPTION:

When the inventory is present for storage inspection, the system gives the error message the inventory is not available on the warehouse.

SOLUTION DESCRIPTION:

The system checks the total inventory available for warehouse and when the available inventory is less than the sample quantity, then the system will give the error message.

# Solution 130752

ITUATION IDENTIFIED IN:

"Maintain Payment Advices" (tfcmg1120s000)

SITUATION DESCRIPTION:

Tax amount not calculated in Payment Advice for Standing Order of type Advance Payment.

SOLUTION DESCRIPTION:

Tax amount will get calculated now in Payment Advice for Standing Order of type Advance Payment.

# Solution 130711

SITUATION IDENTIFIED IN:

"Calls" (tsclm1100)

SITUATION DESCRIPTION:

When creating a Call for an object, which is covered by Warranty, the Warranty field is not selected.

SOLUTION DESCRIPTION:

When creating a Call for an object, which is covered by Warranty, a check is made whether Warranty exists and the Warranty field is selected accordingly.

# Solution 130747

SITUATION IDENTIFIED IN:

Generate Bill of Critical Materials (tibom2220m000)

SITUATION DESCRIPTION:

While generating the Bill of Critical Materials, system is not taking into account the safety time for the Lead time offset calculation. This happens only when the routing is not attached to the Manufactured item.

SOLUTION DESCRIPTION:

The system while calculating the Lead Time offset takes into account the safety time also.

# Solution 130756

SITUATION IDENTIFIED IN:

"Sales invoices" (tfacr1110s000)

SITUATION DESCRIPTION:

Wrong error message when entering a tax code which does not have Posting Data.

SOLUTION DESCRIPTION:

Correct error message will pop up now when entering a tax code, which does not have Posting Data.

# Solution 130848

SITUATION IDENTIFIED IN:

Print Purchase Order Reports (tdpur4405m000)

SITUATION DESCRIPTION:

While printing the Purchase Orders by Currency in the session, system doesn't print the Purchase Order Total in Home Currency. It is shown as 0.

SOLUTION DESCRIPTION:

Now, the amounts for the Purchase Order Total are correctly printed for Home Currency Total.

# Solution 130544

SITUATION IDENTIFIED IN:

"Print Purchase Order Report" (tdpur4405m000)

SITUATION DESCRIPTION:

The report "Print Purchase Order Report " is showing the wrong back order amounts, when it printed with the option "order lines" only is checked.

SOLUTION DESCRIPTION:

Now the problem is solved the report "Print Purchase Order Report " will show the correct back order amounts, even when it printed with the option "order lines" only.

# Solution 130214

SITUATION IDENTIFIED IN:

"Print Purchase Order Report" (tdpur4405m000)

SITUATION DESCRIPTION:

The report "Print Purchase Order Report " is showing the wrong back order quantities, when it printed with the option "order lines" only is checked.

SOLUTION DESCRIPTION:

Now the problem is solved the report "Print Purchase Order Report " will show the correct back order quantities, even when it printed with the option "order lines" only.

# Solution 115361

SITUATION IDENTIFIED IN:

"Engineering BOM" (tiedm1510m000)

SITUATION DESCRIPTION:

Negative quantities should be allowed to enter in Engineering BOM

SOLUTION DESCRIPTION:

The system will allow to enter negative quantities in the Engineering BOM.

# Solution 130740

SITUATION IDENTIFIED IN:

"Process Delivered Sales Orders" (tdsls4223m000).

SITUATION DESCRIPTION:

When running session "Process Delivered Sales Orders" (tdsls4223m000) for an order that is not suited to be processed (yet), message "Process Completed" pops up, although the order has not been processed at all.

Steps to take:

1. Start session "Sales Orderlines Overview" (tdsls4510m000).

2. Select tab "Status".

3. Select an order not having "Process Delivered Sales Orders" in column "Description".

4. Start session "Process Delivered Sales Orders" (tdsls4223m000).

5. Check "Process Order Data" and enter the Order number, as selected in step 3.

6. Choose "Continue".

7. Message "Process completed" pops up, suggesting the order has been processed which is wrong.

SOLUTION DESCRIPTION:

Correct message is being displayed when Processing Delivered Sales Orders.

If order(s) could be processed message "Process completed" pops up.

If nothing could be processed message "Sales: No Data within Selection" is displayed.

# Solution 130779

SITUATION IDENTIFIED IN:

"Remove fully paid sales invoices" (tfacr2260m000)

SITUATION DESCRIPTION:

When 'copy to history' is not selected (unchecked), fatal error (error 506, table does not exist) is shown.

SOLUTION DESCRIPTION:

Now, when 'copy to history' is unchecked, fatal error is not shown

# Solution 130918

SITUATION IDENTIFIED IN:

Reprint Invoices (cisli2405m000)

SITUATION DESCRIPTION:

Initial "From" value for ' Finance company', is displayed as ' 999 ' instead of ' 000 '.

SOLUTION DESCRIPTION:

Initial "From" value for 'Finance company' field is now displayed as ' 000 '.

# Solution 160728

SITUATION IDENTIFIED IN:

"Plan Item Data" (cprpd1500m000)

SITUATION DESCRIPTION:

The message 'Family site cannot be zero' (cprpd100.19) was previously not delivered and missing.

SOLUTION DESCRIPTION:

This solution delivers the message 'Family site cannot be zero' (cprpd100.19).

# Solution 160834

SITUATION IDENTIFIED IN:

"Version Scan Tool" (ttaad0500m000)

SITUATION DESCRIPTION:

The portingset OS was not being displayed on NT servers. Also, if the first "valid" entry in the ipc_info file was commented out, then nothing would be displayed for bshell.

SOLUTION DESCRIPTION:

NT4.0 is now hard coded for the portingset OS. In ERP, we now use the environment variable BSHELL_TAG to determine the current user's bshell. Also, in all version the code was fixed so that if the first "valid" ipc_info entry is commented out, it will skip to the next one.

Solution 131103

SITUATION IDENTIFIED IN:

"Reprint Invoices" (cisli2405m000)

SITUATION DESCRIPTION:

Several Labels are missing in languages other than English

SOLUTION DESCRIPTION:

Now the missing labels are created in languages other than English

# Solution 131095

SITUATION IDENTIFIED IN:

"Purchase Order Lines" (tdpur4501m000)

SITUATION DESCRIPTION:

One label each is missing in the sessions mentioned below:

"Purchase Order Lines" (tdpur4501m000)

"Purchase Order Line Details" (tdpur4501m200)

"Sales Statistics Parameters" (tdsst0100m000)

"Sales order lines overview" (tdsls4510m000)

"Addresses" (tccom4130s000)

SOLUTION DESCRIPTION:

Missing labels are available via this solution.

# Solution 131187

SITUATION IDENTIFIED IN:

"Purchase Order Lines" (tdpur4501m000)

SITUATION DESCRIPTION:

Missing labels on form.

SOLUTION DESCRIPTION:

Labels and forms adapted.

# Solution 130956

SITUATION IDENTIFIED IN:

"Properties of GRNI Reconciliation entry" (tfacp1135m000)

"Accept Values of GRNI Reconciliation" (tfacp1535m000)

"Update last used batch number" (tfcor0600)

"Insert missing tfgld109 records in Archive Company" (tfcor6205m000)

"Copy Budgets" (tffbs1202m000)

"Budget Amounts and Quantities per Year" (tffbs1500m000)

"Print Periodical Journal Report" (tfgld1411m000)

SITUATION DESCRIPTION:

In this solution. several forms and reports are delivered, where in labels were missing or where the labels did not appear in the Dutch and German language. This has been changed.

SOLUTION DESCRIPTION:

All forms and reports, mentioned in this solution are now correct in all languages.

# Solution 131151

SITUATION IDENTIFIED IN:

"Accept Values of GRNI Reconciliation" (tfacp1535m000)

"Insert missing tfgld109 records in Archive Company" (tfcor6205m000)

"Differences per Order" (tfacp1438m000)

"Price Variance Analysis By order" (tfacp1461m000)

SITUATION DESCRIPTION:

In this solution. several forms and reports are delivered, where in labels were missing or where the labels did not appear in the Dutch and German language. This has been changed.

SOLUTION DESCRIPTION:

All forms and reports, mentioned in this solution are now correct in all languages.

# Solution 130963

SITUATION IDENTIFIED IN:

tiedm1201m000 (Copy Engineering Items to Items)

tipcf5290m000 (Archive Product Variants)

SITUATION DESCRIPTION:

Label 'Copy E-Item description' is missing in the session "Copy Engineering Items to Items" in Dutch and German languages.

Label 'Archive Standard Variants' is missing in the session "Archive Standard Variants" in Dutch language.

SOLUTION DESCRIPTION:

Label 'Copy E-Item description' is made available in the session "Copy Engineering Items to Items" in Dutch and German languages.

Label 'Archive Standard Variants' is made available in the session "Archive Standard Variants" in Dutch language.

# Solution 130924

SITUATION IDENTIFIED IN:

"Rebuild budget cost analysis codes" (tpcor3200m000)

SITUATION DESCRIPTION:

Label "Testrun" is missing.

SOLUTION DESCRIPTION:

Label "Testrun" is now been added.

# Solution 128133

SITUATION IDENTIFIED IN:

"Correction of inbound/outbound lines for production orders / Clear Corrupted Inventory" (whcor0213m000/whcor0200m000)

SITUATION DESCRIPTION:

Missing labels on form and report.

SOLUTION DESCRIPTION:

Labels, forms, report adapted.

# Solution 131153

SITUATION IDENTIFIED IN:

"Correction of inbound/outbound lines for production orders / Clear Corrupted Inventory" (whcor0213m000/whcor0200m000)

SITUATION DESCRIPTION:

Missing labels on form and report.

SOLUTION DESCRIPTION:

Labels, forms, report adapted.

Solution 127864

SITUATION IDENTIFIED IN:

"cprrp1210m000" (Simulate Orders)

SITUATION DESCRIPTION:

When planning a Generic- or To-Order Item, customized stock which is consumed by a Salesorder is simultaneously consumed by 'anonymous' demand for the Generic- or To-Order Item from which the customized item is derived.

The customized stock is consumed twice; once for the customized item and once for the Generic- or To-Order Item.

Insufficient Planned Orders are generated as a result.

In session In session "Time Phased Planning Overview" (cprrp0520m000) the total stock (stock of the generic + stock of customized items) is shown and there is no simple way of telling what part of that stock is customized.

SOLUTION DESCRIPTION:

Customized stock is not available for a Generic- or To-Order item (customized stock is only available for the customized item).

When planning a Generic- or To-Order Item Item, first all customized demand and supply is processed. Customized demand will consume customized supply/stock (for the same project).

Any remaining demand (customized or 'anonymous') will be planned for the Generic- or To-Order Item itself (customized or anonymous demand will result in a planned order for the Generic- or To-Order Item when the inventory of the Generic- or To-order Item itself is insufficient)

Customized demand outside the Orderhorizon is not seen during "Simulate Orders" and will therefore not consume customized stock when planning the Generic- or To-Order Item.

Outside of the Orderhorizon the customized stock is handled as 'anonymous' stock.

In session "Time Phased Planning Overview" (cprrp0520m000) for Generic- or To-Order Items the stock per project is shown in 'detail-view'. These "stock"-lines have no 'date'

# Solution 160467

SITUATION IDENTIFIED IN:

"ATP Handling" (tdsls4899m000)

SITUATION DESCRIPTION:

ATP would be over stated for non-Master plan items if there was closed production receipts posted to inventory.

SOLUTION DESCRIPTION:

ATP for order based items should be calculated off from the inventory plus current transactions.

# Solution 160484

SITUATION IDENTIFIED IN:

"cprao1210m000" (Update Signals)

SITUATION DESCRIPTION:

The Signal "Order Must be Transferred, Transfer Late", is generated when the finish date of the planned order is less than the current date.

SOLUTION DESCRIPTION:

The Signal "Order Must be Transferred, Transfer Late", will be generated when the start date of the planned EP order is less than the current date.

Solution 130687

SITUATION IDENTIFIED IN:

"Print Sales Orders" (tdsls4405m000)

SITUATION DESCRIPTION:

The Sales Order report (tdsls4405m000) is not displaying the total amount, if the ordered quantity is zero.

SOLUTION DESCRIPTION:

All amounts are correctly displayed.

# Solution 130280

SITUATION IDENTIFIED IN:

"Print Sales Orders" (tdsls4405m000)

SITUATION DESCRIPTION:

The Sold-To Business Partner and the Ship-To Business partner are printed on the reports. However the corresponding name of the Ship-To Business partner is incorrect.

SOLUTION DESCRIPTION:

The name of the Sold-To Business partner was printed where the name of the Ship-To Business partner was expected. Reports were modified so the right name is printed.

Solution 130761

SITUATION IDENTIFIED IN:

"Installment Orders" (tdsls4506m000)

SITUATION DESCRIPTION:

It is possible to close an installment order (session tdsls4506m000) when a sales order line still has an unconfirmed backorder.

SOLUTION DESCRIPTION:

An installment order can only be closed when all sales order lines are delivered and when there are also no unconfirmed backorders present.

# Solution 130559

SITUATION IDENTIFIED IN:

"Installment orders" (tdsls4506m000)

SITUATION DESCRIPTION:

After solution 128634 was installed, it has been noticed that the program source is not present.

SOLUTION DESCRIPTION:

A new dump under this solution has been created so the source can be reinstalled.

# Solution 131060

SITUATION IDENTIFIED IN:

"Settled Advance Payment Request Lines" (tppin0511m000)

SITUATION DESCRIPTION:

When there are more than one advance lines, each with different currency, then, only the line matching the currency of installment gets settled & not the other lines. This is not correct because all advances made to a customer are to be considered irrespective of the currency in which they were made.

SOLUTION DESCRIPTION:

The above problem is corrected & now all the advances made to the customer are considered irrespective of the currency.

Solution 131048

SITUATION IDENTIFIED IN:

QM Parameters (qmptc0100s000)

SITUATION DESCRIPTION:

In "QM Parameter" (qmptc0100s000) session, user can enter any value in for the fields of the form 'Blocking reasons' and save, even though the values are not present in the session "Blocking Reasons" (tisfc2500m000).

SOLUTION DESCRIPTION:

In "QM Parameter" (qmptc0100s000) session, system will allow entering the values for the fields of the form 'Blocking reasons' and save, only when the values are present in the session "Blocking Reasons" (tisfc2500m000).

# Solution 130995

SITUATION IDENTIFIED IN:

Service Orders: Actual Other Costs (tssoc2141s000)

SITUATION DESCRIPTION:

When the price of the purchase order is changed after receipts, the changed amount is updated to the actual cost price of the Service Subcontracting line. The amount should be divided by the actual quantity so that the change in cost price will be updated correctly.

SOLUTION DESCRIPTION:

Now the Cost Price is updated correctly corresponding to the price change.

# Solution 130067

SITUATION IDENTIFIED IN:

"Service Order: Actual Material Costs" (tssoc2121s000)

SITUATION DESCRIPTION:

1. When changing the status of a Service Order or a Service Order Activity from 'Released' to 'Completed', return lines are generated automatically (based on Service Order Control parameters). When all materials have been issued (From Lines) or received (To Lines) the order can be set to 'Costed'.

When changing the status of a Service Order or a Service Order Activity from 'Released' to 'Costed', return lines are generated automatically (based on Service Order Control parameters), Obviously it is not possible to receive these items in the same step in the warehouse, as this requires a logistical receipt. This situation leads to an unbalanced work in process as long as the item(s) on the return line(s) are not received in the warehouse.

2. A service order material line can generate financial transaction 'Approved for Invoicing' although it is not consumed, i.e. the material is returned to the warehouse.

This happens in the following situation:

After a return line is generated for a material (receipt line is present in Warehousing), the actual quantity is put back from zero to the quantity for which it has been issued before. As a result of this, the receipt line in Warehousing is deleted and the 'To Be Delivered Quantity' on the return line is changed to zero automatically. Subsequently, the 'To Be Delivered Quantity' on the return line is changed from zero to the former value and the material is received in Warehousing.

This results, after setting the order to 'Costed', in a negative issue booking as well as a approved for invoicing booking as can be seen in session "Integration Transactions by Project/Order"(tfgld4510m000)

3. Changing the cost component on a service order actual material line after the materials have been issued / received, the original issue transaction should be reversed and a new booking should be made using the new cost component. This does not happen anymore.

4. When the service order (or activity) has got the status "Released" or "Completed" and a new material line with delivery type "From Warehouse in Car" or "From Warehouse by Transport" is updated, the warehouse transactions (inventory commitments) will not be done during the update of the line. Instead, the error message " Item 'xxxx' not found in warehouse ' '. " is shown although a correct warehouse was defined on the material line.

This error is shown because the estimation warehouse is used in order to check and update the warehouse transactions, but in this case, no estimation is present.

SOLUTION DESCRIPTION:

1. When changing the status of a Service Order or a Service Order Activity from 'Released' to 'Costed', the service order actual material cost lines are checked. All material should be issued/received completely. If there are quantity differences, i.e. more material is issued then on the 'From' line is specified as 'Actual Quantity (tssoc220.adqt), the service order or service order activity first needs to be set to status 'Completed', so return lines can be generated and can be handled correctly.

2. If non-consumed materials need to be returned to the warehouse, automatically a return line can be generated (based on Service Order Control parameters). However, the quantity, prices, discounts and/or surcharges regarding the material are based on the original line ('From Warehouse' line or 'By Purchase Order' -line). This means that any change of quantity on the original line will result in a change of quantity on the return line. Therefore, only the fields Warehouse, Planned Delivery and Return Reason are updateable on returns line that have a line number greater than 5000 (B50b and B50c) or that have the related line number filled (B52a).

3. Changing the cost component on a material line, for which an issue or receipt had already taken place, will result in a negative issue booking using the old cost component and a positive issue booking for the new cost component.

4. Warehouse transactions will be updated in case the service order/activity is "Released" or "Completed" and

- A new material line is created

- A material line with cost line status "Free" is updated with a new - Planned delivery time (return deliveries),

- Item code

- Actual warehouse code

- Sales unit

- Sum of the quantity delivered & subsequent delivery

- A material line is deleted

- The planned times on the service order or activity have been changed.

In all these situations, the estimated warehouse defined on the material line is used to check and update the warehouse transactions.

In case no estimation is present for this line, the actual warehouse defined on the material line will be used in order to check and update warehouse orders.

# Solution 130634

SITUATION IDENTIFIED IN:

"Generate Configuration Structures" (tscfg2210m000)

SITUATION DESCRIPTION:

Labels "Erstellung basiert auf" (tscfgs2213) and "Percentage van verkoopwaarde" (tstsctm300.perc) missing in German and Dutch language.

SOLUTION DESCRIPTION:

Label lengths are made longer so that the labels are displayed in all languages.

# Solution 131094

SITUATION IDENTIFIED IN:

"Reconciliation Payments/Receipts" (tfcmg2103s000)

SITUATION DESCRIPTION:

Rejected anticipated documents do not get the status 'Rejected', when the previous status was 'open'.

SOLUTION DESCRIPTION:

Rejected anticipated documents now correctly get the status 'Rejected'.

# Solution 130288

SITUATION IDENTIFIED IN:

"Anticipated Receipt Details" (tfcmg2117s000)

SITUATION DESCRIPTION:

It not possible to create manual anticipated receipt document with blank bank code and it is giving ' Fatal Error'.

SOLUTION DESCRIPTION:

-- It is possible to create manual anticipated receipt document with blank bank code.

n This functionality has been restricted by giving warning message at the time of creation of manual anticipated payment document with blank bank code. The reason for restricting this functionality is it's not possible to assign the bank code later to the manual anticipated payment document and not possible to reconcile the document.

# Solution 130334

SITUATION IDENTIFIED IN:

"Reconcile Payments/Receipts" (tfcmg2103s000)

SITUATION DESCRIPTION:

In session "Reconcile Payments/Receipts - tfcmg2103s000", the batch is not balanced in the following situation:

-The payment advice contains negative standing orders

-The parameter "Calculate Tax on Advance Payments/Receipts is set to "yes".

SOLUTION DESCRIPTION:

Now the reconciliation batch is balanced.

# Solution 130610

SITUATION IDENTIFIED IN:

"Post Direct Debits" (tfcmg4257s000)

SITUATION DESCRIPTION:

It is not possible to create new batch during the process of post payments

SOLUTION DESCRIPTION:

Now it is possible to create a new batch during the process of post payments.

# Solution 130667

SITUATION IDENTIFIED IN:

"Post Debits" (tfcmg4257s000)

SITUATION DESCRIPTION:

Reference doesn't appear in the session "Display receipt details"

SOLUTION DESCRIPTION:

Reference will now appear correctly in the session "Display receipt details"

# Solution 130933

SITUATION IDENTIFIED IN:

"Reconciliation Payments/Receipts" (tfcmg2103s000)

SITUATION DESCRIPTION:

When the application is locked during reconciliation, message 'Reconciliation in process for this bank and document' is given. This message is misleading because the reconciliation will not be processed in this case.

SOLUTION DESCRIPTION:

When the application is locked during reconciliation, message 'Reconciliation in process by other user' will be given. This message indicates clearly that the reconciliation will not be processed.

# Solution 131313

SITUATION IDENTIFIED IN:

"Display Receipt Details" (tfacr2524s000)

SITUATION DESCRIPTION:

Reference field appears blank

SOLUTION DESCRIPTION:

Reference field will be correctly filled now.

# Solution 131155

SITUATION IDENTIFIED IN:

Reconciliation of Receipts/Payments (tfcmg2103s000)

SITUATION DESCRIPTION:

1) Currency difference calculated during reconciliation for invoice with Fixed hard

2) Fatal error occurring when reconciling receipt anticipated document for sales and Purchase Invoice adjustment.

3) Reconciliation amount in foreign bank currency is wrong for manual anticipated receipt document.

SOLUTION DESCRIPTION:

1) Currency difference not calculated anymore during reconciliation for invoice with Fixed hard

2) Fatal error is not occurring when reconciling Receipt anticipated document for sales and Purchase Invoice adjustment.

3) Reconciliation amount in foreign bank currency is correct for manual anticipated receipt document.

# Solution 130520

SITUATION IDENTIFIED IN:

"Remove Confirmed Shipments" (whinh4250m000)

SITUATION DESCRIPTION:

Run session "Remove Confirmed Shipments" (whinh4275m000) in a job. When there is no data within selection the job fails in a runtime error.

SOLUTION DESCRIPTION:

When there is no data within selection for session "Remove Confirmed Shipments" (whinh4275m000) when this session is placed in a job, the job is completed without runtime errors.

Solution 125795

SITUATION IDENTIFIED IN:

"Copy Forms/Reports/Menus to New VRC using given Label" (ttadv6270m000)

SOLUTION DESCRIPTION:

The session "Copy Forms/Reports/Menus to New VRC using given Label" (ttadv6270m000) offers new functionality. It is meant for translation partners of Baan, who have to copy forms, reports and menus to a new VRC after changing a label translation. This session does this work automatically.

SPECIAL INSTRUCTIONS:

The session "Create Runtime Data Dictionary for Tools" (ttadv5213m000) has to be run after installation of the solution. The field "Also Dump Data Definitions" needs not to be checked. In the session range only session "ttadv6270m000" needs to be specified.

For this session also "Create Runtime Help" (ttadv5230m000) must be executed. When you are using Windows Help, the help-information can be expected in one of the next Service Packs.