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 jpn0 tf Script/Library Source glddll1011 spb50b_15
B50L b jpn0 tf Script/Library Object glddll1011 spb50b_15
B50L b jpn0 tf cisli2200m000 Script/Library Source intdlltfgld spb50b_15
B50L b jpn0 tf cisli2200m000 Script/Library Object intdlltfgld spb50b_15
B50L b jpn0 ti Script/Library Source intdlltfgld spb50b_15
B50L b jpn0 ti Script/Library Object intdlltfgld spb50b_15
B50L b jpn0 ti tipcs3480m000 Script/Library Source pcs3480 spb50b_15
B50L b jpn0 ti tipcs3480m000 Script/Library Object pcs3480 spb50b_15
B50L b jpn0 ti ticst0450m000 Script/Library Object cstdll0450 spb50b_15
B50L b jpn0 ti Help Text DMcst.detw spb50b_15
B50L b jpn0 ti Help Text DMcst.kwip spb50b_15

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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 130527
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100s000)
SITUATION DESCRIPTION:
Rounding Difference not posted properly when assigning Unallocated Receipts to invoices.
SOLUTION DESCRIPTION:
Now, Rounding Difference is posted properly after assigning Unallocated Receipts to invoices.
SPECIAL INSTRUCTIONS:
None.

Solution: 130540
SITUATION IDENTIFIED IN:
"General Localization Parameters" (tccoml100s00l)
SITUATION DESCRIPTION:
When the session is started in the Japanese localization the following BW message comes up:
"BW Error: unknown formfield 'isbe.l' occurs"
SOLUTION DESCRIPTION:
The formfield is now defined for the Japanese localization and the message does not appear anymore.
SPECIAL INSTRUCTIONS:
This contains table definition changes.
Please note, you must run ttadv5210m000 Create Runtime Data Dictionary for the tables and domain.

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: 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: 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: 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: 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: 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: 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: 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: 130821
SITUATION IDENTIFIED IN:
"Register Purchase Invoice" (tfacp1110s000)
SITUATION DESCRIPTION:
When the Purchase invoice was approved, the transaction entry date is filled with blank.
SOLUTION DESCRIPTION:
Now Transaction entry date is filled correctly for the Approved purchase invoice document.
SPECIAL INSTRUCTIONS:
None.

Solution: 130827
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
The standard cost price of a manufacturing item is not getting updated, if the calculated cost price is zero. If the BOM
(Bills of material) and routing get expired for a manufacturing item, even though the system calculates the cost price, the
standard cost price sessions will not be updated.
SOLUTION DESCRIPTION:
When the calculated cost price of a manufacturing item is zero, the standard cost price sessions will be updated.
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: 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: 130857
SITUATION IDENTIFIED IN:
"Match Purchase Order Line" (tfacp2541s000)
SITUATION DESCRIPTION:
When the Order number and packing slip are not entered in the Purchase Invoice, and when the session Match Purchase
order line is started for matching the orders, the performance is bad.
SOLUTION DESCRIPTION:
Now, the session "Match Purchase order line " uses the correct Index when starting from the session Purchase Invoice.
The performance has been optimized.
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: 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: 130982
SITUATION IDENTIFIED IN:
"Delete WIP transactions by Project/Order" (tcfin1200m000)
SITUATION DESCRIPTION:
When deleting wip (Work In Process) transactions for one or a range of production orders or PCS project
the transactions for closed and archived production orders / PCS projects are removed.
SOLUTION DESCRIPTION:
New functionality:
Add an extra option on the form tcfin1200m000 (Delete Wip transactions by Projects/ Production Order).
When ticking the option 'Only archived production orders / PCS projects' only the Work in Process transaction
for archived PCS Projects or Production Orders are removed.
When leaving this option unchecked the old functionallity is used as described in the situation description.
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: 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: 131061
SITUATION IDENTIFIED IN:
Calculate Cost and Valuation Prices (ticpr2210m000)
SITUATION DESCRIPTION:
The standard cost price of a manufacturing item is not getting updated, if the calculated cost price is zero. If the BOM
(Bills of material) and routing get expired for a manufacturing item, even though the system calculates the cost price, the
standard cost price sessions will not be updated.
SOLUTION DESCRIPTION:
When the calculated cost price of a manufacturing item is zero, the standard cost price sessions will be updated.
SPECIAL INSTRUCTIONS:
Please download this solution along with solution 130827.

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: 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: 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: 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: 131179
SITUATION IDENTIFIED IN:
Purchase Order Receipts (tdpur4101s300)
SITUATION DESCRIPTION:
-1- If the valuation method is "average cost (aavg)" , for a sales return order the FTP is posted instead of "Average Cost "
-2-
1. The default inventory valuation method is defined as 'Average Cost' in "Inventory Valuation Methods"
(whina1100m000) for the item group of the item.
2. A direct delivery sales order line is created and the purchase order is generated correspondingly for this sales order.
3. While receiving this purchase orderline in "Purchase Order Receipts" (tdpur4101s300), an error message
"Stock/Financial updation failed" appears and the receipt is not saved.
-3- If the valuation method is "average cost (aavg)" and there is a difference between the purchase order price and the
average cost price, wrong integration transaction "purchase/value correction" is generated for a purchase return order.
SOLUTION DESCRIPTION:
-1- If the valuation method is "average cost (aavg)" , for a sales return order "Average cost " is posted correctly
-2- The receipt of direct delivery purchase orders is saved. The error message no longer appears.
-3- The correct Integration transaction " Purchase Result " is generated in case of purchase return order .
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: 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: 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: 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: 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: 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: 131317
SITUATION IDENTIFIED IN:
"Process Inventory Variances" (whina1200m000)
SITUATION DESCRIPTION:
Variances are created in session "Inventory Variances" (whina1516m000). When the valuation method is "FTP" these are
not resulting into financial transactions. The same should apply when the inventory valuation is "Average Cost (aavg)".
For aavg, a warehouse (valuation) booking is created when session "Process Inventory Variances" (whina1200m000) is
run.
SOLUTION DESCRIPTION:
The warehouse (valuation) / value correction and warehouse (valuation) / retroactive value adjustment bookings are not
created anymore.
SPECIAL INSTRUCTIONS:
None.

Solution: 131328
SITUATION IDENTIFIED IN:
"Totals for Business Partner by Company" (tfacr2534m000)
SITUATION DESCRIPTION:
Fatal Error in session "Totals for Business Partner by Company " : 'Index 3 out of dims, cannot continue in
tfacr2534m000'
SOLUTION DESCRIPTION:
Fatal error does not occur now.
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: 131359
SITUATION IDENTIFIED IN:
"Cash Management Transactions" (tfcmg2120s000)
SITUATION DESCRIPTION:
Tax amount in Home currency was showing wrongly
SOLUTION DESCRIPTION:
Now, VAT amount in Home currency shown correctly.
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: 131382
SITUATION IDENTIFIED IN:
"Bank Transactions" (tfcmg2100m000)
SITUATION DESCRIPTION:
The reference given on the 2nd form of session 'Bank Transactions' is not filled within 'Non finalized transactions'
(tfgld102) during payment/receipt reconciliation. The reference within tfgld102 is generated automatically and filled
with bank relation and anticipated document number. This is a particular problem when recording the cheque number sent
to the supplier or received by a customer.
SOLUTION DESCRIPTION:
After reconciliation, if the reference is blank, the reference field within 'Non-finalized transactions' is filled with the
bank relation and anticipated document number for the documents that were reconciled. If the reference is filled manually
during reconciliation, this manual entered reference is considered.
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: 131390
SITUATION IDENTIFIED IN:
"Print Detailed Scheme of Fixed Asset Transactions" (tffas0441m000)
SITUATION DESCRIPTION:
In report "Purchase Details" of session "Print Detailed Scheme of Fixed Asset Transactions" (tffas0441m000), the column
"By end of fiscal year" was showing incorrect values in case of disposed assets.
SOLUTION DESCRIPTION:
In case of disposed assets, the column "By end of fiscal year" displays zero value.
SPECIAL INSTRUCTIONS:
None.

Solution: 131393
SITUATION IDENTIFIED IN:
"Warehousing Orders" (whinh2500m000)
SITUATION DESCRIPTION:
When a manual warehouse transfer of an item is completed, the valuation results are booked in finance, even though the
issue and receipt values do not differ.
SOLUTION DESCRIPTION:
The actual amounts from warehousing and calculated amounts from costing are rounded based on same domain, which
eliminates the calculation of valuation results, if receipt and issue values are same.
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: 131410
SITUATION IDENTIFIED IN:
"Sales Invoice" (tfacr1110s000)
SITUATION DESCRIPTION:
Calculation of discounts is wrong, when the "Discounts including Tax " in Terms of Payment (tcmcs013) is off.
Calculation is done without considering the tax amount.
SOLUTION DESCRIPTION:
Calculation of discounts is done with the tax amount when "Discounts including Tax " in Terms of Payment (tcmcs013) is
on. Calculation of discounts is done without the tax amount when "Discounts including Tax " in Terms of Payment
(tcmcs013) is off.
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: 131458
SITUATION IDENTIFIED IN:
Integration Transactions by Order / Project (tfgld4510m000)
SITUATION DESCRIPTION:
If the valuation method is "Average Cost (aavg)", for Sales return order FTP is posted instead of "Average Cost ".
SOLUTION DESCRIPTION:
If the valuation method is "Average Cost (aavg)", for Sales return order "Average cost " is posted correctly.
SPECIAL INSTRUCTIONS:
None.

Solution: 131463
SITUATION IDENTIFIED IN:
"Select Invoices for Direct Debits" (tfcmg4220m000)
SITUATION DESCRIPTION:
Partially paid invoices are not allowed to select in direct debit batches
SOLUTION DESCRIPTION:
Now, Partially paid invoices are allowed to select in direct debit batches.
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: 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: 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: 131526
SITUATION IDENTIFIED IN:
"Copy Balances to History Before Specified Year" (tfgld6206m000)
SITUATION DESCRIPTION:
It is not possible to archive Japanese history tables.
SOLUTION DESCRIPTION:
It is possible to archive Japanese history tables.
SPECIAL INSTRUCTIONS:
None.

Solution: 131533
SITUATION IDENTIFIED IN:
"Correct COGS Intgrations" (cicor0111m000)
SITUATION DESCRIPTION:
When sales order is raised in one company and the sales office is linked to another finance company, running
correction program "Correct COGS" (cicor0111m000) gives error "Record not locked".
SOLUTION DESCRIPTION:
Now the fatal error does not arise.
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: 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: 131580
SITUATION IDENTIFIED IN:
"Import Actual Performance" (tfcat2220m000)
SITUATION DESCRIPTION:
The session "Import Actual Performance" (tfcat2220m000) did a wrong import of the records from HRA if the option "Old
Values" on the form is set to "Replace".
SOLUTION DESCRIPTION:
The import of actual performance information from HRA module takes place correctly.
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: 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: 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: 131755
SITUATION IDENTIFIED IN:
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
Error "Run time function call problem" on running the session "Print Actual Cost-Price by Project" (tipcs3462m000) for
a PCS project having surcharges more than 200.
SOLUTION DESCRIPTION:
The allocation of maximum surcharges for a PCS project has been increased to 500 from 200.
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: 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: 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: 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: 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: 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: 131883
SITUATION IDENTIFIED IN:
"Print Currency wise Trial Balance" (tfgld3403m000)
SITUATION DESCRIPTION:
Under Job Process, Rotate Currency does not work. The details in the report are always in the default form currency.
SOLUTION DESCRIPTION:
When Job Process is used, details are printed in the home currency, selected using Rotate Currency.
SPECIAL INSTRUCTIONS:
None.

Solution: 131885
SITUATION IDENTIFIED IN:
"Calculate cost and valuation prices" (ticpr2210m000)
SITUATION DESCRIPTION:
The updation of standard cost price is not correct, if the cost price of manufacturing item is zero.
SOLUTION DESCRIPTION:
The standard cost price will be updated correctly, if the calculated cost price of manufacturing item is zero.
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: 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: 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: 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: 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: 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: 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: 132131
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices " (ticpr2210m000)
SITUATION DESCRIPTION:
Performance problem in the session "Calculate Cost and Valuation Prices" (ticpr2210m000) when calculating the cost price
of a single item, if the item group range is wide open.
SOLUTION DESCRIPTION:
Performance improvement while calculating cost prices of the Item, when the Item Group is wide open (without filling up
the range).
SPECIAL INSTRUCTIONS:
None.

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: 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: 132164
SITUATION IDENTIFIED IN:
"Compose/Print/Post invoices" (cisli2200m000)
SITUATION DESCRIPTION:
The Error 'Not all documents balanced is shown' occurs
If a record is not maintained for ' Financial Data for Tax Code by country ' in the case of multiple taxes, then while posting
project sales invoice, the system is creating only debit line in non-finalized transactions.
SOLUTION DESCRIPTION:
If a record is not maintained for ' Financial Data for Tax Code by country ' in the case of multiple taxes, then while
posting project sales invoice, no Postings will be made now in the non-finalized transactions and an Error 'Ledger account
not filled' will be shown correctly instead of the wrong error ' Not all documents balanced is shown '.
SPECIAL INSTRUCTIONS:
None.

Solution: 132197
SITUATION IDENTIFIED IN:
"Close year" (tfgld6203m000)
SITUATION DESCRIPTION:
During the process of close year, if the update mode of the transaction type is ' Finalization ', then the opening balances
of ILT history tables are not updated.
SOLUTION DESCRIPTION:
The Update mode ' Finalization ' is not allowed during the process of close year and so the opening balances of ILT
history tables will get updated only when the Update mode of the transaction type is "Real time " or "End of Session".
SPECIAL INSTRUCTIONS:
None.

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: 132232
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
Error index out of dims 250[251], during cost price calculation and inventory revaluation for an item. The item has
multiple cost price components defined and the item is present in large number of warehouses.
SOLUTION DESCRIPTION:
Inventory revaluation is done without any errors, If multiple cost price components are defined for an item present in
large number of Warehouses.
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: 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: 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: 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: 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: 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: 132434
SITUATION IDENTIFIED IN:
"Print Scheme of Fixed Asset Transactions" (tffas0440m000)
SITUATION DESCRIPTION:
Depreciation Adjustment amounts of previous year are not considered while calculating the depreciation amounts for the
previous year in report "Print Scheme of Fixed Asset Transactions" (tffas0440m000).
SOLUTION DESCRIPTION:
The previous year's depreciation adjustment amounts are taken into consideration.
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: 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: 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: 132599
SITUATION IDENTIFIED IN:
"Print Multi-level Cost Price Calculation" (ticpr2420m000)
SITUATION DESCRIPTION:
When the session "Print Multi-level Cost Price Calculation" (ticpr2420m000) is run to print the report for standard items
with EOQ (Economic order quantity) sub item flag set to NO, then system takes the BOM quantity as order quantity for sub
item cost calculations, instead of end item's order quantity.
SOLUTION DESCRIPTION:
If EOQ (Economic order quantity) Sub item flag set to NO for standard items, then the order quantity for sub item will be
BOM quantity times the end item's order quantity, for operation cost calculation in the report.
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: 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: 132679
SITUATION IDENTIFIED IN:
"Print Actual Cost-Price by Project" (tipcs3462m000)
SITUATION DESCRIPTION:
The report "Print Actual Cost-Price by Project" shows incorrect quantities, if the receipts for the purchase order lines are
more than one and are not backorders.
SOLUTION DESCRIPTION:
The report "Print Actual Cost-Price by Project" will show only one record per purchase order with correct delivered and
approved quantity.
Please note that this session is developed for printing costing details and not for printing logistical details. So detailed
info on receipts will have to be collected elsewhere; for example in "WIP Transactions by Project"(tcfin1500m001))
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: 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: 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: 132830
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
Session "Print Project Work In Process" (tipcs3480m000), when using form selection "By Ledger Account" (for detail level
) will show in the report field "Total of Leger Account xxxxxx in History" an incorrect amount. This will only occur when
a range of ledger accounts is selected and listed on the report. Also this amount is not recalculated when the Print
currency is changed on the second form.
SOLUTION DESCRIPTION:
The session "Print Project Work In Process" (tipcs3480m000), when using form selection "By Ledger Account" ( for detail
level ) will show the correct amount in the report field "Total of Leger Account xxxxx in History".
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: 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: 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: 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: 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: 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: 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: 133018
SITUATION IDENTIFIED IN:
"Match Orders" (tfacp2541s000)
"Match Receipts" ( tfacp2544s000 )
SITUATION DESCRIPTION:
1. It was not possible to see the Orders / Receipts belonging to the child Business partners of the Invoice from Business
partner mentioned in the Invoice header.
2. A fatal error( Syntax incorrect ) occurs when choosing the Option "Change Order" in the session Match orders.
3.The sorting of the data in the session Match receipts is not not correct when choosing to change the Sort by option Via
the View option.
SOLUTION DESCRIPTION:
1.Its possible to view the child business partner belonging to the Invoice from Business partner mentioned in the Invoice
header.
2. The fatal error no longer occurs when choosing the option "Change Order "
3. When changing the sort by option, the data is sorted according to the option choosen by the user.
Notes on additional changes to the session.
Changes in Specific options:
---------------------------------------------
There has been added 4 new Specific options , namely
- Show BP data only
This option is the default when the invoice is not matched and will show only the Order/ receipts belonging to the
invoice from Business partner mentioned in the Invoice header.
- Show Parent BP and its children
This option will display the Order / Receipt data belonging to the Invoice from Business partner of the Invoice header, Its
parent, and the children of this parent business partner.
- Show BP and its children
This option will show all the Orders/ Receipts belonging to the current Invoice from BP, and its children BP.
- Show Parent and child BP data
This option will show the orders / receipts belonging to all the related BP – So the invoice from BP, its parent, the
parents children and the children of the Invoice from BP.
These options will be disabled when,
- Choosing to see only the Matched Orders / receipts using the option "Hide/ Show Matched Order lines.
- Choosing the Change Order Option.
Changes to the specific option "Change Order" / "Change Packing slip Order number"
---------------------------------------------------------------------------------------------------------------------------------------
1. It will not be possible to Enter an order which is not related to the Invoice from Business Partner of the Invoice header.
2. When an order number is mentioned in the Invoice header, and using the Change order option, if the invoice is matched
with a different order number, then the order number mentioned on the Invoice header will be blanked ( filled with spaces
).
What happens when the invoice is already matched ?
-------------------------------------------------------------------------------------
When the Invoice is already matched then when going to the session "Match order" or "Match Receipt" only the matched
order / receipts will be displayed. The user can see the other non matched Orders/ Receipts by the Specific option "Hide
/ Show matched Order line"
SPECIAL INSTRUCTIONS:
Please note Solution 132323 need to have been Installed for B50_b and B50_c versions and solution 132508 should have
been installed for B52_a versions, before installing this solution.

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: 133021
SITUATION IDENTIFIED IN:
"Print Specifications Delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
Wrong data is displayed, in the case of "direct delivery" with Multiple Shipments. Besides, the performance of the
session was bad.
SOLUTION DESCRIPTION:
Correct data is displayed now. In addition, the performance of the session is improved.
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: 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: 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: 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: 133114
SITUATION IDENTIFIED IN:
"Direct Debit Advice" (tfcmg4120s000)
SITUATION DESCRIPTION:
It's not possible to assign an amount that exceeds the invoice balance to the 'Amount to be cashed'. Error "Amnt to be
cashed exceeds invoice balance' appears.
SOLUTION DESCRIPTION:
It's possible to cash an amount that exceeds the invoice balance. Warning message 'Amount to be cashed exceeds invoice
balance' will be given and the user can proceed. The difference will be posted as payment difference.
SPECIAL INSTRUCTIONS:
1. Download the solution 132967 along with this solution.
2. Download the solution 133208 along with this solution.

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: 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: 133140
SITUATION IDENTIFIED IN:
"tfcmgl270m00l" (Process Payment Batch)
SITUATION DESCRIPTION:
During Process of Payment Batch, Split up of Statement amount was not matching with Payment agreement when payment
batch has both Purchase invoices and negative amount Credit note.
SOLUTION DESCRIPTION:
Now Process statement of Accounts, Split up of Statement amount is matching with Payment agreement when payment
batch has both Purchase invoices and negative amount Credit note
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: 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: 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: 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: 133205
SITUATION IDENTIFIED IN:
"Print Specifications Delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
If limited/Small range of Orders selected, report is taking longer time to print. Required to optimize the query to
improve performance.
SOLUTION DESCRIPTION:
Performance improvement comes into picture when a limited/small range of Orders selected.
If the huge/open range of Orders selected then there may not be any change in the performance.
SPECIAL INSTRUCTIONS:
None.

Solution: 133207
V
ERSION(S):
B50_b
SITUATION IDENTIFIED IN:
"Generate Invoices by Selfbilling" (tfacp2290m000)
SITUATION DESCRIPTION:
When multiple instances of session "Generate invoices by selfbilling " is opened then Fatal error "Record is locked " is
triggered on table Last used document number ( tfgld017 ) .
SOLUTION DESCRIPTION:
Now, when the record on the last used document number table ( tfgld017 ) is locked, the user is warned about it, and it is
advised to try again later. This solution is applicable only to Japanese Version.
SPECIAL INSTRUCTIONS:
None.

Solution: 133208
SITUATION IDENTIFIED IN:
"Direct Debit Advices" (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. If the payment method has the option "Deductions allowed" as
No and the parameter "Trade note" is "ON", no payment difference is allowed. For such parameter set up, it is not
allowed to receive more than the invoice amount.
SOLUTION DESCRIPTION:
Checks are made based on the option "Deductions allowed".
It is possible to receive amount more than the invoice balance. Warning message 'Amount to be cashed exceeds invoice
balance' will be given and a payment difference will be posted.
SPECIAL INSTRUCTIONS:
1. Download the solution 132967 along with this solution.
2. Download the solution 133114 along with this solution.

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: 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: 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: 133283
SITUATION IDENTIFIED IN:
"tfcmgl484m00l" (Print Payment Assessment Reports)
SITUATION DESCRIPTION:
Fatal error "Index 0 out of dims [1] 3" occurs if the company has single currency system.
SOLUTION DESCRIPTION:
Now Fatal error will not occur even if the company has the single currency system.
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: 133307
SITUATION IDENTIFIED IN:
"Print specifications delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
In the session, it is not possible to select and print the report for a range of PCS-Projects.
SOLUTION DESCRIPTION:
It is now possible to select and print the report for a range of PCS-Projects.
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: 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: 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: 133411
SITUATION IDENTIFIED IN:
"Close year " (tfgld6203m000)
SITUATION DESCRIPTION:
Opening balances of Japanese history tables are not updated correctly during the process of close year and rebuilding.
SOLUTION DESCRIPTION:
Opening balances of Japanese history tables are updated correctly during the process of close year and rebuilding.
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: 133493
SITUATION IDENTIFIED IN:
"Print Specifications Delivered but not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
If transaction origin is 'sales (invoicing)' or if sales order has sequence number then status information not reported.
SOLUTION DESCRIPTION:
Now, status information displayed in all cases.
SPECIAL INSTRUCTIONS:
None.

Solution: 133511
SITUATION IDENTIFIED IN:
"Calculate Cost Prices by Project" (tipcs3250m000)
SITUATION DESCRIPTION:
When service orders are related to a PCS project then the Cost of Goods Sold ( COGS ) are made for the Sales Invoicing
(Service) but also for the PCS project.
SOLUTION DESCRIPTION:
When service orders are related to a PCS project then the Cost of Goods Sold ( COGS ) are made only for the Sales
Invoicing (Service) transaction.
SPECIAL INSTRUCTIONS:
On May 21th 2003 the missing Japanese localization solution was added. Customers who use the Japanese localization, and
have downloaded or installed thie standard solution before May 21th should download and install the Japanese solution.
When you have double Cost of Goods Sold transactions and your PCS Project status is lower then "Closed", there is no
problem.
The program "Calculate Cost Prices by Project" (tipcs3250m000) will reverse the integration transaction "Project (PCS) /
Cost of Goods Sold (General).
In case the PCS Project status has the status "Closed", then this PCS Project status should be manually reset to "Finished"
and then "Closed" with the
session "Close Project" (tipcs2250m000); this will start the subsession "Calculate Cost Prices by Project" (tipcs3250m000)
and it will also reverse the
integration transaction "Project (PCS) / Cost of Goods Sold (General).
To indentify those closed PCS Projects you can use the session "Print PCS Project Transaction Specification"
(tfgld4418m100),
and check if you have the transactions :
Sales Invoicing (Service) / Cost Goods Sold (Operation)
Sales Invoicing (Service) / Cost Goods Sold (General)
and PCS Project status equal to "closed".
For these PCS projects you probably have the double COGS problem, and you should consider to correct these
transactions as decsribed above.

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

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

Solution: 133550
SITUATION IDENTIFIED IN:
"Calculate cost prices by Project" (tipcs3250m000)
SITUATION DESCRIPTION:
When cost price of a project is calculated, system generates an error report with message "Cost price of the item is zero",
even if the calculated cost price of customized item is non-zero.
SOLUTION DESCRIPTION:
If the calculated cost price of the customized item is zero, then only system generates an error report with message "Cost
price of the item is zero".
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: 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: 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: 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: 133643
SITUATION IDENTIFIED IN:
"Print Aging-Analysis by Invoice-from Business Partner" (tfacp2420m000)
SITUATION DESCRIPTION:
In session "Print Aging-Analysis by Invoice-from Business Partner" (tfacp2420m000), the defaults are not saved under
the group "Dates and Periods".
SOLUTION DESCRIPTION:
The defaults are not getting changed to the current date or periods.
SPECIAL INSTRUCTIONS:
None.

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

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: 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: 133803
SITUATION IDENTIFIED IN:
"Calculate Cost and Valuation Prices" (ticpr2210m000)
SITUATION DESCRIPTION:
If no receipt history exist the fields Annual Average Cost(material), Annual Average Cost(operation) and Annual
Average Cost(surcharge) from table "Item Inventory by Warehouse" (whwmd215) aren't updated.
SOLUTION DESCRIPTION:
An extra check is created that determines if a receipt history exist. If not, the mentioned fields are updated.
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: 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: 133846
SITUATION IDENTIFIED IN:
"Specifications Delivered, not yet invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
The report ' Specifications Delivered, not yet invoiced ' is showing incorrect values for the consignment payment sales
order.
SOLUTION DESCRIPTION:
The report ' Specifications Delivered, not yet invoiced ' is showing correctly for the consignment payment sales order.
SPECIAL INSTRUCTIONS:
For non-PMC users: Please install solution 134262.
For PMC users: Please install this solution and solution 134262.

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: 133885
SITUATION IDENTIFIED IN:
"Print Invoice-from/to Business Partner's Finalized Transactions" (tfacp2416m000/tfacr2416m000)
SITUATION DESCRIPTION:
It is only possible to print this session up to a period and not to print this session from until a period.
SOLUTION DESCRIPTION:
Because changing the functionality of the session the possibility to print from/until is there.
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: 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: 133984
SITUATION IDENTIFIED IN:
"Specifications Delivered, not yet invoiced " (tfacr1432m000)
SITUATION DESCRIPTION:
The Report ' Specifications Delivered, not yet invoiced ' is printing incorrectly even though sales invoice maintained for
order.
SOLUTION DESCRIPTION:
The Report ' Specifications Delivered, not yet invoiced ' is printing correctly
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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 134350
SITUATION IDENTIFIED IN:
"Process Payment Batch" (tfcmgl270m00l)
SITUATION DESCRIPTION:
Payment advices are split incorrectly with differences of small amounts.
SOLUTION DESCRIPTION:
Now Payment advices are split correctly
SPECIAL INSTRUCTIONS:
None.

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: 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: 134406
SITUATION IDENTIFIED IN:
"Transfer Plan/Order" (cppat1210m000)
SITUATION DESCRIPTION:
Unable to transfer planned purchase order created in Enterprise Planning package, to actual purchase order. This happens
if the setup of master data is such that the Invoice From Business Partner code is different from Ship From Business
Partner code and Ship From Business Partner does not have Invoice From role.
SOLUTION DESCRIPTION:
It is possible to transfer planned purchase order created in Enterprise Planning package to actual purchase order.
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: 134450
SITUATION IDENTIFIED IN:
"Bank Balances" (tfcmg2101s000)
SITUATION DESCRIPTION:
Opening Balance is not correctly calculated within session 'Bank Balances' (tfcmg2101s000) when option 'Other
Currencies allowed' is enabled for the Bank relation (tfcmg0510m000) and an opening balance exists in more than one
currency.
SOLUTION DESCRIPTION:
Opening balance is calculated correctly in session 'Bank Balances'.
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: 134471
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
1. Sales Issues on PCS project are recognized as "Incoming value" on both the "Interim Sales Delivery (PCS / WIP)" and
"Inventory" acounts.
This is incorrect and results in an overstatement of the PCS wip account. The amount being issued should be
recognized as incoming on the
"Interim Sales Delivery (PCS / WIP)" account and as Outgoing on the "Inventory" acount.
2. When for a PCS project no transactions are posted yet, values are being printed twice with a blank ledger account,
although the message "Only posted integration Transactions will be printed" is printed.
SOLUTION DESCRIPTION:
1. In session "Print Project Work In Process" (tipcs3480m000) with option Detail level "By Ledger account" the Sales
Issues on a PCS project are now recognized as incoming on the "Interim Sales Delivery (PCS / WIP)" account and as
Outgoing on the "Inventory" acount.
2. With option Detail level "By Ledger account" values are now only being printed when they are posted.
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: 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: 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: 134535
SITUATION IDENTIFIED IN:
"Process Statement Batch" (tfcmgl275m00l)
SITUATION DESCRIPTION:
During Process of Statement Batch, Split up of Statement amount was not matching with Payment agreement, when Direct
Debit batch has both Sales invoices and negative amount Credit notes.
SOLUTION DESCRIPTION:
During Process of Statement Batch, Split up of Statement amount is matching with Payment agreement when Direct Debit
batch has both Sales invoices and negative amount Credit notes.
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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 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: 134912
SITUATION IDENTIFIED IN:
"Print Project Work In Process" (tipcs3480m000)
SITUATION DESCRIPTION:
There are 3 cases where Costs are booked on a Service order linked to a PCS project, and where these Costs are not
recognized
as "Outgoing value" in "Print Project Work In Process" (tipcs3480m000). This results in wrong WIP amounts.
Case 1:
Service Order linked to a PCS Project, and service order costs are made marked as "internal";
These Costs are booked as "Internal Service Costs", but are not seen in "Print Project Work In Process" (tipcs3480m000)
as
"Outgoing value".
Case 2 :
Service order which is created from a Field change order is linked to a PCS Project; when costs are booked on this service
order
related to Field change order activities, then these costs are booked as "Field change order Costs". These costs are not
seen in
"Print Project Work In Process" (tipcs3480m000) as "Outgoing value".
Case 3:
Service order with Warranty Costs is linked to a PCS Project; when Warranty Costs are booked on this service order these
Costs
are booked as "Warranty Costs". These costs are not seen in "Print Project Work In Process" (tipcs3480m000) as
"Outgoing value".
In all 3 situations the WIP amount in Service and PCS is not correct.
SOLUTION DESCRIPTION:
The session "Print Project Work In Process" ( tipcs3480m000 ) is modified such that the integration transaction with
Transaction Origin "Service" and Financial transaction "Internal Service Costs" or "Field change order Costs" or
"Warranty Costs" are now included in the "Outgoing value" amount on the report. Because of this also the WIP amount is
now correct.
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: 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: 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: 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: 135055
SITUATION IDENTIFIED IN:
"Receipts" (whinh3520m000)
SITUATION DESCRIPTION:
When purchase order receipts are done in "Receipts"(whinh3520m000), then unexpected small amounts are posted as
results in finance. The result amount is posted on Surcharge component and is due to surcharges defined for the item in
"Item surcharges"(ticpr1510m000).
SOLUTION DESCRIPTION:
No results are posted in "Integration Transaction by Project/Order"(tfgld4510m000), when purchase order receipts are
done in "Receipts"(whinh3520m000) for an Item having surcharges defined.
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: 135074
SITUATION IDENTIFIED IN:
"Print Specifications Delivered, Not Yet Invoiced" (tfacr1432m000)
SITUATION DESCRIPTION:
In report "Print Specifications Delivered, Not Yet Invoiced" (tfacr1432m000), the amount is incorrectly calculated for an
order/position because of incorrect rounding.
SOLUTION DESCRIPTION:
The report now prints correct values.
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: 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: 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: 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: 158774
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000, tfcmgl200m000)
SITUATION DESCRIPTION:
Implement 1099-MISC requirements per U.S. IRS tax publication 1220 for year 2002.
The following solutions were for the 2001 changes:
156275 - All versions - The solution with the IRS changes for 2001 is # 156275
4c, 4b & 3b solutions to load with the 2001 updates are # 157002, 157014 and 157431
5b & 5c solutions to load with the 2001 updates are # 157002, 157014, 157220, 157431 and 156842
The IRS has not made any significant changes to the 1099-MISC paper form for the year 2002.
This will be monitored on a regular basis and any changes will be noted and updated in this generic solution.
Electronic form information is available in Internal Revenue Bulletin 2002-25 as a Revenue Procedure.
DF # 208852 has been logged to accommodate electronic filing change requirements per IRB 2002-25.
Laser printer instructions are now available. See solution 157257
SOLUTION DESCRIPTION:
General
(1) 9-track magnetic tape is no longer an acceptable type of media for submitting information returns to IRS/MCC.
(2) A new field Record Sequence Number was added to Field Positions 500-507 in all records. The Record Sequence Number
will be in Field Positions 500-507 of the "T" Record, the "A" Record(s), the "B" Record(s), the "C" Record(s), any
applicable "K" Record(s), and the "F" Record.
Programming Changes - Transmitter "T" Record:
(1) For all forms, Payment Year, Field Positions 2-5, must be incremented to update the four-digit report year (2001 to
2002), unless reporting prior year data.
(2) Contact Email Address was added to Field Positions 359-393.
(3) Cartridge Tape File Indicator was moved to Field Positions 394-395.
(4) Electronic File name for a Replacement File was moved to Field Positions 396-410.
(5) Transmitter's Media Number was added to Field Position 411-416.
(6) Vendor Indicator was moved to Field Position 518.
(7) Vendor Name was moved to Field Positions 519-558.
(8) Vendor Mailing Address was moved to Field Positions 559-598.
(9) Vendor City was moved to Field Positions 599-638.
(10) Vendor State was moved to Field Positions 639-640.
(11) Vendor ZIP code was moved to Field Positions 641-649.
(12) Vendor Contact Name was moved to Field Positions 650-689.
(13) Vendor Contact Phone Number and Extension was moved to Field Positions 690-704.
(14) Vendor Contact Email Address was moved and expanded to 35 positions in Field Positions 705-739.
Programming Changes - Payer "A" Record:
(1) For all forms, Payment Year, Field Positions 2-5, must be incremented to update the four-digit report year (2001 to
2002), unless reporting prior year data.
Programming Changes - Payee "B" Record:
(1) For all forms, Payment Year, Field Positions 2-5, must be incremented to update the four-digit report year (2001 to
2002), unless reporting prior year data.
Programming Changes - End of File "F" Record:
(1) Total Number of Payees was added to Field Positions 50-57.
Multi-site: Several multisite issues have also been resolved for companies that invoice and make payment across
multiple companies.
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: 160348
SITUATION IDENTIFIED IN:
"Rebuild Ledger/Dimension History of Period" (tfgld3206m000)
SITUATION DESCRIPTION:
When rebuilding ledger/dimension history with the "Opening Balance" box checked, the Dual Accounting Indicator field
in table tfgld206 (Opening Balances - Combination of Dimension/Ledger/Currency) was not being populated.
SOLUTION DESCRIPTION:
The Dual Accounting Indicator field in table tfgld206 (Opening Balances - Combination of Dimension/Ledger/Currency)
is now being populated based on the value of the Dual Accounting Indicator in the Chart of Accounts.
SPECIAL INSTRUCTIONS:
None.

Solution: 160372
SITUATION IDENTIFIED IN:
"Post Integration to Finance Transactions" (tfgld4201m000)
SITUATION DESCRIPTION:
When using session tfgld4201m000 (Post Integration Transactions to Finance) or other sessions that are capable of creating
transactions to finance, if the session is unable to post to the next open period, the English version of the error message
that is responsible for notification is different from its Dutch and German counterparts.
SOLUTION DESCRIPTION:
The error message in now correct across all three languages (English, Dutch, and German).
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: 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: 160478
SITUATION IDENTIFIED IN:
"Ledger History" (tfgld3501s000)
"Distribution By Period For Ledger Account" (tfgld3505m000)
SITUATION DESCRIPTION:
When running the session if the percentage variance was greater than 999.99 or less than -999.99 then overflow characters
'#####' were displayed on the form and an error was written into the bshell log.
SOLUTION DESCRIPTION:
A change has been made to several forms to allow another decimal place to the percent variance field. The sessions will
now allow values from -9999.99 to 9999.99 to be displayed without error. Anything exceeding the above range will still
be displayed as overflow characters "#####" and should be controlled by using proper data.
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: 160626
SITUATION IDENTIFIED IN:
"Post Transactions" (tpppc4202m000)
SITUATION DESCRIPTION:
When using session tpppc4202m000 (Post Transactions) or other sessions that are capable of creating transactions to
finance, if the integration parameter (tfgld4150s000) "Posting to Next Open Period Allowed" is set - transactions can be
posted into closed periods.
SOLUTION DESCRIPTION:
The process tfglddll4011 (Write Integration Transactions part II) has been modified to properly handle posting transactions
to the correct period.
SPECIAL INSTRUCTIONS:
Please review and install solution 159439, which corrects tfglddll4010 (Write Integration Transactions) to correctly use
the "Post to Next Open Period Allowed" parameter. You should also review and install solution 160372 that corrects an
incorrect error message.

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: 160768
V
ERSION(S):
B40_c, B50_b, B50_c, B52_a
SITUATION IDENTIFIED IN:
"Print Unbalanced Ledger Accounts during Year End " (tfgld6403m000)
SITUATION DESCRIPTION:
The session designed to show unbalanced ledger accounts would also erroneously print data for balanced ledger accounts.
(B40_c):
This would only happen when selecting 'no' for the option 'Print only History (tfgld201/tfgld205)' and if there were
finalized opening balance transactions within the selection range.
(B50_b, B50_c, and B52_a):
This would only happen when selecting 'yes' for the option 'also include finalized transactions (tfgld106)' and if there
were finalized opening balance transactions within the year/ledger account/currency ranges selected.
SOLUTION DESCRIPTION:
The problem occurred because the total of all finalized transactions including opening balance transactions were
compared to history tables amounts. The history tables do not include opening balance amounts so the report would
always show the amount of the opening balance transactions as a difference.
(B40_c only)-
- A second report has been added to the session to compare opening balance transactions.
- The original session report has been renamed to better describe the function of the report.
- The label field on the form 'Print only History (tfgld201/tfgld205)' has been replaced by 'also include finalized
transactions (tfgld106)' as was already done in future versions. Now choosing 'yes' on the form will include table
'Finalized Transactions' (tfgld106) where previously 'No' would include data from this table.
(All Versions)
- Selection of finalized transactions has been changed to not select opening balance transactions from the finalized
transactions table (tfgld106) when running with the session using report option #1 "Compare History tables tfgld201 and
tfgld205"
- Selection of finalized transactions has been changed to select only opening balance transactions from the finalized
transactions table (tfgld106) when running with the session using report option #2 "Compare Opening Balances tables
tfgld203 and tfgld206"
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: 160895
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000)
SITUATION DESCRIPTION:
When running session tfcmg3204m000 (File 1099-MISC) in ERP versions (5b & 5c) using the FORM print mode the session
may not print the 'payers' telephone number on the 1099-MISC form. The session may also produce one or both of the
following error messages in all supported versions 3.1b to 5c. For versions less than 4c the session id is tfcmgl200m000
(File 1099-MISC).
Fatal error : Error 205 (Out of range) on tfcmg304xxx in db_insert(n)
For versions before 4c:
Fatal error : Error 205 (Out of range) on tfcmg938xxx in db_insert(n)
The range error can occur when more than 10 payments have been applied to a business partner or supplier per a single
invoice.
When running in a multi-site environment the following error may also be generated:
Fatal error: Error 100 (Duplicate value) on tfcmg304nnn (Max retries (10)
For versions before 4c
Fatal error: Error 100 (Duplicate value) on tfcmg938nnn (Max retries (10)
The duplicate error can occur in multi-site environments were document types are not unique between individual
companies.
SOLUTION DESCRIPTION:
The 1099-MISC report (FORM) has been corrected to properly print the 'payers' telephone number on the form. The 10
payments per business partner or supplier limitation have been increased to 1000. And for multi-site configurations, the
session will now properly handle duplicate documents between different companies correctly.
SPECIAL INSTRUCTIONS:
Because there is a change to a table definition in this solution, it will also be necessary to run the session Create
Runtime Data Dictionary (ttadv5210m000).

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: 160934
SITUATION IDENTIFIED IN:
"Period Status" (tfgld0107m000)
SITUATION DESCRIPTION:
There are problems when attempting to close tax periods.
#1- (B40_c, B50_b) An error message that unposted fixed asset transactions existed was given even though no such
transactions existed. This occurred because the tax year and period being closed were being compared to the fiscal
year/period in the fixed asset tables.
#2- (B50_b, B50_c) A check for unposted recurring transactions was not done correctly when the company calendar has
different tax and fiscal years. When closing a tax period, the fiscal year was being checked instead of the tax year. This
could result in an error message that unposted recurring transactions exist when no transactions existed or result in no
error message being given when there were transactions present.
#3- (B40_c) When giving the error message that unposted recurring transactions exist, the fiscal year and batch number are
displayed to allow the users to see what is in error. When getting this error was displayed, the fiscal year was left blank
in the error message.
SOLUTION DESCRIPTION:
- The session will now only check for unposted fixed asset transactions when closing fiscal periods.
- The error check for unposted recurring transactions will now be done based on tax year when closing a tax period.
- The error message will now display the fiscal year as part of the error message for unposted recurring transactions
present.
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: 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: 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: 160998
SITUATION IDENTIFIED IN:
"Calculate Cost Prices by Project" (tipcs3250m000)
SITUATION DESCRIPTION:
When buying purchased items for a project and returning the full quantity for a different amount, the actual average item
cost price was too high, because the total quantity received was set to 1 instead of the actual quantity of 0. Example:
Purchase order for 10 x item X for $100, return order for 10 x item X for $60. The total cost for the project is $400, but
the actual inventory of item X is 0. The actual cost price used to be calculated as $400 divided by 1, which resulted in a
very high average actual cost price for item X.
SOLUTION DESCRIPTION:
The average actual cost price for this item is now set to $0 in this situation, but the cost is still reflected in the project
costs.
SPECIAL INSTRUCTIONS:
None.

Solution: 161013
SITUATION IDENTIFIED IN:
"Distribution by Company" (tfgld3510m000)
SITUATION DESCRIPTION:
The following two errors occur when the session is started.
Error : unknown formfield 'z.cwoc.sj.l'
Error : unknown formfield 'cwoc.desc.sj.l'
These fields are for the work center and its description and are duplicates, as the fields z.wrkc.sj.l and wrkc.desc.sj.l exist
for this.
SOLUTION DESCRIPTION:
Since the fields causing the error are duplicates, they are being removed from the form.
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: 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: 161090
SITUATION IDENTIFIED IN:
"Global Selection of Batches For Finalization" (tfgld1210m000)
SITUATION DESCRIPTION:
Problem #1(B52_a)- When finalizing a batch from 'Maintain Transactions' (tfgld1101m000), the error message "Invalid
Period" was always given if a company did not use reporting periods.
Problem #2 (B50_b, B50_c, B52_a) The session has a check to make sure all transaction lines have been processed by the
background programs if the update mode of the transaction type is "Real Time" or "End Of Session". This check was not
done correctly in a multi-finance environment which could cause batches to be selected for finalization that have not yet
been processed by the background process.
SOLUTION DESCRIPTION:
Error checks for invalid reporting periods are no longer done if a company does not use reporting periods. Batches
which contain transaction lines unprocessed by the background programs (Real Time or End of Session update mode) will
no longer be selected for finalization in a multi-company environment.
SPECIAL INSTRUCTIONS:
None.

Solution: 161127
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000, tfcmgl200m000)
SITUATION DESCRIPTION:
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session does not select invoices that
have been reconciled.
SOLUTION DESCRIPTION:
The session's tfcmg3204m000 and tfcmgl200m000 have been modified to select invoices that have reconciled.
SOLUTION 161184
*********************************
***Prior to loading this solution please make sure solution 158774 & 160895 are also loaded. Please note the loading
instructions for these two pre-requisites - you will need to run the create runtime data dictionary for the tf package.****
VERSION(S):
3.1_b, B40_b, B40_c, B50_b, B50_c
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: 161149
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
Errant variance postings lead to work in process amounts for production orders upon closing of the orders.
SOLUTION DESCRIPTION:
Variance calculations are corrected and work in process for production orders is zero upon closing.
SPECIAL INSTRUCTIONS:
None.

Solution: 161184
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000, tfcmgl200m000)
SITUATION DESCRIPTION:
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session may not select invoices
reconciled in the next year (2003).
SOLUTION DESCRIPTION:
The session's tfcmg3204m000 and tfcmgl200m000 have been modified to use the anticipated payment year vs. the
reconciled year.
SOLUTION 161209. Please note the loading instructions for these two
pre-requisites - you will need to run the create runtime data dictionary for the tf package.****
VERSION(S):
3.1_b, B40_b, B40_c, B50_b, B50_c
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: 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: 161209
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000, tfcmgl200m000)
SITUATION DESCRIPTION:
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session will not select invoices if the tax
year and fiscal year are the different.
SOLUTION DESCRIPTION:
The session's tfcmg3204m000 and tfcmgl200m000 have been modified to exclusively use the tax year.
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: 161226
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000, tfcmgl200m000)
SITUATION DESCRIPTION:
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session may not include invoices that
were not processed via anticipated payment steps.
SOLUTION DESCRIPTION:
The session's tfcmg3204m000 and tfcmgl200m000 have been modified to include electronic or wired invoice / payment
scenerios.
SOLUTION 161209. Please note the loading instructions for these two
pre-requisites - you will need to run the create runtime data dictionary for the tf package.****
VERSION(S):
3.1_b, B40_b, B40_c, B50_b, B50_c
SPECIAL INSTRUCTIONS:
After applying this solution (161226), solution # 161235 should be also applied.

Solution: 161235
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000 (B40c and above), tfcmgl200m000(B40b and below))
SITUATION DESCRIPTION:
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), invoices paid by wire transfer payment method
using no anticipated steps are not selected for 1099's when paid in the following year.
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), the session may select only one check for
invoices with several checks (this was happening for invoices with and without anticipated steps)
SOLUTION DESCRIPTION:
The session's tfcmg3204m000 and tfcmgl200m000 have been modified to include electronic or wired invoice and
multiple payment scenerios.
SOLUTION 161209. Please note the loading instructions for these
three pre-requisites.****
VERSION(S):
3.1_b, B40_b, B40_c, B50_b, B50_c
SPECIAL INSTRUCTIONS:
***Prior to loading this solution please make sure solution 158774 & 160895 are also loaded. IF FISCAL YEAR
IS NOT SETUP AS A CALENDAR YEAR PLEASE LOAD SOLUTION 161209. Please note the loading instructions for
these three pre-requisites.****

Solution: 161236
SITUATION IDENTIFIED IN:
"Print Finalized Transactions By Date" (tfgld1440m000)
SITUATION DESCRIPTION:
-When running the session in a multicompany/dependent currency system and printing for all companies it was possible for
the wrong currency or for no currency to be displayed on the report.
-(B50_c only) The option 'rotate currency' was not always enabled/disabled at the correct time. This option should be
disabled if running the session in a multicompany/dependent currency system and printing for all companies. On changing
the form field 'print all companies' the session would not check to see if the rotate currency option should be enabled or
disabled.
SOLUTION DESCRIPTION:
Change have been made to the reports so that the same currency selected on the session form is displayed on the report
header. All amount fields will also print in the currency format of this currency.
The program script has been changed so that when selecting or unselecting 'Print All Companies" the program will check to
determine if the user should be allowed to choose the option "rotate currency".
SPECIAL INSTRUCTIONS:
None.

Solution: 161259
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When closing more than one production order with each order having more than one cost component with a price variance,
the price variance amounts for an order are not cleared between orders and are added into each subsequent order's price
variances. This results in incorrect price variances and incorrect calculation variances for a production order.
SOLUTION DESCRIPTION:
The price variance amounts are cleared between production orders so that the price variance will not incorporate amounts
from previously closed orders.
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: 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: 161295
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When closing a production order with more than 300 operations, a fatal "Out of Dims" error occurs.
SOLUTION DESCRIPTION:
A production order with more than 300 operations can be closed without the fatal error.
SPECIAL INSTRUCTIONS:
None.

Solution: 161332
SITUATION IDENTIFIED IN:
"Archive/ Purge Financial Transactions" (tfgld6205m000)
SITUATION DESCRIPTION:
When archiving transactions with text, the error 606 "reference does not exist on tfgld106" (on the current company) was
given which prevents the process from finishing.
SOLUTION DESCRIPTION:
This error occurred because the wrong company was used for the text in the company where the session was being run.
Changes have been made so that the correct company is now used and the error will no longer occur.
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: 161353
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When closing a production order that makes use of more than 2000 cost components, a fatal error: "Index out of dims
(2001)" occurs.
SOLUTION DESCRIPTION:
Production orders using more than 2000 cost components can now be closed without the fatal error.
SPECIAL INSTRUCTIONS:
None.

Solution: 161389
SITUATION IDENTIFIED IN:
"Ledger History" (tfgld3501s000)
SITUATION DESCRIPTION:
If company currency system is dependent and Ledger History is printed for one specific company, the default currency
was reference currency instead of local currency.
SOLUTION DESCRIPTION:
Now if Ledger History is to be shown for only one company the local home currency of that company will be selected by
default.
SPECIAL INSTRUCTIONS:
None.

Solution: 161409
SITUATION IDENTIFIED IN:
"File 1099-MISC" (tfcmg3204m000 (B40c and above), tfcmgl200m000(B40b and below))
SITUATION DESCRIPTION:
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC), Standing orders created in current year and
reconciled in the next year, are reported in the reconciled year.
When running session tfcmg3204m000 or tfcmgl200m000 (File 1099-MISC) for a reconciled standing order the currency
information maybe invalid. This can cause the order amount to be incorrectly calculated, and not reported in 1099-MISC.
SOLUTION DESCRIPTION:
The session's tfcmg3204m000 and tfcmgl200m000 have been modified to correctly handle standing orders that have been
created & reconciled in separate years. Further, the session now correctly calculates the amount using the correct
currency code.
SOLUTION 161209. Please note the loading instructions for these
three pre-requisites.****
VERSION(S):
3.1_b, B40_b, B40_c, B50_b, B50_c
SPECIAL INSTRUCTIONS:

Solution: 161410
SITUATION IDENTIFIED IN:
"Rebuild Opening Balance/History from Transactions" (tfgld3203m000)
SITUATION DESCRIPTION:
The program rebuild opening balance/history from transactions takes a long time to complete.
SOLUTION DESCRIPTION:
Technical changes have been made to program script so that the session run more efficiently.
SPECIAL INSTRUCTIONS:
None.

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: 161454
SITUATION IDENTIFIED IN:
"Archive and Purge Integration Transactions" (tfgld4210m000)
SITUATION DESCRIPTION:
When attempting to run session tfgld4210m000 (Archive and Purge Integration Transactions) in a job, the session fails to
execute.
SOLUTION DESCRIPTION:
The session was terminating abnormally, because several verification dialogs were being prompted for user input. These
dialogs are still prompted when creating a job, however they no longer interfere when the session executes in a job.
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: 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: 161573
SITUATION IDENTIFIED IN:
"Import Actual Costs from GLD" (tfcat2210m000)
SITUATION DESCRIPTION:
When using session tfcat2210m000 (Import Actual Costs from GLD) if the default currency code in the FBS parameters has
not been setup or contains a currency that is not a home currency - the session will generate a Fatal Error: tfgld205.fdah
index 0 out of dims.
SOLUTION DESCRIPTION:
If a default currency has not been setup in FBS parameters with one of the company's home currencies, an appropriate error
message is displayed and the session will exit. Follow the instructions in the error message before re-running this session.
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: 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: 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: 161729
SITUATION IDENTIFIED IN:
"Close Periods" (tfgld1206m000)
SITUATION DESCRIPTION:
Get a BW error because a couple of messages in the script are missing an argument. The messages that have the problem
are displayed when the P&L document is not in balance
SOLUTION DESCRIPTION:
The necessary changes have been ported from 50c (SOL 161510) to the 50b script. Messages will not cause a BW error
anymore.
SPECIAL INSTRUCTIONS:
None.

Solution: 161740
SITUATION IDENTIFIED IN:
"Print Trial Balance - Ledger Account/Dimensions" (tfgld3404m000)
"Print Trial Balance - Dimensions" (tfgld3405m000)
"Print Trial Balance - Dimensions/Ledger Account" (tfgld3406m000)
SITUATION DESCRIPTION:
If the user chose to generate the report without visiting the second form/tab the following errors occurred:
1. Run time error "Index out of Dims" was given and the session aborted. This occurred only for tfgld3404m000.
2. The report output did not print the currency in which the report was being printed.
SOLUTION DESCRIPTION:
The problem happened because of some initialization issues in the scripts. These have been corrected.
SPECIAL INSTRUCTIONS:
None.

Solution: 161758
SITUATION IDENTIFIED IN:
"Integration Mapping Scheme (General)" (tfgld4500m000)
"Integration Transactions by Project/Order" (tfgld4510m000)
"Integration Transactions by Document Line" (tfgld4512m000)
"Integration Transactions Log" (tfgld4532m000)
SITUATION DESCRIPTION:
It is possible to set up a mapping scheme for the integration combination Purchase/Receipt(Invoiced). However, no
integration transactions with this combination are ever created.
SOLUTION DESCRIPTION:
The integration combination Purchase/Receipt(Invoiced) is not used by the application. It has been removed from all the
required sessions.
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: 161791
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When closing production orders and calculating price variances, rounding between actual and estimated costs can differ
resulting in incorrect price variance postings.
SOLUTION DESCRIPTION:
The rounding of costs in calculating price variances has been modified and the incorrect price variances are no longer
posted.
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: 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: 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: 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: 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: 162299
SITUATION IDENTIFIED IN:
"Print Financial Transactions" (tcfin1400m000)
SITUATION DESCRIPTION:
When using a multi-company setup and printing the financial transactions of a logistic company, the exchange rate types
of the company were not correctly read. This resulted that the amounts on the report were not converted to the report
currency.
SOLUTION DESCRIPTION:
The exchange rate types are now correctly read for the actual company. The defined 'Exchange Rate Types' (tcmcs040) and
the 'Currency Rates' (tcmcs008) need to be shared between all linked companies and the exchange rate types need to be
the same for all the linked company.
SPECIAL INSTRUCTIONS:
None.

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: 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: 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: 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: 162559
SITUATION IDENTIFIED IN:
"Close Production Orders" (ticst0201m000)
SITUATION DESCRIPTION:
When closing shop floor orders, with variances posted across more than one detailed cost component, resulting inventory
variances, posted by aggregated cost component, can differ from variance amounts posted to the general ledger due to
differing methods of rounding.
SOLUTION DESCRIPTION:
Variances, posted to inventory and the general ledger, are now rounded in the same manner eliminating the potential for
rounding error discrepancies between the two packages.
SPECIAL INSTRUCTIONS:
On May 22th 2003 the missing Japanese localization solution was added. Customers who use the Japanese localization,
and have downloaded or installed the standard solution before May 21th should download and install the Japanese
solution.

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: 162608
SITUATION IDENTIFIED IN:
"Archive/Purge Finance Transactions" (tfgld6205m000)
SITUATION DESCRIPTION:
Multi-company transactions in which the current company is the target company, do not always get archived even if they
belong to the fiscal year being archived.
SOLUTION DESCRIPTION:
The archiving session picks up data from the Finalized Transactions table (tfgld106) based on the batch number and year
retrieved from the Batch Status table (tfgld100).
In an inter-company transaction the transactions in the target company are stored with the batch number of the
originating company. If the target company has less usage and thus the batch number has not advanced to the number
which was used in the inter-company transaction then such transactions will be missed from the archive/purge process.
Now an additional search for such transactions is done by making use of the Relations Inter-company Documents table
(tfgld112) to make sure the transactions missed in the first processing get processed.
After downloading this solution please run this session in the last archived year and it will process all the missed
transactions from that year and any earlier year..
SPECIAL INSTRUCTIONS:
None.

Solution: 162628
SITUATION IDENTIFIED IN:
"Copy Item Data" (tcibd0205m000)
SITUATION DESCRIPTION:
When copying general item data, and no warehouse item data exists, an error 606 (reference does not exist) is received.
SOLUTION DESCRIPTION:
Now when copying general item data, and no warehouse item data exists, the item is copied without error.
SPECIAL INSTRUCTIONS:
None.

Solution: 162742
SITUATION IDENTIFIED IN:
"Update Interim History - Ledger Account Totals" (tfgld1215s000)
"Rebuild Ledger History" (tfgld3201m000)
"Rebuild Dimension History" (tfgld3202m000)
"Rebuild Opening Balance/History from Transactions" (tfgld3203m000)
"Close Year - Provisional" (tfgld6201m000)
SITUATION DESCRIPTION:
Ledger history amounts that are shown on the Trial Balance reports are rounded incorrectly. Rounding in the sessions
listed above has been done using the same rounding factor for all amounts regardless of currency.
SOLUTION DESCRIPTION:
Each currency has its own rounding factor, which determines the number of decimal places up to which an amount is stored
and displayed in Baan. Due to a problem the same rounding factor (for the first currency read) got re-used while
calculating rounded amounts for the other currencies processed by the above sessions. This led to amounts being stored
with incorrect number of decimals. The above sessions have been corrected to use the rounding factor of the currency
whose amounts are being processed. The amounts in the history tables can be corrected after downloading this solution and
running the re-build sessions listed above again.
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.

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.

135397

SITUATION IDENTIFIED IN:

"'Reconciliation of Receipts/Payments" (tfcmg2103s000)

SITUATION DESCRIPTION:

Once payment document is rejected in the session 'Reconciliation of Receipts/Payments

(tfcmg2103s000)' can't be re-opened again. If the rejected payment document is tried to re-open again then the re-open process fails and an error message "Zero Amount not allowed" is displayed on the screen.

SOLUTION DESCRIPTION:

Payment document rejected in the session 'Reconciliation of Receipts/Payments (tfcmg2103s000)’ is allowed to re-open again, if the rejected payment reconciliation document batch is not finalized. No error message is displayed while re-opening the rejected payment reconciliation document.