Solution: 126106
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
In the current BaanERP software, especially in the area of Inventory, PCS and Service, it is difficult to reconcile Financial
and Logistical figures.
SOLUTION DESCRIPTION:
To be able to reconcile the following new session are created:
- tfgld4418m100: Print PCS Project Transaction Specification
With this session specific transaction information can be retrieved from the system for PCS projects.
- tfgld4418m200: Print Inventory Transaction Specification
With this session specific transaction information can be retrieved from the system for Inventory transactions.
- tfgld4418m300: Print difference between Logist. and Finan. integr. tables
With this session all differences between records in Financial Integration tables and Logistical tables will be printed.
These new sessions can be found in the mtfgld2010m000: Financial Reconciliation.
The following sessions are adjusted:
- tipcs3480m000: Print Project Work in Process
Within this session it is now possible to select on Ledger Account for printing the WIP.
- ticst0450m000: Print Work in Process
Within this session it is now possible to select on Ledger Account for printing the WIP.
- tcfin3400m000: Print BaanService Finance Reconciliation.
Within this session it is now possible to print detailed service integration transactions.
SOLUTION CONTAINS NEW FUNCTIONALITY.
SOLUTION 128443, 128493, 128487, 128596, 128858 and 160018 are POST REQUISITES OF THIS SOLUTION
FOR BAAN50_C.
PLEASE INSTALL THESE SOLUTIONS AS WELL.
VERSION(S):
B50_c; B50_b
SPECIAL INSTRUCTIONS:
This solution contains domain changes. In order to make these changes effective in your environment you should run the
Create Runtime Data Dictionary (ttadv5210m000) session after installing this solution.
For the new session the Options Sessions and Print Errors should be marked. In the field Package Combination your
Package Combination.
In the field Package the letters tf and in the field session for example the session gld4418m100. This should be repeated
for the sessions mentioned within this solution.
VRC packag component comp_type comp_code servicepack
B50L b bgl0 tf Script/Library Source glddll1011 spb50b_15
B50L b bgl0 tf Script/Library Object glddll1011 spb50b_15
B50L b bgl0 tf cisli2200m000 Script/Library Source intdlltfgld spb50b_15
B50L b bgl0 tf cisli2200m000 Script/Library Object intdlltfgld spb50b_15

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

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

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

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

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

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

Solution: 129887
SITUATION IDENTIFIED IN:
"Transfer payments" (tfcmg1260m000)
SITUATION DESCRIPTION:
When a Swiss DTA bank file is sent to the Swiss Telekurs, the file is read by special software checking the layout of the
file to see if it meets the guidelines.
The Telekurs program generates an error report indicating that various addresses placed in the DTA bank file are not
formatted according to the guidelines.
SOLUTION DESCRIPTION:
The addresses placed in the Swiss DTA bank file meet the DTA guidelines.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 130047
SITUATION IDENTIFIED IN:
"Easy Warehousing Order Entry" (whinh2202m000)
SITUATION DESCRIPTION:
Locking problem when re-using runnumber.
SOLUTION DESCRIPTION:
Removed setting of application lock when re-using runnmber.
SPECIAL INSTRUCTIONS:
None.

Solution: 130135
SITUATION IDENTIFIED IN:
"Correction programme for updating tfgld037" (tfcor0437m000)
SITUATION DESCRIPTION:
System is allowing selecting of trade notes related ledger accounts defined in Financial Business Partner Group while
creating Manual Journal Voucher.
SOLUTION DESCRIPTION:
Now, the correction program is provided for treating the trade notes related ledger accounts used as control account.
This correction program deletes all the records in the table tfgld037 (Ledger Accounts Used as Control Account) and
rebuilds all the records.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 130204
F
or B50_b version please also download solution 132902 which contains the form dump of tfcor2245m000 in language 1
and 3.
VERSION(S):
B50_b, B50_c, B52_a
SITUATION IDENTIFIED IN:
"GRNI Sessions" (GRNI Sessions)
SITUATION DESCRIPTION:
Several problems were logged:
All Versions:
- Amounts of session tfacp1432m000 "Print receivable Invoice Specifications" were incorrectly calculated due to PUR
rate type and INT rate type.
- Because the option "Based on values in ACP in session tfacp1438m000 "Print Receivable Invoice Checklist" is the same
functionality as the session tfacp1432m000 "Print receivable Invoice Specifications", the scripts should be moved to a
DLL.
- Session tfacp1438m000, tfacp1432m000 and session tfacp1439m000 read the rate tables in order to get the correct internal
rates. However rate can be antidated and therefore the internal rate should be stored in the logistic tables.
iBaan ERP 5.2a:
- The report of Session tfacp1237m000 "Global accept GRNI Entries" showed a character before the ledgeraccount
- The document number in session tfacp1535m000 "Accept values og GRNI Reconciliation" should be moved to the first
tab.
SOLUTION DESCRIPTION:
- Rates are stored now in the logisitc tables as soon as a receipt is done
- Old transactions read the currencyrate from the currency rate tables, new transactions read the rate in the logistic tables
for receipts
- The functionality of tfacp1432m000 is moved to a DLL because the checklist tfacp1438m000 uses the same
functionality.
- Improved the calculation of logistic receipt and approval amounts.
BaanERP5.0b/iBaan ERP 5.0c
- Table changes of table tfacp245 were delivered via solution 132323. The field business partner is added to the table.
This solution delivers a correctionprogram (tfcor2245m000) to fill the business partner.
iBaan 5.2a:
- Report of Session tfacp1237m000 is modified. Character is no longer printed on the report
- The document number in session tfacp1535m000 is moved to the first tab.
- Table changes of table tfacp 245 were delivered via solution 132508. The field business partner is added to the table.
This solution delivers a correctionprogram (tfcor2245m000) to fill the business partner.
SPECIAL INSTRUCTIONS:
Execute correction program tfacp2245m000 in order to update the field tfacp245.otbp "Buy-from Business Partner"

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

Solution: 130225
SITUATION IDENTIFIED IN:
"Outbound Advice" (whinh2125s000)
SITUATION DESCRIPTION:
Fatal Error 206 "Record is not locked" when changing runnumber inside outbound advice.
SOLUTION DESCRIPTION:
Record lock is re-newed due which fatal error is prevented.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

Solution: 130325
SITUATION IDENTIFIED IN:
"Select Invoices for Reminder" (tfacr3210m000)
SITUATION DESCRIPTION:
There should be a possibility to do a selection based on payment method.
SOLUTION DESCRIPTION:
Invoices related to entered range of payment method, will be selected for reminding. For this "From Payment Method"
and "To Payment Method" are provided.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 130349
SITUATION IDENTIFIED IN:
"Print Collected Suspended VAT" (tfgldl415m00l)
SITUATION DESCRIPTION:
In session "Print Collected Suspended VAT" (tfgldl415m00l)
1. Help file is not correct.
The session "Print Collected Suspended VAT" also prints the payments. So, the help text has to include information
about payments.
2. In the summary part, the information is printed only for one tax authority. It has to print for all the tax authorities.
SOLUTION DESCRIPTION:
In session "Print Collected Suspended VAT" (tfgldl415m00l)
1. Help file is not correct.
The session "Print Collected Suspended VAT" also prints the payments. So, the help text has to include information about
payments. So, the help text has been changed.
2. In the summary part, the information is now printed only for all the tax authorities.
SPECIAL INSTRUCTIONS:
None.

Solution: 130368
P
LEASE DOWNLOAD SITUATION IDENTIFIED IN:
"Print Registered and Matched Purchase Invoices " (tfacp1433m000)
SITUATION DESCRIPTION:
When an invoice is approved in period one and unapproved in the next period, when printing the report Print Registered
and Matched Purchase Invoices (tfacp1433m000) for the period one, the invoice is shown as not approved.
SOLUTION DESCRIPTION:
Now, if an invoice is approved in a specific period, the session Print Registered and Matched Purchase Invoices shows
those invoices approved in that period, even if they are unapproved later.
Please note that, this solution becomes active only when the new table definition has been created, and also the new table
has been created. After this the correction program tfcor1826m000 should be run to populate this table.
NOTE For Baan 4 Version, this table is not used at this moment. However this table will be used in the future to resolve
performance issues. This table will be activated only when the correction program tfcor1826m000 has been run ( See solution
131548 ). Untill this correction program is not run, this table will not be active , and no inserts will be done on this table.
Please read the special instructions about installing the solution.
SOLUTION 131396, AFTER INSTALLING THIS SOLUTION, TO AVOID FATAL ERROR
DURING FINALIZATION, WHEN A CREATE TO RUNTIME DATA DICTIONARY FOR TABLE TFGLD126 HAS
NOT BEEN RUN.
PLEASE ALSO DOWNLOAD AND INSTALL SOLUTION 131548 TO USE THE FINALIZATION PROGRAM
WITHOUT CREATING THE TABLE TFGLD126.
VERSION(S):
B40_c, B50_b, B50_c
SPECIAL INSTRUCTIONS:
This solution contains a new table definition( tfgld126 ) and a new session and form to populate this table (
tfcor1826m000 ).
- Run session "Create runtime datadictionary (Forms and Menus)" (ttadv5214m000) -----> to activate the new forms.
Run for the tabledefinition tfgld126:
- Session "Create runtime datadictionary" (ttadv5210m000) with the option reconfigure tables on .

Solution: 130377
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
' Data overflow ' error message is displayed, while composing the negative payment slip amount
SOLUTION DESCRIPTION:
' Data overflow ' error message is not displayed, while composing the negative payment slip amount
SPECIAL INSTRUCTIONS:
None.

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

Solution: 130412
SITUATION IDENTIFIED IN:
"Print Invoices" (cisli2400m000)
SITUATION DESCRIPTION:
Wrong field order in the session
SOLUTION DESCRIPTION:
The order is now corrected.
SPECIAL INSTRUCTIONS:
None.

Solution: 130413
_
______________________________________________________
For Version(s) B52_a Please download solution 130415 AFTER this.
________________________________________________________
VERSION(S):
B50_b, B50_c, B52_a
SITUATION IDENTIFIED IN:
"Post Invoices" (cisli3200m000)
SITUATION DESCRIPTION:
If the Invoice date in session Compose/Print/Post or the Transaction Entry date in the session Compose/Print/Post or in
session Post Invoices is made empty, then no posting takes place and wrong error report is displayed.
SOLUTION DESCRIPTION:
Now when the Transaction Entry date or the Invoice date is made empty a message that the Date should not be empty is
displayed. It is compulsory to have a date in these fields.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 130428
SITUATION IDENTIFIED IN:
"Print Invoice-To Business Partner's Balances" (tfacr2424m000)
SITUATION DESCRIPTION:
The Advance/Unallocated Receipts column shows wrong sign for the amount. Display of balance is incorrect.
SOLUTION DESCRIPTION:
The Advance/Unallocated Receipts column shows right sign for the amount. Display of balance has now been made
correct.
SPECIAL INSTRUCTIONS:
None.

Solution: 130431
SITUATION IDENTIFIED IN:
"Print Reminder Letters" (tfacr3420m000)
SITUATION DESCRIPTION:
Invoice amount is wrong in the report. It prints the open invoice amount same as that of the invoice amount.
SOLUTION DESCRIPTION:
The invoice amount is calculated correctly when the receipt schedule is on.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 130453
SITUATION IDENTIFIED IN:
"Transfer Project Data to Invoicing" (tppin4200m000)
SITUATION DESCRIPTION:
After transferring a project installment, marked as 'to be invoiced', the installment gets 'transferred', although no record is
inserted in table "Project Invoice lines"(cisli235). However the interim tax table (cisli942) gets filled.
This happens only if localization Parameter "Multiple Tax" is ON.
SOLUTION DESCRIPTION:
Now if the insertion of the project invoice line fails, then no record will be inserted in the Interim tax table.
SPECIAL INSTRUCTIONS:
None.

Solution: 130464
SITUATION IDENTIFIED IN:
"Lots" (whltc1100s000)
SITUATION DESCRIPTION:
Lot size not correct in case of production rework order.
SOLUTION DESCRIPTION:
In case of issue for production order with type rework order lot size will be decreased.
SPECIAL INSTRUCTIONS:
Please install solution 161130 AFTER installing this solution.

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

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

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

Solution: 130506
SITUATION IDENTIFIED IN:
"Sales Order Lines, Purchase Order Lines" (tdsls4101s000, tdpur4101s000)
SITUATION DESCRIPTION:
When the Order Quantity is different from the Sales Price Unit, there exist some rounding differences that are reflected in
the Order
Acknowledgement, and Invoice.
The Reporting documents - Acknowledgement and Invoice report the price only in terms of the Sales Price Unit,
irrespective of the
Order Quantity Unit, and the Agreements maintained in the Price Book. This makes it difficult to check the agreement
prices also.
SOLUTION DESCRIPTION:
Pricing Parameter 'Price Based On' has been added, one for Sales and another for Purchase. This Parameter has two
options. The Options are
1. Item Sales Data 2. Price Structure - for Sales, and
1. Item Purchase Data 2. Price Structure - for Purchase.
The Default is Item Sales Data/Item Purchase Data. If this is chosen, then old functionality remains. There is no change,
and the price in the Sales Order Line/ Purchase Order Line/ Purchase Requisition or the Sales Quotation line would be the
Sales Price Unit / Purchase Price Unit.
If the 'Price Structure' were chosen, then, the Price Unit would be picked up based on the Price Unit available for the
order quantity in the Price Book.
This way, since, there is no conversion to other unit, there is no rounding problem encountered. Order Acknowledgements,
and the Invoices would be printed with this Unit. So, the Acknowledgement and the Invoice could be seen in the respective
units.
SPECIAL INSTRUCTIONS:
This Solution is Superceded.
For non-PMC users: Please install solution 133714.
For PMC users: Please install this solution and solution 133714.
Table change has been done for Pricing Parameter (tdpcg000) table, and domains have been added. Convert to Runtime is
required after installing this solution.
For B52_a:
----------------
'Please refer to solution 123462 for installation instructions of the changed online help.''
'This solution (also) contains updated online help information. Please refer to solution 123462 for downloading
instructions '. The updated online help will be available and can be downloaded after <28-March- 2003>.

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

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

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

Solution: 130553
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
Two problems are solved:
1) The amounts in the home currencies gets rounded as per the Swiss format
even though they do not belong to the Swiss currencies.
2) Receipt Schedule can't be generated if terms of payment aren't filled in
Order
SOLUTION DESCRIPTION:
1) Now Swiss rounding will now take place only for the Swiss currencies.
2) The receipt schedule is generated based on the Terms of payment defined in the Business partner
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

Solution: 130675
SITUATION IDENTIFIED IN:
"Sales Header" (cisli2140s000)
SITUATION DESCRIPTION:
In the Invoice headers in "Central Invoicing" the Pay-By BP is having a label "Pay-from". The label should be "Pay-by"
Also in Localizations for iBaan ERP 5.0c, when the Invoice-to BP is changed to some unrelated BP in the "Manual Sales"
header, then no error message is displayed.
SOLUTION DESCRIPTION:
The label is changed now. And also the error message is displayed.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 130695
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When cash discount is applicable for manual sales invoices, the amount in finance was exclusive of cash discount. But when
sales invoices raised from the finance module then the amount filled in this field is the Gross amount. Therefore there is
an inconsistency in the way in which the table is updated from different modules
SOLUTION DESCRIPTION:
Now Gross amount (including cash discount) is booked in Finance. Therefore values in the finance are same in both
situations.
SPECIAL INSTRUCTIONS:
__________________________________________________________________________________________________
_________________________________________
The following care should be taken before installing this solution:
The status of the Sales orders or the Manual Sales order in the Central Invoice are On Hold, Confirmed, Composed,
Printed, Posted or Cancelled.
Before installing this solution, make sure that NO sales order lines or the Manual sales order lines have the status
"COMPOSED" or "PRINTED".
These lines are to be first POSTED and then the solution has to be installed.
To know which sales order lines or the Manual sales order lines have the status COMPOSED or PRINTED please run
session cisli2410m000 "Print Invoice lines by Status" with the following options checked:
Options for "Status"
Printed Yes (checked)
Composed Yes (checked)
All Other options Unchecked
Option for "Invoice Types"
Sales Order Yes (checked)
Warehouse Order Yes (checked)
Manual Sales Invoice Yes (checked)
All Other options Unchecked
The report gives all those sales order lines and the Manual sales order lines, which have the status, COMPOSED or
PRINTED.
Please POST these order lines before installing this solution.
__________________________________________________________________________________________________
________________
SPECIAL INSTRUCTIONS GIVEN BELOW BEFORE INSTALLING THIS
SOLUTION****************
__________________________________________________________________________________________________
__________
VERSION(S):
B50_b

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

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

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

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

Solution: 130728
SITUATION IDENTIFIED IN:
"Receipt Fiscal Documents" (tdrecl104m00l)
SITUATION DESCRIPTION:
The following fields on the Receipt Fiscal Document Lines (tdrecl505m00l): Operational Fiscal Code, Operation Origin,
Standard History Code and History Description, are changed to the value on the header without warning when making a
change on the Receipt Fiscal Document (tdrecl104m00l).
SOLUTION DESCRIPTION:
The functionality is as follows now:
When making a change in one of the above mentioned fields on the Receipt Fiscal Document (tdrecl104m00l) the following
question is asked: "Update line(s) with this header change?" When the question is answered with 'yes' the value of that
field is also adjusted on the lines. This happens after saving the modified Receipt Fiscal Document.
SPECIAL INSTRUCTIONS:
None.

Solution: 130739
SITUATION IDENTIFIED IN:
"Select Invoices for Direct Debit" (tfcmg4220m000)
SITUATION DESCRIPTION:
When sales invoices are selected for direct debits, the fields "Amount in INv. Curr" and "Amount in home currency" are
not filled in the Direct Debit Advice table.
SOLUTION DESCRIPTION:
Now the amounts are filed.
SPECIAL INSTRUCTIONS:
None.

Solution: 130766
SITUATION IDENTIFIED IN:
Change Prices/Discounts after Receipts (tdpur4122m000)
Integration Transactions by Project / Order (tfgld4510m000)
SITUATION DESCRIPTION:
When the user changes the prices of the PO line using the session "Change Prices/Discounts after Receipts
(tdpur4122m000)", after receipt of a subcontracting purchase order line. When we look at the generated integration
transactions, some order fields are empty.
When the subcontracting purchase order item is received using the purchase order receipt session, then the multiple
transactions have been posted.
SOLUTION DESCRIPTION:
Now the system will show all the relevant information in the generate integration transactions when the user changes the
prices, after receipt of a subcontracting PO lines are made.
Multiple transactions are not posted any more .
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

Solution: 130851
SITUATION IDENTIFIED IN:
Print Purchase Orders (tdpur4401m000)
SITUATION DESCRIPTION:
User is able to print the Purchase Orders with "All Lines" option even when the purchase order has a manual approval
activity that has not been executed. Because of this, normal users are able to print and read the unapproved purchase
orders.
SOLUTION DESCRIPTION:
User is able to print the Purchase Orders with "All Lines" option even when the purchase order has a manual approval
activity that has not been executed. Because of this, normal users are able to print and read the unapproved purchase
orders.
SPECIAL INSTRUCTIONS:
Now, user will not be able to print the purchase orders waiting for the release of manual activities. If "Print Purchase
Orders (tdpur4401m000)" is not a part of order step then user will be able to print the orders even when the manual
activities are not released.

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

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

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

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

Solution: 130927
SITUATION IDENTIFIED IN:
"Print Aging Analysis for Schedule lines" (tfacrl404m00l)
SITUATION DESCRIPTION:
Report shows wrong document dates for an invoice. It shows invoice document date as that of the receipt document date.
SOLUTION DESCRIPTION:
Document dates for the invoice and the receipt are correctly displayed
SPECIAL INSTRUCTIONS:
None.

Solution: 130929
SITUATION IDENTIFIED IN:
"Process Bank Files" (tfcmgl215m00l)
SITUATION DESCRIPTION:
In session "Process Bank Files" (tfcmgl215m00l) it is not possible the reconciliation of bank files when the Reporting
Periods are not used. After starting the update process, the message "Invalid Period Number" (tfgldd0003) is displayed.
SOLUTION DESCRIPTION:
When not using Reporting Periods, the error message is not displayed anymore while processing the bank file.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131008
SITUATION IDENTIFIED IN:
"Select Invoices for Reminder" (tfacr3210m000)
SITUATION DESCRIPTION:
Situation One: Receipt Schedules are selected for the Invoice and for receipt documents also.
Situation Two: Invoices are not filtered based on credit analyst entered in the form.
SOLUTION DESCRIPTION:
Solution for Situation One: Receipt Schedules are selected for the Invoice only.
Solution for Situation Two: Invoices are filtered based on credit analyst entered in the form.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

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

Solution: 131082
SITUATION IDENTIFIED IN:
Processed Delivered Purchase Order (tdpur4223m000)
SITUATION DESCRIPTION:
It was not possible to delete the normal processed purchase order. The check has been done only for the BaaN project.
SOLUTION DESCRIPTION:
It is now deleted for the normal processed purchase order.
SOLUTION AFTER DOWNLOADING THE PREVIOUS SOLUTION 130647.
VERSION(S):
B50_b, B50_c
SPECIAL INSTRUCTIONS:
PLEASE DOWNLOAD THIS SOLUTION AFTER DOWNLOADING THE PREVIOUS SOLUTION 130647.

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

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

Solution: 131150
SITUATION IDENTIFIED IN:
"Print Statement of Account" (tfacr3440m000)
SITUATION DESCRIPTION:
If receipt schedules parameter is ON, wrong "Total Amount Open" is displayed
SOLUTION DESCRIPTION:
Correct "Total Amount Open" is displayed.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 131177
SITUATION IDENTIFIED IN:
Assign unallocated /advance receipts to invoices (tfcmg2105s000)
SITUATION DESCRIPTION:
When schedules parameter is on, 2 lines are shown with the same amounts and details while re-entering the session
"Assign unallocated /advance receipts to invoices (tfcmg2105s000)" after linking an invoice to the unallocated receipt.
Only one line should be shown.
SOLUTION DESCRIPTION:
Now, assignments are shown properly. Only one line is shown for every assignment.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 131207
SITUATION IDENTIFIED IN:
"Delete Bank File" (tfcmgl223m00l)
SITUATION DESCRIPTION:
The system doesn't delete the bank files if it is run with the options:
Payment Type: all
Status: all
SOLUTION DESCRIPTION:
Now all bank files are deleted if the options are:
Payment Type: all
Status: all
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131215
SITUATION IDENTIFIED IN:
Shipment lines by warehousing order (whinh4131s000)
SITUATION DESCRIPTION:
When a shipment lines are confirmed, it is not possible to confirm the shipment line, as there is error set in one function
mistakenly. This problem was occuring in Grieg only.
SOLUTION DESCRIPTION:
The problem is identified and it is not because of the previous 128865. Hence it is better to download that solution along
with this present solution 131215 also. The shipment lines are now able to confirm without any error message pops up.
SPECIAL INSTRUCTIONS:
Please download this solution also after downloading the previous solutions 129433, 128865

Solution: 131216
SITUATION IDENTIFIED IN:
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
When printing the actual cost price of a project, the system is not printing the Purchase Order receipts linked to a back
order.
SOLUTION DESCRIPTION:
The system prints all purchase orders including the backorders while printing the actual cost price of a project.
SPECIAL INSTRUCTIONS:
This Solution is Superceded.
For non-PMC users: Please install solution 132679
For PMC users: Please install this solution and solution 132679.

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

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

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

Solution: 131253
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
In localization environment, when sales invoices with non-singular tax codes are posted, then the "Interim Tax table
(tfgld107)" is not getting filled with the tax percentage.
SOLUTION DESCRIPTION:
Now the tax percentages are correctly filled.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131341
SITUATION IDENTIFIED IN:
"Purchase Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
The localization parameter "Vat Book" is set.
Consider a situation where there are 2 purchase invoices created, one with a transaction date of 01/11/2002 and another
with a transaction date of 01/12/2002. Hence it is no longer possible to create new transactions earlier than 01/12/2002.
Now in the session "Purchase Invoice Transactions"(tfacp1120s000), of purchase invoice with the date 01/11/2002 was
updated, then it is now possible to enter transactions after 01/11/2002.
SOLUTION DESCRIPTION:
Even if changes are made to a transaction line with a previous transaction date, it is no longer possible to create new
purchase invoices before the latest one present.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131374
SITUATION IDENTIFIED IN:
"Payment Schedule Detail Lines" (tfacpl504m00l)
SITUATION DESCRIPTION:
In session "Payment Schedule Detail Lines" (tfacpl504m00l), there is some extra code, which is no longer used after
the payment schedule entry has been moved to session "Payment Schedule Details" (tfacpl104m00l).
SOLUTION DESCRIPTION:
The redundant code has been removed from the script.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 131384
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When creating a Purchase Invoice, the due date of the Payment Schedule based on the linked Terms of Payment, was not
calculated correctly. This was caused by an incorrect handling of the different date/time types (Dates/UTC's).
SOLUTION DESCRIPTION:
When creating a Purchase Invoice, the due date of the Payment Schedule based on the linked Terms of Payment, is
calculated correct.
SPECIAL INSTRUCTIONS:
None.

Solution: 131396
SITUATION IDENTIFIED IN:
"Select Batches for Finalization " (tfgld1212s000)
SITUATION DESCRIPTION:
After Installing solution 130368, Fatal error "No definition in definition file for sopen ( F_BRDD:dtfgld126, dtfgld126) "
occured.
This error message occurs when the Create runtime data dictionary for the table tfgld126 is not run.
SOLUTION DESCRIPTION:
The Finalization process is now modified so that when there is no data definition present for table tfgld126, updating the
table will be skipped.
SOLUTION 131548 TO USE THE FINALIZATION PROGRAM
WITHOUT CREATING THE TABLE TFGLD126.
VERSION(S):
B40_c, B50_b, B50_c
SPECIAL INSTRUCTIONS:
None.

Solution: 131443
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
"Maintain Payment Methods" (tfcmg0140m000)
"N, Norske Bank, Foreign"- B40L_c_nc20: report 20 (tfcmg126021999)
- B50_b and B50_c: report 27 (tfcmgL2561500L)
SITUATION DESCRIPTION:
In the session "Maintain Payment Methods" (tfcmg0140m000) the report 20 (for B50_b and B50_c: report 27) cannot be
used with IBAN.
The IBAN functionality is not yet available for the BETFOR payment file.
SOLUTION DESCRIPTION:
The IBAN functionality has been implemented for the BETFOR payment file. The field "Use IBAN" is now accessible for
the report 20 (for B50_b and B50_c: report 27), also in combination with report 9.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131465
SITUATION IDENTIFIED IN:
"Maintain Market Prices for LIFO by Year" (whinal104m00l)
SITUATION DESCRIPTION:
In session "LIFO by year" (whinal103m00l), it was not possible to enter a new year if the session "Perform Inventory
Valuation" was run. Also in session "Maintain Market Prices for LIFO by Year" (whinal104m00l) it was not possible to
update the market value anymore.
SOLUTION DESCRIPTION:
It is possible to update the market value in session "Maintain Market Prices for LIFO by year".
SPECIAL INSTRUCTIONS:
None.

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

Solution: 131484
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
1. During "confirm shipments" (whinh4275m000) a fatal error occurred. "Domain tdcms.reln not defined"
2. Sales Order Line text is added to a sales order line in session "Sales Order Lines" (tdsls4101m000); this text is not
printed on the Delivery Note (whinh4475m000)
SOLUTION DESCRIPTION:
1. Shipments can be confirmed without errors.
2. If there is a Sales Order Line Text for a shipment, this is printed on the Delivery Note
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131503
SITUATION IDENTIFIED IN:
"Warehouse Orders" (whinh2100s000)
SITUATION DESCRIPTION:
It is not possible to change the information present under the tab "Miscellaneous" for a sales order of type transfer
between a normal warehouse and a consignment warehouse.
SOLUTION DESCRIPTION:
The information under the tab "Miscellaneous" can now be modified.
SOLUTION 132032 AFTER
DOWNLOADING THIS SOLUTION
*******************************************************************************************
VERSION(S):
B50_b, B50_c, B52_a
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 131537
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
It is not possible in session "Transactions" (tfgld1101m000) to finalize an assignment of an anticipated payment batch
with VAT to an invoice (with VAT). This happens when the anticipated payment batch is finalized before the assignment
is done.
SOLUTION DESCRIPTION:
It is possible to finalize an assignment of an anticipated payment batch with VAT to an invoice, even when the anticipated
payment batch is finalized before the assignment is done.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131598
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
1. it is possible to create more negative inventory than on order
2. for warehouses without locations, if any inventory is present, never negative inventory is created
SOLUTION DESCRIPTION:
1. it is not possible anymore to create more negative inventory than on order;
2. for warehouses without locations, if any inventory is present, negative inventory is created when the present inventory
is booked on shipment lines
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

Solution: 131665
SITUATION IDENTIFIED IN:
"Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
The calculation of the Due Date of the Invoice was based on the Calendar Lines (table tcccp020) in stead of the Actual
Calendar (table tcccp030).
SOLUTION DESCRIPTION:
The calculation of the Due Date of the Invoice is based on the Actual Calendar (table tcccp030) in stead of the Calendar
Lines (table tcccp020) .
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 131714
SITUATION IDENTIFIED IN:
"Purchase Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
When entering Lines in session "tfacp1120s000 - Purchase Invoice transactions" and a tax code is entered with Social
Contribution (Italian vat code) the Interim Account linked to the Company Social Contribution Cost Account is not
adjusted when Social Contribution amounts are changed in session "tfgld1109s000 - Tax Codes on Line". This results in
a remaining amount.
SOLUTION DESCRIPTION:
The Interim Account linked to the Company Social Contribution Cost Account is adjusted when Social Contribution
amounts are changed in session "tfgld1109s000 - Tax Codes on Line".
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 131754
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
After changing the payment method, 'Amount in invoice currency' and 'Total amount by business partner' is calculated
wrongly in the direct debit advice.
SOLUTION DESCRIPTION:
After changing the payment method, 'Amount in invoice currency' and 'Total amount by business partner' is calculated
correctly in the direct debit advice.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 131770
SITUATION IDENTIFIED IN:
"Assign unallocated /advance receipts to invoices" (tfcmg2105s000)
"Assign unallocated /advance payments to invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
In session "Transactions" (tfgld1101m000) it is not possible to finalize an assignment of an anticipated payment batch
with VAT to an invoice (with VAT). This happens when the anticipated payment batch is finalized before the assignment
is done.
SOLUTION DESCRIPTION:
It is possible to finalize an assignment of an anticipated payment batch with VAT to an invoice, even when the anticipated
payment batch is finalized before the assignment is done.
SPECIAL INSTRUCTIONS:
None.

Solution: 131773
SITUATION IDENTIFIED IN:
"Control account checklist" (tfacp2415m000)
SITUATION DESCRIPTION:
Incase two finace company share the same transaction type and series for anticipated payment, and when there is an
intercompany payment by one of this company, and a normal anticipated payment by another company then the control
account checklist can potentially show differences when there are no differences.
SOLUTION DESCRIPTION:
The situation happened because, the document number of a non-inter-company payment and an intercompany payment were
same. Because of this the normal anticipated payment was mistaken to be a intercompany payment. The situation no
longer occurs.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

Solution: 131881
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
Updating of payment status, balance in schedules are wrong in running the session "Post Electronic Bank
Statements"(tfcmg5222m000).
SOLUTION DESCRIPTION:
While executing the session "Post Electronic Bank Statements" (tfcmg5222m000) the payment status is correctly updated
with paid or partly paid status and balance in schedules with correct amount.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

Solution: 131940
SITUATION IDENTIFIED IN:
"Print Goods receipt Notes" (whinh3412m000)
SITUATION DESCRIPTION:
When Product Configurator (PCF) is implemented, the field "Print Variant Option Description" is disabled in session
"Print Goods Received Notes" (whinh3412m000).
SOLUTION DESCRIPTION:
Now The Option "Print Variant Option Description" is disabled only when both parameter fields "Configurator
Implemented " and "Product Configurator for MTO " is set to NO.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 131952
SITUATION IDENTIFIED IN:
"Sales-Quotation Lines" (tdsls1501m000)
SITUATION DESCRIPTION:
While performing the option 'Recalculate Price/Discounts Entire Quotation', the Amount of the quotation lines becomes
zero.
SOLUTION DESCRIPTION:
The amount in the Quotation lines does not become zero on recalculation.
SPECIAL INSTRUCTIONS:
This solution is superceded by solution 132459.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 132086
SITUATION IDENTIFIED IN:
"Purchase Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
When the tax is introduced by lines, and the tax code is defined as Gross, the system modifies the Gross amount
introduced by the user when it should not be modified. The system is adding to the Gross amount the amount of VAT while
saving in session "tfacp1120s000 - Purchase invoice transactions". If the user exits the session the user enters again the
Gross amount is shown as the original amount introduced by the user.
SOLUTION DESCRIPTION:
The gross amount is not modified at saving anymore.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 132098
SITUATION IDENTIFIED IN:
"Posing data by bank/payment method" (tfcmg0546m000)
SITUATION DESCRIPTION:
For the step Document cancelled/void/dishonored ,if an account type "input" is used by Data by Bank/Payment Method
session,"Contra-post previous step" cannot be used.It pops up an error message.
SOLUTION DESCRIPTION:
The user should be able to give the "contrapost previous step" when the posting scheme for BP is OFF.
When the document cancelled/void/dishonored steps the selection of the account type should be made mandatory.
SPECIAL INSTRUCTIONS:
Download the solution 132894 along with this Solution.

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

Solution: 132139
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
1) Consider that order discount is present for a Cost Item. Enter the cost item in the purchase order lines and save. The
order balance is updated by applying the discount while the open balance is updated without applying the order discount.
2) The 'Credit Limit' and 'Linked order line data' Labels are not displayed correctly.
SOLUTION DESCRIPTION:
The Order Balance will be correctly calculated excluding the order discount if the item on the purchase order line is a
Cost or Service Item.
The Labels for 'Credit Limit' and the 'Specific option' namely 'Linked order line data' are displayed correctly.
SPECIAL INSTRUCTIONS:
Do a Create Runtime Data Dictionary (Forms and Menus) using the session ttadv5214m000 after installing this solution for
the form delivered in this solution.

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

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

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

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

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

Solution: 132209
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
When the cash discount parameter is "ON", Updating of Net amount (tfgld110.amnt) for Sales Credit Notes in "Maintain
Tax analysis" (tfgld110) table is wrong.
SOLUTION DESCRIPTION:
When the cash discount parameter is "ON", the Net amount (tfgld110.amnt) for Sales Credit Notes is updated correctly in
"Maintain Tax analysis" (tfgld110) table.
SPECIAL INSTRUCTIONS:
None.

Solution: 132214
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When in session tfacp1110s000 "Purchase Invoices" the Control Account Type is changed, the following error appears:
Fatal error: "Use of NULL pointer on"
Fatal Error: "Cannot continue in tfacp1110s000 (before.rewrite) (exec_function)
Error: tfacp1110s000: A not terminated transaction is aborted (before.rewrite () in object otfacp1110) "
SOLUTION DESCRIPTION:
No more errors occur when the control account type is changed.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 132226
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
When a cost item or a project item is added to a Purchase Order that is linked to a Direct Delivery Sales Order, system
doesn't allow the user to process it further. The cost line is not linked to the sales order. Due to that, lot of unprocessed
purchase orders will remain in the system.
SOLUTION DESCRIPTION:
It is now possible to process the non linked sales order line and can also be matched and invoiced.
SOLUTION ( 132226), ALSO DOWNLOAD THE SOLUTION 132583 WITHOUT
FAIL.
VERSION(S):
B50_b, B50_c
SPECIAL INSTRUCTIONS:
AFTER DOWNLOADING THIS SOLUTION ( 132226), ALSO DOWNLOAD THE SOLUTION 132583 WITHOUT
FAIL.

Solution: 132228
SITUATION IDENTIFIED IN:
"Generate Invoice by selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The selfbilling process does not consider the "Negative amount allowed" flag of the selfbillied invoice transaction type.
Hence even though negative amounts are not allowed , transactions are created with negative amount
SOLUTION DESCRIPTION:
Now, when the transaction type for selfbilled invoice does not allow negative amount, then the transaction created will have
their sign and debit /credit indicator switched. This is applicable only when the localization parameter "Fiscal receipt" is
not on.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 132323
SITUATION IDENTIFIED IN:
"Finance Table definition" ()
SITUATION DESCRIPTION:
In Baan ERP, performance problems were noticed in the following sessions, which can be solved only with a table
change
- Match Purchase Receipt Line( tfacp2544m000)
- Send Trade Notes/Checks to Bank ( tfcmg4130m000 )
SOLUTION DESCRIPTION:
The table changes have been implemented. The tables involved are
- Orders by Packing Slip ( tfacp245 )
- Anticipated Payment / Receipts ( tfcmg110 ).
NOTE: This solution contains only the table change. The solution for improving the performance will be delivered
seperately.
SOLUTION 132597 WHICH CONTAINS THE TRANSLATION FOR THE
NEW INDICES IN A LANGUAGES.
VERSION(S):
B50_b, B50_c
SPECIAL INSTRUCTIONS:
Pre-installation instructions
This Solution contains changes in table definition for finance tables - tfacp245 and tfcmg110.
A convert to runtime and reorganize on these table need to be undertaken after installing this solution.
Please take a 'Back-up' of the tables tfacp245 and tfcmg110, before installing this solution.
Post-installation instructions
This solution makes changes to table definitions. One of the changes made is the addition of table field tfacp245.otbp.
Also a new index is added with tfacp245.otbp as leading.
1. In order to fill the new field tfacp245.otbp, for the historical data and new data, please download and install solution
130204 . This Solution contains a correction program( tfcor2245m000 ) to fill up the tfacp245.otbp.
2. Once the tfacp245.otbp is filled for all the historical data in tfacp245, Please do a reorganize of tfacp245, with rebuild
Index, to correctly populate the new Index file of tfacp245.

Solution: 132333
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When a Withholding tax code is used, if the terms of payment are changed after having introduced all the invoice
information, then it is not possible to finalize the batch.
The batch is left as ready, and the withholding tax amount is kept in "Purchase invoices" (tfacp1110s000), however the
withholding tax amount is not visible in the non-finalized transactions report.
SOLUTION DESCRIPTION:
The batch is balanced after changing the terms of payment as well now.
SPECIAL INSTRUCTIONS:
None.

Solution: 132353
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
A float exception can occur in the localization sessions. This is due to the fact that not all the needed data is retrieved
from the table Outbound Order Lines (whinh220).
SOLUTION DESCRIPTION:
The section in which the mentioned data is retrieved is changed. All the data now is retrieved from the table and the float
exception error doesn't occur anymore.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 132388
SITUATION IDENTIFIED IN:
1. "Item Supplier Information" (tdipu0110s000)
2. "General Table Maintenance" (ttaad4100)
SITUATION DESCRIPTION:
1. The default value for the "Capacity Time Unit" field in the "Item Supplier Information" table definition is 'Year'. But,
the allowed values are 'Week' and 'Month'. This causes a problem when data is imported in to this table using Baan
Exchange, which sets the initial value even though that value is not allowed.
2. The name of the table tdpur451 is displayed as "Purchase Order Lines" even though this should be "Purchase Order
Lines History".
SOLUTION DESCRIPTION:
1. The initial value for the field "Capacity Time Unit" is changed from 'Year' to 'Week'. When user imports data in to the
"Item Supplier Information" table through Baan Exchange, the initial value for this field "Capacity Time Unit" will be
'Week' instead of 'Year'.
2. System will display the correct name for the Purchase Order Lines History table.
SPECIAL INSTRUCTIONS:
After installing this solution, the user must run Create Runtime Data Dictionary with tables and reconfigure tables
checked. All users must be off the system when this is run. Please contact your support analyst for more information on
how to do this procedure if you are unsure of how to proceed.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 132546
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Wrong tax basis amount printed in the case of Italian invoices, when spilt deliveries are present.
This happened only when price varied between the detail lines.
SOLUTION DESCRIPTION:
Now the invoice is printed correctly
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 132583
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
When a cost item or a project item is added to a Purchase Order that is linked to a Direct Delivery Sales Order, system
doesn't allow the user to process it further. The cost line is not linked to the sales order. Due to that, lot of unprocessed
purchase orders will remain in the system.
SOLUTION DESCRIPTION:
It is not possible to enter a new line for a Purchase Order originated from a Direct Delivery Sales Order.
SOLUTION ( 132583) AFTER DOWNLOADING THE SOLUTION 132226.
VERSION(S):
B50_b, B50_c
SPECIAL INSTRUCTIONS:
PLEASE DOWNLOAD THIS SOLUTION (132583) AFTER DOWNLOADING THE SOLUTION 132226.

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

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

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

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

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

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

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

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

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

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

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

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

Solution: 132727
SITUATION IDENTIFIED IN:
"Select Invoices for Payment" (tfcmg1220m000)
SITUATION DESCRIPTION:
Amount to be paid in the transaction currency was wrong, in the report of non-finalized transactions, when EMU invoice
is paid in EUR.
SOLUTION DESCRIPTION:
Now, amounts are displayed properly in the report.
SPECIAL INSTRUCTIONS:
None.

Solution: 132746
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
"Error 1169" occurs while posting the invoice in case of level 2 drivers.
SOLUTION DESCRIPTION:
"Error 1169" does not occur while posting the invoice in case of level 2 drivers.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

Solution: 132821
SITUATION IDENTIFIED IN:
"Payment/Receipt Method" (tfcmg0140)
SITUATION DESCRIPTION:
When localization parameter "Trade Notes" is set, then in the session Payment/Receipt Method (tfcmg0140s000), it is not
possible to have the field "Number by" as batch for a receipt method.
SOLUTION DESCRIPTION:
In case the localization parameter "Trade Notes" is set and the option "Replace Invoice by payment Document" is set, then
the field "Number by" is set to document for receipt method else it can be changed to "Batch".
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

Solution: 132867
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
The payment status for payment schedules is not updated to "Paid" for paid invoices. This happens in session "Selection
for Automatic Reconciliation" (tfcmg2123s000) in case there are multiple invoices being paid in a single payment advice and
the due date of the invoice is different for different invoices.
SOLUTION DESCRIPTION:
The payment schedule status is updated correctly for paid documents.
SPECIAL INSTRUCTIONS:
None.

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

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

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

Solution: 132887
SITUATION IDENTIFIED IN:
"Generate Invoice by Self-Billing" (tfacp2290m000)
SITUATION DESCRIPTION:
The Purchase variance was booked with the wrong date, when compression was used, even after installation of solution
132701. This happened in B50_b and B52_a.
SOLUTION DESCRIPTION:
Now, the Transaction entry date is used to create the purchase variance booking in integration.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 132894
SITUATION IDENTIFIED IN:
"Posing data by bank/payment method" (tfcmg0546m000)
SITUATION DESCRIPTION:
For the step Document cancelled/void/dishonored ,if an account type "input" is used by Data by Bank/Payment Method
session,"Contra-post previous step" cannot be used.It pops up an error message.
SOLUTION DESCRIPTION:
The user should be able to give the "contrapost previous step" when the posting scheme for BP is OFF.
When the document cancelled/void/dishonored steps the selection of the account type should be made mandatory.
SPECIAL INSTRUCTIONS:
Download the solution 132278 along with this Solution.

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

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

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

Solution: 132926
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
The Cash transactions were unbalanced when partially paying invoices that were created in ESP (Spanish Pesetas) and a
customer receipt or supplier payment is made in EUR.
SOLUTION DESCRIPTION:
Cash transactions are now balanced when partially paying invoices that were created in ESP (Spanish Pesetas) and a
customer receipt or supplier payment is made in EUR.(reference currency)
SPECIAL INSTRUCTIONS:
None.

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

Solution: 132936
SITUATION IDENTIFIED IN:
"Sales Invoices" (tfacr1110s000)
SITUATION DESCRIPTION:
Unable to link a sales invoice directly to a credit note if the due date of the sales invoice is before the document date of the
credit note.
SOLUTION DESCRIPTION:
Able to link a sales invoice directly to a credit note even if the due date of the sales invoice is before the document date of
the credit note.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 132973
SITUATION IDENTIFIED IN:
"Process Bank Files" (tfcmg1260s000)
SITUATION DESCRIPTION:
In the Norwegian Domestic payment file sent to the bank, all payments for one supplier get the same payment date. The
payment file consists of "Record types". Record type "BETFOR21" contains the supplier data and the payment date. Per
supplier one "BETFOR21" record is created. All payments for one supplier will be done on the same date even when the
original payments have different payment dates.
SOLUTION DESCRIPTION:
In the Norwegian Domestic payment file fore every payment date a seperate "BETFOR21" record is created per supplier.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

Solution: 133022
SITUATION IDENTIFIED IN:
"Assign Unallocated/Advance Receipts to Invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
When assigning an unallocated receipt to an advance receipt no assignment records are created in table "Open Entries"
(tfacr200). The assignment records are present for the unallocated receipts but are missing for the advance receipt.
SOLUTION DESCRIPTION:
The assignment records are now inserted correctly in the table "Open Entries" (tfacr200).
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 133052
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
For the outbound line of a transfer order a unit without assignment to any package definition was used. Nevertheless, the
field package definition was filled automatically for this unit in the corresponding receipt line preventing the line from
being inbounded.
SOLUTION DESCRIPTION:
The package definition is initialized and will be left empty.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

Solution: 133099
SITUATION IDENTIFIED IN:
"Terms of Payment" (tfacr1112s000)
SITUATION DESCRIPTION:
When changing terms of payment the Due date remains the same.
SOLUTION DESCRIPTION:
When changing "Terms of Payment" the Due date changes accordingly.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 133111
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
1. Wrong Cost Component booked in the integration transactions for 'Order Discount'.
2. Enterprise Unit of Calculation office is not populated in the 'Integration Additions' table when PCS item is used.
Please note that point 1 is applicable to B50_c version alone.
SOLUTION DESCRIPTION:
Now the correct cost component is being filled. Also the enterprise unit of the calculation office gets filled if PCS item is
used.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 133138
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260m000)
SITUATION DESCRIPTION:
In the Belgium bank file (report 37, tfcmgl2571100l ) on the last line a record count value is present of the number of lines
starting with '1'. In case that a composing limit is reached, the value in the file does not reflect the number of lines in the
file starting with '1'. Due to this the bank does not accept the file.
SOLUTION DESCRIPTION:
If a composing limit is reached, the record count value in the file shows the number of lines starting with '1'.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 133163
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
1. When a foreign payment is made with Swiss Francs, the DTA file is created with the record type 827 and not with the
record type 830.
2. When a payment is made to a one-time business partner, the bank account number maintained in session "One-time
Business Partner Addresses" (tfacp1102s000) is not getting filled up in the DTA file, which is created.
SOLUTION DESCRIPTION:
1. If the country of the pay-to business partner bank address is different from the country of the current company then the
record type picked up is 830.
2. If the business partner is a one-time business partner, then the bank account and address details are picked up from
the session "One-time Business Partner Addresses" (tfacp1102s000).
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

Solution: 133194
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
The field 'e-item revision' in the same session is also enabled although the parameter ' Engineering Revisions Active in
Sales' in session "Sales Parameters" (tdsls0100s000) is not checked.
SOLUTION DESCRIPTION:
Field is disabled when it should be disabled according to parameter settings
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

Solution: 133273
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Invoice date is empty in 'Sales Listing' when Bilateral or Triangular Invoicing is done.
SOLUTION DESCRIPTION:
Now the date is correctly filled.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

Solution: 133326
SITUATION IDENTIFIED IN:
"Match/aprrove purchase invoices" (tfacp2507m000)
SITUATION DESCRIPTION:
The Net amount is displayed incorrectly when withholding tax is involved. The nett amount is displayed as the Invoice
amount minus the vat amount minus the withholding vat amount. It should display Invoice amount minus vat amount.
SOLUTION DESCRIPTION:
The nett amount is displayed correctly now as Invoice amount minus vat amount.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

Solution: 133483
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
The Swedish bank authorities still have not decided upon changes of the file layout for the BankGirot payment file. Yet,
use of the IBAN is compulsory for cross-border payments as of July 1st 2003.
The banks have now confirmed that the current position for the payer's bank account in the BankGirot file can be used for
the IBAN code. The report file 12 has to be adjusted for that. In order to put the field 'Use IBAN' on 'Yes' in the payment
method, the report group has to be added in the list of IBAN-enabled reports.
SOLUTION DESCRIPTION:
The IBAN code can be used for the Swedish BankGirot payment file. Depending on the settings in the payment method the
bank account number or the IBAN code is printed in the bank file.
SPECIAL INSTRUCTIONS:
None.

Solution: 133487
SITUATION IDENTIFIED IN:
"Transfer payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Not all lines in the Norwegian payment files are 80 characters long. As a result the banks do not accept the payment files.
SOLUTION DESCRIPTION:
The length of each line in the Norwegian payment files is 80 positions.
SPECIAL INSTRUCTIONS:
None.

Solution: 133508
SITUATION IDENTIFIED IN:
"COM/MCS Reports" (COM/MCS Reports)
SITUATION DESCRIPTION:
Some of the labels are missing or not displayed in languages 1 and 3 on the following reports.
SOLUTION DESCRIPTION:
All labels are displayed in the reports of all languages.
SPECIAL INSTRUCTIONS:
None.

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

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

Solution: 133581
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
After modifying the business partner in session 'Bank Transactions', the field 'Document' is enabled for already saved
document. Due to this a document number is created with the series number.
SOLUTION DESCRIPTION:
After modifying the business partner in session 'Bank Transactions', the field 'Document' is not enabled for already
saved document. No incorrect document number is created.
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

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

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

Solution: 133678
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Incorrect rounding differences when assigning an unallocated receipt/payment to an invoice.
In session "Bank Transactions" (tfcmg2100s000), the amount is not rounded correctly as per the rounding format for the
home currencies.
SOLUTION DESCRIPTION:
The amounts are rounded correctly; hence no rounding difference transactions are created after allocation of an invoice
to an unallocated receipt/payment.
SPECIAL INSTRUCTIONS:
Solution 130527 is available for B50L_c_bgl0.

Solution: 133679
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Posting an installment order creates an unbalanced batch when localization parameter "Multiple Tax" is ON
And also the due amount printed in the goods invoice is wrong.
SOLUTION DESCRIPTION:
Now the batch is posted correctly and also the invoice is printed correctly
SPECIAL INSTRUCTIONS:
None.

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

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

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

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

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

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

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

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

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

Solution: 133817
SITUATION IDENTIFIED IN:
"Transfer payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
In the Swiss DTA bank file the SWIFT code is written at the wrong position in Transaction Type 830, Record 3.
SOLUTION DESCRIPTION:
The SWIFT code for Transaction Type 830 in Record 3 is located according the Swiss DTA guidelines.
SPECIAL INSTRUCTIONS:
None.

Solution: 133829
SITUATION IDENTIFIED IN:
"Print Supplier Balance Report" (tfacp2424m000)
SITUATION DESCRIPTION:
Session "tfacp2420m000 - Print Supplier Aging Analysis" gets the assignment document as payment document and shows
invoice balance is zero. However session "tfacp2424m000 - Print Supplier Balance Report" shows invoice is outstanding.
SOLUTION DESCRIPTION:
Session "tfacp2424m000 - Print Supplier Balance Report" outputted wrong data. This has been solved now.
SPECIAL INSTRUCTIONS:
None.

Solution: 133841
SITUATION IDENTIFIED IN:
"Print Receivable Invoices Checklist" (tfacp1438m000)
SITUATION DESCRIPTION:
The project field is not printed on the report "Print Receivable Invoices Checklist".
SOLUTION DESCRIPTION:
The project field is now printed in the first 2 reports of the session "Print Receivable Invoices Checklist".
SPECIAL INSTRUCTIONS:
None.

Solution: 133847
SITUATION IDENTIFIED IN:
"Recalculate Customer Balances" (tfacr2245m000)
SITUATION DESCRIPTION:
Anticipated balance is wrongly calculated, if anticipated document is rejected.
SOLUTION DESCRIPTION:
Anticipated balance is correctly calculated.
SPECIAL INSTRUCTIONS:
None.

Solution: 133861
SITUATION IDENTIFIED IN:
"Sales Quotation Lines" (tdsls1501m000).
SITUATION DESCRIPTION:
Errors caused by duplicate records during Global Confirmation of Sales Quotation Lines in session "Sales Quotation
Lines" (tdsls1501m000).
SOLUTION DESCRIPTION:
Application logic for writing records to Sales Quotation Line History table (tdsls151) is modified.
During Global Confirmation of Sales Quotation Lines no "Duplicate Record" error will be generated anymore.
SPECIAL INSTRUCTIONS:
NOTE: for B50L_c_bgl0 please install Solution 134089 also.

Solution: 133865
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoice" (cisli2200m000)
SITUATION DESCRIPTION:
Cut Off Date is not filled for a Sale Order with Cost Item, when the Localization parameter "Delivery Note" is selected.
SOLUTION DESCRIPTION:
Cut Off Date is now filled for a Sale Order with Cost Item, when the Localization parameter "Delivery Note" is selected.
SPECIAL INSTRUCTIONS:
None.

Solution: 133883
SITUATION IDENTIFIED IN:
"Invoice-to BP aging summary" (tfacr2511m000)
SITUATION DESCRIPTION:
Invoices with greater than "as of" date are not selected.
SOLUTION DESCRIPTION:
Invoices with greater than "as of" date are also selected. Input fields "Last Invoice Date/Period" and "Last Receipt
Date/Period" are added.
SPECIAL INSTRUCTIONS:
None.

Solution: 133918
SITUATION IDENTIFIED IN:
"Open Entries by Business Partner" (tfacr2421m000)
SITUATION DESCRIPTION:
The report "Open Entries by Business Partner" (tfacr242111000) shows a wrong label in German. It shows "Finanzielle
Kreditorengruppe" but it should be "Finanzielle Debitorengruppe". This was caused by a wrong translation of label
tfacr001.itbp. This has been corrected
SOLUTION DESCRIPTION:
The report "Open Entries by Business Partner" (tfacr242111000) now shows the correct label in English and German via
label tfacr002.bprg.
SPECIAL INSTRUCTIONS:
None.

Solution: 133929
SITUATION IDENTIFIED IN:
"Created Sales Order Line History by Business Partner and Item" (tdsls5501m000)
SITUATION DESCRIPTION:
Fields Price and Unit are empty in sessions "Created Sales Order Line History by Business Partner and Item"
(tdsls5501m000) and "Created Sales Order Line History by Item" (tdsls5503m000) when the Specific option "Only
Balance per Order/Position" is chosen.
SOLUTION DESCRIPTION:
Fields Price and Unit are filled when the Specific option "Only Balance per Order/Position is chosen". In session
"Created Sales Order Line History by Business Partner and Item" (tdsls5501m000) also the field gross profit is always
shown.
For both sessions the help texts are changed.
SPECIAL INSTRUCTIONS:
Please also install sol 134085
If your Current VRC is B52_a:
Please refer to solution 123462 for installation instructions of the changed online help.

Solution: 133930
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260s000)
SITUATION DESCRIPTION:
Within the Swiss DTA bankfile the address additions from the suppliers bank relation are written in record 4 of TA 830
instead of the address data of the supplier.
SOLUTION DESCRIPTION:
Within the Swiss DTA bankfile the address data of the supplier is written in record 4 of TA 830.
SPECIAL INSTRUCTIONS:
None.

Solution: 133949
SITUATION IDENTIFIED IN:
"whinh4531m000" (Shipment Lines)
"whinh4275m000" (Confirm Shipment)
SITUATION DESCRIPTION:
It is impossible to confirm multiple shipment lines in a row in case a project is linked to the corresponding sales order
lines. Once a shipment line is confirmed, the following shipment lines cannot be confirmed and error message "Enterprise
unit not defined for sales office" (whinhs0249) is given.
SOLUTION DESCRIPTION:
The check on departments is improved and shipment lines are confirmed properly.
SPECIAL INSTRUCTIONS:
None.

Solution: 133952
SITUATION IDENTIFIED IN:
"Receipt Lines" (whinh3120s000)
SITUATION DESCRIPTION:
In session "Receipt Lines" (whinh3120s000) it is possible to enter a larger Received Quantity than the production order
completion quantity.
Message "The received quantity may not exceed the ordered quantity for % orders" is displayed, but it is possible to save
it and continue. However, it will be not possible to confirm the receipt.
SOLUTION DESCRIPTION:
Message "The received quantity may not exceed the ordered quantity for % orders" is displayed and user is forced to input
the data again.
SPECIAL INSTRUCTIONS:
None.

Solution: 133966
SITUATION IDENTIFIED IN:
"Process Transactions" (tpppc4802m000)
SITUATION DESCRIPTION:
When a transfer order from a warehouse to a project is completely received in two or more parts, it is not possible to
close the project in session "Process Transactions" (tpppc4802m000). The flag "Process Financial Result" must be
selected. Then a message comes up saying that an open warehousing order is present.
SOLUTION DESCRIPTION:
The check whether the order was completely received did not take the status into account. Therefore always indicated that
the order was not finalized.
SPECIAL INSTRUCTIONS:
None.

Solution: 133974
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the localization parameter "Cash Discount" is ON and if it is OFF at the Invoice-to BP level, then the batch created
is unbalanced if the sales invoice had cash discount at order level.
SOLUTION DESCRIPTION:
Now the batch is posted correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 133975
SITUATION IDENTIFIED IN:
"Display Gross Profit of Purchase Order Line" (tdpur4808s000)
SITUATION DESCRIPTION:
Some times the session crashes when the session is started.
SOLUTION DESCRIPTION:
Now, the session will not crash when the session is started.
SPECIAL INSTRUCTIONS:
None.

Solution: 133979
SITUATION IDENTIFIED IN:
"Copy Sales Contracts" (tdsls3801m000)
SITUATION DESCRIPTION:
When copying an active contract to another Business Partner, message "item X already included in active contract Y" is
shown. But this is incorrect as the Business Partner of contract Y is the Business Partner from the source contract, not the
Business Partner of the copied contract.
SOLUTION DESCRIPTION:
The message "item X already included in active contract Y" only appears when the item X is used in an active contract for
the Business Partner of the copied contract.
SPECIAL INSTRUCTIONS:
None.

Solution: 133989
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
When creating a Purchase Order Line, the Purchase Office country is ignored for VAT determination, even when the
Purchase Office has a VAT registration on its address.
SOLUTION DESCRIPTION:
When creating a Purchase Order Line with a Purchase Office in a different Country than the Financial Company and the
Purchase Office has a VAT registration on its address, this Country of the Purchase Office is taken into account for
determining the default VAT Code.
SPECIAL INSTRUCTIONS:
None.

Solution: 133997
SITUATION IDENTIFIED IN:
"Print Registered Invoices" (tfacp1433m000)
SITUATION DESCRIPTION:
Invoices that should be included in the selection are not always shown on the report.
SOLUTION DESCRIPTION:
The "To" fields in the selection form are only refreshed after tabbing them. When only changing the "From" fields this can
result in wrong selection criteria. After installing this solution the "To" fields are refreshed immediately after leaving the
corresponding "From" fields.
SPECIAL INSTRUCTIONS:
None.

Solution: 133999
SITUATION IDENTIFIED IN:
"Copy Budget to Project" ( tipcs2220m000 )
"Copy Project" ( tipcs2210m000 )
SITUATION DESCRIPTION:
When using session "Copy Budget to Project" ( tipcs2220m000 ) and using a zoom in the "Target Project Field" to the
session "Display First Free Numbers" ( tcmcs0547s000 ) and selecting a
serie, you will get the message "Copying not allowed because of project status" when a project with the same number and
status > active does already exist.
This results in the fact that the next project number for the selected serie is not created.
SOLUTION DESCRIPTION:
Now when using the session "Copy Budget to Project" ( tipcs2220m000 ) and using a zoom in the "Target Project Field" to
the session "Display First Free Numbers" ( tcmcs0547s000 ), it is possible to select a serie and return to the original
session without getting a message ( even when a project with the same number as the selected serie and project status >
active does already exist ).
The next project number for the selected serie is now created correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 134003
SITUATION IDENTIFIED IN:
"Import/Export Statistics" (tccom7571m000)
SITUATION DESCRIPTION:
When a cost item does not have the option "release to warehousing" activated in session "Item Sales Data" (tdisa0101s000),
then this item is not taken into account for import/export statistics.
SOLUTION DESCRIPTION:
Import/export statistics are created when appropriate.
SPECIAL INSTRUCTIONS:
THIS SOLUTION IS SUPERCEDED.
Please install solution 135155 also

Solution: 134053
SITUATION IDENTIFIED IN:
"Assign Unallocated / Advance Receipt" (tfcmg2105s000)
SITUATION DESCRIPTION:
Small Amount of balance is showing for customer even though the invoice amount is paid in full.
SOLUTION DESCRIPTION:
Now correct balance is shown for the customer balance when the invoice amount paid in full
SPECIAL INSTRUCTIONS:
None.

Solution: 134065
SITUATION IDENTIFIED IN:
"Receipt Correction" (whinh3121s000)
SITUATION DESCRIPTION:
It is not possible to toggle the "Final Receipt Flag" while doing "Receipt Correction" (whinh3121s000), for a purchase
order line with inspection, after confirming and approving the receipt line.
SOLUTION DESCRIPTION:
Changes made to allow toggling of the "Final Receipt" flag, when there is no change in either the quantity or the unit,
when doing "Receipt Correction".
SPECIAL INSTRUCTIONS:
None.

Solution: 134085
SITUATION IDENTIFIED IN:
"Created Sales Order Line History by Business Partner and Item" (tdsls5501m000)
"Created Sales Order Line History by Item" (tdsls5503m000)
SITUATION DESCRIPTION:
Field Unit is empty for cost items without inventory unit in sessions "Created Sales Order Line History by Business
Partner and Item" (tdsls5501m000) and "Created Sales Order Line History by Item" (tdsls5503m000) when the Specific
option "Only Balance per Order/Position" is chosen.
SOLUTION DESCRIPTION:
Unit fields are filled with the unit of the last entry when option "Only Balance per Order/Position" is chosen
SPECIAL INSTRUCTIONS:
-

Solution: 134093
SITUATION IDENTIFIED IN:
"Reconciliation payments and receipts" (tfcmg2102s000)
SITUATION DESCRIPTION:
When a doubtful invoice is paid via anticipated receipt and reconciled, the control account for the doubtful invoice is not
considered.
SOLUTION DESCRIPTION:
When an anticipated receipt (created for a doubtful invoice) is reconciled, the doubtful invoices control account of the
Business Partner is cancelled at the time of reconciliation.
SPECIAL INSTRUCTIONS:
None.

Solution: 134105
SITUATION IDENTIFIED IN:
"Shipment Packing Structure" (whinh3116m000)
SITUATION DESCRIPTION:
When the field "Shipped Quantity" is changed in session "Shipment Packing Structure" (whinh3116m000), which is
activated from session "Shipment Lines" (whinh4131s000), the fields "Net Weight" and "Gross Weight" aren't changed
in the session "Shipment Lines" (whinh4131s000).
SOLUTION DESCRIPTION:
When changing the field "Shipped Quantity" in session "Shipment Packing Structure" (whinh3116m000), the fields "Net
Weight" and "Gross Weight" are updated accordingly in the session "Shipment Lines" (whinh4131s000).
SPECIAL INSTRUCTIONS:
None.

Solution: 134107
SITUATION IDENTIFIED IN:
"Invoice-To Business Partner Aging Summary" (tfacr2411m000)
SITUATION DESCRIPTION:
If invoice date is greater than the advance payment (or unallocated receipt) and "Invoice fiscal year" is greater than the
"last invoice date/period" then amounts are wrongly calculated.
SOLUTION DESCRIPTION:
Amounts are calculated correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 134110
SITUATION IDENTIFIED IN:
"Sales Invoice" (tfacr1110s000)
SITUATION DESCRIPTION:
Tax amount posted incorrectly for receipt transaction in case of partly received sales invoice. This problem is happening
in the following conditions.
1) Credit note linked to the sales invoice partly
2) In the receipt transaction, discount is given for partly received sales invoice.
SOLUTION DESCRIPTION:
Tax amount posted correctly for receipt transaction in case of partly received sales invoice
SPECIAL INSTRUCTIONS:
None.

Solution: 134131
SITUATION IDENTIFIED IN:
"Confirm receipts session whinh3520m000 "Receipts"" (whinh3520m000)
SITUATION DESCRIPTION:
When confirming a final receipt using session whinh3520m000 "Receipts" of 0 quantity, the error Unresolved reference error
to function tfint.dlltfacp.create.last.ppv.transaction occurs.
SOLUTION DESCRIPTION:
Problem only occurred in the localized package modified the software and the problem does not occur.
SPECIAL INSTRUCTIONS:
None.

Solution: 134137
SITUATION IDENTIFIED IN:
"Enter Receipt Amounts for Assignment" (tfcmg2107s000)
SITUATION DESCRIPTION:
1. During automatic write off, payment difference tolerances, defined in CMG parameters, are not taken into
consideration.
2. Discount is not calculated for overpaid invoices.
SOLUTION DESCRIPTION:
1. During automatic write off, payment difference tolerances in CMG parameters are considered.
2. Discount is calculated for overpaid invoices.
SPECIAL INSTRUCTIONS:
None.

Solution: 134141
SITUATION IDENTIFIED IN:
"Print Business Partner wise Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
Invoices already paid are shown in Aging Analysis report when it is sorted by "Sales Representatives"
SOLUTION DESCRIPTION:
Already paid Invoices are not shown in Aging Analysis report when it is sorted by "Sales Representatives"
SPECIAL INSTRUCTIONS:
None.

Solution: 134147
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000).
"Sales-Order Lines" (tdsls4101s000).
SITUATION DESCRIPTION:
Wrong country (tdsls401.ccty) defaulted when changing a sales order line's Ship-to Address (tdsls401.stad).
SOLUTION DESCRIPTION:
Recalculation of tax modified.
When changing any tax-related field on a Sales Order Header or Line, tax will be recalculated automatically.
No question is asked anymore whether or not to recalculate tax:
- When changing the Ship-to Address (tdsls400.stad), a question is asked if all Line's Ship-to addresses should be adjusted.
If answered 'Yes', tax is recalculated for all Lines as well.
- When changing Invoice-to Address (tdsls400.itad) or Sales Office (tdsls400.cofc), tax code of lines is recalculated
without user intervention.
- When changing any tax-related field like Warehouse (tdsls401.cwar), Ship-to Address (tdsls401.stad) or Ship-to Business
Partner (tdsls401.stbp), no question is asked anymore whether to recalculate tax or not. From now on tax will always be
recalculated.
SPECIAL INSTRUCTIONS:
Not Applicable.

Solution: 134151
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When all receipts are done and a final zero receipts is made for a subcontracting purchase order linked to a production
order, the production order is not getting closed and an error message is generated saying "Purchase Invoice for purchase
order not yet processed".
SOLUTION DESCRIPTION:
The zero final receipts made after all receipts done to a subcontracting purchase order will not be a hurdle to close the
production order linked to the subcontracting purchase order.
SPECIAL INSTRUCTIONS:
None.

Solution: 134166
SITUATION IDENTIFIED IN:
"Select invoices for reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
Trade notes that are not yet overdue are selected for reminding.
SOLUTION DESCRIPTION:
For payment documents, the document date was considering for reminding . Now the due date will be considered for
reminding.
SPECIAL INSTRUCTIONS:
None.

Solution: 134180
SITUATION IDENTIFIED IN:
"Purchase Requisitions" (tdpur2101s000)
SITUATION DESCRIPTION:
1. Fields "Delivery Warehouse" & "Delivery Address" should be disabled when a Requisition is submitted. This was not
happening.
2. While submitting the requisition, "Last Transaction Date" field in table "Purchase Requisitions" and "Requisition
Processing Date" field in table "Purchase Requisition Approval" get different time values and hence the Approval field is
not accessible.
SOLUTION DESCRIPTION:
Now, if a requisition is submitted, delivery warehouse and address cannot be changed.
Also, the "Last Transaction Date" field in table "Purchase Requisitions" and "Requisition Processing Date" field in table
"Purchase Requisition Approval" will have same values when a requisition is submitted so that Approval is done.
SPECIAL INSTRUCTIONS:
None.

Solution: 134182
SITUATION IDENTIFIED IN:
"Convert Electronic Bank Statements" (tfcmg5202m000)
SITUATION DESCRIPTION:
During conversion of Electronic Bank Statements (tfcmg5202m000), amounts are converted to 0.00.
SOLUTION DESCRIPTION:
Amounts are converted correcly during the conversion of Electronic Bank Statements.
SPECIAL INSTRUCTIONS:
None.

Solution: 134197
SITUATION IDENTIFIED IN:
"Receipt Lines" (whinh3120s000)
SITUATION DESCRIPTION:
Error messages appears and saving of receipt line is not possible, when an "Unexpected Receipt" line is created and the
order quantity is entered.
There are two situations in which unexpected receipts can occur
1. When "Unexpected Receipts" is selected through the specific option in warehouse receipts.
2. When the final receipt flag is set to 'Yes' for the inbound order line, and more goods are received for the same inbound
order line.
SOLUTION DESCRIPTION:
Error messages do not appear, when an "Unexpected Receipt" line is created and the order quantity is entered, and saving
of Receipt line is possible.
SPECIAL INSTRUCTIONS:
None.

Solution: 134211
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4501m000).
SITUATION DESCRIPTION:
For Consignment Invoicing Orders it is allowed to set "Inventory Issue Status" (tdsls401.isss) on a Sales Order Line to
"Issue Components".
This can be confusing because solution #110442-9 made this impossible for Consignment Replenishment orders .
SOLUTION DESCRIPTION:
"Inventory Issue Status" (tdsls401.isss) cannot be set to "Issue Components" in case of Consignment Invoicing Orders.
Due to limitations of Warehousing Module in handling generated Transfer Orders, solution #110442-9 made it impossible
to use this status in case of Consignment Replenishment Orders. Only status "Issue Main Item" is valid in that case.
For consistency reasons this now also applies to Consignment Invoicing Orders.
SPECIAL INSTRUCTIONS:
Not Applicable.

Solution: 134220
SITUATION IDENTIFIED IN:
"Link Invoices to Credit Note II" (tfacr2121m000)
SITUATION DESCRIPTION:
Incorrect calculation of receipt schedule balance, because of this wrong amounts posted during payment difference.
SOLUTION DESCRIPTION:
Correct balance is calculated and posted for receipt schedules
SPECIAL INSTRUCTIONS:
Nil

Solution: 134233
SITUATION IDENTIFIED IN:
"Addresses" (tccom4530m000)
SITUATION DESCRIPTION:
When selecting an address and then press the print button the selected address is not transferred to the print session.
SOLUTION DESCRIPTION:
When an address is selected this will be transferred to the print session as an address print range. When there is no record
selected the full range for addresses is taken as print selection.
SPECIAL INSTRUCTIONS:
None.

Solution: 134242
SITUATION IDENTIFIED IN:
"Addresses" (tccom4130s000)
SITUATION DESCRIPTION:
The check on tax number is only done on digits and letters.
SOLUTION DESCRIPTION:
All positions of the tax number will be checked except for trailing spaces which will be ignored for checking.
SPECIAL INSTRUCTIONS:
None.

Solution: 134258
SITUATION IDENTIFIED IN:
"Reprint Invoices" (cisli2405m000)
SITUATION DESCRIPTION:
When the invoices are reprinted, then the page numbers are not printed correctly.
SOLUTION DESCRIPTION:
When the invoices are reprinted, then the page numbers are to be printed correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 134291
SITUATION IDENTIFIED IN:
"Transactions" (tfgld1101m000)
SITUATION DESCRIPTION:
In a multi-finance/single-logistics environment, following problem occurs:
When linking service order lines to a financial document, one can choose a service order line of a service order that
has got another financial company than the target company on the document in Finance. But when finalizing the batch,
error message " The BaanERP Service amount not completely split up" (tfglds0634) appears.
SOLUTION DESCRIPTION:
1. It is not possible to link a service order line of a service order that has got another financial company than the target
company on the document in Finance.
2. When finalizing a batch, the service order lines will be checked in order to find out if the costs are split up correctly.
Here, the amount given from Finance is checked with the amount retrieved from the service order lines. These amounts
are converted in the same currency (local currency).
SPECIAL INSTRUCTIONS:
None.

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

Solution: 134316
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When trying to confirm a receipt line that has a zero receipt quantity and "Final Receipt" flag checked, an empty message
is displayed and the receipt line is not confirmed.
SOLUTION DESCRIPTION:
It is possible to confirm a receipt line that has zero receipt quantity and "Final Receipt" flag checked without any error
messages.
SPECIAL INSTRUCTIONS:
None.

Solution: 134330
SITUATION IDENTIFIED IN:
"Split Shipment" (whinh4231m000)
SITUATION DESCRIPTION:
It can take too long for this session to present the first set of data.
SOLUTION DESCRIPTION:
The initial search routine is changed so that it is more logic and that the search time is shorter.
SPECIAL INSTRUCTIONS:
Please also load solution 134789

Solution: 134333
SITUATION IDENTIFIED IN:
"Copy Sales Order" (tdsls4201s000).
SITUATION DESCRIPTION:
1. New form is not showing new label "Use Delivered Quantities" (tdsls4201.03) as delivered via solution #116720.
2. Label for field tdsls4201s0001.copy.only.header very unclear in Dutch ("Alleen kop kopieren" instead of "Alleen kop
kop.")
SOLUTION DESCRIPTION:
This solutions solves 2 issues mentioned above.
1.Form "Copy Sales Order" (tdsls4201s0001), as it was modified by solution #116720, is correctly displayed.
With solution #116720 a new label was introduced for field tdsls4201s0001.add.up.deliveries.
The description of this label was changed from "Cumulate Deliveries" to "Use Delivered Quantities".
2. For Dutch cusomers: a more speaking label is used. Description "Alleen kop kopieren" is now used instead of "Alleen
kop kop." (field: tdsls4201s0001.copy.only.header).
SPECIAL INSTRUCTIONS:
This solution may be needed after downloading solution #116720.

Solution: 134335
SITUATION IDENTIFIED IN:
"tfacrl403m00l" (Print Receipt Schedule)
SITUATION DESCRIPTION:
Session is taking long time to print Report.
SOLUTION DESCRIPTION:
Performance of the session "Print Receipt Schedule" is improved
SPECIAL INSTRUCTIONS:
None.

Solution: 134339
SITUATION IDENTIFIED IN:
"Print Payment Notification" (tfcmgl443m00l)
SITUATION DESCRIPTION:
Report was always printed irrespective of the number given in 'Documents by Business Partner'.
SOLUTION DESCRIPTION:
Value in 'Documents by Business Partner' is the minimum number of composed records to be present for each of the
Business Partners in the payment batch for printing the 'Payment Notification'.
SPECIAL INSTRUCTIONS:
None.

Solution: 134342
SITUATION IDENTIFIED IN:
"Print Aging Summary" (tfacr2411m000)
SITUATION DESCRIPTION:
If invoice/credit note fiscal period is greater than the receipts/assignment periods then wrong data is printed.
SOLUTION DESCRIPTION:
If invoice/credit note fiscal period is greater than the receipts/assignment periods , the balance is now correctly
calculated.
SPECIAL INSTRUCTIONS:
None.

Solution: 134349
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
If the Integration Mapping Scheme for the Purchase / General Costs is maintained with the Logistic Company "0", then
the Dimensions are not defaulted correctly when user maintains a Purchase Order Line for a Cost Item. The Ledger
Account is defaulted correctly on to the Purchase Order Line even when the Integration-Mapping Scheme is maintained
for the Logistic Company "0".
SOLUTION DESCRIPTION:
The dimensions are defaulted now even when the Integration-Mapping Scheme is maintained with the Logistic Company
"0".
SPECIAL INSTRUCTIONS:
None.

Solution: 134378
SITUATION IDENTIFIED IN:
"Sales Orders" (tdsls4100s000)
SITUATION DESCRIPTION:
Sales Order Line is recalculated with blank tax code, when changing any tax-related field on the corresponding sales order
Header. This only applies to the FIRST Line; for subsequent lines the tax code is calculated correctly.
However, if the combination of tax country and blank tax code is not a valid one, no changes will be made to any of the
lines.
SOLUTION DESCRIPTION:
When changing any tax-related field on a Sales Order Header, forcing a recalculation of tax for all related Sales Order
Lines, recalculation should be done correctly.
SPECIAL INSTRUCTIONS:
Not Applicable.

Solution: 134380
SITUATION IDENTIFIED IN:
"Specifications Delivered, not yet invoiced " (tfacr1432m000)
SITUATION DESCRIPTION:
On the Report ' Specifications Delivered, not yet invoiced ' the Order-line Status is needed for further interpretation of
the results. This status was displayed incorrectly which led to confusion in which action should be taken.
SOLUTION DESCRIPTION:
The Report ' Specifications Delivered, not yet invoiced ' will now print a status 'Open' or 'Closed' depending on the
order-line status within logistics. The status is printed per sales orderline. If the issue is booked and the cost of goods
sold is not booked then the status is 'Open' which means invoicing should take place. If the issue and the cost of goods
sold is booked then the status is 'Closed'. Please note that if a sales orderline has backorders then the status can switch
from 'Closed' to 'Open'. This happens when a backorder is confirmed and for that backorder only the issue is booked and
not the cost of goods sold. It is not possible to print tfacr1432m000 per sales orderline sequence.
SPECIAL INSTRUCTIONS:
None.

Solution: 134381
SITUATION IDENTIFIED IN:
"Print Packing Slips" (whinh4475m000)
SITUATION DESCRIPTION:
When printing the delivery note, the name associated with delivery address is not printed but instead the associated with
the address of the business partner is printed.
SOLUTION DESCRIPTION:
Name associated with the delivery address is printed, and not the name associated with the business partner.
SPECIAL INSTRUCTIONS:
None.

Solution: 134384
SITUATION IDENTIFIED IN:
"Maintain Sales Invoices" (tfacr1110m000)
SITUATION DESCRIPTION:
When the session " print non finalized transactions" is executed , the text entered in the Sales invoice header is not
printed for the control account .
SOLUTION DESCRIPTION:
Now, when the session " print non finalized transactions" is executed , the text entered in the Sales invoice header is
printed for the control account.
SPECIAL INSTRUCTIONS:
None.

Solution: 134417
SITUATION IDENTIFIED IN:
"Print Order Acknowledgements/RMAs" (tdsls4401m000)
SITUATION DESCRIPTION:
If Group Tax codes are used on an order line and the Order Acknowledgement is printed, the report does not show the tax
in the totals line.
SOLUTION DESCRIPTION:
The tax is now printed in the totals line on the Order Acknowledgement for Group Tax Codes.
SPECIAL INSTRUCTIONS:
None.

Solution: 134421
SITUATION IDENTIFIED IN:
"Remove Closed Warehousing Orders" (whinh2250m000)
SITUATION DESCRIPTION:
It is not possible to remove Receipt Headers via a standard Baan session.
SOLUTION DESCRIPTION:
The functionality of removing receipt headers has been added to session "Remove Closed Warehousing Orders"
(whinh2250m000).
Receipt headers for which no receipt lines do exist will be deleted when running this session.
SPECIAL INSTRUCTIONS:
None.

Solution: 134433
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
The invoice amount generated by the selfbilling process was based on the Order amount and order quantity. When there are
multiple receipts, then the Invoice amount calculated with this method differed from the Invoice amount calculated based
on the Quantity and price by few cents.
SOLUTION DESCRIPTION:
The Invoice amount is now calculated based on the Receipt quantity and the Price and discount information from the
order.
SPECIAL INSTRUCTIONS:
None.

Solution: 134461
SITUATION IDENTIFIED IN:
"Sales Quotation Lines" (tdsls1101s000)
SITUATION DESCRIPTION:
When entering a Sales Quotation Line (tdsls1101s000), the vat code is defaulted.
When the vat code of the Item Sales Data is used, and this code does not exist for the vat-country, the message "Tax Code
by Country not found" is displayed, and the line cannot be saved.
SOLUTION DESCRIPTION:
When the vat code of the item sales data is used, and this code does not exist for the vat-country, the tax code is made
empty. Sales Order Lines and Sales Quotation Lines are working similarly now.
SPECIAL INSTRUCTIONS:
None.

Solution: 134465
SITUATION IDENTIFIED IN:
"Print Composed Direct Debits" (tfcmg4403m000)
SITUATION DESCRIPTION:
In report "Print Composed Direct Debits" (tfcmg4403m000), the business partner name is printed as "********".
SOLUTION DESCRIPTION:
The name of the Business Partner mentioned in the address of the pay-by business partner is printed on the report.
SPECIAL INSTRUCTIONS:
None.

Solution: 134491
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
In a triangular invoicing scenario, zero prices and amounts are booked for sales return orders when transfer pricing method
is "Valuation Price".
This situation occurs when the sales return order is not linked to a normal sales order and no surcharges are involved.
SOLUTION DESCRIPTION:
Prices and amounts are calculated properly based on the valuation price and the amounts are displayed correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 134498
SITUATION IDENTIFIED IN:
"Assign unallocated / advance receipts to invoices" (tfcmg2105s000)
SITUATION DESCRIPTION:
Unable to allocate Unallocated/ Advance documents to invoices with tax calculation on Transaction Line level and more
than 10 transactions lines including tax.
SOLUTION DESCRIPTION:
Assigning of unallocated/advanced documents to an invoice with tax calculation on Transaction Line level, which has more
than 10 transaction lines including tax, can be done properly without getting a fatal error.
SPECIAL INSTRUCTIONS:
None.

Solution: 134500
SITUATION IDENTIFIED IN:
"One-time Business Partners Addresses" (tfacp1102s000)
SITUATION DESCRIPTION:
In case an invoice with bank data and one-time business partner address is entered, the bank data fields remain disabled.
This is not correct.
After saving and clicking on the address field the bank data fields are enabled
SOLUTION DESCRIPTION:
After installing this solution the bank data fields are enabled when entering an invoice with bank data and one-time
business partner address
SPECIAL INSTRUCTIONS:
None.

Solution: 134520
SITUATION IDENTIFIED IN:
"Sales Invoice details" (tfacr2100s000)
SITUATION DESCRIPTION:
'Due Date' of sales invoice detail does not change though the date of 'Planned Receipt Date' in receipt schedule is
changed.
SOLUTION DESCRIPTION:
Now, 'Due Date' of sales invoices detail changes whenever the date of 'Planned Receipt Date' in receipt schedule is
changed.
SPECIAL INSTRUCTIONS:
None.

Solution: 134525
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
Sales/Issue and Sales Invoicing Sales/COGS are not congruent if rates are changed after shipments.
For COGS bookings, the same rates, as on delivery date has to be used.
SOLUTION DESCRIPTION:
Now the COGS are booked using the same rate as on the delivery date. So the Issue and the COGS tally.
SPECIAL INSTRUCTIONS:
None.

Solution: 134530
SITUATION IDENTIFIED IN:
"Print Sales Orders" (tdsls4405m000)
SITUATION DESCRIPTION:
The Sales Order Report is printed with option 'Order Lines' checked. When a sales order is split and partially delivered,
the report shows incorrect values for the delivered quantities and for amounts.
SOLUTION DESCRIPTION:
Quantities and amounts on the report are correct. The delivered quantity for a total line is the sum of all the delivered
quantities of the details. The amounts are based on the setting of the field 'Calculate Amount Based on'
SPECIAL INSTRUCTIONS:
None.

Solution: 134531
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When the level of tax calculation is set to Transaction Line and a Purchase Order is entered with tax specified, the
amount defaulted in session "tfacp1110s000 - Register Purchase Invoices" is the Order Amount minus the Vat amount. When
the tax calculation is set to header now the tax is recalculated taking the amount defaulted as gross.
When from the beginning the level of vat calculation is set to header all defaulting is done correctly.
SOLUTION DESCRIPTION:
When the level of vat calculation is set to transaction line the gross order amount is defaulted now. The amount is now
similar defaulted as done with level of tax calculation set to header.
SPECIAL INSTRUCTIONS:
None.

Solution: 134546
SITUATION IDENTIFIED IN:
"Section codes" (tfgldl108m001l)
SITUATION DESCRIPTION:
The next labels were missing in the Japanese localization:
On form gld1520 the label Taxable amount in HC, on form gld1402 the label Print Header report, form cmgl170 the label
Date details, and on report cor3401 the labels Cono and Type and on report cmgl4221 the label for the dot, and on the
form gldl108 a label for the description was programmed twice, so one is removed.
SOLUTION DESCRIPTION:
The mentioned forms, reports and labels are delivered
SPECIAL INSTRUCTIONS:
Because forms are involved, a convert to runtime for forms and menus have to be executed.

Solution: 134562
SITUATION IDENTIFIED IN:
"Import/Export Statistics" (tccom7571m000)
SITUATION DESCRIPTION:
The parameter "Method of Logging Cost/Service Items" as defined in session "Intra EU Transaction Parameters"
(tccom7500m000) is not taken into account when it is set to "If Commodity Code Filled".
This means that import/export statistics are also logged for cost/service items without commodity code in this case.
SOLUTION DESCRIPTION:
If the parameter "Method of Logging Cost/Service Items" as defined in session "Intra EU Transaction Parameters"
(tccom7500m000) is set to "If Commodity Code Filled", then import/export statistics are only logged for cost/service
items with a commodity code.
SPECIAL INSTRUCTIONS:
None.

Solution: 134572
SITUATION IDENTIFIED IN:
"Service Order: Estimated Material Costs" (tssoc2120m000)
SITUATION DESCRIPTION:
A text is entered in the Material line of a Service Order. A delivery type is chosen which results in the creation of
"Issue" type Warehousing Order is chosen. The Service Order is released and the Warehousing Orders are created. How
ever the Text entered in the Material Line is not carried to the Warehousing Orders.
SOLUTION DESCRIPTION:
The Texts entered in the Material Lines are carried on to the Warehousing Orders created for those Material Lines.
This enables the user to print the Service Order Material Text on the Goods Receive Note or on the Packing Slip.
Special Note:
===========
Baan provides the facility of hiding / printing a text or a part of a text in the Reports.
1) When a line in the Text is preceded by a '<' (less than) symbol, this line is meant for internal reports only (example
Goods Receive Note). These lines will not be printed on external documents (example Packing Slip).
2) When a line in the Text is preceded by a '>' (greater than) symbol, this line is meant for external reports only
(example Packing Slip). These lines will not be printed on internal documents (example Goods Receive Note).
SPECIAL INSTRUCTIONS:
None.

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

Solution: 134584
SITUATION IDENTIFIED IN:
"Post Electronic Bank Statements" (tfcmg5222m000)
SITUATION DESCRIPTION:
The posting of EBS batches with session 'Post Electronic Bank Statements' (tfcmg5222m000) stops in case of doubtful
invoice-to Business Partners. The posting can be continued after changing the status of the Business Partner into 'Active'.
Everytime the process stops a new batch is created.
SOLUTION DESCRIPTION:
Transactions of doubtful invoice-to Business Partners within an EBS batch can be posted.
SPECIAL INSTRUCTIONS:
None.

Solution: 134628
SITUATION IDENTIFIED IN:
"Print Business Partner wise Aging Analysis" (tfacr2420m000)
SITUATION DESCRIPTION:
'Aging analysis of Business partner wise' report is not matching with 'Aging analysis of Business Partner summary' report
and it is showing a difference of 0.01
SOLUTION DESCRIPTION:
'Aging analysis of Business partner wise' report is matching with 'Aging analysis of Business Partner summary' report.
SPECIAL INSTRUCTIONS:
None.

Solution: 134630
SITUATION IDENTIFIED IN:
"Checks" (tfcmg1260s000)
"Print Forwarding Notes" (tdsls4421m000)
SITUATION DESCRIPTION:
Two main sessions exist that display amounts in words:
1. In the sub session 'Transfer Payments' (tfcmg1260m000) payments can get transferred to a check. On these checks the
amount is presented both in digits and in words.
2. In the session "Print Forwarding Notes" (tdsls4421m000) bills of lading can be printed. When "Cash on Delivery" has
been selected as the type of bill of lading the amount to be received is printed in words as well.
Amounts are incorrectly translated to words in Spanish language on check reports.
SOLUTION DESCRIPTION:
Amounts are correctly translated to words in Spanish language on check reports.
SOLUTION 135154 ALSO AFTER INSTALLING THIS(134630) SOLUTION ***
VERSION(S):
B40_c, B50_b, B50_c (Spanish language)
SPECIAL INSTRUCTIONS:
*** Please install also solution 135154 after installing this solution ***

Solution: 134653
SITUATION IDENTIFIED IN:
"Link credit notes to invoices II" (tfacr2121s000)
SITUATION DESCRIPTION:
When two sales invoices are created each with schedules, a credit note is assigned to sales invoice schedules, batch is
left unbalanced and the amounts are not getting stored correctly in General Ledger.
SOLUTION DESCRIPTION:
One sales credit note is assigned to several sales invoices with schedules, the batch is left balanced, all the assignment
records are getting stored correctly in General Ledger.
SPECIAL INSTRUCTIONS:
None.

Solution: 134659
SITUATION IDENTIFIED IN:
"Business Partner Totals By Company" (tfacp2534m000)
"Business Partner Totals By Company" (tfacr2534m000)
SITUATION DESCRIPTION:
In session "Business Partner Totals By Company" (tfacp2534m000), the totals are always shown by reference currency.
SOLUTION DESCRIPTION:
The totals are shown in the home currency. The "Rotate Currency" option has been enabled in the script.
SPECIAL INSTRUCTIONS:
None.

Solution: 134665
SITUATION IDENTIFIED IN:
"Compose/Print/Post Invoices" (cisli2200m000)
SITUATION DESCRIPTION:
When the amount is shorter than 14 digits, no leading zeros are printed in the payment slip.
SOLUTION DESCRIPTION:
Now the leading zeroes are printed in the reference field of the payment slip.
SPECIAL INSTRUCTIONS:
None.

Solution: 134679
SITUATION IDENTIFIED IN:
"Purchase Contract Lines" (tdpur3101s000)
SITUATION DESCRIPTION:
User is not allowed to enter a position number of 9999 in the Purchase Contract Lines but is allowed to enter a position
of 9998.
SOLUTION DESCRIPTION:
User will be allowed to enter a position number of 9999 in the Purchase Contract Lines.
SPECIAL INSTRUCTIONS:
None.

Solution: 134680
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
1.Confirmed Delivery dates and Changed delivery dates are copied to the detail session, if it is filled in the Total line/
original line of the purchase order.
2.The field VAT Country Code "tdpur401.cvat" in the purchase order lines session "tdpur4101s000" is disabled.
3.When the actual delivery date in the purchase order receipt is set to blank and saved back order is created
automatically, Delivery date is blank after creation of the back order also and the receipt is not confirmed.
SOLUTION DESCRIPTION:
1.To maintain the dates in the detail session, now the user is been prompted with a question Yes/ No? When the answer is YES,
then the dates are maintained in the detail session. If it is not, then the dates are cleared off in the Original as well as Detail
lines.
And in the Line Details session, to maintain the same dates while splitting the detail, a similar question will be asked. If
the answer is YES, then the dates will be maintained and if it is NO, Confirmed and Changed delivery dates will be cleared. It
is also noted that if a line has to be split, then the split quantity should be less than the ordered quantity of that
particular line. If the user tries to enter the same and greater than the ordered quantity, then a warning message will pop
up and the user will be again prompted to correct the order quantity.
2.The field VAT Country Code "tdpur401.ccty" is enabled in the purchase order lines session.
3.When the receipt is saved, and the back order is created delivery date is filled with current date and the receipt is
confirmed automatically.
SPECIAL INSTRUCTIONS:
When your VRC is B50_b or B50_c please also install solution 135035.

Solution: 134683
SITUATION IDENTIFIED IN:
"Print Reminders" (tfacr3420m000)
SITUATION DESCRIPTION:
Interest gets calculated for the unallocated receipts, on re-executing session without closing, after the first execution
SOLUTION DESCRIPTION:
Interest does not get calculated for the unallocated receipts, on re-executing session without closing, after the first
execution
SPECIAL INSTRUCTIONS:
None.

Solution: 134695
SITUATION IDENTIFIED IN:
"Remove Fully Paid Purchase Invoices" (tfacp2250m000)
SITUATION DESCRIPTION:
The documents in table "Reference to Finalized Transactions" (tfgld126) are not deleted if the related documents in table
"Finalized Transactions" (tfgld106) are deleted.
SOLUTION DESCRIPTION:
When running session "Remove Fully Paid Purchase Invoices" (tfacp2250m000) or "Remove Fully Paid Sales Invoices)"
(facr2260m000), the documents in table "Reference to Finalized Transactions" (tfgld126) are also deleted.
SPECIAL INSTRUCTIONS:
None.

Solution: 134699
SITUATION IDENTIFIED IN:
"Assign unallocated / advance receipts to invoices" (tfcmg2105s000)
"Assign unallocated / advance payments to invoices" (tfcmg2106s000)
SITUATION DESCRIPTION:
With the sessions "Assign unallocated / advance receipts to invoices" (tfcmg2105s000) and "Assign unallocated / advance
payments to invoices" (tfcmg2106s000) unallocated documents can be assigned to invoices. When an unallocated document
is assigned to more than one invoice and for that same Business partner a new unallocated document is created with the
same document number (but with another line number), the balance of the previous unallocated document has changed after
processing this second assignment. Furthermore, the other unallocated documents that were created within the same batch
show up in the list for the next unallocated document, even when the balance is zero and they can be maintained as well.
This is incorrect.
SOLUTION DESCRIPTION:
The list in the sessions "Assign unallocated / advance receipts to invoices" (tfcmg2105s000) and "Assign unallocated /
advance payments to invoices" (tfcmg2106s000)only shows the other unallocated documents from the same batch, when
the balance is unequal to zero. They can only be maintained from the place where they were processed originally.
SPECIAL INSTRUCTIONS:
None.

Solution: 134702
SITUATION IDENTIFIED IN:
"Select Invoices for Reminding" (tfacr3210m000)
SITUATION DESCRIPTION:
Schedule lines of sales invoice selected for reminding, even if an anticipated document exists for the sales invoice
SOLUTION DESCRIPTION:
Schedule lines of sales invoice are not selected for reminding, if an anticipated document exists for the sales invoice
SPECIAL INSTRUCTIONS:
None.

Solution: 134704
SITUATION IDENTIFIED IN:
"Direct Network Communication" (ecedi7205m000)
SITUATION DESCRIPTION:
System is searching for Active Sales Contracts when contracts are not implemented.
SOLUTION DESCRIPTION:
Improved search for active Sales Contracts. Now Sales Parameter "Contract Module Implemented" (tdsls000.cons.3) is taken
into account. If this parameter is set to 'false', no active Sales Contracts are in place. Hence, the search for such a
Contract can be aborted.
Performance of Sales Order entry (especially when reading Sales Orders by means of EDI) improved significantly.
SPECIAL INSTRUCTIONS:
Not Applicable.

Solution: 134730
SITUATION IDENTIFIED IN:
"Print invoice to Business Partner Open Entries" (tfacr2421m000)
SITUATION DESCRIPTION:
Changed amounts are not displayed when the credit note amount is modified through a sales correction.
SOLUTION DESCRIPTION:
Changed amounts are displayed for credit note.
SPECIAL INSTRUCTIONS:
Nil

Solution: 134746
SITUATION IDENTIFIED IN:
"Confirm Shipments" (whinh4275m000)
SITUATION DESCRIPTION:
In this session several performance problems occurred.
SOLUTION DESCRIPTION:
The database functions that are responsible for the performance problems are optimized to improve performance.
SPECIAL INSTRUCTIONS:
If your Current VRC is:
B50L_c_bgl0: please down load also solution 134878

Solution: 134764
SITUATION DESCRIPTION:
1. The field 'lot code' on a Sales Order Line (tdsls4101s000) is displayed as empty after the line is delivered.
2. When entering a sales order line for a planned item with order policy as 'To order', shortage menu does not pop up.
This menu is needed to perform ATP check (only B50_c)
SOLUTION DESCRIPTION:
1. The field 'lot code' on a Sales Order Line (tdsls4101s000) always displays the correct data.
2. When entering a sales order line for a planned item with order policy as 'To order', shortage menu does pop up.
SPECIAL INSTRUCTIONS:
None.

Solution: 134786
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100)
SITUATION DESCRIPTION:
After reconciling and unreconciling a check payment, it is possible to delete the reconciliation transaction from session
'Bank Transactions' (tfcmg2100s000).
SOLUTION DESCRIPTION:
If the status of an anticipated document is changed from 'Completed' to 'Open', it's not possible anymore to delete the
reconciliation transaction from session 'Bank Transactions'. Message: 'Reconciliation data found for this payment
document. Record cannot be deleted' will be displayed
SPECIAL INSTRUCTIONS:
n/a

Solution: 134789
SITUATION IDENTIFIED IN:
"Split Shipment" (whinh4231m000)
SITUATION DESCRIPTION:
It can take too long for this session to present the first set of data.
SOLUTION DESCRIPTION:
The initial search routine is changed so that it is more logic and that the search time is shorter.
SPECIAL INSTRUCTIONS:
Please also load solution 134799

Solution: 134792
SITUATION IDENTIFIED IN:
"Transfer Payments" (tfcmg1260m000)
SITUATION DESCRIPTION:
When a payment is made to a one-time business partner, the address maintained in session "One-time Business Partner
Addresses" (tfacp1102s000) is not getting filled up in the DTA file, which is created.
SOLUTION DESCRIPTION:
If the business partner is a one-time business partner, then the address details are picked up from the session "One-time
Business Partner Adressess".
SPECIAL INSTRUCTIONS:
None.

Solution: 134797
SITUATION IDENTIFIED IN:
"Add Costs" (tfacp1133s000)
SITUATION DESCRIPTION:
In session "Match/Approve Purchase Invoices" (tfacp2107s000), when the session "Add costs" (tfacp1133s000) is started and
if the period of the invoice has been closed, the periods default to the next open period. In case it is a correction period, it
defaults with the correction period.
SOLUTION DESCRIPTION:
The periods default to the next open period, which is not a correction period.
SPECIAL INSTRUCTIONS:
None.

Solution: 134799
SITUATION IDENTIFIED IN:
"Split Shipment" (whinh4231m000)
SITUATION DESCRIPTION:
It can take too long for this session to present the first set of data.
SOLUTION DESCRIPTION:
The initial search routine is changed so that it is more logic and that the search time is shorter.
SPECIAL INSTRUCTIONS:
None.

Solution: 134802
SITUATION IDENTIFIED IN:
"Read Bank File" (tfcmgl214m00l)
SITUATION DESCRIPTION:
Session 'Read Bank File (tfcmgl214m00l)' is incompatible with non-unix server. When bank files are read on a Windows
system, fatal error: PTY Error: "No more pty's available" (e=0) is given.
SOLUTION DESCRIPTION:
Session 'Read Bank File (tfcmgl214m00l)' is compatible with unix and non-unix servers. No fatal error is occuring
anymore.
SPECIAL INSTRUCTIONS:
None.

Solution: 134824
SITUATION IDENTIFIED IN:
"Purchase Requisition Lines" (tdpur2101m000)
SITUATION DESCRIPTION:
The Item Types Subcontracting and Equipment are not allowed in Purchase Requisitions. This restriction has to be
relaxed for Project Subcontracting and Project Equipment items.
SOLUTION DESCRIPTION:
1. In Purchase Requisitions, the check for Item has been modified. Currently, Items of type Subcontracting or Equipment
will be allowed only if they are linked to a Project (TP).
2. Purchase Requisitions for Subcontracting or Equipment can be converted directly to Purchase Orders allowed only if
those Items are linked to a project.
SPECIAL INSTRUCTIONS:
None.

Solution: 134839
SITUATION IDENTIFIED IN:
"Cycle Count / Adjustment order lines" (whinh5101s000)
SITUATION DESCRIPTION:
When processing cycle counting orders for an item which does have package definitions and some inventory is allocated
the following blocking message could be returned: "Negative net available on hand not allowed (on hand - on hold -
allocated - variance)" (message code: whinhs0026). This could happen even though sufficient inventory is available to be
decreased.
When multiple cycle count lines exist for a stock point, the stock point was unblocked after the first cycle counting line
that was processed, despite of the fact that other unprocessed lines could still be present.
SOLUTION DESCRIPTION:
The check on inventory availability when processing a cycle-counting order has been corrected which allows the user to
process the cycle count order in above mentioned situation.
Unblock of stock point is only done when all cycle counting lines for the same stock point have been processed.
SPECIAL INSTRUCTIONS:
None.

Solution: 134842
SITUATION IDENTIFIED IN:
"Maintenance Sales Order Lines" (tsmsc1110m000)
SITUATION DESCRIPTION:
1) In version B52_a, when saving a new Maintenance Sales Order Line with the warehouses filled, the message "Fatal
Error: Illegal number of args (26) for function tsint.dllwhinh.generate.wh.order expected 29" appears.
2) For versions B50_b, B50_c and B52_a, when warehouse order text is changed, the change appears in the service order
also.
SOLUTION DESCRIPTION:
1) It is now possible to save a maintenance sales order line correctly.
2) Changes in warehousing order text are not reflected back to service order text.
SPECIAL INSTRUCTIONS:
None.

Solution: 134868
SITUATION IDENTIFIED IN:
"Sales-Order Lines" (tdsls4101s000).
SITUATION DESCRIPTION:
When adding a non-project item in "Sales-Order Lines" (tdsls4101s000), field "Project" (tdsls401.cprj) gets defaulted with
the value this field has on the first occurrence as displayed in "Sales-Order Lines" (tdsls4501m000).
SOLUTION DESCRIPTION:
Defaulting of field "Project" is corrected.
When a project-item is entered, the project field will be filled with the item's project segment.
When a non-project item is entered, the project field can be filled manually.
SPECIAL INSTRUCTIONS:
Not Applicable.

Solution: 134875
SITUATION IDENTIFIED IN:
"Selection for Automatic Reconciliation" (tfcmg2123s000)
SITUATION DESCRIPTION:
Anticipated documents selected via 'Select for Automatic Reconciliation' (tfcmg2122s000) are not displayed when session
'Selection for Automatic Reconciliation' (tfcmg2123s000) comes up. The user needs to scroll down to see the selected
records.
SOLUTION DESCRIPTION:
Anticipated documents selected via 'Select for Automatic Reconciliation' are being displayed directly when session
'Selection for Automatic Reconciliation' comes up.
SPECIAL INSTRUCTIONS:
None.

Solution: 134893
SITUATION IDENTIFIED IN:
"Sales Contracts" (tdsls3100s000)
SITUATION DESCRIPTION:
When de-activating a Sales Contract (tdsls3100m000) the field 'Effective Date' remains disabled. When clicking on another
field, it is enabled.
SOLUTION DESCRIPTION:
When de-activating a Sales Contract (tdsls3100m000) the field 'Effective Date' is enabled.
SPECIAL INSTRUCTIONS:
None.

Solution: 134901
SITUATION IDENTIFIED IN:
"Print Reminder Letters" (tfacr3420m000)
SITUATION DESCRIPTION:
In session "Print Reminder Letter" (tfacr3420m000), the reminder-procedure will use the credit notes for checking the
open-balance for a certain customer. Since the credit note will not get a letter-number it's impossible to calculate a proper
interest-amount.
SOLUTION DESCRIPTION:
The interest amount is calculated only when the letter-number is updated.
SPECIAL INSTRUCTIONS:
None.

Solution: 134907
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
Incomplete posting for advanced receipts generating unbalanced batches, as the field "Amount in invoice
Currency"(tfcmg401.amti) is not filled.
SOLUTION DESCRIPTION:
"Amount in invoice Currency" will get filled correctly and so the Batches will get balanced for Advance Receipts.
SPECIAL INSTRUCTIONS:
None.

Solution: 134915
SITUATION IDENTIFIED IN:
"Purchase Invoice Transactions" (tfacp1110s000)
SITUATION DESCRIPTION:
(1) A credit note with normal tax and the subcontracting flag is not set gets assigned to an original invoice for which the
original invoice has shifted tax and the subcontracting flag is set. (The credit note amount is the same as the invoice
amount.)
(2) After saving a correction is done on the credit note. The normal tax is changed to shifted tax and the subcontracting flag
is set.
(3) Now when confirming the record gives an open amount although this should be zero.
SOLUTION DESCRIPTION:
Assigning and changing invoices to credit notes with or without shifted tax and with or without the subcontracting flag
set does not give any problems anymore.
SPECIAL INSTRUCTIONS:

Solution: 134936
SITUATION IDENTIFIED IN:
"Transfer Purchase Order Advice" (whina3212m000)
SITUATION DESCRIPTION:
An active purchase contract exists for a particular Item - Supplier combination subject to a minimum order quantity per
order.
A purchase advice for the same Item - Supplier combination (but the order quantity is less than the minimum order quantity
specified in the purchase contract, hence the contract cannot be applied) is transferred to Purchase Order. The resulting
order line is linked to the Purchase Contract even though the order quantity does not qualify for the contract to be
applicable.
This does not happen when a purchase order is created manually with the same data.
SOLUTION DESCRIPTION:
If the retrieved purchase price for the Purchase order line has not originated from the linked purchase contract then the
orderline will be disconnected from the contract.
SPECIAL INSTRUCTIONS:
None.

Solution: 134942
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4101s000)
SITUATION DESCRIPTION:
It is possible to insert a Discount Code with "Use in Agreement" marked for a purchase order line that does not meet the
agreement at all.
On the purchase order line you can insert manually a price, manually a discount percentage and then you can enter any
discount code you like in the field Discount Code.
SOLUTION DESCRIPTION:
User is not allowed to enter a discount code marked with use is agreements on a purchase order line when the prices and
discounts are entered manually. In this case, system gives an error message saying, "Discount code must be of type
Discount and should not be used in agreements".
SPECIAL INSTRUCTIONS:
None.

Solution: 134962
SITUATION IDENTIFIED IN:
"Purchase Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
When entering lines and the vat amount of the last line gets modified, not the total of entered tax is the tax amount of
open entry but only the amount of vat of the modified line.
SOLUTION DESCRIPTION:
The tax amount of the open entry is updated correctly now. The total entered vat is taken now.
SPECIAL INSTRUCTIONS:
None.

Solution: 134972
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
SITUATION DESCRIPTION:
When the financial period of the delivery date is closed, the system does not allow receiving the purchase orders by giving
the error
+++++++++++++++++++++++++++++++++++++
Fiscal year 2003 period 3 not open in company XXX"
++++++++++++++++++++++++++++++++++++++
The integration posting created at the time of changing the price after receipt in the session "Change Prices/Discounts
after Receipts" (tdpur4122m000) are also logged with the receipt date of the purchase order line. But, at this time the
system does not check if the period corresponding to the receipt date is already closed or not.
SOLUTION DESCRIPTION:
The following error message pops up at the time of changing the price after receipt in the session "Change
Prices/Discounts after Receipts" (tdpur4122m000).
+++++++++++++++++++++++++++++++++++++
Fiscal year 2003 period 3 not open in company XXX"
++++++++++++++++++++++++++++++++++++++
SPECIAL INSTRUCTIONS:
None.

Solution: 134976
SITUATION IDENTIFIED IN:
"Standing Orders" (tfcmg1110s000)
SITUATION DESCRIPTION:
When changing the rate determinator to 'Manual Entered' in session 'Standing Orders' (tfcmg1110s000) and also the rate
is changed, the rate changes back to the previous value when saving the record.
SOLUTION DESCRIPTION:
In session 'Standing Orders' the manually entered rates are saved properly when the rate determintor is 'Manual Entered'.
In case a currency is entered for which no rates exists, message 'No Currency Rate is defined between and
'
SPECIAL INSTRUCTIONS:
None

Solution: 134982
SITUATION IDENTIFIED IN:
"Purchase order header" (tdpur4100s000)
SITUATION DESCRIPTION:
'Pay to BP' on order header can not maintained since it is disabled.
SOLUTION DESCRIPTION:
'Pay to BP' on order header level is available to be maintained.
SPECIAL INSTRUCTIONS:
None.

Solution: 134992
SITUATION IDENTIFIED IN:
"Write off Payment Difference" (tfacp2230m000)
SITUATION DESCRIPTION:
When the session "Write off Payment Differences" (tfacp2230m000) was run, if there was a payment difference the
balance amount of the invoice was updated but not the balance in home currency of the invoice.
SOLUTION DESCRIPTION:
After running the session "Write off Payment Differences", it updates the balance correctly of the invoice.
SPECIAL INSTRUCTIONS:
None.

Solution: 135010
SITUATION IDENTIFIED IN:
"Purge Sales Invoice Data" (cisli3210m000)
SITUATION DESCRIPTION:
Eventhough only project invoice is selected for purging, the system gives a fatal error 205 (Out of Range) for service order
lines table.
SOLUTION DESCRIPTION:
Now the fatal error does not arise.
SPECIAL INSTRUCTIONS:
None.

Solution: 135014
SITUATION IDENTIFIED IN:
"Planned Inventory Transactions" (whinp1500m000)
SITUATION DESCRIPTION:
When the inventory handling parameter "Correct SFC Production Order till" is set to "Generate Outbound Advice" or
"Release Outbound Advice" the following two problems are experienced:
A redundant inbound line and wrong planned inventory transactions remain in the Warehousing module after processing a
negative material issue in production.
SOLUTION DESCRIPTION:
When the inventory handling parameter "Correct SFC Production Order till" is set to "Generate Outbound Advice" or
"Release Outbound Advice" and processing a negative material issue in the Baan Production module the outbound and
inbound lines are updated correctly. Furthermore the planned inventory transactions are updated accordingly.
SPECIAL INSTRUCTIONS:
For B50_c please download solution 134570.

Solution: 135019
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When changing the currency of a purchase invoice, the newly stored currency does not get saved correctly in the
documents table (tfgld018).
SOLUTION DESCRIPTION:
When changing the currency of a purchase invoice, the newly stored currency is correctly saved in the documents table
(tfgld018).
SPECIAL INSTRUCTIONS:
None.

Solution: 135021
SITUATION IDENTIFIED IN:
"Purchase-Invoice Corrections" (tfacp2110s000)
SITUATION DESCRIPTION:
1. In session "Purchase-Invoice Corrections" (tfacp2110s000), if the tax code is changed from singular tax code to a
multiple tax code, then the tax line amounts are not calculated correctly.
2. Also in the session, when only the business partner is changed in the purchase invoice, then no tax transactions are
created, hence the information in session "Tax Analysis" (tfgld1520m000) is wrong.
SOLUTION DESCRIPTION:
1. The tax line amounts are calculated correctly.
2. Tax transactions are created when the business partner is changed.
SPECIAL INSTRUCTIONS:
None.

Solution: 135031
SITUATION IDENTIFIED IN:
"Print Sales Invoices" (tfacr2421m000)
SITUATION DESCRIPTION:
For invoices which are created long back (overdue days greater than 999), hashes(#) are printed on the report for the
column overdue days
SOLUTION DESCRIPTION:
For the invoices created long back are printed correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 135033
SITUATION IDENTIFIED IN:
"Write off payment difference" (tfacr2240m000)
SITUATION DESCRIPTION:
Wrong warning message when invoice period compared with fiscal period.
SOLUTION DESCRIPTION:
Correct warning message displayed when invoice period compared with fiscal period.
SPECIAL INSTRUCTIONS:
None.

Solution: 135035
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
1. When entering an item which does not have enough inventory, the Stock Shortage Menu appears after the ordered
quantity is entered. When choosing option 'Alternative Items' and choosing an item which also does not have enough
inventory, the Shortage Menu does not appear again.
2. When splitting a Sales Order Detail by using the 'Split'-button, a fatal error occurs (only B50_b and B50_c)
SOLUTION DESCRIPTION:
1. When the Alternative Item also does not have enough inventory, the Shortage Menu appears again.
2. A Sales Order Detail can be split without fatal errors.
SPECIAL INSTRUCTIONS:
None.

Solution: 135037
SITUATION IDENTIFIED IN:
"Process Quotations" (tdsls1200m000)
SITUATION DESCRIPTION:
Sales orders are not being created when sales quotations are processed. This occurs when the calendar doesn't have null
availability type.
SOLUTION DESCRIPTION:
The release date is zero when the calender doesn't have null availability type. Therefore, the release date will be equal to
the order date. This is to allow the sales order to be created since sales orders cannot be inserted with an empty release
date.
SPECIAL INSTRUCTIONS:
None.

Solution: 135048
SITUATION IDENTIFIED IN:
"Print Forecast Components by Date/Currency " (tfcmg3420m000)
SITUATION DESCRIPTION:
A budget created for a credit Balance Sheet account is printed under the Inflow Budget in the session "Print Forecast
Components by Date/Currency (tfcmg3420m000)". This should be the opposite. For a credit ledger account and a budget
defined for the credit site the budget should be printed under Outflow Budget.
SOLUTION DESCRIPTION:
A budget created for a balance sheet account, which is defined on credit site of the budget, will be printed under the
Outflow Budget in the session "Print Forecast Components by Date/Currency (tfcmg3420m000)".
SPECIAL INSTRUCTIONS:
None.

Solution: 135054
SITUATION IDENTIFIED IN:
"Perform Inventory Valuation by Warehouse and Item" (whina1210m000)
SITUATION DESCRIPTION:
A range of warehouses can be entered. The check on this range however was carried out with the 'to' warehouse only
instead of with the 'from' and the 'to' warehouse.
SOLUTION DESCRIPTION:
The range check is changed so that the proper warehouses are taken into account.
SPECIAL INSTRUCTIONS:
None.

Solution: 135056
SITUATION IDENTIFIED IN:
"Manual Sales Header" (cisli2520m000)
SITUATION DESCRIPTION:
Only the first invoice gets printed when several manual sales headers are selected for direct processing. The rest of the
invoice gets printed only if the session "Manual Sales Header" (cisli2520m000) is closed.
And also when a range of headers are selected for direct processing, the system tries to process right from the first manual
sales header instead of the first selected header.
SOLUTION DESCRIPTION:
Now all the invoices are printed correctly.
Also only the selected range of headers are processed.
SPECIAL INSTRUCTIONS:
None.

Solution: 135068
SITUATION IDENTIFIED IN:
"Change Prices/Discounts after Receipts" (tdpur4122m000)
"Commitments (Materials)" (tpppc2110s000)
SITUATION DESCRIPTION:
1. If the price of a purchase order linked to project is changed after receiving the item, then the 'Registration Date' in
project commitment is updated with 'Current Date'. Instead it should be 'Receipt Date' of the order.
2. Similarly, the 'Registration Date' in case of 'Order' commitment line should be 'Order Date' instead of 'Planned Delivery
Date'.
This will then be consistent with the normal purchase order with respect to finance entries.
SOLUTION DESCRIPTION:
. For a price change after the receipt of goods, the 'Registration Date' in 'Projects' commitment line will be the 'Receipt
Date'.
In case the price is changed where there have been partial receipts, the 'Registration Date' for the commitment line will be
the corresponding 'Receipt Date'.
2. The 'Registration Date' in case of 'Order' commitment line (i.e. the Soft Commitment line) will be 'Order Date' instead
of 'Planned Delivery Date'.
SPECIAL INSTRUCTIONS:
None.

Solution: 135069
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When running session "Register Purchase Invoices" ( tfacp1110s000) the transaction is unbalanced due to tax amount
modification when a group tax code is used.
SOLUTION DESCRIPTION:
Because of disabling the Tax amount field in case of a group tax code the transaction will stay balanced.
SPECIAL INSTRUCTIONS:
None.

Solution: 135076
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When using shifted VAT the base value of VAT is the invoice amount minus VAT. This should be the invoice amount
only.
SOLUTION DESCRIPTION:
When using shifted VAT the base value of VAT is the invoice amount.
The solution is only applicable for the localization in B50b and B50c
SPECIAL INSTRUCTIONS:
None.

Solution: 135110
SITUATION IDENTIFIED IN:
"Close Production orders" (ticst0201m000)
SITUATION DESCRIPTION:
It is possible to close the production order even before the purchase invoice is approved for the sub-contracting purchase
orders corresponding to the production order.
SOLUTION DESCRIPTION:
The production order is now prevented from being closed when the invoice of the corresponding purchase order is not
approved in finance.
SPECIAL INSTRUCTIONS:
None.

Solution: 135135
SITUATION IDENTIFIED IN:
"tdpur4101s000" (Purchase Order Lines)
SITUATION DESCRIPTION:
When the Purchase Order lines are already maintained and if the same Purchase Order is reached from the Purchase Order
header session by pressing "Order Lines" button, the system opens a new single occurrence Purchase Order lines session,
instead of Purchase Order lines multi occurrence session.
SOLUTION DESCRIPTION:
The problem is solved, when the lines are already maintained and if the same Purchase Order is reached from the
Purchase Order Header session by pressing "Order Lines" button, then the system will open the multi occurrence Purchase
Order Lines session. If a new Purchase Order is maintained and "Order Lines" button is pressed from the header then the
system will automatically open the single occurrence Purchase Order Lines session.
SPECIAL INSTRUCTIONS:
This Solution is Superceded.

Solution: 135153
SITUATION IDENTIFIED IN:
"Cash Management Transaction" (tfcmg2120s000)
SITUATION DESCRIPTION:
When trying to finalize a batch with a Receipt Reconciliation in which sundry costs are included message 'Background
process not completed' is given. Even when running session 'Invoke background process' (tfgld1214m000) the batch cannot
be finalized. Message 'Document balance is not 0' is given within the error log, although the document is balanced.
SOLUTION DESCRIPTION:
Batch used for a Receipt Reconciliation in which sundry costs are included can be finalized succesfully.
SPECIAL INSTRUCTIONS:
None.

Solution: 135154
SITUATION IDENTIFIED IN:
"Checks" (tfcmg1260s000)
"Print Forwarding Notes" (tdsls4421m000)
SITUATION DESCRIPTION:
Two main sessions exist that display amounts in words:
1. In the sub session 'Transfer Payments' (tfcmg1260m000) payments can get transferred to a check. On these checks the
amount is presented both in digits and in words.
2. In the session "Print Forwarding Notes" (tdsls4421m000) bills of lading can be printed. When "Cash on Delivery" has
been selected as the type of bill of lading the amount to be received is printed in words as well.
Amounts are incorrectly translated to words in Spanish language on check reports.
SOLUTION DESCRIPTION:
Amounts are correctly translated to words in Spanish language on check reports.
SOLUTION 134630 BEFORE INSTALLING THIS SOLUTION ***
VERSION(S):
B40_c, B50_b, B50_c (Spanish language)
SPECIAL INSTRUCTIONS:
*** Please install solution 134630 before installing this solution ***

Solution: 135155
SITUATION IDENTIFIED IN:
-1- "Receipts" (whinh3520m000)
-2- "Import/Export Statistics"(tccom7571m000)
SITUATION DESCRIPTION:
-1- When a sales return order is processed for an item with valuation method "lot price", the amount for "Cost Of Goods
Sold" in session "Release to Invoicing" (tdsls4501m130) is determined as zero. This happens when the return order is not
linked to an original sales order.
-2- Import/export statistics are created when a purchase order line is entered with quantity zero.
SOLUTION DESCRIPTION:
-1- The value of the "Cost Of Goods Sold" is determined properly.
-2- Import/export statistics are only created when goods are received, not when a purchase order line is created.
SPECIAL INSTRUCTIONS:
None.

Solution: 135175
SITUATION IDENTIFIED IN:
"Payment Advice " (tfcmg1120s000)
SITUATION DESCRIPTION:
Error 'Amount exceeds invoice balance' is given when adding a Purchase Credit Note into a payment advice even when the
amount is less than the invoice balance.
SOLUTION DESCRIPTION:
When adding a Purchase Credit Note into a payment advice, error 'Amount exceeds invoice balance' is not given when the
amount is less than the invoice balance.
SPECIAL INSTRUCTIONS:
None.

Solution: 135178
SITUATION IDENTIFIED IN:
"Generate Inventory Commitment" (whinp2200m000)
SITUATION DESCRIPTION:
Though all Inventory Commitments are generated correctly the report does not show all the commitments that are
generated.
SOLUTION DESCRIPTION:
All Inventory Commitments that are generated are now also printed on the report.
SPECIAL INSTRUCTIONS:
None.

Solution: 135240
SITUATION IDENTIFIED IN:
"Purchase Order Lines" (tdpur4501m000)
SITUATION DESCRIPTION:
It is possible to delete a Direct Delivery back order from Purchase side. This causes incorrect updating of Linked Order
line data in Sales and the user is not able to process the delivered Purchase Orders. The direct delivery purchase back
orders are created (triggered) from sales and that means the deletion/cancellation of the back orders should also be
triggered from sales. It should never be possible to delete the back order in purchase with out the knowledge of sales.
SOLUTION DESCRIPTION:
From Purchase side, the back order for a Direct Delivery order cannot be deleted any more.
SPECIAL INSTRUCTIONS:
None.

Solution: 135286
SITUATION IDENTIFIED IN:
"Register Purchase Invoices" (tfacp1110s000)
SITUATION DESCRIPTION:
When inserting a second invoice without leaving the session with a business partner that not belongs to the business
partner structure of the business partner from the previous invoice the message "BP xxx does not belong to the business
partner structure of BP yyy" pops up wrongly because it is a new invoice.
SOLUTION DESCRIPTION:
Because the business partner structure check now is done for each separate invoice the message "BP xxx does not belong to
the business partner structure of BP yyy" will not pop up.
SPECIAL INSTRUCTIONS:
None.

Solution: 135297
SITUATION IDENTIFIED IN:
"Process Delivered Purchase Orders" (tdpur4223m000)
SITUATION DESCRIPTION:
While deleting a Purchase Order line created through Requisition process, system throws Fatal error 605 (Reference
exists).
SOLUTION DESCRIPTION:
The Fatal error no does not appear now and system deletes the purchase order line without any problem.
SPECIAL INSTRUCTIONS:
None.

Solution: 159448
SITUATION IDENTIFIED IN:
"Close Periods" (tfgld1206m000)
SITUATION DESCRIPTION:
If an error is found during the process of period closing then corresponding error message will be given and process will be
stopped. It's impossible to get a full list of errors to fix them at once.
SOLUTION DESCRIPTION:
New mode has been added to satisfy the need to know all errors that prevent period from being closed. In this mode all
errors are printed on the report.
New form field "Print all errors" has been added to switch between modes. If this field is set to "NO" then as soon as an
error is detected the error message will be shown and next period will be processed. If the value of the field "Print all
errors" is "YES" then all errors will be printed on the report. If no errors are found then period will be closed.
Some performance issues have been solved as well.
SPECIAL INSTRUCTIONS:
None.

Solution: 160231
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
In Spanish localization it is possible to work with 'withholding tax' which is a specific kind of tax. Actually, the
commissions invoices are not capable of handling this kind of taxes, as neither the functionality is available, not the
format of the commissions invoice can support this. Therefore, the commission invoices need to be adapted for this.
SOLUTION DESCRIPTION:
When the Localization Parameters 'Multiple Taxes' and 'Generic Taxes' (tccom936.mtax.l and tccom936.gtcd.l) are ON,
then the Group Taxes can be used. According to the group tax code used the withhold tax/Social contribution taxes will be
calculated.
SPECIAL INSTRUCTIONS:
After installing the solution, you must perform the following steps before the solution will work correctly:
1) Run the session 'Convert to Run Time Data Dictionary' (ttadv5210m000) for tables tdcms201 and tdcms203.
2) Run the session 'Create Tables' (ttaad4230m000) for table tdcms203, to physically create the new table in your
database.
3) Download and install solution 161406, which contains a correction program for existing commission/rebate invoices.
4) Run the correction program 'Insert values in tdcms203 (Solution 160231)' (tdcor2203m000).

Solution: 160345
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
When printing commission invoices for multiple orders and the same relation in a multi-finance environment, commissions
for different finance companies are being grouped together, rather than printing separately.
SOLUTION DESCRIPTION:
In a multi-finance environment, the sales office is used to determine to which finance company the invoices will be
posted. However, the session was only grouping commissions together by relation, ignoring the different sales offices of
the commissions.
The session has been modified to group the commissions by relation and then by sales office as well, so that commissions
for different finance companies will no longer be printed together on one invoice.
SPECIAL INSTRUCTIONS:
None.

Solution: 160387
SITUATION IDENTIFIED IN:
"Termination Process (actual)" (tfgld1212s000)
SITUATION DESCRIPTION:
When issuing a partial payment for an invoice with a vat on payment tax code, the net amounts were not written correctly
to the tax analysis table (tfgld110). These amounts were being filled with the total of the invoice and should have been
filled with the amount of the partial payment being issued. This problem does not occur in B50.
When a foreign currency invoice with a vat on payment tax code is entered at one rate, and the rate changes and the
currency difference is written off, the amount of the tax entry generated at the time of payment was written incorrectly
in the tax analysis table (tfgld110). The tax amount was being calculated based on the new currency rate. Since general
ledger accounts used for tax are not defined to recognize currency differences, the amount should be calculated based on
the rate at the time of the invoice. This problem is occurring in both B40 and B50.
SOLUTION DESCRIPTION:
In B40 a correction has been made so that when partial payments are made, the amount filled in the tax analysis table
(tfgld110) will be the partial payment amount.
In B40 and B50 corrections have been made so that when paying invoices where a currency difference has occurred and a vat
on payment tax code is used, the interim tax clearing transactions will be calculated based on the original invoice currency
rate.
SPECIAL INSTRUCTIONS:
None.

Solution: 160412
SITUATION IDENTIFIED IN:
"cisli2200m000" (Compose/Print/Post Invoices)
SITUATION DESCRIPTION:
Transactions from Central Invoicing are posted to manually created batch when manual batch and Central Invoicing batch
are being created at the same time. The reason behind this problem lies in the handling of the simultaneous update of
the table "Maintain Last Used Batch Number" (tfgld014) by the sessions "Maintain Transactions"(tfgld1101m000) and
"Compose/Print/Post Invoices" (cisli2200m000). Both sessions use the same batch number.
SOLUTION DESCRIPTION:
The handling of the update of the table "Maintain Last Used Batch Number" (tfgld014) by the session
"Compose/Print/Post Invoices" (cisli2200m000) has been changed. If the table is being updated by the session "Maintain
Transactions"(tfgld1101m000) then the session "Compose/Print/Post Invoices" (cisli2200m000) will get the next
available batch number.
SPECIAL INSTRUCTIONS:
None.

Solution: 160414
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Order" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating project structure for sales order for a phantom item, the new structure is not generated if the "check
standard item inventory" flag is set to YES and there is no economic stock for the components.
SOLUTION DESCRIPTION:
Now when generating project structure for sales order for a phantom item, the new structure is generated if the "check
standard item inventory" flag is set to YES and there is no economic stock for the components.
SPECIAL INSTRUCTIONS:
None.

Solution: 160468
SITUATION IDENTIFIED IN:
"Print Finalized Transactions by Ledger Account" (tfgld1406m000)
"Print Finalized Transactions by Ledger Account/Dimensions" (tfgld1407m000)
SITUATION DESCRIPTION:
The sessions Print Finalized Transactions by Ledger Account (tfgld1406m000) and Print Finalized Transactions by Ledger
Account/Dimension (tfgld1407m000) do not have the functionality of printing the reports by Reporting Period. This
functionality exists in Baan 4 but is missing in ERP.
SOLUTION DESCRIPTION:
The above functionality has been added into ERP as well. A new field "Period Type" has been added on the form. The user
can choose to print the above sessions either by "Fiscal Period" or "Reporting Period".
SPECIAL INSTRUCTIONS:
None.

Solution: 160499
SITUATION IDENTIFIED IN:
"Finalization Process" (tfgld1212s000)
SITUATION DESCRIPTION:
When intergroup company transactions are finalized, the source document information is missing in tfgld106.
SOLUTION DESCRIPTION:
Problems in the script were causing inter-group company transactions to be treated as single company transactions. Hence
the required information was not getting filled in.
SPECIAL INSTRUCTIONS:
None.

Solution: 160513
SITUATION IDENTIFIED IN:
"Maintain Transaction Scheme Details" (tfgld0113s000)
SITUATION DESCRIPTION:
When entering a new line to an existing transaction schedule, it is only possible to enter this line at the end of the
schedule.
If the user wanted to add a new line in the middle of an existing schedule they had to delete all the lines they wanted after
the new line, insert the new line, and re-enter all the data they just deleted.
SOLUTION DESCRIPTION:
This solution now allows the user to change the line number when entering a transaction schedule. Thus they can leave
open line numbers within the schedule which can then be used to add more details at a later date without having to delete
and re-enter data.
SPECIAL INSTRUCTIONS:
None.

Solution: 160534
SITUATION IDENTIFIED IN:
"Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
When entering a multiple line journal voucher, it was not possible to create documents for complementary accounts.
SOLUTION DESCRIPTION:
Functionality has been added so that it is now possible to create journal vouchers to complementary accounts. The fields
for 'currency base' and 'dual accounting scheme' are now input fields when entering the document header.
SPECIAL INSTRUCTIONS:
None.

Solution: 160555
SITUATION IDENTIFIED IN:
"Calculate Currency Differences" (tfgld5201m000)
SITUATION DESCRIPTION:
When Calculate Currency Differences (tfgld5201m000) transactions are created, the history code description
(tfgld102.desc.l) is not written into the tfgld102 table.
SOLUTION DESCRIPTION:
The reason the description was blank was because the form field Standard History Code Description (tfgld102.desc.l) was
getting reset by the db.set.to.default() function in the script when the tfgld102 table is written.
If the user changed the description on the form that was also being reset by the check.all.input() call in the program script.
Changes have been made to ensure that
a) The description is filled into Standard History Code Description (tfgld102.desc.l)
b) If the user changes the history code description on the form then the new description is written into Standard History
Code Description (tfgld102.desc.l), instead of the original std history code description.
SPECIAL INSTRUCTIONS:
None.

Solution: 160696
SITUATION IDENTIFIED IN:
"Finalized Transactions" (tfgld3509m000)
"Non-Finalized Transactions" (tfgld3508m000)
SITUATION DESCRIPTION:
When paging up and down in session tfgld3508m000 (Non-Finalized Transactions) or within tfgld3509m000 (Finalized
Transactions) a fatal error can occur on the first tab of these sessions if the user attempts to page pass the last record.
Under these circumstances, these two sessions produce the following fatal errors:
1: process 14 - Fatal error : g.itab index 0 out of dims [1] 13
2: process 14 - Fatal error : Can not continue in tfgld3509m000 in DLL: ottstpstandard () [retry.point]
SOLUTION DESCRIPTION:
This situation has been corrected.
SPECIAL INSTRUCTIONS:
None.

Solution: 160737
SITUATION IDENTIFIED IN:
"Transfer Planned Orders" (cprrp1250s000)
SITUATION DESCRIPTION:
It is possible to transfer planned distribution orders to warehousing even if the item on the planned order line has no cost
price.
SOLUTION DESCRIPTION:
It is not possible anymore to transfer planned distribution orders to warehousing, if the item on the planned order line has
no cost price.
SPECIAL INSTRUCTIONS:
None.

Solution: 160740
SITUATION IDENTIFIED IN:
"Archive Warehousing Order History" (whinh2255m000)
SITUATION DESCRIPTION:
When the session "Archive Warehouse Order History (whinh2255m000)" processes a large number of records, the session
stops with the error "Snapshot too old" [Error Code: 1555].
SOLUTION DESCRIPTION:
Now, even when the session "Archive Warehouse Order History (whinh2255m000) processes a large number of records, the
session doesn't stop with the error "Snapshot too old".
Technical information about the solution: Every 30 minutes, the open queries are closed and started again. Hence, the
rollback segments are cleared and the data are read again.
SPECIAL INSTRUCTIONS:
None.

Solution: 160782
SITUATION IDENTIFIED IN:
"Rebuild Planned Inventory Transaction" (whinp1200m000)
SITUATION DESCRIPTION:
If the session "Rebuild Planned Inventory Transaction (whinp1200m000)" is run in job mode, the allocation for the sales
quotation is removed if the success percentage of the sales quotation is not equal to 100%. This problem doesn't occur if
the session is run manually.
SOLUTION DESCRIPTION:
Now, if the session "Rebuild Planned Inventory Transaction (whinp1200m000)" is run either manually or through job mode,
the allocation for the sales quotation is rebuilt, provided the success percentage in the sales quotation is greater than
the minimum success percentage mentioned in the sales quotation parameter.
SPECIAL INSTRUCTIONS:
None.

Solution: 160800
SITUATION IDENTIFIED IN:
"Maintain Journal Vouchers (Multiple lines)" (tfgld1115s000)
SITUATION DESCRIPTION:
In Baan version 4c, session tfgld1103m000 (Maintain Journal Vouchers) or tfgld1115s000 (Maintain Journal Vouchers -
Multiple lines) no warning message is given when Recurring / Reversing Instructions have not been entered. In versions 5c
and 5b the error message is reported, regardless of whether or not the instructions were entered.
SOLUTION DESCRIPTION:
In versions 5b and 5c the message has been changed from "Have you "Recurring/Reversing Instructions not created -
Continue?" to "Recurring/Reversing Instructions not created - Continue?". Further the message is only displayed if the
instructions were not entered vs. always being displayed on the session's exit. In 4c the latter functionality was completely
back ported.
SPECIAL INSTRUCTIONS:
None.

Solution: 160813
SITUATION IDENTIFIED IN:
"Generate Budget Structure for Sales Quotations" (tdsls1201m000)
SITUATION DESCRIPTION:
When generating a budget structure for a sales quotation, there is no input option "Include Cost Item". The same
functionality of "Including Cost Items" that exists for sales needs to be added to the generation of budget structures.
When generating a project structure for a sales order, the existing input option "Include Cost / Service Items" is
incorrect. The option should only be applicable for cost items and not service items. The input option should show
"Include Cost Item".
SOLUTION DESCRIPTION:
Now when generating a budget structure for a sales quotation, the input option of "Include Cost Item" is available.
Now when generating a project structure for a sales order, the input option of "Include Cost Item" is now shown.
SPECIAL INSTRUCTIONS:
None.

Solution: 160826
SITUATION IDENTIFIED IN:
"Print Warehousing Parameters" (whwmd0400m000)
SITUATION DESCRIPTION:
In the report, the inventory handling (INH) parameters 'Correct SFC Production Order till' and 'Over Delivery' are not
printed.
SOLUTION DESCRIPTION:
Now, in the report, the inventory handling (INH) parameters 'Correct SFC Production Order till' and 'Over Delivery' are
printed.
SPECIAL INSTRUCTIONS:
None.

Solution: 160911
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
When calculating and invoicing commissions/rebates, the exchange rate type from the CMS Parameters should be used, if
one has been defined there. It is currently using the exchange rate type from the sales order.
SOLUTION DESCRIPTION:
The programs have been modified to use the exchange rate type from CMS parameters for commissions/rebates whenever one is
defined in the parameters session. If it is not defined, the programs use the default exchange rate type as it has in the past.
SPECIAL INSTRUCTIONS:
None.

Solution: 160937
SITUATION IDENTIFIED IN:
"Print Trial Balance - Dimensions" (tfgld3405m000)
SITUATION DESCRIPTION:
1. Trial Balance reports could not be printed for all companies within the group.
2. Reports don't have enough space for amounts and total amounts. Amounts are shown as ############## instead of
real numbers.
SOLUTION DESCRIPTION:
1. New option "All companies of group" that is enabled only for multicompanies has been introduced. If this new option is
selected then report will be printed for all companies within the group. In case of dependent currency system selection
of the option "All companies of group" disables the currency rotation because companies may have different currencies
except for the reference currency.
2. Format of the report fields has been expanded to allow printing of more characters and to show amounts according to
the selected currency format. The reports now have the maximum possible size for the amount fields. Anything more than
this will have to be customized by adjusting the formats and report fields.
SPECIAL INSTRUCTIONS:
None.

Solution: 160963
SITUATION IDENTIFIED IN:
"Purchase Order Creation DLL" (tdpurdll1234) B40c, B50b, B50c
"Purchase Order Header/Lines" (tdpur4101 & tdpur4102) B40c
SITUATION DESCRIPTION:
When e-procurement sends a purchase order request to Baan, with a purchase unit that is different from the purchase unit of
the item in Baan, the newly created purchase order's quantity is incorrectly multiplied by the conversion factor between the
two different units.
SOLUTION DESCRIPTION:
Now when e-procurement sends a purchase order request to the Baan, with a purchase unit that is different from the
purchase unit of the item in Baan, the newly created purchase order's quantity is not changed.
SPECIAL INSTRUCTIONS:
None.

Solution: 160964
SITUATION IDENTIFIED IN:
"Sales Order Lines" (tdsls4101s000)
SITUATION DESCRIPTION:
Even with all proper parameters set, it is not possible for commissions to calculate automatically or interactively. One
must manually calculate commissions later.
SOLUTION DESCRIPTION:
Automatic and Interactive commission calculation is now correctly executed from within "Sales Order Lines".
SPECIAL INSTRUCTIONS:
None.

Solution: 160975
SITUATION IDENTIFIED IN:
"Maintain Purchase Invoice Transactions" (tfacp1120s000)
SITUATION DESCRIPTION:
If "Dimension Ranges by Ledger Account" (tfgld0509m000) were empty for a ledger account, the session would accept
any dimension for that ledger account.
SOLUTION DESCRIPTION:
An error message is now given when the user put a dimension on a ledger account, which has no valid dimension range.
SPECIAL INSTRUCTIONS:
None.

Solution: 160980
SITUATION IDENTIFIED IN:
"Easy Warehousing Order Entry" (whinh2202m000)
SITUATION DESCRIPTION:
It is not possible to process multiple easy transfer warehousing orders simultaneously. When the second easy transfer
warehousing order (which normally gets processed quickly) is started immediately after the first easy transfer warehousing
order (which involves multiple lots and normally takes a longer time), the system waits for the first order to get
completed before the second order gets processed.
SOLUTION DESCRIPTION:
Now, it is possible to process multiple easy transfer warehousing orders simultaneously.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 160988
SITUATION IDENTIFIED IN:
"Imported Journals" (tfgld2513m000)
SITUATION DESCRIPTION:
The session tfgld2215m000 (Import Journal Voucher Batches by ID Number) is not updating the import batch header
information after importing. This causes the display session tfgld2513m000 (Imported Journals) to not display the
username and batch number used/created during the import process.
SOLUTION DESCRIPTION:
The session tfgld2215m000 (Import Journal Voucher Batches by ID Number) has been corrected to update the username
and batch number per successful import.
SPECIAL INSTRUCTIONS:
None.

Solution: 161025
SITUATION IDENTIFIED IN:
"Print Journal Report - Belgium" (tfgld1442m000) in version B52_a
(tfgldl420m00l) in versions B50_b and B50_c
SITUATION DESCRIPTION:
The report 'Centralization By GL Account Group' does not fulfill legal reporting requirements.
SOLUTION DESCRIPTION:
The report has been modified so that instead of sorting, displaying, and totaling by transaction type, the report will
now work with transaction category. Also changes have been made in the program to improve performance when printing
the report 'Centralization By GL Account' or the report 'Centralization By GL Account Group'.
SPECIAL INSTRUCTIONS:
None.

Solution: 161029
SITUATION IDENTIFIED IN:
"Print General Ledger" (tfgldl423m000)
SITUATION DESCRIPTION:
When running the session with "Print only affected accounts" set to "Yes" the session is slow.
SOLUTION DESCRIPTION:
The selection of data has been made more efficient. This will speed up the session.
SPECIAL INSTRUCTIONS:
None.

Solution: 161036
SITUATION IDENTIFIED IN:
"Journal Vouchers" (tfgld1103s000)
"Journal Voucher (Multi-Line)" (tfgld1115m000)
SITUATION DESCRIPTION:
When re-entering a Journal Voucher batch, if any other non-finalized batch exists with the same number and document
type (from other years) then that document becomes visible for update in the current batch.
SOLUTION DESCRIPTION:
The selection of documents to be displayed was not checking whether the year on the batch was the same as the current
batch. Thus documents in batches from previous years which were still un-finalized got displayed in the current batch.
This has been corrected.
SPECIAL INSTRUCTIONS:
None.

Solution: 161045
SITUATION IDENTIFIED IN:
"Tax analysis" (tfgld1520m000)
SITUATION DESCRIPTION:
When user switches the finance company in the session and balances are shown in the currency which is home currency
in the current finance company but not in the switched finance company, the system generates error message "No home
currencies are defined for company xxx".
SOLUTION DESCRIPTION:
Now if currency on the form is not one of the home currencies of the new company, then balances will be shown in local
currency (home currency 1) of the new company.
SPECIAL INSTRUCTIONS:
None.

Solution: 161130
SITUATION IDENTIFIED IN:
"Material Issue for Production Orders" and "Report Orders Completed" (ticst0101s000 and tisfc0120s000)
SITUATION DESCRIPTION:
When issuing material for a rework production order, the lot size is decreased. The lot size of the issued lot is
subsequently increased when the rework production order is reported completed.
SOLUTION DESCRIPTION:
The lot size is not decreased when issuing to a rework production order. If the same lot is received into inventory
following the completion of the rework production order, the lot size is not increased.
SPECIAL INSTRUCTIONS:
None.

Solution: 161188
SITUATION IDENTIFIED IN:
"Companies" (tccom0100s000)
"Item Segmentation" (tcibd0100s000)
SITUATION DESCRIPTION:
New/Customized sessions were not found when a session checked for the existence of other sessions using the tools
function tt.session.present().
SOLUTION DESCRIPTION:
The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of
new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function
are now recompiled and delivered by this solution.
SPECIAL INSTRUCTIONS:
None.

Solution: 161189
SITUATION IDENTIFIED IN:
"Activities by Order Type" (tdpur0560m000)
"Activities by Order Type" (tdsls0560m000)
"Sales Order Types" (tdsls0194s000)
SITUATION DESCRIPTION:
New/Customized sessions were not found when a session checked for the existence of other sessions using the tools
function tt.session.present().
SOLUTION DESCRIPTION:
The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of
new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function
are now recompiled and delivered by this solution.
SPECIAL INSTRUCTIONS:
None.

Solution: 161190
SITUATION IDENTIFIED IN:
"Transaction Types" (tfgld0111s000)
"Payment Receipt Methods" (tfcmg0140s000)
"Audit Payments" (tfcmg1255m000)
"Create Payment Orders" (tfcmg1256m000)
"Audit Direct Debits" (tfcmg4255m000)
"Create Direct Debit Orders" (tfcmg4256m000)
SITUATION DESCRIPTION:
New/Customized sessions were not found when a session checked for the existence of other sessions using the tools
function tt.session.present().
SOLUTION DESCRIPTION:
The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of
new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function
are now recompiled and delivered by this solution.
SPECIAL INSTRUCTIONS:
None.

Solution: 161192
SITUATION IDENTIFIED IN:
"Activities by Procedure" (whinh0106m000)
"Master Data Parameters" (whinh0100s000)
SITUATION DESCRIPTION:
New/Customized sessions were not found when a session checked for the existence of other sessions using the tools
function tt.session.present().
SOLUTION DESCRIPTION:
The tools function tt.session.present() has been modified by solution 114812 to be able to verify the existence of
new/customized sessions. To make this fix in tools active, the objects from the application that make use of this function
are now recompiled and delivered by this solution.
SPECIAL INSTRUCTIONS:
None.

Solution: 161213
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
1. If multiple taxes are on the report then total net amounts by company and by country will include net amounts only from the
first tax lines of the multiple taxes. But if report is to be printed only for the tax authority that is linked to the tax of the
second line then total net amount will be zero because first line tax is not printed.
2. Total tax amount by tax authority group is printed after each change of the tax authority, but not after change of the tax
authority group.
3. When form fields "Tax authority group from" and "Tax authority group to" are not blank then records without any tax
authority group will be printed as well.
4. Some net amounts are printed with a star while they should not.
SOLUTION DESCRIPTION:
1. Total net amounts include net amount from the first PRINTED tax line of the multiple tax.
2. Report layouts have been adjusted.
3. Empty tax authority groups are checked.
4. Star is printed only for the net amounts that are not included in the totals.
SPECIAL INSTRUCTIONS:
None.

Solution: 161270
SITUATION IDENTIFIED IN:
"Period Status" (tfgld0107m000)
SITUATION DESCRIPTION:
During the process of closing a fiscal period for GLD module program checks whether depreciation has been calculated for
this period. Since depreciation cannot be calculated for the future periods these periods cannot be closed. Such
functionality restricts users from having only one open period at a time.
SOLUTION DESCRIPTION:
Now depreciation will be checked only in case of final close of a period or in case of close of a year.
SPECIAL INSTRUCTIONS:
None.

Solution: 161271
SITUATION IDENTIFIED IN:
"Print Non-Finalized Transactions" (tfgld1401m000)
SITUATION DESCRIPTION:
The defaulting of currency is not done correctly in a dependent currency system. The session defaults are company 000 to
999 and the screen currency = reference currency. When the user changes the company range to print only the current
company the currency default does not change from reference currency to local currency as it should.
When running the session in a job the report is always printed in the local home currency instead of the currency specified
when creating the job.
SOLUTION DESCRIPTION:
Changes have been made in the program so that when running in a dependent currency system for only the current company
the local home currency is defaulted instead of the reference currency.
Now the report will print in the user specified currency when running the session in a job.
SPECIAL INSTRUCTIONS:
None.

Solution: 161281
SITUATION IDENTIFIED IN:
"Print Tax Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
In the US there are two kinds of taxes that need to be tracked by business. 1099 taxes that have to work with calendar
years and the regular purchase/sales tax which can use any calendar (e.g. company calendar). When a business has to
support both these they have to use the tax calendar for one purpose say 1099 and the use the fiscal calendar for the
purchase/sales tax because we do not have two tax calendars.
In case of summary report the session "Print Tax Analysis" (tfgld1420m000) prints one line per tax country, code,
tax/fiscal period and the amount details. When running this report over multiple periods there is no way to know what the
total for the tax code for the entered range of periods is. Thus option of printing totals by tax codes should be available
for the summary reports.
SOLUTION DESCRIPTION:
Required option "Print Totals by tax Code" has been added. This option is enabled for the summary reports only. If "Print
Totals by tax Code" is selected then totals for purchase and sales will be printed for each tax code.
SPECIAL INSTRUCTIONS:
Please refer to solution 123462 for installation instructions of the changed online help.

Solution: 161288
SITUATION IDENTIFIED IN:
"Confirm Shipments/Loads" (whinh4275m000)
SITUATION DESCRIPTION:
When running the Confirm Shipments/Loads session (whinh4275m000), the system locks up. This only occurs when using
CMS with automatic commission calculation and when we are short shipping a sales order line that has commission
relations linked to it.
SOLUTION DESCRIPTION:
When you short ship a sales order, it causes a backorder. If you have the parameter "Confirm backorders automatically"
checked in Sales-Order Parameters (tdsls0100s400), the backorder is automatically confirmed at the time of confirming the
shipment. When the backorder is confirmed, a new sales order line detail is added to the sales order line for the
backorder amount. If you are using commissions, this will also link default commissions to the new order line detail
and, if automatic commission calculation is set up in Commissions/Rebates Parameters (tdcms0100s000), the commission
calculation will also be done in the background at this time.
There was a problem with how the commission calculation was being executed that would cause the system to sometimes
hang. This procedure has been modified to eliminate the problem, so the system will no longer hang.
SPECIAL INSTRUCTIONS:
None.

Solution: 161292
SITUATION IDENTIFIED IN:
"Copy Item Data" (tcibd0205m000)
SITUATION DESCRIPTION:
When copying general item data, which has incorrect item supplier information, linked to the purchase item data, the
copy process completes, but does not copy the item supplier information and does not inform the user of the reason why.
SOLUTION DESCRIPTION:
Now during the copying of general item data which has incorrect item supplier information linked to the purchase item
data, the copy process does not copy the item supplier information, aborts the copy process and informs the user of the
reason why.
SPECIAL INSTRUCTIONS:
None.

Solution: 161309
SITUATION IDENTIFIED IN:
"Inbound Advice" (whinh2515m000)
SITUATION DESCRIPTION:
It is impossible to put away an inbound advice if the unit on the inbound advice is different from the unit in which the
goods are received.
The problem occurs in case the inventory unit of the item is not the smallest physical unit.
Example:
-Item "A"
-Inventory unit = "box"
-1 "box" = 10 "pcs".
When 9 "box" are received it is possible to create a manual inbound advice for 90 "pcs".
When trying to put away the advice the message whinhs0277 "Corrupt inventory detected in Whs xxx, Location xxx, Item
xxx, Lot xxx, Inv. Date xxx" appears.
SOLUTION DESCRIPTION:
It is no longer possible to change the unit for an inbound advice if the receipt is done in inventory units. Hence the
situation cannot occur anymore.
SPECIAL INSTRUCTIONS:
None.

Solution: 161311
SITUATION IDENTIFIED IN:
"Print Company Parameters" (tfgld0404m000)
"Display Company Parameters" (tfgld0503m000) (B40_c only)
SITUATION DESCRIPTION:
Solution 106818 has introduced a new field to the company parameters table. The corresponding print/display sessions do
not report this information.
(B40_c only) Several address fields do not display correctly on the print company parameters report. The address for the
history or group company was displayed instead of the current company.
(B40L_MCR only) Solution 156143 introduced new fields for complementary rounding difference account and dimensions.
These fields are not shown on the 'print company parameters' report.
SOLUTION DESCRIPTION:
- Changes have been made to the report and display sessions to now include the missing fields from the company parameters
as well as the field descriptions.
- The program script has been modified to populate the missing description fields and to correctly store the address
variables of the current company.
SPECIAL INSTRUCTIONS:
None.

Solution: 161337
SITUATION IDENTIFIED IN:
"Print Tax Analysis (Invoice-to Business Partner)" (tfgld1431m000)
SITUATION DESCRIPTION:
When sales tax returns are filed based on a fiscal year, it is necessary to retrieve tax information based on the fiscal
year/period. Fiscal and Tax periods are not always the same. For example, in the USA, tax periods are defined within
Baan based on a Calendar year (January 1 through Dec 31), but the company's fiscal year may be different (April 1
through March 31).
SOLUTION DESCRIPTION:
The report can now be generated based on a tax year and period range or a fiscal year and period range. A business
partner range has been added to the form, as well.
SPECIAL INSTRUCTIONS:
None.

Solution: 161349
SITUATION IDENTIFIED IN:
"Automatic Balancing of Profit and Loss Accounts" (tfgld6202m000)
SITUATION DESCRIPTION:
After running this session the batch created cannot be finalized.
SOLUTION DESCRIPTION:
This problem happened because the line which inserted a record in the documents table (tfgld018) had gone missing. Without
this record it is not possible to finalize batches. This has been corrected.
SPECIAL INSTRUCTIONS:
None.

Solution: 161354
SITUATION IDENTIFIED IN:
"Print Packing Slip" (whinh4475)
SITUATION DESCRIPTION:
The packing slip report prints lines for which the shipped quantity of normal item is zero.
SOLUTION DESCRIPTION:
The packing slip report now only prints the lines for which the shipped quantity of normal item is non-zero. For cost and
service items, the printing of zero shipped lines is still applicable.
SPECIAL INSTRUCTIONS:
None.

Solution: 161396
SITUATION IDENTIFIED IN:
"Integration Transactions by Project/Order" (tfgld4510m000)
SITUATION DESCRIPTION:
In a multi logistic environment, ledger account for the default project cannot be found or a wrong ledger account could
be selected. This problem happens because default projects are looked up in the finance company instead of the logistic
company.
SOLUTION DESCRIPTION:
Now default project is searched in the logistic company.
SPECIAL INSTRUCTIONS:
None.

Solution: 161406
SITUATION IDENTIFIED IN:
"Print Commission/Rebate Invoices" (tdcms2402m000)
SITUATION DESCRIPTION:
After installing solution 160231, it is also necessary to correct data for invoices that have already been printed but not
processed.
SOLUTION DESCRIPTION:
A correction program (tdcor2203m000) has been created to correct the data for previously printed invoices.
SPECIAL INSTRUCTIONS:
After installing this solution, you must run the session Create Runtime Data Dictionary (ttadv5210m000) before trying to
run the correction program.
When you run the create runtime data dictionary session, enter the full range of package combinations in the to and from
fields. In the selection fields for package, enter 'td' for both the to and from fields. In the selection fields for session,
enter 'cor2203m000' in both the to and from fields. After these fields are entered, press the 'Create Runtime' button to
create the runtime data dictionary enteries for the new correction program session.
Once you have completed this, you can run the correction program with the following steps:
1) Select the 'Run Progam' option under the File menu.
2) Enter 'tdcor2203m000' in the Program/Session field.
3) Press the OK button.

Solution: 161411
SITUATION IDENTIFIED IN:
"Create Transactions from Schedule" (tfgld1204s000)
SITUATION DESCRIPTION:
This solution addresses two issues.
1. When creating transactions with gross tax and multiple debit lines, the last debit line had an incorrect amount. This was
due to the tax amount not being considered as part of the total transaction amount. The same problem existed for credit
lines, as well.
2. The document status for the document created within the session would be "used" even when no transactions are
created.
SOLUTION DESCRIPTION:
1. The tax amount is now considered as part of the total transaction amount.
2. A check is introduced to make sure transactions will be created prior to creating the document.
SPECIAL INSTRUCTIONS:
None.

Solution: 161423
SITUATION IDENTIFIED IN:
"Print Trial Balance" (tfgld3402m000)
"Print Trial Balance- Currency" (tfgld3403m000)
"Print Trial Balance Ledger Account/Dimensions" (tfgld3404m000)
"Print Trial Balance- With Dimensions" (tfgld3405m000)
"Print Trial Balance Dimension Code/Ledger Accounts" (tfgld3406m000)
"Print Trial Balance Dimension Type/Dimension Code" (tfgld3408m000)
SITUATION DESCRIPTION:
Several problems have been identified and corrected in the various print trial balance sessions.
tfgld3402m000 "Print Trial Balance"
#1- The session did not print in the correct currency when running from a job.
#2- (B52_a) When running the report for all companies in the group where the group has a dependent currency system,
the amounts were not being added up in the correct currency if the reference currency was not in the same position across
all companies.
#3- It was possible that budget amounts were rounded by the incorrect rounding format. This could cause budget
amounts to have too many or too few decimal places on the report.
#4- (B52_a) Ledger accounts with sublevel greater than 0 would always print 0 as closing balance.
tfgld3403m000 "Print Trial Balance- Currency"
The session did not perform properly if the following conditions are met:
- Dependent multi-company system
- Being run from a job for all companies in the group
- Being run from a company where the local currency is not same as the reference currency
The result was that either wrong amounts are printed on the trial balance (amounts in the local currency and not the
reference currency) or error "index out of dims".
tfgld3404m000 "Print Trial Balance Ledger Account/Dimensions"
#1 The session did not print in the correct currency when running in a job. Report was always in the local currency.
#2 (B52_a) The session did not display the correct budget amounts when the report was selected for a home currency that
was different than the default budget currency (FBS parameter) because of incorrect currency conversions.
#3 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many
or too few decimal places on the report.
#4 Budget amounts were not calculated correctly when budgets were for a credit amount.
#5 Amounts did not total up correctly when printing over all companies in the group.
#6 (B52_a) The variance percentage fields were always 0 on the budget report.
(B50_c) The variance percentage is not correct when printing over all companies in the group.
#7 (B52_a) The session showed incorrect amounts in all columns for the budget report.
tfgld3405m000 "Print Trial Balance- With Dimensions"
#1 The session did not print in the correct currency when running in a job. Report was always in the local currency.
#2 (B52_a) The session did not display the correct budget amounts when the report was selected for a home currency that
was different than the default budget currency (FBS parameter) because of incorrect currency conversions.
#3 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many
or too few decimal places on the report.
tfgld3406m000 "Print Trial Balance Dimension Code/Ledger Accounts"
#1 The session did not print in the correct currency when running in a job. Report was always in the local currency.
#2 (B52_a) The session did not display the correct budget amounts when the report was selected for a home currency that
was different than the default budget currency (FBS parameter) because of incorrect currency conversions.
#3 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many
or too few decimal places on the report.
#4 Amounts did not total up correctly when printing over all companies in the group.
#5 (B52_a) Total by dimension in the budget report was not correct as it contained the amounts of the last printed
record.
tfgld3408m000 "Print Trial Balance Dimension Type/Dimension Code"
#1 The session did not print in the correct currency when running in a job. Report was always in the local currency.
#2 It was possible that budget amounts were rounded in the wrong format. This could cause amounts to have too many
or too few decimal places on the report.
SOLUTION DESCRIPTION:
Changes have been made to the trial balance sessions so that the errors listed above will no longer occur.
SPECIAL INSTRUCTIONS:
None.

Solution: 161460
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
For a return sales order of a lot controlled item, split the receipts into two. While confirming the second receipt, the
system gives the error message "Lot %s: returned quantity may not exceed shipped quantity" (whinhs0358) even though the
returned quantity is less than the shipped quantity.
SOLUTION DESCRIPTION:
Now, for return sales orders, when the returned quantity is less than the shipped quantity, the system doesn't give any
error message.
SPECIAL INSTRUCTIONS:
None.

Solution: 161485
SITUATION IDENTIFIED IN:
"Print VAT Book" (tfgldl408m00l)
SITUATION DESCRIPTION:
1. If there are no transactions associated with Intra EEC VAT book then fatal error (Error 100 (Duplicate value) on
tfgld945XXX (No retry point specified) occurs during final printing of that VAT book. Table tfgld945 (VAT Book History)
is updated while report is printing. Since two reports (Purchases and Sales) are printed for each Intra EEC VAT book then
table tfgld945 will be update twice. At this moment fatal error occurs.
2. If Intra EEC VAT book is being finally printed then deleted transactions are not included on the Sales report.
3. If Intra EEC VAT book is being reprinted then data cannot be found for Purchases report but Sales report is printed.
Also, both reports are reprinted with the same title.
SOLUTION DESCRIPTION:
1. Table tfgld945 is updated just once during final printing of Intra EEC VAT book.
2 and 3. Now both reports (Purchases and Sales) will be printed correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 161538
SITUATION IDENTIFIED IN:
"Post Integration Transactions to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When posting integration transactions, some transactions would generate the error message "Ledger account not defined"
and not be posted even if the ledger account is defined. This problem occurred when table boosters are being used.
SOLUTION DESCRIPTION:
An insufficient amount of memory was being allocated to store the mapping scheme when using table boosters. The
amount of memory available for storing the mapping scheme has been increased to the maximum allowable value so that
transactions can now be posted properly.
SPECIAL INSTRUCTIONS:
None.

Solution: 161561
SITUATION IDENTIFIED IN:
"Process Commission/Rebate" (tdcms2201m000)
SITUATION DESCRIPTION:
When processing commissions/rebates, the current date is passed to finance instead of the invoice date.
SOLUTION DESCRIPTION:
The session has been modified so that the invoice date of the commission/rebate invoice will be sent to finance instead of
the current date.
SPECIAL INSTRUCTIONS:
None.

Solution: 161572
SITUATION IDENTIFIED IN:
"tssoc2121s000" (Actual Material Costs)
SITUATION DESCRIPTION:
Modifying the "To Be Delivered" quantity is not allowed for a service order in the session "Actual Material Costs"
(tssoc2121s000) even though there exists a corresponding "Open" outbound line in warehousing. The system issues the
error message "The order is being processed within warehousing (outbound advice started)".
SOLUTION DESCRIPTION:
It now allowed to modify the "To Be Delivered" quantity for service order in the session "Actual Material Costs"
(tssoc2121s000), provided that there exists a corresponding "Open" outbound line in warehousing. If the quantity is made
zero, then the "Open" outbound line is deleted.
SPECIAL INSTRUCTIONS:
None.

Solution: 161575
SITUATION IDENTIFIED IN:
"Process Commissions/Rebates" (tdcms2201m000)
SITUATION DESCRIPTION:
There is no reference information in finance for rebate integration transactions.
SOLUTION DESCRIPTION:
When processing commissions/rebates, the reference field will now be filled in. It will show whether the transaction is a
commission or a rebate and the relation for which it was paid. This will allow users to look up information in the CMS
module, based on the financial integrations.
SPECIAL INSTRUCTIONS:
None.

Solution: 161589
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Orders" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating project structure for a range of sales orders, and cost items are selected to be added to the project parts,
only the last sales order in the selection range gets updated with the cost items.
SOLUTION DESCRIPTION:
Now when generating project structure for a range of sales orders, and cost items are selected to be added to the project
parts, all the sales order in the selection range gets updated with the cost items.
SPECIAL INSTRUCTIONS:
None.

Solution: 161612
SITUATION IDENTIFIED IN:
"Journal Vouchers (Summarized)" (tfgld1114s000)
SITUATION DESCRIPTION:
It is not possible to access the Baan Project Transaction session through the specific menu on the Journal Vouchers
(Summarized) session.
SOLUTION DESCRIPTION:
The specific options for the session Journal Vouchers (Summarized) (tfgld1114s000) has been modified to include the
same options as those contained in the Journal Voucher (tfgld1103s000).
SPECIAL INSTRUCTIONS:
None.

Solution: 161655
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000 (B40c and above), tfcmgl200m000(B40b and below))
SITUATION DESCRIPTION:
1.) When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC) using the filing option FORM + Electronic
the session unnecessarily collects the payment information twice.
2.) In multi-finance environments, the user must select all the possible companies where a 1099 related invoice,
standing order, or stand alone payment was created within the 'to' and 'from' company range. This company range must
also include companies were the actual payment(s) were processed - possibly in another finance company. This prevents
the session from running for an individual company(s) if invoices and payments were processed in different companies.
3.) The 1099-MISC sessions lacks functionality to collect Stand-alone payments that are 1099-MISC related.
SOLUTION DESCRIPTION:
1.) The payment collection process has been consolidated such that - the payment information is only collected once -
improving performance for the filing option Electronic + Form by 50%.
2.) The 1099 processing has been altered to allow the printing of a single company or a subset of companies, without
having to include in the 'to' and 'from' company range the possible set of companies were the payment may have been
processed.
3.) Added additional functioniality to retrieve stand-alone payments that are 1099-MISC related. Several adjustments
were also made to the two 1099-MISC detail reports to all the display of stand-alone payments. On the detail report
under the invoice/standing order column - a stand-alone payment document id will be "(StandAlone)" for each payment
that occurred.
SPECIAL INSTRUCTIONS:

Solution: 161684
SITUATION IDENTIFIED IN:
"Business Partners" (tccom4500m000)
SITUATION DESCRIPTION:
When changing the Search Key for a Business Partner, the system needs to update the Search Key in all the Roles by
Business Partner tables. In the situation that the Business Partner table is shared between the companies and the Roles by
Business Partner tables are not shared and there is no Roles by Business Partner record defined in the actual company, the
system did not update possibly existing records in the other companies.
SOLUTION DESCRIPTION:
The system is now updating the Search Key for the Roles by Business Partner tables in all companies that share the
Business Partner table.
SPECIAL INSTRUCTIONS:
None.

Solution: 161687
SITUATION IDENTIFIED IN:
"Copy Item Data" (tcibd0205m000)
SITUATION DESCRIPTION:
When copying item data, and the sales pricing parameter 'default price book' and 'default service price book' are the same,
an error 100 (duplicate value) is received on the price book data table.
SOLUTION DESCRIPTION:
Now when copying item data, and the sales pricing parameter 'default price book' and 'default service price book' are the
same, the copy process is completed properly.
SPECIAL INSTRUCTIONS:
None.

Solution: 161701
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme" (tfgld4500m000)
SITUATION DESCRIPTION:
Problem #1 (B52_a only)
In the details sessions it is possible to define a ledger account which has an Integration Indicator in the Mapping scheme
for the following financial Transactions.
- General Cost Via Finance
- WIP Via Finance
- Revenue Via Finance.
It was not possible to map default accounts which have an Integration Indicator for these same transactions.
Problem #2 (B52_a only)
When mapping integrations for transaction origin "fixed assets", it should not be possible to enter a transaction type or
series as the values entered in the mapping scheme are not used. The transaction type from the FAM parameters and its
default series are always used for fixed asset transactions.
Problem #3 (B50_b and B50_c)
It was not possible to map to ledger accounts with integration indicator for transactions
- WIP Via Finance
- Revenue Via Finance
SOLUTION DESCRIPTION:
Changes have been made so that it is now possible to map default ledger accounts with integration indicators for the
transactions (General Cost Via Finance, WIP Via Finance, Revenue Via Finance).
It is no longer allowed to enter a transaction type or series for fixed asset transactions.
Adjustments have been made in B50_b and B50_c (standard and localizations) so that it is now possible to map
integrations for WIP Via Finance & Revenue Via Finance.
SPECIAL INSTRUCTIONS:
None.

Solution: 161708
SITUATION IDENTIFIED IN:
"Material Issue for Production Orders" (ticst0101s000)
SITUATION DESCRIPTION:
When the material is returned from shop floor, if the outbound order line is open/advised/released and even when the
order quantity in outbound order line can be reduced, a new inbound order line is created.
SOLUTION DESCRIPTION:
When the material is returned from shop floor, if the outbound order line is open/advised/released, and if the order
quantity in outbound order line can be reduced, new inbound order line is not created. Instead, outbound order line
quantity is reduced.
SPECIAL INSTRUCTIONS:
Please download the solution 162303 to get the updated help texts related this topic.
DOCUMENTATION:
For more detailed functional info please ask for document #22199.

Solution: 161726
SITUATION IDENTIFIED IN:
"Qualified Demand by Period" and "Calculate Demand Forecast by Item" (whinr1520m000 and whina2202m000)
SITUATION DESCRIPTION:
When material is issued to a rework production order, the issued quantity is recorded as "Actual Issue" as can be seen
in the session "Qualified Demand by Period" (whinr1520m000). This data is later used in the session "Calculate
Demand Forecast by Item" (whina2202m000).
SOLUTION DESCRIPTION:
Material issues to a rework production order are not registered as "Actual Issue" in session "Qualified Demand by
Period" (whinr1520m000).
SPECIAL INSTRUCTIONS:
None.

Solution: 161748
SITUATION IDENTIFIED IN:
"Generate Product Variant Structure for Project." (tipcs2220m000)
SITUATION DESCRIPTION:
When generating a product variant structure, with a lower level generic item set to be replaced by a standard anonymous
item via the generic item data settings, the generation process continues down through the generic bom structure to the
lower levels below the standard item, which is not necessary and only presents performance issues.
SOLUTION DESCRIPTION:
Now when generating a product variant structure, with a lower level generic item set to be replaced by a standard
anonymous item via the generic item data settings, the generation process does not continue down through generic bom
structure to the lower levels below the standard item.
SPECIAL INSTRUCTIONS:
None.

Solution: 161765
SITUATION IDENTIFIED IN:
"Remove Fully-Paid Sales Invoices" (tfacr2260m000)
SITUATION DESCRIPTION:
The session is working very slowly even when trying to delete a few invoices.
SOLUTION DESCRIPTION:
The master data is archived each time this session is run to make sure that there are no reference errors in the archive
company. However, this process was being triggered more than once leading to excessive amount of time being taken. Now
this will be done just once.
SPECIAL INSTRUCTIONS:
None.

Solution: 161799
SITUATION IDENTIFIED IN:
"Generate Product Variant Structure for Project" (tipcs2220m000)
SITUATION DESCRIPTION:
1. When re-generating the project structure from the sales line and then selecting a component of the main top level item,
this component item is placed back on the sales line overwriting the main top level item. This is incorrect. The main top
level item should remain on the sales line.
2. When re-generating the project structure and the description is changed via generic item data settings, the search key 1
is not updated with the new description.
3. When generating the project structure, the search key 2 is not updated with the new customized item code.
SOLUTION DESCRIPTION:
1. Now when re-generating the project structure from the sales line and then selecting a component of the main top level
item, this main top level item remains on the sales line.
2. Now when re-generating the project structure and the description is changed via generic item data settings, the search
key 1 is updated with the new description.
3. Now when generating the project structure, the search key 2 is updated with the new customized item code.
SPECIAL INSTRUCTIONS:
None.

Solution: 161803
SITUATION IDENTIFIED IN:
"Integration Mapping" (tfgld4500m000)
"Integration Mapping Scheme" (tfgld4101s000)
"Options by Integration Element" (tfgld4121m000)
"Integration Relations by Range" (tfgld4122s000, tfgld4124s000)
"Integration Relations by Elements" tfgld4123s000, tfgld4125s000)
SITUATION DESCRIPTION:
When creating the integration mapping for Warehousing (Order) / Cycle Counting Adjustment, when doing a ZOOM in
the field Reason, sub-session Reasons (tcmcs0105m000) is displayed instead of session whinh5110m000 (Reason Codes
for Variance Changes).
For the above integration mapping combination the only valid option for the reason code will be the one from the
warehousing module, therefore the zoom should be made to Reason Codes for Variance Changes and not to session
Reasons.
SOLUTION DESCRIPTION:
1) In session Integration Mapping Scheme (tfgld4101s000) if the financial transaction is "Cycle Counting Adjustment"
then the zoom session will be Reason Code Variance Changes (whinh5110m000) for all other financial transactions the
zoom session will be "Reasons" (tcmcs0105m000).
2) In sessions Integration Relations by Range (tfgld4122s000, tfgld4124s000) and Integration Relations by
Elements(tfgld4123s000, tfgld4125s000) a new menu will be displayed when the user zooms on the "Reason Code"
field. The menu will provide the option to select session "Reasons" (tcmcs0105m000)" or session "Reason Code
Variance Changes (whinh5110m000)".
3) In session Integration Mapping Scheme (tfgld4500m000) the same Integration Element cannot be used for Transaction
Origin/Financial Transaction combinations Warehousing(Order)/Correction and Warehousing(Order)/Cycle Counting
Adjustment, if any integration option for the integration element is "Reason"
4) In session Options by Integration Element (tfgld4121m000) the integration option cannot be set to Reason if the
same Integration Element is used in the Mapping Scheme (tfgld4500m000) for Warehousing(Order)/Correction and
Warehousing(Order)/Cycle Counting Adjustment.
SPECIAL INSTRUCTIONS:
None.

Solution: 161818
SITUATION IDENTIFIED IN:
"Inbound Advice" (whinh2515m000)
SITUATION DESCRIPTION:
Create Inbound Advice for a production order using a storage unit other than the storage unit which was produced.
The session will allow a converted quantity greater than the quantity produced to be advised.
SOLUTION DESCRIPTION:
The session will no longer advise for a quantity greater than produced.
SPECIAL INSTRUCTIONS:
None.

Solution: 161854
SITUATION IDENTIFIED IN:
"Termination Process (Actual)" (tfgld1212s000)
SITUATION DESCRIPTION:
During finalization, the session tfgld1210m000 (Global Selection of Batches to Finalization) can generate an Error 205 -
tfgld110.sern not according to RANG (value 1000). This is due to the tfgld110.sern (Tax Sequence Number) not being
reinitialized correctly.
SOLUTION DESCRIPTION:
The tfgld110.sern (Tax Sequence Number) is now reinitialized correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 161883
SITUATION IDENTIFIED IN:
"Print Finalized Transactions By Date" (tfgld1440m000)
"Print Journal" (tfgld1441m000)
SITUATION DESCRIPTION:
When printing over all companies, transactions that are in batches that were created in other companies did not display on
the report.
SOLUTION DESCRIPTION:
Changes have been made so that transactions from all the companies entered on the form are now reported.
SPECIAL INSTRUCTIONS:
Customers on B52_a should also install solution 161983 after this solution.

Solution: 161930
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (Manufacturing/Order Management)" (tfgld4101s000)
SITUATION DESCRIPTION:
When trying to set-up an integration mapping scheme for transaction origin Manufacturing/Order Management, with the
combination 'Financial Business Partner Group(ACP)/Item Group/Reason Code', the error message " Invalid combination of
selected field for Key Definition " was given.
Similar combinations are allowed ('Financial Business Partner Group(ACP)/Reason Code' or 'Item Group/Reason Code') but
it is not possible to map using all three of these key elements.
SOLUTION DESCRIPTION:
Functionality has been changed to allow mapping the combination "Financial Business Partner Group(ACP)/Item
Group/Reason Code" as well as the related combination "Financial Business Partner Group(ACP)/Item/Reason Code"
The help text for integrations has been changed to show the new combinations and some changes have been made to the
posting process to make sure the new combinations are used when posting integration transactions.
SPECIAL INSTRUCTIONS:
None.

Solution: 161954
SITUATION IDENTIFIED IN:
"Generate Outbound Advice" and "Outbound Order Lines " (whinh4201m000 and whinh2520m000 )
SITUATION DESCRIPTION:
This situation applies when "Issue Components" is selected on the sales order lines.
When generating outbound advice for a list or phantom item or for the components of the main line item on a sales order,
which has insufficient inventory for its components, the system correctly generates outbound advice with a shortage the
first time. Subsequently, when more inventory is available for the components but not enough to cover the entire ordered
quantity, the system does not generate additional advice.
SOLUTION DESCRIPTION:
The system now generates additional outbound advises correctly, based on the additional inventory available for the
components.
SPECIAL INSTRUCTIONS:
None.

Solution: 161958
SITUATION IDENTIFIED IN:
"Confirm Shipments / Loads" (whinh4275m000)
SITUATION DESCRIPTION:
While confirming the shipment lines, the value of COGS (Cost of Goods Sold) in sales order lines depends on the behavior
of the database i.e. based on the sequence in which shipment positions are returned by the database.
SOLUTION DESCRIPTION:
Now, while confirming the shipment lines, the value of COGS (Cost of Goods Sold) in sales order lines are consistent by
forcing the database to return shipment positions in the required order.
SPECIAL INSTRUCTIONS:
None.

Solution: 161967
SITUATION IDENTIFIED IN:
"Close periods" (tfgld1206m000)
SITUATION DESCRIPTION:
1. Some amounts in the "History" tables (tfgld201, tfgld202 and tfgld205) and the "Opening balances" tables (tfgld203,
tfgld204 and tfgld206) have more digits after the decimal point than amounts in the "Transactions" tables (tfgld102 and
tfgld106) although amounts in the "History" tables and in the "Opening balances" tables are the sum of amounts from the
"Transactions" tables.
2. The last fiscal period cannot be finally closed for GLD module because difference between total credit and total debit is
too big. But all amounts in the "History" tables are correct.
SOLUTION DESCRIPTION:
Some amounts are stored in the database with more numbers after the decimal point than allowed (For instance,
0,4399999999). But in BAAN these amounts appear as numbers that are rounded according to the rounding factor (In our
example, 0,44). If we sum a great number (more than 40000) of these amounts then the result will have more decimals
than it should. That is why "History" tables and the "Opening balances" tables contain amounts that have more decimals
than allowed by the rounding factor.
1. Sessions that update the "History" tables and the "Opening balances" tables have been changed to round amounts before
saving. Refer to the components list to see the all changed sessions.
2. Total debit and total credit are rounded before comparing.
SPECIAL INSTRUCTIONS:
Solution # 162742 must be installed after installation of this solution.

Solution: 161970
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0101s000)
SITUATION DESCRIPTION:
The item revision is not shown correctly when selecting different items with different revisions.
SOLUTION DESCRIPTION:
Now the item revision is not shown correctly when selecting different items with different revisions.
SPECIAL INSTRUCTIONS:
None.

Solution: 161991
SITUATION IDENTIFIED IN:
"Print TAX Analysis" (tfgld1420m000)
SITUATION DESCRIPTION:
When using the session tfgld1420m000 (Print Tax Analysis) with the Final Print option, contra tax lines for shifted tax
are not being updated as printed. This prevents the archive session tfgld6207m000 from archiving these records.
SOLUTION DESCRIPTION:
The session has been modified to properly update contra tax lines for shifted tax when processing a 'Final Print'. An
additional change was made to the report layout to ensure that the contra tax lines for shifted tax are displayed correctly on
the report when using the option print contra for shift taxes.
SPECIAL INSTRUCTIONS:
None.

Solution: 162004
SITUATION IDENTIFIED IN:
"Picking List" (whinh2525m100)
SITUATION DESCRIPTION:
When confirming the shipments, with negative inventory allowed, the message "Cannot determine the cost of goods sold"
(whinas0062) is issued and the shipments are not confirmed.
SOLUTION DESCRIPTION:
The shipments can now be confirmed successfully. It is now not allowed to confirm shipment lines of stockpoints which
are blocked for inspection.
SPECIAL INSTRUCTIONS:
None.

Solution: 162072
SITUATION IDENTIFIED IN:
"Print Finalized Transactions By Ledger Account" (tfgld1406m000)
SITUATION DESCRIPTION:
It is an audit requirement in France to be able to print transactions by ledger account by tax period.
SOLUTION DESCRIPTION:
Functionality has been added to the report so that transactions can be selected by tax period. This functionality is added
only for French users. The localization parameter 'French Check Report' must be turned on to be able to use this additional
functionality.
SPECIAL INSTRUCTIONS:
None.

Solution: 162109
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Orders" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating project structure for sales order for a generic item, and there is item data text generated as part of this
process, then the generated
text does not appear on the sales acknowledgement, packing list or the sales invoice.
SOLUTION DESCRIPTION:
Now when generating project structure for sales order for a generic item, and there is item data text generated as part of
this process, then the generated text does appear on the sales acknowledgement, packing list or the sales invoice.
SPECIAL INSTRUCTIONS:
None.

Solution: 162118
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Order" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating project structure for a non-generic phantom item from a sales order, with the option 'create order lines
for phantom' set to YES, and the main item has another phantom item as a component, then the error 'no valid components
present' is received for the customized component.
SOLUTION DESCRIPTION:
Now when generating project structure for a non-generic phantom item from a sales order, with the option 'create order
lines for phantom' set to YES, and the main item has another phantom item as a component, then the customized component is
added to the sales order with the issue status set to 'issue main'.
SPECIAL INSTRUCTIONS:
None.

Solution: 162133
SITUATION IDENTIFIED IN:
"Remove Closed Warehousing Orders" (whinh2250m000)
SITUATION DESCRIPTION:
The session is run for a particular range with the option Error Report = No. Without closing the window, the session is run
for another range with the option Error Report = Yes. In the error report, the error logs corresponding to first range is
printed.
SOLUTION DESCRIPTION:
Now, even when the session is run repeatedly without closing the window, the error logs are printed correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 162165
SITUATION IDENTIFIED IN:
"General Item Data" (tcibd0101m000)
SITUATION DESCRIPTION:
After inserting a new item and then changing the inventory unit in the session "General Item Data" (tcibd0101m000), the
warning message "No conversion factor found between inventory unit and sales unit" (tcibds0150) is received.
This is incorrect, as no inventory is present and no orders are placed against this new item. The functionality should ask
the question to change the other units in sales, purchasing and service.
SOLUTION DESCRIPTION:
Now after inserting a new item and changing the inventory unit in the session "General Item Data" (tcibd0101m000), a
question is asked to "Change other units with same value?" (tcibd0101b). When answering yes to the question, the units in
sales, purchasing and service are updated to the new inventory unit.
SPECIAL INSTRUCTIONS:
None.

Solution: 162177
SITUATION IDENTIFIED IN:
"Chart of Accounts" (tfgld0508m000)
SITUATION DESCRIPTION:
It should not be possible to remove a ledger account using the "Chart of Accounts" (tfgld0508m000) session if an account
number has finalized transactions. This issue is only applicable in a multi-finance environment, since the deletion process
was not checking all possible companies for transactions.
SOLUTION DESCRIPTION:
When removing an account, the session now checks all companies for finalized transactions before permitting a deletion.
SPECIAL INSTRUCTIONS:
None.

Solution: 162194
SITUATION IDENTIFIED IN:
"Import Journal Voucher Batches by ID Number" (tfgld2215m000)
SITUATION DESCRIPTION:
Two users cannot use this session one after another until the first user exits the session. This is because the second user
is given the message "Journal Voucher Batches are being imported by other user". It should be possible for the second user to
import journals as soon as the first user has finished processing even if the first user forgets to exit the session.
SOLUTION DESCRIPTION:
This session should not be run by more than one user at a time. To prevent this, the session puts a lock on itself as soon
as importing begins. This lock was being removed too late i.e. only when the user exited the session. Now the lock will be
removed as soon as the importing ends allowing a second user to start using the session even if the first user has forgotten
to exit the session.
SPECIAL INSTRUCTIONS:
None.

Solution: 162247
SITUATION IDENTIFIED IN:
"Maintain Journal Vouchers (Multiple Lines)" (tfgld1115m000)
SITUATION DESCRIPTION:
When using "Maintain Journal Vouchers (Multiple Lines)" (tfgld1115m000), the ledger account and dimension
descriptions are not included on the display.
SOLUTION DESCRIPTION:
The ledger account and dimension description have been added to the session.
SPECIAL INSTRUCTIONS:
None.

Solution: 162252
SITUATION IDENTIFIED IN:
"Close Year - Provisional" (tfgld6201m000)
SITUATION DESCRIPTION:
1. Opening balances in the "Customer/Supplier History" (tables tfacr500 and tfacp500) have been updated based on the
batch year instead of the fiscal year.
2. Creation of the opening balances in the "Customer/Supplier History" (tables tfacr500 and tfacp500) has performance
problems.
3. LOCALIZATION ONLY: Opening balances in the "Customer/Supplier History" (tables tfacr500 and tfacp500) have not
been created for the non-trade control accounts.
SOLUTION DESCRIPTION:
1. The fiscal year is used when updating the "Customer/Supplier History" (tables tfacr500 and tfacp500).
2. The database requests have been optimized.
3. LOCALIZATION ONLY: The opening balances are created for the non-trade control accounts as well.
SPECIAL INSTRUCTIONS:
None.

Solution: 162303
SITUATION IDENTIFIED IN:
"Inventory Handling Paramters" (whinh0100s000)
SITUATION DESCRIPTION:
The help text for the parameter 'Correct SFC Production Order till' (whinh000.crpr) does not clearly state the intended
functionality.
SOLUTION DESCRIPTION:
The help text of the parameter 'Correct SFC Production Order till' (whinh000.crpr) is re-written to clearly state the
intended functionality.
SPECIAL INSTRUCTIONS:
You may need to download the solution 161708 if you have not already done so.

Solution: 162320
SITUATION IDENTIFIED IN:
"Initiate Inventory Issue" (tisfc0207m000)
SITUATION DESCRIPTION:
When initiating inventory for a production order, if the 'Issue Date' is backdated and the component item is new and
doesn't have a cost price for the date the user backdates to, the system still unblocks the outbound order line. This
outbound line cannot be released because there is no cost price for the date it's trying to issue. System issues the
error message "Effective Cost Component Structure for Item %s not found on Date %s and Time %s" (tcibds1204).
SOLUTION DESCRIPTION:
When initiating inventory for a production order, the system now ensures that cost price is present for the component as of
the 'Issue Date'. If the cost price is not present, the outbound is left blocked and the system issues the message "Cost price
structure not present for this date" (whinhs0510).
SPECIAL INSTRUCTIONS:
None.

Solution: 162328
SITUATION IDENTIFIED IN:
"Post Integration Transactions To Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
In the session "Default Project Data By Number Group" (tipcs0503m000), it is possible to set up a default project to be
used in integration mapping for a series of actual projects.
When assigning ledger accounts to integration transactions and using default projects for mapping, it was possible that
ledger accounts were assigned based on a mapping scheme of lower priority even though a valid mapping of higher
priority existed.
For example: A ledger account would be picked up based on a match with item group before a match with project/item
group if the mapping was based on default project.
SOLUTION DESCRIPTION:
The functionality of assigning ledger accounts for integration transactions has been changed. This will only change when
using default projects.
The priority list will now check the highest priority combination for actual project and then for default project before
checking the next highest priority. Previously, all combinations were checked for actual project before any combinations
were checked based on default project.
This solution solves the problem for distribution/manufactoring transactions. Please load solution 162554
to solve for service transactions.
SPECIAL INSTRUCTIONS:
None.

Solution: 162348
SITUATION IDENTIFIED IN:
"Shipment Lines" (whinh4131s000)
SITUATION DESCRIPTION:
When confirming shipments using the session "Shipment Lines" (whinh4131s000), the outbound order line status is not
changed from "Staged" to "Shipped". This happens only when using package definitions.
SOLUTION DESCRIPTION:
The outbound line status is now correctly updated from 'Staged' to 'Shipped' when confirming a shipment line in the
session "Shipment Lines" (whinh4131s000) when packaged definitions are involved.
SPECIAL INSTRUCTIONS:
None.

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

Solution: 162383
SITUATION IDENTIFIED IN:
"Transfer Planned Orders" (cppat1210m000)
SITUATION DESCRIPTION:
When transferring planned purchase orders for the same supplier but different buyers, the buyer on some of the purchase
order headers were incorrect.
SOLUTION DESCRIPTION:
When transferring planned purchase orders for the same supplier but different buyers, the buyer is correctly populated on
to the purchase order header.
SPECIAL INSTRUCTIONS:
None.

Solution: 162395
SITUATION IDENTIFIED IN:
"Generate Project Structure for Sales Orders" (tdsls4244m000)
SITUATION DESCRIPTION:
When generating project structure for sales order, for the newly generated item, the main item text is copied to the sales
item text. However, the text number of both the main item and the sales item are the same, thus preventing the sales item
text to be edited separately from the main item text.
SOLUTION DESCRIPTION:
Now when generating project structure for sales order, for the newly generated item, the main item text is copied to the
sales item text with a separate and different text number, thus allowing the sales item text to edited separately.
SPECIAL INSTRUCTIONS:
None.

Solution: 162402
SITUATION IDENTIFIED IN:
"Company Parameters" (tfgld0103s000)
SITUATION DESCRIPTION:
When entering the company parameters and zooming on the ledger accounts, the accounts displayed for selection were not
correct.
- For both the currency difference profit and loss accounts, only accounts of type "profit & loss" were displayed even
though the session accepts both "profit & loss" and "balance sheet" accounts.
- For the currency difference profit account, only accounts with the dual accounting indicator = "Statutory", currency
translation method = "BOTH", and currency analysis = "Not required" are allowed. The zoom on currency difference profit
account did not filter the ledger accounts displayed accordingly.
- For several other accounts defined in the parameters, only accounts with the currency translation method = "Both"
are allowed. The zoom would show accounts with currency translation methods other than "Both".
- There are two different currency translation accounts in the parameters one for "statutory" and one for
"complementary". The zooms for both of these accounts would show both statutory and complementary accounts.
SOLUTION DESCRIPTION:
- When zooming to select currency difference accounts, "balance sheet" accounts will now be displayed along with
"profit & loss" accounts.
- For the currency difference profit account, only ledger accounts that have dual accounting indicator = "Statutory",
currency translation method = "BOTH", and currency analysis = "Not required" will be displayed.
- For parameters that only accept ledger accounts with currency translation method = "BOTH" zooming will now only
display accounts that are defined as "BOTH".
- When zooming to select currency translation accounts, only "Statutory" or "complementary" accounts will be displayed
based on the currency translation account that is being selected.
SPECIAL INSTRUCTIONS:
None.

Solution: 162493
SITUATION IDENTIFIED IN:
"Copy Sales Quotation" (tdsls1201m000)
SITUATION DESCRIPTION:
When copying sales quotation lines for generic items with new customers, the sales quotation is not copied, but the variant
is copied with the original customer. Also, when copying sales order lines, the sales order is copied, but again the variant
is copied with the original customer.
SOLUTION DESCRIPTION:
Now when copying sales quotation/order lines for generic items with new customers, the sales quotation/order are copied,
and the variant is copied with the new customer.
SPECIAL INSTRUCTIONS:
None.

Solution: 162511
SITUATION IDENTIFIED IN:
"Remove Confirmed Shipments" (whinh4250m000)
SITUATION DESCRIPTION:
Sales order lines cannot be released to invoicing, if the confirmed shipments have been removed to history. The error
message "Cannot determine the cost of goods sold" is issued.
SOLUTION DESCRIPTION:
Now the confirmed shipments can be removed only after the sales order lines are released to invoicing.
SPECIAL INSTRUCTIONS:
None.

Solution: 162539
SITUATION IDENTIFIED IN:
"Import Journal Voucher Batches by ID Number" (tfgld2215m000)
SITUATION DESCRIPTION:
No transaction lines are imported even though they should be.
SOLUTION DESCRIPTION:
The form field Audit was not being initialized properly. This was causing the process that imports the data to be skipped.
Now the form field Audit is initialized allowing the import process to occur.
SPECIAL INSTRUCTIONS:
None.

Solution: 162554
SITUATION IDENTIFIED IN:
"Post Integration Transactions To Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
In the session "Default Project Data By Number Group" (tipcs0503m000), it is possible to set up a default project to be
used in integration mapping for a series of actual projects.
When assigning ledger accounts to integration transactions and using default projects for mapping, it was possible that
ledger accounts were assigned based on a mapping scheme of lower priority even though a valid mapping of higher
priority existed.
For example: A ledger account would be picked up based on a match with item group before a match with project/item
group if the mapping was based on default project.
SOLUTION DESCRIPTION:
The functionality of assigning ledger accounts for integration transactions has been changed. This will only change when
using default projects.
The priority list will now check the highest priority combination for actual project and then for default project before
checking the next highest priority. Previously, all combinations were checked for actual project before any combinations
were checked based on default project.
This solution solves the problem for service transactions. Please load solution 162328 to solve for
distribution/manufactoring transactions.
SPECIAL INSTRUCTIONS:
None.

Solution: 162564
SITUATION IDENTIFIED IN:
"Termination Process (Actual)" (tfgld1212s000)
SITUATION DESCRIPTION:
The lines written to the Tax Analysis Table (tfgld110) have the wrong sign for the contra for shifted tax record.
SOLUTION DESCRIPTION:
This was caused by the incorrect initialization of field values when the contra for shifted tax lines were created. Now the
values are initialized correctly and the signs will be correct.
SPECIAL INSTRUCTIONS:
None.

Solution: 162581
SITUATION IDENTIFIED IN:
"Transaction types" (tfgld0111s000)
SITUATION DESCRIPTION:
1. When an existing transaction type is opened and the user just looks at the data in all three forms and exists without
modifying anything a message is shown "Data has been changed....". Since nothing has been changed this message should
not appear.
2. For a transaction type of category Journals or Recurring/Reversing journals if one sets up the decimal characters for
quantities and amounts on form 2 as a comma, they get displayed as dots instead of comma when viewing them later.
3. When inserting or modifying a transaction type, if the transaction category is entered as anything other than
Purchase or Sales Credit note and then changed to Purchase or Credit Note one can get a confusing message "Enter
Yes/No" when trying to save the changes and the changes do not get saved.
SOLUTION DESCRIPTION:
1. Only transaction types of category Journals or Recurring / Reversing Journals can have values in the fields "Date Format", "Decimal
character for Amount", and "Decimal character for Quantity". The user does not have access to these fields for any other transaction category and
these fields are displayed as blanks. However, when saving a new transaction type, these fields got saved with values incorrectly. When this record
was selected for modification the system internally corrected the values to blanks and hence the user received the message even though the user
did not change anything. The problem of incorrect value while creating new transaction types has been corrected so the problem will not happen
for new transaction types. For
existing transaction types the user should select "Save" when prompted with the message once. Then the correct values will
be stored and the user will not receive this message from next time onwards for that transaction type.
2. Now the correct value comma or dot as entered by the user will be displayed.
3. This message got shown because the field "Negative Amount for Credit Notes" on the third form got an incorrect value
when the steps defined above are followed. This field should either have a "yes" or "no" value but got an empty value. Thus
the saving of the record failed. Now this field will have a value and this message will not appear.
SPECIAL INSTRUCTIONS:
None.

Solution: 162599
SITUATION IDENTIFIED IN:
"Item Costing Data" (tcibd0107m000)
SITUATION DESCRIPTION:
When manufacturing is turned off, item costing data can still be accessed, however the costs cannot be calculated.
SOLUTION DESCRIPTION:
Now when manufacturing is turned off, item costing data can be accessed, and the costs can be calculated.
SPECIAL INSTRUCTIONS:
None.

135398

SITUATION IDENTIFIED IN:

"Tax Transactions" (tfacp1112s000)

SITUATION DESCRIPTION:

The Purchase invoice is left unbalanced when the purchase invoice related with order has the Tax code introduced by line using session "Tax Transactions - tfacp1112s000) when the transaction type has defined the update mode as "Real time". The batch is left unbalanced by the tax amount.

SOLUTION DESCRIPTION:

The Vat amounts in Home Currency are filled correctly now so the batch is not left unbalanced anymore.

135428

SITUATION IDENTIFIED IN:

"Sales Order Lines" (tdsls4101s000)

SITUATION DESCRIPTION:

It is not possible to save a changed Tax Code in the Sales Order Lines (session tdsls4101s000) in the Localizations. The Tax Code is set back to the default Tax Code when saving the changes.

SOLUTION DESCRIPTION:

The changed Tax Code will not be overwritten by the default anymore.

135430

SITUATION IDENTIFIED IN:

"Purchase Invoice Corrections" (tfacp2110s000)

SITUATION DESCRIPTION:

If in the localization parameter the option "Generic Taxes" is set, then when doing a "Purchase Invoice Correction" (tfacp2110s000) of an invoice with a tax code, the batch is not getting balanced during finalization.

SOLUTION DESCRIPTION:

The purchase correction goes correctly and the batch is balanced.